Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Software design
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Value == [[Software design document]]ation may be reviewed or presented to allow constraints, specifications and even requirements to be adjusted prior to [[computer programming|coding]]. Redesign may occur after a review of a programmed [[simulation]] or [[prototype]]. It is possible to design software in the process of coding, without a plan or requirement analysis,<ref>Ralph, P., and Wand, Y. A Proposal for a Formal Definition of the Design Concept. In, Lyytinen, K., Loucopoulos, P., Mylopoulos, J., and Robinson, W., (eds.), Design Requirements Engineering: A Ten-Year Perspective: Springer-Verlag, 2009, pp. 103-136</ref> but for more complex projects this is less feasible. A separate design prior to coding allows for [[multidisciplinary]] designers and [[subject-matter expert]]s (SMEs) to collaborate with programmers in order to produce software that is useful and technically sound.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)