Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chapter 3: Models for Software Architecture - Coggle Diagram
Chapter 3:
Models for Software
Architecture
3.2 UML for Software Architecture
Structural (Static) Diagrams
Class
An overview of classes for modeling and design. It shows how classes are statically related, but not how classes dynamically interact with each other
Object
Objects and their relationship at runtime. An overview of particular instances of a class diagram at a point of time for a specific case. It is based on the class diagram.
Composite
structure
Describes the inner structure of a component including all
classes within the component, interface of the omponent,
Component
Describes all components in a system, their interrelationships, interactions,and the interface of the system. lt is an outline of the composition structure of components or modules.
Package
Describes the package structure and organization. It covers
classes in the package and packages within another package
Deployment
Describes system hardware, software, and network connections for distributed computing. It covers server configuration and network connections between server nodes in real-world setting.
Behavioral (Dynamic) Diagrams
Use case
Derived from use-case study scenarios. It is an overview of use cases, actors, and their communication relationships to demonstrate how the system reacts to requests from external users. It is used to capture system requirements.
Activity
Outline of activity's data and control flow among related objects.
State machine
Describes the life cycle of objects using a finite state machine
Sequence
Describes time sequence of messages passed among objects in a timeline.
Interaction
overview
Combines activity and sequence diagrams to provide control flow
overview of the system and business process
Communication
Describes the sequence of message passing among objects in the system
Time sequence
Describes the changes by messages in state, condition, and events.
3.3 Architecture View Models
The Scenario View
The scenario view describes the functionality of the system, i.e., how the
user employs the system and how the system provides services to the users.
The Logical or Conceptual View
The logical view is based on application domain entities necessary to
implement the functional requirements.
The Development or Module View
The development view derives from the logical view and describes the
static organization of the system modules
The Process View
The process view focuses on the dynamic aspects of the system, i.e., its
execution time behavior.
The Physical View
The physical view describes installation, configuration, and deployment of
the software application
The User Interface View
The User Interface (UI) view is an extended view that provides a clear usercomputer interface view and hides implementation details.