Faculty of Informatics

Department of Information System

Management Information System | Assignment 1

By: Ateklet Tesfaye

January 2021
Contents

1. Waterfall model.....................................................................................................................................3

1.1. Illustration Diagram.....................................................................................................................................3

1.2. Advantages..................................................................................................................................................4

1.3. Disadvantages.............................................................................................................................................5

2. V-Model......................................................................................................................................................5

2.1. Illustration Diagram.....................................................................................................................................5

2.2. V-Model – Advantage and Disadvantage.....................................................................................................6

3. Spiral model................................................................................................................................................6

3.1. Phases involved in Spiral Model..................................................................................................................7

3.2. Advantages and disadvantages of spiral model...........................................................................................7

4. RAD Model..................................................................................................................................................8

4.1. Advantages and Disadvantages for RAD model...........................................................................................9

5. Prototyping Model......................................................................................................................................9

6. Staged Delivery Model..............................................................................................................................10

7. Code and Fix Model..................................................................................................................................10

8. system development methodologies comparison...................................................................................11

 Assignment for Management Information System | 2021

1. Waterfall model
The waterfall model is first process model that breakdown of project activities into linear sequential
phases, where each phase depends on the deliverables of the previous one and corresponds to a
specialization of tasks. The model also referred to as a linear-sequential life cycle model. It is very
simple to understand and use. In a waterfall model, each phase must be completed before the next
phase can begin and there is no overlapping in the phases, in this waterfall model, the phases do not
overlap.

1.1. Illustration Diagram

The following illustration is a representation of the different phases of the Waterfall Model

The sequential phases in Waterfall model are

 Requirement Gathering and analysis: All possible requirements of the system to be

developed are captured in this phase and documented in a requirement specification document.
 System Design: The requirement specifications from first phase are studied in this phase and
the system design is prepared. This system design helps in specifying hardware and system
requirements and helps in defining the overall system architecture.
 Implementation: With inputs from the system design, the system is first developed in small
programs called units, which are integrated in the next phase. Each unit is developed and tested
for its functionality, which is referred to as Unit Testing.
 Integration and Testing: All the units developed in the implementation phase are integrated
into a system after testing of each unit. Post integration the entire system is tested for any faults
and failures.

1
 Assignment for Management Information System | 2021

 Deployment of system: Once the functional and non-functional testing is done; the product is
deployed in the customer environment or released into the market.
 Maintenance: There are some issues which come up in the client environment. To fix those
issues, patches are released. Also, to enhance the product some better versions are released.
Maintenance is done to deliver these changes in the customer environment.

1.2. Advantages
Some of the major advantages of the Waterfall Model are as follows −

 Simple and easy to understand and use

 Easy to manage due to the rigidity of the model. Each phase has specific deliverables and a
review process.
 Phases are processed and completed one at a time.
 Works well for smaller projects where requirements are very well understood.
 Clearly defined stages.
 Well understood milestones.
 Easy to arrange tasks.
 Process and results are well documented.

1.3. Disadvantages
The major disadvantages of the Waterfall Model are as follows −
 No working software is produced until late during the life cycle.
 High amounts of risk and uncertainty.
 Not a good model for complex and object-oriented projects.
 Poor model for long and ongoing projects.
 Not suitable for the projects where requirements are at a moderate to high risk of changing. So,
risk and uncertainty are high with this process model.
 It is difficult to measure progress within stages.
 Cannot accommodate changing requirements.
 Adjusting scope during the life cycle can end a project.
 Integration is done as a "big-bang. at the very end, which doesn't allow identifying any
technological or business bottleneck or challenges early.

2
 Assignment for Management Information System | 2021

2. V-Model
The V-model is an SDLC model where execution of processes happens in a sequential manner in a V-
shape. It is also known as Verification and Validation model.

The V-Model is an extension of the waterfall model and is based on the association of a testing phase
for each corresponding development stage. This means that for every single phase in the development
cycle, there is a directly associated testing phase. This is a highly-disciplined model and the next phase
starts only after completion of the previous phase.

