Software Engineering Features - Models, Methods, Tools, Standards, and Metrics

From SEBoK
Revision as of 19:18, 13 October 2015 by Thilburn (talk | contribs)
Jump to: navigation, search

In recent decades software has become ubiquitous. Almost all modern engineered systems include significant software subsystems; this includes systems in the transportation, finance, education, healthcare, legal, military, and business sectors. Along with the increase in software utility, capability, cost, and size there has been a corresponding growth in methods, models, tools, metrics and standards, which support software engineering.

Chapter 10 of the SWEBOK discusses modeling principles and types, and the methods and tools that are used to develop, analyze, implement, and verify the models. The other SWEBOK chapters on the software development phases (e.g., Software Design) discuss methods and tools specific to the phase. Table 2 identifies software engineering features for different life-cycle phases. The table is not meant to be complete; it simply provide examples. In Part 2 of the SEBoK there is discussion of models and the following is one of the definitions offered: “an abstraction of a system, aimed at understanding, communicating, explaining, or designing aspects of interest of that system” (Dori 2002). For the purposes of Table 2 we extend the definition of a model to some aspect of the software system or it development. So as an example, we list “Project Plan” as a model in the Software Management area. The idea is that the Project Plan provides a model of how the project is going to be carried out: the project team organization, the process to be used, the work to be done, the project schedule, and the resources needed.

Table 2: SWE Features

Life-Cycle Activity Models Methods & Tools Standards

Software Management

  • Life-Cycle Process Model
  • Work Breakdown Structure
  • Constructive Cost Model (COCOMO)
  • Project Plan
  • Configuration Management (CM) Plan
  • Risk Management Plan
  • Effort, Schedule and Cost Estimation
  • Risk Analysis
  • Data Collection
  • Project Tracking
  • CM Management
  • Iterative/Incremental Development
  • Agile Development
  • [IEEE 828]
  • [IEEE 1058]
  • [IEEE 1540]
  • [IEEE 12207]

Software Requirements

  • Functional Model
  • User Class Model
  • Data Flow Diagram
  • Object Model
  • Formal Model
  • User Stories
  • Requirements Elicitation
  • Prototyping
  • Structural Analysis
  • Data-Oriented Analysis
  • Object-Oriented Analysis
  • Object Modeling Language (OML)
  • Formal Methods
  • Requirements Specification
  • Requirements Inspection

[IEEE 830] [IEEE 1012] [IEEE 12207]


Works Cited

Primary References

Additional References

< Previous Article | Parent Article | Next Article >

SEBoK v. 1.9.1 released 30 September 2018

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