7/25/25, 5:21 PM 315332-SOFTWARE ENGINEERING AND TESTING

Page 1/9
7/25/25, 5:21 PM 315332-SOFTWARE ENGINEERING AND TESTING
25-07-2025 05:21:16 PM

SOFTWARE ENGINEERING AND TESTING Course Code : 315332

Programme Name/s : Information Technology
Programme Code : IF
Semester : Fifth
Course Title : SOFTWARE ENGINEERING AND TESTING
Course Code : 315332

I. RATIONALE
Software engineering plays a pivotal role in addressing complex problems and improving efficiency to build
software product. This course focuses on providing a structured framework by understanding and applying the
working knowledge of the principles, techniques, and practices for estimation, designing, testing and quality
management of software development projects. It enables students to blend the domain specific knowledge with the
programming skills to get quality software products.

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 - Identify relevant software process model for software development.

CO2 - Use appropriate principles of software modeling to create data design.
CO3 - Apply project management techniques in software development.
CO4 - Apply different software testing types to ensure the quality of software product.
CO5 - Identify defect to improve the overall quality of the software using automated testing tools.

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
315332 ENGINEERING SET DSC 4 - 4 1 9 3 3 30 70 100 40 25 10 25@ 10 25 10 175
AND TESTING

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

Page 2/9
7/25/25, 5:21 PM 315332-SOFTWARE ENGINEERING AND TESTING
25-07-2025 05:21:16 PM

SOFTWARE ENGINEERING AND TESTING Course Code : 315332

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.

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.
Unit - I Basics of Software Engineering
1.1 Software, software engineering as layered
TLO 1.1 Explain different types
approach, characteristics of software, types of
and characteristics of software.
software
TLO 1.2 Describe software
1.2 Software development framework: Software
engineering layered technology
generic process framework activities and umbrella
and process framework.
activities
TLO 1.3 State software
1.3 Software engineering core principles, Presentations
engineering principles for
1 communication practices, planning practices, Chalk-Board
requirement engineering.
modelling practices, construction practices, software Videos
TLO 1.4 Select software process
deployment practices
model for the given problem
1.4 Prescriptive process models: Waterfall model,
statement.
incremental model, RAD model, prototyping model,
TLO 1.5 Apply agile
spiral model
development process with
1.5 Agile software development: Agile process, and
justification.
its importance, extreme programming, scrum
1.6 Selection criteria for software process model

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

Page 3/9
7/25/25, 5:21 PM 315332-SOFTWARE ENGINEERING AND TESTING
25-07-2025 05:21:16 PM

SOFTWARE ENGINEERING AND TESTING Course Code : 315332

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 2.1 Determine requirement
engineering tasks in the given Unit - II Software Requirement, Modeling and
problem. Design
TLO 2.2 Prepare use case 2.1 Requirement engineering: Requirement
diagram for given scenario. engineering task, types of requirement, developing
TLO 2.3 Prepare SRS for the use-case Presentations
given problem. 2.2 SRS (Software Requirements Specifications): Chalk-Board
2 TLO 2.4 Convert analysis model Need of SRS, format and it's characteristics Problem Based
into requirement model. 2.3 Translating requirement model into design model Learning
TLO 2.5 Apply the specified 2.4 Design modelling: Fundamental design concepts Video
design feature for requirements - abstraction, information hiding, patterns,
software modeling. modularity, concurrency, verification, aesthetics
TLO 2.6 Represent the specified 2.5 Design notations: Data flow diagram (DFD),
problem in the given design structured flowcharts
notation.
TLO 3.1 Explain 4 P's of
management spectrum.
TLO 3.2 Estimate the size of the
Unit - III Software Project Management
software product using the given
3.1 The management spectrum- 4P's
method.
3.2 Metrics for size estimation: Line of code (LoC),
TLO 3.3 Evaluate the cost of the Presentations
function points(FP)
given software using COCOMO Chalk-Board
3.3 Project cost estimation using COCOMO
3 model. Problem Based
(Constructive Cost Model), COCOMO II
TLO 3.4 Describe the RMMM Learning
3.4 Define risk, types of risk, RMMM strategy
strategy for the given problem. Video
3.5 Project scheduling: Basic principle, scheduling
TLO 3.5 Use various scheduling
techniques - CPM, PERT
techniques for the given project.
3.6 Project tracking: Timeline charts, Gantt charts
TLO 3.6 Prepare the Timeline
chart / Gantt chart to track
progress of the given project.
TLO 4.1 State the importance of
software testing.
TLO 4.2 Identify errors and bugs
Unit - IV Basics of Software Testing
in the program.
4.1 Software testing, objective of testing, software
TLO 4.3 Prepare test case for the
testing life cycle (STLC)
application.
4.2 Failure, fault, error, defect, bug terminology
TLO 4.4 Identify the entry and
4.3 Test case, when to start and stop testing
exit criteria for the given test
4.4 Quality assurance, quality control and Presentations
application.
4 verification - validation, Quality evaluation Chalk-Board
TLO 4.5 Describe features of the
standards: Six sigma, CMMI levels Videos
given software quality evaluation
4.5 Static and dynamic testing
standard.
4.6 The box approaches: Compare white box testing,
TLO 4.6 Explain V model for the
black box testing
given application.
4.7 Levels of testing: Unit testing, integration
TLO 4.7 Describe features of the
testing, system testing, acceptance testing
given testing method.
TLO 4.8 Apply specified testing
levels for the given application.

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

