forked from Arquisoft/wiq_0
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Añadido final 03_system_scope_and_context.adoc
- Loading branch information
Showing
1 changed file
with
4 additions
and
66 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,75 +1,13 @@ | ||
| ifndef::imagesdir[:imagesdir: ../images] | ||
|
|
||
| [[section-system-scope-and-context]] | ||
| == System Scope and Context | ||
|
|
||
|
|
||
| [role="arc42help"] | ||
| **** | ||
| .Contents | ||
| 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). | ||
| .Motivation | ||
| The domain interfaces and technical interfaces to communication partners are among your system's most critical aspects. Make sure that you completely understand them. | ||
| .Form | ||
| Various options: | ||
| * Context diagrams | ||
| * Lists of communication partners and their interfaces. | ||
| .Further Information | ||
| See https://docs.arc42.org/section-3/[Context and Scope] in the arc42 documentation. | ||
| **** | ||
|
|
||
|
|
||
| === Business Context | ||
|
|
||
| [role="arc42help"] | ||
| **** | ||
| .Contents | ||
| 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. | ||
| :imagesdir: ../images | ||
| image::business.png[] | ||
|
|
||
| .Motivation | ||
| All stakeholders should understand which data are exchanged with the environment of the system. | ||
| .Form | ||
| 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. | ||
| **** | ||
|
|
||
| **<Diagram or Table>** | ||
|
|
||
| **<optionally: Explanation of external domain interfaces>** | ||
|
|
||
| === Technical Context | ||
|
|
||
| [role="arc42help"] | ||
| **** | ||
| .Contents | ||
| 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. | ||
| .Motivation | ||
| 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. | ||
| .Form | ||
| E.g. UML deployment diagram describing channels to neighboring systems, | ||
| together with a mapping table showing the relationships between channels and input/output. | ||
| **** | ||
|
|
||
| **<Diagram or Table>** | ||
|
|
||
| **<optionally: Explanation of technical interfaces>** | ||
|
|
||
| **<Mapping Input/Output to Channels>** | ||
| :imagesdir: ../images | ||
| image::technical.png[] |