Read more
1.1 Introduction This book introduces and guides the you through the use of the Unified Modeling Language (UML) and the Unified Process (both originally devised by Grady Booch,James Rumbaugh and Ivar Jacobson) and their application to Java systems.This means that the book will present you, thereader,withthenotationusedintheUMLandthestepsdescribedbytheUnifiedProcesswith particular reference to the Java environment (including the classes and the syntax). The book itself is structured in three parts. Part 1 introduces object-oriented analysis and design and the Unified Process. The UML is introduced, as necessary, to support the Unified Process steps.Part 2 discusses the topic of design patterns,while Part 3 looks at the UnifiedProcessandUMLintherealworld. The first part of the book is structured in the following manner: Chapter 2: Object -Oriented Analysis and Design This chapter surveys the most significant object-oriented design and analysis methods to emerge since the late 1980s. Chapter 3: An Introduction to the UML and the Unified Process This chapter provides the background to the UML and the Unified Process. It also presents a summary of both. Chapter 4: Software Architecture and Object-Oriented Design This chapter explains and justifies why an architecture is essential to the successful design and implementation of a large object-oriented system. Chapter 5: Requirements Discipline: Use Case Analysis Thischapterintroducestherequirementsdiscipline(whichmayalsobeknownasUseCaseAna- sis).Thisdisciplineattemptstoidentifywhatthefunctionalityofthesystemwillbe.Theseusecases will be essential as the backbone to the whole design process.
List of contents
The Unified Process.- Object-Oriented Analysis and Design.- An Introduction to the UML and the Unified Process.- Software Architecture and Object-Oriented Design.- Requirements Discipline: Use Case Analysis.- The Analysis Discipline: Finding the Entities.- The Design Discipline: System and Class Design.- Implementation Phase.- The Test Discipline: How It Relates to Use Cases.- The Four Phases.- The JDSync Case Study.- Design Patterns.- Software Patterns.- Patterns Catalogs.- Applying the Model-View-Controller Pattern.- The Hierarchical MVC.- The Visitor Framework.- The EventManager.- J2EE Patterns.- The Fault Tracker J2EE Case Study.- The Unified Process in the Real World.- Are UML Designs Language-Independent?.- Customizing the Unified Process for Short Time-Scale Projects.- Augmenting the Unified Process with Additional Techniques.- Inheritance Considered Harmful!.- Incremental Software.- Agile Modeling.
Summary
1.1 Introduction This book introduces and guides the you through the use of the Unified Modeling Language (UML) and the Unified Process (both originally devised by Grady Booch,James Rumbaugh and Ivar Jacobson) and their application to Java systems.This means that the book will present you, thereader,withthenotationusedintheUMLandthestepsdescribedbytheUnifiedProcesswith particular reference to the Java environment (including the classes and the syntax). The book itself is structured in three parts. Part 1 introduces object-oriented analysis and design and the Unified Process. The UML is introduced, as necessary, to support the Unified Process steps.Part 2 discusses the topic of design patterns,while Part 3 looks at the UnifiedProcessandUMLintherealworld. The first part of the book is structured in the following manner: Chapter 2: Object -Oriented Analysis and Design This chapter surveys the most significant object-oriented design and analysis methods to emerge since the late 1980s. Chapter 3: An Introduction to the UML and the Unified Process This chapter provides the background to the UML and the Unified Process. It also presents a summary of both. Chapter 4: Software Architecture and Object-Oriented Design This chapter explains and justifies why an architecture is essential to the successful design and implementation of a large object-oriented system. Chapter 5: Requirements Discipline: Use Case Analysis Thischapterintroducestherequirementsdiscipline(whichmayalsobeknownasUseCaseAna- sis).Thisdisciplineattemptstoidentifywhatthefunctionalityofthesystemwillbe.Theseusecases will be essential as the backbone to the whole design process.
