(EstablishedunderthePresidencyUniversityAct,2013 of the KarnatakaAct41of2013) ACA-

[2022-23 EVEN/ WINTER SEMESTER]

COURSE HAND OUT [Revision 02 - Jan 2022]

SCHOOL: SOCSE&IS DEPT.:CSE DATEOFISSUE:16-02-2023

NAME OF THE PROGRAM: B. TECH

P.R.C. APPROVAL REF.: PU/AC-17/CSE/2021-2025/2021

SEMESTER/YEAR: II/I, VI/III

COURSE CODE & TITLE: CSE2014 & Software Engineering

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

CONTACT HOURS: 42 hours

COURSE INTRUCTOR INCHARGE: Dr. Mohammadi Akheela Khanum, Mr. Jerrin Joe Francis

COURSE INSTRUCTOR:

COURSE URL:

PROGRAM OUTCOMES:

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

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.

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, so cietal,
and environmental considerations.

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.

PO9: Individual and team work: Function effectively as an individual, and as a member or leader in diverse teams, and in
multidisciplinary settings.
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.

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.

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.

COURSE PREREQUISITES:
NIL
Topics include:
Type of Skill: Employability
Nature of the Course: Conceptual
COURSE OUTCOMES: On successful completion of the course the students shall be able to,

TABLE 1: COURSE OUTCOMES

CO CO Blooms Taxonomy Level/RBT

Number Level

CO1 Describe the Software Engineering principles, ethics Knowledge (Remember)

and process models

CO2 Identify the requirements, analysis and appropriate Comprehension (Understand)

design models for a given application

CO3 Understand the Agile Principles Knowledge (Remember)

CO4 Apply testing strategies for various levels of testing the Application (Apply)
software, and also apply appropriate planning,
scheduling, evaluation and maintenance principles
involved in software

MAPPING OF C.O. WITH P.O

CO
.
No PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO 10 PO 11 PO 12
CO M M
1
CO M H
2
CO M L M L
3
CO L M H L M
4
[H-HIGH , M- MODERATE, L-LOW]

COURSE CONTENT (SYLLABUS):

Module 1
Introduction to Software Engineering and Process Models (Knowledge level) 09 Hrs [Remember]
 Introduction: What is a software? Characteristics of Software, Types of software, Need for Software Engineering, Professional
Software Development, Software Engineering Ethics, Software Engineering Practice-Essence of Practice, General Principles
Software Development Life Cycle
Models: Waterfall Model – Classical Waterfall Model, Iterative Waterfall Model, Evolutionary model-Spiral, Prototype.
Module 2
Software Requirements, Analysis and Design (Comprehension level) 12 Hrs [Understand]
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 support in Software Life Cycle, Characteristics of CASE Tools, Architecture of a CASE
Environment.
Design: Design principles, Design concepts, Effective Modular Design-Functional dependence, Cohesion and Coupling.
Architectural design, Data Design-Data Modeling, Data Structures, Databases, and the Data Warehouse, Data Design at the
Component Level, Architectural Styles, User interface design.
Module 3
Agile Principles & Devops (Knowledge level) 09 Hrs [Remember]
Agile: 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 Level) 12 Hrs [Apply]
Software Testing-verification and validation, Test Strategies - White Box Testing, Black box Testing. Automation Tools for
Testing.
Software Quality Assurance-Elements of software quality assurance, SQA Tasks, Goals and Metrics, Software configuration
management- SCM process, SCM Tools (GitHub).
Maintenance- Characteristics of Software Maintenance, Software Reverse Engineering, Software Maintenance Process Models.

DELIVERY PROCEDURE (PEDAGOGY):

TABLE 3: SPECIAL DELIVERY METHOD/ PEDAGOGY PLANNED WITH TOPICS

S. No Lecture Subtopic as per Pedagogy title/ short Status
Number lesson Plan explanation of adopted
pedagogy
1 L9 SDLC models Group discussion
2 L20 UID Flip Classroom
3 L29 Git/GitHub Flip Classroom

TOOLS:
• Selenium
• Git/GitHub

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

Text Book

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

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

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

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

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

Web Links

1. LIBRARY - Presidency University

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

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

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

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: As per time table
5] All the notices related to this course will be posted in Teams Class.

COURSE SCHEDULE:

TABLE 4: COURSE BROAD SCHEDULE

Sl. ACTIVITY STARTING DATE CONCLUDING DATE TOTAL

No. NUMBEROF
PERIODS
01 Program Integration 1
Overview of the course
02 Module: 01 09
03 Module 02 12

04 Quiz1 15 mins

05 Course/Module Integration 1

06 MidTerm(CAT) 02 Hours

07 Module:03 09

08 Course/Module Integration 1

