SE Syllabus
SE Syllabus
L T P S J C
CSEN1131 SOFTWARE ENGINEERING
3 0 2 0 0 4
Pre-requisite CSEN1011:Problem Solving and Programming with C
Co-requisite None
Preferable
None
exposure
Course Description:
The purpose of this course is to impart knowledge on the basic principles of software engineering
and enabling the learner to understand software lifecycle stages. Systematic development of
software products or solutions is emphasized throughout the course to enable the student ensure
quality of development activities.
UNIT 5 9 hours
Software Management - Planning for software development
Estimation of time, resources, the cost for software development: COCOMO, Function
Point, Putnam Resource Allocation Models
Planning activities and re-planning, Risk Analysis
Release mechanisms, Configuration Management, Licensing methods and Maintenance
Software Life Cycle Management - planning, tracking, communication, negotiation,
delivery, quality aspects.
2. Develop weather modeling using the quadratic model in teams of 5 using Waterfall, Iterative,
Agile modes
3. a. Teams of 5 to work on gathering requirements for different simple projects related to
University and student activities
b. Represent requirements in terms of lists, use cases, scenarios (UML)
c. try simple architecture and design of modules. Represent in activity, sequence, collaboration
diagrams(UML)
Lab Infrastructure:
1. Eclipse, Visual Studio, SQL Server, MS Access, Oracle
2. StarUML /RationalPro, jira
TextBooks:
1. Ian Sommerville, “Software Engineering”, 10th Edition, Pearson Education, 2015 (overall – Part
I: 1 to 9, Part IV: parts of 23 to 25 )
2. Klaus Pohl, Chris Rupp, “Requirements Engineering Fundamentals” 2nd Edition, RockyNook,
2015.
3. Rajib Mall, Fundamentals of Software Engineering, 4/e, PHI, 2009. (for metrics))
4. K. K. Aggarwal & Yogesh Singh, “Software Engineering”, 3rd Edition, New Age International,
2008. (for metrics)
5. Steve Mcconnell, “Code complete”, 2nd Edition, Microsoft Press, 2004, Print 2015 (for design)
6. Frederic P. Brooks, “The Mythical Man-Month: Essays on Software Engineering”, Addison-
Wesley,1995, print 2010 (for project management)
References:
1. Michael R Blaha, James R Rumbaugh, “Object-Oriented Modeling and Design with UML”, 2nd
Edition,Pearson Education, 2005
2. Axel van Lamsweerde, “Requirements Engineering” Wiley Publications, 2009
3. http://vlabs.iitkgp.ernet.in/se/
4. http://softwarecost.org/tools/COCOMO/
Course Outcomes:
After successful completion of the course the student will be able to:
1. Demonstrate understanding of the process of Software Development
2. Determine Suitability of processes for varying software applications development
3. Differentiate Development phases through the life cycle of software
4. Reflect on design choices and development standards
5. Check and verify software quality from requirements to release of software and across versions
CO-PO Mapping:
PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10 PO11 PO12 PSO1 PSO2 PSO3
CO1 3 1 2
CO2 3 2 2 2
CO3 2 2 1
CO4 3 2
CO5 3 2 2 2
APPROVED IN:
BOS : 06-09-2021 ACADEMIC COUNCIL: 01-04-2022
SDG Justification: