Question

1. Summarize the two systems development methodologies: SDLC and Prototyping. (Briefly)
2. Compare the waterfall methodology and the prototype methodology. (Briefly, in terms of advantages and disadvantages of both)

Answer 1

SDLC - Software Prototype Model. The Software Prototyping points out to building software application prototypes that display the functionality of the product under development but may not carry the exact logic of the original software.

the most common SDLC methodologies.

1. Waterfall Model.
2. V-Shaped Model.
3. Iterative Model.
4. Spiral Model.
5. Big Bang Model.
6. Agile Model.

Prototype methodology is a Software Development model in which a prototype is erect, tested, and then reworked when needed until an admissible prototype is achieved. The software prototyping model works best in scenarios where the project's requirements are unknown. A prototype is a preliminary model of an idea, design, process, interface, technology, product, service, or creative work. A prototype that is close on the result in functionality.

The Two types of prototyping: incremental or evolutionary and throwaway. Throwaway Approach, In the incremental approach, the prototype is revised and refined frequently up to it becomes the final product.

In prototyping, the analyst works with users to determine the initial or basic requirements for the system, while in SDLC, asserts that the spotlight on goals timeline. This means that SDLC focuses more on the analysis and design part of the system instead of fully conceptualizing user requirements.

WATERFALL MODEL vs. PROTOTYPING MODEL

Waterfall Model is a flow-based model which consist of following phases:-

1. System/Information Engineering and Modeling

2. Software Requirements Analysis

3. Systems Analysis and Design

4. Code Generation

5. Testing

6. Maintenance

A Waterfall method of software development has to pass through every phase once, and not meant to go back to the previous phase again. Once the requirements request is frozen, changes can’t be done during any phase. That is why it is used rarely nowadays. Due to this If there is any change in requirements, then it becomes difficult as well as costly affair. Apart from this, each phase takes a lot of time to solve its consecutive next phase as it is an irreversible process the solution should be well optimized and satisfactory. If one phase result goes wrong means subsequent phases get affected.

Prototyping Model is a technique that uses the technique of replication of a few aspects or features of the expected product and it is then developed upon it to obtain the full software. It can be called designing of software prototypes or temporary versions of the software program being developed for full edition deliverables.

The main theme behind the prototyping is to allow users to evaluate the developer’s proposals for the design of expected products based on real-time analysis by users rather than interpreting by the developers themselves. So it is also referred to as an efficient way of controlling the prototype that acts as a key factor in the commercial relationship between clients and respective solution providers. The customer and the contractor can contrast if the software made matches the software specification, according to which the software program is constructed.

In Prototype strategy of development as we create several Prototypes of the product, before the release of the final one. We release the number of Prototypes with some differences between them just as versions, and take client opinion, and modify the final product, as per client suggestions. The prototype is developed by keeping currently known requirements in the mind. The development of the prototype undergoes design, coding, testing like phases which give the client an actual feel of the system. The prototype is a model that looks exactly like the Software development life cycle (SDLC).