MAHARASHTRA STATE BOARD OF TECHNICAL

EDUCATION – MUMBAI

A
Micro-Project Report On
“Selection criteria for software processing model and their
characteristics”

Submitted by,
Anurag Sandeep Mhaske[28]
Mohit Deepak Khandale [11]
Sahil Bhaskar Gaikwad [50]
Guided by
Prof. S.B. Patil ,
Head of Department,
Department of Information Technology

Academic Year
2022-23
MET’S INSTITUTE OF TECHNOLOGY - POLYTECHNIC
BHUJBAL KNOWLEDGE CITY, ADGAON, NASHIK
 MET’s Institute of Technology, Polytechnic
Bhujbal Knowledge City,
Adgaon, Nashik-422 003
Tel.: ( 0253)2303515, 2303267, 2303268 Telefax : ( 0253 )2303305,
Toll-free: 1800 22 0234 Email:principal_iot@bkc.met.edu

CERTIFICATE
This is to Certify that this report,
“Selection criteria for software processing model and their
characteristics”

Submitted by,
Anurag Sandeep Mhaske[28]
Mohit Deepak Khandale [11]
Sahil Bhaskar Gaikwad [50]
The students of Second year Information Technology Department
In 2022-23
As a part of project work as prescribed by
The Maharashtra State Board of Technical Education, Mumbai
And that I have guided them for the said work from time to time
And I found them satisfactorily progressive.
And that, the said work has been assessed by me and I am satisfied that the
same is up to the standard envisaged for the level of the course.

Prof . S.B. Patil Prof. S.B. Patil Dr. R.S. Narkhede

Project Guide Head of Department Principal
 ACKNOWLEDGEMENTS

We take this opportunity to express our deepest sense of gratitude and

sincere thanks to those who have helped us in completing this task.

We express our sincere thanks to our Project Guide Prof. S.B. Patil
Information Technology Department, who has given us excellent guidance,
continuous Encouragement for the completion of this work. His kind assistance
and constant inspiration will always help us in our future also.

We are very thankful to Head of Department Prof. S.B. Patil for

encouraging us to undertake this project and he has taken keen interest in
making the project and report absolutely flawless.

We are very thankful to Principal. Dr. R.S. Narkhede, for encouraging

us to undertake this project and he has taken keen interest in making the project
and report absolutely flawless.
 Annexure –I A

PART A - Plan
“ Selection criteria for software processing model and their characteristics”

1.0 Brief Introduction

Selection Process parameters plays an important role in software development as it helps to

choose the best suitable software life cycle model. Following are the parameters which
should be used to select a SDLC.Selection development life cycle (SLDC) is a process
utilised by the software industry for designing, developing and testing high quality software.
The SDLC intent to produce a high-quality software that meets or outreaches customer
expectancy, that meets completion within times and also less costing. SDLC is the short form
of Software Development Life Cycle. It is also known as Software Development Process.
Software development Life Cycle is a framework laying out task performed at each step in
the software development process. Software life cycle processes standard is ISO/IEC 12207
which is internationally recognised. It focuses to be the standard that characterises all the
tasks that are needed for developing and maintain software. What is SDLC? Software
development life cycle is a process pursued for a software project, in a software organisation.
It compromises of a step by step plan that explains how to develop, maintain, replace and
change or improve specific software. The life cycle entitles a methodology for enhancing the
quality of software and the general development process. Various stages of a typical software
development life cycle are − Planning Defining Designing Building Testing Deployment
Now we will look into each one of them in detail.
2.0 Aim of the Micro-Project

This Micro-Project aims at

1. To understand concept of Selection criteria of software processing & Characteristic
2. To know it’s significance.
3. To establish group co-ordination & participation by each member.
4. To understand the Importance of Software Selecting Criteria.
3.0 Action Plan
S. Details of activity Planned Planned Name of
No. Start date Finish date Responsible Team
Members
1 Discuss with the subject Anurag Mhaske
teacher regarding the concept 06/02/2023 06/02/202 Sahil Gaikwad
of “micro-project” which 3 Mohit Khandale
include in the I scheme.
2 Discuss with the subject Anurag Mhaske
teacher how to write a diary 13/02/2023 13/02/202 Sahil Gaikwad
and report of micro-project. 3 Mohit Khandale
3 Discuss with the subject Anurag Mhaske
teacher regarding the micro- 27/02/2023 27/02/202 Sahil Gaikwad
project topic. 3 Mohit Khandale
4 Searching Information Related Anurag Mhaske
to Scheduling Techniques . 13/03/2023 15/03/202 Sahil Gaikwad
3 Mohit Khandale
5 Anurag Mhaske
Differed the CPM and PERT 27/03/2023 27/03/202 Sahil Gaikwad
3 Mohit Khandale
6 Anurag Mhaske
Project Report Preparation 03/04/2023 03/04/202 Sahil Gaikwad
3 Mohit Khandale

