INFO INSTITUTE OF ENGINEERING AC 17(10)

Coimbatore-641107

COURSE PLAN – THEORY AND PRACTICAL

1 Class : VI Semester B.E (CSE)

2 Course Code : CCS356

3 Course Title : OBJECT ORIENTED SOFTWARE ENGINEERING

4 Course Type & Hours : Theory and practical; 75 hours

5 Course Status & Credits : UG, Professional Competence Course Elective; 4 Credits

6 Academic Year : 2024-2025

7 Regulation : Regulation 2021
8 Staff In-charge : [Link], AP/IT,
E-mail: kingrr20@[Link]
9 Aim/Course Description : The aim of this Software Engineering course is to provide
a solid foundation in software development processes, including lifecycle models, requirements
analysis, system design, testing, maintenance, and project management using DevOps practices.
Students will gain hands-on experience to develop high-quality software solutions efficiently.

10 Prerequisite: Basic Programming Concepts, Logical Thinking and Problem-Solving

:
11 Text Books
T1: Bernd Bruegge and Allen H. Dutoit, “Object-Oriented Software Engineering: Using UML,
Patterns and Java”, Third Edition, Pearson Education, 2009.
T2: Roger S. Pressman, Object-Oriented Software Engineering: An Agile Unified
Methodology, First Edition, Mc Graw-Hill International Edition, 2014.
12 Reference Books
R1: Carlo Ghezzi, Mehdi Jazayeri, Dino Mandrioli, Fundamentals of Software Engineering,
2nd edition, PHI Learning Pvt. Ltd., 2010.
R2: Craig Larman, Applying UML and Patterns, 3rd ed, Pearson Education, 2005.
R3: Len Bass, Ingo Weber and Liming Zhu, “DevOps: A Software Architect‘s Perspective”,
Pearson Education, 2016.
R4: Rajib Mall, Fundamentals of Software Engineering, 3rd edition, PHI Learning Pvt. Ltd.,
2009.
 R5: Stephen Schach, Object-Oriented and Classical Software Engineering, 8th ed, McGraw-
Hill, 2010.
R6: Software Engineering: A Practitioner's Approach 6th edition by Roger S. Pressman.
McGraw- Hill.
13 Web Resources
W1: [Link]
specification
W2: [Link]
W3: [Link]
W4: [Link]

14 E-Learning Resources
E1: [Link]
E2: [Link]
engineering_2_ed

15 Course Outlines

Books to
Mode of
Units Periods Topics to be Covered be Page No
Delivery
Referred
Introduction to Software 45,
1 BB T1,R6
Engineering 36-42
SOFTWARE PROCESS AND AGILE

1 Software Process BB R6 53-62

Perspective Process Models, 56
1 BB T1,R6
Waterfall Model 78-80
DEVELOPMENT

1 Incremental Model, RAD Model BB R6 80-83

UNIT I

1 Evolutionary Process Model BB R6 83-88

1 Evolutionary Process Model BB R6 88-90

1 Specialized Process Models BB R6 91-93

Introduction to Agility, Agile
1 BB R6 105-109
process
Extreme programming-XP
1 BB R6 110-113
Process

Total Periods for Unit-I = 9

 Requirement analysis and

REQUIREMENTS ANALYSIS AND SPECIFICATION

1 BB T1 161-168
specification

1 Requirements gathering and analysis BB R6 182

1 Requirement Engineering Process BB R6 176-180

Software Requirement Specification,
1 PPT W1 -
Formal system specification
UNIT II

1 Finite State Machines, Petrinets PPT R5 376, 382

Object modeling using UML, Use case
1 BB T1 84-90
Model
Class diagrams, Interaction diagrams T1
1 BB 91-101

Activity diagrams, State chart

1 BB T1 102-107
diagrams

Functional modeling, Data Flow

1 BB R4 225
Diagram

Total Periods for Unit-II = 9

1 Software design, Design process BB T1 266

1 Design concepts BB T1 268

1 Coupling , Cohesion , Functional

BB T1 270
independence
SOFTWARE DESIGN

1 Design patterns , Model-view-

PPT W2 -
controller
UNIT III

1 Publish-subscribe , Adapter BB R2 377

1 Command, Strategy , Observer ,

BB R2 457, 521
Proxy , Facade

1 Architectural styles – Layered , Client

BB R2 448
Server

1 Tiered - Pipe and filter BB T2 283-285

1 User interface design, Case Study PPT R4 373

Total Periods for Unit-III = 9

 1 Software Testing BB T1 475

