Difference between revisions of "System Architecture"
Tag: visualeditor |
Afaisandier (talk | contribs) Tag: visualeditor |
||
| Line 1: | Line 1: | ||
| + | The purpose of system architecture activities is to define a comprehensive solution based on principles, concepts, and properties logically related and consistent with each other. The solution architecture has features, properties, and characteristics satisfying, as far as possible, the problem or opportunity expressed by a set of system requirements (traceable to mission/business and stakeholder requirements) and life cycle concepts (e.g., operational, support) and are implementable through technologies (e.g., mechanics, electronics, hydraulics, software, services, procedures). | ||
| + | |||
| + | System Architecture is abstract, conceptualization-oriented, global, and focused to achieve the mission and operational concepts of the system. It also focuses on high‐level structure in systems and system elements. It addresses the architectural principles, concepts, properties, and characteristics of the system-of-interest. It may also be applied to more than one system, in some cases forming the common structure, pattern, and set of requirements for classes or families of similar or related systems. | ||
| + | |||
| + | General Concepts and Principles | ||
| + | |||
| + | Notion of Structure | ||
| + | |||
<center>[[System Requirements|< Previous Article]] | [[System Definition|Parent Article]] | [[Logical Architecture Development|Next Article >]]</center> | <center>[[System Requirements|< Previous Article]] | [[System Definition|Parent Article]] | [[Logical Architecture Development|Next Article >]]</center> | ||
Revision as of 13:52, 22 June 2015
The purpose of system architecture activities is to define a comprehensive solution based on principles, concepts, and properties logically related and consistent with each other. The solution architecture has features, properties, and characteristics satisfying, as far as possible, the problem or opportunity expressed by a set of system requirements (traceable to mission/business and stakeholder requirements) and life cycle concepts (e.g., operational, support) and are implementable through technologies (e.g., mechanics, electronics, hydraulics, software, services, procedures).
System Architecture is abstract, conceptualization-oriented, global, and focused to achieve the mission and operational concepts of the system. It also focuses on high‐level structure in systems and system elements. It addresses the architectural principles, concepts, properties, and characteristics of the system-of-interest. It may also be applied to more than one system, in some cases forming the common structure, pattern, and set of requirements for classes or families of similar or related systems.
General Concepts and Principles
Notion of Structure
SEBoK Discussion
Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.
If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.
blog comments powered by Disqus