White and black box design

From UG

(Difference between revisions)
Jump to: navigation, search
(Black box design)
 
(One intermediate revision not shown)
Line 20: Line 20:
* Requirements doc completed
* Requirements doc completed
-
* Developer codes based on Requirements doc (creating functional Prototype)
+
* Developer codes based on Requirements doc (creating Fully Functional Prototype)
* Sys analyst creates and documents Design based on Prototype
* Sys analyst creates and documents Design based on Prototype
* Design and Prototype go through review process
* Design and Prototype go through review process
* QA tests based on Design doc
* QA tests based on Design doc
 +
 +
== Test ==

Current revision as of 16:29, 3 December 2010


Contents

[edit] Intro

Lets introduce Two types of Design methodology.

[edit] White box design

What we follow now in most cases:

  • Requirements doc completed
  • Sys analyst creates and documents Design based on Requirements doc
  • Design goes through review process
  • developer codes based on Design doc
  • QA tests based on Design doc

[edit] Black box design

Alternative approach:

  • Requirements doc completed
  • Developer codes based on Requirements doc (creating Fully Functional Prototype)
  • Sys analyst creates and documents Design based on Prototype
  • Design and Prototype go through review process
  • QA tests based on Design doc

[edit] Test

Personal tools