The software modeling and design method described in this book is called COMET (Collaborative Object Modeling and Architectural Design Method), which uses the UML notation. COMET is an iterative use case–driven and object-oriented method that specifically addresses the requirements, analysis, and design modeling phases of the software development life cycle. This chapter considers the COMET method from a software life cycle perspective.
The development process for the COMET method is a use case–based software process, which is compatible with the Unified Software Development Process (USDP) (Jacobson, Booch, and Rumbaugh 1999) and the spiral model (Boehm 1988). This chapter presents the COMET use case– based software life cycle and describes how the COMET method may be used with the USDP or the spiral model. It then outlines the main activities of the COMET method and concludes with a description of the steps in using COMET.
Section 5.1 describes the COMET use case–based software life cycle, and Section 5.2 compares COMET with other software processes. Section 5.3 gives an overview of the requirements, analysis, and design modeling activities in COMET. Section 5.4 gives an overview of the design of different kinds of software architectures covered in this textbook. 5.1 COMET USE CASE–BASED SOF TWARE LIFE CYCLE The COMET use case–based software life cycle model is a highly iterative software development process based around the use case concept.
In the requirements model, the functional requirements of the system are described in terms of actors and use cases. Each use case defines a sequence of interactions between one or more actors and the system. In the analysis model, the use case is realized to describe the objects that participate in the use case and their interactions.
In the design model, the software architecture is developed, describing components and their interfaces. The full COMET use case–based software life cycle model is illustrated in Figure 5.1 and described next. The COMET life cycle is highly iterative. The COMET method ties in the three phases of requirements, analysis, and design modeling by means of a use case–based approach, as outlined next.