TODO: Answer the questions below to help you define your system
architecture. Consider how the reusable sample text relates to your
project or prompts you to think of new ideas. Add, edit or delete
text as needed.
Architectural Scenarios
TODO: Provide architecture scenarios that show how objects will
communicate across components, processes, and machines. Focus on
scenarios where the architecture itself is changing, e.g., system
startup, shutdown, adding or upgrading components, load balancing,
or fail-over.
The following sequence diagrams give step-by-step descriptions of
how components communicate during some important usage
scenarios:
The following steps describe how components communicate during
some important usage scenarios:
- System startup
- COMPONENT-NAME initializes first
- COMPONENT-NAME-2 must check the DATA-STRUCTURE on start-up
- COMPONENT-NAME-3 starts only when needed on the first
request
- Process IDs are written to the DIRECTORY-NAME/pid file
- System shutdown
- COMPONENT-NAME drives the shutdown process
- COMPONENT-NAME-2 must flush DATA-STRUCTURE before shutdown
- COMPONENT-NAME-3 sends a message to COMPONENT-NAME-4 then
waits for it to shut down first
- The shutdown script deletes all temporary and pid files
- SCENARIO-NAME