SOFTWARE ENGINEERING COURSE PLAN

BIJAYA KUMAR BISWAL

Assistant Professor, CSE
 2013-14

COURSE PLAN
Regulation: R11

FACULTY DETAILS:
Name of the Faculty: Bijaya Kumar Biswal
Designation: Assistant Professor
Department: Computer Science & Engineering

COURSE DETAILS :
Name Of The Programme: B.Tech Batch:: 2011
Designation: B. Tech-III Year
Year : 2013 Semester: I
Department: CSE
Title of The Subject: Software Engineering Subject Code: SE
No of Students: 131
 2013-14
COURSE PLAN
Regulation: R11

FACULTY DETAILS:
Name of the Faculty: Bijaya Kumar Biswal
Designation: Assistant Professor
Department: Computer Science & Engineering

1. TARGET

a) Percentage Pass 100 %

b) Percentage I class 90%

2. COURSE PLAN

(Please write how you intend to cover the contents: i.e., coverage of Units by lectures, guest lectures, design exercises, solving
numerical problems, demonstration of models, model preparation, or by assignments, etc.)

3. METHOD OF EVALUATION

3.1. Continuous Assessment Examinations (CAE 1, CAE 2)

3.2. Assignments / Seminars

3.3. Mini Projects

3.4. Quiz

3.5. Term End Examination

3.6. Others

4. List out any new topic(s) or any innovation you would like to introduce in teaching the subject in this Semester.

Signature of HOD Signature of Faculty

Date: Date:
 2013-14

GUIDELINES TO STUDY THE SUBJECT

Regulation: R11

FACULTY DETAILS:
Name of the Faculty: Bijaya Kumar Biswal
Designation: Assistant Professor
Department: Computer Science & Engineering
Guidelines for Preparing the Course:

Course Description:
Software Engineering (SE) comprises the core principles consistent in software construction and
maintenance: fundamental software processes and life-cycles, mathematical foundations of software
engineering, requirements analysis, software engineering methodologies and standard notations,
principles of software architecture and re-use, software quality frameworks and validation, software
development, and maintenance environments and tools. An introduction to object-oriented software
development process and design. Topics include: iterative development, interpretation of
requirements and use case documents into code; application of design notation in UML and use of
commonly-used design patterns. Current industry-strength programming languages, technologies and
systems feature highly in the practical components, electives and projects of the course, but they are
also taught with a view to understanding and applying principles underlying their more ephemeral
character.

Course Objectives:
1. Knowledge of basic SW engineering methods and practices, and their appropriate application.
2. Describe software engineering layered technology and Process frame work.
3. A general understanding of software process models such as the waterfall and evolutionary
models.
4. Understanding of software requirements and the SRS documents.
5. Understanding of the role of project management including planning, scheduling, risk
management, etc.
6. Describe data models, object models, context models and behavioural models.
7. Understanding of different software architectural styles.
8. Understanding of implementation issues such as modularity and coding standards.

9. Understanding of approaches to verification and validation including static analysis, and

reviews.

10. Understanding of software testing approaches such as unit testing and integration testing.

11. Describe software measurement and software risks.

12. Understanding of software evolution and related issues such as version management.

13. Understanding on quality control and how to ensure good quality software.
 2013-14
COURSE OBJECTIVES
Regulation: R11

Learning Outcomes:
1. Basic knowledge and understanding of the analysis and design of complex systems.
2. Ability to apply software engineering principles and techniques.
3. Ability to develop, maintain and evaluate large-scale software systems.
4. To produce efficient, reliable, robust and cost-effective software solutions.
5. Ability to perform independent research and analysis.
6. To communicate and coordinate competently by listening, speaking, reading and writing english for
technical and general purposes.
7. Ability to work as an effective member or leader of software engineering teams.
8. To manage time, processes and resources effectively by prioritising competing demands to achieve
personal and team goals Identify and analyzes the common threats in each domain.
9. Ability to understand and meet ethical standards and legal responsibilities.

FACULTY DETAILS:
Name of the Faculty: Bijaya Kumar Biswal
Designation: Assistant Professor
Department: Computer Science & Engineering

On completion of this Subject / Course the student shall be able to:

S. No. Objectives Outcomes

1.
Understand basic SW engineering methods and practices, and their appropriate
application.
1
2.
Understand u of software process models such as the waterfall and evolutionary

