5/12/25, 7:06 PM 315323-SOFTWARE ENGINEERING

12-05-2025 07:06:28 PM

SOFTWARE ENGINEERING Course Code : 315323

: Computer Technology/ Computer Engineering/ Computer Science & Engineering/
Programme Name/s Computer Hardware & Maintenance/
Computer Science & Information Technology/ Computer Science
Programme Code : CM/ CO/ CW/ HA/ IH/ SE
Semester : Fifth
Course Title : SOFTWARE ENGINEERING
Course Code : 315323

I. RATIONALE
Software Engineering is the foundation for professional processes to be followed for designing, developing, testing
and maintaining software involving principles, different techniques, and practices for software development. This
course enable students to develop requisite abilities to follow systemic and disciplined approach to software
development that aims to create high quality, reliable and maintainable software.

II. INDUSTRY / EMPLOYER EXPECTED OUTCOME

Apply software engineering principles to develop software product.

III. COURSE LEVEL LEARNING OUTCOMES (COS)

Students will be able to achieve & demonstrate the following COs on completion of course based learning

CO1 - Select suitable software development process model

CO2 - Prepare software requirement specification.
CO3 - Construct different Software design models
CO4 - Apply different planning and cost estimation techniques for a software product
CO5 - Apply project management techniques in software development.
CO6 - Use quality assurance principles in software development

IV. TEACHING-LEARNING & ASSESSMENT SCHEME

Learning Scheme Assessment Scheme
Actual
Based on LL &
Contact Based on
Theory TL
Course Course Hrs./Week SL
Course Title Abbr Credits Paper Total
Code Category/s SLH NLH Practical
Duration Marks
FA- SA-
CL TL LL Total FA-PR SA-PR SLA
TH TH
Max Max Max Min Max Min Max Min Max Min
SOFTWARE
315323 STE DSC 4 - 4 1 9 3 3 30 70 100 40 25 10 25@ 10 25 10 175
ENGINEERING
Total IKS Hrs for Sem. : 0 Hrs
Abbreviations: CL- ClassRoom Learning , TL- Tutorial Learning, LL-Laboratory Learning, SLH-Self Learning
Hours, NLH-Notional Learning Hours, FA - Formative Assessment, SA -Summative assessment, IKS - Indian
Knowledge System, SLA - Self Learning Assessment
Legends: @ Internal Assessment, # External Assessment, *# On Line Examination , @$ Internal Online
Examination
Note :

1. FA-TH represents average of two class tests of 30 marks each conducted during the semester.
2. If candidate is not securing minimum passing marks in FA-PR of any course then the candidate shall be
declared as "Detained" in that semester.
3. If candidate is not securing minimum passing marks in SLA of any course then the candidate shall be
declared as fail and will have to repeat and resubmit SLA work.
4. Notional Learning hours for the semester are (CL+LL+TL+SL)hrs.* 10 Weeks
5. 1 credit is equivalent to 30 Notional hrs.
6. * Self learning hours shall not be reflected in the Time Table.
7. * Self learning includes micro project / assignment / other activities.

MSBTE Approval Dt. 24/02/2025 Semester - 5, K Scheme

Page 1/6
5/12/25, 7:06 PM 315323-SOFTWARE ENGINEERING
12-05-2025 07:06:28 PM

SOFTWARE ENGINEERING Course Code : 315323

V. THEORY LEARNING OUTCOMES AND ALIGNED COURSE CONTENT

