DATTA MEGHE COLLEGE OF ENGINEERING
DEPARTMENT OF COMPUTER ENGINEERING
ACADEMIC YEAR 2023-24 (TERM I)
SUBJECT: SOFTWARE ENGINEERING LAB (CSL501)
SEM: V DIV: A&B
RUBRICS FOR GRADING ASSIGNMENTS
Rubric Marks*
Rubric Title Criteria
Number (out of 5)
On-time 2
Punctuality,
R1 Completion Time Delayed by not more than a Week 1
/ Timeline
Delayed more than a Week 0
Clear understanding 2
Knowledge &
R2 Partially understood 1
Concept
Weak understanding 0
Correct Documentation 1
R3 Documentation
Not documented properly 0
*means obtained marks will be scaled to 5 for Assignments
EXPERIMENT NO.:01
Date of Performance:
Date of Submission:
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 particular
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
● Agile model
● Iterative model
● Spiral model
● Prototype model
8
Waterfall model
Reasons to use waterfall model for our project:
The waterfall model is simple and easy to understand, implement, and use.
All the requirements are known at the beginning of the project, hence it is easy to
manage.
Our model is prediction model so waterfall model is used in this project.
Waterfall methodology just follows the direction where the first goes or those who
leads the direction.
Spiral Model
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 exact number of phases needed to develop the product can
be varied by the project manager depending upon the project risks. As the project
manager dynamically determines the number of phases, so the project manager has an
important role to develop a product using the spiral model.
The Radius of the spiral at any point represents the expenses(cost) of the project so far,
and the angular dimension represents the progress made so far in the current phase.
Advantages of Spiral Model:
Below are some advantages of the Spiral Model.
1. Risk Handling: The projects with many unknown risks that occur as the
development proceeds, in that case, Spiral Model is the best development
model to follow due to the risk analysis and risk handling at every phase.
2. Good for large projects: It is recommended to use the Spiral Model in large
and complex projects.
3. Flexibility in Requirements: Change requests in the Requirements at later
phase can be incorporated accurately by using this model.
4. Customer Satisfaction: Customer can see the development of the product at
the early phase of the software development and thus, they habituated with the
system by using it before completion of the total product.
Conclusion: Process Model was successfully selected for the project.
Sign and Remark:
Total
R1 R2 R3 Signature
Marks
(5) (5) (5) (15)