models.
3
3.
Role of project management including planning, scheduling and, risk management.

5
4.
Discuss data models, object models, context models and behavioural models.
6
5.

Understand of different software architectural styles and Process frame work.

2,7
6.
Understand of implementation issues such as modularity and coding standards.
8
7.
 Understand to verification and validation including static analysis, and reviews.
9,10

Describe software measurement and software risks.

8. 11
9.
Discuss software evolution and related issues such as version management.
12
10.
Understand on quality control and how to ensure good quality software.
13

Signature of Faculty
Date:

Note: For each of the OBJECTIVE indicate the appropriate OUTCOMES to be achieved.
Kindly refer Page 16, to know the illustrative verbs that can be used to state the objectives.
 2013-14
COURSE OUTCOMES
Regulation: R11

FACULTY DETAILS:
Name of the Faculty: Bijaya Kumar Biswal
Designation: Assistant Professor
Department: Computer Science & Engineering

The expected outcomes of the Course / Subject are:

S.No. General Categories of Outcomes Specific Outcomes of the Course
An ability to apply knowledge of mathematics,
A. science, and engineering
Fundamental knowledge in mathematics, computer
science, programming and computer systems
An ability to design and conduct experiments, as
B. well as to analyze and interpret data
Basic knowledge and understanding of the analysis,
synthesis and design of complex systems
An ability to design a system, component, or Software engineering principles and techniques
C. process to meet desired needs within realistic
Constraints such as economic, environmental,
social, political, ethical, health and safety,
Manufacturability and sustainability

An ability to function on multi-disciplinary teams

D.
To develop, maintain and evaluate large-scale software
systems
An ability to identify, formulate, and solve
To produce efficient, reliable, robust and cost-effective
E. engineering problems software solutions

An understanding of professional and ethical

F. responsibility
To meet ethical standards and legal responsibilities
To communicate and coordinate competently by listening,
An ability to communicate effectively speaking, reading and writing
G.

The broad education necessary to understand the

H. impact of engineering solutions in a global,
Apply the principles, tools and practices of IT project
economic, environmental, and societal context management
A recognition of the need for, and an ability to
I. engage in life-long learning
To manage time, processes and resources effectively by
prioritising competing demands
A knowledge of contemporary issues
J.
To work as an effective member or leader of software
engineering teams
 To rapidly learn and apply emerging technologies

An ability to use the techniques, skills, and

K. modern engineering tools necessary for
engineering practice.

Objectives – Outcome Relationship Matrix (Indicate the relationships by mark).

Outcomes
Objectives A B C D E F G H I J K
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
 2013-14
COURSE SCHEDULE
Regulation: R11

FACULTY DETAILS:
Name of the Faculty: Bijaya Kumar Biswal
Designation: Assistant Professor
Department: Computer Science & Engineering
The Schedule for the whole Course / Subject is: Software Engineering

Duration (Date) Total No.

S. No. Description
From To of Periods
Introduction to Software Engineering and
1. a generic view of process
03-07-2013 15-07-2013 09

Process models and software

2.
requirements 08
16-07-2013 27-07-2013
Requirements engineering process and
3. system models
07

29-07-2013 05-08-2013
Design engineering creating an
4.
architectural design 07

06-08-2013 17-08-2013
Model component- level design
5.
and performing user interface design 06

20-08-2013 24-08-2013
6.
Testing strategies product metrics 10
26-08-2013 11-09-2013

Metrics for process and products

7
Risk management 07
13-09-2013 23-09-2013

8 Quality Management
24-09-2013 19-10-2013 06

Total No. of Instructional periods available for the course: 50 Hours / 60 Periods
 SCHEDULE OF
INSTRUCTIONS 2013-14
Regulation:
UNIT - I R11

FACULTY DETAILS:
Name of the Faculty: Bijaya Kumar Biswal
Designation: Assistant Professor
Department: Computer Science & Engineering
The Schedule for the whole Software Engineering
Course / Subject is:

SI Objective
s& References
. No. of
Topics / Sub - Outco (Text Book,
N Perio
Date Topics me Journal…)
o. ds
Page No___ to
Nos. ___
Introduction to software
03-07- Engineering
1 2013 1 1 TB1
The evolving role of
03-07- software
2 2013 2 1 TB1
Changing nature of
03-07- software
3 2013 3 1 TB1
Legacy systems,
03-07- software myths
4 2013 4 1 TB1
Software engineering- a
03-07- layered technology
5 2013 5 2 TB1
03-07- Process frame work
6 2013 6 2 TB1 TB1
03-07- CMMI, Process patterns
7 2013 7 2 TB1
Process assessment
03-07- 1,
8 2013 8 2 TB1
Personal and team
15-07- process models 1,
9 2013 9 2 TB1

