Talk:Software design/Archives/2017
 | This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Definition of Software Design
This definition of software is very confusing and inaccurate. I think the Software Engineering Institute Book of Knowledge (SWEBOK) contains a clearer definition.
- Design is defined as both “the process of defining the architecture, components, interfaces, and other characteristics of a system or component” and “the result of [that] process”
I also believe that design is not part of requirements; they are different disciplines. Again, there is a clear distinction in the SWEBOK between design and requirements.
Konjurer (talk) 20:32, 11 January 2017 (UTC)
This is how I would paraphrase the SWEBOK definition of software design and its relationship to software requirements:
- Software Design is the process of describing a software solution by defining an architecture, software components, interfaces between components and other characteristics of the solution.
- Software Design also includes the result of this process, frequently in the form of diagrams and models of the intended solution. It is the bridge between the software requirements and the actual solution. In a tradition software development lifecycle design fits between requirements and implementation.