Difference between revisions of "Software Engineering in the Systems Engineering Life Cycle"
| Line 15: | Line 15: | ||
<center> | <center> | ||
| − | [Key Points a Systems Engineer Needs to Know about Software Engineering|< Previous Article]] | [[Systems Engineering and Software Engineering|Parent Article]] | [[Software Engineering Features - Models, Methods, Tools, and Standards|Next Article >]]</center> | + | [[Key Points a Systems Engineer Needs to Know about Software Engineering|< Previous Article]] | [[Systems Engineering and Software Engineering|Parent Article]] | [[Software Engineering Features - Models, Methods, Tools, and Standards|Next Article >]]</center> |
{{DISQUS}} | {{DISQUS}} | ||
[[Category: Part 6]][[Category: Topic]][[Category:Systems Engineering and Software Engineering]] | [[Category: Part 6]][[Category: Topic]][[Category:Systems Engineering and Software Engineering]] | ||
Revision as of 12:39, 20 October 2015
The development of a complex software system or subsystem has a life cycle. Like for any system, the engineering of a software product consists of analysis and design, construction testing, operation, maintenance, and eventually retirement or replacement.
In Part 3 of the SEBoK, SE and Management, there is discussion of SE life cycle models and processes, with special attention to the Vee and Iterative process models. Both models, with some modification, apply equally to the development of software products and systems. Part 3 also discusses the IEEE standard on System Life Cycle Processes [IEEE 15528] which describes a set of processes that address the various phases of the SE life-cycle – for example, Project Planning, Requirements Analysis, Architectural Design, Implementation, Verification, Operation, Maintenance, and Disposal. There is a corresponding IEEE standard on Software Life Cycle Processes [IEEE 12207], which describes a set of processes that address the various phases of the software life-cycle – for example, Requirements Analysis, Architectural Design, Detailed Design, Construction, Verification, Maintenance, Operation, and Disposal.
When the software part of system is complex enough to be considered a subsystem, its life-cycle would be assimilated as part of the life-cycle of the entire system, with such activities as software requirements analysis, and software verification and validation embedded as part of the corresponding systems activities. Table 2 presents some of the models, methods and tools used in software engineering. The table is meant to illustrative and is not exhaustive or complete.
References
Works Cited
[IEEE 12207] IEEE Computer Society, IEEE Standard for Systems and Software Engineering —Software Life Cycle Processes, IEEE Std 12207-2008, 2008.
[IEEE 15528] IEEE Computer Society, IEEE Standard for Systems and Software Engineering —System Life Cycle Processes, IEEE Std 15528-2008, 2008.
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