Text Book:

TB1: Software Engineering: A Practitioner’s Approach, Roger S Pressman 6th Edition

TB1: Software Engineering: Iyan Somarville, 7th Edition

Signature of Faculty
Date
 Note: 1. ENSURE THAT ALL TOPICS SPECIFIED IN THE COURSE ARE MENTIONED.
2. ADDITIONAL TOPICS COVERED, IF ANY, MAY ALSO BE SPECIFIED BOLDLY.
3. MENTION THE CORRESPONDING COURSE OBJECTIVE AND OUT COME NUMBERS AGAINST EACH TOPIC.

SCHEDULE OF INSTRUCTIONS 2013-14

UNIT - II Regulation: R11

FACULTY DETAILS:
Name of the Faculty: Bijaya Kumar Biswal
Designation: Assistant Professor
Department: Computer Science & Engineering
The Schedule for the whole Course / Subject is: Software Engineering

Objectives & References

SI. No. of
Date Topics / Sub - Topics Outcome (Text Book, Journal…)
No. Periods
Nos. Page No___ to ___
The water fall model, Incremental
16-07- process models
10 2013 10 3 TB1,TB2
Evolutionary process models
19-07-
11 2013 11 3 TB1
Specialized process models
20-07-
12 2013 12 3 TB1,TB2
The unified process
22-07-
13 2013 13 3,4 TB1,TB2
Functional requirements
23-07-
14 2013 14 3,4 TB1,TB2
Non functional requirements
24-07-
15 2013 15 4 TB1,TB2

26-07- User requirements, System

16 2013 16 requirements 4 TB1,TB2

27-07- System requirements and Interface

17 2013 17 specification 4 TB1

Signature of Faculty
Date

Note: 1. ENSURE THAT ALL TOPICS SPECIFIED IN THE COURSE ARE MENTIONED.
2. ADDITIONAL TOPICS COVERED, IF ANY, MAY ALSO BE SPECIFIED BOLDLY.
MENTION THE CORRESPONDING COURSE OBJECTIVE AND OUT COME NUMBERS AGAINST EACH TOPIC.
 SCHEDULE OF INSTRUCTIONS 2013-14

UNIT - III Regulation: R11

FACULTY DETAILS:
Name of the Faculty: Bijaya Kumar Biswal
Designation: Assistant Professor
Department: Computer Science & Engineering
The Schedule for the whole Course / Subject is: Software Engineering

Objectives & References

SI. No. of
Date Topics / Sub - Topics Outcome (Text Book, Journal…)
No. Periods
Nos. Page No___ to ___
Feasibility studies
29-07-
18 2013 18 5 TB2
Requirements elicitation and analysis TB2
30-07-
19 2013 19 5
Requirements validation, TB2
31-07-
20 2013 20 5
Requirements management TB2
02-08-
21 2013 21 5
Context models, Behavioral models TB2
03-08-
22 2013 22 6
Structured methods TB2
04-08-
23 2013 23 6
data models, object models TB2
05-08-
24 2013 24 6

Signature of Faculty
Date

Note: 1. ENSURE THAT ALL TOPICS SPECIFIED IN THE COURSE ARE MENTIONED.
2. ADDITIONAL TOPICS COVERED, IF ANY, MAY ALSO BE SPECIFIED BOLDLY.
MENTION THE CORRESPONDING COURSE OBJECTIVE AND OUT COME NUMBERS AGAINST EACH TOPIC.
 SCHEDULE OF INSTRUCTIONS 2013-14

UNIT - IV Regulation: R11

FACULTY DETAILS:
Name of the Faculty: Bijaya Kumar Biswal
Designation: Assistant Professor
Department: Computer Science & Engineering
The Schedule for the whole Course / Subject is: Software Engineering

Objectives & References

