rptInstructionPlan (3) | Object Oriented Programming | Object (Computer Science)

of 6

Please download to get full document.

View again

All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
PDF
6 pages
0 downs
2 views
Share
Description
Lovely Professional University,Punjab Format For Instruction Plan [for Courses with Lectures and Labs Course No CSE532T Cours Title OBJECT ORIENTED SOFTWARE ENGINEERING Course Planner 14573 :: Harikesh Bahadur Yadav Lectures Tutorial Practical Credits 3 0 0 3 Text Book: 1 Author: Timothy C Lethbridge and Robert Langaniere, Title: Object Oriented Software Engineering ,Publishers: Tata Mcgraw Hill edition2004 Other Specific Book: 2 Icar Jacobsan, Object Oriented Software Engineering: A use
Tags
Transcript
  Lovely Professional University,Punjab Course NoCours TitleCourse PlannerLecturesTutorialPracticalCredits CSE532TOBJECT ORIENTED SOFTWARE ENGINEERING14573 :: Harikesh Bahadur Yadav3003 Sr. No.(Web adress) (only if relevant to the courses)Salient Features 9http://www.bleading-edge.com/Publications/C++Journal/Cpjour2.htmWhat is S/W Engg, Its purpose.10http://infolab.stanford.edu/~ullman/dscb/oo-old.pdf OOPs concepts with examples Sr NoJouranls atricles as compulsary readings (specific articles, Complete reference) 6http://www.scirp.org/journal/jsea/ 7http://www.sersc.org/journals/IJSEIA/ 8http://linkinghub.elsevier.com/retrieve/pii/S0965997807000294Author: Timothy C Lethbridge and Robert Langaniere, Title: Object Oriented Software Engineering ,Publishers: Tata Mcgraw Hilledition20041 Text Book:Other Specific Book: Icar Jacobsan, Object Oriented Software Engineering: A use case Driven Approach, Pearson Education2Booch,G,obJect oriented analysis and design, Benjamin/Cummins publishing co. Redwood City, CA, USA3Richard C Lee, William M. Tepfenhard, UML and C++, A Practical guide to object oriented Development, Pearson Education4Stephen R. Scach, classical & Object oriented Software Engineering with UML and java: McGraw Hill5 Relevant WebsitesOther Reading Format For Instruction Plan [for Courses with Lectures and Labs 1Approved for Spring Session 2011-12  11http://www.stsc.hill.af.mil/crosstalk/2008/03/0803Gottesdiener.htmlRequirements as per specific use12http://www.agilemodeling.com/artifacts/classDiagram.htm Class Diagram13http://ezinearticles.com/?Design-Patterns-for-Software-Engineering&id=550329Design Pattern14http://www.cs.ucl.ac.uk/staff/A.Finkelstein/advmsc/14.pdf Testing Detailed Plan For Lectures Week NumberLecture NumberLecture TopicChapters/Sections ofTextbook/otherreferencePedagogical toolDemonstration/casestudy/images/anmation ctc. planned Part 1 Week 1 Lecture 1Software & Software Engineering: Nature of S/W,Meaning of S/W Engg,->Reference :1,ch1Visual Paradigm forUMLLecture 2Stakeholders in Software engineering, SoftwareQuality, Activities common to S/W Projects, S/WEngg. Projects->Reference :1,ch1Lecture 3Difficulties in S/W Engg, Risks in S/W Engg->Reference :1,ch1 Week 2 Lecture 4Review of Object Orientation: Meaning, Classes &Objects, Instance Variables->Reference :1,ch2Lecture 5Methods, operations & polymorphism, InheritanceHierarchies, Effect of inheritance on polymorphismand variable declaration->Reference :1,ch2Lecture 6Concepts that define object orientation, Difficultyand risk in PL choice and OOP->Reference :1,ch2 Week 3 Lecture 7Incorporating reusability and reuse in S/Wengineering,->Reference :1,ch3Lecture 8Framework: reusable subsystems->Reference :1,ch3http://www.youtube.com/watch?v=KaPC0gsEQ68(video Vmodel)Lecture 9The client server architecture. Technology neededto built Client-server subsystems->Reference :1,ch32Approved for Spring Session 2011-12  Week 4 Lecture 10Basic Description of OCSF, Difficulties & risksinvolved in reusable technology and client serversubsystem->Reference :1,ch3 Part 2 Week 4 Lecture 11Developing Requirements: Domain Analysis and itsbenefits->Reference :1,ch4Lecture 12Division of sections in Domain analysis document->Reference :1,ch4 Week 5 Lecture 13Domain Problem definition & scope->Reference :1,ch4Lecture 14Object oriented requirement analysis ,Functionalrequirements->Reference :1,ch4Lecture 15Non-Functional requirements->Reference :1,ch4 Week 6 Lecture 16Some techniques for gathering and analyzingrequirements,Types of Requirements document,requirementgathering->Reference :1,ch4http://www.byu.com.ve /htmlsite/ Servic1.gifLecture 17Test 1Lecture 18Reviewing requirement, managing changingrequirements, Difficulties & risks in domain andrequirements analysis->Reference :1,ch4 Week 7 Lecture 19Modeling with classes: What is UML, Classdiagrams, Associations & multiplicity->Reference :1,ch5Lecture 20Generalization, Instance diagram, Advance featuresof class diagram->Reference :1,ch5Lecture 21Developing class diagram, Difficulties & risks whenusing class diagram->Reference :1,ch5 MID-TERMPart 3 Week 8 Lecture 22Design Patterns: Introductionto pattern, Various PatternsAbstraction Occurrence->Reference :1,ch6Lecture 23General hierarchy, Player role, Singleton, Adapter,facade, immutable->Reference :1,ch6Lecture 24read only interface & proxy patterns. Difficulties &Risks when using design pattern.->Reference :1,ch6 Week 9 Lecture 25Focusing on Users and their tasks: User-centreddesign, the importanceof focusing on users,->Reference :1,ch73Approved for Spring Session 2011-12  Week 9 Lecture 26characteristics of user, Developing use casemodels, The basics of user interface design, basicterminology of user interface design.->Reference :1,ch7Lecture 27Modelling Interaction and Behaviour: Interactiondiagrams, Sequence diagram, Collaborationdiagrams and patterns, state Diagrams,->Reference :1,ch8 Week 10 Lecture 28Architecting and Designing Software: The Processof design, principle leading to good design(11principles),->Reference :1,ch9Lecture 29Architectural patterns, Writing good designdocument, difficulties & risks in design->Reference :1,ch9 Part 4 Week 10 Lecture 30Architectural patterns, Writing good designdocument, difficulties & risks in design->Reference :1,ch9 Week 11 Lecture 31Testing & inspection: Effective & efficient testing,Defects in ordinary & numerical algorithms, Defectsin timing & co-ordination.->Reference :1,ch10Lecture 32Testing & inspection: Effective & efficient testing,Defects in ordinary & numerical algorithms, Defectsin timing & co-ordination.->Reference :1,ch10Lecture 33Managing the Software Process: ProjectManagement-activities of project manager,->Reference :1,ch11 Week 12 Lecture 34S/W Process models->Reference :1,ch11Lecture 35S/W Process models->Reference :1,ch11Lecture 36Cost estimation and its principle, building S/Wengineering teams, project,->Reference :1,ch11 Week 13 Lecture 37Cost estimation and its principle,->Reference :1,ch11Lecture 38building S/W engineering teams, project,->Reference :1,ch11Lecture 39contents of a project plan, difficulties & risks inproject management->Reference :1,ch11 Spill Over Week 14 Lecture 40Application and Review of Object Oriented SoftwareEngineering- Understanding the customer and user->Reference :3,topicooseLecture 41Basing development on solid principles andreusable technology->Reference :4,topicreuse4Approved for Spring Session 2011-12
Related Search
Advertisements
Similar documents
View more...
Advertisements
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks