Department of Computer Science & Engineering
Delhi Technological University
Shahabad Daulatpur, Bawana Road
Delhi, India
August 2020
SE 302: Object Oriented Software Engineering
Instructor: Dr. Ruchika Malhotra
Title:
Object Oriented Software Engineering – SE 302
Text Book:
Y.Singh, R. Malhotra, “Object Oriented Software Engineering”, PHI, 2012.
Reference Books:
• I. Jacobson, M. Christerson, P. Jonsson, G. Overgaard, “Object Oriented
Software Engineering”, 2nd Edition, Pearson Education, 2007.
• G. Booch, J Rumbaugh, I Jacobson, “The Unified Modeling Language User
Guide” 11th Ed., Pearson Education, 2003.
• R. Binder, Object Oriented Testing.
• Y. Singh, “Software Testing”, Cambridge, UK, 2010.
• Additional reading material will be assigned during the class.
Course Overview:
The course presents the fundamentals of object-oriented software engineering and
discusses the recent technological developments in the field. It focuses on object-
oriented analysis, design and implementation in the context of an overall effort to
present object-oriented concepts, techniques and models that can be applied in
software estimation, analysis, design, testing and quality improvement. It applies
Page 1 of 4
unified modelling language notations to a series of examples with a real-life case
study.
Administrative Details:
• Instructor: Dr. Ruchika Malhotra – [email protected],in
• Class Timings: MTWT 12 pm -- 1 pm
Course Description:
• Introduction to Object Oriented Concepts
• Object Oriented life Cycle Models- Fountain and RUP - The importance of
modeling, principle of modeling, object oriented modeling, Introduction to
Object oriented Methodologies such as Unified Modeling Language,
Overview of UML, conceptual model of UML, architecture, software
development lifecycle using Rational Unified Process
• Requirement Analysis – Use case Approach, Initial Requirement Document,
SRS
• Object Oriented Analysis – Identification of classes, relationships,
Identification of state and behaviour.
• Object Oriented Design - Object oriented methodologies of Jacobson,
design model, System development using various UML Diagrams.
• Object Oriented Implementation
• Software Quality and Object Oriented Metrics – Software Quality attributes,
CMM model, Object Oriented Metrics.
• Object Oriented Testing – Use case testing, Path Testing, State based
testing, Class Testing.
• Applications & Tools
Grading Information:
• Quizzes – 2 Quiz -- There will be random quizzes during the entire
semester. These quizzes will take place mostly at the beginning of the class.
• 3 class tests
• Project – Each group of students, typically consisting of 1-2 students, will
select a case study from a given list of case studies in the class.
o Project Statement and SRS -- 10%
o Project Documentation -- 15%
o Project Presentation and Execution -- 15%
Page 2 of 4
Semester Laboratory Project:
The semester project is an opportunity, as a group of 1-2 students, to implement
the concepts discussed in the class. The students will have to select the case study
from the given list of case studies in the class. No case study can be repeated.
The project is made up of the following components:
1. Project Statement -- One page document describing the objective of the
project. This is due by August 16, 2020.
2. Progress Report -- One page document indicating the current state of the
project. This is due by September 30, 2020.
3. Final Report -- A report is required at the end of the semester (12 font,
Times new Roman). It should have the following format:
o Title
o Table of Contents
o Introduction and Problem Statement
o Initial Requirement Document
o Software Requirement Specification Document
o UML Diagrams – use case, sequence, class, activity, statechart
o Project screen shots and execution details
o Test Cases
4. Presentation -- Each group will be required to present their project to the
class towards the end of the semester and during laboratories in the
semester.
The project evaluation will be based on the creativity, the quality and
the completeness.
Page 3 of 4
LIST OF EXPERIMENTS
Object Oriented Software Engineering
The following experiments shall be conducted in lab:
1. Write the problem statement of CASE STUDY 1-12.
2. Write the initial requirement document of CASE STUDY 1-12.
3. Write the Software Requirement Specification document of CASE STUDY
1-12.
4. Design use case diagram of CASE STUDY 1-12.
5. Write use case description of the CASE STUDY 1-12.
6. Draw class diagram of the given CASE STUDY 1-12.
7. Draw sequence diagram of the given CASE STUDY 1-12.
8. Draw collaboration diagram of the given CASE STUDY 1-12.
9. Draw activity diagram of the given CASE STUDY 1-12.
10. Design test cases of the given CASE STUDY 1-12.
CASE STUDY 1: Hospital Patient Management System
CASE STUDY 2: Mobile Chat System
CASE STUDY 3: University Registration System
CASE STUDY 4: Online Examination System
CASE STUDY 5: Insurance Management System
CASE STUDY 6: Course Reservation System
CASE STUDY 7: Tenant Management System
CASE STUDY 8: ATM Management System
CASE STUDY 9: Parking Management System
CASE STUDY 10: Air Ticket Reservation System
CASE STUDY 11: Attendance Tracking Management System
CASE STUDY 12: Video Library Management System
Page 4 of 4