1 Unit testing BB T1 493

1 Black box testing BB R4 413

SOFTWARE TESTING
AND MAINTENANCE

1 White box testing BB R4 417

UNIT IV

1 Integration and System testing BB R4 430,435

1 Regression testing, Debugging BB T1,R4 518,427

1 Program analysis, Symbolic execution BB R4 428

1 Model Checking BB W3 -

Assignme -
1 Case Study on Software Testing -
nt

Total Periods for Unit-IV = 9

1 Software Project Management BB T1 609,629

1 Software Configuration Management BB T1 574

PROJECT MANAGEMENT

1 Software Configuration Management BB T1 584

1 Project Scheduling BB W4 -
UNIT-V

1 DevOps: Motivation BB R3 3

1 Cloud as a platform PPT R3 27

1 Cloud Operations PPT R3 47

1 Deployment Pipeline PPT R3 63

1 Testing-Deployment, Tools, Case BB R3 79,101

Study

Total Periods for Unit-V = 9

Total = 45 Periods
16 PRACTICAL EXERCISES:
1. Identify a software system that needs to be developed.
2. Document the Software Requirements Specification (SRS) for the identified system.
3. Identify use cases and develop the Use Case model.
4. Identify the conceptual classes and develop a Domain Model and also derive a Class
Diagram from that.
5. Using the identified scenarios, find the interaction between objects and represent them using
UML Sequence and Collaboration Diagrams
6. Draw relevant State Chart and Activity Diagrams for the same system.
7. Implement the system as per the detailed design
8. Test the software system for all the scenarios identified as per the usecase diagram
9. Improve the reusability and maintainability of the software system by applying appropriate
design patterns.
10. Implement the modified system and test it for various scenarios.

SUGGESTED DOMAINS FOR MINI-PROJECT:

1. Passport automation system.
2. Book bank
3. Exam registration
4. Stock maintenance system.
5. Online course reservation system
6. Airline/Railway reservation system
7. Software personnel management system
8. Credit card processing 9. e-book management system
10. Recruitment system
11. Foreign trading system
12. Conference management system 102
13. BPO management system
14. Library management system
15. Student information system
30 PERIODS
17 Professional Components

Course Component Contribution in Percentage

Mathematics 0%
Science 0%
Humanities 20%
Core Engineering 80%

18 Evaluation Components

[Link] Components Marks

Internal Test ( Internal Tests of 2 hours
1 duration for 60 marks) and Practical 50
marks.
University Examination ( Conducted for
100 marks and 3 hours duration )
Part-A (10×2=20 Marks)
Part-B (5×16=80 Marks)
2 50
and
University Practical Examination
(Conducted for 100 marks and 3 hours
duration)
Total 100

19 Laboratory

S.N
Components Marks
o
1 Record 35
2 Observation 30
3 Viva voce 10
4 Model Practical Examination 25
Total 100

20 Course Outcomes and its Contributions to PO

Course Outcomes [CO’s]

CO1:Compare various Software Development Lifecycle Models

CO2:Evaluate project management approaches as well as cost and schedule estimation strategies
CO3:Perform formal analysis on specifications.
CO4:Use UML diagrams for analysis and design.
CO5:Architect and design using architectural styles and design patterns, and test the system
Programme Outcomes [PO’s]

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, societal, 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 Programme Outcomes [PO’s] PSO’s
Outco
mes

PSO1

PSO2

PSO3
PO10

PO11

PO12
PO1

PO2

PO3

PO4

PO5

PO6
PO7
PO8
PO9
[CO’s]

CO1 2 2 1 2 2 - - - - 1 1 2 2 2 1

CO2 2 3 2 3 2 - - - 2 2 2 2 3 2 1

CO3 2 3 2 1 1 - - - 2 2 3 2 2 3 1

CO4 2 3 2 2 3 - - - 2 2 3 2 2 3 1

CO5 2 3 1 2 2 - - - - - - 1 3 2 2

AVG 2 2 1 2 2 - - - - 1 1 2 2 2 1

CO satisfy the PO lightly - 1 Point

CO satisfy the PO on an average - 2 Points
CO satisfy the PO strongly - 3 Points

21 Assignment Topics

1. Software Engineering Life Cycle models

2. Software Requirement Specification (SRS) Document
3. Various Architectural styles in Software Design

22 Content Beyond Syllabus

1. Clean Room Software Engineering
2. Validation Testing- Alpha and Beta Testing

Staff Incharge HOD /Programme Coordinator PRINCIPAL