SE31

2013-14
COURSE PLAN
Regulation: R11
FACULTY DETAILS:
Name of the Faculty::
Designation:
Department::
COURSE DETAILS
Name Of The Programme::
Designation::
Year
: III
Department::
Title of The Subject
No of Students
S.Divya
Assistant Professor
Information Technology
B.Tech
Assistant Professor
Batch::
Semester
Software Engineering
84
2011
: I
Subject Code
: 55029
2013-14
COURSE PLAN
Regulation: R11
FACULTY DETAILS:
Designation:
Department::
S.Divya
Assistant Professor
1. TARGET
a) Percentage Pass: 100
b) Percentage I class : 95
2.
COURSE PLAN
The topics of Units are covered by lectures, guest lectures, design exercises, solving numerical problems (if it consists of),
demonstration of models, and by assignments, etc.)
3.
4.
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
List out any new topic(s) or any innovation you would like to introduce in teaching the subject in this Semester.
Signature of HOD
Date:
Signature of Faculty
Date:
2013-14
GUIDELINES TO STUDY THE SUBJECT

Regulation: R11
FACULTY DETAILS:
S.Divya
Designation:
Assistant Professor
Department::
Guidelines for Preparing the Course:
Course Description:
Requirements, Analysis, Design, Implementation, Testing. Project Management. Applying a
development design process to produce high quality software. Topics include: identifying user
requirements; performing problem analysis to produce process oriented documentation; using UML
notation to create design models and diagrams; investigating and applying design patterns, project
management; configuration management. Completing software projects applying development
processes using an object-oriented language.
Course Objectives:
1. knowledge of basic SW engineering methods and practices, and their appropriate application;
2. A general understanding of software process models such as the waterfall and evolutionary
models.
3. An understanding of the role of project management including planning, scheduling, risk
management, etc.
4. An understanding of software requirements and the SRS document.
5. An understanding of different software architectural styles.
6. An understanding of implementation issues such as modularity and coding standards.
7. An understanding of approaches to verification and validation including static analysis, and
reviews.
8. An understanding of software testing approaches such as unit testing and integration testing.
9. An understanding of software evolution and related issues such as version management.
10. An understanding on quality control and how to ensure good quality software.
Learning Outcomes:
1. Students will demonstrate knowledge of the distinction between critical and non-critical
Systems.
2. Students will demonstrate the ability to manage a project including planning, scheduling and
risk Assessment/management.
3. Students will author a software requirements document.
4. Students will demonstrate an understanding of the proper contents of a software
requirements Document.
5. Students will author a formal specification for a software system.
6. Students will demonstrate an understanding of distributed system architectures and
application architectures.
7. Students will demonstrate an understanding of the differences between real-time and nonreal Time systems.
8. Students will demonstrate proficiency in rapid software development techniques.
9. Students will be able to identify specific components of a software design that can be targeted
3. For reuse.
10. Students will demonstrate proficiency in software development cost estimation.
2013-14
COURSE OBJECTIVES
Regulation: R11
FACULTY DETAILS:
Designation:
Department::
S.Divya
Assistant Professor
On completion of this Subject / Course the student shall be able to:

S.No
.
1.
Objectives
Outcomes
knowledge of basic SW engineering methods and Students will demonstrate knowledge of the
practices, and their appropriate application;
distinction between critical and non-critical
Systems.
2.
A general understanding of software process

models such as the waterfall and evolutionary
models.
Students will demonstrate the ability to manage a

project including planning, scheduling and risk
Assessment/management.
3.
An understanding of the role of project

Students will be able to create their own project
management including planning, scheduling, risk planning accordingly.
management, etc.
4.
An understanding of software requirements and Students will author a software & Hardware
the SRS document.
requirements document.
5.
An understanding of different software

architectural styles.
Students will demonstrate an understanding of

the proper contents of a software requirements .
6.
An understanding of implementation issues such Students will demonstrate an understanding of

as modularity and coding standards.
distributed system architectures and application
architectures.
7.
An understanding of approaches to verification

and validation including static analysis, and
reviews.
Students will demonstrate an understanding of

the differences between real-time and non-real
An understanding of software testing

approaches such as unit &integration testing.
Students will demonstrate proficiency in rapid

software development techniques.
An understanding of software evolution and

related issues such as version management.
Students will be able to identify specific

