Software engineering/Catalogs/Topics: Difference between revisions
Jump to navigation
Jump to search
imported>Pat Palmer No edit summary |
imported>Eric M Gearhart (underscores are unneccessary) |
||
| Line 1: | Line 1: | ||
This is a list of topics that sometimes fall within the field of [[software engineering]]. It is also currently a place to brainstorm items which might, or might not, end up in the main [[Software engineering]] article. See also the [[ | This is a list of topics that sometimes fall within the field of [[software engineering]]. It is also currently a place to brainstorm items which might, or might not, end up in the main [[Software engineering]] article. See also the [[List of software tools for software engineering]]. | ||
* [[Capability Maturity Model]] (CMM) - A set of guidelines from the [[Software Engineering Institute]] for assessing project maturity in the software development process, CMM classifies projects into one of five "maturity levels". Many U. S. government contracts awarded for software development require bidding vendors to use CMM guidelines. | * [[Capability Maturity Model]] (CMM) - A set of guidelines from the [[Software Engineering Institute]] for assessing project maturity in the software development process, CMM classifies projects into one of five "maturity levels". Many U. S. government contracts awarded for software development require bidding vendors to use CMM guidelines. | ||
Revision as of 12:24, 24 October 2007
This is a list of topics that sometimes fall within the field of software engineering. It is also currently a place to brainstorm items which might, or might not, end up in the main Software engineering article. See also the List of software tools for software engineering.
- Capability Maturity Model (CMM) - A set of guidelines from the Software Engineering Institute for assessing project maturity in the software development process, CMM classifies projects into one of five "maturity levels". Many U. S. government contracts awarded for software development require bidding vendors to use CMM guidelines.
- Software project risk analysis
- Project schedule estimation
- Software project or process metrics
- Code inspection
- Software project failure analysis
- Software project management
- Software reliability
- Software testing - including sub-topics such as:
- Software unit testing
- Software integration testing
- Software system testing
- Software Acceptance testing
- Software Verification
- Software Validation
- Software life-cycle models
- Design patterns
- Software development process
- SPICE - Software Process Improvement and Capability dEtermination
- CASE tools and the guy who started the idea
- requirements analysis
- software design
- code generation
- static analysis
- dynamic linking
- ISO 9000 quality assurance process standard
- Rational Unified Process (RUP)