(EstablishedunderthePresidencyUniversityAct,2013 of the KarnatakaAct41of2013) ACA-

[2023-24 ODD/ FALL SEMESTER]

COURSE PLAN

SCHOOL: SOCSE&IS DEPT.: CSE DATEOFISSUE: 28 AUGUST 2023

NAME OF THE PROGRAM: B. TECH

SEMESTER/YEAR : III/II

COURSE CODE & TITLE : CSE2014 & Software Engineering

COURSE CREDIT STRUCTURE (L-P-C): 3-0-3

CONTACT HOURS : 39 hours

COURSE INTRUCTOR INCHARGE : Dr.S.Pravinth Raja & Dr. Mohammed Shakir

COURSE INSTRUCTOR : Dr. Pamela Vinitha Eric, Dr. Mohammadi Akheela Khanum, Dr. Jerrin Joe
Francis, Dr.Srinivas Moshra , Mr. Sharon M, Mr.Jinesh VN, Ms.Kayalvizhi

COURSE URL : https://camu.in/index#/TeachingPlan

PROGRAM OUTCOMES:

PO1: Engineering knowledge: Apply the knowledge of mathematics, science, engineering fundamentals, and an engineering
specialization to the solution of complex engineering problems. [H]

PO2: Problem analysis: Identify, formulate, review research literature, and analyze complex engineering problems reaching
substantiated conclusions using first principles of mathematics, natural sciences, and engineering sciences. [M]

PO3: Design/development of solutions: Design solutions for complex engineering problems and design system components or
processes that meet the specified needs with appropriate consideration for the public health and safety, and the cultural, societal, and
environmental considerations. [H]

PO4: Conduct investigations of complex problems: Use research-based knowledge and research methods including design of experiments,
analysis and interpretation of data, and synthesis of the information to provide valid conclusions.

PO5: Modern tool usage: Create, select, and apply appropriate techniques, resources, and modern engineering and IT tools including
prediction and modeling to complex engineering activities with an understanding of the limitations.
PO6: The engineer and society: Apply reasoning informed by the contextual knowledge to assess societal, health, safety, legal and cultural
issues and the consequent responsibilities relevant to the professional engineering practice.

PO7: Environment and sustainability: Understand the impact of the professional engineering solutions in societal and environmental contexts,
and demonstrate the knowledge of, and need for sustainable development.

PO8: Ethics: Apply ethical principles and commit to professional ethics and responsibilities and norms of the engineering practice.
[M]

PO9: Individual and team work: Function effectively as an individual, and as a member or leader in diverse teams, and in
multidisciplinary settings. [M]
PO10: Communication: Communicate effectively on complex engineering activities with the engineering community and with society
at large, such as, being able to comprehend and write effective reports and design documentation, make effective presentations, and
give and receive clear instructions. [M]

PO11: Project management and finance: Demonstrate knowledge and understanding of the engineering and management principles
and apply these to one’s own work, as a member and leader in a team, to manage projects and in multidisciplinary environments. [H]

PO12: Life-long learning: Recognize the need for and have the preparation and ability to engage in independent and life-long learning in the
broadest context of technological change.

PROGRAMME SPECIFIC OUTCOMES

PSO1 [Problem Analysis]: Identify, formulate, research literature, and analyze complex engineering problems
related to Software Engineering principles and practices, Programming and Computing technologies reaching
substantiated conclusions using first principles of mathematics, natural sciences, and engineering sciences.

PSO2 [ Design/development of Solutions]: Design solutions for complex engineering problems related to Software
Engineering principles and practices, Programming and Computing technologies and design system components or
processes that meet the specified needs with appropriate consideration for the public health and safety, and the cultural,
societal, and environmental considerations.

PSO3 [Modern Tool usage] : Create, select, and apply appropriate techniques, resources, and modern engineering
and IT tools including prediction and modelling to complex engineering activities related to Software Engineering
principles and practices, Programming and Computing technologies with an understanding of the limitations.

COURSE PREREQUISITES:

NIL

COURSE DESCRIPTION:
The objective of this course is to provide an in-depth knowledge of the fundamental concepts of Software Engineering
process and principles. The course covers software requirement engineering processes, system analysis, design,
implementation and testing aspects of software system development. The course covers software quality, configuration
management and maintenance.

Course Objectives: The objective of the course is to familiarize the learners with the concepts of Software
Engineering and attain Skill Development through Participative Learning techniques.

TABLE 2b: CO PSO Mapping ARTICULATION MATRIX

CO. No. PSO1 PSO2 PSO3

