| PO1 | PO2 | PO3 | PO4 | PO5 | PO6 | PO7 | PO8 | PO9 | PO10 | PO11 | PO12 | PSO1 | PSO2 | PSO3 | ||
| K3 | K4 | K5 | K5 | K6 | - | - | - | - | - | - | - | K5 | K3 | K6 | ||
| CO1 | K4 | 3 | 2 | |||||||||||||
| CO2 | K3 | 3 | 2 | 2 | 2 | |||||||||||
| CO3 | K3 | 3 | 2 | 2 | 2 | 2 | 2 | |||||||||
| CO4 | K3 | 3 | 2 | 2 | 2 | 2 | ||||||||||
| CO5 | K2 | 2 | 1 | 1 | 1 | 1 | ||||||||||
| Score | 14 | 9 | 5 | 2 | 2 | 5 | 7 | |||||||||
| Course Mapping | 3 | 2 | 2 | 0 | 2 | 0 | 0 | 0 | 0 | 0 | 2 | 0 | 2 | 2 | 0 |
{{{credits}}}
| L | T | P | C |
| 3 | 0 | 0 | 3 |
- To understand the phases in a software project
- To understand fundamental concepts of requirements engineering and Analysis Modeling.
- To understand the various software design methodologies
- To learn various testing techniques and maintenance measures.
{{{unit}}}
| UNIT I | SOFTWARE PROCESS MODELS | 9 |
Introduction to software engineering; Principles and practices; Software Process: Generic process model – Perspective and specialized process models – Secure development lifecycle; Introduction to Agility: Agile process model.
{{{unit}}}
| UNIT II | PROJECT PLANNING AND MANAGEMENT | 9 |
Project planning process; Software Project Estimation: Decomposition techniques – Empirical estimation models – The make/buy decision – Project scheduling; Risk Management: Risk identification – Risk projection – Risk mitigation.
{{{unit}}}
| UNIT III | REQUIREMENTS ANALYSIS AND SPECIFICATION | 9 |
Software Requirements: Functional and non-functional – User requirements – System requirements – Software requirements document; Requirement Engineering Process: Feasibility studies – Requirements elicitation and analysis – Requirements validation – Requirements Management; Classical Analysis: Structured system analysis; Petri Nets.
{{{unit}}}
| UNIT IV | SOFTWARE DESIGN | 9 |
Design Concepts: Design process – Design concepts – Design model – Modeling principles; Architectural Design: Architectural Styles –Architectural Mapping using Dataflow; User Interface Design: The Golden rules – Interface Analysis – Interface Design; Design for security; Component Level Design: Designing Class based Components – Traditional Components.
{{{unit}}}
| UNIT V | TESTING AND MAINTENANCE | 9 |
Software Testing Fundamentals; Internal and External Views of Testing: White Box Testing – Basis Path Testing – Control Structure Testing– Black Box Testing – Unit Testing – Integration Testing – Regression Testing – Validation Testing – System Testing – Security Testing; Debugging; Software Implementation: Coding Practices and Principles; Maintenance: Types – Reengineering – Reverse Engineering – Restructuring.
\hfill Total Periods: 45
After the completion of this course, students will be able to:
- Understand principles of software engineering and choose an appropraite process model (K4)
- Manage project schedule, estimate project cost and effort required (K3)
- Perform requirements analysis and modeling (K3)
- Apply systematic procedure for software design (K3)
- Compare and contrast the various testing and maintenance activities (K2).
- Roger S Pressman, “Software Engineering – A Practitioner’s Approach”, McGraw-Hill International Edition, Seventh Edition, 2010.
- Ian Sommerville, “Software Engineering”, Pearson Education Asia,Nineth Edition, 2011.
- Rajib Mall, “Fundamentals of Software Engineering”, PHI Learning Private Limited, Third Edition, 2009.
- Pankaj Jalote, “Software Engineering, A Precise Approach”, Wiley India, 2010.
- Kelkar S A,“Software Engineering”, Prentice Hall of India, 2007.
- Stephen R Schach, “Software Engineering”, Tata McGraw-Hill Publishing Company Limited,2007.
- https://www.cisco.com/c/dam/en_us/about/doing_business/trust-center/docs/cisco-secure-development-lifecycle.pdf