Page 4/9
7/25/25, 5:21 PM 315332-SOFTWARE ENGINEERING AND TESTING
25-07-2025 05:21:16 PM

SOFTWARE ENGINEERING AND TESTING Course Code : 315332

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 5.1 Prepare test plan for the
given application.
TLO 5.2 Identify the resource
Unit - V Test and Defect Management
requirement for test
5.1 Test planning: Preparing a test plan
infrastructure management.
5.2 Test management: Test infrastructure
TLO 5.3 Prepare test report of
management
executed test cases for given Presentations
5.3 Test reporting: Executing test cases, preparing
application. Chalk-Board
test summary report
5 TLO 5.4 Apply defect life cycle. Problem Based
5.4 Definition and types of defect, defect life cycle,
TLO 5.5 Prepare defect report Learning
defect template
for identified defect for AUT. Video
5.5 Comparison of manual testing and automation
TLO 5.6 Compare automation
testing
and manual testing based on
5.6 Metrics and measurement: Types of metrics -
various parameters.
product metrics and process metrics
TLO 5.7 Describe metrics and
measurement for the given
application.

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

Laboratory Experiment /
Practical / Tutorial / Laboratory Learning Outcome Sr Number Relevant
Practical Titles / Tutorial
(LLO) No of hrs. COs
Titles
*Problem statement to define
LLO 1.1 Use any software tool to Write problem
1 the project title with bounded 2 CO1
statement and identify scope of the project.
scope of the software project
LLO 2.1 Select relevant process model to define
activities and related tasks set for assigned software *Process model to define
2 2 CO1
project like Library Management System (Teacher can activities and related tasks set
assign different projects in a group).
LLO 3.1 Gather application specific requirements for
assimilate into RE (Requirements engineering) model. *Software Requirement
3 2 CO2
LLO 3.2 Prepare SRS (Software Requirement Software) Specification (SRS)
document.
LLO 4.1 Write use cases for different user scenarios.
LLO 4.2 Draw use case diagram for different user 4 *Use-case diagram 2 CO2
scenarios using any tool.
Software Design tools :
LLO 5.1 Draw the Activity diagram to represent the
flow from one activity to another activity using any tool. 5 a) Activity diagram 2 CO2
LLO 5.2 Design Decision table using any tool.
b) Decision table
LLO 6.1 Draw data flow diagram: DFD 0 Level, DFD 1
Level, DFD 2 Level for the software project using any 6 *Data Flow Diagram 2 CO2
tool.

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

Page 5/9
7/25/25, 5:21 PM 315332-SOFTWARE ENGINEERING AND TESTING
25-07-2025 05:21:16 PM

SOFTWARE ENGINEERING AND TESTING Course Code : 315332

