Specification of Reactive Hardware/Software Systems - Electronic ...

5.7 Views 129
Management
£
£
£
Purchasing
Customer Service
Marketing
Legal Department
Information Systems
Accounting
Specification
model
International Sales
Sales
Manufacturing
Figure 5.5: Concurrent Specification
Quality Assurance
Packaging
Distribution
XYZ
CORPORATION
£
Finance
directly to additional behaviour in a system. For example, maintenance or test may
require a function that puts a system in a different working mode. Input from dedicated
experts will be necessary to add appropriate requirements.
Specific behaviour is not necessarily related to all other aspects of the behaviour of a
system. Therefore we use specific views on the system model. We propose to use
graphical notations for the communication with experts, users, designers, etcetera. The
most important ones are Object Instance Diagrams. A specific view, for example a test
view, can show all collaborating objects that play a role in various test scenarios. In
Section 6.5, we will introduce scenarios as views that focus the attention on specific part
of the system behaviour. These scenarios can be used to focus on specific discipline
views. For complex systems such views may be necessary for various different levels of
abstraction.
Although we emphasise the role of views for behaviour, their role for structuring the
system may be as strong. Simultaneous modelling of both behaviour and structure
views must finally lead to a consistent extension of a Unified Model.