components of a software design that can be
targeted For reuse.
8.
9.
10.
An understanding on quality control and how to Students will demonstrate proficiency in software
ensure good quality software.
development cost estimation.
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:
Designation:
Department::
S.Divya
Assistant Professor
The expected outcomes of the Course / Subject are:

S.No.
General Categories of Outcomes
A.
An ability to apply knowledge of mathematics,

science, and engineering
B.
An ability to design and conduct experiments, as

well as to analyze and interpret data
Specific Outcomes of the Course
An ability to design a system, component, or

process to meet desired needs within realistic
Constraints such as economic, environmental,
social, political, ethical, health and safety,
Manufacturability and sustainability
C.
D.
An ability to function on multi-disciplinary teams
E.
An ability to identify, formulate, and solve

engineering problems
F.
An understanding of professional and ethical

responsibility
G.
An ability to communicate effectively
H.
The broad education necessary to understand the

impact of engineering solutions in a global,
economic, environmental, and societal context
I.
A recognition of the need for, and an ability to

engage in life-long learning
J.
A knowledge of contemporary issues
K.
An ability to use the techniques, skills, and

modern engineering tools necessary for
engineering practice.
Objectives Outcome Relationship Matrix (Indicate the relationships by

Outcomes
Objectives
mark).
G
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
2013-14
COURSE SCHEDULE
Regulation: R11
FACULTY DETAILS:
Designation:
Department::
The Schedule for the whole Course / Subject is::
S. No.
1.
2.
S.Divya
Assistant Professor
Description
Duration (Date)
From
To
Total No.
of Periods
Introduction to Software Engineering: The

evolving role of software, Changing Nature of
Software, legacy software, Software myths.A
Generic
view
of
process:
Software
engineering- Alayered technology, a process
framework, The capability Maturity Model
Integration(CMMI), Process patters,process
assessment, personal and team process models.
1-7-13
12-7-13
10
Process models: The waterfall model,

Incremental process models,Evolutionary
process models, Specialized process models,
The Unified process.Software Requirements:
Functional and non-fuctional requirements,
User requirements, System requirements,
Interface specification, the software
requirements document.
15-7-13
31-7-13
Requirements engineering process: Feasibility

studies, Requirements elicitation and analysis,
Requirements validation, Requirements
management. System models: Context
Models, Behavioural models, Data models,
Object models, structured methods.
1-8-13
7-8-13
3.
4.
Design Engineering: Design process and

Design quality, Design concepts, The design
model, pattern based software design. Creating
an architectural design: software architecture,
Data design, Architectural styles and patterns,
Architectural Design, assessing alternative
architectural design, mapping data flow into a
software architecture.
5.
Modeling components level design: Designing
class-based components, conducting
component-level design.Object constraint
language, designing conventional components,
Performing User interface design: Godlen
rules, User interface analysis and design,
interface analysis, interface design steps,
8-8-13
4-9-13
13
Design evaluation.
6.
5-9-13
19-9-13
Metrics for Process and Products: Software

Measurement, Metrics for software
quality.Risk management: Reactive vs
proactive Risk strategies, software risks, Risk
identification, Risk projection, Risk
refinement, RMMM,RMMM Plan.
20-9-13
30-9-13
Quality M anagement: Quality concepts,

Software quality assurance,Software Reviews,
Formal technical reviews, Statistical Software
quality Assurance, Software reliability, The
ISO 9000 quality standards.
3-10-13
23-10-13
Testing Strategies: Astrategic approach to

software testing, test strategies for
conventional software , Black-box and Whitebox testing, Validation testing, System testing,
the art of Debugging.Product metrics:Software
Quality, Frame work for Product metrics,
Metrics for Analysis Model, Metrics for
Design Model, Metrics for source code.
Metrics for testing, Metrics for maintenance.
Total No. of Instructional periods available for the course:
Hours / Periods
SCHEDULE OF INSTRUCTIONS
2013-14
UNIT - I
Regulation: R11
FACULTY DETAILS:
Designation:
Department::
SI.
No.
Date
No. of
Periods
S.Divya
Assistant Professor
Topics / Sub - Topics
Objectives &
Outcome
Nos.
Introduction to Software Engineering:

The evolving role of software, Changing
Nature of Software,
1-7-13 3
1
legacy software, Software myths.
References
(Text Book, Journal)
Page No___ to ___
Software Engineering: A
Practictionars Approach,
Roger S Pressman, six
edition. McGrawHill
International Edition,
2005. (TB1)
Software Engineering, Ian
SommerVille, seventh
edition, Pearson
education, 2004.
4-7-13 1
A Generic view of process: Software
engineering- Alayered technology
3
5-7-13 2
a process framework, The capability

Maturity Model Integration(CMMI)
4
9-7-13 2
Process patters,process assessment,

personal and team process models.
5
11-7-13 1
Overview
6
12-7-13 1
7
Conclusion
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.
(TB2)
2013-14
UNIT - II
Regulation: R11
FACULTY DETAILS:
Designation:
Department::
SI.
No.
Date
No. of
Periods
S.Divya
Assistant Professor
Objectives &
Outcome
Nos.
References
Page No___ to ___
Process models: The waterfall model,

Incremental process models,
15-7-13 3
(TB1), (TB2)
Evolutionary process models,

Specialized process models, The Unified
process.
18-7-13 1
Software Requirements: Functional and
non-fuctional requirements,
User
requirements,
System
requirements, Interface specification,
the software requirements document.
19-7-13 1
Overview and Conclusion
22-7-13 1
Date
MENTION THE CORRESPONDING COURSE OBJECTIVE AND OUT COME NUMBERS AGAINST EACH TOPIC.
2013-14
UNIT - III
Regulation: R11
FACULTY DETAILS:
Designation:
Department::
SI.
No.
Date
No. of
Periods
S.Divya
Assistant Professor
Objectives &
Outcome
Nos.
References
Page No___ to ___
Requirements engineering process:

Feasibility studies, Requirements
elicitation and analysis, Requirements
validation,
23-7-13 2
(TB1), (TB2)
Requirements elicitation and analysis,

Requirements validation,
26-7-13 2
Requirements management.
System models: Context Models,
29-7-13 1
Behavioral models, Data models, Object
models, structured methods.
30-7-13 1
Overview
31-7-13 1
Conclusion
1
Date
2013-14
UNIT - IV
Regulation: R11
FACULTY DETAILS:
Designation:
Department::
SI.
No.
Date
No. of
Periods
S.Divya
Assistant Professor
Objectives &
Outcome
Nos.
References
Page No___ to ___
Design Engineering: Design process and

Design quality, Design concepts,
1-8-13 2
(TB1), (TB2)
The design model, pattern based

software design.
5-8-13 1
Creating an architectural design:
software architecture, Data design,
Architectural styls and patterns
6-8-13 1
assessing
alternative
architectural
design, mapping data flow into a
software architecture.
7-8-13 1
Date
2013-14
UNIT - V
Regulation: R11
FACULTY DETAILS:
Designation:
Department::
SI.
No.
Date
No. of
Periods
S.Divya
Assistant Professor
Objectives &
Outcome
Nos.
References
Page No___ to ___
Modeling components level design:

Designing class-based components,
8-8-13 3
(TB1), (TB2)
conducting component-level design.

Object constraint language,
20-8-13 3
designing conventional components,
Performing ,User interface design
23-8-13 3
Godlen rules, User interface analysis and
design, interface analysis, interface
design steps, Design evaluation.
26-8-13 2
Over view and Conclusion
4-9-13 2
Date
2013-14
UNIT - VI
Regulation: R11
FACULTY DETAILS:
Designation:
Department::
SI.
No.
Date
No. of
Periods
S.Divya
Assistant Professor
Objectives &
Outcome
Nos.
References
Page No___ to ___
Testing Strategies: A strategic approach

to software testing, test strategies for
conventional software ,
5-9-13 3
(TB1), (TB2)
Black-box and White-box testing,

Validation testing, System testing, the
art of Debugging.
6-9-13 2
Product metrics: Software Quality,
Frame work for Product metrics, Metrics
for Analysis Model.
12-9-13 2
16-9-13 2
Metrics for Design Model, Metrics for

source code. Metrics for testing, Metrics
for maintenance.
Date
2013-14
UNIT - VII
Regulation: R11
FACULTY DETAILS:
Designation:
Department::
SI.
No.
Date
No. of
Periods
20-9-13 2
S.Divya
Assistant Professor
Objectives &
Outcome
Nos.
References
Page No___ to ___
Metrics for Process and Products:

