AGILE SOFTWARE ENGINEERING Credit

Course Code L T P C
Version NEP-V-1.1 3 0 0 3
Pre-requisites/ Expo-
Basic knowledge of software development
sure
Co-requisites Nil
Approved on (BOS)

Assessment Scheme:

Theory

Components Continuous Assessment (CA) [For- End Semester Assessment (ESA)

Course Description:
This course provides an in-depth understanding of software engineering principles and practices
across the software development life cycle. It covers software process models, metrics, and project
planning techniques to ensure effective cost and resource management. Students will learn require-
ment analysis, design methodologies, coding practices, and UML modeling for structured and ob-
ject-oriented development. The course emphasizes software reliability, testing strategies, debug-
ging, and maintenance approaches to enhance software quality. By the end, learners will be able to
apply standards, tools, and modern engineering techniques for developing reliable and maintainable
software systems.
Course Objectives:
The objective of this course is to:
1. Introduce the fundamental concepts, principles, and practices of software engineering.
2. Understand software development life cycle (SDLC) models and their applicability.
3. Develop skills in requirements analysis, system design, coding, testing, and maintenance.
4. Apply software project management techniques including effort estimation, scheduling, and risk
management.
5. Emphasize software quality assurance, standards, and metrics for reliable system development.
Course Outcomes:
On completion of this course, the students will be able to:

CO No Statement BT Levels
Explain software engineering principles, software development life cy- L1, L2
CO1 cle (SDLC) models, Agile methodologies, Scrum practices, and soft-
ware quality standards used in software development.
Apply project management principles including software metrics, cost L3, L4
CO2
estimation models (COCOMO, Putnam), and risk management.
 Analyze and specify software requirements, and design systems using L3, L4
CO3 function-oriented, object-oriented design approaches.

Apply testing techniques and reliability models to ensure software L3, L4

Detailed Syllabus:
Number
Modules Blooms level*
of Hours
Module 1: Introduction
Introduction Software life cycle models: Waterfall, Prototype, Evolutionary
and Spiral models, Overview of Quality Standards like ISO 9001, SEI-CMM.

Agile Manifesto and Agile Principles, Scrum Framework, Scrum Roles and
Responsibilities, Scrum Artifacts, Scrum Events (Sprint, Sprint Planning, L1, L2 12
Daily Scrum, Sprint Review, Sprint Retrospective), User Stories and Accep-
tance Criteria, Product Backlog Management, Sprint Backlog Management,
Story Mapping, Estimation Techniques (Planning Poker, Story Points, T-Shirt
Sizing), Velocity and Burndown Charts, Kanban Methodology, Lean Software
Development, Extreme Programming (XP), Pair Programming.
Module 2: Software Project Management
Software Metrics and Project Planning, Size Metrics like LOC, Token Count,
Function Count, Design Metrics, Data Structure Metrics, Information Flow L2, L3, L4 08
Metrics. Cost estimation, static, Single and multivariate models, COCOMO
model, Putnam Resource Allocation Model, Risk management.
Module 3: Software Requirement Analysis and Design
Software Requirement Analysis, design and coding Problem Analysis, Soft-
ware Requirement and Specifications, Behavioural and non-behavioural re-
quirements, Software Prototyping Cohesion & Coupling, Classification of Co- L2, L3, L4 08
hesiveness & Coupling, Function Oriented Design, Object Oriented Design,
User Interface Design Top-down and bottom-up Structured programming, In-
formation hiding.
Module 4: Software Reliability, Testing and Maintenance
Software Reliability, Testing and Maintenance Failure and Faults, Reliability
Models: Basic Model, Logarithmic Poisson Model, Software process, Func-
tional testing: Boundary value analysis, Equivalence class testing, Structural
L2, L3, L4 9
testing: path testing, Data flow and mutation testing, unit testing, integration
and system testing, Debugging, Testing Tools, & Standards. Management of
maintenance, Maintenance Process, Maintenance Models, Reverse Engineer-
ing, Software RE-engineering
Module 5: UML
UML Introduction to UML Use Case Diagrams, Class Diagram: State Diagram
in UML Activity Diagram in UML Sequence Diagram in UML Collaboration
L2, L3, L4 8
Diagram in UML, Domain, Component Diagram and Deployment Diagram

*Bloom’s Level: L1: Remember; L2: Understand; L3: Apply; L4: Analyze L5: Evaluate, L6: Create

Textbooks:
● K. K. Aggarwal, Yogesh Singh, Software Engineering, New Age International.
● R. S. Pressman, Software Engineering – A Practitioner’s Approach, McGraw Hill Int.
● Robert C. Martin, Agile Software Development: Principles, Patterns, and Practices.
References:
● R. Fairley, Software Engineering Concepts, Tata McGraw Hill.
● P. Jalote, An Integrated approach to Software Engineering, Springer.
● Stephen R. Schach, Classical & Object-Oriented Software Engineering, McGraw Hill Higher
Education.
● James Peter, W. Pedrycz Software Engineering, John Wiley & Sons.
● Sommerville, Software Engineering, Pearson Education.
● Ken Schwaber and Mike Beedle, Agile Software Development with Scrum

Modes of Evaluation: Quiz/Assignment/ Seminar/Written Examination

Examination Scheme:

Components A CT1 & CT2 S/V/Q HA EE

CT: Class Test, HA: Home Assignment, S/V/Q: Seminar/Viva/Quiz, EE: End Semester Examination; Att: At-
tendance

CO–PO–PSO Mapping
PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PSO1 PSO2 PSO3

CO1 3 3 3 2 - 2 1 2 3 - -

CO2 3 3 1 3 2 2 3 3 3 - 3

CO3 3 3 3 3 - 2 1 2 3 - -

CO4 3 3 3 3 - 2 1 2 3 - -

CO5 3 3 3 3 - 2 1 2 3 - -

Overall 3 3 2.6 2.8 2 2 1.4 2.2 3 - 3

1: weakly related, 2: moderately related and 3: strongly related