Laboratory Experiment /
Practical / Tutorial / Laboratory Learning Outcome Sr Number Relevant
Practical Titles / Tutorial
(LLO) No of hrs. COs
Titles
LLO 7.1 Draw class diagram for the software project
using any tool.
LLO 7.2 Draw Sequence diagram for the software
7 UML Diagrams 2 CO2
project using any tool.
LLO 7.3 Draw Collaboration diagram for the software
project using any tool.
LLO 8.1 Estimate size of the project using function *Function point metric for
8 2 CO3
point metric for the software project using any tool. size estimation
LLO 9.1 Estimate cost of the project using COCOMO *COCOMO (Constructive
(Constructive Cost Model)/COCOMO II approach for 9 Cost Model) /COCOMO II 2 CO3
the software project using any tool. for cost estimation
LLO 10.1 Identify risk involved in the project. RMMM (RMMM-Risk
LLO 10.2 Prepare RMMM(Risk Management, 10 Management, Mitigation and 2 CO3
Mitigation and Monitoring) Plan. Monitoring) plan
CPM (Critical Path Method) /
LLO 11.1 Use CPM (Critical Path Method) / PERT
PERT (Programme
(Programme Evaluation and Review Technique) for 11 2 CO3
Evaluation and Review
software project scheduling.
Technique).
LLO 12.1 Prepare Timeline charts / Gantt charts to track *Timeline charts / Gantt
12 2 CO3
the progress of the software project using any tool. charts
LLO 13.1 Design test cases w.r.t. functional testing for *Test cases for Functional
13 2 CO4
the software project. Testing
LLO 14.1 Design test cases w.r.t. Control and decision
Test cases for Control and
making statement for the software project 1) For... Loop 14 2 CO4
decision making statements
2) Switch...case 3) Do... While 4) If...else
LLO 15.1 Design test cases for Web Page Testing for Test cases for Web
15 2 CO4
any Web Site. Application
LLO 16.1 Design test cases for e-commerce (Flipkart,
16 *Test cases for GUI Testing 2 CO4
Amazon) login form with respect to GUI testing.
*Test plan for a standalone
LLO 17.1 Prepare test plan for a standalone application. 17 2 CO5
application
LLO 18.1 Prepare test plan for web application like any
18 Test plan for web Application 2 CO5
Chatting Application.
LLO 19.1 Prepare defect report after executing test cases
19 *Defect report 2 CO5
for login functionality.
LLO 20.1 Execute test cases for e-commerce application
(Flipkart, Amazon) login form using an Automation 20 Test cases for automation tool 2 CO5
Tool.
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)

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

Page 6/9
7/25/25, 5:21 PM 315332-SOFTWARE ENGINEERING AND TESTING
25-07-2025 05:21:16 PM

SOFTWARE ENGINEERING AND TESTING Course Code : 315332

Micro project

Visit any medical shop, gather information about purchasing and selling medicines, maintaining their inventory,
generating sales invoices and generating reminders of expiry date about medicines. Write the Functional and non-
functional requirements for the medical shop management system.
Visit your Institute library, Collect the functional requirements for a Library Management System and estimate cost
and size of the project.
Visit any grocery shop, collect requirements from shop keeper and prepare SRS document.

Assignment

Estimate size of software using any tool and risk involved in any food delivery system.
Estimate cost of software using any tool and risk involved in the Hotel management system.
Prepare test plan and defect report for calculator.

Other

Use Infosys Springboard or any MOOC's platform to complete any one course related to Software Engineering and
Testing.
Discuss paper titled "Case Study Based Software Engineering Project Development: State of Art" reference link:
https://arxiv.org/pdf/1306.2502.

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

Relevant LLO
Sr.No Equipment Name with Broad Specifications
Number
1 Software Project Management Tools: open source Software such as Jira 1,2,3,10,17,18,19
2 Spreadsheet Package 13,14,15,16
Software Tools : SmartDraw / Draw.io / TINY TOOLS / STRS COCOMO / any
3 4,5,6,7,8,9,11,12
other
4 Hardware: Personal computer, (i5-i7 preferable), RAM minimum 4 GB All
5 Operating system: Windows 10/Windows 11/ Ubuntu or any other 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 Basics of Software Engineering CO1 6 2 6 4 12
MSBTE Approval Dt. 24/02/2025 Semester - 5, K Scheme
Page 7/9
7/25/25, 5:21 PM 315332-SOFTWARE ENGINEERING AND TESTING
25-07-2025 05:21:16 PM

