Difference between revisions of "Software design"
From Wiki @ Karl Jones dot com
Karl Jones (Talk | contribs) (etc) |
Karl Jones (Talk | contribs) (Software requirements) |
||
| Line 4: | Line 4: | ||
Software design usually involves problem solving and planning a software solution. This includes both low-level component and [[algorithm design]] and high-level [[Software architecture|architectural design]]. | Software design usually involves problem solving and planning a software solution. This includes both low-level component and [[algorithm design]] and high-level [[Software architecture|architectural design]]. | ||
| + | |||
| + | == See also == | ||
| + | |||
| + | * [[Software requirements]] | ||
== External links == | == External links == | ||
* [https://en.wikipedia.org/wiki/Software_design Software design] @ Wikipedia | * [https://en.wikipedia.org/wiki/Software_design Software design] @ Wikipedia | ||
Revision as of 09:41, 4 June 2015
Software design is the process of creating specifications for software, including software development artifacts.
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."
Software design usually involves problem solving and planning a software solution. This includes both low-level component and algorithm design and high-level architectural design.
See also
External links
- Software design @ Wikipedia
