DOC/LP/01/02.1.13
LP- IT2251
LESSON PLAN
LP Rev. No: 01
Sub Code & Name : IT2251 & SOFTWARE ENGINEERING AND
Date: 02.01.2013`
QUALITY ASSURANCE
Unit: I
Page 01 of 06
Branch: IT
Semester:IV
SOFTWARE PRODUCT AND PROCESS
Introduction – S/W Engineering Paradigm – Verification – Validation – Life Cycle Models –
System Engineering – Computer Based System – Business Process Engineering Overview –
Product Engineering Overview.
Objective:
To understand the fundamental concepts and life cycle models of software Engineering.
Session
No
Topics to be covered
Time
Allocation
Books
Referred
(Page
Numbers)
Teaching
Method
1
Introduction to Software Engineering
50m
1(33-48)
BB
2
S/W Engineering Paradigm
50m
1(33-48)
BB
3
Verification and Validation definition
Examples
50m
2(538-548)
BB
4
Life cycle models and Life Cycle
processes
50m
1(78-83)
2(87-103)
BB
5
Water fall, Incremental development
and RAD model
50m
6
Evolutionary models - Spiral model,
Prototyping model
50m
1(83-90)
BB
8
System Engineering -Computer based
system, System engineering hierarchy
50m
1(155-160)
2(47-55)
BB
9
Business Process Engineering
Product Engineering Overview.
[Type text]
–
50m
1(161-170)
2(29-36)
BB
DOC/LP/01/02.1.13
LP- IT2251
LESSON PLAN
LP Rev. No: 01
Sub Code & Name : IT2251 & SOFTWARE ENGINEERING AND
QUALITY ASSURANCE
Unit: II
Date: 02.01.2013
Page 02 of 06
Branch: IT
Semester: IV
SOFTWARE REQUIREMENTS
Functional and Non-Functional – Software Document – Requirement Engineering Process –
Feasibility Studies – Software Prototyping – Prototyping in the Software Process – Data –
Functional and Behavioral Models – Structured Analysis and Data Dictionary.
Objective:
To understand the Requirement elicitation and software prototyping.
Session
No
Topics to be covered
Time
Allocation
Books
Referred
(Page
Numbers)
Teaching
Method
10
Functional and non-functional
requirements.
50m
2(141-148)
BB
11
User and System requirements.
50m
2(149-156)
BB
12
Requirement engineering processFeasibility studies,
Requirements Elicitation and Analysis
50m
2(164-179)
BB
13
Requirements validation and
Management
50m
2(180-187)
BB
14
Software prototyping –
Prototyping in the software process
50m
3(172-180)
BB
15
Rapid prototyping techniques,
User interface prototyping
50m
3(181-189)
BB
16
Software Requirement documents.
50m
3(115-118)
BB/OHP
17
Analysis and modeling –
Data models,
Functional and behavioral models.
50m
2(191-199)
BB/OHP
18
Structured analysis, Data Dictionary
50m
1(226-232)
[Type text]
BB
DOC/LP/01/02.1.13
LP- IT2251
LESSON PLAN
LP Rev. No: 01
Sub Code & Name : IT2251 & SOFTWARE ENGINEERING AND
QUALITY ASSURANCE
Unit: III
Date: 02.01.2013
Page 03 of 06
Branch: IT
Semester:IV
ANALYSIS, DESIGN CONCEPTS AND PRINCIPLES
Systems Engineering - Analysis Concepts - Design Process And Concepts – Modular Design –
Design Heuristic – Architectural Design – Data Design – User Interface Design – Real Time
Software Design – System Design – Real Time Executives – Data Acquisition System –
Monitoring And Control System.
Objective:
To learn about the software architecture and detailed design methods.
Session
No
19
20
Topics to be covered
Analysis modeling approachesData modeling, Scenario based
modeling
Class based modeling, Behavioral
modeling
Time
Allocation
Books Referred
(Page
Numbers)
Teaching
Method
50m
1(208-225)
BB
50m
1(233-250)
BB
21
Design process
50m
1(258-264)
BB
22
Design concepts, Modular design
Design heuristic, Design model
50m
1(265-282)
BB
23
Architectural design and software
architecture- Data design
50m
1(286-297)
BB/OHP
50m
1(298-315)
BB/OHP
50m
1(316-320)
BB/OHP
50m
1(356-77)
BB
50m
2(361-370)
BB
50m
2(371-378)
BB
24
25
26
27
28
[Type text]
Architectural design -Transform
mapping with examples
Transaction mapping with
examples
User interface design - User
interface design principles
Real time systems, Real time
System design
Real time executives,
Data acquisition system,
Monitoring and control system
DOC/LP/01/02.1.13
LP- IT2251
LESSON PLAN
LP Rev. No: 01
Sub Code & Name : IT2251 & SOFTWARE ENGINEERING AND
Date: 02.01.2013
QUALITY ASSURANCE
Unit: IV
Page 04 of 06
Branch: IT
Semester:IV
TESTING
Taxonomy of Software Testing – Types Of S/W Test – Black Box Testing – Testing Boundary
Conditions – Structural Testing – Test Coverage Criteria Based On Data Flow Mechanisms –
Regression Testing – Unit Testing – Integration Testing – Validation Testing – System Testing
And Debugging – Software Implementation Techniques
Objective:
To have an understanding of testing strategies, Verification and validation techniques.
Session
No
29
30,31
32,33
Time
Allocation
Books
Referred
(Page
Numbers)
Teaching
Method
Taxonomy of software testing
Testing levels, test activities
50m
1(421-424)
BB
Types of software testing –
black box testing
100m
1(434-441)
BB
White Box testing –
Basis path testing
Testing boundary conditions
50m
1(424-434)
BB/OHP
Topics to be covered
Structural testing –
Test coverage criteria based on data
flow mechanisms
50m
34
Testing in the large,
S/W testing strategies
Strategic approach and issues
50m
1(386-393)
BB
35
Unit testing
integration testing, Regression testing
50m
1(394-404)
BB
50m
1(406-413)
BB
36
[Type text]
Validation testing,
System testing and debugging
Continuous Assessment Test-II
3 hrs
DOC/LP/01/02.1.13
LP- IT2251
LESSON PLAN
LP Rev. No: 01
Date: 02.01.2013
Sub Code & Name : IT2251 & SOFTWARE ENGINEERING AND
QUALITY ASSURANCE
Unit: V
Page 05 of 06
Branch: IT
Semester:IV
SOFTWARE QUALITY ASSURANCE
Process and Product Quality – Quality Assurance and Standards – Quality Planning and Control –
Software metrics – Process Improvement – Software configuration Management.
Objective:
To understand the concepts of Quality planning and Use of CASE tools.
Session
No
Topics to be covered
Time
Allocation
Books
Referred
Teaching
Method
37
Process and Product Quality
50m
2(663-666)
BB
38
Quality Assurance and Standards,
Quality Planning and Control
50m
2(667-675)
BB
39
Software metrics
50m
2(676-684)
BB
40
Process Improvement- Process classification
50m
2(687-691)
41
Process measurement , Analysis and modeling
50m
2(694-699)
BB
42
Process change, CMMI
50m
2(700-708)
BB
43
SCM, Need for SCM
50m
1(772,775)
BB
44
Planning, Change management, Version and
release management
50m
2(711-720)
BB
45
System Building, CASE tools for
configuration management.
50m
2(721-732)
BB
Continuous Assessment Test-III
75m
BB
[Type text]
DOC/LP/01/02.1.13
LP- IT2251
LESSON PLAN
LP Rev. No: 01
Sub Code & Name : IT2251 & SOFTWARE ENGINEERING AND
Date: 02.01.2013
QUALITY ASSURANCE
Page 06 of 06
Unit: I,II,III,IV,V
Branch: IT
Semester:IV
Course Delivery Plan:
Week
Units
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
I II I II I II I II I II I II I II I II I II I II I II I II I II I II I II
1
2
3
4
5
CAT II
CAT III
TEXT BOOKS:
1.Roger S. Pressman, “SOFTWARE ENGINEERING AND QUALITY ASSURANCEAND
QUALITY ASSURANCEAND QUALITY ASSURANCE– A practitioner’s
Approach”,
Sixth Edition, McGraw-Hill International Edition, 2005.
2.Ian Sommerville, “Software engineering”, Seventh Edition, Pearson Education Asia, 2007.
REFERENCES:
3.Ian Sommerville, “Software engineering”, Sixth Edition, Pearson Education Asia, 2000.
4.Watts S.Humphrey,”A Discipline for Software Engineering”, Pearson Education, 2007.
5.James F.Peters and Witold Pedrycz,”Software Engineering, Engineering Approach”, WileyIndia, 2007.
6.Stephen R.Schach, “Software Engineering”, Tata McGraw-Hill Publishing Company Limited,
2007.
7.S.A.Kelkar,”Software Engineering”, Prentice Hall of India Pvt, 2007.
Prepared by
Approved by
Signature
Name
Designation
Date
[Type text]
C.Silambarasi
S.K.Umamaheswari
Assistant Professor
Assistant Professor
02.01.2013
Prof.E.G.Govindan
HOD/IT