Software Measurement, Metrics for
software quality.
7
2
22-9-13 2
Risk management: Reactive vs proactive

Risk strategies,
24-9-13 2
software risks, Risk identification, Risk

projection,
25-9-13 2
Risk refinement, RMMM,RMMM Plan.
27-9-13 1
Overview
30-9-13
Conclusion
(TB1), (TB2)
Date
2013-14
UNIT - VIII
Regulation: R11
FACULTY DETAILS:
Designation:
Department::
SI.
No.
Date
No. of
Periods
3-10-13 2
S.Divya
Assistant Professor
Quality Management: Quality concepts,

Software quality assurance,
5-10-13 2
Software Reviews, Formal technical

reviews,
8-10-13 2
Statistical Software quality Assurance,

Software reliability,
22-10-13 2
The ISO 9000 quality standards.
23-10-13 1
Objectives &
Outcome
Nos.
8,9,
10
References
Page No___ to ___
(TB1), (TB2)
Date
2013-14
COURSE COMPLETION STATUS
Regulation: R11
FACULTY DETAILS:
Name of the Faculty:: S.Divya
Subject:: Software Engineering
Department::
Actual Date of Completion & Remarks, if any
Subject Code: 55029
Nos. of
Units
Remarks
Objectives
Achieved
Unit 1
Unit 2
Unit 3
Unit 4
Unit 5
Unit 6
Unit 7
Unit 8
Signature of Dean of School

Date:
Date:
NOTE: AFTER THE COMPLETION OF EACH UNIT MENTION THE NUMBER OF OBJECTIVES ACHIEVED.
TUTORIAL SHEETS - II
2013-14
TUTORIAL SHEETS - I
Regulation: R11
FACULTY DETAILS:
Designation:
Department::
S.Divya
Assistant Professor
Date:
This Tutorial corresponds to Unit Nos.
Time:
Q1. What is software and software engineering?
Q2. what are the objectives of CMMI?
Q3. What are the phases of waterfall model?
Q4. Briefly explain about Functional and non-functional requirements.
Q5. What is Requirement validation and verification ?
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.

Date:
Date:
Regulation: R11
FACULTY DETAILS:
Designation:
Department::
S.Divya
Assistant Professor
Date:
Time:
Q1. Explain all System models.
Q2. Explain Design process and Design quality?
Q3. what is Software architecture? Briefly explain with Architectural styls and patterns.
Q4. Explain Golden rules in User interface design.
Q5. Briefly explain Design evaluation in Modeling component-level design.

Date:
Date:
2013-14
TUTORIAL SHEETS - II
Regulation: R11
FACULTY DETAILS:
Designation:
Department::
S.Divya
Assistant Professor
Date:
Time:
Q1. Explain about test strategies for conventional software.
Q2. what is the difference between product measurements and metrics?
Q3. Discuss about software tools for test case design
Q4. How should we use metrics during the project itself
Q5.

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
Knowledge
2
Comprehension
Understanding
Application
Analysis
Synthesis
Evaluation
of knowledge &
comprehension
of whole w.r.t. its

constituents
combination of
ideas/constituents
judgement
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
Adhere
Resolve
Bend
C. Psychomotor Domain (skill development)

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 preciselyReset
Influence
Decrease
Handle
Operate
Run
Initiate
Demonstrate
Increase
Paint
Set
Weigh
2013-14
LESSON PLAN
Unit-1
Name of the Faculty:

Subject
Unit
INSTRUCTIONAL OBJECTIVES:
Session
No
Regulation: R11
S.Divya
Subject Code
55029
Topics to be covered
Time
Ref
Teaching
Method
50min
TB1,TB 2
Black Board
Introduction to Software Engineering: The evolving role of

software, Changing Nature of Software,
1
legacy software, Software myths.

2
A Generic view of process: Software engineering- Alayered

technology
a process framework,
Integration(CMMI)
Process patters,process assessment, personal and team process

models.
6
7
The
capability
Maturity
Model
Overview
Conclusion
On completion of this lesson the student shall be able to (Outcomes)

1. Students will demonstrate knowledge of the distinction between critical and non-critical
Systems.
2. Students will demonstrate the ability to manage a project including planning, scheduling and
risk Assessment/management.
3. Students will author a software requirements document.
4 Students will demonstrate an understanding of the proper contents of a software requirements
2013-14
ASSIGNMENT
Unit-I
Regulation: R11
Assignment / Questions
1. Explain Software engineering Layered technology?

