Lovely Professional University,Punjab

Format For Instruction Plan [for Courses with Lectures and Labs ]
Course No. CSE364

Course Title:

SOFTWARE ENGINEERING CONCEPTS & TOOLS

L: 3

T: 0

P: 2

Cr: 4

Course Planner :-

13075 :: Balraj Singh

TextBook

1. P.Jalote, "An Integrated Approach to Software Engineering", Narosa 2. Author,R.S. Pressman.Title :Software engineering - A Practitioner's appraoch
Other Specific Books

3. 4. 5. 6.
Other Readings

R. Fairely,Software Engineering Concepts ",Tata McGraw Hill,1997 Stephen R. Schach, Classical & Object Oriented Software Engineering , IRWIN, 1996. James Peter, W. Pedrycz, Software Engineering, John Wiley & Sons. Sommerville, Software Engineering , Addison Wesley

Sr. No.

Jouranls atricles as compulsary readings (specific articles, Complete reference)

7 8 9

http://ieeexplore.ieee.org/xpl/RecentIssue.jsp?reload=true&punumber=2225 http://www.springerlink.com/content/?k=software+engineering http://opensource.mit.edu/online_papers.php

Relevant Websites

Sr. No.

Web adress

(only if relevant to the courses)

Salient Features

10 11

http://www.sereferences.com/testingtools.php http://editorial.co.in/software/software-testing-life-cycle.php

onine tools testing

Page 1 of 7

Approved for Autumn Session 2010-11

Detailed Plan For Lectures

Week No. Lecture No. Topic Chapters/Sections of Textbook/other reference Homework to be Assigned to students Pedagogical tool Demonstration/case study/images/anmation ctc. planned

Part 1
Week 1

Lecture 1 Lecture 2 Lecture 3

Introduction to concept of Software, Problem Domain Software engineering Challenges Software Engineering Approach, Characteristics of software process Software Processes:Software Development Process Models Software Processes;Software Development Process Models3

Book :1,Ch1 ( 1.1) Book :1,Ch1 (1.2) Book :1,Ch1 (1.3) Book :1,Ch2 (2.3) Book :1,Ch2 (2.3)
HomeWork 1 Allocation

Week 2

Lecture 4 Lecture 5

home work 1 allocation http://www.softpanorama .org/SE/software_life_cyc le_models.shtml

Lecture 6
Week 3

Software Processes: Project Management Process, Inspection Process Software Requirement Analysis and Specification: Software Requirement, Problem Analysis Software Requirement Analysis and Specification: Requirement Specification Software Requirement Analysis and Specification:Functional Specification with Use Cases Software Requirement Analysis and Specification: Developing use cases

Book :1,Ch2 (2.4) Book :1,Ch3(3.1- 3.2) Book :1,Ch3 (3.3) Book :1,Ch3 (3.4) Book :1,Ch3 (3.4)
HomeWork 1 Submission Design problem1

Lecture 7 Lecture 8 Lecture 9

Week 4

Lecture 10

home work 1 submission, Demonstration using HMagic draw. Class test based on homework 1 home work 2 allocation demonstration of estimation : http://cost.jsc.nasa.gov/C OCOMO.html

Part 2
Week 4

Lecture 11 Lecture 12

Software Requirement Analysis and Specification: Validation Planning Software Project: Efforts Estimation Planning Software Project: Efforts Estimation

Book :1,Ch3 (3.5) Book :1,ch5 (5.2) Book :1,ch5 (5.2)

Class test based on homework1 HomeWork 2 Allocation

Week 5

Lecture 13

Page 2 of 7

Approved for Autumn Session 2010-11

Part 2
Week 5

Lecture 14 Lecture 15

Project scheduling and staffing Planning Software Project: Quality Plan Planning Software Project:Risk Management Planning Software Project:Risk Management Planning Software Project:Project Monitoring Plan Software Design: Design Principal,Module Level Components Software Design: Design Notation and Specification Software Design:Cohesion and coupling

Book :1,ch5 (5.3) Book :1,ch5 (5.5) Book :1,ch5 (5.6) Book :1,ch5 (5.6) Book :1,ch5 (5.7) Book :1,ch6 (6.1) Book :1,ch6 (6.3) Book :1,ch6 (6.2)
HomeWork 2 Submission Class test based on homework2

Week 6

Lecture 16 Lecture 17 Lecture 18

DP1 submission homework 2 submission Class test based on homework 2

Week 7

Lecture 19 Lecture 20 Lecture 21

MID-TERM
Part 3
Week 8

Lecture 22

Verification and Validation: Planning Verification and Validation ,Software Inspection,V-Model. Verification and Validation: Automated Static analysis,verification and formal methods. Software Reliability: Importance, Hardware Reliability & Software Reliability,Failure and Faults, Reliability Models Software Quality Models, CMM & ISO 9001 Software Quality Models, CMM & ISO Testing process, Design of test cases Functional testing, Equivalence class testing, Decision table testing

->Reference :6,ch22(22.1-22.2)

http://www.ece.cmu.edu/ ~koopman/des_s99/verifi cation/

Lecture 23 Lecture 24
Week 9