SI. No. of
Date Topics / Sub - Topics Outcome (Text Book, Journal…)
No. Periods
Nos. Page No___ to ___
Design process & design quality
06-08-
25 2013 25 8 TB1
Design concepts, The design models TB1
06-08-
26 2013 26 8
Software architecture TB1
06-08-
27 2013 27 7
Data design TB1
06-08-
28 2013 28 8
Architectural styles & patterns TB1
06-08-
29 2013 29 7
Architectural design, Assessing TB1
06-08- alternative architectural designs
30 2013 30 7
Mapping data flow into a software TB1
17-08- architecture.
31 2013 31 8

Signature of Faculty
Date

Note: 1. ENSURE THAT ALL TOPICS SPECIFIED IN THE COURSE ARE MENTIONED.
2. ADDITIONAL TOPICS COVERED, IF ANY, MAY ALSO BE SPECIFIED BOLDLY.
MENTION THE CORRESPONDING COURSE OBJECTIVE AND OUT COME NUMBERS AGAINST EACH TOPIC.
 SCHEDULE OF INSTRUCTIONS 2013-14

UNIT - V Regulation: R11

FACULTY DETAILS:
Name of the Faculty: Bijaya Kumar Biswal
Designation: Assistant Professor
Department: Computer Science & Engineering
The Schedule for the whole Course / Subject is: Software Engineering

Objectives & References

SI. No. of
Date Topics / Sub - Topics Outcome (Text Book, Journal…)
No. Periods
Nos. Page No___ to ___
Designing class based components,
20-08- conducting component level design
32 2013 32 8 TB1
Object constraint language TB1
20-08-
33 2013 33 8
Designing conventional components TB1
21-08-
34 2013 34 9
Golden rules, user interface analysis and TB1
22-08- design
35 2013 35 8
Interface analysis TB1
23-08-
36 2013 36 9
Interface design steps, design evaluation TB1
24-08-
37 2013 37 9

Signature of Faculty
Date

Note: 1. ENSURE THAT ALL TOPICS SPECIFIED IN THE COURSE ARE MENTIONED.
2. ADDITIONAL TOPICS COVERED, IF ANY, MAY ALSO BE SPECIFIED BOLDLY.
MENTION THE CORRESPONDING COURSE OBJECTIVE AND OUT COME NUMBERS AGAINST EACH TOPIC.
 SCHEDULE OF INSTRUCTIONS 2013-14

UNIT - VI Regulation: R11

FACULTY DETAILS:
Name of the Faculty: Bijaya Kumar Biswal
Designation: Assistant Professor
Department: Computer Science & Engineering
The Schedule for the whole Course / Subject is: Software Engineering

Objectives & References

SI. No. of
Date Topics / Sub - Topics Outcome (Text Book, Journal…)
No. Periods
Nos. Page No___ to ___
A strategic approach to software testing
26-08-
38 2013 38 9 TB1
Test strategies for conventional software TB1
26-08-
39 2013 39 9
Black box and white box testing, TB1
26-08- Validation testing
40 2013 40 10
System testing, The art of debugging TB1
26-08-
41 2013 41 10
Functional and Non functional testing TB1
26-08-
42 2013 42 10
Planning and Ad hoc testing
11-09-
43 2013 43 10 TB1
TB1
11-09-
44 2013 44 Test case format representation 9
Frame work for product metrics TB1
11-09-
45 2013 45 9
Metrics for analysis model, metrics for TB1
11-09- design model
46 2013 46 9
TB1
11-09- Metrics for source code, metrics for
47 2013 47 testing, metrics for maintenance 9

Signature of Faculty
Date

Note: 1. ENSURE THAT ALL TOPICS SPECIFIED IN THE COURSE ARE MENTIONED.
2. ADDITIONAL TOPICS COVERED, IF ANY, MAY ALSO BE SPECIFIED BOLDLY.
MENTION THE CORRESPONDING COURSE OBJECTIVE AND OUT COME NUMBERS AGAINST EACH TOPIC.
 SCHEDULE OF INSTRUCTIONS 2013-14

UNIT - VII Regulation: R11

FACULTY DETAILS:
Name of the Faculty: Bijaya Kumar Biswal
Designation: Assistant Professor
Department: Computer Science & Engineering
The Schedule for the whole Course / Subject is: Software Engineering

Objectives & References

