Use Cases Combined with Booch/OMT/UML
Process and Products
Published on 24. July 1997
Book
Mixed media product
465 pages
978-0-13-727405-5 (ISBN)
Description
For software engineering courses, with a focus on object technology and software process.
This book will illustrate how to help organizations evolve from ad hoc software development processes to a clearly-defined custom framework that builds on existing knowledge, can be monitored, and delivers significantly improved object-oriented software quality throughout the entire project lifecycle.
This book will illustrate how to help organizations evolve from ad hoc software development processes to a clearly-defined custom framework that builds on existing knowledge, can be monitored, and delivers significantly improved object-oriented software quality throughout the entire project lifecycle.
More details
Language
English
Place of publication
Upper Saddle River
United States
Publishing group
Pearson Education (US)
Target group
College/higher education
Dimensions
Height: 240 mm
Width: 181 mm
Thickness: 23 mm
Weight
944 gr
ISBN-13
978-0-13-727405-5 (9780137274055)
Copyright in bibliographic data is held by Nielsen Book Services Limited or its licensors: all rights reserved.
Schweitzer Classification
Content
I. INTRODUCTION.
Case Study Problem Statement. Habitat Control Center (HCC).
Introduction. Sealed Environment Monitor (SEM). Monitored Data. Alarm Conditions. Annunciator Panel. Nominal Values. Alarms.
II. SYSTEMS ENGINEERING.
Phase 1: Requirements Engineering.
Identify External Interfaces. Capture "shall" Statements. Allocate Requirements. Prioritize Requirements.
Phase 2: Systems OOA-Static View.
Identify Software Use Cases. Develop Scenarios. Develop Draft GUI Sketches. Establish Project Categories. Allocate Use Cases to Categories. Develop System Category Diagram (SCD).
Phase 3: Systems OOA-Dynamic View.
Allocate Categories to Category Managers/Leads. Develop Category Interaction Diagrams (CIDs).
Phase 4: Hardware/Software Split.
Partition Categories.
III. SOFTWARE OBJECT-ORIENTED ANALYSIS.
Phase 5: Software OOA-Static View.
Initiate Category Class Diagram (CCD). Refine Inheritance/Aggregation Hierarchies. Decompose Scenario. Analyze Annotations. Update CCD. Add View Classes to the CCD. Complete Class Specifications (CSs). Develop Class-Centric Class Diagram (CCCD).
Phase 6: Software OOA-Dynamic View.
Develop State Transition Diagram (STD). Refine Category Interaction Diagram (CID). Update Category Class Diagram (CCD). Update Class Specification (CS).
IV. SOFTWARE OBJECT-ORIENTED DESIGN - LANGUAGE-INDEPENDENT.
Phase 7: Software OOD-Process View.
Initiate the Process Architecture Diagram (PAD). Identify Processes. Identify Processors. Allocate Processes to Processors. Allocate Classes to Processes. Develop Process Interaction Diagram (PID). Develop State Transition Diagrams (STDs). Update Class Specifications(CSs).
Phase 8: Software OOD-Static View.
Update Category Class Diagram (CCD). Reuse Existing Design Patterns. Update Class Specification (CS).
Phase 9: Software OOD-Dynamic View.
Update Classes/Messages on Interaction Diagrams (IDs). Add Exception Handling.
V. SOFTWARE OBJECT-ORIENTED DESIGN-LANGUAGE-DEPENDENT.
Phase 10: Software OOD-Language Representation.
Transition to Implementation Class. Represent Inter-Class Visibility. Develop Class "Body" Structure. Compile Class. Integrate Controller Class PDL. Process PDL. Implement View Classes. Develop Database Schema.
Phase 11: Method Design.
Decide on Representation Mechanism. Develop Method PDL. Process PDL.
VI. IMPLEMENTATION.
Phase 12: Class Implementation/Class Test.
Implement Class Methods. Determine Class Test Strategy. Develop Class Test Drivers. Perform Class Test.
VII. TEST.
Phase 13: Category Test.
Phase Overview. Develop Category Test Strategy. Develop Category Test Drivers. Perform Intra-Category Tests. Perform Inter-Category Tests.
Phase 14: Software Integration and Test (SWIT).
Develop SWIT Test Plan. Perform SWIT.
Phase 15: System Integration and Test (SIT).
Develop SIT Test Plan. Perform SIT Test.
Phase 16: Requirements Trace.
Generate Forward Requirements Trace (FRT). Generate Reverse Requirements Trace (RRT).
VIII. POST DELIVERY.
Phase 17: Maintenance Phase Overview.
Requirements Engineering. System OOA. System OOA-Dynamic View. Hardware/Software Split. Software OOA-Static View. Software OOA-Dynamic View. Software OOD-Process View. Software OOD-Static View. Software OOD-Dynamic View. Language Representation. Method Design. Class Implementation/Class Test. Category Test. Software Integration and Test (SWIT). System Integration Test (SIT). Requirements Trace.
Appendix A: Acronym List.
Appendix B: Glossary.
Appendix C: Bibliography.
Appendix D: Case Study Solutions.
Appendix E:Tracking Progress.
Appendix F: Configuration Management (CM).
Index.
Case Study Problem Statement. Habitat Control Center (HCC).
Introduction. Sealed Environment Monitor (SEM). Monitored Data. Alarm Conditions. Annunciator Panel. Nominal Values. Alarms.
II. SYSTEMS ENGINEERING.
Phase 1: Requirements Engineering.
Identify External Interfaces. Capture "shall" Statements. Allocate Requirements. Prioritize Requirements.
Phase 2: Systems OOA-Static View.
Identify Software Use Cases. Develop Scenarios. Develop Draft GUI Sketches. Establish Project Categories. Allocate Use Cases to Categories. Develop System Category Diagram (SCD).
Phase 3: Systems OOA-Dynamic View.
Allocate Categories to Category Managers/Leads. Develop Category Interaction Diagrams (CIDs).
Phase 4: Hardware/Software Split.
Partition Categories.
III. SOFTWARE OBJECT-ORIENTED ANALYSIS.
Phase 5: Software OOA-Static View.
Initiate Category Class Diagram (CCD). Refine Inheritance/Aggregation Hierarchies. Decompose Scenario. Analyze Annotations. Update CCD. Add View Classes to the CCD. Complete Class Specifications (CSs). Develop Class-Centric Class Diagram (CCCD).
Phase 6: Software OOA-Dynamic View.
Develop State Transition Diagram (STD). Refine Category Interaction Diagram (CID). Update Category Class Diagram (CCD). Update Class Specification (CS).
IV. SOFTWARE OBJECT-ORIENTED DESIGN - LANGUAGE-INDEPENDENT.
Phase 7: Software OOD-Process View.
Initiate the Process Architecture Diagram (PAD). Identify Processes. Identify Processors. Allocate Processes to Processors. Allocate Classes to Processes. Develop Process Interaction Diagram (PID). Develop State Transition Diagrams (STDs). Update Class Specifications(CSs).
Phase 8: Software OOD-Static View.
Update Category Class Diagram (CCD). Reuse Existing Design Patterns. Update Class Specification (CS).
Phase 9: Software OOD-Dynamic View.
Update Classes/Messages on Interaction Diagrams (IDs). Add Exception Handling.
V. SOFTWARE OBJECT-ORIENTED DESIGN-LANGUAGE-DEPENDENT.
Phase 10: Software OOD-Language Representation.
Transition to Implementation Class. Represent Inter-Class Visibility. Develop Class "Body" Structure. Compile Class. Integrate Controller Class PDL. Process PDL. Implement View Classes. Develop Database Schema.
Phase 11: Method Design.
Decide on Representation Mechanism. Develop Method PDL. Process PDL.
VI. IMPLEMENTATION.
Phase 12: Class Implementation/Class Test.
Implement Class Methods. Determine Class Test Strategy. Develop Class Test Drivers. Perform Class Test.
VII. TEST.
Phase 13: Category Test.
Phase Overview. Develop Category Test Strategy. Develop Category Test Drivers. Perform Intra-Category Tests. Perform Inter-Category Tests.
Phase 14: Software Integration and Test (SWIT).
Develop SWIT Test Plan. Perform SWIT.
Phase 15: System Integration and Test (SIT).
Develop SIT Test Plan. Perform SIT Test.
Phase 16: Requirements Trace.
Generate Forward Requirements Trace (FRT). Generate Reverse Requirements Trace (RRT).
VIII. POST DELIVERY.
Phase 17: Maintenance Phase Overview.
Requirements Engineering. System OOA. System OOA-Dynamic View. Hardware/Software Split. Software OOA-Static View. Software OOA-Dynamic View. Software OOD-Process View. Software OOD-Static View. Software OOD-Dynamic View. Language Representation. Method Design. Class Implementation/Class Test. Category Test. Software Integration and Test (SWIT). System Integration Test (SIT). Requirements Trace.
Appendix A: Acronym List.
Appendix B: Glossary.
Appendix C: Bibliography.
Appendix D: Case Study Solutions.
Appendix E:Tracking Progress.
Appendix F: Configuration Management (CM).
Index.