[Book Cover]

Use Cases Combined with Booch/OMT/UML: Process and Products, 1/e

Putnam P. Texel, Texel & Co., West Palm Beach, Florida
Charles B. Williams, Template Software, Inc., Dulles, Virginia

Published July, 1997 by Prentice Hall PTR (ECS Professional)

Copyright 1997, 465 pp.
Cloth
ISBN 0-13-727405-X
$55.00


Sign up for future
mailings on this subject.

See other books about:
    UML

 [Preface]





The first complete roadmap for building and customizing Object-Oriented software development processes. With this book you can create a well-defined management and technical project infra-structure based on your existing methodology. Extending the highly effective Use Case model, OO experts Putnam Texel and Charles Williams address every step of the system/software development lifecycle, including:

  • Requirements engineering and trace.
  • Systems architecture.
  • Software OOA and OOD.
  • Language independent and language dependent OO design.
  • Implementation, testing, and maintenance.
They show how an incremental, iterative approach to identifying, analyzing, designing, implementing and testing Use Cases can help you build a project infra-structure your entire team will have confidence in. Additionally they answer three very important questions: “Where are we going?”, “What do I do next?”, and “When am I done?”.

Texel and Williams unfold the process within the context of a case study designed to present virtually all major software development issues. Their techniques are specifically designed to help you build repeatable, measurable processes which meet the requirements of the SEI CMM. Better yet, these techniques leverage the OO methods you may already be using, and are fully consistent with UML Version 1.0. Whether you're a project manager or a software engineer, with this book you have the tools to lead your organization away from ad hoc software development processes and improve the quality of the developed code and the productivity of the staff.

Author Bio

PUTNAM P. TEXEL founded Texel & Company in 1984 after being affiliated with Control Data, Teledyne Brown Engineering, and SofTech. Since 1984 she has provided advanced Object-Oriented training and consulting services to both commercial and defense industry clients, including NASA, NATO, Harris, GTE, Motorola, the U.S. Air Force, and the U.S. Army.

CHARLES B. WILLIAMS has spent 12 years in the software industry working on Object-Oriented systems. At Template Software, Inc. he is a Senior Consultant responsible for the development of OO prototype systems. At Virtual Software Factory, Inc. he was responsible for building customized OO CASE tools; prior to that, he managed an internal R&D project to develop Computer Sciences Corporation's next-generation Object-Oriented methodology.



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.

[Help] [Home]

© Prentice-Hall, Inc. A Pearson Education Company
Comments To webmaster@prenhall.com