Ch 02 Flashcards
EO 2.1:
system context?
system boundary?
context boundary?
System Context:
- People (stakeholder or groups of stakeholders)
- Systems in operation (technical systems, software and hardware)
- Processes (technical or physical processes, business processes)
- Events (technical or physical)
- Documents (e.g. laws, standards, system documentation)
System Boundary:
It is the function of the system boundary to define which aspects will be covered by the planned system and which aspects are part of this system’s environment.
Context Boundary:
The context boundary identifies the part of the environment that has a connection to the system to be developed.
EU 2.2 Determining System and Context Boundaries
Often the system boundary is only precisely defined towards the end of the requirements process. Before that, the desired functions and qualities of the planned system are only incompletely known or not known at all. Therefore there will be a grey zone in which the possible system boundary lies. Besides a shifting of the system boundary within the grey zone, the grey zone itself can also shift during the RE process, e.g. when, through a shifting of the system boundary, further aspects of the environment become important.
Also the context boundary can change over time, e.g. when it turns out, contrary to expectations, that a legal requirement, previously classified as relevant, has absolutely no impact on the planned system, then the system context is reduced in this area.
The context boundary also has a grey zone. It comprises the identified aspects of the environment for which, at a particular time, it is unclear whether these aspects have a relation to the planned system or not.
Use case diagrams or data flow diagrams are often used for the documentation of the system contexts