CO1 L
CO2 H
CO3 H
CO4 H
 COURSE OUTCOMES: On successful completion of the course the students shall be able to,

CO CO Blooms Taxonomy Level

Number

CO1 Describe the Software Engineering principles, ethics and process Remember
models

CO2 Identify the requirements, analysis and appropriate design models Understand
for a given application

CO3 Understand the Agile Principles Remember

CO4 Apply an appropriate planning, scheduling, evaluation and Application

maintenance principles involved in software

MAPPING OF C.O. WITH P.O

TABLE 2: CO PO Mapping ARTICULATION MATRIX [H-

CO.
PO PO PO
No
PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO 10 11 12 13
CO1 M M

CO2 M H

CO3 M L M L

CO4 L M M L M
HIGH M- MODERATE , L-LOW ]

COURSE CONTENT (SYLLABUS):

Module 1
Introduction to Software Engineering and Process Models (Remember) 09 Hours
Introduction:
Software, Need for Software Engineering, Software Engineering Ethics, Essence of Software Engineering Practice, Software
Development Life Cycle Model, Software Process Models: Waterfall Model, Evolutionary model, Incremental model, RAD
model, A Process Framework – The Capability Maturity Model Integration (CMMI)
Module 2
Software Requirements, Analysis and Design (Understand) 11 Hours
Requirements Engineering: Eliciting requirements, Functional and non- Functional requirements, Software Requirements
Specification (SRS), Requirement Analysis and validation. Requirements modelling- Introduction to Use Cases, Activity
diagram and Swim Lane diagram. CASE- Characteristics of CASE Tools, Architecture of a CASE Environment.
Design: Design concepts, Architectural design, Component based design, User interface design.
Module 3
Agile Principles & Devops (Remember) 09 Hours
Scrum Roles and activities, Sprint Agile software development methods - Scaling, User Stories, Agile estimation techniques,
Product backlogs, Stake holder roles, Dynamic System Development Method.
Devops: Introduction, definition, history, tools.
Module 4 Software Testing and Maintenance (Application) 12 Hours
Software Testing-verification and validation, Test Strategies - White Box Testing, Black box Testing. Automation
Tools for Testing, Regression Testing, Boundary Value Analysis. Software configuration management- SCM process,
tools. Maintenance- Reverse Engineering, Software Maintenance Process Models, Software Cost Estimation, Risk
Managements
DELIVERY PROCEDURE (PEDAGOGY):

TABLE 3: SPECIAL DELIVERY METHOD/ PEDAGOGY PLANNED WITH TOPICS

S. No Lecture Subtopic as per lesson Plan Pedagogy title/ short ** At end of
Number explanation of adopted semester please
pedagogy update whether
activity was done
1 L11 Construction of SRS document Student Centric
based on a problem statement Methods : Group
(functional and non-functional based
requirements).
2 L14 Requirement Feasibility study, Web Self-learning topics
App design.
3 L16 Selenium Tools, CASE Tools Book Review/Article
Review
4 L16 Automation Tools, SCM Tools-GitHub. Book Review/Article
Review

REFERENCE MATERIALS: Textbooks, Reference books, any other resources, like webpages.

SPECIFIC GUIDELINES TO STUDENTS:

TOOLS:
 Selenium
 Git/GitHub

Text Book

1] Roger S. Pressman, “Software Engineering – A Practitioner’s Approach”, VII Edition, McGraw-Hill, 2017.

2] Bob Hughes, Mike Cotterell, Rajib Mall, “Software Project Management”, VI Edition, McGraw-Hill, 2018.

References

1] Rajib Mall, “Fundamentals of Software Engineering”, VI Edition, PHI learning private limited, 2015.

2] Ian Sommerville, “Software Engineering”, IX Edition, Pearson Education Asia, 2011.

3] Agile Software Development Principles, Patterns and Practices.1st Edition, Wiley, 2002

Web Links

1. NPTEL link on SE- https://www.youtube.com/watch?v=w0LQh0vCeqI

2. Github - https://www.youtube.com/watch?v=PQsJR8ci3J0

3. DevOps- https://www.youtube.com/watch?v=hQcFE0RD0cQ

PU Library Link : https://puniversity.knimbus.com/user#/home

 Or
: http://182.72.188.193/

GUIDELINES TO STUDENTS:

1] Be regular to the classes.

