Scribd
Upload
47 views7 pages

Pratdnya Patra

1. The Waterfall model was used for the Time Scheduler project, which follows a linear sequential approach with distinct phases that must be completed before moving to the next. 2. The RAD model was used for the QR Attendance project, which is based on iterative prototyping and development with early customer testing and feedback. 3. Both models were evaluated based on their suitability for the respective projects and advantages.

Uploaded by

CM-B-01-Rohit Mithagari
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
47 views7 pages

Pratdnya Patra

1. The Waterfall model was used for the Time Scheduler project, which follows a linear sequential approach with distinct phases that must be completed before moving to the next. 2. The RAD model was used for the QR Attendance project, which is based on iterative prototyping and development with early customer testing and feedback. 3. Both models were evaluated based on their suitability for the respective projects and advantages.

Uploaded by

CM-B-01-Rohit Mithagari
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Experiment No.

: 1

Aim: Application of at least two traditional process models.

Software Used: MS Word

Theory: Software Processes is a coherent set of activities for specifying, designing,


implementing, and testing software systems. A software process model is an abstract
representation of a process that presents a description of a process from some perspective. There
are many different software processes but all involve:
• Specification – defining what the system should do;
• Design and implementation – defining the organization of the system and implementing
the system;
• Validation – checking that it does what the customer wants;
• Evolution – changing the system in response to changing customer needs.

Types of Software Process Model


Software processes, methodologies and frameworks range from specific prescriptive steps that
can be used directly by an organization in day-to-day work, to flexible frameworks that an
organization uses to generate a custom set of steps tailored to the needs of a specific project or
group. In some cases, a “sponsor” or “maintenance” organization distributes an official set of
documents that describe the process.
Software Process and Software Development Lifecycle Model
One of the basic notions of the software development process is SDLC models which stands for
Software Development Life Cycle models. There are many development life cycle models that
have been developed in order to achieve different required objectives. The models specify the
various stages of the process and the order in which they are carried out. The most used, popular
and important SDLC models are given below:
• Waterfall model
• V model
• Incremental model
• RAD model
• Iterative model
• Spiral model
• Prototype model
• Agile model
Library Management System:
The process model which is used by Time scheduler project is known as Waterfall model. The
Waterfall Model was the first Process Model to be introduced. It is 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. The Waterfall model is the earliest SDLC approach that was used for software
development.
The waterfall Model illustrates the software development process in a linear sequential flow.
This means that any phase in the development process begins only if the previous phase is
complete. In this waterfall model, the phases do not overlap.
Situations where the use of Waterfall model is most appropriate are −
• Requirements are very well documented, clear, and fixed.
• Product definition is stable.
• Technology is understood and is not dynamic.
• There are no ambiguous requirements.
• Ample resources with required expertise are available to support the product.
• The project is short.
Some of the major advantages for 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.
Implementation:
QR based Attendance:

The process model that is used by QR based Attendance project is known as RAD (Rapid
Application Development) Model. The RAD (Rapid Application Development) model is based
on prototyping and iterative development with no specific planning involved. The process of
writing the software itself involves the planning required for developing the product.
Rapid Application Development focuses on gathering customer requirements through workshops
or focus groups, early testing of the prototypes by the customer using iterative concept, reuse of
the existing prototypes (components), continuous integration and rapid delivery.
RAD model can be applied successfully to the projects in which clear modularization is possible.
If the project cannot be broken into modules, RAD may fail.
The applications of RAD are as follows −
• RAD should be used only when a system can be modularized to be delivered in an
incremental manner.
• It should be used if there is a high availability of designers for Modelling.
• It should be used only if the budget permits use of automated code generating tools.
• RAD SDLC model should be chosen only if domain experts are available with relevant
business knowledge.
The advantages of the RAD Model are as follows −
• Changing requirements can be accommodated.
• Progress can be measured.
• Iteration time can be short with use of powerful RAD tools.
• Productivity with fewer people in a short time.
• Reduced development time.
• Increases reusability of components.
• Quick initial reviews occur.
• Encourages customer feedback.
• Integration from very beginning solves a lot of integration issues.
Conclusion: Thus, applied at least two traditional process models on multiple projects.

Rubrics Timely Signature of staff


Neatness (5) Knowledge (5)
Submission (5) With Date
Marks

You might also like