Software engineering: Difference between revisions
imported>Charles F. Radley (format) |
imported>Charles F. Radley (grammar) |
||
Line 3: | Line 3: | ||
The approaches used vary greatly. | The approaches used vary greatly. | ||
Most organizations who are engaged in Software Engineering | Most organizations who are engaged in Software Engineering employ some form of [[Software Development Life Cycle]], either explicitly or implicitly. The classical SDLC is the [[Waterfall]] model, which employees a sequential series of development phases culminating in a single release milestone. There are also different processes in use, including [[iterative]], and [[agile]]. In practice most processes employee some elements of the waterfall model phases, but instead of being sequential, they can be iterated multiple times. | ||
There are many techniques that are used within one or more of these approaches, some being applicable across the board and some only applying in a subset of approaches. There are [[object-oriented]], [[function-oriented]], [[rules-based]], [[state machine]], and other approaches. | There are many techniques that are used within one or more of these approaches, some being applicable across the board and some only applying in a subset of approaches. There are [[object-oriented]], [[function-oriented]], [[rules-based]], [[state machine]], and other approaches. |
Revision as of 21:12, 17 June 2007
Software engineering is "the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software".[1]
The approaches used vary greatly.
Most organizations who are engaged in Software Engineering employ some form of Software Development Life Cycle, either explicitly or implicitly. The classical SDLC is the Waterfall model, which employees a sequential series of development phases culminating in a single release milestone. There are also different processes in use, including iterative, and agile. In practice most processes employee some elements of the waterfall model phases, but instead of being sequential, they can be iterated multiple times.
There are many techniques that are used within one or more of these approaches, some being applicable across the board and some only applying in a subset of approaches. There are object-oriented, function-oriented, rules-based, state machine, and other approaches.
One of the leading organizations promoting best practices for the field of Software Engineering is the Carnegie Mellon® Software Engineering Institute(SEI). SEI has established a Capability Maturity Model scale of measuring the maturity of any software engineering organization.
References
- “IEEE Standard Glossary of Software Engineering Terminology,” IEEE std 610.12-1990, 1990.
- ↑ “IEEE Standard Glossary of Software Engineering Terminology,” IEEE std 610.12-1990, 1990.