SI. No. of
Date Topics / Sub - Topics Outcome (Text Book, Journal…)
No. Periods
Nos. Page No___ to ___
Software measurement
13-09-
48 2013 48 11 TB1
Metrics for software quality TB1
14-09-
49 2013 49 11
Reactive vs. Proactive risk strategies TB1
16-09-
50 2013 50 11
Software risks TB1
17-09-
51 2013 51 11
Risk identification, Risk projection TB1
20-09-
52 2013 52 11
Risk refinement
21-09-
53 2013 53 11 TB1
RMMM, RMMM Plan TB1
23-09-
54 2013 54 11

Signature of Faculty
Date

Note: 1. ENSURE THAT ALL TOPICS SPECIFIED IN THE COURSE ARE MENTIONED.
2. ADDITIONAL TOPICS COVERED, IF ANY, MAY ALSO BE SPECIFIED BOLDLY.
MENTION THE CORRESPONDING COURSE OBJECTIVE AND OUT COME NUMBERS AGAINST EACH TOPIC.
 SCHEDULE OF INSTRUCTIONS 2013-14

UNIT - VIII Regulation: R11

FACULTY DETAILS:
Name of the Faculty: Bijaya Kumar Biswal
Designation: Assistant Professor
Department: Computer Science & Engineering
The Schedule for the whole Course / Subject is: Software Engineering

Objectives & References

SI. No. of
Date Topics / Sub - Topics Outcome (Text Book, Journal…)
No. Periods
Nos. Page No___ to ___
Quality concepts
24-09- 12,
55 2013 55 13 TB1
Software quality assurance TB1
24-09- 12,
56 2013 56 13
Software reviews, formal technical TB1
19-10- reviews
57 2013 57 12
Statistical software quality assurance TB1
19-10-
58 2013 58 13
Software reliability TB1
19-10-
59 2013 59 13
The ISO 9000 quality standards
19-10-
60 2013 60 13 TB1

Signature of Faculty
Date

Note: 1. ENSURE THAT ALL TOPICS SPECIFIED IN THE COURSE ARE MENTIONED.
2. ADDITIONAL TOPICS COVERED, IF ANY, MAY ALSO BE SPECIFIED BOLDLY.
MENTION THE CORRESPONDING COURSE OBJECTIVE AND OUT COME NUMBERS AGAINST EACH TOPIC.
 2013-14
COURSE COMPLETION STATUS
Regulation: R11

FACULTY DETAILS:
Name of the Faculty: Bijaya Kumar Biswal
Subject: Software Engineering Subject Code: SE
Department: Computer Science & Engineering
Actual Date of Completion & Remarks, if any

Nos. of
Units Remarks Objectives
Achieved
Unit 1
No 1,2
Unit 2

No 3,4
Unit 3

No 5,6
Unit 4

No 7,8
Unit 5
No 8,9

Unit 6 No 9,10

Unit 7 No 11

Unit 8 No 12,13

Signature of Dean of School Signature of Faculty

Date: Date:

NOTE: AFTER THE COMPLETION OF EACH UNIT MENTION THE NUMBER OF OBJECTIVES ACHIEVED.
 2013-14

TUTORIAL SHEETS - I
Regulation: R11

FACULTY DETAILS:
Name of the Faculty: Bijaya Kumar Biswal
Designation: Assistant Professor
Department: Computer Science & Engineering
The Schedule for the whole Course / Subject is: Software Engineering

Date: 07-08-2013
This Tutorial corresponds to Unit Nos.: I and II Time: 10.00 A.M

Q1. Define software and explain the software characteristics.

Q2. Discuss the attributes of a good software.

Q3. Explain the process maturity levels in detail.

Q4. Discuss the about various phases of the assessment.

Q5. Define Functional & Non functional requirements.

Q6. Explain various types of evolutionary development.

Please write the Questions / Problems / Exercises which you would like to give to the students and also mention the
objectives to which these questions / Problems are related.

Signature of Dean of School Signature of Faculty

Date: Date:
 2013-14

TUTORIAL SHEETS - II
Regulation: R11

FACULTY DETAILS:
Name of the Faculty: Bijaya Kumar Biswal
Designation: Assistant Professor
Department: Computer Science & Engineering
The Schedule for the whole Course / Subject is: Software Engineering

Date: 04-09-2013
This Tutorial corresponds to Unit Nos.: III, IV and V Time: 10.00 A.M

Q1. Explain the requirement analysis techniques.

Q2. Explain the structure of viewpoints and services template form.

Q3. What is requirements management and why is it needed.

