1 / 19

BDSA – Deployment and Documentation

BDSA – Deployment and Documentation. Jakob E. Bardram. Today. UML Deployment & Component Diagrams [OOAD] ch. 38 Architecture Documentation [OOAD] ch. 39 UML N+1 (4+1) View Model The Project!. UML Deployment and Component Diagrams. UML Deployment Diagram. UML Deployment Diagram

sasha
Download Presentation

BDSA – Deployment and Documentation

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. BDSA – Deployment and Documentation Jakob E. Bardram

  2. Today • UML Deployment & Component Diagrams • [OOAD] ch. 38 • Architecture Documentation • [OOAD] ch. 39 • UML • N+1 (4+1) View Model • The Project!

  3. UML Deployment and Component Diagrams

  4. UML Deployment Diagram • UML Deployment Diagram • shows the assignment of software • to computational nodes • i.e. the deployment of software elements • to the physical architecture • Physical Node • device – i.e. physical computing resource • PC, PDA, phone, server, ... • execution environment node (EEN) – a software computing resource • OS, VM, DB, Web browser, EJB container, ...

  5. UML Deployment Diagram

  6. UML Component Diagram • Component • A component represents a modular part of a system that encapsulates its contents an whose manifestation is replaceable within its environment. • A component defines its behavior in terms of provided and required interfaces. • UML Components are design level perspectives • they do not exist in the concrete software perspective • but may map to a set of files (in e.g. a package)

  7. UML Component Diagram

  8. Documenting ArchitectureThe N+1 View Model

  9. Software Architecture Document • The SAD • the overall picture & idea of the system architecture • architectural decisions (using technical memos) • N+1 architectural views • Architectural View • a view of the system architecture from a given perspective • focus on • structure, modularity, essential components, main control flow • a window on the system from a particular perspective – emphasize something, ignores the rest

  10. Logical View – static • Class & Package diagrams

  11. Logical View – dynamic Sequence Diagrams

  12. The 4+1 View Model • Kruchten, P. The 4+1 View Model of Architecture. IEEE Software 12(6), 1995. • 4 Views • Logical – conceptual organization • Process – execution and threads • Physical – software deployment on physical nodes • Data – data flow, persistence schema, O-R mapping • +1 View • Use cases – summary of most important use cases • + non-functional requirements • NB! Remember the motivation = the text! • explain WHY the architecture is the way it is...

  13. The 4+1 View Model

  14. Logical View

  15. Deployment View

  16. Data View

  17. Use Case View

  18. Software Architecture Document • Architectural Representation • Architectural Factors • Architectural Decisions • 4 Views • Logical View • Deployment View • Process View • Data View • +1 View • Use-Case View • Other Views • Security, Implementation, Development, ...

  19. That’s all Folks!

More Related