Difference between revisions of "Chapter 9: Software Engineering Models"
(Created page with "{{TOC}} {{Acronyms|{{Acronym|name=3GL|description=3rd Generation Language}} {{Acronym|name=BNF|description=Backus-Naur Form}} {{Acronym|name=FDD|description=Feature-Driven Dev...") |
|||
| Line 9: | Line 9: | ||
{{Acronym|name=XP|description=eXtreme Programming}} | {{Acronym|name=XP|description=eXtreme Programming}} | ||
}} | }} | ||
| + | |||
| + | {{IntroSection|title=Introduction|body= | ||
| + | Software engineering models and methods | ||
| + | impose structure on software engineering with | ||
| + | the goal of making that activity systematic, | ||
| + | repeatable, and ultimately more success-oriented. | ||
| + | Using models provides an approach to problem | ||
| + | solving, a notation, and procedures for model | ||
| + | construction and analysis. Methods provide an | ||
| + | approach to the systematic specification, design, | ||
| + | construction, test, and verification of the end-item | ||
| + | software and associated work products. | ||
| + | Software engineering models and methods | ||
| + | vary widely in scope—from addressing a single | ||
| + | software life cycle phase to covering the complete | ||
| + | software life cycle. The emphasis in this | ||
| + | knowledge area (KA) is on software engineering | ||
| + | models and methods that encompass multiple | ||
| + | software life cycle phases, since methods specific | ||
| + | for single life cycle phases are covered by other | ||
| + | KAs.}} | ||
Revision as of 15:54, 26 August 2015
- 3GL
- 3rd Generation Language
- BNF
- Backus-Naur Form
- FDD
- Feature-Driven Development
- IDE
- Integrated Development Environment
- PBI
- Product Backlog Item
- RAD
- Rapid Application Development
- UML
- Unified Modeling Language
- XP
- eXtreme Programming
Software engineering models and methods impose structure on software engineering with the goal of making that activity systematic, repeatable, and ultimately more success-oriented. Using models provides an approach to problem solving, a notation, and procedures for model construction and analysis. Methods provide an approach to the systematic specification, design, construction, test, and verification of the end-item software and associated work products. Software engineering models and methods vary widely in scope—from addressing a single software life cycle phase to covering the complete software life cycle. The emphasis in this knowledge area (KA) is on software engineering models and methods that encompass multiple software life cycle phases, since methods specific for single life cycle phases are covered by other KAs.
