Difference between revisions of "Systems Engineering and Quality Attributes"
| Line 1: | Line 1: | ||
| + | |||
| + | <html> | ||
| + | <meta name="citation_title" content="Systems Engineering and Specialty Engineering"> | ||
| + | <meta name="citation_author" content="Pyster, Art"> | ||
| + | <meta name="citation_author" content="Olwell, David H."> | ||
| + | <meta name="citation_author" content="Hutchison, Nicole"> | ||
| + | <meta name="citation_author" content="Enck, Stephanie"> | ||
| + | <meta name="citation_author" content="Anthony, James F., Jr."> | ||
| + | <meta name="citation_author" content="Henry, Devanandham"> | ||
| + | <meta name="citation_author" content="Squires, Alice (eds)"> | ||
| + | <meta name="citation_publication_date" content="2012/11/30"> | ||
| + | <meta name="citation_journal_title" content="Guide to the Systems Engineering Body of Knowledge (SEBoK)"> | ||
| + | <meta name="citation_volume" content="version 1.0.1"> | ||
| + | <meta name="citation_pdf_url" content="http://www.sebokwiki.org/1.0.1/index.php?title=Main_Page"></html> | ||
Specialty engineering disciplines support product, service and enterprise development by applying crosscutting knowledge to system design decisions, balancing total system performance and affordability. This knowledge area presents several of the supporting engineering disciplines with a focus on the systems engineer. | Specialty engineering disciplines support product, service and enterprise development by applying crosscutting knowledge to system design decisions, balancing total system performance and affordability. This knowledge area presents several of the supporting engineering disciplines with a focus on the systems engineer. | ||
Revision as of 18:15, 28 November 2012
<html> <meta name="citation_title" content="Systems Engineering and Specialty Engineering"> <meta name="citation_author" content="Pyster, Art"> <meta name="citation_author" content="Olwell, David H."> <meta name="citation_author" content="Hutchison, Nicole"> <meta name="citation_author" content="Enck, Stephanie"> <meta name="citation_author" content="Anthony, James F., Jr."> <meta name="citation_author" content="Henry, Devanandham"> <meta name="citation_author" content="Squires, Alice (eds)"> <meta name="citation_publication_date" content="2012/11/30"> <meta name="citation_journal_title" content="Guide to the Systems Engineering Body of Knowledge (SEBoK)"> <meta name="citation_volume" content="version 1.0.1"> <meta name="citation_pdf_url" content="http://www.sebokwiki.org/1.0.1/index.php?title=Main_Page"></html> Specialty engineering disciplines support product, service and enterprise development by applying crosscutting knowledge to system design decisions, balancing total system performance and affordability. This knowledge area presents several of the supporting engineering disciplines with a focus on the systems engineer.
Topics
Each part of the SEBoK is divided into knowledge areas (KAs), which are groupings of information with a related theme. The KAs in turn are divided into topics. This KA contains the following topics:
- Integration of Specialty Engineering
- Reliability, Availability, and Maintainability
- Human Systems Integration
- Safety Engineering
- Security Engineering
- System Assurance
- Electromagnetic Interference/Electromagnetic Compatibility
- Resilience Engineering
- Manufacturability and Producibility
- Affordability
- Environmental Engineering
Specialty Requirements
The systems engineering team must ensure that specialty requirements are properly reviewed with regard to their impact on life cycle costs, development schedule, technical performance, and operational utility. For example, security requirements can impact operator workstations, electromagnetic interference requirements can impact the signal in the interfaces between subsystems, and mass-volume requirements may preclude the use of certain materials to reduce subsystem weight.
Engineering specialists audit the evolving design and resulting configuration items to ensure that the overall system performance also satisfies the specialty requirements. Including appropriate specialty engineers within each systems engineering team assures that all system requirements are identified and balanced throughout the development cycle.
References
Works Cited
None.
Primary References
None.
Additional References
None.
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