SOFTWARE ENGINEERING AND TESTING Course Code : 315332

Aligned Learning R- U- A- Total
Sr.No Unit Unit Title
COs Hours Level Level Level Marks
Software Requirement, Modeling and
2 II CO2 10 4 4 8 16
Design
3 III Software Project Management CO3 10 2 4 10 16
4 IV Basics of Software Testing CO4 8 2 4 8 14
5 V Test and Defect Management CO5 6 2 4 6 12
Grand Total 40 12 22 36 70

X. ASSESSMENT METHODOLOGIES/TOOLS

Formative assessment (Assessment for Learning)

For theory two offline unit tests of 30 marks and average of two unit test marks will be considered for out of 30
marks.
For formative assessment of laboratory learning 25 marks.
Each practical will be assessed considering 60% weightage to process, 40% weightage to product.

Summative Assessment (Assessment of Learning)

End semester assessment is of 70 marks.

End semester examination if of 25 marks, lab performance, viva voce

XI. SUGGESTED COS - POS MATRIX FORM

Programme
Specific
Programme Outcomes (POs)
Outcomes*
(PSOs)
Course PO-5
Outcomes PO-1 Basic Engineering
PO-3 PO-7
(COs) 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 2 2 2 - - -
CO3 1 2 2 3 - 2 1
CO4 2 2 3 3 1 2 1
CO5 2 2 3 3 1 1 1
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 & Software Engineering: A McGraw Hill Higher Education, New Delhi,
1
Bruce R. Maxim practitioner's approach (Ninth Edition) ISBN 93-5532-504-5

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

Page 8/9
7/25/25, 5:21 PM 315332-SOFTWARE ENGINEERING AND TESTING
25-07-2025 05:21:16 PM

SOFTWARE ENGINEERING AND TESTING Course Code : 315332

Sr.No Author Title Publisher with ISBN Number
Srinivasan Desikan, Software Testing: Principles PEARSON Publisher: Pearson India 2007,
2
Gopalaswamy Ramesh and Practices ISBN: 978-81-7758-121-8,
Software Engineering McGraw Hill Education New Delhi -2001,
3 Richard Fairly
Concepts ISBN-13: 9780074631218
Software Engineering: Oxford University Press, New Delhi ISBN
4 Deepak Jain
Principles and practices 9780195694840
Sams Publishing; 2nd edition, 2005 ISBN:
5 Ron Patton Software Testing
0672327988
Software Testing: Principles, Tata McGraw Hill Education, New Delhi.,
6 M. G. Limaye
Techniques and Tools 2009 ISBN 13: 9780070139909
Software Testing: Principles Oxford University Press Noida. ISBN:
7 Naresh Chauhan
and Practices 9780198061847
Cambridge University Press, Cambridge, 2021
8 Yogesh Singh Software Testing
ISBN: 9781107012967

XIII . LEARNING WEBSITES & PORTALS

Sr.No Link / Portal Description
1 www.tutorialspoint.com//software_engineering/ Software Engineering Tutorial
Software Engineering Institute
2 https://insights.sei.cmu.edu/library/
Digital Library
NPTEL course on Introduction to
3 https://nptel.ac.in/courses/106105087
Software Engineering
4 https://www.geeksforgeeks.org/software-testing-basics/ Software Testing Tutorial
Video tutorial on Software testing
5 https://www.youtube.com/watch?v=sO8eGL6SFsA&t=12304s
by Edureka
Video tutorial on Software testing
6 https://www.youtube.com/@softwaretestingmentor
by RCV Academy
https://infyspringboard.onwingspan.com/web/en/app/toc/lex_au Software engineering and testing
7
th_01384297011411353628269_shared/overview courses
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 9/9