Lovely Professional University, Punjab

Course Code Course Title Course Planner Lectures Tutorials Practicals Credits
CAP509 SOFTWARE ENGINEERING 11579::Deepak Mehta 3 0 0 3
Course Weightage ATT: 5 CA: 25 MTT: 20 ETT: 50 Exam Category: 55: Mid Term Exam: All Subjective – End Term Exam: All
Subjective
Course Orientation KNOWLEDGE ENHANCEMENT

TextBooks ( T )
Sr No Title Author Publisher Name
T-1 AN INTEGRATED APPROACH TO PANKAJ JALOTE NAROSA PUBLISHING HOUSE
SOFTWARE ENGINEERING
Reference Books ( R )
Sr No Title Author Publisher Name
R-1 SOFTWARE ENGINEERING: A ROGER S. PRESSMAN MCGRAW HILL EDUCATION
PRACTITIONER'S APPROACH
R-2 FUNDAMENTALS OF SOFTWARE RAJIB MALL PRENTICE HALL
ENGINEERING
Other Reading ( OR )

Sr No Journals articles as Compulsary reading (specific articles, complete reference)

OR-1 www.bcs.org/content/ConWebDoc/3063 , ,
OR-2 user.it.uu.se/~carle/softcraft/notes/Motivation.pdf ,
OR-3 https://www.comp.glam.ac.uk/staff/dwfarthi/projman.htm#notes ,

Relevant Websites ( RW )
Sr No (Web address) (only if relevant to the course) Salient Features
RW-1 http://www.tutorialspoint.com/software_testing/testing_overview.htm Complete details regarding software testing

RW-2 softwaretestingfundamentals.com/verification-vs-validation/ Information on validation and verification

Audio Visual Aids ( AV )

Sr No (AV aids) (only if relevant to the course) Salient Features
AV-1 http://nptel.ac.in/courses/106101061/1 It is a video on Introduction of Software Engineering Challaneges
AV-2 http://nptel.ac.in/courses/106101061/2 It is a video on Introduction of Software Engineering
AV-3 http://nptel.ac.in/courses/106101061/4 It is a video on different phases of software engineering

An instruction plan is only a tentative plan. The teacher may make some changes in his/her teaching plan. The students are advised to use syllabus for preparation of all examinations. The students are expected to keep themselves
updated on the contemporary issues related to the course. Upto 20% of the questions in any examination/Academic tasks can be asked from such issues even if not explicitly mentioned in the instruction plan.
 LTP week distribution: (LTP Weeks)
Weeks before MTE 7
Weeks After MTE 7
Spill Over (Lecture) 7

Detailed Plan For Lectures

Week Lecture Broad Topic(Sub Topic) Chapters/Sections of Other Readings, Lecture Description Learning Outcomes Pedagogical Tool Live Examples
Number Number Text/reference Relevant Websites, Demonstration/
books Audio Visual Aids, Case Study /
software and Virtual Images /
Labs animation / ppt
etc. Planned
Week 1 Lecture 1 Introduction to software T-1 OR-1 L1 Introductory Lecture L1 Student will learn Demonstration A thing or
engineering(problem and learn about objective and need of person that is
domain) paradigms L2 To this subject and learn the result of an
understand about paradigms and action or process
characteristics of applications. L2
software development Student shall be able
to understand
inherent basic
characteristics of
software
development.
Lecture 2 Introduction to software T-1 AV-2 Discusses software Student will learn Demonstration
engineering(software engineering challenges software engineering
engineering challenges) challenges
Lecture 3 Introduction to software T-1 AV-2 Discusses software Student will learn Demonstration
engineering(software engineering approach software engineering
engineering approach) approach
Week 2 Lecture 4 Software process models T-1 AV-1 Describe characteristics Student will learn Demonstration
(desired characteristics of of software process characteristics of
software process) software process
Lecture 5 Software process models T-1 OR-2 Discusses waterfall Student shall learn Demonstration Flo of water
(waterfall model) R-1 model classical SDLC from top to
model. bottom
Lecture 6 Software process models T-1 Describes prototyping Student will learn Demonstration
(prototyping model) R-1 and iterative prototyping and
development iterative development
Software process models T-1 Describes prototyping Student will learn Demonstration
(iterative development) R-1 and iterative prototyping and
development iterative development
Week 3 Lecture 7 Software requirements T-1 OR-3 Makes student Student will Demonstration
analysis and specification understand need for SRS understand need for
(need for SRS) and requirement SRS and requirement
process, process,

