-
-
Notifications
You must be signed in to change notification settings - Fork 1
Context
System scope and context - as the name suggests - delimits your system (i.e. your scope) from all its communication partners (neighboring systems and users, i.e. the context of your system). It thereby specifies the external interfaces.
If necessary, differentiate the business context (domain specific inputs and outputs) from the technical context (channels, protocols, hardware).
The domain interfaces and technical interfaces to communication partners are among your system's most critical aspects. Make sure that you completely understand them.
Various options:
- Context diagrams
- Lists of communication partners and their interfaces.
Specification of all communication partners (users, IT-systems, ...) with explanations of domain specific inputs and outputs or interfaces. Optionally you can add domain specific formats or communication protocols.
All stakeholders should understand which data are exchanged with the environment of the system.
All kinds of diagrams that show the system as a black box and specify the domain interfaces to communication partners.
Alternatively (or additionally) you can use a table. The title of the table is the name of your system, the three columns contain the name of the communication partner, the inputs, and the outputs.
Add explanation of external domain interfaces.
ADD IMAGE OF BUSINESS CONTEXT HERE
Item | Explanation |
---|---|
Dispatcher (User) | ... |
External Data Provider (Third-party system) | ... |
Technical interfaces (channels and transmission media) linking your system to its environment. In addition a mapping of domain specific input/output to the channels, i.e. an explanation which I/O uses which channel.
Many stakeholders make architectural decision based on the technical interfaces between the system and its context. Especially infrastructure or hardware designers decide these technical interfaces.
E.g. UML deployment diagram describing channels to neighboring systems, together with a mapping table showing the relationships between channels and input/output.
Add explanation of technical interfaces.
ADD IMAGE OF TECHNICAL CONTEXT HERE
Item | Explanation |
---|---|
Browser | Gives access to the front-end part of the application using HTTP protocol and renders the GUI |
External Data Provider (Third-party system) | Public REST-APIs used to fetch external data |
README | Contributing | Code of Conduct | Support | Funding | Security | License |
- Home of the Wiki
- Roadmap
- API Reference
- Glossary
- Contributor Guide
- Code of Conduct
- Support
- Funding
- Security
- License
- Description of Core Essence
- Cost Estimates
- Staffing Estimates
- Predicted Benefits
- Risks
- Scheduled Milestones
- Definition of Ready
- Definition of Done
- Project Decisions
- Technological Decisions
- Sprint Reviews
- Sprint Retrospectives
- Continuous Integration
- Continuous Deployment
- Operations Troubleshooting
- External Systems
- Style Guide
- Specific Views
- View 1
- ...
- About
- Introduction and Goals
- Constraints
- Context
- Solution Strategy
- Building Block View
- Runtime View
- Deployment View
- Cross Cutting Concepts
- Design Decisions
- ADRXX Template
- ...
- Quality Requirements
- Risks and Technical Debt
- Glossary
- Reference Manuals
- Support Guides
- Release Notes