SOFTWARE DESIGN BOOK GOOD FOR REFERENCE, Essays (university) of Computer Science

Download SOFTWARE DESIGN BOOK GOOD FOR REFERENCE and more Essays (university) Computer Science in PDF only on Docsity!

This page intentionally left blank

SOFTWARE MODELING

AND DESIGN

UML, Use Cases, Patterns, and

Software Architectures

Hassan Gomaa

George Mason University, Fairfax, Virginia

To Gill, William and Neela, Alex,

Amanda and Neil, and Edward

viii Contents

Preface

OVERVIEW

This book describes a use case–driven UML-based method for the modeling and design of software architectures, including object-oriented software architectures, client/server software architectures, service-oriented architectures, component- based software architectures, concurrent and real-time software architectures, and software product line architectures. The book provides a unified approach to design- ing software architectures and describes the special considerations for each cate- gory of software architecture. In addition, there are four case studies, a client/server banking system, a service-oriented architecture for an online shopping system, a distributed component-based emergency monitoring system, and a real-time auto- mated guided vehicle system. This book describes a UML-based software modeling and design method called COMET (Collaborative Object Modeling and Architectural Design Method). COMET is a highly iterative object-oriented software development method that addresses the requirements, analysis, and design modeling phases of the object- oriented development life cycle. The book is intended to appeal to readers who wish to design software architec- tures using a systematic UML-based method that starts from requirements modeling with use cases, through static and dynamic modeling, to software design based on architectural design patterns.

WHAT THIS BOOK PROVIDES

Various textbooks on the market describe object-oriented analysis and design con- cepts and methods. This book addresses the specific needs of designing software architectures. It addresses UML-based design of software architectures, starting with use cases for requirements modeling, static modeling with class diagrams, and dynamic modeling with object interaction analysis and state machine model- ing, through software design with architectural design patterns. All examples are

xv

Preface xvii

WAYS TO READ THIS BOOK

This book may be read in various ways. It can be read in the order in which it is pre- sented, in which case Chapters 1 through 4 provide introductory concepts; Chapter 5 provides an overview of the COMET/UML software modeling and design method; Chapters 6 through 20 provide an in-depth treatment of software modeling and design; and Chapters 21 through 24 provide detailed case studies. Alternatively, some readers may wish to skip some chapters, depending on their level of familiarity with the topics discussed. Chapters 1 through 4 are introductory and may be skipped by experienced readers. Readers familiar with software design concepts may skip Chapter 4. Readers particularly interested in software modeling and design can proceed directly to the description of COMET/UML, starting in Chapter 5. Readers who are not familiar with UML, or who are interested in finding out about the changes introduced by UML 2, can read Chapter 2 in conjunction with Chapters 5 through 20. Experienced software designers may also use this book as a reference, referring to various chapters as their projects reach a particular stage of the requirements, analysis, or design process. Each chapter is relatively self-contained. For example, at different times one might refer to Chapter 6 for a description of use cases, to Chapter 7 for a discussion of static modeling, and to Chapter 9 for a description of dynamic interaction modeling. Chapter 10 can be referenced for designing state machines; Chapter 12 and Appendix A for software architectural patterns; Chapter 14 for object-oriented software architectures; and Chapter 15 for designing a relational database from a static model. Chapter 16 can be consulted for service-oriented architectures; Chapter 17 for distributed component-based software design; Chap- ter 18 for real-time design; and Chapter 19 for software product line design. One can also improve one’s understanding of how to use the COMET/UML method by reading the case studies, because each case study explains the decisions made at each step of the requirements, analysis, and design modeling processes in the design of a real-world application.

Hassan Gomaa George Mason University December 2010 Email: [email protected] Web: http://mason.gmu.edu/∼hgomaa