2] Refer Online materials, YouTube videos on Software Engineering
3] Practice UML based modeling using “Software Engineering Virtual Lab” made available by IIT-
Kharaghpur (URL – https://vlabs.iitkgp.ernet.in/se/)
4] Chamber consultation hour: Will be announced in the class.
5] All the notices related to this course will be posted in Teams Class.
COURSE SCHEDULE:

TABLE 4: COURSE BROAD SCHEDULE

Sl. ACTIVITY STARTING CONCLUDING TOTAL

No. DATE DATE NUMBEROF PERIODS
01 Program 28 August 2023 28 August 2023 1
Integration
Overview of the
course
02 Module: 01 28.08.2023 15.09.2023 09
03 Module 02 10.09.2023 13.10.2023 11
04 Quiz1 14.10.2023 15 mins
05 Course/Module 13.10.10.2023 1
Integration
06 Mid Term (CAT) 16.10.2023 20.10.2023 02 Hours
07 Module:03 01.11.2023 25.11.2023 09
08 Course/Module 03.11.2023 1
Integration
09 Assignment 1 03.11.2023 week
10 Module :04 28.11.2023 19.12.2023 12
13 Assignment2 11.12.2023 week
14 Quiz 2 20.12.2023 15 mins
15 Program 21.12.2023 1
Integration
16 EndTerm As per CoE 3 Hours
Examination(FAT Date NA
)
TABLE 4 COURSE BROAD SCHEDULE

Sl. Session Lesson Title Topics Course Delivery Reference

No no Outcom Mode
e
Numbe
r
MODULE-1: Introduction to Software Engineering and Process Models
1 L1 Course Program Integration, PPT
Overview Details of the course
and
Learning Objectives
2 L2 Introduction What is a software? CO Chalk and T1,R1
 Characteristics of 1 talk, PPT
Software, Types of
software Need for
Software Engineering,
Professional Software
Development
3 L3 Software User Ethics, Developer CO Chalk and R1
Engineering Ethics, 1 talk,PPT
Ethics
4 L4 Software Essence of Practice CO Chalk and T1,R1
Engineering 1 talk, PPT
Practice
5 L5 General Software Development CO Chalk and T1,R1
Principles Life Cycle Model 1 talk, PPT
6 L6 Models: Classical Waterfall CO Chalk and T1,R1
Waterfall Model 1 talk, PPT
Model
7 L7 Waterfall Iterative Waterfall CO Chalk and T1,R1
Model Model 1 talk, PPT
8 L8 Evolutionary Spiral, Model Prototype CO Chalk and T1,R1
model 1 talk, PPT
9 L9 Evolutionary Prototype Model CO Chalk and T1,R1
model 1 talk, PPT
Module - 1 Completed

Module-2: Software Requirements, Analysis and Design

7 L10 Eliciting requirements, CO Chalk and T1,R1

2 talk, PPT
Functional and non-
Functional
Requirement requirements,
s
8 L11 Software Requirements CO Chalk and T1,R1
Engineering
Specification (SRS) 2 talk, PPT

9 L12 Software Requirements CO Chalk and T1,R1

Specification (SRS) 2 talk, PPT

10 L13 Requirement Analysis CO Chalk and T1,R1

and validation 2 talk, PPT

11 L14 Requiremen Introduction to Use CO Chalk and T1,R1

ts modelling Cases 2 talk, PPT

12 L15 Activity diagram and CO Chalk and T1,R1

Swim Lane diagram 2 talk, PPT

13 L16 CASE Characteristics of CO Chalk and T1,R1

2 talk, PPT
support in CASE Tools,
Software Life Architecture of a CASE
Cycle Environment.
14 L17 Design concepts CO Chalk and T1,R1
2 talk, PPT
15 L18 Architectural design CO Chalk and T1,R1
Design 2 talk, PPT
16 L19 Component based CO Chalk and T1,R1
design 2 talk, PPT
17 L20 User interface design. CO Chalk and T1,R1
2 talk, PPT
Module 2 Completed

Module 3: Agile Principles &Devops (Knowledge level) 09 Hours

18 L21 Agile: Scrum Roles and CO Chalk and T1,R1

3 talk, PPT
activities
19 L22 Scaling CO Chalk and T1,R1
3 talk, PPT
20 L23 Sprint Agile User Stories CO Chalk and T1,R1
software 3 talk, PPT
21 L24 developmen Agile estimation CO Chalk and T1,R1
t methods techniques 3 talk, PPT
22 L25 Product backlogs, CO Chalk and T1,R1
3 talk, PPT
23 L26 Stake holder roles CO Chalk and T1,R1
3 talk, PPT
24 L27 Dynamic System CO Chalk and T1,R1
Development Method 3 talk, PPT
25 L28 Devops: Introduction, definition CO Chalk and T1,R1
3 talk, PPT
26 L29 history, tools. CO Chalk and T1,R1
3 talk, PPT
Module 3 Completed