Objectives: Students will demonstrate knowledge of the distinction between critical and noncritical Systems.
2. Explain Software Myths?
Note: Mention for each question the relevant objectives and outcomes.
2013-14
LESSON PLAN
Unit-II

Subject
Unit
Session
No
Regulation: R11
S.Divya
Subject Code
55029
II
Time
Ref
Teaching
Method
50min
TB1,TB 2
Black Board
Process models: The waterfall model, Incremental process

models,
1
Evolutionary process models, Specialized process models, The

Unified process.
50min
Software Requirements:
requirements,
Functional
and
non-fuctional 50min
User
requirements,
System
requirements,
specification, the software requirements document.
4
On completion of this lesson the student shall be able to

1. Different types of models
2. Identify functional and non-functional requirements.
3. User requirements, system requirements
4. Prepare the documentation.
Interface
50min
2013-14
ASSIGNMENT
Unit-II
Regulation: R11
1.Explain about Spiral and Incremental process models.

2.What is Software requirement document?
Outcomes: Students will author a software requirements document.
2013-14
LESSON PLAN
Unit-III

Subject
Unit
Session
No
Regulation: R11
S.Divya
Subject Code
55029
III
Time
Ref
Teaching
Method
50min
TB1,TB 2
Black Board
Requirements engineering process: Feasibility studies,

Requirements elicitation and analysis, Requirements validation,
1
Requirements elicitation and analysis, Requirements validation,

Requirements management.
5
6
System models: Context Models,

Behavioral models, Data models, Object models, structured
methods.
Overview
Conclusion
On completion of this lesson the student shall be able to(Outcomes)

1. Know about what consists under Requirements elicitation and analysis
2.
Know the difference between verification and validation
3.
Different types of models
4.
Structured methods.
2013-14
ASSIGNMENT
Unit-III
Regulation: R11
1.Briefly explain about the Requirements elicitation and analysis.

2.Write short notes on
(a) Object models and
(b) Structured methods.
Objective: Students will author a formal specification for a software system.
2013-14
LESSON PLAN
Unit-IV

Subject
Regulation: R11
S.Divya
Unit
Session
No
Subject Code
55029
IV
Time
Ref
Teaching
Method
50min
TB1,TB 2
Black Board
Design Engineering: Design process and Design quality, Design

concepts,
1
The design model, pattern based software design.

2
Creating an architectural design: software architecture, Data

design,
3
Architectural styles and patterns
Assessing alternative architectural design, mapping data flow

into software architecture.

1. Students will demonstrate an understanding of distributed system architectures and
2. Make selection different architectural style patterns

3. Assessing alternative architectural design
4. Mapping data flow into a software architecture.
5.
2013-14
ASSIGNMENT
Unit-IV
Regulation: R11
1.What is prototype in software engineering? Mapping data flow into a software architecture.
2.Explain with DFD for all Design concept

Objective: Students will demonstrate an understanding of distributed system architectures and
2013-14
LESSON PLAN
Unit-V

Subject
Unit
Session
No
Regulation: R11
S.Divya
Subject Code
55029
Time
Ref
Teaching
Method
50min
TB1,TB 2
Black Board
Modeling components level design: Designing class-based

components,
1
conducting component-level design.

2
Object constraint language,
designing conventional components, Performing ,User interface

design
Godlen rules, User interface analysis and design, interface

analysis, interface design steps, Design evaluation.
Over view and Conclusion

1.Modeling design with class and object
2.user interface design
3.importance of golden rules
4 interface design steps and design evaluation.
2013-14
ASSIGNMENT
Unit-V
Regulation: R11
1.Write short notes on User interface analysis and design.
2.How the Golden rules are useful in User interface Design.
2013-14
LESSON PLAN
Unit-VI

Subject
Unit
Session
No
Regulation: R11
S.Divya
Subject Code
55029
VI
Time
Ref
Teaching
Method
50min
TB1,TB 2
Black Board
Testing Strategies: Astrategic approach to software testing, test

strategies for conventional software ,
1
Black-box and White-box testing, Validation testing, System

testing, the art of Debugging.
2
Product metrics:Software Quality, Frame work for Product