Suggested
Theory Learning Outcomes Learning content mapped with Theory Learning
Sr.No Learning
(TLO's)aligned to CO's. Outcomes (TLO's) and CO's.
Pedagogies.
TLO 1.1 Select the attributesUnit - I Software Development Process
that match with standards for1.1 Software characteristics, Types of software.
the given software 1.2 The Process: Software Engineering: A Layered
application. approach -Process, Methods and Tools
TLO 1.2 Suggest the relevant 1.3 Software development framework.
software solution for the 1.4 Software Process Model: Waterfall Model Presentations
1 given problem. 1.5 Incremental Process Model: RAD Model Lecture Using
TLO 1.3 Select the relevant 1.6 Evolutionary Process Models: Prototyping model, Chalk-Board
software process model for Spiral model
the given problem. 1.7 Agile Process Model: Extreme Programming,
TLO 1.4 Suggest the relevant Adaptive Software Development (ASD), Scrum,
activities in Agile Dynamic System Development Method (DSDM),
Development Process. CRYSTAL. Agile Unified Process (AUP)
Unit - II Software Requirement Engineering
TLO 2.1 Apply principles of 2.1 Software Engineering core principles.
software engineering for the 2.2 Software Practices: Communication, Planning,
given problem. Modelling, Construction, Software deployment
TLO 2.2 Select the relevant (Statement and meaning of each principles for each
Lecture Using
requirement engineering practice).
Chalk-Board
2 steps for the given problem. 2.3 Requirement Engineering: Requirement Gathering
Presentations
TLO 2.3 Construct the and Analysis, Types: Functional, Product, organizational,
Case Study
Requirement Engineering External Requirements, Eliciting Requirements,
model for the given problem. Developing Use-cases, Building requirement models,
TLO 2.4 Prepare SRS for the Negotiation, Validation.
given problem. 2.4 Software Requirement Specification: Need, Format,
and its Characteristics.
TLO 3.1 Identify the
elements of analysis model
for the given software Unit - III Software Modelling and Design
requirements. 3.1 Translating Requirement model into design model:
TLO 3.2 Apply the specified Data Modelling.
design concepts for software 3.2 Analysis Modelling: Elements of Analysis model.
requirements modeling. 3.3 Design modelling: Fundamental Design Concepts
TLO 3.3 Construct software (Abstraction, Information hiding, Structure, Modularity, Lecture Using
design using standard design Concurrency, Verification, Aesthetics). Chalk-Board
3
notation. 3.4 Design notations: Data Flow Diagram (DFD), Presentations
TLO 3.4 State the purpose of Structured Flowcharts, Decision Tables. Demonstration
software testing. 3.5 UML Modelling :Use-Case ,Class Diagrams,
TLO 3.5 Draw Use-Case Sequence Diagrams.
,Class Diagrams, Sequence 3.6 Testing – Meaning and purpose, testing methods -
Diagrams for software Black-box and White-box, Static and Dynamic testing,
project. Level of testing, V-model.
TLO 3.6 Explain basic types
of software testing.

MSBTE Approval Dt. 24/02/2025 Semester - 5, K Scheme

Page 2/6
5/12/25, 7:06 PM 315323-SOFTWARE ENGINEERING
12-05-2025 07:06:28 PM

SOFTWARE ENGINEERING Course Code : 315323

Suggested
Theory Learning Outcomes Learning content mapped with Theory Learning
Sr.No Learning
(TLO's)aligned to CO's. Outcomes (TLO's) and CO's.
Pedagogies.
TLO 4.1 Explain the
management spectrum for
software project.
Unit - IV Software Project Cost Estimation
TLO 4.2 Estimate size of
4.1 The Management Spectrum – 4P’s.
software product.
4.2 Metrics for Size Estimation: Line of Code (LoC), Lecture Using
TLO 4.3 Estimate cost of
Function Points (FP). Chalk-Board
software product using the
4.3 Project Cost Estimation Approaches: Overview of Presentations
4 empirical method.
Heuristic, Analytical, and Empirical Estimation. Case Study
TLO 4.4 Compute size of the
4.4 COCOMO (Constructive Cost Model), COCOMO II. Flipped
given software using
4.5 Risk Analysis and Management: Risk identification, Classroom
COCOMO model.
Risk assessment, Risk management and monitoring, Risk
TLO 4.5 Apply RMMM
Refinement and Mitigation, RMMM Plan.
strategy in Identified risks
for any software
development problem.
TLO 5.1 Apply CPM/PERT Unit - V Software Project Management
scheduling technique for 5.1 Project Scheduling: Basic principles, Work
Lecture Using
software project. breakdown structure, Activity network
Chalk-Board
5 TLO 5.2 Construct timeline 5.2 Project Tracking: Timeline charts, Earned Value
Presentations
chart/ Gantt chart to track Analysis, Gantt Charts.
Demonstration
progress of the given 5.3 Scheduling techniques: Critical Path Method(CPM),
software project. Program Evaluation Review Technique(PERT)
TLO 6.1 Differentiate
between Software Quality
Unit - VI Software Quality Assurance
Management and Software
6.1 Software Quality Management vs. Software Quality
Quality Assurance. Lecture Using
Assurance.
TLO 6.2 Apply the phases of Chalk-Board
6 6.2 Phases of Software Quality Assurance: Planning,
Software Quality Assurance Presentations
activities, audit, and review.
in software development Case Study
6.3 Quality Evaluation standards: Six Sigma, CMMI:
project
Levels, Process areas.
TLO 6.3 Apply software
quality evaluation standards.

VI. LABORATORY LEARNING OUTCOME AND ALIGNED PRACTICAL / TUTORIAL EXPERIENCES.

Practical / Tutorial / Laboratory Sr Laboratory Experiment / Practical Titles / Number Relevant
Learning Outcome (LLO) No Tutorial Titles of hrs. COs
LLO 1.1 Use software tool to Write
*Write problem statement to define the project
problem statement and identify 1 2 CO1
title with bounded scope of the project.
scope of the project
LLO 2.1 Use appropriate process
Select relevant process model to define activities
model and activities related to 2 2 CO1
and related tasks set
project.
*Gather application specific requirements for
LLO 3.1 Apply the principles of
3 assimilate into RE (Requirement’s engineering) 2 CO2
requirement engineering.
model.
LLO 4.1 Create SRS document for *Prepare broad SRS (software requirement
4 2 CO2
the project. software) for the project.
LLO 5.1 Construct use case
5 *Write use-cases and draw use-case diagram. 2 CO3
diagram for software models.
LLO 6.1 Design activity diagram Draw the activity diagram to represent flow from
6 2 CO3
for the project. one activity to another for software development.

MSBTE Approval Dt. 24/02/2025 Semester - 5, K Scheme

Page 3/6
5/12/25, 7:06 PM 315323-SOFTWARE ENGINEERING
12-05-2025 07:06:28 PM

SOFTWARE ENGINEERING Course Code : 315323

Practical / Tutorial / Laboratory Sr Laboratory Experiment / Practical Titles / Number Relevant
Learning Outcome (LLO) No Tutorial Titles of hrs. COs
LLO 7.1 Draw data flow diagram
for the project. *Create DFDs (data flow diagram), Decision
7 2 CO3
LLO 7.2 Create Decision tables and tables and E-R (entity-relationship) diagram.
E-R diagram.
LLO 8.1 Represent software project Draw class diagram and Sequence diagram, State
8 2 CO3
by class diagrams. Transition Diagram.
LLO 9.1 Prepare decision table for
9 * Create decision table for a project. 2 CO3
the project
LLO 10.1 Design test cases by *Write test cases to validate requirements from
10 2 CO3
referring SRS document. SRS document.
LLO 11.1 Write test cases for
11 Prepare test cases for Black Box Testing. 2 CO3
Blackbox testing.
LLO 12.1 Identify risk involved in * Identify risks involved in the project and
the project 12 prepare RMMM (RMMM-Risk Management, 2 CO4
LLO 12.2 Prepare RMMM Plan. Mitigation and Monitoring) plan.
LLO 13.1 Estimate size of project * Calculate size of the project using Function
13 2 CO4
using function point matrix point metric.
*Calculate cost of the project using COCOMO
LLO 14.1 Estimate size of project
14 (Constructive Cost Model) / COCOMO II 2 CO4
using COCOMO approach.
approach.
*Create software project scheduling charts using
LLO 15.1 Prepare project schedule
15 CPM (Critical Path Method) / PERT (Project 2 CO5
using CPM/PERT technique.
Evaluation and Review Technique)
LLO 16.1 Monitor the progress of Track progress of the project using Timeline
16 2 CO5
project using timeline/Gantt chart charts/ Gantt charts.
LLO 17.1 Prepare SQA plan to Prepare SQA plan that facilitates various
17 2 CO6
ensure various quality processes. attributes of quality of process.
LLO 18.1 Prepare SQA plan to *Prepare SQA plan that facilitates various
18 2 CO6
ensure quality product. attributes of quality of product.
Note : Out of above suggestive LLOs -
'*' Marked Practicals (LLOs) Are mandatory.
Minimum 80% of above list of lab experiment are to be performed.
Judicial mix of LLOs are to be performed to achieve desired outcomes.

VII. SUGGESTED MICRO PROJECT / ASSIGNMENT/ ACTIVITIES FOR SPECIFIC LEARNING /

SKILLS DEVELOPMENT (SELF LEARNING)

Micro project

Apply the principles of software engineering for Portfolio website for showcasing Skills and Work , Searchability
and Online Presence , Demonstrating Growth and Progress , Career Advancement and Networking and Prepare
complete technical document.
Apply the principles of software engineering for Chatbot Application to create an intelligent chatbot to enhance
customer support processes, providing efficient and personalized assistance and Develop technical document.
Apply the principles of software engineering for Online Chat Application Project that enables users to exchange
messages and communicate with each other in real-time. It allows individuals or groups to have conversations, share
information, and collaborate instantly over the Internet. Online Chat Application is designed to provide a responsive
and interactive experience, where messages are delivered and displayed immediately as they are sent and Prepare
complete technical document.

Assignment

Estimate Cost of software using any tool and risk involved in the library Management System
MSBTE Approval Dt. 24/02/2025 Semester - 5, K Scheme
Page 4/6
5/12/25, 7:06 PM 315323-SOFTWARE ENGINEERING
12-05-2025 07:06:28 PM

SOFTWARE ENGINEERING Course Code : 315323

Create DFDs, Activity Diagram, ER-Diagrams for Student Management System.
Visit any medical shop and collect requirements from shop keeper and create SRS document

Other

Complete the course basic of software engineering on Infosys Springboard or any MOOCs platforms.

Note :

Above is just a suggestive list of microprojects and assignments; faculty must prepare their own bank of
microprojects, assignments, and activities in a similar way.
The faculty must allocate judicial mix of tasks, considering the weaknesses and / strengths of the student in
acquiring the desired skills.
If a microproject is assigned, it is expected to be completed as a group activity.
SLA marks shall be awarded as per the continuous assessment record.
For courses with no SLA component the list of suggestive microprojects / assignments/ activities are
optional, faculty may encourage students to perform these tasks for enhanced learning experiences.
If the course does not have associated SLA component, above suggestive listings is applicable to Tutorials
and maybe considered for FA-PR evaluations.

VIII. LABORATORY EQUIPMENT / INSTRUMENTS / TOOLS / SOFTWARE REQUIRED

Sr.No Equipment Name with Broad Specifications Relevant LLO Number
1 Software Project Management Tools: Open source Software such as Jira. 1,2,3,4,10,11,17,18
2 Software Design tools : Projectriskmanager 12
3 Software Design tools :Open Project, Ganttproject 3.3 15,16
4 Software Design tools: Free Use Case Diagram Creator 5
5 Software Design tools: Draw.io, Decision Table Maker, Tiny tools 6,7,8,9,13,14
6 Hardware: Personal computer, processor i3 and above, RAM minimum 4 GB All
7 Operating system: Windows 10 and above All

IX. SUGGESTED WEIGHTAGE TO LEARNING EFFORTS & ASSESSMENT PURPOSE (Specification

Table)
Aligned Learning R- U- A- Total
Sr.No Unit Unit Title
COs Hours Level Level Level Marks
1 I Software Development Process CO1 7 2 6 4 12
Software Requirement
2 II CO2 9 4 6 4 14
Engineering
3 III Software Modelling and Design CO3 9 4 4 8 16
4 IV Software Project Cost Estimation CO4 8 2 2 8 12
5 V Software Project Management CO5 4 2 2 4 8
6 VI Software Quality Assurance CO6 3 2 2 4 8
Grand Total 40 16 22 32 70

X. ASSESSMENT METHODOLOGIES/TOOLS

Formative assessment (Assessment for Learning)

Each practical will be assesed considering 60% weightage to process, 40% weighatge to product.
Continuous assessment based on process and product related performance indicators.
A Continuous assessment -based term work.

Summative Assessment (Assessment of Learning)

End Semester Examination, Lab Performance, Viva voce

MSBTE Approval Dt. 24/02/2025 Semester - 5, K Scheme

Page 5/6
5/12/25, 7:06 PM 315323-SOFTWARE ENGINEERING
12-05-2025 07:06:28 PM

SOFTWARE ENGINEERING Course Code : 315323

XI. SUGGESTED COS - POS MATRIX FORM

Programme
Specific
Programme Outcomes (POs)
Outcomes*
(PSOs)
Course PO-5
Outcomes PO-1 Basic Engineering
(COs) PO-3 PO-7
and PO-2 PO-4 Practices for
Design/ PO-6 Project Life PSO- PSO- PSO-
Discipline Problem Engineering Society,
Development Management Long 1 2 3
Specific Analysis Tools Sustainability
of Solutions Learning
Knowledge and
Environment
CO1 1 2 2 2 1 - 1
CO2 2 3 3 2 1 - 1
CO3 2 2 3 3 - - 1
CO4 2 2 2 3 - 2 2
CO5 2 3 2 3 - 3 2
CO6 - 2 2 3 1 2 2
Legends :- High:03, Medium:02,Low:01, No Mapping: -
*PSOs are to be formulated at institute level

XII. SUGGESTED LEARNING MATERIALS / BOOKS

Sr.No Author Title Publisher with ISBN Number
Roger S. Pressman & Bruce Software Engineering: A McGraw Hill Higher Education, New Delhi,
1
R. Maxim practitioner's approach (Ninth Edition) ISBN 93-5532-504-5
Software Engineering McGraw Hill Education New Delhi -2001,
2 Richard Fairly
Concepts ISBN-13: 9780074631218
Software Engineering: Oxford University Press, New Delhi ISBN
3 Deepak Jain
Principles and practices 9780195694840
Srinivasan Desikan, Software Testing: Principles PEARSON Publisher: Pearson India 2007,
4
Gopalaswamy Ramesh and Practices ISBN: 978-81-7758-121-8
Sams Publishing; 2nd edition, 2005 ISBN:
5 Ron Patton Software Testing
0672327988

XIII . LEARNING WEBSITES & PORTALS

Sr.No Link / Portal Description
https://www.geeksforgeeks.org/software-engineering-introduct Software engineering tutorials from
1
ion-to-software-engineering/ Geeksforgeeks
https://www.tutorialspoint.com/software_engineering/index.ht
2 Software Engineering Tutorials
m
3 https://www.sei.cmu.edu/ Software Engineering Institute
4 https://www.youtube.com/watch?v=WjwEh15M5Rw Agile Methodology
Software Design -DFDs, Class
5 https://app.diagrams.net/
Diagrams, Use Case Diagrams
Note :

Teachers are requested to check the creative common license status/financial implications of the suggested
online educational resources before use by the students

MSBTE Approval Dt. 24/02/2025 Semester - 5, K Scheme

Page 6/6