SOFTWARE ENGINEERING Course Code LotiPic cs2005 [fo ‘COURSE OBJECTIVES: To understand Software Engineering Lifecycle Models To Perform software requirements analysis To gain knowledge of the System Analysis and Design concepts To understand software testing and maintenance approaches To work on project management scheduling using DevOps yeene UNIT. 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 IL REQUIREMENTS ANALYSIS AND SPECIFICATION 9 Requirement analysis and specification ~ Requirements gathering and analysis ~ Functional and Non Functional requirements ~ Software Requirement Specification ~ Formal system specification — Finite State Machines ~ Petrinets ~ Object modelling using UML ~ Use case Model ~ Class diagrams — Interaction diagrams ~ Activity 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. 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 ~ Release Management 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: C01: Compare various Software Development Lifecycle Models CO2: Evaluate project management approaches as well as cost and schedule estimation strategies, 3. C03: Perform formal analysis on specifications. (C04: Use UML diagrams for analysis and design 5. COS: Architect and design using architectural styles and design patterns, and test the system 45 PERIODSPRACTICAL EXERCISES: 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 ClassDiagram from that. Using the identified scenarios, find the interaction between objects and represent them usingUML Sequence and Collaboration Diagrams Draw relevant State Chart and Activity Diagrams for the same system. Implement the system as per the detailed design Test the software system for all the scenarios identified as per the use case diagram Improve the reusability and maintainability of the software system by applying appropriatedesign patterns. 10. Implement the modified system and test it for various scenarios. ‘SUGGESTED DOMAINS FOR MINI 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 13, BPO management system 14, Library management system TOTAL:75 PERIODS 15, Student information system ROIECT: TEXT BOOKS 30 PERIODS 4. Bernd Bruegge and Allen H. Dutoit, “Object-Oriented Software Engineering: Using UML,Patterns and Java”, Third Edition, Pearson Education, 2008. 2. Roger S. Pressman, Object-Oriented Software Engineering: An Agile Unified Methodology First Edition, Mc Graw-Hill International Edition, 2014. REFERENCES 1. Carlo Ghezzi, Mehdi Jazayeri, Dino Mandrioli, Fundamentals of Software Engineering, 2ndedition, PHI Learning Pvt. Ltd., 2010. 2. Craig Larman, Applying UML and Patterns, 3rd ed, Pearson Education, 2005. 3. Len Bass, Ingo Weber and Liming Zhu, “DevOps: A Software Architect's Perspective” Pearson Education, 2016 |. Rajib Mall, Fundamentals of Software Engineering, 3rd edition, PHI Learning Pvt. Ltd., 2009, 5. Stephen Schach, Object-Oriented and Classical Software Engineering, 8th ed, McGraw-Hil