Difference between revisions of "Systems Engineering and Quality Attributes"

From SEBoK
Jump to navigation Jump to search
Line 1: Line 1:
 
Specialty engineering includes those disciplines that support the development process for a product, service, or enterprise endeavor by applying crosscutting knowledge to system design decisions in order to balance total system performance and affordability.
 
Specialty engineering includes those disciplines that support the development process for a product, service, or enterprise endeavor by applying crosscutting knowledge to system design decisions in order to balance total system performance and affordability.
 
+
==Topics==
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, EMI requirements can impact the signal in the interfaces between subsystems, and mass-volume requirements may preclude 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. 
 
===Topics===
 
 
The Systems Engineering and Specialty Engineering knowledge area contains the following topics:
 
The Systems Engineering and Specialty Engineering knowledge area contains the following topics:
 
*[[Integration of Specialty Engineering]]
 
*[[Integration of Specialty Engineering]]
Line 17: Line 13:
 
*[[Manufacturability and Producibility]]
 
*[[Manufacturability and Producibility]]
 
*[[Workplace Engineering]]
 
*[[Workplace 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, EMI requirements can impact the signal in the interfaces between subsystems, and mass-volume requirements may preclude 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==  
 
==References==  

Revision as of 16:54, 1 September 2011

Specialty engineering includes those disciplines that support the development process for a product, service, or enterprise endeavor by applying crosscutting knowledge to system design decisions in order to balance total system performance and affordability.

Topics

The Systems Engineering and Specialty Engineering knowledge area contains the following topics:

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, EMI requirements can impact the signal in the interfaces between subsystems, and mass-volume requirements may preclude 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

Citations

None.

Primary References

No primary references have been identified for version 0.5. Please provide any recommendations on additional references in your review.

Additional References

No additional references have been identified for version 0.5. Please provide any recommendations on additional references in your review.


Article Discussion

[Go to discussion page]

<- Previous Article | Parent Article | Next Article ->

Signatures

--Bkcase 19:08, 22 August 2011 (UTC) (on behalf of Dick Fairley) --Asquires 17:25, 30 August 2011 (UTC)(see Discussion)