An instruction plan is only a tentative plan. The teacher may make some changes in his/her teaching plan. The students are advised to use syllabus for preparation of all examinations. The students are expected to keep themselves
updated on the contemporary issues related to the course. Upto 20% of the questions in any examination/Academic tasks can be asked from such issues even if not explicitly mentioned in the instruction plan.
Week 3 Lecture 7 Software requirements T-1 OR-3 Makes student Student will Demonstration
analysis and specification understand need for SRS understand need for
(requirement process) and requirement SRS and requirement
process, process,
Lecture 8 Software requirements R-2 AV-3 Discusses requirement Student will learn Demonstration
analysis and specification gathering process. requirement
(requirement gathering) gathering process.
Lecture 9 Software requirements T-1 RW-1 Discusses problem Student will learn Demonstration
analysis and specification R-2 analysis problem analysis
(problem analysis)
Week 4 Lecture 10 Software requirements T-1 Characteristics of an Student will learn Demonstration
analysis and specification R-2 SRS characteristics of an
(characteristics of an SRS) SRS
Lecture 11 Software requirements T-1 RW-2 Describes components Student will learn Demonstration
analysis and specification of an SRS about components of
(components of an SRS) an SRS
Lecture 12 Software requirements T-1 Discusses structure of a Student will learn Demonstration Format for SRS.
analysis and specification requirements document structure of a
(structure of a requirements requirements
document) document
Week 5 Lecture 13 Function-oriented design T-1 Discusses function Student will learn Demonstration
(modularity) oriented design function oriented
design strategies.
Function-oriented design T-1 Discusses function Student will learn Demonstration
(top-down and bottom-up oriented design function oriented
strategies) design strategies.
Lecture 14 Function-oriented design T-1 AV-3 Discusses types of coupling and its types Demonstration Inter
(coupling) R-2 coupling dependency
among
activities.
Lecture 15 Function-oriented design T-1 OR-1 Discusses types of Student will learn Demonstration
(cohesion) R-2 AV-3 cohesion types of cohesion

Week 6 Lecture 16 Test 1

Lecture 17 Design notation and T-1 OR-2 Drawing of structure Student will learn Demonstration
specification(structure OR-3 charts drawing of structure
charts) charts
Lecture 18 Design notation and T-1 AV-1 Discusses specification Student will learn Demonstration
specification(specification) of design specification of
design
Week 7 Lecture 19 Design notation and T-1 RW-1 Drawing data flow Student will learn Demonstration
specification(data flow R-2 diagram drawing data flow
diagram) diagram

SPILL OVER
Week 7 Lecture 20 Spill Over

An instruction plan is only a tentative plan. The teacher may make some changes in his/her teaching plan. The students are advised to use syllabus for preparation of all examinations. The students are expected to keep themselves
updated on the contemporary issues related to the course. Upto 20% of the questions in any examination/Academic tasks can be asked from such issues even if not explicitly mentioned in the instruction plan.
Week 7 Lecture 21 Spill Over

MID-TERM
Week 8 Lecture 22 Coding(programming T-1 OR-3 Describes programming Student will learn Demonstration
principles and guidelines) principles and programming
guidelines principles and
guidelines
Lecture 23 Coding(common coding T-1 RW-2 Discusses common Student will learn Demonstration
errors) coding errors common coding
errors
Lecture 24 Coding(structured T-1 OR-1 Discusses structured Student will learn Demonstration
programming) programming concepts structured
programming
concepts
Week 9 Lecture 25 Coding(information hiding) T-1 OR-3 Defines information Student will learn Demonstration
hiding information hiding
concepts
Lecture 26 Coding(some programming T-1 RW-1 Shows some Student will learn Demonstration
practices) programming practices some programming
practices
Lecture 27 Coding(coding standards) T-1 AV-2 Discusses coding Student will learn Demonstration
standards and coding coding standards and
process coding process
Coding(coding process) T-1 AV-2 Discusses coding Student will learn Demonstration
standards and coding coding standards and
process coding process
Week 10 Lecture 28 Testing(difference among T-1 OR-1 Shows difference among Student will learn Demonstration
error fault and failure) error fault and failure, difference among
test oracles error fault and
failure, test oracles
Testing(test oracles) T-1 OR-1 Shows difference among Student will learn Demonstration
error fault and failure, difference among
test oracles error fault and
failure, test oracles
Lecture 29 Test 2
Lecture 30 Testing(test cases) T-1 RW-1 Discusses test criteria Student will learn to Demonstration
decide test criteria
Testing(test criteria) T-1 RW-1 Discusses test criteria Student will learn to Demonstration
decide test criteria
Week 11 Lecture 31 Testing(black box testing) T-1 AV-3 Elaborates black box Student will learn Demonstration
R-1 testing and its types. about black box
testing
Lecture 32 Testing(white box testing) T-1 AV-3 Discusses white box Student will learn Demonstration
R-1 testing and its types white box testing and
its types

