System Definition (glossary): Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
''<blockquote>A set of core technical activities of [[Systems Engineering (glossary)]], including the activities that are completed primarily in the front-end portion of the | ''<blockquote>A set of core technical activities of [[Systems Engineering (glossary)]], including the activities that are completed primarily in the front-end portion of the [[System (glossary)]] [[Design (glossary)]]. These consist of [[Mission (glossary)]] analysis and [[Stakeholder Requirement (glossary)|stakeholders requirements]], [[System Requirement (glossary)|system requirements]], architectural design, and system analysis.</blockquote>'' | ||
====Source==== | ====Source==== | ||
This definition was developed for the SEBoK version 0.5. ‘’Note to reviewers’’: If you are aware of a more authoritative definition, please provide this information in your review. | |||
===Discussion=== | ===Discussion=== | ||
There is currently no discussion for this term. This will be completed for SEBoK version 1.0. | |||
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
Revision as of 14:00, 14 September 2011
A set of core technical activities of systems engineering , including the activities that are completed primarily in the front-end portion of the system design . These consist of mission analysis and stakeholders requirements, system requirements, architectural design, and system analysis.
Source
This definition was developed for the SEBoK version 0.5. ‘’Note to reviewers’’: If you are aware of a more authoritative definition, please provide this information in your review.
Discussion
There is currently no discussion for this term. This will be completed for SEBoK version 1.0.