System Development Methodology: Difference between revisions

Revision as of 17:45, 11 February 2006

Revision as of 08:51, 16 March 2006

Line 51:

* Global design. This phase combines a functional and technical design and only gives a broad design for the system. Often, the architecture of the system is described here.

* Detailed design. This phase continues the global design by creating more detailed designs to the point where they can be used to build the system itself. This is split to create seperateseparate parts of the system to be created.

===Building the system===

Line 61:

The testing consists of two steps: A system test and an acceptance test.

During the system test the development team (or a seperateseparate testing team) tests the system. Most of this will be focused on the technical aspects: Does the system work as it should or are there bugs still present? Bugs that are found in this phase will be fixed. At the ending of this phase, the program should work properly.

During the acceptance test the end-users will test the system. They will test to see if the program does what they want it to do. They will not test every possible scenario, but they will test to see if the program does what they want and expect it to do and that it works in an easy way. Bugs that are found in this phase will be reported to the development team so that they can fix these bugs.