Iterative Prototyping Methodology for Desklib

Methodology
Iterative Prototyping
The system development life cycle to be used is the iterative Prototyping methodology. This was
arrived at after consideration of the requirements specification, which are understood and
predicted to evolve with time. The process allows the developer to start with a limited part of the
requirements and the iteration design gives room to return and add to the requirements to expand
the abilities repeatedly until the system is fully developed, and can be implemented and later
deployed(Morell, 2018).
The idea is to deliver small tested features for review with the customer, meaning a continuous
improvement in small discrete parts. In simple terms, each iteration can be modified according to
new functionalities that are developed. The methodology is versatile enough, such that more than
one iteration can take place in the cycle at one given time (Choetkiertikul et al., 2018) . The
frequent, rigorous testing of each version are vital in delivering quality prototypes, making it an
ideal methodology for successful projects
Suitable projects for the method.
The methodology works best on projects of the following type:
• The essential requirements are established and analyzed, but more requirements are expected
to be added and evolve to suit the client need.
• The timeline to deliver is a constraint
• Clear requirements are well defined for a start
• The technology being used is expected to develop
• New technology is being learned by the developer
• The goals of the project are expected to change (moving target)
• The budget is limited
The advantages and disadvantages of the methodology.
Advantages

• Risks are identified and dealt with early enough, during iterations and testing.
• Testing is easy as it is done in the small modules.
• The progress of the development can be easily measured
• The lifecycle produces functional prototypes that indicate potential defects
• The development team coordinates easily
• More resources and emphasis is put on development and design rather than on
documentation.
• It is easier to incorporate ideas on the go
• It is cheaper to deal with changes in goals and scope
• The project is easily managed using milestones
• The development time is significantly reduced
• Each iteration produces an operational prototype for further evaluation
• The success rate is very high as compared to other methodologies
• The client gives feedback according to a presentable and working prototype
• The return on investment (ROI) is quick
Disadvantages
Each methodology has its limitations, but the iterative design has relatively few limitations as
compared to other methods (Dessai and Kamat, 2012).
• Lack of full requirements may lead to a constraint in the system architecture and
infrastructure
• Might need more resources to achieve the desired functionality successfully
• The successful cycles are rigid
• Professional project management may be required
• The risk analysis requires highly skilled and experienced staff
• The project duration is difficult to establish accurately and can only be estimated

When developing an application, or software, most methodologies employ a closer relationship
between the developer or the developing team and the customer. When this happens, in most times,
there occurs a trade-off between the system functionality, time and time factor (Fulbright, 2013),
leading to a pullback of one of the elements, which are essential.
The iterative methodology works best to collaborate and put more emphasis on the crucial factors and
implementing them effectively, which handles risks more cheaply and efficiently and saves the project from
stalling (Ramsin and Paige, 2010). Before full launch, each iteration and prototype passes through rigorous tests,
from the storyboards, wireframes and other initial stages, to front-end and back-end designs and the final stages of
the user testing. The methodology furthermore allows the developer to be reactive to possible and emerging risks
and be proactive too (Managing Iterative Software Development Projects, 2007).
Below is a diagramatic representation of the model.

3RD ITERATION Nth
1ST ITERATION
2ND ITERATION
The Iterative Prototype Methodology.
Requirements
Task ID 1
Analysis
Task ID 2
Design
Task ID 3
Testing
Task ID 4
Implementation
Task ID 5
(Prototype)
Review
Task ID 6
Design
Testing
Implementation
Review
Design
Testing
Implementation
Integration
Task ID 7
Deployment
Task ID 8
Maintenance
Task ID 9