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.
- Portal Development Guidelines Guidelines we follow while working on the 121 portal.
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.
Diagrams that model the behavior of the 121 Platform.
- Actors: a UML Use Case Diagram documenting the Actors for the system.
- Use cases: a UML Activity Diagram for each Use Case that is relevant and valuable to document in more detail
- Registration Status: a UML State Machine Diagram documenting the statuses of a Registration
121 Service A page with various diagrams of the 121 Service, which is the server-side "back-end" of the system.
Integrations with external systems A diagram that shows integrations with external systems