This is the architectural model for the system. This is similar to the way the system is partitioned into subdomains (domain categories). The advantage of creating a system architecture is that many requirements can be associated with specific subsystems. Furthermore, in some cases the system architecture may be a requirement itself. Examples of system architecture are layers, client-server, blackboard, repository and pipeline.
The overall hardware and software configuration and database design supporting a particular HSE-MIS application.
a framework that describes how system components interact and work together to achieve the system's goals
The documented, significant design decisions which, taken together, describe the structure and behaviour of a proposed or implemented system. The elements which are documented include the components which make up the system and the interfaces between these components, system usage, functionality, performance, resilience, and constraints and trade-offs.
A means for describing the elements and interactions of a complete system including its hardware elements and its software elements.
The composite of the design architectures for products and their life cycle processes. (IEEE 1220-1998)
A representation of a system in which there is a mapping of functionality onto hardware and software components, a mapping of the software architecture onto the hardware architecture, and human interaction with these components.
the configuration of components, consoles, peripherals and connections that make up a total system.
a description of the design and contents of a computer system. If documented, it may include information such as a detailed inventory of current hardware, software and networking capabilities; a description of long-range plans and priorities for future purchases, and a plan for upgrading and/or replacing dated equipment and software.
Systems and their building blocks. Includes System, Subsystem, System Component, and Security Data.