2.1. Illustration Diagram

The following illustration depicts the different phases in a V-Model of the SDLC.

Developer's life Tester's Life cycle

cycle

One of the key aspects of the V model is that verification and validation are performed simultaneously
in both the branches. It is essential to link the left branch with the right branch as the left side of V
model is executed to correct problems, which are encountered during verification and validation (the
right side).

2.2. V-Model – Advantage and Disadvantage

Advantage Disadvantage
 Easy to use  Very rigid
 Simple to use  Least flexible
 Testing activities like planning, test  Software is developed during the
designing happens well before coding. implementation phase, so no early prototypes

3
 Assignment for Management Information System | 2021

 Time saving, quick of the software are produced

 Hence higher chance of success over the
waterfall model
 Proactive defect tracking – that is defects
are found at early stage
 Avoids the downward flow of the defects
 Works well for small projects where
requirements are easily understood.
 If any changes happen in midway, then the
test documents along with requirement
documents has to be updated
 Risky.
 The processes are institutionalized during the
project and when the project is finished, they
are abolished.

3. Spiral model
Spiral model is the combination of both sequential model and prototype model. The spiral model is
specifically designed for projects which are huge in size and requires regular enhancements. The spiral
model is somewhat similar to the incremental model but more emphasis on risk analysis, engineering,
and evaluation.

To understand better have a look at the sequential diagram about the model!

3.1. Phases involved in Spiral Model