metrics, Metrics for Analysis Model, Metrics for Design Model,
Metrics for source code. Metrics for testing, Metrics for
maintenance.

1.Strategic approach on software testing
2.different types of testing
3.product metrics
4 metrics on all phases.
2013-14
ASSIGNMENT
Unit-VI
Regulation: R11
1. How can you explain about the Metrics for maintenance?

2. Give some Metrics for source code.
Objective : Students will be able to identify specific components of a software design that can be
targeted with implementation and then testing.
2013-14
LESSON PLAN
Unit-VII

Subject
Unit
Session
No
Regulation: R11
S.Divya
Subject Code
55029
VII
Time
Ref
Teaching
Method
50min
TB1,TB 2
Black Board
Metrics for Process and Products: Software Measurement,

Metrics for software quality.
1
2
3
4
5
6
Risk management: Reactive vs proactive Risk strategies,

software risks, Risk identification, Risk projection,
Risk refinement, RMMM,RMMM Plan.
Overview
Conclusion

1.Measure the software products
2.find metrics for software quality
3.Identify risks
4 RMMM plan.
2013-14
ASSIGNMENT
Unit-VII
Regulation: R11
1. Discuss the direct and indirect measures of software process and product
2. What is meant by BVA? Discuss the guidelines to create BVA test cases.
Objective: Students will demonstrate proficiency in software development cost estimation.
2013-14
LESSON PLAN
Unit-VIII

Subject
Unit
Session
No
1
2
3
4
5
Regulation: R11
S.Divya
Subject Code
55029
VIII
Time
Quality Management: Quality concepts, Software quality

assurance,
50min
Software Reviews, Formal technical reviews,
50min
Statistical Software quality Assurance, Software reliability,
50min
The ISO 9000 quality standards.
50min
50min

1.Know about SQA
2.How are the reviews
3. ISO 9000 quality standards
4. Statistical Software quality Assurance
Ref
Teaching
Method
TB1,TB 2
Black Board
2013-14
ASSIGNMENT
Unit-VIII
Regulation: R11
1. The Mean-Time-Between-Failure(MTBF)concept for software is open to criticism.
2. Can a program be correct and still not be reliable?

SE31

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

SE31

Caricato da

Copyright:

Formati disponibili

2013-14

Continuous Assessment Examinations (CAE 1, CAE 2)

Term End Examination

GUIDELINES TO STUDY THE SUBJECT

Guidelines for Preparing the Course:

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

A general understanding of software process

Students will demonstrate the ability to manage a

An understanding of the role of project

An understanding of different software

Students will demonstrate an understanding of

An understanding of implementation issues such Students will demonstrate an understanding of

An understanding of approaches to verification

Students will demonstrate an understanding of

An understanding of software testing

Students will demonstrate proficiency in rapid

An understanding of software evolution and

Students will be able to identify specific

The expected outcomes of the Course / Subject are:

General Categories of Outcomes

An ability to apply knowledge of mathematics,

An ability to design and conduct experiments, as

Specific Outcomes of the Course

An ability to design a system, component, or

An ability to function on multi-disciplinary teams

An ability to identify, formulate, and solve

An understanding of professional and ethical

An ability to communicate effectively

The broad education necessary to understand the

A recognition of the need for, and an ability to

A knowledge of contemporary issues

An ability to use the techniques, skills, and

Objectives Outcome Relationship Matrix (Indicate the relationships by

Introduction to Software Engineering: The

Process models: The waterfall model,

Requirements engineering process: Feasibility

Design Engineering: Design process and

Metrics for Process and Products: Software

Quality M anagement: Quality concepts,

Testing Strategies: Astrategic approach to

Total No. of Instructional periods available for the course:

Topics / Sub - Topics

Introduction to Software Engineering:

a process framework, The capability

Process patters,process assessment,

Topics / Sub - Topics

Process models: The waterfall model,

Evolutionary process models,

Topics / Sub - Topics

Requirements engineering process:

Requirements elicitation and analysis,

Topics / Sub - Topics

Design Engineering: Design process and

The design model, pattern based

Topics / Sub - Topics

Modeling components level design:

conducting component-level design.

Topics / Sub - Topics

Testing Strategies: A strategic approach

Black-box and White-box testing,

Metrics for Design Model, Metrics for

Topics / Sub - Topics

Metrics for Process and Products:

Risk management: Reactive vs proactive