Difference between revisions of "Software design"
From Wiki @ Karl Jones dot com
Karl Jones (Talk | contribs) |
Karl Jones (Talk | contribs) |
||
| Line 1: | Line 1: | ||
'''Software design''' is the process of creating specifications for [[software]], including [[Artifact (software development)|software development artifacts]]. | '''Software design''' is the process of creating specifications for [[software]], including [[Artifact (software development)|software development artifacts]]. | ||
| + | |||
| + | This article is about the activity between requirements and programming. For the broader meaning, see [[software development]]. | ||
== Description == | == Description == | ||
Revision as of 08:05, 7 February 2016
Software design is the process of creating specifications for software, including software development artifacts.
This article is about the activity between requirements and programming. For the broader meaning, see software development.
Contents
Description
Software design may refer to either "all the activities involved in conceptualizing, framing, implementing, commissioning, and ultimately modifying complex systems" or "the activity following requirements specification and before programming, as ... [in] a stylized software engineering process."
Solving problems with software
Software design usually involves problem solving and planning a software solution.
High-level, low-level
Software design is typically divided into two (or more) scales:
- High-level: architectural design
- Low-level: component and algorithm design
See also
- Artifact (software development)
- Software architecture
- Software development
- Software engineering
- Software requirements
External links
- Software design @ Wikipedia