Q4. Discuss the advantages and disadvantages of modularization.

Q5. What are the goals of the user interface design.

Q6. What is software architecture gives an example.

Please write the Questions / Problems / Exercises which you would like to give to the students and also mention the
objectives to which these questions / Problems are related.

Signature of Dean of School Signature of Faculty

Date: Date:
 2013-14

TUTORIAL SHEETS - III

Regulation: R11

FACULTY DETAILS:
Name of the Faculty:: Bijaya Kumar Biswal
Designation: Assistant Professor
Department:: Computer Science & Engineering

Date: 11-10-2013
This Tutorial corresponds to Unit Nos.: VI, VII and VIII Time: 10.00 A.M

Q1. What is the overall strategy for software testing.

Q2. State and explain various debugging tactics.

Q3. Explain the size oriented metrics with an example.

Q4. Distinguish between metrics and measurements.

Q5. Discuss the importance of quality assurance.

Q6. Discuss about ISO 9000 quality standards.

Please write the Questions / Problems / Exercises which you would like to give to the students and also mention the
objectives to which these questions / Problems are related.

Signature of Dean of School Signature of Faculty

Date: Date:
 2013-14
ILLUSTRATIVE VERBS
FOR STATING
INSTRUCTIONAL OBJECTIVES Regulation: R11

These verbs can also be used while framing questions for Continuous Assessment Examinations as well as for End –
Semester (final) Examinations.
ILLUSTRATIVE VERBS FOR STATING GENERAL OBJECTIVES

Know Understand Analyze Generate

Comprehend Apply Design Evaluate

ILLUSTRATIVE VERBS FOR STATING SPECIFIC OBJECTIVES:

A. Cognitive Domain
1 2 3 4 5 6
Comprehension
Knowledge Application Analysis Synthesis Evaluation
Understanding
of knowledge & of whole w.r.t. its combination of
judgement
comprehension constituents ideas/constituents

Define Convert Change Breakdown Categorize Appraise

Identify Defend Compute Differentiate Combine Compare
Label Describe (a Demonstrate Discriminate Compile Conclude
List procedure) Deduce Distinguish Compose Contrast
Match Distinguish Manipulate Separate Create Criticize
Reproduce Estimate Modify Subdivide Devise Justify
Select Explain why/how Predict Design Interpret
State Extend Prepare Generate Support
Generalize Relate Organize
Give examples Show Plan
Illustrate Solve Rearrange
Infer Reconstruct
Summarize Reorganize
Revise

B. Affective Domain C. Psychomotor Domain (skill development)

Adhere Resolve Bend Dissect Insert Perform Straighten
Assist Select Calibrate Draw Keep Prepare Strengthen
Attend Serve Compress Extend Elongate Remove Time
Change Share Conduct Feed Limit Replace Transfer
Develop Connect File Manipulate Report Type
Help Convert Grow Move precisely Reset Weigh
Influence Decrease Handle Operate Run
Initiate Demonstrate Increase Paint Set
 2013-14
LESSON PLAN
Unit-1
Regulation: R11

Name of the Faculty: Bijaya Kumar Biswal

Subject: Software Engineering Subject code:
SE
Unit: I
INSTRUCTIONAL OBJECTIVES:

Session Teaching
Topics to be covered
No Time Ref Method

Introduction to software Engineering

1 50 Min Black Board
TB1
The evolving role of software 50 Min
2 Black Board
TB1
Changing nature of software 50 Min
3 Black Board
TB1
Legacy systems, software myths 50 Min
4 Black Board
TB1
Software engineering- a layered technology 50 Min
5 PPT
TB1
Process frame work 50 Min
6 Black Board
TB1
CMMI, Process patterns 50 Min
7 PPT
TB1
Process assessment 50 Min
8 Black Board
TB1
Personal & team process models 50 Min
9 PPT
TB1

On completion of this lesson the student shall be able to (Outcomes)

1. Understand the basic SW engineering methods and practices, and their appropriate
application.

2. Describe software engineering layered technology and Process frame work.

 2013-14
ASSIGNMENT
Unit-I
Regulation: R11

Assignment / Questions

A1- Explain Software engineering Layered technology.

A2- What are the objectives of CMMI.

A3- Explain Software Myths.

Signature of Faculty

Note: Mention for each question the relevant objectives and outcomes.
 2013-14