An instruction plan is only a tentative plan. The teacher may make some changes in his/her teaching plan. The students are advised to use syllabus for preparation of all examinations. The students are expected to keep themselves
updated on the contemporary issues related to the course. Upto 20% of the questions in any examination/Academic tasks can be asked from such issues even if not explicitly mentioned in the instruction plan.
Week 11 Lecture 33 Testing(levels of testing) T-1 AV-3 Discusses levels of Student will learn Demonstration
testing about levels of testing
Week 12 Lecture 34 Test 3
Lecture 35 Software testing process(test T-1 OR-1 Creation of test plan Student will learn ho Demonstration Planning a event
plan) to create test plan
Lecture 36 Software testing process(test T-1 AV-2 Discusses test case Student will learn test Demonstration
case specifications) specifications and test case specifications
case execution and and test case
analysis execution and
analysis
Software testing process(test T-1 AV-2 Discusses test case Student will learn test Demonstration
case execution and analysis) specifications and test case specifications
case execution and and test case
analysis execution and
analysis
Week 13 Lecture 37 Software testing process T-1 AV-2 Discusses defect logging Student will learn Demonstration
(defect logging and tracking) and tracking defect logging and
tracking
Lecture 38 Software maintenance and R-1 AV-3 Discusses various types Student will learn Demonstration
metrics(types of R-2 of maintenance various types of
maintenance) maintenance
Lecture 39 Software maintenance and T-1 OR-3 elaborates function Student will learn Demonstration
metrics(function points) R-1 points calculation function points
calculation
Week 14 Lecture 40 Software maintenance and T-1 RW-2 Describes COCOMO Student will learn Demonstration
metrics(COCOMO model) model calculation. COCOMO model
calculation.

SPILL OVER
Week 14 Lecture 41 Spill Over
Lecture 42 Spill Over
Week 15 Lecture 43 Spill Over
Lecture 44 Spill Over
Lecture 45 Spill Over

Scheme for CA:

CA Category of this Course Code is:A0203 (2 best out of 3)

Component Weightage (%)

Test 50
Test 50

An instruction plan is only a tentative plan. The teacher may make some changes in his/her teaching plan. The students are advised to use syllabus for preparation of all examinations. The students are expected to keep themselves
updated on the contemporary issues related to the course. Upto 20% of the questions in any examination/Academic tasks can be asked from such issues even if not explicitly mentioned in the instruction plan.
 Test 50

Details of Academic Task(s)

Academic Task Objective Detail of Academic Task Nature of Academic Academic Task Marks Allottment /
Task Mode submission
(group/individuals) Week
Test 1 To evaluate the Introduction to software engineering, Software process models, Individual Offline 30 5/6
student performance Software requirements analysis and specification

Test 2 To evaluate the Function-oriented design, Design notation and specification, coding Individual Offline 30 9 / 10
student performance
Test 3 To evaluate the Testing, Testing process, maintenance and metrics Individual Offline 30 11 / 12
student performance

An instruction plan is only a tentative plan. The teacher may make some changes in his/her teaching plan. The students are advised to use syllabus for preparation of all examinations. The students are expected to keep themselves
updated on the contemporary issues related to the course. Upto 20% of the questions in any examination/Academic tasks can be asked from such issues even if not explicitly mentioned in the instruction plan.