5. System Development Life Cycle

The methodology used for developing this system is PROTOTYPING MODEL. This model is used here because detailed input, output requirements are not present in the beginning, and thus it is felt that a prototyping model will be more suitable for development. In this model, we will create a quick design and then invite user to test the developed system and refine requirements if any. Thus, the process for development will be iterative.

Often, a customer defines a set of general objectives for software but does not identify detailed input, processing or output requirements. In other cases, the developer may be unsure of the efficiency of an algorithm, the adaptability of an operating system, or the form that human/machine interaction should take. In these, and many other situations, a prototyping model offers the best approach.

It generally has the following steps:
i. Requirement Gathering
ii. Quick Design
iii. Build Prototype
iv. Customer Evaluation
v. Review/Modify Requirements
vi. Coding
vii. Testing