->Reference :6,ch22(22.3-22.4) Book :1,ch10(10.6) ->Reference :6,ch 28 ->Reference :6,ch28 Book :1,ch10(10.4) Book :1,ch10(10.2)
HomeWork 3 Submission Design problem2 HomeWork 3 Allocation

homework 3 allocation http://www.isoqar.com/is o9001/qualintro.htm

Lecture 25 Lecture 26 Lecture 27

Week 10

Lecture 28

homework 3 submission , Demonstrate test cases followed by software companies

Page 3 of 7

Approved for Autumn Session 2010-11

Part 3
Week 10

Lecture 29

Verification & Validation, Unit Testing, Integration testing

Book :2,ch13(13.3-13.4-13.5)

Class test based on homework3

Class test based on homework 3

Part 4
Week 10 Week 11

Lecture 30 Lecture 31 Lecture 32 Lecture 33

System Testing , Debugging, Alpha & Beta Testing Structural testing, Path Testing, Regression Testing Testing Tools & Standards Quality Management: Process and Product quality, Quality assurance and standards Quality Planning, Quality Control Software measurement and metrics Software measurement and metrics Software Maintenance: Types of Maintenance Maintenance Process, Maintenance Models Reverse Engineering

Book :2,Ch13(13.5-13.6) ->Reference :6,ch23(23.3) ->Reference :6,ch23(23.4) ->Reference :6,ch27(27.1 27.2) ->Reference :6,ch27(27.3 27.4) ->Reference :6,ch27(27.5) ->Reference :6,ch27(27.5) ->Reference :6,ch21(21.1) ->Reference :6,ch21(21.2) ->Reference :6,ch21(21.3-21.4)

HomeWork 4 Allocation

homework 4 allocation

Live demonstration of software testing tool. DP2 Submission

Week 12

Lecture 34 Lecture 35 Lecture 36

HomeWork 4 Submission Class test based on homework4

homework 4 submission Class test based on homework 4

Week 13

Lecture 37 Lecture 38 Lecture 39

Demonstration of reverse engineering on tool.

Spill Over
Week 14

Lecture 40 Lecture 41

Emerging Technologies:Service oriented software engineering Emerging Technologies: Aspect Oriented Software Development

->Reference :6,ch31(31.1-31.2)

Page 4 of 7

Approved for Autumn Session 2010-11

Details of homework and case studies plan

Homework No. Topic of the Homework Nature of homework (group/individuals/field work

Homework 1

Problem Domain,Software engineering Challenges,Software Engineering Approach,Software Development Process Models, Project Management Process, Inspection Process, Software Configuration Management Process Software Requirement Analysis and Specification: Software Requirement, Problem Analysis, Requirement Specification, Functional Specification with Use Cases, Validation. Planning Software Project: Efforts Estimation,Quality Plan and Risk Management, Project Monitoring Plan. Verification and Validation: Planning Verification and Validation , Software Inspection, Automated Static analysis Software Reliability: Importance, Hardware Reliability & Software Reliability, Failure and Faults, Reliability Models. Software Quality Models, CMM & ISO 9001 Design of test cases, functional testing, Equivalence class testing, verification & Validation, Unit Testing, Integration System Testing,Debugging, Regression , Testing Tools & Standards.Process and Product quality,Quality Planning, Software measurement and metrics

Individual

Homework 2

Individual

Homework 3

Individual

Homework 4

Individual

*Normally all the homeworks shall be submitted online but in special courses where homeworks cannot be submited online , the insructor can edit the mode of submission while entering the IP Details

Scheme for CA:out of 100*

Component Frequency Out of (If any) Marks for each Total Marks

Design problem Class test based on homework Homework Lab Assesment

2 3 3 10 4 4 12
Total :-

20 7 3 3

40 21 9 30
100

* In ENG courses wherever the total exceeds 100, consider x best out of y components of CA, as explained in teacher's guide available on the UMS

Page 5 of 7

Approved for Autumn Session 2010-11

*Each experiment of the lab will be evaluated using following relative scheme:

Component

% of Marks

J/E WR VIVA

50 20 30

Page 6 of 7

Approved for Autumn Session 2010-11

List of experiments :Expt. No Title Equipment Used Reference of Lab manual

Before Mid-Term

UML 1 UML 2

Defining requirement : Creation of SRS Document Defining different classes using UML and their association among themselves Defining depenencie,Objects unsing UML Definings inheritance,ggregation using UML Use Cases using UML Sequence diagram

Computer:Open Office Computer:Magic Draw software

UML 3 UML 4 UML 5 UML 6

After Mid-Term

Computer:Magic Draw software Computer:Magic Draw software Computer:Magic Draw software Computer:Magic Draw software

UML 7 UML 8 UML 9 UML 10 UML 11

Spill Over

Activity diagrams Data flow diagram unsing UML Developing Test Plan Developing Test cases Black box testing,white box testing

Computer:Magic Draw software Computer:Magic Draw software Computer: open office Computer: open office Computer: open office

UML 12

Regression testing, Validation

Computer: open office

Page 7 of 7

Approved for Autumn Session 2010-11