Difference between revisions of "Systems Engineering and Quality Attributes"

From SEBoK
Jump to navigation Jump to search
Line 19: Line 19:
  
 
==References==  
 
==References==  
Please make sure all references are listed alphabetically and are formatted according to the Chicago Manual of Style (15th ed). See the [http://www.bkcase.org/fileadmin/bkcase/files/Wiki_Files__for_linking_/BKCASE_Reference_Guidance.pdf BKCASE Reference Guidance] for additional information.
 
 
 
===Citations===
 
===Citations===
List all references cited in the article. Note:  SEBoK 0.5 uses Chicago Manual of Style (15th ed). See the [http://www.bkcase.org/fileadmin/bkcase/files/Wiki_Files__for_linking_/BKCASE_Reference_Guidance.pdf BKCASE Reference Guidance] for additional information.
+
None.
 
 
 
===Primary References===
 
===Primary References===
All primary references should be listed in alphabetical order. Remember to identify primary references by creating an internal link using the ‘’’reference title only’’’ ([[title]]).  Please do not include version numbers in the links.
+
No primary references have been identified for version 0.5.  Please provide any recommendations on additional references in your review.
 
 
 
===Additional References===
 
===Additional References===
All additional references should be listed in alphabetical order.
+
No additional references have been identified for version 0.5.  Please provide any recommendations on additional references in your review.
 
----
 
----
 
====Article Discussion====
 
====Article Discussion====

Revision as of 17:23, 30 August 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.

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:

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)