4.0 Resources Required

S. Name of Specifications Qty Remark
No. Resource/mate s
rial
1 Computer Windows 11, 8GB RAM 1 -
system
2 Internet Various Websites like 1 -
www.tutorialspoint.com/software_engineerin
g/
www.sei.cmu.edu
www.nptel.ac.in/courses/
3 References Software Engineering : A practitioner’s
approach 1
 - Pressman, Roger S.
4 Word 2013 - 1 -

Annexure –II A
PART B
“ Selection criteria for software processing model and their characteristics”

1.0 Brief Introduction

Selection development life cycle (SLDC) is a process utilised by the software industry
for designing, developing and testing high quality software. The SDLC intent to
produce a high-quality software that meets or outreaches customer expectancy, that
meets completion within times and also less costing. SDLC is the short form of
Software Development Life Cycle. It is also known as Software Development Process.
Software development Life Cycle is a framework laying out task performed at each
step in the software development process. Software life cycle processes standard is
ISO/IEC 12207 which is internationally recognised. It focuses to be the standard that
characterises all the tasks that are needed for developing and maintain software.
What is SDLC? Software development life cycle is a process pursued for a software
project, in a software organisation. It compromises of a step by step plan that
explains how to develop, maintain, replace and change or improve specific software.
The life cycle entitles a methodology for enhancing the quality of software and the
general development process. Various stages of a typical software development life
cycle are − Planning Defining Designing Building Testing Deployment Now we will
look into each one of them in detail.

Stage 1: Planning and Requirement Analysis Requirement analysis is the most vital
and fundamental stage in Software Development Life Cycle. Reviews from the
customer, the sales department, market surveys and subject specialist in the
industry is taken as inputs which are further used by the senior members of the
team to perform the 4/11/23, 7:34 PM Selection Process Parameters for a Software
Life Cycle Model This detail is afterwards used to plan the basic project appeal and to
perform product feasibility study in the economical, operational and technical areas.
Things like planning for the quality assurance requirements and identification During
the planning stage, the quality assurance needs are planned for, as well as the risks
connected with the project. The technical feasibility study will outline the different
technical methods that may be used to effectively implement the project with the
least amount of risk.
 Stage 2: Establishing Requirements Following the completion of the requirement
study, the next stage is to explicitly describe and record the product needs and
obtain approval from the customer or market analysts. This is accomplished through
the use of an SRS (Software Requirement Specification) document, which contains all
of the product requirements that must be defined and produced throughout the
project life cycle.

Stage 3: Product Architecture Design SRS is the go-to resource for product architects
looking for the optimal architecture for a new product. Many design approaches for
the product architecture are typically presented and defined in a DDS-Design
Document Specification based on the SRS criteria. This DDS is evaluated by all key
stakeholders, and the ideal design strategy for the product is chosen based on
numerous factors such as risk assessment, product robustness, design modularity,
budget, and time limits. A design approach accurately outlines all of the product's
architectural modules, as well as its communication and data flow representation
with external and third-party modules (if applicable) (if any). All modules of the
proposed architecture's internal design should be completely specified in DDS, right
down to the tiniest detail.

Stage 4: Creating or Improving the Product The real development of the product
begins at this level of the SDLC. During this stage, the programming code is
generated following DDS. Code generation may be achieved without much difficulty
if the design is detailed and structured. Developers must adhere to their
organization's coding requirements, and programming tools such as compilers,
interpreters, debuggers, and so on are used to create code. For coding, many
highlevel programming languages such as C, C++, Pascal, Java, and PHP are utilized.
The programming language is chosen based on the sort of software being created

Stage 5: Product Testing As in contemporary SDLC models, testing activities are

mainly included in all SDLC stages, this stage is usually a subset of all phases. This
stage, however, refers to the product's testing only stage, during which product
faults are reported, monitored, repaired, and retested until the product meets the
quality requirements established in the SRS.

Stage 6: Market Deployment and Maintenance Once the product has been
thoroughly tested and is ready for deployment, it is formally released in the relevant
market. Product deployment may occur in stages depending on the organization's
business plan. The product may first be introduced in a small market sector and
tested in a real world business setting (UAT- User acceptance testing). The product
 may then be released as is or with recommended enhancements in the targeted