LESSON PLAN
Unit-II
Regulation: R11

Name of the Faculty: Bijaya Kumar Biswal

Subject: Software Engineering Subject
Code: SE
Unit: II
INSTRUCTIONAL OBJECTIVES:

Session Teaching
Topics to be covered
No Time Ref Method

The water fall model, Incremental process models

50 Min Black Board
10 TB1,TB2
Evolutionary process models 50 Min
Black Board
11 TB1
Specialized process models 50 Min
Black Board
12 TB1,TB2
The unified process 50 Min
Black Board
13 TB1,TB2
Functional requirements 50 Min
Black Board
14 TB1,TB2
Non functional requirements 50 Min
Black Board
15 TB1,TB2
50 Min
Black Board
16 User requirements, System requirements TB1,TB2
50 Min
Black Board
17 System requirements & Interface specification TB1

On completion of this lesson the student shall be able to

1. Understanding of software process models such as the waterfall and evolutionary models.

2. Understanding of software requirements and the SRS documents

 2013-14
ASSIGNMENT
Unit-II
Regulation: R11

Assignment / Questions

A4- What are the phases of waterfall model.

A5- Explain about Functional and non-functional requirements.

A6- Explain about Spiral and Incremental process models.

Signature of Faculty

Note: Mention for each question the relevant objectives and outcomes.
 2013-14
LESSON PLAN
Unit-III
Regulation: R11

Name of the Faculty: Bijaya Kumar Biswal

Subject: Software Engineering Subject
Code: SE
Unit: III
INSTRUCTIONAL OBJECTIVES:

Session Teaching
Topics to be covered
No Time Ref Method

Feasibility studies TB2

50 Min Black Board
18
Requirements elicitation and analysis 50 Min TB2
Black Board
19
Requirements validation, 50 Min TB2
Black Board
20
Requirements management 50 Min TB2
Black Board
21
Context models, Behavioral models 50 Min TB2
Black Board
22
Structured methods 50 Min TB2
Black Board
23
data models, object models TB2
50 Min Black Board
24

On completion of this lesson the student shall be able to (Outcomes)

1. Understanding of the role of project management including planning, scheduling and risk
management.

2. Describe data models, object models, context models and behavioural models.
 2013-14
ASSIGNMENT
Unit-III
Regulation: R11

Assignment / Questions

A7. Briefly explain about the Requirements elicitation and analysis.

A8. Write short notes on Object models and structured methods.

Signature of Faculty

Note: Mention for each question the relevant objectives and outcomes.
 2013-14
LESSON PLAN
Unit-IV
Regulation: R11

Name of the Faculty: Bijaya Kumar Biswal

Subject: Software Engineering Subject
Code: SE
Unit: IV
INSTRUCTIONAL OBJECTIVES:

Session Teaching
Topics to be covered
No Time Ref Method

Design process & design quality

50 Min Black Board
25 TB1
Design concepts, The design models 50 Min TB1
Black Board
26
Software architecture 50 Min TB1
PPT
27
Data design 50 Min TB1
Black Board
28
Architectural styles & patterns 50 Min TB1
PPT
29
Architectural design, Assessing alternative architectural 50 Min TB1
designs PPT
30
Mapping data flow into a software architecture. 50 Min TB1
PPT
31

On completion of this lesson the student shall be able to (Outcomes)

1. Understanding of different software architectural styles.

2. Understanding of implementation issues such as modularity and coding standards.

 2013-14
ASSIGNMENT
Unit-IV
Regulation: R11

Assignment / Questions

A9. What is Software architecture? Briefly explain with Architectural styles and patterns.

A10. What is prototype in software engineering? Mapping data flow into a software architecture.

Signature of Faculty

Note: Mention for each question the relevant objectives and outcomes.
 2013-14
LESSON PLAN
Unit-V
Regulation: R11

Name of the Faculty: Bijaya Kumar Biswal

Subject: Software Engineering Subject
Code: SE
Unit: V
INSTRUCTIONAL OBJECTIVES:

Session Teaching
Topics to be covered
No Time Ref Method

Designing class based components, conducting component level

design 50 Min Black Board
32 TB1
Object constraint language 50 Min TB1
Black Board
33
Designing conventional components 50 Min TB1
Black Board
34
Golden rules, user interface analysis and design 50 Min TB1
Black Board
35
Interface analysis 50 Min TB1
36
Interface design steps, design evaluation 50 Min TB1
Black Board
37

On completion of this lesson the student shall be able to (Outcomes)

1. Understanding of approaches to verification and validation including static analysis and

reviews.

2. Understanding the Interface design steps and evaluation.

 2013-14
ASSIGNMENT
Unit-V
Regulation: R11

Assignment / Questions

A11. Briefly explain Design evaluation in modelling component level design.

A12. Write short notes on User interface analysis and design.

Signature of Faculty

Note: Mention for each question the relevant objectives and outcomes.
 2013-14
LESSON PLAN
Unit-VI
Regulation: R11

Name of the Faculty: Bijaya Kumar Biswal

Subject: Software Engineering Subject
Code: SE
Unit: VI
INSTRUCTIONAL OBJECTIVES:

Session Teaching
Topics to be covered
No Time Ref Method

A strategic approach to software testing

50 Min Black Board
38 TB1
Test strategies for conventional software 50 Min TB1
Black Board
39
Black box and white box testing, Validation testing 50 Min TB1
Black Board
40
System testing, The art of debugging 50 Min TB1
Black Board
41
Functional and Non functional testing 50 Min TB1
Black Board
42
Planning and Adhoc testing 50 Min
Black Board
43 TB1
50 Min TB1
Black Board
44 Test case format representation
Frame work for product metrics 50 Min TB1
PPT
45
Metrics for analysis model, metrics for design model 50 Min TB1
PPT
46
Metrics for source code, metrics for testing, metrics for 50 Min TB1
PPT
47 maintenance

On completion of this lesson the student shall be able to (Outcomes)

1. Understanding of software testing approaches such as unit testing and integration testing.

2. Understanding of approaches to verification and validation including static analysis and

metrics for analysis mode.

.
 2013-14
ASSIGNMENT
Unit-VI
Regulation: R11

Assignment / Questions

A13. Explain about test strategies for conventional software.

A14. What is the difference between product measurements and metrics.

Signature of Faculty

Note: Mention for each question the relevant objectives and outcomes.
 2013-14
LESSON PLAN
Unit-VII
Regulation: R11

Name of the Faculty: Bijaya Kumar Biswal

Subject: Software Engineering Subject
Code: SE
Unit: VII
INSTRUCTIONAL OBJECTIVES:

Session Teaching
Topics to be covered
No Time Ref Method

Software measurement
50 Min Black Board
48 TB1
Metrics for software quality 50 Min TB1
Black Board
49
Reactive vs. Proactive risk strategies 50 Min TB1
Black Board
50
Software risks 50 Min TB1
Black Board
51
Risk identification, Risk projection 50 Min TB1
Black Board
52
Risk refinement 50 Min
Black Board
53 TB1
RMMM, RMMM Plan TB1
50 Min Black Board
54

On completion of this lesson the student shall be able to

1. Understanding the software measurement and software risks.

2. Understanding risk refinement and risk projection.

 2013-14
ASSIGNMENT
Unit-VII
Regulation: R11

Assignment / Questions

A15. Discuss the direct and indirect measures of software process and product.

A16. Discuss about software tools for test case design.

Signature of Faculty

Note: Mention for each question the relevant objectives and outcomes.
 2013-14
LESSON PLAN
Unit-VIII
Regulation: R11

Name of the Faculty: Bijaya Kumar Biswal

Subject: Software Engineering Subject
Code: SE
Unit: VIII
INSTRUCTIONAL OBJECTIVES:

Session Teaching
Topics to be covered
No Time Ref Method

Quality concepts
50 Min Black Board
55 TB1
Software quality assurance 50 Min TB1
Black Board
56
Software reviews, formal technical reviews 50 Min TB1
Black Board
57
Statistical software quality assurance 50 Min TB1
Black Board
58
Software reliability 50 Min TB1
Black Board
59
The ISO 9000 quality standards 50 Min
Black Board
60 TB1

On completion of this lesson the student shall be able to

1. Understanding on quality control and how to ensure good quality software.

2. Understanding of software evolution and related issues such as version management.

 2013-14
ASSIGNMENT
Unit-VIII
Regulation: R11

Assignment / Questions

A17. What is meant by SQA? Discuss in detail SQA activities.

A18. What is formal technical review? Explain how it will assess software design quality.

Signature of Faculty

Note: Mention for each question the relevant objectives and outcomes.