Module 4: Software Testing and Maintenance (Application Level) 12 Hours

27 L30-L35 Software verification and CO Chalk and T2,R1

Testing 4 talk, PPT
validation, Test
Strategies - White Box
Testing, Black box
Testing. Automation
Tools for Testing.
28 L36-L39 Software Elements of software CO Chalk and T2,R1
Quality quality assurance 4 talk, PPT
29 Assurance- SQA Tasks, Goals and CO Chalk and T2,R1
Metrics, 4 talk, PPT
30 L40-L41 SCM process, SCM CO Chalk and T2,R1
4 talk, PPT
Tools (GitHub).
31 Maintenance- CO Chalk and T2,R1
4 talk, PPT
Characteristics of
Software
configuratio Software Maintenance,
n Software Reverse
management
Engineering, Software
 Maintenance Process
Models.

Topics Relevant to “Skill Development: Balck box Testing, White box Testing, Automated Testing for Skill development
through Participative Learning Techniques. This is attained through assessment mentioned in the course handout

ASSESSMENT SCHEDULE:

S Assessment type Contents Course Durati Ma weightag DATE

r outcome on In rks e
. Number Hours
n
o
1 Quiz 1 Module 1 CO1 15 Mins 15 7.5%
2 Quiz 2 Module 3 CO3 15 Mins 15 7.5%
3 Assignment 1 Module 2 CO2 1 Week 10 5%
4 Assignment 2 Module 4 CO4 1 Week 10 5%
5 Mid Term Module 1 & 2 CO1 & CO2 2 Hours 50 25%
6 End Term Module1-4 CO1,CO2,C 3 Hours 100 50% CoE Date
O3,CO4

Course Clearance Criteria will be as per Program Regulations.

MAKEUP EXAM POLICY:

AS PER ACADEMIC REGULATIONS OF THE UNIVERSITY

CONTACT TIMINGS IN THE CHAMBER FOR ANY DISCUSSIONS:

Will be as per time table .

TABLE7: SAMPLE THOUGHT PROVOKING QUESTIONS

QUESTION MARKS COURSE BLOOM’S

SL OUTCOME LEVEL
NO NO.

1 ABC Software limited developing projects 7.5 CO1 2

based on the customer’s requirement. The
customer has
provided well defined requirements to the
developer. Developer has confusion to decide
waterfall
model or Iterative water fall model. Help the
developer by comparing both models and
justify which
model will be more suitable here
2 Jaslin Surgical manufacturing company wants 7.5 CO1 2
 to design a surgical scissor for Apollo
Hospital. Help
the surgical company to choose a process
model and explain how it will be helpful in the
effective
development process of designing and
developing a new surgical scissor.
3 “SRS document describes all aspects of a 7.5 CO1 2
software to be built”. Justify the above
statement and develop
a sample SRS document.
4 Imagine you are designing the use case 7.5 CO1 2
diagram for an online banking website. The
banking website
allows a customer to create a new savings
account. There are also options for requesting
loans and
starting a fixed deposit. Elaborate the above
system with suitable actors, and implement
use cases with
suitable extends and include relationships.
5 Explain the fundamental design concepts. 7.5 CO2 2

Target set for course Outcome attainment: (check)

TABLE 8: TARGET SET FOR ATTAINMENT OF EACH CO and ATTAINMENT ANALYSIS

AFTER RESULTS
Sl. No C.O. No. Course Outcomes Target set for attainment
in percentage
1 CO1 Describe the Software Engineering principles, 70
ethics and process models
2 CO2 Identify the requirements, analysis and appropriate 65
design models for a given application
3 CO3 Understand the Agile Principles 65

4 CO4 Apply an appropriate planning, scheduling, 60

evaluation and maintenance principles involved in
software

Signature of the course Instructor:

This course has been duly verified Approved by the D.A.C.

Signature of the Chairperson D.A.C.

Course Completion Remarks & Self-Assessment

Activity Scheduled Actual Remarks

As listed in the course Completion Completion
Sl.
Schedule Date Date
no.

Course Outcome Attainment:

Sl.No C.O. Course Outcomes Target set for ActualC.O. Remarkon attainment
No. attainment in AttainmentIn &Measures to
percentage Percentage enhancetheattainment

Name and signature of the Faculty member:

D.A.C. observation and approval: