1 / 13

Requirements Models to Architectural Design Models: A Simple Library Example

Learn about architectural design concepts and subsystem interactions using a simple library example. Understand architecture types, component architectures, transitioning to architectural design, and modeling with use cases and classes. Explore how subsystems interact to accomplish tasks like checking out copies in a library system.

donaldgreen
Download Presentation

Requirements Models to Architectural Design Models: A Simple Library Example

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirements Models to Architectural Design Models: A Simple Library Example Robert France Colorado State University

  2. What is architectural design? • Concerned with identifying subsystems and their relationships • Architectural design is an example of programming-in-the-large • Basic element of construction is a subsystem or layer or system component (unlike programming-in-the-small where the basic unit of construction is a statement in a programming language) • Subsystems are systematically refined to show more details in detailed design.

  3. Architecture Types • Logical Architecture • Organization of a system into logical units (e.g., layers, subsystems) • Logical units do not necessarily result in units of implementation (e.g., Java packages, components) • Implementation (Deployment) Architecture • Organization of a system into physical units (e.g., source files, Java packages, components)

  4. Layered Architectures • Separate presentation and application logic, and other areas of concern. UI Layer “Domain” or “Application Logic” Layer Services Layer Persistence Subsystem Logging Subsystem . . .

  5. Component Architectures • An architectural component is an architectural unit provides a well defined set of services. • An architecture is constructed by composing components. • A component has two types of interfaces • Provided interface: describes the services provided by a component • Required interface: describes the services that the component requires to provide its services

  6. Transitioning to Architectural Design Describe how subsystems interact to accomplish use cases Requirements use case Architectural sequence models Identify subsystems by grouping use cases Architectural static model Identify subsystems by grouping classes Requirements class model

  7. Simple Library Example • Library consists of reference and general copies • Only general copies can be chacked out; reference copies cannot be checked out • A borrower cannot check out a copy if they have outstanding fines. • A borrower is charged $1 for each week after its due date that it is not returned.

  8. Library Example: required services CheckOutCopy ReturnCopy AddCopy DeleteCopy AddBorrower DeleteBorrower FindCopy

  9. CheckOutCopy UseCase (draft form) UseCase: CheckOutCopy Main flow • Clerk enters borrower and copy identifiers • If borrower is registered, does not have fines, and copy is a general copy then system indicates that checkout is successful; else system indicates that checkout is not successful

  10. Requirements Class Model

  11. Architectural Static Model Use cases grouped into borrower services and administrative services; two subsystems for each of these groupings is created – one responsible for borrower services, the other for administrative services Both administrative and borrower services need copy and borrower information. This observation results in a decision to include two subsystems for managing copies and borrowers.

  12. CheckOut Sequence Model

  13. ReturnCopy Sequence Model

More Related