University of Madras - Syllabus of Bachelor of Science (BSc) Software Engineering - Semester IV - BSE 206 - Object Oriented Software Engineering
UNIVERSITY OF MADRAS
B.Sc. DEGREE COURSE IN SOFTWARE ENGINEERING
SEMESTER SYSTEM WITH CREDITS
(Effective from the Academic Year 2003-2004)
SYLLABUS
Semester IV - BSE 206 - Object Oriented Software Engineering
Lecture Per Week: 6 hrs
Duration of Examination: 3 hrs
Maximum Marks: 100
Credits: 4
Unit I
Introduction to objects - module - cohesion - coupling - data encapsulation - abstract data types - information hiding - objects, - inheritance - polymorphism & dynamic binding - cohesion & coupling of objects. Reusability, protability & interoperability - reuse concepts - impediments to reuse, reuse case studies - objects & productivity - reuse during design & implementation phases - reuse & maintenance, portability, why portability, techniques for achieving portability - ihnteroperability - future trends in
interoperability.
Unit II
Planning and estimation - planning and the software process - estimating duration and cost - components of a software project management plan - software project management plan frame work - IEEE software project management plan - planning of testing - planning of object oriented projects - training requirements - documentation standards - CASE tools for planning and estimating - testing the software project management requirements phase - requirements analysis techniques - reusing the prototyping - human factors - rapid prototyping as a specification technique - reusing the rapid prototyping - other uses of rapid prototyping - management implication of the application design (JAD) - Comparison of requirement analysis techniques - testing during requirement phase - CASE tools for the requirement phase - metrics for the requirement phase - obsert oglesby case study: requirements phase obsert oglesby case study - rapid prototype - object oriented requirements.
Unit III
Specification phase - specification document informal - specification - structured, systems analysis - other semi formal techniques - entity relationship modeling - finite. state machines - Petrinets z357 - other formal techniques - comparison of specification techniques - testing during specification phase - CASE tools for the specification phase - metrics for the specification phase - obvert oglesy case study:
Structured systems analysis - software project management. Object oriented analysis phase - object oriented versus structured paradigm - object oriented analysis - elevator problem - use case modeling - dynamic modeling - testing during object oriented analysis phase - case tools - software project management.
Unit IV
Design phase - design and abstraction - action oriented design - data flow analysis - transaction analysis - data oriented design - object oriented design - elevator problem - formal techniques for detail designs - real time design techniques - testing - case tools
- metrics - object oriented design.- Implementation phase: choice or programming
language - forth generation language - good programming practice - coding standards
- module reuse - module test case selection - black box - glass box module testing techniques - comparison clean room - potential problems when testing objects - management aspects of module testing - CASE tools for implementation phase.
Unit V
Implementation and integration phase - testing - graphical user interfaces - product testing - acceptance testing - case tools for this phase - integration enviromnents for business applications - public tools infrastructure - potential problems with environments. Maintenance phase - why maintenance is necessary - case study - management - maintenance of objet oriented software - maintenance skill versus development skills - reverse engineering - testing - case tools.
Books for Study
1. Stephen R. Schach - Classical and Object oriented Software Engineering 4th Edition - McGraw Hill
2. Ivar Jacobson - Object Oriented Software Engineering - Addison Wesley.