Scribd
Upload
19 views

ASE Syllabus

This document outlines an advanced software engineering course that focuses on software processes, project management, quality assurance, estimation, and risk management. The course aims to help students understand software engineering processes, identify quality attributes, develop effective project plans based on requirements, and apply techniques like quality assurance, cost estimation, and risk prioritization. It is a 4 credit course with 60 contact hours that includes lectures and assignments. The syllabus covers topics like software processes, requirements engineering, quality management, project management concepts, and software process improvement.

Uploaded by

Fatema Taha
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
19 views

ASE Syllabus

This document outlines an advanced software engineering course that focuses on software processes, project management, quality assurance, estimation, and risk management. The course aims to help students understand software engineering processes, identify quality attributes, develop effective project plans based on requirements, and apply techniques like quality assurance, cost estimation, and risk prioritization. It is a 4 credit course with 60 contact hours that includes lectures and assignments. The syllabus covers topics like software processes, requirements engineering, quality management, project management concepts, and software process improvement.

Uploaded by

Fatema Taha
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

ADVANCED SOFTWARE ENGINEERING

Course Title: Advanced Software Engineering


Course Code: 22MCACE4012
Credits Units: 04 Contact Hours: 60 L-T-P: 4-0-0
IA: UE Weightage – 50 : 50 Pass Marks (IA & UE) - 20&20 Aggregate Pass Marks: 50
UE Question Paper Marks: 50

Course Objectives:
COB1 To understand the process and activities in Software Engineering.
COB2 To identify the quality attributes and techniques for quality assurance.
COB3 To develop the project plan effectively according to the collected requirements.

Course Outcomes:
At the end of the course, students will be able to

Course Bloom’s
Description
Outcome Taxonomy Level
Identify the suitable software process model to develop the software
CO 1 L2
systems.
CO 2 Illustrate project management principles to define perfect requirements. L3

CO 3 Applying quality assurance techniques to manage the software quality. L4


CO 4 Analyse the project scope and size to perform cost estimation. L5
CO 5 Prioritize the different levels of possible risks to maintain the project. L6

CO-PO-PSO Mapping (3-strong, 2-medium, 1-weak)

PO1 PO2 PO PO PO PO PO7 PO8 PO PO1 PO1 PO1 PSO1 PSO2


3 4 5 6 9 0 1 2
CO1 3 2 2 - 3 - - - - - - - 3 -
CO2 3 1 2 - 3 - - - - - - - 3 -
CO3 3 1 2 - 3 1 - - - - - - 3 -
CO4 3 1 2 - 3 1 - - - - 1 - 2 -
CO5 3 1 2 - 3 1 - - - - 1 - 2 -
Syllabus:

Tools/Soft
Module
Details COs POs ware/Data
(Hrs)
base Used
SOFTWARE PROCESS
Software and Software Engineering, The Nature of Software,
Software Engineering, The Software Process, Software Engineering PO1
Practice, Software Myths. PO2
PROCESS MODELS: A Generic Process Model, Process
I Assessment and Improvement, Prescriptive Process Models, PO3
CO1 -
(12 Hrs) Specialized Process Models, The Unified Process, Personal and Team
Process Models, Process Technology, Product and Process, Agile
Development: What is Agility?, Agility and the Cost of Change, Agile
Process, Other Agile Process Models, A Tool Set for the Agile
Process.

PROJECT MANAGEMENT PRINCIPLES PO2


PRINCIPLES THAT GUIDE PRACTICE: Software Engineering
Knowledge, Core Principles, Principles That Guide Each Framework PO3
II Activity (topics are like sentences).
UNDERSTANDING REQUIREMENTS : Requirements CO2 -
(12 Hrs)
Engineering, SRS Document, Establishing the Groundwork, Eliciting
Requirements, Developing Use Cases, Building the Requirements
Model, Negotiating Requirements, Validating Requirements.
CASE STUDY – ATM System
QUALITY MANAGEMENT PO1
Software Quality, Software Quality Dilemma, Achieving Software
Quality. PO2
REVIEW TECHNIQUES: Cost Impact of Software Defects, Defect PO3
III Amplification and Removal, Review Metrics and their uses. Formality
Spectrum, Informal Reviews, Formal Technical Reviews CO3 PO6 -
(12 Hrs)
SOFTWARE QUALITY ASSURANCE: Background Issues,
Elements of Software Quality Assurance, SQA Tasks, Goals, and
Metrics.
Test Management – Test Organization, Test Planning, Test
Reporting.
PROJECT MANAGEMENT CONCEPTS PO3
Management Spectrum, People, Product, Process, Project, WHH
Principle, Critical Practices.
PROJECT ESTIMATION: Observations on Estimation, Project
IV Planning Process, Software Scope and Feasibility, Resources,
Software Project Estimation, Decomposition Techniques, Empirical CO4 -
(12 Hrs)
Estimation Models, Estimation for Object-Oriented Projects,
Specialized Estimation Techniques.
PROJECT SCHEDULING: Basic Concepts, Project Scheduling,
Defining a Task Set for the Software Project, Defining a Task
Network, Scheduling, Earned Value Analysis.
Risk Management and Software Process Improvement PO1
V
RISK MANAGEMENT: Reactive versus Proactive Risk Strategies, CO5 -
(12 Hrs) Software Risks, Risk Identification, Risk Projection, Risk Refinement, PO3
Risk Mitigation, Monitoring, and Management, The RMMM Plan. PO7
MAINTENANCE AND REENGINEERING :Software
Maintenance, Software Supportability, Reengineering, Business
Process Reengineering, Software Reengineering, Reverse
Engineering, Restructuring, Forward Engineering
SOFTWARE PROCESS IMPROVEMENT: Introduction, The SPI
Process, The CMMI, People CMM, SPI Return on Investment.

TEXT BOOKS:

1 Pressman, (2019), “Software Engineering-A Practitioners approach”, Mc Graw


Hill,8th Edition.
2 Chauhan, Naresh (2010), “Software Testing : principles and practices”, Oxford
University Press, 1st Edition.

REFERENCE BOOKS:
1 Ian Sommerville (2007), Software Engineering, 8th Edition, Person Education Ltd., 2007.
2 Pfleeger (2001), Software Engineering Theory and Practice, 2nd Edition, Pearson
Education.
3 Waman S Jawadekar (2004) Software Engineering Principles and Practice, Tata McGraw
Hill.

You might also like