80 likes | 207 Vues
This document explores the essential concepts of software design as outlined in the SWEBOK 2004 framework. It delves into two key activities: Architectural Design and Detailed Design. Architectural Design focuses on how software is decomposed and organized into components, while Detailed Design describes each component in sufficient detail for construction. It also highlights the significance of UML (Unified Modeling Language) diagrams, including Use Case and Class Diagrams, alongside the collaborative contributions of Grady Booch, James Rumbaugh, and Ivar Jacobson in the late 1990s.
E N D
Requirements Design Construction Testing Delivery and Installation Software Waterfall Life Cycle Concept Exploration Operations and Maintenance
Software Design From SWEBOK 2004
Two Software Design Activities • Architectural Design • Top-level design • How the software is decomposed and organized into components • Detailed Design • Describing each component sufficiently do allow for its construction
UML Diagrams • Unified Modeling Language • Collaboration of three different modeling techniques in late 1990’s • Three Amigos: Grady Booch, James Rumbaugh, Ivar Jacobson
Class Diagram Class Name, Attributes, Operations