15.09.

2022

V Semester
SOFTWARE ENGINEERING
Course Code 21CB51 CIE Marks 50
Teaching Hours/Week (L:T:P:S) 2:2:0:0 SEE Marks 50
Total Hours of Pedagogy 40 Total Marks 100
Credits 03 Exam Hours 03
Course Learning Objectives
CLO 1. Identify ethical and professional issues and explain why they are of concern to software engineers.
CLO 2. Recognize the importance of software maintenance and describe the intricacies involved in
software evolution.
CLO 3. Apply estimation techniques, schedule project activities and compute pricing.
CLO 4. Identify software quality parameters and quantify software using measurements and metrics.
CLO 5. Recognize the need for agile software development, describe agile methods, apply agile practices
and plan for agility.
Teaching-Learning Process (General Instructions)

These are sample Strategies, which teachers can use to accelerate the attainment of the various course
outcomes.
1. Lecturer method (L) need not to be only a traditional lecture method, but alternative
effective teaching methods could be adopted to attain the outcomes.
2. Use of Video/Animation to explain functioning of various concepts.
3. Encourage collaborative (Group Learning) Learning in the class.
4. Ask at least three HOT (Higher order Thinking) questions in the class, which promotes
critical thinking.
5. Adopt Problem Based Learning (PBL), which fosters students’ Analytical skills, develop
design thinking skills such as the ability to design, evaluate, generalize, and analyze
information rather than simply recall it.
6. Introduce Topics in manifold representations.
7. Show the different ways to solve the same problem with different circuits/logic and
encourage the students to come up with their own creative ways to solve them.
8. Discuss how every concept can be applied to the real world - and when that's possible, it
helps improve the students' understanding.
Module-1
Introduction: Software Crisis, Need for Software Engineering. Professional Software Development,
Software Engineering Ethics. Case Studies. Software Processes: Models: Waterfall Model, Incremental
Model and Spiral Model, Process activities. Requirements Engineering: Requirements Engineering
Processes. Requirements Elicitation and Analysis, Functional and non-functional requirements. The
software Requirements Document, Requirements Specification, Requirements validation, Requirements
Management.
15.09.2022

Teaching-Learning Process Chalk and board, Active Learning, Problem based learning
Module-2
System Models: Context models, Interaction models, Structural models, Behavioral models, Model-driven
engineering. Design and Implementation: Introduction to RUP, Design Principles, Object-oriented design
using the UML, Design patterns, Implementation issues, Open source development.

Teaching-Learning Process Chalk and board, Active Learning, Demonstration

Module-3
Software Testing: Development testing, Test-driven development, Release testing, User testing, Test
Automation. Software Evolution: Evolution processes, Program evolution dynamics, Software
maintenance, Legacy system management
Teaching-Learning Process Chalk and board, Active Learning, Demonstration
Module-4
Project management: Risk management, Managing People, Teamwork. Project Planning: Software
pricing, Plan-driven development, Project scheduling: Estimation techniques, Quality management:
Software quality, Reviews and inspections, Software measurement and metrics, Software standards

Teaching-Learning Process Chalk and board, Active Learning, Demonstration

Module-5
Agile Software Development: Coping with Change, The Agile Manifesto: Values and Principles. Agile
methods: SCRUM (Ref “The SCRUM Primer, Ver 2.0”) and Extreme Programming. Plan-driven and agile
development. Agile project management, Scaling agile methods.
15.09.2022

Teaching-Learning Process Chalk and board, Active Learning, Demonstration

Course Outcomes
At the end of the course the student will be able to:
CO 1. Design a software system, component, or process to meet desired needs within
realistic constraints.
CO 2. Assess professional and ethical responsibility
CO 3.Function on multi-disciplinary teams
CO 4. Use the techniques, skills, and modern engineering tools necessary for
engineering practice
CO 5. Analyze, design, implement, verify, validate, implement, apply, and maintain
software systems or parts of software systems
Assessment Details (both CIE and SEE)
The weightage of Continuous Internal Evaluation (CIE) is 50% and for Semester End Exam (SEE) is 50%.
The minimum passing mark for the CIE is 40% of the maximum marks (20 marks). A student shall be
deemed to have satisfied the academic requirements and earned the credits allotted to each subject/
course if the student secures not less than 35% (18 Marks out of 50) in the semester-end examination
(SEE), and a minimum of 40% (40 marks out of 100) in the sum total of the CIE (Continuous Internal
Evaluation) and SEE (Semester End Examination) taken together
Continuous Internal Evaluation:
Three Unit Tests each of 20 Marks (duration 01 hour)
1. First test at the end of 5th week of the semester
2. Second test at the end of the 10th week of the semester
3. Third test at the end of the 15th week of the semester
Two assignments each of 10 Marks
4. First assignment at the end of 4th week of the semester
5. Second assignment at the end of 9th week of the semester
Group discussion/Seminar/quiz any one of three suitably planned to attain the COs and POs for 20
Marks (duration 01 hours)
6. At the end of the 13th week of the semester
The sum of three tests, two assignments, and quiz/seminar/group discussion will be out of 100 marks
and will be scaled down to 50 marks
(to have less stressed CIE, the portion of the syllabus should not be common /repeated for any of the
methods of the CIE. Each method of CIE should have a different syllabus portion of the course).
CIE methods /question paper has to be designed to attain the different levels of Bloom’s taxonomy
as per the outcome defined for the course.
Semester End Examination:
Theory SEE will be conducted by University as per the scheduled timetable, with common question
papers for the subject (duration 03 hours)
1. The question paper will have ten questions. Each question is set for 20 marks.
2. There will be 2 questions from each module. Each of the two questions under a module (with a
maximum of 3 sub-questions), should have a mix of topics under that module.
The students have to answer 5 full questions, selecting one full question from each module. Marks scored
out of 100 shall be reduced proportionally to 50 marks
Suggested Learning Resources:
Textbooks
1. Ian Sommerville: Software Engineering, 9th Edition, Pearson Education, 2012.
Reference Books:
1. Roger S. Pressman, “Software Engineering-A Practitioners approach”, Tata McGraw Hil, 7th
Edition
2. Pankaj Jalote: An Integrated Approach to Software Engineering, Wiley India.
15.09.2022

Weblinks and Video Lectures (e-Resources):

1. https://onlinecourses.nptel.ac.in/noc20_cs68/preview
2. https://www.youtube.com/watch?v=WxkP5KR_Emk&list=PLrjkTql3jnm9b5nr-
ggx7Pt1G4UAHeFlJ
3. http://elearning.vtu.ac.in/econtent/CSE.php
4. http://elearning.vtu.ac.in/econtent/courses/video/CSE/15CS42.html
5. https://nptel.ac.in/courses/128/106/128106012/ (DevOps)
Activity Based Learning (Suggested Activities in Class)/ Practical Based learning
Case study, Field visit