Punjab University College of Information Technology, University of the Punjab 1-7

Course Outline
Title Software Engineering
Code CS – 3901-3
3
Theory/week:
Weight: 3 Cr. Hrs.
Contact Hours: 3 Hrs.
Lectures: 2
Credit Hours Duration: 1.5 Hrs.
Lab/week:
Weight 0 Cr. Hrs.
Contact Hours 0 Hrs.
Labs. 0
Duration 0 Hrs.
Prerequisite CS – 2402 – 4 Object-Oriented Programming
Prerequisite Skills • Understanding of basic programming concepts.
Follow Up CS – 3902-3: Object Oriented Analysis & Design
Category Major
• Application of software engineering elements to the development of software in any computing application
domain where professionalism, quality, schedule, and cost are important in producing a software system.
• To convey the importance and need of software engineering
• To discuss different software development models appropriate for the development and maintenance of
Aims and Objectives software products
• To introduce the basic project management concepts for the development of a high-quality product
• To impart comprehensive knowledge regarding software development lifecycle
• To demonstrate, with justification, an appropriate set of tools to support the development of a range of
software projects
Punjab University College of Information Technology, University of the Punjab 2-7

• The students will recognize the importance and need of software engineering to cope with the modern trends in
software industry
• The students will have the knowledge of all phases of software life cycle including the artifacts that are
Learning Outcomes produced
• The students will be proficient enough to analyze, evaluate and apply a set of CASE tools
• The term project will enable the students to implement the software engineering concepts in a disciplined way,
to compete the local and international market
The Scope of Software Engineering: Definition, Motivation and Need, Software Characteristics and Applications. The
Software Process: Definition, Introduction to Software Development Life Cycle, Software Process Models. Project
Management Concepts: Essentials, 4Ps (People, Product, Process, Project); Software Measurement concepts:
Project, Process, Product and Software Quality Metrics, Software Cost Estimation techniques; Project Scheduling:
GANTT chart, Critical Path Method. Requirements Engineering: Definition, Requirements Elicitation, Requirement
Syllabus
Traceability, Requirements Analysis and Specification. Software Designing: Elementary Concepts, Data Design,
Software Architecture, Functional Independence, Interface Design, Component-level Design, Coding Standards.
Software Testing: Fundamentals, Verification & Validation, Testing Plan, Testing Techniques, White Box Testing and
Black Box Testing, Test Case Design, Unit Testing, Integration Testing, Validation Testing, System Testing, Debugging
practices.
Text Book/s A - Roger S. Pressman “Software Engineering- A practitioner’s approach”, 6th Ed.
A. Ian Sommerville “Software Engineering”, 6th Ed.
B. An integrated approach to software engineering by Pankaj Jalote
Reference Material C. Fundamentals of Software Engineering By Carlo Ghezzi
D. http://www.mhhe.com
E. http://www.sei-cmu.edu
Punjab University College of Information Technology, University of the Punjab 3-7

• Class facilities to Instructor and students for Lectures per Room

o 1 Network enabled PC
o 1 Multimedia
o 1 Whiteboard
o 1 Rostrum
o 1 Board marker/Month i.e. 4 Week Lectures (eight sessions)
o Max 45 students sitting facility
o CASE tools must be available in the lecture room as well as in labs.

Instructional • Evaluation and Support facilities

Aids/Resources o Announced Tests i.e. pre mid and pre final Testes should not be conducted during class hours
• Photocopy facility for different Handouts
o Subject description document that includes student version of course outline, prerequisite test and its
solution should be distributed in first class.
o Handout: - Required handouts as mentioned in lecture framework
o Quizzes and Solution: - Quizzes and their standard solution must be provided to students in handout
form after each quiz.
o Case Studies and Tutorials: - Description of case study and handout of each tutorial should be
provided.
Sessional 15% Project 10% Mid 35% Final 40% Total 100%
Assessment Criteria Tests/Assignment and Term Project 10 Final Paper
Mid Paper 35 100
Presentations 40

Marks division for sessional or project may vary on the basis of complexity of project or available time for project
Recommendations
execution and documentation.
 Punjab University College of Information Technology, University of the Punjab 4-7

