Software architecture - global-121/121-platform GitHub Wiki

This software architecture section focuses on a selected range of topics. It only focuses on components/scenarios/topics/etc. that are most relevant, which makes the value of maintaining it outweigh the costs.

The intended audience is at the moment mostly the 121 Development Team itself, to enable the development process. But the content is definitely relevant to any party with a technical or conceptual interest in the 121-platform.

Understanding of UML diagrams and terminology is assumed.

Guidelines Software Architecture

Guidelines we follow while working on the 121 service.

Requirements

A categorized list of system requirements for the 121 Platform, both non-functional and high-level functional. More detailed functional requirements are modeled into diagrams. See below.

Behavioral diagrams

Diagrams that model the behavior of the 121 Platform.

1. Actors: a UML Use Case Diagram documenting the Actors for the system.
2. Business Processes: a non-UML diagram giving a categorized overview of all business processes in scope for the system
3. Elementary Business Processes: a UML Use Case Diagram for each Elementary Business Process that is relevant and valuable to document in more detail than only having it in the Business Processes diagram
4. Use cases: a UML Activity Diagram for each Use Case from the Elementary Business Process Use Case Diagrams that is relevant and valuable to document in more detail
5. Person Affected Status: a UML State Machine Diagram documenting the statuses of a Person Affected

121 Service

A page with various diagrams of the 121 Service, which is the server-side "back-end" of the system.