Syllabus
What the course covers
B Tech CSE, Semester VI. Lab Based (70:30). Credits (L, T, P, C): 3–0–2–4.
This course is about how software is really made by teams. We start with how a team organizes its work, with Agile and Scrum, and then follow a product from its first requirements through design and testing to delivery with DevOps practices. You will learn from live case studies from industry, use the tools that professional teams use, and build a project that starts from a statement supplied by industry and ends up deployed on the cloud. By the end you should feel at home with the processes, the tools, and the vocabulary of a software team, which is what we mean by being industry ready.
Course objectives
- This course addresses issues in the engineering of software systems and development using live case studies from industries.
- The objectives of this course are to introduce basic software engineering concepts; to introduce the Agile software development process; and to provide hands on training (experiential learning) using state of the art tools to understand the concepts learnt in the class.
- The course helps students to be industry ready in terms of processes, tools, and terminologies from the Agile and DevOps point of view.
Course outcomes
| CO1 | Understand process models and apply Agile methodologies for proficient software process management. |
|---|---|
| CO2 | Apply requirement engineering principles to analyze, model, and validate requirements for effective software solutions. |
| CO3 | Design and implement robust software architectures and intuitive user interfaces, following industry best practices. |
| CO4 | Implement comprehensive testing strategies to ensure high software quality. |
| CO5 | Utilize industry standard tools and Scrum for efficient software project management and collaboration. |
CO to PO mapping
| CO | PO1 | PO2 | PO3 | PO4 | PO5 | PO6 | PO7 | PO8 | PO9 | PO10 | PO11 | PO12 | PSO1 | PSO2 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CO1 | 3 | 1 | 1 | 1 | ||||||||||
| CO2 | 3 | 2 | 3 | 1 | ||||||||||
| CO3 | 3 | 3 | 3 | 2 | 2 | 2 | 3 | 3 | 3 | |||||
| CO4 | 2 | 3 | 3 | 3 | 2 | 2 | 3 | 3 | 3 | 2 | 3 | 3 | ||
| CO5 | 3 | 3 | 1 | 2 | 3 | 3 | 3 |
Units
Unit 1
Process Models and Agile Overview: Overview of Process Models, Introduction to Agile, Agile Manifesto, Principles of Agile Manifesto.
Agile Methodologies: Scrum, XP, Lean, Kanban.
Agile Requirements: User Personas, Story Mapping, User Stories, Estimating and Prioritizing Stories, INVEST, Acceptance Criteria, Definition of Done, Release Planning.
Key Aspects of Scrum: Product Owner, Scrum Master, Team, Manager in Scrum, Product Backlog.
Scrum Process Flow: Product Backlog, Sprint Backlog, Scrum Meetings, Demos.
How Sprint Works: Sprint Planning, Daily Scrum Meeting, Updating Sprint Backlog, Burndown Chart, Sprint Review, Sprint Retrospective.
Scrum Metrics: Velocity, Burndown, Defects Carried Over.
Unit 2
Traditional Process Models: Waterfall, Incremental, Evolutionary, Concurrent.
Requirements Engineering: Tasks Initiation, Elicitation, Developing Use Cases, Building the Analysis Model, Negotiation, Validation, Requirements Modeling, Scenario Based Methods, UML Models, Data Models.
Design Engineering: Design Concepts, Design Models, Software Architecture, Architectural Styles and Patterns, Architectural Design, Refining Architecture into Components.
User Interface Design: Golden Rules, User Interface Analysis and Design, Interface Analysis, Interface Design Steps.
Unit 3
Testing Strategies and Tactics: Unit Testing, Integration Testing, Validation and System Testing, DevOps.
Syllabus coverage in the lecture plan
Session numbers refer to the lecture sessions.
| Syllabus topic | Sessions | Treatment |
|---|---|---|
| Overview of process models; Waterfall, incremental, evolutionary, concurrent | 1 | Waterfall and the V model, then incremental, prototyping, spiral, and concurrent models as a survey of 15 to 20 minutes. There is no worked comparison exercise and no deep spiral risk analysis. The lecture notes carry the full detail for independent study. Quiz 1 and the midterm assess each model at the level of recognition, trade offs, and suitability. |
| Agile, Agile Manifesto, principles | 2 | Full session. |
| Scrum, XP, Lean, Kanban | 3 to 8 | Scrum in sessions 3 to 6; XP, Lean, and Kanban compared in session 7; test driven development and pair programming in session 8. |
| Key aspects of Scrum, including Manager in Scrum | 3 | The role of management around a Scrum team is treated alongside the Product Owner, Scrum Master, and Development Team. |
| Scrum process flow, how a sprint works, Scrum metrics | 4 to 6 | Sprint planning, daily scrum, sprint review, and retrospective in sessions 4 and 5; velocity, burndown, and defects carried over in session 6, practiced in the lab sprints. |
| Agile requirements | 11 to 15 | Requirements engineering tasks are taught inside the Agile requirements sessions. |
| Requirements engineering, analysis model, use cases, scenario based methods, UML, data models | 11, 17 to 20 | Modeling with emphasis on reviewing and validating models, including AI generated models. |
| Design concepts, design models, architecture, styles and patterns, components | 22 to 28 | Tutorial in session 28. |
| User interface design | 29 to 30 | Golden rules, then analysis and design steps. |
| Unit testing | 10 | One session, taught early. Test design, test doubles, coverage, and tests as the oracle for human and AI written code. Students already program, so no test framework is taught. |
| Integration, validation, and system testing | 31 to 32 | Followed by regression and automation, non functional testing, and code review in sessions 33 to 35. |
| DevOps | 37 to 41 | Five sessions, with a tutorial in session 43. |
Textbook
Roger S. Pressman and Bruce R. Maxim. 2019. Software Engineering: A Practitioner’s Approach (9th ed.). McGraw Hill Education.
We recommend the prescribed textbook for reading, learning, and exam preparation. The slides are only for our discussion in the session, and they point you to further reading.
References
- [1]James A. Crowder and Shelli Friess. 2015. Agile Project Management: Managing for Success. Springer International Publishing.
- [2]Andrew Stellman and Jennifer Greene. 2015. Learning Agile: Understanding Scrum, XP, Lean, and Kanban. O’Reilly Media.
- [3]Janet Gregory and Lisa Crispin. 2016. More Agile Testing: Learning Journeys for the Whole Team. Addison-Wesley Professional.
- [4]Kenneth S. Rubin. 2012. Essential Scrum: A Practical Guide to the Most Popular Agile Process. Addison-Wesley.
- [5]Mike Cohn. 2004. User Stories Applied: For Agile Software Development. Addison-Wesley Professional.
Additional reading
These titles go with the sessions that list an AR number. They are suggested reading, not required.
- AR1Addy Osmani. 2025. Beyond Vibe Coding: From Coder to AI-Era Developer. O’Reilly Media.
- AR2John Berryman and Albert Ziegler. 2024. Prompt Engineering for LLMs: The Art and Science of Building Large Language Model–Based Applications. O’Reilly Media.
- AR3Chip Huyen. 2025. AI Engineering: Building Applications with Foundation Models. O’Reilly Media.
- AR4Titus Winters, Tom Manshreck, and Hyrum Wright. 2020. Software Engineering at Google: Lessons Learned from Programming Over Time. O’Reilly Media.
- AR5David Farley. 2021. Modern Software Engineering: Doing What Works to Build Better Software Faster. Addison-Wesley Professional.
- AR6Nicole Forsgren, Jez Humble, and Gene Kim. 2018. Accelerate: The Science of Lean Software and DevOps. IT Revolution Press.
- AR7Ken Schwaber and Jeff Sutherland. 2020. The Scrum Guide. Available at scrumguides.org.