Source
(Book-
Topic Chapter Recommendations for Learning
Week Lecture
No. Activities
Section
No.)
Introduction: A-2.1
The Scope of Software Engineering: Motivation
1 and need for software engineering, Definition of
Software Engineering, Introduction to software
1
engineering vocabulary
The Software: A-1.2, 1.3,
2 Software characteristics, software application, 1.5
Software Myths
A Generic View of Process: A-2.1,
3 Software Engineering: A layered technology, A 2.2,2.3
process framework, CMMI
2
Process Models: A-3.1, 3.2, Project Announced
4 Introduction, The Waterfall Model, Incremental 3.3-3.3.1
Process Models-The Incremental Model
Process Models: A-3.3.2, Case Study
5 The RAD Model, Evolutionary process models, 3.4, 3.4.1 Assignment 1 (Process Models)
Prototyping
3 Process Models: A-3.4.2, Test 1 (The software process)
The Spiral Model, A Final Comment on 3.4.4,
6
Evolutionary Processes, The Formal Methods 3.5.2, 4.2
Model, Introduction to Agile Process Models
 Punjab University College of Information Technology, University of the Punjab 5-7

Project Management: Handouts Project Proposal Announced

7 Project Management Concepts, Project
4 Management Lifecycle
Project Management: A-21.1,
8 The Management Spectrum: The people, The 21.2, 21.3,
product, The process, The project 21.4, 21.5
Estimation: A-15.2.1, Project Phase 1: Project Planning
Software Metrics: Metric, Measure, and 22.3, 23.6,
Indicator, Metric for software quality, 22.2,
9
Decomposition Techniques, Software 22.2.1,
5 Measurements, Size oriented metrics, Function 22.2.2
oriented metric
Metrics for Process and Project: A-22.2.2,
10 Function oriented Metrics, An example of FP 15.3.1,
based Estimation 23.6.4
COCOMO Model: Ref. 2
11
6 The COCOMO Model
Project Scheduling: Handouts Assignment 2 (Scheduling and
12
GANTT chart, Critical Path Method Costing)
LAB Session: Microsoft Project Handouts LAB session
13
Case Study
Requirements Engineering: A-7.1, 7.2, Project Phase 2: Software
7 Requirement gathering and fact finding 7.3, 7.4 Requirement Engineering
techniques Kendall & Test 2 (Scheduling, project
14
Kendall, management, and project metrics)
Ref. 1-
6.2.1
Requirement Elicitation: A-7.4, 7.5
15 FAST, QFD, Use – cases
8
Rational Rose 2002 overview
16 Pre Mid Review
 Punjab University College of Information Technology, University of the Punjab 6-7

Building the Analysis Model: A-8.1, 8.3,

17 Requirements Analysis, Data modeling concepts Handouts
(A-5th ed.)
9
Flow-oriented Modeling: A-8.6.1, Case Study
18 Creating a Data Flow Model Handouts
(A-5th ed.)
Behavioral Modeling: A-8.8,
The Control Specification, The Process 8.6.3,
Specification 8.6.4, B-
19
10 12,
Handouts
(A-5th ed.)
20 LAB Session: VISIO and ERWIN Handouts Case Study
Software Design: Design within the Context of A-9.1, 9.2, Test 3 (Analysis Modeling)
Software Engineering, Design Process and 9.3, Project Phase 3: Software Design
21
Design Quality, Design concepts Handouts
(A-5th ed.)
11 Software Design: Effective Modular Design A-9.4,
11.2.3,11.
22 23.4,
Handouts
(A-5th ed.)
Software Design: A-10.1,
Software Architecture, Architectural Styles, 10.3,10.6,
23
Mapping Requirements into software Handouts
12 architecture (A-5th ed.)
Software Design: A-10.6, Case Study
24 Transform Mapping, Transactional Mapping Handouts
(A-5th ed.)
 Punjab University College of Information Technology, University of the Punjab 7-7

Lab Session: VB- User Interface Design A-12.1, Lab Session

25 12.2, 12.4,
Handouts
Component-level Design: A-11.5 Project Phase 4: Software
13
Component-level design A-14.1, Implementation
26 Testing Tactics: 14.2, 14.6 Project Phase 5: Software Testing
Software Testing Fundamentals, Black Box
Testing
Testing Tactics: A-14.3,
27 White Box Testing, White Box testing with 14.4
example
Testing Strategies: A-13.1, Test 4 (Testing)
14
A strategic approach to software testing, 13.2, 13.3
28 Strategic Issues, Testing Strategies for
Conventional Software: Unit Testing,
Integration testing
Testing Strategies: A-13.3,
29 Integration Testing, Validation Testing, System 13.5, 13.6,
15
Testing, The art of debugging 13.7
30 Presentations on Final Project and viva Group Presentations
31 Presentations on Final Project and viva Group Presentations
16
32 Post Mid Review Interactive session