dynamic and implementation uml diagram syllabus.pdf
- 1. 100 REFERENCES 1. George Coulouris, Jean Dollimore, Time Kindberg, “Distributed Systems Concepts and Design”, Fifth Edition, Pearson Education, 2012. 2. Pradeep L Sinha, “Distributed Operating Systems: Concepts and Design”, Prentice Hall of India, 2007. 3. Tanenbaum A S, Van Steen M, “Distributed Systems: Principles and Paradigms”, Pearson Education, 2007. 4. Liu M L, “Distributed Computing: Principles and Applications”, Pearson Education, 2004. 5. Nancy A Lynch, “Distributed Algorithms”, Morgan Kaufman Publishers, 2003. 6. Arshdeep Bagga, Vijay Madisetti, “ Cloud Computing: A Hands-On Approach”, Universities Press, 2014. CO’s-PO’s & PSO’s MAPPING CO’s PO’s PSO’s 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 1 2 2 3 3 1 - - - 2 1 3 3 2 1 1 2 1 3 2 1 2 - - - 2 2 2 2 1 3 2 3 2 2 1 3 3 - - - 3 2 1 1 1 2 1 4 1 2 2 3 1 - - - 3 3 2 1 3 1 1 5 3 3 1 2 3 - - - 3 3 3 1 3 2 3 AVg. 1.8 2.4 1.8 2.4 2 - - - 2.6 2.2 2.2 1.6 2 1.8 1.6 1 - low, 2 - medium, 3 - high, ‘-“- no correlation CCS356 OBJECT ORIENTED SOFTWARE ENGINEERING L T P C 3 0 2 4 COURSE OBJECTIVES: To understand Software Engineering Lifecycle Models To Perform software requirements analysis To gain knowledge of the System Analysis and Design concepts using UML. To understand software testing and maintenance approaches To work on project management scheduling using DevOps UNIT I SOFTWARE PROCESS AND AGILE DEVELOPMENT 9 Introduction to Software Engineering, Software Process, Perspective and Specialized Process Models –Introduction to Agility-Agile process-Extreme programming-XP Process-Case Study. UNIT II REQUIREMENTS ANALYSIS AND SPECIFICATION 9 Requirement analysis and specification – Requirements gathering and analysis – Software Requirement Specification – Formal system specification – Finite State Machines – Petrinets – Object modelling using UML – Use case Model – Class diagrams – Interaction diagrams – Activity diagrams – State chart diagrams – Functional modelling – Data Flow Diagram- CASE TOOLS. UNIT III SOFTWARE DESIGN 9 Software design – Design process – Design concepts – Coupling – Cohesion – Functional independence – Design patterns – Model-view-controller – Publish-subscribe – Adapter – Command – Strategy – Observer – Proxy – Facade – Architectural styles – Layered - Client Server - Tiered - Pipe and filter- User interface design-Case Study.
- 2. 101 UNIT IV SOFTWARE TESTING AND MAINTENANCE 9 Testing – Unit testing – Black box testing– White box testing – Integration and System testing– Regression testing – Debugging - Program analysis – Symbolic execution – Model Checking-Case Study UNIT V PROJECT MANAGEMENT 9 Software Project Management- Software Configuration Management - Project Scheduling- DevOps: Motivation-Cloud as a platform-Operations- Deployment Pipeline:Overall Architecture Building and Testing-Deployment- Tools- Case Study COURSE OUTCOMES: 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 45 PERIODS PRACTICAL EXERCISES: 30 PERIODS LIST OF EXPERIMENTS: 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