MOHAMED SATHAK A J COLLEGE OF ENGINEERING, Chennai - 603103

LESSON PLAN - THEORY

Department of Information Technology
Name of the
Object Oriented Software Engineering Regulation 2021
Subject
Subject Code CCS356 Year / Sem III/VI
Course Objective
1.To understand Software Engineering Lifecycle Models
2.To Perform software requirements analysis
3.To gain knowledge of the System Analysis and Design concepts using UML
4.To understand software testing and maintenance approaches
5.To work on project management scheduling using DevOps

Course Outcome
1.Compare various Software Development Lifecycle Models
2.Evaluate project management approaches as well as cost and schedule estimation strategies.
3.Perform formal analysis on specifications.
4.Use UML diagrams for analysis and design.
5.Architect and design using architectural styles and design patterns, and test the system

Lesson Plan
T / R* Mode of Teaching (BB /
Periods Blooms Level (L1-
Sl. No. Topic(s) Required
PPT / NPTEL / MOOC /
L6)
CO PO
Book etc )
UNIT I-SOFTWARE PROCESS AND AGILE DEVELOPMENT
1 Introduction to Software Engineering, T1 1 BB L2 CO1 PO 1,12
2 Software Process T1 1 BB L2 CO1 PO 1,12
3 Perspective and Specialized Process Models T1 1 BB L2 CO1 PO 1,12
4 Specialized Process Models R1 1 BB L2 CO1 PO 1,12
5 Introduction to Agility R2 1 BB L2 CO1 PO 1,12
6 Agile process- T/R1 1 BB L2 CO1 PO 1,12
7 Extreme programming T1 1 BB L2 CO1 PO 1,12
8 XP Process T1 1 BB L2 CO1 PO 1,12
9 Case Study T1 1 BB L4 CO1 PO 1,12
Suggested Activity: Assignment / Case Studies / Tuorials/ Quiz / Mini Projects / Model Developed/others Planned if any
Evaluation method - Assignment
UNIT II - REQUIREMENTS ANALYSIS AND SPECIFICATION
13 Requirement analysis and specification T1/R2 1 BB L2,L3 CO2 PO3
14 Requirements gathering and analysis T1/R2 1 BB L2,L3 CO2 PO3
15 Software Requirement Specification T1/R2 1 BB L2,L3 CO2 PO3
16 Formal system specification T1/R2 1 BB L6 CO2 PO3
17 Finite State Machines T1/R2 1 BB L2,L6 CO2 PO3
18 Petrinets ,Object modelling using UML, T1 1 BB L2,L6 CO2 PO3
19 Use case Model , Class diagrams, T1 1 BB L2,L6 CO2 PO3
20 Interaction diagrams,Activity diagrams T1 1 BB L2,L6 CO2 PO3
21 State chart diagrams T1 1 BB L2,L6 CO2 PO3
Suggested Activity: Assignment / Case Studies / Tuorials/ Quiz / Mini Projects / Model Developed/others Planned if any
Evaluation method -Assignment
UNIT III- SOFTWARE DESIGN
25 Software design and design process T1/R2 1 BB L6 CO3 PO3
26 Design concepts, Coupling,Cohesion T1/R2 1 BB L6 CO3 PO4
27 Functional independence T1/R2 1 BB L6 CO3 PO5
28 Design patterns T1/R2 1 BB L6 CO3 PO6
29 Model-view,controller and Publish-subscribe T1 1 BB L6 CO3 PO7
30 Adapter ,Command and Strategy T1 1 BB L6 CO3 PO8
31 Observer , Proxy , Façade and Architectural styles T1 1 BB L6 CO3 PO9
32 Layered ,Client Server , Tiered and Pipe and filter T1 1 BB L6 CO3 PO10
33 User interface design,Case Study. T1 1 BB L4 CO3 PO11
Suggested Activity: Assignment / Case Studies / Tuorials/ Quiz / Mini Projects / Model Developed/others Planned if any
Evaluation method -Quiz
UNIT IV-SOFTWARE TESTING AND MAINTENANCE
37 Testing ,Unit testing, T2 1 BB L2,L3 CO4 PO 5.6
38 Black box testing T2 1 BB L2,L3 CO4 PO 5.6
39 White box testing T2 1 BB L2,L3 CO4 PO 5.6
40 Integration and System testing T2 1 BB L2,L3 CO4 PO 5.6
41 Regression testing T2 1 BB L2,L3 CO4 PO 5.6
42 Debugging and Program analysis T2 1 BB L2,L3 CO4 PO 5.6
43 Symbolic execution T2 1 BB L2,L3 CO4 PO 5.6
44 Model Checking- T2 1 BB L2,L3 CO4 PO 5.6
45 Case Study T2 1 BB L4 CO4 PO 5.6
Suggested Activity: Assignment / Case Studies / Tuorials/ Quiz / Mini Projects / Model Developed/others Planned if any
Evaluation method
UNIT V- PROJECT MANAGEMENT
50 Software Project Management T1/T2 1 BB L2 CO5 PO11
51 Software Configuration Management T1/T2 1 BB L2 CO5 PO11
52 Project Scheduling T1/T2 1 BB L2 CO5 PO11
53 DevOps T1/T2 1 BB L2 CO5 PO11
54 DevOps: Motivation T1/T2 1 BB L2 CO5 PO11
55 Cloud as a platform-Operations T1/T2 1 BB L2 CO5 PO11
56 Deployment Pipeline:Overall Architecture Building T1/T2 1 BB L3 CO5 PO11
57 Testing T1/T2 1 BB L2,L5 CO5 PO11
58 Deployment-,Tools and Case Study T1/T2 1 BB L4 CO5 PO11
Suggested Activity: Assignment / Case Studies / Tuorials/ Quiz / Mini Projects / Model Developed/others Planned if any
Evaluation method

Content Beyond the Syllabus Planned

1
2
Text Books
1 Bernd Bruegge and Allen H. Dutoit, “Object-Oriented Software Engineering: Using UML, Patterns and Java”, Third Edition, Pearson Education, 2009.
2 Roger S. Pressman, Object-Oriented Software Engineering: An Agile Unified Methodology, First Edition, Mc Graw-Hill International Edition, 2014.
Reference Books
1 Carlo Ghezzi, Mehdi Jazayeri, Dino Mandrioli, Fundamentals of Software Engineering, 2nd edition, PHI Learning Pvt. Ltd., 2010.
2 Craig Larman, Applying UML and Patterns, 3rd ed, Pearson Education, 2005.
3 Rajib Mall, Fundamentals of Software Engineering, 3rd edition, PHI Learning Pvt. Ltd., 2009.
4 Stephen Schach, Object-Oriented and Classical Software Engineering, 8th ed, McGraw-Hill, 2010.
5 Len Bass, Ingo Weber and Liming Zhu, “DevOps: A Software Architect‘s Perspective”, Pearson Education, 2016
Website / URL References
1 https://www.javatpoint.com/software-engineering-object-oriented-design
2 https://www.geeksforgeeks.org/object-oriented-analysis-and-design/
Blooms Level
Level 1 (L1) : Remembering Level 4 (L4) : Analysing Higher Projects
Lower Order Fixed Hour
Level 2 (L2) : Understanding Thinking Exams
Level 5 (L5) : Evaluating Order / Mini
Level 3 (L3) : Applying Level 6 (L6) : Creating Thinking Projects

Mapping syllabus with Bloom’s Taxonomy LOT and HOT

Unit No Unit Name L1 L2 L3 L4 L5 L6 LOT HOT Total
Unit 1 SOFTWARE PROCESS AND AGILE DEVELOPMENT 0 1 0 2 0 0 1 2 3
Unit 2 SOFTWARE TESTING AND MAINTENANCE 2 0 1 0 0 1 3 1 4
Unit 3 SOFTWARE DESIGN 0 0 2 0 1 3 2 4 6
Unit 4 SOFTWARE TESTING AND MAINTENANCE 0 1 1 2 0 0 2 2 4
Unit 5 PROJECT MANAGEMENT 0 1 1 2 1 0 2 3 5
Total 2 3 5 6 2 4 10 12 22
Total Percentage 9 14 23 27 9 18 45 55 100
CO PO Mapping
PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10 PO11 PO12 PSO1 PSO2
CO1 2 2 1 2 2 0 0 0 0 1 1 2 1 2
CO2 2 3 2 3 2 0 0 0 2 2 3 2 2 2
CO3 2 3 2 1 1 0 0 0 2 2 3 2 3 3
CO4 2 3 2 2 3 0 0 0 2 2 3 2 2 3
CO5 2 3 1 2 2 0 0 0 0 0 0 3 2 2
Avg 2 2 1 2 2 0 0 0 0 1 1 2 3 2
Justification for CO-PO mapping
CO1 Students get the knowledge about software process models
CO2 Students able to understand the requirement analysis and specification
CO3 Student can gain knowledge of the system design concepts using UML
CO4 Students able to understand about testing strategies and can able apply the test cases
CO5 Students can undestand how to manage the project using software tools .
3 High level 2 Moderate level 1 Low level
*Kindly sign with date
Name & Sign of Faculty Incharge : A.Gowri AP/IT
Name & Sign of Subject Expert :Dr.J .Paramesh
Head of the Department : Information Technology
Format No :TLP 12 Rev.No.: 01 Rev. Date: 04.01.21