CSC3003 Software Engineering

L T P J C
3 0 2 0 4

Prerequisite: CSC2003
Preamble
This course is an introductory course to software engineering principles. It is used to create software
based on a set of procedures so that it can comply with predefined standards.
Objective of the course
 To teach the concepts of process, product and project.
 To elucidate the knowledge of requirement analysis.
 To provide the knowledge of software design and testing.

Expected Outcome
After successfully completing the course the student should be able to 1. Perform requirement analysis.
2. Write software requirement specification.
3. Model software system development.
4. Perform testing on the developed software.
Module Topics L Hrs SLO
1 Introduction to Software Engineering
Software engineering problem - Software process models - 6 2
Characteristics of a software process.
2 Requirement Engineering
Requirements elicitation - Requirements analysis - Functional and Non- 6 9
functional requirements.
3 Requirement Specification
Modelling technique (Use case model) - IEEE SRS standard - 5 12
requirement specification.
4 Planning a Software project 6 9
Cost Estimation – Project Scheduling - Staffing and Personal planning.
5 Software Design
Design Principles - Module level concepts (WBS) - Design notation and 6 12
specification.
6 Advanced Design
6 2
Function oriented design – Object oriented design.
7 Software Testing
Testing process - Test plan - Black-box and white-box testing – Unit - 5 9
Integration.
8 Maintenance and Quality
5 12
Characteristics of maintainable software – Capability Maturity Model.
Lab 30 2, 9,
1. Role of Software 12
2. Identify the problem related to software crisis for a given scenario
3. Identify suitable software development model for the given scenario
4. Identify the various requirement development activities viz. elicitation, analysis,
specification and verification for the given scenarios.
5. Identify the various elicitation techniques and their usage for the Banking case
study

Proceedings of the 37th Academic Council [16.6.2015] 130

6. Classify the requirement into functional and non-functional requirements.
7. Identify the elements in software Requirements Specification document.
8. To verify the requirements against the quality attributes.
9. Identify the elements and relationship by analysing the class diagram of Easy
Shop Retail Application case study.
10. Identify the design principle that is being violated in relation to the given
scenario.

TextBooks
1. Pankaj Jalote, An Integrated Approach to Software Engineering, Narosa Publishing House, 3rd Edition,
Reprint 2014.
Reference Books
1. R. S. Pressman, Software Engineering, A Practitioner’s Approach, McGraw Hill Education India Pvt
Ltd, 7th Edition 2014.
2. Ian Sommerville, "Software Engineering", Pearson Education, 9th Edition 2014.

Proceedings of the 37th Academic Council [16.6.2015] 131