This book covers all you need to know to model and design software applications from use cases to software architectures in UML and shows how to apply the COMET UML-based modeling and design method to real-world problems. The author describes architectural patterns for various architectures, such as broker, discovery, and transaction patterns for service-oriented architectures, and addresses software quality attributes including maintainability, modifiability, testability, traceability, scalability, reusability, performance, availability, and security. Complete case studies illustrate design issues for different software architectures: a banking system for client/server architecture, an online shopping system for service-oriented architecture, an emergency monitoring system for component-based software architecture, and an automated guided vehicle for real-time software architecture. Organized as an introduction followed by several short, self-contained chapters, the book is perfect for senior undergraduate or graduate courses in software engineering and design, and for experienced software engineers wanting a quick reference at each stage of the analysis, design, and development of large-scale software systems.Example of user interaction subsystem 13.3.3 Clients and Services Clients and services should be in separate subsystems. ... in Figure 13.4, there are two services, Alarm Service and Monitoring Data Service, which are in separate subsystems from their clients. ... deals with a subset of the actors shown in the use case model and a subset of the external real-world objects shown on the context diagram.
|Title||:||Software Modeling and Design|
|Publisher||:||Cambridge University Press - 2011-02-21|