market group depending on the feedback. Following the product's release to the
market, it is maintained for the current client base. Models of the SDLC Various
software development life cycle models have been created and intended to be used
during the software development process. These are also called as Software
Development Process Models ". To assure success in the software development
process, each process model follows a set of procedures that are specific to its kind.
The following are the most essential and widely used SDLC models in the industry −
The Waterfall Model The Iterative Model The Spiral Model The V-Model The Big
Bang Model Agile Model, RAD Model, Rapid Application Development, and
Prototyping Models are also similar methods. Waterfall Model of SDLC The Waterfall
Model was first referred to as a Process Model. It's also known as a linear-sequential
life cycle model. It is really simple to grasp and apply. In a waterfall model, each state
must be finished before the next one can start, and the stages must not overlap. The
Waterfall model was the first SDLC technique utilized in software development.

Selection Process parameters plays an important role in software development as it

helps to choose the best suitable software life cycle model. Following are the
parameters which should be used to select a SDLC.
1. Requirements characteristics : Reliability of Requirements How often the
requirements can change Types of requirements Number of requirements Can
the requirements be defined at an early stage Requirements indicate the
complexity of the system

2. Development team : Team size Experience of developers on similar type of

projects Level of understanding of user requirements by the developers Environment
Domain knowledge of developers Experience on technologies to be used Availability
of training

2. User involvement in the project : Expertise of user in project Involvement of user

in all phases of the project Experience of user in similar project in the past

3. Project type and associated risk : Stability of funds Tightness of project schedule
Availability of resources Type of project Size of the project Expected duration for the
completion of project Complexity of the project Level and the type of associated risk

2.0 Aim of the Micro-Project

This Micro-Project aims at

 1. To understand concept Criteria software Selecting model .
2. To know it’s significance.
3. To establish group co-ordination & participation by each member
4. To understand the importance of Software development criteria .

3.0 Action Plan

S. Details of activity Planned Planned Name of

No. Start date Finish date Responsible Team
Members
1 Discuss with the subject Anurag Mhaske
teacher regarding the concept 06/02/2023 06/02/202 Sahil Gaikwad
of “micro-project” which 3 Mohit Khandale
include in the I scheme.
2 Discuss with the subject Anurag Mhaske
teacher how to write a diary 13/02/2023 13/02/202 Sahil Gaikwad
and report of micro-project. 3 Mohit Khandale
3 Discuss with the subject Anurag Mhaske
teacher regarding the micro- 27/02/2023 27/02/202 Sahil Gaikwad
project topic. 3 Mohit Khandale
4 Searching Information Related Anurag Mhaske
to Scheduling Techniques . 13/03/2023 15/03/202 Sahil Gaikwad
3 Mohit Khandale
5 Anurag Mhaske
Differed the CPM and PERT 27/03/2023 27/03/202 Sahil Gaikwad
3 Mohit Khandale
6 Anurag Mhaske
Project Report Preparation 03/04/2023 03/04/202 Sahil Gaikwad
3 Mohit Khandale

4.0 Resources Required

S. Name of Specifications Qty Remark

No. Resource/mate s
rial
1 Computer Windows 11, 8GB RAM 1 -
system
2 Internet Various Websites like 1 -
www.tutorialspoint.com/software_engineerin

3 References
4 Word 2016
g/
www.sei.cmu.edu
www.nptel.ac.in/courses/
Software Engineering : A practitioner’s
approach 1
- Pressman, Roger S.
- 1 -

5.0 Skill Developed / learning out of this Micro-Project

 From This microproject we learnt about concepts we learned in Software

Engineering Scheduling techniques and its proper significance .
 Plus, we had a good team work in this microproject, each one done there work
carefully and with proper observation.
 Also we learnt a more Criteria for software and what information is needed for it.
 Learned to prepare a proper format , and more about a computer.
 Teacher Evaluation Sheet

Name of Student: Anurag Sandeep Mhaske Enrollment No. : 2107760287

Name of Department : Information Technology Semester: 4-I
Course Title: Software Engineering (SEN) Code: 22413
Title of the Micro-Project : Selection criteria for software processing model and their
characteristics

Course Outcomes Achieved:

1) Select suitable Software Process model for software development.
2) Process model and their uses.
3) Learned about Selecting Criteria with their significance .

Evaluation as per Suggested Rubric for Assessment of Micro Project

Sr. Characteristic to be assessed Poor Average Good Excellent

No. ( Marks 1 - ( Marks 4 - ( Marks 6 - ( Marks 9-
3) 5) 8) 10 )
1 Relevance to the course
2 Literature Survey / Information
Collection
3 Project Proposal
4 Completion of the Target as per
project proposal
5 Analysis of Data and
representation
6 Quality of Prototype/Model

