Beruflich Dokumente
Kultur Dokumente
Format For Instruction Plan [for Courses with Lectures and Labs
Course No CSE532T
Text Book:
1 Author: Timothy C Lethbridge and Robert Langaniere, Title: Object Oriented Software Engineering ,Publishers: Tata Mcgraw Hill edition2004
2 Icar Jacobsan, Object Oriented Software Engineering: A use case Driven Approach, Pearson Education 3 Booch,G,obJect oriented analysis and design, Benjamin/Cummins publishing co. Redwood City, CA, USA 4 Richard C Lee, William M. Tepfenhard, UML and C++, A Practical guide to object oriented Development, Pearson Education
5 Stephen R. Scach, classical & Object oriented Software Engineering with UML and java: McGraw Hill
Other Reading Sr No Jouranls atricles as compulsary readings (specific articles, Complete reference) 6 http://www.scirp.org/journal/jsea/ 7 http://www.sersc.org/journals/IJSEIA/ 8 http://linkinghub.elsevier.com/retrieve/pii/S0965997807000294 Relevant Websites Sr. No. (Web adress) (only if relevant to the courses) 9 http://www.bleading-edge.com/Publications/C+ +Journal/Cpjour2.htm 10 http://infolab.stanford.edu/~ullman/dscb/oo-old.pdf Salient Features What is S/W Engg, Its purpose. OOPs concepts with examples
11 http://www.stsc.hill.af.mil/crosstalk/2008/03/0803Gottesdiener. Requirements as per specific use html 12 http://www.agilemodeling.com/artifacts/classDiagram.htm 13 http://ezinearticles.com/?Design-Patterns-for-SoftwareEngineering&id=550329 14 http://www.cs.ucl.ac.uk/staff/A.Finkelstein/advmsc/14.pdf Class Diagram Design Pattern Testing
Part 1
Week 1 Lecture 1 Lecture 2 Software & Software Engineering: Nature of S/W, Meaning of S/W Engg, Stakeholders in Software engineering, Software Quality, Activities common to S/W Projects, S/W Engg. Projects Difficulties in S/W Engg, Risks in S/W Engg Review of Object Orientation: Meaning, Classes & Objects, Instance Variables Methods, operations & polymorphism, Inheritance Hierarchies, Effect of inheritance on polymorphism and variable declaration Concepts that define object orientation, Difficulty and risk in PL choice and OOP Incorporating reusability and reuse in S/W engineering, Framework: reusable subsystems ->Reference :1,ch1 ->Reference :1,ch1 Visual Paradigm for UML
->Reference :1,ch2 ->Reference :1,ch3 ->Reference :1,ch3 http://www.y outube.com/w atch?v=KaPC 0gsEQ68 (video Vmodel)
Lecture 9
->Reference :1,ch3
Week 4
Lecture 10
Basic Description of OCSF, Difficulties & risks involved in reusable technology and client server subsystem
->Reference :1,ch3
Part 2
Week 4 Lecture 11 Lecture 12 Week 5 Lecture 13 Lecture 14 Lecture 15 Week 6 Lecture 16 Developing Requirements: Domain Analysis and its ->Reference :1,ch4 benefits Division of sections in Domain analysis document Domain Problem definition & scope Object oriented requirement analysis ,Functional requirements Non-Functional requirements Some techniques for gathering and analyzing requirements,Types of Requirements document, requirement gathering Test 1 Reviewing requirement, managing changing requirements, Difficulties & risks in domain and requirements analysis Modeling with classes: What is UML, Class diagrams, Associations & multiplicity ->Reference :1,ch4 ->Reference :1,ch4 ->Reference :1,ch4 ->Reference :1,ch4 ->Reference :1,ch4 ->Reference :1,ch4 http://www.b yu.com.ve /htmlsite/ Servic1.gi f
Lecture 17 Lecture 18
Week 7
->Reference :1,ch5
Generalization, Instance diagram, Advance features ->Reference :1,ch5 of class diagram Developing class diagram, Difficulties & risks when using class diagram ->Reference :1,ch5
MID-TERM Part 3
Week 8 Lecture 22 Design Patterns: Introduction to pattern, Various Patterns Abstraction Occurrence General hierarchy, Player role, Singleton, Adapter, facade, immutable read only interface & proxy patterns. Difficulties & Risks when using design pattern. Focusing on Users and their tasks: User-centred design, the importanceof focusing on users, ->Reference :1,ch6
Week 9
Lecture 26
characteristics of user, Developing use case models, The basics of user interface design, basic terminology of user interface design. Modelling Interaction and Behaviour: Interaction diagrams, Sequence diagram, Collaboration diagrams and patterns, state Diagrams, Architecting and Designing Software: The Process of design, principle leading to good design(11 principles), Architectural patterns, Writing good design document, difficulties & risks in design
->Reference :1,ch7
Lecture 27
->Reference :1,ch8
Week 10
Lecture 28
->Reference :1,ch9
Lecture 29
->Reference :1,ch9
Part 4
Week 10 Week 11 Lecture 30 Lecture 31 Architectural patterns, Writing good design document, difficulties & risks in design ->Reference :1,ch9 Testing & inspection: Effective & efficient testing, ->Reference :1,ch10 Defects in ordinary & numerical algorithms, Defects in timing & co-ordination. Testing & inspection: Effective & efficient testing, ->Reference :1,ch10 Defects in ordinary & numerical algorithms, Defects in timing & co-ordination. Managing the Software Process: Project Management-activities of project manager, S/W Process models S/W Process models Cost estimation and its principle, building S/W engineering teams, project, Cost estimation and its principle, building S/W engineering teams, project, contents of a project plan, difficulties & risks in project management ->Reference :1,ch11 ->Reference :1,ch11 ->Reference :1,ch11 ->Reference :1,ch11 ->Reference :1,ch11 ->Reference :1,ch11 ->Reference :1,ch11
Lecture 32
Spill Over
Week 14 Lecture 40 Lecture 41 Application and Review of Object Oriented Software ->Reference :3,topic Engineering- Understanding the customer and user oose Basing development on solid principles and reusable technology ->Reference :4,topic reuse
Test 1 Homework 1
evaluation of students To enhance the analytical skills of student To enhance the analytical skills of student
Case study 1
case study
Group
written,presentatio n/viva
9 / 12
* In ENG courses wherever the total exceeds 100, consider x best out of y components of CA, as explained in teacher's guide available on the UMS List of suggested topics for term paper[at least 15] (Student to spend about 15 hrs on any one specified term paper) Sr. No. Topic 1 Reverse Engineering
2 Design Pattern 3 Pattern optimization 4 Understanding Behavioral Dependencies in Class Hierarchies using Concept Analysis 5 X-Ray Views on a Class using Concept Analysis.
6 The Concept of Dynamic Analysis 7 Conceptual module querying for software reengineering. 8 Lattice Theory 9 Reconciling Use Cases via Controlled Language and Graphical Models 10 Reverse Engineering of Use Case Realizations in UML 11 Re-Engineering Object-Oriented Legacy Systems 12 Reverse Engineering and Design Recovery 13 A Hybrid Reverse Engineering 14 Platform Combining Metrics and Program Visualization 15 Identifying Candidate Objects During System Analysis