Difference between revisions of "Software design"

From Wiki @ Karl Jones dot com
Jump to: navigation, search
(Software requirements)
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]].
 +
 +
== 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."
 
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."
Line 7: Line 9:
 
== See also ==
 
== See also ==
  
 +
* [[Artifact (software development)]]
 +
* [[Software development]]
 +
* [[Software engineering]]
 
* [[Software requirements]]
 
* [[Software requirements]]
  

Revision as of 11:05, 4 February 2016

Software design is the process of creating specifications for software, including software development artifacts.

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."

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