7 Report Preparation
8 Presentation
9 Defense
 MIcro-Project Evaluation Sheet

Process Assessment Product Assessment Total

Part A - Project Methodology PartB - Project individual Marks
Project (2 marks) Report/Working Presentation/Viva
Proposal Model (4 marks) 10
(2 marks) (2 marks)

Note:
Every course teacher is expected to assign marks for group evolution in first 3
columns & individual evaluation in 4TH columns for each group of students as per
rubrics.

Comments/Suggestions about team work/leadership/inter-personal communication (if

any)
………………………………………………………………………………………………
……………………………………………………………………………………………..
……………………………………………………………………………………………..
……………………………………………………………………………………………..

Any Other Comment:

……………………………………………………………………………………………
……………………………………………………………………………………………
……………………………………………………………………………………………
………………………………………………………………………………………………

Prof. S.B. Patil – Head of Department

Signature…………………………………………………………………………………………...
 Teacher Evaluation Sheet

Name of Student: Mohit Deepak Khandale Enrollment No. : 2107760266

Name of Department : Information Technology Semester: 4-I
Course Title: Software Engineering (SEN) Code: 22413
Title of the Micro-Project : Selection criteria for software processing model and their
characteristics

Course Outcomes Achieved:

11) Select suitable Software Process model for software development.
2) Process model and their uses.
3) Learned about Selecting Criteria with their significance .
Evaluation as per Suggested Rubric for Assessment of Micro Project

Sr. Characteristic to be assessed Poor Average Good Excellent

No. ( Marks 1 - ( Marks 4 - ( Marks 6 - ( Marks 9-
3) 5) 8) 10 )
1 Relevance to the course
2 Literature Survey / Information
Collection
3 Project Proposal
4 Completion of the Target as per
project proposal
5 Analysis of Data and
representation
6 Quality of Prototype/Model

7 Report Preparation
8 Presentation
9 Defense
 MIcro-Project Evaluation Sheet

Process Assessment Product Assessment Total

Part A - Project Methodology PartB - Project individual Marks
Project (2 marks) Report/Working Presentation/Viva
Proposal Model (4 marks) 10
(2 marks) (2 marks)

Note:
Every course teacher is expected to assign marks for group evolution in first 3
columns & individual evaluation in 4TH columns for each group of students as per
rubrics.

Comments/Suggestions about team work/leadership/inter-personal communication (if

any)
………………………………………………………………………………………………
……………………………………………………………………………………………..
……………………………………………………………………………………………..
……………………………………………………………………………………………..

Any Other Comment:

……………………………………………………………………………………………
……………………………………………………………………………………………
……………………………………………………………………………………………
………………………………………………………………………………………………

Prof. S.B. Patil – Head of Department

Signature…………………………………………………………………………………………...
 Teacher Evaluation Sheet

Name of Student: Sahil Bhaskar Gaikwad Enrollment No. : 2107760317

Name of Department : Information Technology (IF) Semester: 4-I
Course Title: Software Engineering (SEN) Code: 22413
Title of the Micro-Project :
Selection criteria for software processing model and their characteristics

Course Outcomes Achieved:

1) Select suitable Software Process model for software development.
2) Process model and their uses.
3) Learned about Selecting Criteria with their significance .
Evaluation as per Suggested Rubric for Assessment of Micro Project

Sr. Characteristic to be assessed Poor Average Good Excellent

No. ( Marks 1 - ( Marks 4 - ( Marks 6 - ( Marks 9-
3) 5) 8) 10 )
1 Relevance to the course
2 Literature Survey / Information
Collection
3 Project Proposal
4 Completion of the Target as per
project proposal
5 Analysis of Data and
representation
6 Quality of Prototype/Model

7 Report Preparation
8 Presentation
9 Defense
 MIcro-Project Evaluation Sheet

Process Assessment Product Assessment Total

Part A - Project Methodology PartB - Project individual Marks
Project (2 marks) Report/Working Presentation/Viva
Proposal Model (4 marks) 10
(2 marks) (2 marks)

Note:
Every course teacher is expected to assign marks for group evolution in first 3
columns & individual evaluation in 4TH columns for each group of students as per
rubrics.

Comments/Suggestions about team work/leadership/inter-personal communication (if

any)
………………………………………………………………………………………………
……………………………………………………………………………………………..
……………………………………………………………………………………………..
……………………………………………………………………………………………..

Any Other Comment:

……………………………………………………………………………………………
……………………………………………………………………………………………
……………………………………………………………………………………………
………………………………………………………………………………………………

Prof. S.B. Patil – Head of Department

Signature…………………………………………………………………………………………...