Name – Adil

Roll No. – 2200320140015

Subject – SPM
1. Explain the following Models: i) Waterfall Model ii)RAD

i. Waterfall Model
The waterfall Model is also known as the Classical or Traditional Model.
Sometimes It is referred to as the linear-sequential life cycle model because all
phases involved in this model are completed one by one linearly. In this model,
we get software after the completion of all coding phases. This model is used
for small projects. There exist only one cycle in the waterfall model.

ii. RAD Model

RAD model stands for Rapid Application Development and it is the type
of Incremental Model. It can’t handle large projects but it can handle small
projects as well as medium projects. In the RAD model, any changes can be
made at any stage but in the waterfall, it can’t happen.
Planning at the initial phases of development is not necessary using the RAD
approach of software development. The quick development of the application is
the RAD model’s main objective. For development, the RAD paradigm requires
a small team size. The RAD approach also allows for any adjustments to be
made at any time. Consequently, compared to the waterfall model, it is a model
that is adaptable to changes. When using the RAD paradigm, there is less risk
associated.

2. Write the Name the Stack Holders of a Software Project.

The term Software Project Stakeholder refers to, “a person, group or

company that is directly or indirectly involved in the project and who may
affect or get affected by the outcome of the project”.

What is Stakeholder Identification?

It is the process of identifying a person, group or a company which can affect
or get affected by a decision, activity or the outcome of the software project.
It is important in order to identify the exact requirements of the project and
what various stakeholders are expecting from the project outcome.
Type of Stakeholders:
1. Internal Stakeholder:
An internal stakeholder is a person, group or a company that is directly involved
in the project.
For example,

1. Project Manager:
Responsible for managing the whole project. Project Manager is generally
never involved in producing the end product but he/she controls, monitors
and manages the activities involved in the production.
2. Project Team:
Performs the actual work of the project under the Project Manager including
development, testing, etc.
3. Company:
Organisation who has taken up the project and whose employees are
directly involved in the development of the project.
4. Funders:
Provides funds and resources for the successful completion of the project.
2. External Stakeholder:
An external stakeholder is the one who is linked indirectly to the project but has
significant contribution in the successful completion of the project.
For example,

1. Customer:
Specifies the requirements of the project and helps in the elicitation process
of the requirement gathering phase. Customer is the one for whom the
project is being developed.
2. Supplier:
Supplies essential services and equipment for the project.
3. Government:
Makes policies which helps in better working of the organisation.
 3. List some essential qualities of a software. ln spiral model,
what the radius of spiral shows?
The Spiral Model is one of the most important Software Development Life
Cycle models, which provides support for Risk Handling. In its diagrammatic
representation, it looks like a spiral with many loops. The exact number of loops
of the spiral is unknown and can vary from project to project. Each loop of the
spiral is called a Phase of the software development process.

The Spiral Model is a risk-driven model, meaning that the focus is on managing
risk through multiple iterations of the software development process. It consists
of the following phases:

 Planning: The first phase of the Spiral Model is the planning phase, where
the scope of the project is determined and a plan is created for the next
iteration of the spiral.
 Risk Analysis: In the risk analysis phase, the risks associated with the
project are identified and evaluated.
 Engineering: In the engineering phase, the software is developed based on
the requirements gathered in the previous iteration.
 Evaluation: In the evaluation phase, the software is evaluated to determine
if it meets the customer’s requirements and if it is of high quality.
 Planning: The next iteration of the spiral begins with a new planning phase,
based on the results of the evaluation.
 The Spiral Model is often used for complex and large software development
projects, as it allows for a more flexible and adaptable approach to software
development. It is also well-suited to projects with significant uncertainty or
high levels of risk.
4. What do you understand by scope of project? Why software re-
engineering is required for software product.
Project scope is the part of project planning that involves determining and
documenting a list of specific project goals, deliverables, tasks, costs and
deadlines. The documentation of a project's scope is called a scope
statement or terms of reference. It explains the boundaries of the project,
establishes responsibilities for each team member and sets up procedures for
how completed work will be verified and approved.

 articulates what the project entails so that all stakeholders can understand
what's involved;

 provides a roadmap that managers can use to assign tasks, schedule work
and budget appropriately;

 helps focus team members on common objectives; and

 prevents projects, particularly complex ones, from expanding beyond the

established vision.
Software Re-engineering is a process of software development which is done
to improve the maintainability of a software system. Re-engineering is the
examination and alteration of a system to reconstitute it in a new form. This
process encompasses a combination of sub-processes like reverse
engineering, forward engineering, reconstructing etc.
1. Improving software quality: Re-engineering can help improve the quality of
software by eliminating defects, improving performance, and enhancing
reliability and maintainability.
2. Updating technology: Re-engineering can help modernize the software
system by updating the technology used to develop, test, and deploy the
system.
3. Enhancing functionality: Re-engineering can help enhance the
functionality of the software system by adding new features or improving
existing ones.
4. Resolving issues: Re-engineering can help resolve issues related to
scalability, security, or compatibility with other systems.
The process of software re-engineering involves the following steps:
1. Planning: The first step is to plan the re-engineering process, which
involves identifying the reasons for re-engineering, defining the scope, and
establishing the goals and objectives of the process.
2. Analysis: The next step is to analyze the existing system, including the
code, documentation, and other artifacts. This involves identifying the
system’s strengths and weaknesses, as well as any issues that need to be
addressed.
3. Design: Based on the analysis, the next step is to design the new or
updated software system. This involves identifying the changes that need to
be made and developing a plan to implement them.
4. Implementation: The next step is to implement the changes by modifying
the existing code, adding new features, and updating the documentation and
other artifacts.
5. Testing: Once the changes have been implemented, the software system
needs to be tested to ensure that it meets the new requirements and
specifications.
6. Deployment: The final step is to deploy the re-engineered software system
and make it available to end-users

5. Why is it required to identify critical path in software

development cycle? How a critical path can be identified in small
network?
Critical path is a sequence of critical tasks/activities and is the largest path in
the project network. It gives us the minimum time which is required to complete
the whole project. The activities in the critical path are known as critical
activities and if these activities are delayed then the completion of the whole
project is also delayed.
Major steps of the Critical Path Method:
1. Identifying the activities
2. Construct the project network
3. Perform time estimation using forward and backward pass
4. Identify the critical path
Rules for designing the Activity-on-Node network diagram:
 A project network should have only one start node
 A project network should have only one end node
 A node has a duration
 Links normally have no duration
 “Precedents” are the immediate preceding activities
 Time moves from left to right in the project network
 A network should not contain loops
 A network should not contain dangles

 Activity label is the name of the activity represented by that node.

 Earliest Start is the date or time at which the activity can be started at the
earliest.
 Earliest Finish is the date or time at which the activity can completed at the
earliest.
 Latest Start is the date or time at which the activity can be started at the
latest.
 Latest Finish is the date or time at which the activity can be finished at the
latest.
 Float is equal to the difference between earliest start and latest start or
earliest finish and latest finish.