Planning phase: All the required information about the project will be gathered in this phase.
Requirements such as BRS (business requirement specification and SRS (system requirement
specifications), design alteration, etc. will be done in this phase. Cost estimation, scheduling the
resources for iteration, etc. also happens in this phase.

4
 Assignment for Management Information System | 2021

Risk Analysis: Requirements of the project is studied and brainstorm sessions are conducted to figure
out potential risks involved. Once the risk has been identified proper strategies and risk mitigation
methodologies will be planned.

Testing phase: Testing alongside developmental changes will be done in this phase. Coding, test case
development, test execution, test summary report, defect report generation, etc. happens in this phase.

Evaluation phase: Customer can evaluate the tests and can give feedback before the project goes to the
next level.

3.2. Advantages and disadvantages of spiral model

Advantages:

 Risk management is easy in this type of model. When you are handling expensive and complex
projects, risk management is a must. Moreover, Spiral model has the ability to make any
software testing project transparent.
 Customer can see and review the test and different stages
 Projects can be separated into various parts to ease the management difficulty
 Documentation control is strong in this type of methodology
 Project estimate will tend to be more realistic as it progresses.

Disadvantages:

 Cannot be used for small projects as it can be expensive

 A vast amount of documentation owing to several intermediate stages
 The end date of the project cannot be calculated at the early stages of the project
 Complex process
 High expertise is required to run the model

4. RAD Model
RAD Model or Rapid Application Development model is a software development process based on
prototyping without any specific planning. In RAD model, there is less attention paid to the planning
and more priority is given to the development tasks. It targets at developing software in a short span of
time.

The following illustration depicts the different phases in a RAD Model of the SDLC.

5
 Assignment for Management Information System | 2021

The following are the five main stages of RAD model.

Business Modeling:  In this phase, business functions and product scope are decided during various
meetings between the requirements planning team and the client team.

Data Modeling: In the data modeling phase, all the information derived in the business modeling phase
is analyzed and separated into different data elements important for the business.

Process Modeling: In this phase, all the data objects gathered in the process modeling phase are
transformed into required useful information.

Application Generation: In this stage, the actual prototype is developed using different automated
CASE tools.

Testing and Turnover: In this stage, all the modules and interfaces of the prototype are tested.

4.1. Advantages and Disadvantages for RAD model

Advantage
 Requirements can be changed at any time
 Encourages and priorities customer feedback
 Reviews are quick
 Development time is drastically reduced
 More productivity with fewer people
 Time between prototypes and iterations is
short
Disadvantage
 Needs strong team collaboration
 Cannot work with large teams
 Needs user requirement throughout the life
cycle of the product
 Only suitable for projects which have a small
development time
 More complex to manage when compared to

 Integration isn’t a problem, since it other models

integrates from project inception  Only systems which can be modularized can be

6
 Assignment for Management Information System | 2021

developed using Rapid application development.

5. Prototyping Model
Prototyping Model is a software development model in which prototype is built, tested, and reworked
until an acceptable prototype is achieved. It also creates base to produce the final system or software. It
works best in scenarios where the project's requirements are not known in detail. It is an iterative, trial
and error method which takes place between developer and client.

The prototype model phases are illustrated as below

6. Staged Delivery Model

The staged-delivery model is another lifecycle model in which you show software to the customer in
successively refined stages. Unlike the evolutionary-prototyping model, when you use staged delivery,
you know exactly what you're going to build when you set out to build it. What makes the staged-
delivery model distinctive is that you don't deliver the software at the end of the project in one fell
swoop. You deliver it in successive stages throughout the project. (This model is also known as
"incremental implementation.") 

7. Code and Fix Model

The code and fix model probably are the most frequently used development methodology in software
engineering. It starts with little or no initial planning. You immediately start developing, fixing
problems as they occur, until the project is complete.

Code and fix are a tempting choice when you are faced with a tight development schedule because you
begin developing code right away and see immediate results.

Unfortunately, if you find major architectural problems late in the process, you usually have to rewrite
large parts of the application. Alternative development models can help you catch these problems in the
early concept stages, when making changes is easier and less expensive.

7
 Assignment for Management Information System | 2021

The code and fix model are appropriate only for small projects that are not intended to serve as the
basis for future development.

8. system development methodologies comparison

Due to the fact that there are plenty of methodologies and some of them are proprietary, meaning that
they are owned by the organization that put them together and uses them, it’s quite difficult to put
together a framework for a comparison study of methodologies.
To overcome this difficulty, In the following section we would list and define some criteria that would
be helpful for any IT professional involved in a system development project to choose among the
existing methodologies to determine which one would fit the project he/she is working on based on a
predefined objective.
So, all the criteria would be related to a component of a methodology or one of its phases. As stated in
the definition above, a methodology is a set of steps to follow for a system development. One of the
differences between the step-by-step methodologies and the SCURM methodology is that the latter has
only two defined processes planning and closure, whereas the waterfalls admit that all processes are
defined and well known, and the various step are implemented in a linear fashion.

So, the first criteria of comparison would be

Processes definition: By process definition we mean does the methodology assume that every step in
the development life cycle is well known? and that there is no room for environmental changes? or does
the methodology allow a big deal of flexibility in all stages of the development cycle to incorporate
those changes that needs to be incorporated in the project before its closure.

Final product determination: Other criteria would be related to the final product. Does the
methodology define the final product early on in the planning stage or does it define it during the
project and close to project closure time.

Project cost: This criterion is related to the estimation of the cost of the project and at what stage of the
project it's done.

8
 Assignment for Management Information System | 2021

Project completion date: Estimation of a schedule of deliverable based on the estimation of the tasks
to be accomplished. Is that done up front or as the project progresses.

Responsiveness to environment: This criterion measures the flexibility that the methodology allows to
incorporate changes during the project, changes due to the environment, technology, competition or
other.

Team dynamic and creativity: The steps predefined by the methodology could be an obstacle to
creativity among teams, as the linear model suggests that some work needs to be done first by a small
group and then the project moves to the next stage. This criterion try to measure the ability of allowing
some team work and interactions among the team members.

Role of the upper management: Is management an obstacle in creating a better system, or is the role
of management to empower the team by taking care of any obstacles that impact the team performance.

Training and knowledge: Does the methodology steps allow training and knowledge transfer during
the project or does it put a limitation to what a team member can do and learn.

Probability of success: This criterion measures the probability of success of a project using a certain
methodology by embracing a certain degree of complexity and unpredictability.