Revision as of 22:01, 1 June 2007 edit AlephGamma (talk \| contribs) 908 edits m Added related topics ← Previous edit		Revision as of 20:49, 4 June 2007 edit undo 77.99.124.7 (talk) Changed text - user shouldn't be intimidated about an issue! Next edit →
Line 22: ''Main article [[Systems design]]'' System engineers analyze and understand the business of the proposed system by studying the user requirements document. They figure out possibilities and techniques by which the user requirements can be implemented. If any of the requirements is not feasible, the user is ~~intimidated~~informed ~~about~~of the issue. A resolution is found and the user requirement document is edited accordingly. The software specification document which serves as a blueprint for the development phase is generated. This document contains the general system organization, menu structures, [[Data structure\|data structures]] etc. It may also hold examples business scenarios, sample windows, reports for the better understanding. Other technical documentation like entity diagrams, data dictionary will also be produced in this phase. The documents for system testing is prepared in this phase.

V-model (software development): Difference between revisions