CS507 Solution Assignment 3

Provided by ♥ρoωєя gιяlѕ♥

Q. 1: How can you describe the factors which will ensure the successful
implementation of SDLC? Explain at least three.

Factors for Successful implementation of SDLC

1. Well Defined Procedures

In every process there are procedures that seemed identical with another procedure.
Developers should have a clear understanding of each phase, the goal of a certain step
and evaluate of if the goal of a certain procedure is followed.

2. Management Support

Developers need to have the support of the management as much as possible since the
management will read out whether they need the product or not. Developers, especially
those who are working with a company have to work with managers in creating this type
of software.

3. Proper Documentation for success

Success in building software will only be once they are released to the pubic with ease.
Although there will be problems, it’s up to the developers to maintain these programs
until these are decommissioned. If worst comes to worst and it has to go back to the
drawing board, documentation will tell the developers where they might have done it
wrong.

Q. 2: List down the pros and cons of Incremental Model? Also mention when to use
the Incremental Model?

Pros of Incremental Model

 Delivers an operational quality product at each stage, but one that satisfies
only a subset of the client’s requirements.
 A relative small number of programmers/developers may be used.
 From the delivery of the first build, the client is able to perform useful
work (portions of the complete product might be available to customers in weeks
 instead of waiting for the final product, compared waterfall, rapid prototyping
model, which deliver only then the complete product is finished).
 Reduces the traumatic effect of imposing a completely new product on the
client organization by providing a gradual introduction.
 There is a working system at all times.
 Clients can see the system and provide feedback.
 Progress is visible, rather than being buried in documents.
 Most importantly, it breaks down the problem into sub-problems, dealing
with reduced complexity, and reduced the ripple effect of changes by reducing
the scope to only a part of the problem at a time.
 Distributes feedback throughout the whole development cycle, leading to
more stable artifacts.

Cons of Incremental Model

 Each additional build has somehow to be incorporated into the existing

structure without degrading the quality of what has been build to date.
 Addition of succeeding builds must be easy and straightforward.
 The more the succeeding builds are the source of unexpected problems,
the more the existing structure has to be reorganized, leading to inefficiency
and degrading internal quality and degrading maintainability.
 The incremental models can easily degenerate into the build and fix
approach.
 Design errors become part of the system and are hard to remove.
 Clients see possibilities and want to change requirements.

Uses of the Incremental Model

Incremental model may involve a complete open set of requirements that are
implemented in a series of small projects. As an alternative, a project using the
incremental model may start with general objectives
The incremental model performs the waterfall in overlapping sections attempting to
compensate for the length of waterfall model projects by producing usable functionality
earlier.