SOFTWARE ENGINEERING> <(SE)>

COURSE 23CA5207 MODE LTPS 2-1-0-0 PRE- NIL

CODE REQUISITE

Course Outcomes
CO# CO Description BTL PO Mapping
CO1 Understand the fundamental concept of software and 3 PO1, PO2, PO3
software engineering, as well as the nature of the
process, including numerous software models with
reverse engineering.
CO2 Apply the demands of users and which methodology 3 PO2, PO3, PO4
will be best suited to meet those needs. They can
employ extreme software models to elicit and validate
the user's needs. They can also use agile
methodologies to design and develop project-based
softwares
CO3 Apply various software methodologies of Scrum, 4 PO2, PO3, PO5
Kanban and SAFe Methodology for developing user-
friendly software and also they can able to analyse
various software projects by using project Monitoring
Tools such as JIRA, Design Patterns - Architectural
Patterns - Model Driven Architecture.
CO4 Analyze numerous testing methodologies for testing 4 PO1, PO2, PO3
diverse software, as well as risk management, project
planning, and estimating in order to design and analyse
any software project.

Syllabus
Module Software and Software Engineering, Nature of software, software application
1 domains, unique nature of web applications, software engineering, software
process, software engineering practice, SDLC, software myths. Process
Models: Generic process model, prescriptive process models, specialized
process models, unified process, personal and team process models, product
and process.
Module REQUIREMENTS -
2 Requirements Development Methodology - Specifying Requirements -
Eliciting Accurate Requirements -Documenting Business Requirements -
Defining User Requirements - Validating Requirements – Achieving
Requirements Traceability - Managing Changing Requirements - Reviews,
Walkthroughs, and Inspections, SRS Vs User Stories. Agile Modelling,
Extreme Programming.
Module Scrum, Kanban, SAFe Methodology, Project Monitoring Tool using JIRA,
3 Design Patterns - Architectural Patterns - Model Driven Architectures.

Module A strategic approach to software testing, strategic issues, test strategies for
4 conventional software, Black-Box and White-Box testing, validation testing,
system testing. RISK MANAGEMENT IN SOFTWARE ENGINEERING
PROJECTS - Project Planning and Estimation.
Reference Books:
Sl Title Author(s) Publisher Year
No
1 Object Oriented Software Timothy C Mc Graw Hill
Engineering: Practical Software Lethbridge &
Development using UML and Java. Robert,
Langaneire,
2 The Unified Modeling Language Grady Booch, Addison-
User Guide James Rumbaugh Wesley
and Ivar Jacobson
3 Software Engineering; A Roger SPressman
Practitioner’s Approach
4 Object-Oriented Software Bernd Bruegge 2nd Edition,
Engineering: Using UML, Patterns and Allen H. Pearson
and Java Dutoit Education
Global Certifications:
Mapped Global Certifications:
Certific Form
Sl ation Proctor at of Exam
URL of the Certification
N Provide ed the Provide
o Title r (Y/N) Exam r
SCRUM SCRUM
ORGAN OBJE ORGAN https://www.scrum.org/
1
SCRU IZATIO CTIV IZATIO assessments/professional-scrum-
M N YES E N master-i-certification
SAFe
Certifi Scaleda OBJE Scaleda
2
cation gile.co CTIV gile.co https://scaledagile.com/safe-
s m Yes E m certification/

Tools used in Practical / Skill:

Sl No Tool Name Parent Industry Open Source/ Commercial
1 STAR UML NA
Open Source
2 JIRA TOOL NA Open Source

Evaluation Components:
Evaluation Component Weightage Total
Active Learning 6 26
In-Sem Home Assignment 5
Formative Tutorial Continuous Evaluation 15

In-Sem In-Sem 1 17 34
Summative In-Sem 2 17
40 40
End-Sem
Summative