SUMMARY Object-oriented analysis methods enable a software engineer to model a problem by
21.7 SUMMARY Object-oriented analysis methods enable a software engineer to model a problem by
representing both static and dynamic characteristics of classes and their relation- ships as the primary modeling components. Like earlier OO analysis methods, the Unified Modeling Language builds an analysis model that has the following charac- teristics: (1) representation of classes and class hierarchies, (2) creation of object- relationship models, and (3) derivation of object-behavior models.
Analysis for object-oriented systems occurs at many different levels of abstrac- tion. At the business or enterprise level, the techniques associated with OOA can be coupled with a business process engineering approach. This technique is often called domain analysis. At an application level, the object model focuses on specific cus- tomer requirements as those requirements affect the application to be built.
The OOA process begins with the definition of use-cases—scenarios that describe how the OO system is to be used. The class-responsibility-collaborator modeling tech- nique is then applied to document classes and their attributes and operations. It also provides an initial view of the collaborations that occur among objects. The next step in the OOA process is classification of objects and the creation of a class hierarchy. Subsystems (packages) can be used to encapsulate related objects. The object- relationship model provides an indication of how classes are connected to one another, and the object-behavior model indicates the behavior of individual objects and the overall behavior of the OO system.
CHAPTER 21 O B J E C T - O R I E N T E D A N A LY S I S
REFERENCES [ALH98] Alhir, S.S., UML in a Nutshell, O’Reilly & Associates, 1998.
[AMB95] Ambler, S., “Using Use-Cases,” Software Development, July 1995, pp. 53–61. [ARA89] Arango, G. and R. Prieto-Diaz, “Domain Analysis: Concepts and Research Directions,” Domain Analysis: Acquisition of Reusable Information for Software Con- struction, (Arango, G. and R. Prieto-Diaz, eds.), IEEE Computer Society Press, 1989. [BEN99] Bennett, S., S. McRobb, and R. Farmer, Object Oriented System Analysis and Design Using UML, McGraw-Hill, 1999. [BER93] Berard, E.V., Essays on Object-Oriented Software Engineering, Addison- Wesley, 1993. [BOO94] Booch, G., Object-Oriented Analysis and Design, 2nd ed., Benjamin Cum- mings, 1994. [BOO99] Booch, G., I. Jacobson, J. Rumbaugh, The Unified Modeling Language User Guide, Addison-Wesley, 1999. [CAR98] Carmichael, A., Developing Business Objects, SIGS Books, 1998). [CHA93] De Champeaux, D., D. Lea, and P. Faure, Object-Oriented System Develop- ment, Addison-Wesley, 1993. [COA91] Coad, P. and E. Yourdon, Object-Oriented Analysis, 2nd ed., Prentice-Hall, 1991. [EEL98] Eeles, P. and O. Sims, Building Business Objects, Wiley, 1998. [ERI98] Eriksson, H.E. and M. Penker, UML Toolkit, Wiley, 1998. [FIC92] Fichman, R.G. and C.F. Kemerer, “Object-Oriented and Conventional Analy- sis and Design Methodologies,” Computer, vol. 25, no. 10, October 1992, pp. 22–39. [FIN96] Fingar, P., The Blueprint for Business Objects, Cambridge University Press, 1996. [FIR93] Firesmith, D.G., Object-Oriented Requirements Analysis and Logical Design, Wiley, 1993. [GRA94] Graham, I., Object-Oriented Methods, Addison-Wesley, 1994. [JAC92] Jacobson, I., Object-Oriented Software Engineering, Addison-Wesley, 1992. [JAC99] Jacobson, I., G. Booch, J. Rumbaugh, Unified Software Development Process, Addison-Wesley, 1999. [MAT94] Mattison, R., The Object-Oriented Enterprise, McGraw-Hill, 1994. [MON92] Monarchi, D.E. and G.I. Puhr, “A Research Typology for Object-Oriented Analysis and Design,” CACM, vol. 35, no. 9, September 1992, pp. 35–47. [RUM91] Rumbaugh, J., et al., Object-Oriented Modeling and Design, Prentice-Hall, 1991. [RUM99] Rumbaugh, J., I. Jacobson, and G. Booch, The Unified Modeling Language Reference Manual, Addison-Wesley, 1999. [SUL94] Sullo, G.C., Object Engineering, Wiley, 1994. [TAY95] Taylor, D.A., Business Engineering with Object Technology, Wiley, 1995. [WIR90] Wirfs-Brock, R., B. Wilkerson, and L. Weiner, Designing Object-Oriented Soft-
599
Parts
» The Concurrent Development Model
» SUMMARY Software engineering is a discipline that integrates process, methods, and tools for
» PEOPLE In a study published by the IEEE [CUR88], the engineering vice presidents of three
» THE PROCESS The generic phases that characterize the software process—definition, development,
» THE PROJECT In order to manage a successful software project, we must understand what can go
» METRICS IN THE PROCESS AND PROJECT DOMAINS
» Extended Function Point Metrics
» METRICS FOR SOFTWARE QUALITY
» INTEGRATING METRICS WITHIN THE SOFTWARE PROCESS
» METRICS FOR SMALL ORGANIZATIONS
» ESTABLISHING A SOFTWARE METRICS PROGRAM
» Obtaining Information Necessary for Scope
» An Example of LOC-Based Estimation
» QUALITY CONCEPTS 1 It has been said that no two snowflakes are alike. Certainly when we watch snow
» SUMMARY Software quality assurance is an umbrella activity that is applied at each step in the
» R diagram 1.4 <part-of> data model; data model <part-of> design specification;
» SYSTEM MODELING Every computer-based system can be modeled as an information transform using an
» Facilitated Application Specification Techniques
» Data Objects, Attributes, and Relationships
» Entity/Relationship Diagrams
» Hatley and Pirbhai Extensions
» Creating an Entity/Relationship Diagram
» SUMMARY Design is the technical kernel of software engineering. During design, progressive
» Data Modeling, Data Structures, Databases, and the Data Warehouse
» Data Design at the Component Level
» A Brief Taxonomy of Styles and Patterns
» Quantitative Guidance for Architectural Design
» Isolate the transform center by specifying incoming and outgoing
» SUMMARY Software architecture provides a holistic view of the system to be built. It depicts the
» The User Interface Design Process
» Defining Interface Objects and Actions
» D E S I G N E VA L U AT I O N
» Testing for Real-Time Systems
» Organizing for Software Testing
» Criteria for Completion of Testing
» The Transition to a Quantitative View
» The Attributes of Effective Software Metrics
» Architectural Design Metrics
» Component-Level Design Metrics
» SUMMARY Software metrics provide a quantitative way to assess the quality of internal product
» Encapsulation, Inheritance, and Polymorphism
» Identifying Classes and Objects
» The Common Process Framework for OO
» OO Project Metrics and Estimation
» Event Identification with Use-Cases
» SUMMARY Object-oriented analysis methods enable a software engineer to model a problem by
» Partitioning the Analysis Model
» Designing Algorithms and Data Structures
» Program Components and Interfaces
» SUMMARY Object-oriented design translates the OOA model of the real world into an
» Testing Surface Structure and Deep Structure
» Deficiencies of Less Formal Approaches 1
» What Makes Cleanroom Different?
» Design Refinement and Verification
» SUMMARY Cleanroom software engineering is a formal approach to software development that
» Structural Modeling and Structure Points
» Describing Reusable Components
» SUMMARY Component-based software engineering offers inherent benefits in software quality,
» Guidelines for Distributing Application Subsystems
» Middleware and Object Request Broker Architectures
» An Overview of a Design Approach
» Consider expert Web developer will create a complete design, but time and cost can be appropriate
» A Software Reengineering Process Model
» Reverse Engineering to Understand Data
» Forward Engineering for Client/Server Architectures
» SUMMARY Reengineering occurs at two different levels of abstraction. At the business level,
Show more