Text Books

  1. Roger Pressman, "Software Engineering: A Practitioners Approach, (6th Edition), McGraw Hill, 1997

Reference Books

  1. Sommerville, "Software Engineering, 7th edition", Adison Wesley, 1996
  2. Watts Humphrey, "Managing software process", Pearson education, 2003
  3. James F. Peters and Witold Pedrycz, "Software Engineering – An Engineering Approach", Wiley
  4. Mouratidis and Giorgini, "Integrating Security and Software Engineering–Advances and Future", IGP. ISBN – 1-59904-148-0
  5. Pankaj Jalote, "An integrated approach to Software Engineering", Springer/Narosa
  6. Fundamentals of Software Engineering by Rajib Mall, PHI-3rd Edition, 2009

dth, initial-scale=1.0"> Software Engineering (Theory & Lab)

Software Engineering (BTCS 503-18)

Course Outcomes

At the end of the course the student should be able to:

  1. CO1: Students should be able to identify the need for engineering approach to software development and various processes of requirements analysis for software engineering problems.
  2. CO2: Analyse various software engineering models and apply methods for design and development of software projects.
  3. CO3: Work with various techniques, metrics and strategies for Testing software projects.
  4. CO4: Identify and apply the principles, processes and main knowledge areas for Software Project Management.
  5. CO5: Proficiently apply standards, CASE tools and techniques for engineering software projects.

Detailed Syllabus

Module 1: Software Life Cycle and Requirements - CO1

Duration: 10 hours

Module 2: Software Design and Development - CO2

Duration: 8 hours

Module 3: Software Testing - CO3

Duration: 10 hours

Module 4: Software Project Management - CO4

Duration: 8 hours

Module 5: Software Quality and Maintenance - CO5

Duration: 6 hours

Text Books

Reference Books


Software Engineering Lab (BTCS 506-18)

List of Experiments

  1. Study and usage of OpenProj or similar software to draft a project plan
  2. Study and usage of OpenProj or similar software to track the progress of a project
  3. Preparation of Software Requirement Specification Document, Design Documents and Testing Phase
  4. Related documents for some problems
  5. Preparation of Software Configuration Management and Risk Management related documents
  6. Study and usage of any Design phase CASE tool
  7. To perform unit testing and integration testing
  8. To perform various white box and black box testing techniques
  9. Testing of a web site

Suggested Tools

Visual Paradigm, Rational Software Architect, Visio, Argo UML, Rational Application Developer etc. platforms.