09 Assignment 1 week
10 Module :04 12
13 Assignment2 week
14 Quiz 2 15 mins
15 Program Integration 1
16 EndTerm As per CoE Date 3 Hours
Examination(FAT) NA
 TABLE 5: DETAILED COURSE SCHEDULE/ LESSON PLAN
Ses Lesson Topics Course Referenc
sio Title Outcom e
n e
no Numbe
r
L1 Course Program Integration,
Overview Details of the course
and
Learning Objectives
L2 Introducti What is a software? CO1 T1,R1
on Characteristics of
Software, Types of
software Need for
Software
Engineering,
Professional
Software
Development
L3 Software User Ethics, CO1 R1
Engineeri Developer Ethics,
ng Ethics
L4 Software Essence of Practice CO1 T1,R1
Engineeri
ng
Practice
L5 General Software CO1 T1,R1
Principles Development Life
Cycle Model
L6 Models: Classical Waterfall CO1 T1,R1
Waterfall Model
Model
L7 Waterfall Iterative Waterfall CO1 T1,R1
Model Model
L8 Evolution Spiral, Model CO1 T1,R1
ary model Prototype
L9 Evolution Prototype Model CO1 T1,R1
ary model
L10 Eliciting CO2 T1,R1
requirements,
Functional and non-
Functional
Requirem
ents requirements,
L11 Engineeri Software CO2 T1,R1
ng Requirements
Specification (SRS)
L12 Software CO2 T1,R1
Requirements
Specification (SRS)
L13 Requirement CO2 T1,R1
Analysis and
validation
L14 Require Introduction to Use CO2 T1,R1
ments Cases
modellin
 g

L15 Activity diagram and CO2 T1,R1

Swim Lane diagram

L16 CASE Characteristics of CO2 T1,R1

support in CASE Tools,
Software Architecture of a
Life Cycle CASE Environment.

L17 Design principles, CO2 T1,R1

Design concepts,
Effective Modular
Design
Design-Functional
dependence,
Cohesion and
Coupling.
L18 Architecture CO2 T1,R1
Design, Data
Design-Data
Modeling, Data
Structures,
Databases, and the
Data Warehouse,
L19 Data Design at the CO2 T1,R1
Component Level,
Architectural
Styles
L20 User interface CO2 T1,R1
design.
L21 Agile: Scrum Roles and CO3 T1,R1
activities
L22 Scaling CO3 T1,R1
L23 Sprint User Stories CO3 T1,R1
L24 Agile Agile estimation CO3 T1,R1
software techniques
L25 develop Product backlogs, CO3 T1,R1
ment
L26 methods Stake holder roles CO3 T1,R1
L27 Dynamic System CO3 T1,R1
Development
Method
L28 Devops: Introduction, CO3 T1,R1
definition
L29 history, tools. CO3 T1,R1

L30- Software verification and CO4 T2,R1

L35 Testing
validation, Test
Strategies - White
Box Testing, Black
box Testing.
Automation Tools
for Testing.
 L36- Software Elements of software CO4 T2,R1
L39 Quality quality assurance
Assuranc SQA Tasks, Goals CO4 T2,R1
e- and Metrics,
L40- SCM process, SCM CO4 T2,R1
L42
Tools (GitHub).
Maintenance- CO4 T2,R1
Characteristics of
Software
configur Software
ation Maintenance,
manage
Software Reverse
ment
Engineering,
Software
Maintenance Process
Models.

TABLE 6 ASSESSMENT SCHEDULE

S Assessment Contents Course Durati Mar weightage DAT

r type outcome on In ks 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 Module 2 CO2 1 Week 10 5%
1
4 Assignment Module 4 CO4 1 Week 10 5%
2
5 Mid Term Module 1 CO1 & 2 Hours 50 25%
&2 CO2
6 End Term Module1-4 CO1, 3 Hours 100 50% CoE
CO2, Date
CO3,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 OUTCO LEVEL
NO ME NO.

1 ABC Software limited developing 7.5 CO1 Understand

projects 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 7.5 CO1 Understand
wants 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 Understand
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 Understand
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 Understand
 Target set for course Outcome attainment:

TABLE 8 TARGET SET FOR ATTAINMENT OF EACH CO and ATTAINMENT ANALYSIS AFTER RESULTS

Sl. C.O. Course Outcomes Target set for Actual C.O. Remarks on
No No. attainment Attainment In attainment
in percentage Percentage &Measures to
enhance the
attainment
1 CO1 Describe the Software 70
Engineering principles,
ethics and process models
2 CO2 Identify the requirements, 65
analysis and appropriate
design models for a given
application
3 CO3 Understand the Agile 65
Principles
4 CO4 Apply an appropriate 60
planning, scheduling,
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.no.
Schedule Date Date

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: