3-Se (13 CS 301) 14-06-2016

K L University
Department of Computer Science & Engineering

Course Handout for III Year B.Tech PROGRAM
A.Y.2016-17, First Semester
Course Name
Course Code
: Software Engineering
: 13 CS 301
L-T-P structure
: 3-0-2
Course Credits
:4
Course Coordinator
: Dr.K.V.D.Kiran
Course Instructors
: Dr.V.Rama Krishna,
Mr.G.Siva Nageswara Rao,
Dr.G.Sridevi,
Dr. C.V.P.R.Prasad,
Mr.G.V.S.Prasad,
Mrs.P.Vijaya Lakshmi
Course Teaching Associates
Course Objective:
This course is to provide students with an overview of the concepts and fundamentals of software
engineering .The objective of Software Engineering is to enable the student to understand, grasp and
practice the software development process, various software models that evolved till date, analyze a given
problem in a domain, design software solution to the problem, impart quality to software through coding
and testing and deliver the software for operation and maintenance.
Course Rationale:
Software Engineering is about the discipline needed to develop high quality software that can be
understood, maintained and adapted over long periods of time by many different people . In order to
enable the student to develop quality software, the course provides an overview of the software
engineering discipline, introducing the fundamental principles and methods in software engineering and
highlights the need for an engineering approach to translate the problem into software. It provides an
opportunity for the students to gain knowledge of industrial approach to real-world projects and
importance of team environment. The course then details various methods and models to train the student
to learn the process of gathering user requirements, analyzing them, and designing both functional and
non functional requirements emphasizing system constraints incorporating Quality assurance. The student
is then exposed to the existing design models and patterns for different domains. The student is then
enabled to code and test software with quality that can be delivered to the user so that he can operate and
maintain software.
Course Outcomes (CO): Students will able to
CO
CO
No:
1
Summarize software evolution and software development process models with
emphasis on agile methodology by including modeling core principles
2
Demonstrate the concepts of requirement modeling carrying out the analysis
and basic design model with a case study
SO
a
BT
L
1
b,e
3
4
5
Examine Software Architecture, Software design and Demonstrate User Interface

for an application using golden rules of HCI
Illustrate testing strategies and software quality assurance for a given case
study.
Demonstrate conceptualization, analysis and design of software using software
case tools
COURSE OUTCOME INDICATORS (COI): Students will able to

CO
COI-1
COI-2
No.
1
Understand
the
nature
& Identify and explain a process
evolution
of
software
and model either in conventional or
distinguish between desktop, evolutionary or unified process
mobile and web applications. and agile process with a case
Discuss different phases and study
myths involved in the software
development
2
Analyze the concepts
of Illustrate
the
requirements
understanding requirements
modeling,
scenarios,
information
and
analysis
classes, patterns and web apps
3
Infer about the architecture and Develop the concepts of UI
component design concepts of design rules
software with a set of classes
4
Experiment with the review Explain the various issues for
concepts and software quality software testing strategies
assurance
5
Demonstrate the basic programs Project
work
in
Software
by including UML designs
Engineering
b,e
b,e
COI-3
Examine
extreme
programming and other Agile
models and core principles
that guide for each framework
activity
Inspect the methodology of
carrying out design concepts
and models with a case study
Examine the quality concepts
and
their
standards
for
achieving excellence software
Identify the issues present in
testing
conventional
applications
SYLLABUS (As approved by BoS):

Software and software engineering: Nature of software, software application domains, unique nature of
web applications, software engineering, software process, software engineering practices, software myths.
Process models: Generic process models, perspective models, product and process. Agile development:
Agility, agile process, extreme programming and other agile process models. Modeling: Core Principles,
principles that guide each framework activity, Understanding requirements: identifying stakeholders,
eliciting requirements, building requirement model, negotiating and validation requirements, Requirement
Modeling Design Concepts: Design process, Concepts and models. Architecture design: software
architectures, architecture styles and designs, assessing alternative architectural designs, architectural
mapping using dataflow. Component level design: Designing class based components, conducting
component level design. User Interface design: The golden rules, User interface analysis and design,
interface analysis and interface designs steps. Quality concepts: Software Quality, Software quality
dilemma, achieving software quality. Review Techniques, software quality assurance: Elements of software
quality assurance, sqa tasks, goals, forma approaches, and software testing strategies: A Strategic
approach to software testing, Strategic issues, test strategies for conventional software, validation testing,
and system testing, and testing conventional applications.
BoS Approved Text book:
1. Roger S.Pressman ,Software Engineering A Practioners Approach , 7 th Editon, Mc GrawHill (2010).
BoS Approved Reference Books:

1. Ian Somerville, Software engineering, sixth edition, Pearson education 2001
2. Software engineering : Modern Approaches by Wiley, 2nd edition,2010
3. Shari lawerence, Software engineering and practice ,4/e prentice hall, 2009
Deviations (if any) from BoS approved syllabus and the topics planned:
NIL.
COURSE DELIVERY PLAN:

Ses
s.
No.
C
O
CO
I
Topic (s)
Course Handout Explanation ,Introduction, Nature of

Software, Software process and myths
Process Models: Generic process model, Prescriptive

Process Models
Specialized process models, Unified process model
Agile development: Agility, agile process
Extreme programming ,Other Agile Models
Core principles and principles that guide each

framework activity
Experiment with user requirements, Identify

stakeholders, recognizing multiple view points
Building the requirement models, Eliciting ,validating

requirements
Requirement analysis and different modeling concepts
10
Requirement modeling strategies
TeachingLearning
Methods
Chalk and Talk,
PPTsListens &
Practice
Active Learning
Chalk and Talk,
PPTsListens &
Practice
Active Learning
Chalk and Talk,
PPTsListens &
Practice
Lab taken to
class
Chalk and Talk,
PPTsListens &
Practice Lab
taken to class
Chalk and Talk,
PPTsListens &
Practice Lab
taken to class
Chalk and Talk,
PPTsListens &
Practice Lab
taken to class
Chalk and Talk,
PPTsListens &
Practice
Lab taken to
class
Chalk and Talk,
PPTsListens &
Practice
Active Learning
Chalk and Talk,
PPTsListens &
Practice
Lab taken to
class
Chalk and Talk,
PPTsListens &
Practice
Lab taken to
class
Evaluation
Components
Q&A,
Test 1,
Semester End
Exam (SE
Exam)
Quiz
Test 1, SE
Exam
Illustrate Use
of Star UML
tool for
Software
Design
Test 1, SE
Exam
Use case
diagram for
Bank ATM
Test 1, SE
Exam
Activity
diagram for
Bank ATM
Test 1, SE
Exam
Class diagram
for Bank ATM
Test 1, SE
Exam
Sequence
diagram for
Bank ATM
Test2,
SE Exam
Quiz
Test 2, SE
Exam
Use case
diagram for
Library
Scenario
Test 2, SE
Exam
Activity
diagram for
Library
Scenario
Test 2, SE
Exam
11
Design process, concepts
12
Design models
13
Architecture styles and design, Assessing Alternative

Architectural Designs
14
Designing Class-Based Components, Component-Based

Development
15
16
The Golden Rules, User Interface Analysis and Design
Interface Analysis & Design Steps
17
Software Quality, The Software Quality Dilemma
18
Achieving Software Quality
19
20
Chalk and Talk,

PPTsListens &
Practice
Lab taken to
class
Chalk and Talk,
PPTsListens &
Practice
Lab taken to
class
Chalk and Talk,
PPTsListens &
Practice
Lab taken to
class
Chalk and Talk,
PPTsListens &
Practice
Lab taken to
class
Chalk and Talk,
PPTsListens &
Practice
Active Learning
Chalk and Talk,
PPTsListens &
Practice
Lab taken to
class
Chalk and Talk,
PPTsListens &
Practice
Lab taken to
class
Chalk and Talk,
PPTsListens &
Practice
Active Learning
Review Metrics and Their Use, informal reviews,

Elements of Software Quality Assurance
Chalk and Talk,

PPTsListens &
Practice
Lab taken to
class
SQA Tasks, Goals, and Metrics, Software Reliability, The

ISO 9000 Quality Standards
Chalk and Talk,

PPTsListens &
Practice
Lab taken to
class
Class diagram
for Library
Scenario
Test 2, SE
Exam
Sequence
diagram for
library
scenario
Test 2, SE
Exam
State chart
diagram for
Library
Scenario
Test 3, SE
Exam
Difference
between state
and activity
diagrams
Test 3, SE
Exam
One minute
paper
Test 3, SE
Exam
Difference
between
sequence and
activity
diagrams
Test 3, SE
Exam
State chart
diagram for
Bank Scenario
Test3,
SE Exam
Q&A
Test 3, SE
Exam
Use case
diagram for
school of
engineering
Semester End
Exam (SE
Exam)
Activity
diagram for
school of
engineering
Semester End
Exam (SE
Exam)
21
22
23
24
A Strategic Approach to Software Testing, Test

Strategies for Conventional and object oriented
Software
Chalk and Talk,

PPTsListens &
Practice
Lab taken to
class
System Testing
Chalk and Talk,

PPTsListens &
Practice
Lab taken to
class
White box testing , black box testing
Chalk and Talk,

PPTsListens &
Practice
Lab taken to
class
Model based testing , testing for specialized

environments and applications
Chalk and Talk,

PPTsListens &
Practice
Active Learning
Class diagram
for school of
engineering
Semester End
Exam (SE
Exam)
Sequence
diagram for
school of
engineering
Semester End
Exam (SE
Exam)
State chart
diagram for
school of
engineering
Semester End
Exam (SE
Exam)
Q&A
Semester End
Exam (SE
Exam)
Session wise Teaching Learning Plan

At the end of each session students will able to
Session Number:1
Session Outcome: To explain the purpose of software.
To discuss various properties of software and mthys.
Time(min)
10
20
10
20
Topic
Introduction and description of software engineering (se)
Syllabus
Explanation of Course Handout, The Nature of Software
Active Learning Method
Software Application Domains
BT
L
1
1
1
1
20
The Software Process, Software Myths
10
05

Conclusion & Summary
1
1
Teaching Learning Method

Talk Discussion
Chalk and Talk, PPTsObserve
Q &A
Chalk and Talk, PPTs Observe
Chalk and Talk, PPTs
Observe
Q &A
Discussion
Session Number: 2
Session Outcome:
1 Differentiate various process models
2. Discuss process assessment and improvement
Time(min)
10
Topic
Recap / Introduction
BT
L
1

Talk Discussion
30
25
20
10
A Generic Process Model, Prescriptive Process Models

Process Assessment and Improvement
1
1
1
1

Observe
Observe
Quiz
Discussion
Session Number:3
Session Outcome:
1. Study the Various process & products.
2. Study the software process on different applications .
Time(min)
Topic
BT
L
1
10
10
Specialized Process Models
20
The Unified Process
10
Personal and Team Process Models
10
Product and Process
30
05
Discussion and explaining the working of Star UML

software

Talk Discussion
Observe
Observe
Observe
Observe
Discussion
Session Number:4
Session Outcome:
1. Understand the logical structure with methodologies
2. Discuss work performed using agility models.
3. Benefits about agile process models
Time(min)
Topic
BT
L
1
10
20
What Is Agility?
20
Agility Principles
20
The Politics of Agile Development
20
Active Learning Method: LTC (ATM)
05

Talk Discussion
Observe
Observe
Observe
Construct a Use case
diagram for Bank ATM in
Laptop
Discussion
Session Number:5
Session Outcome:
1. Benefits of extreme programming
2. Apply the extreme programming concept to software development
Time(min)
Topic
BT
L
1
10
Introduction
30
Extreme Programming (XP)
10
Other Agile Process Models
20
A Tool Set for the Agile Process
20
Active Learning Method: LTC (ATM)
05

Talk Discussion
Construct an Activity
Laptop
Discussion
Session Number:6
Session Outcome:
1. Identify stakeholders of each framework activity

2. Recognizing multiple view points
Time(min)
Topic
10
Introduction
25
Software Engineering Knowledge
15
Core Principles
BT
L
1
1
1
20
Principles That Guide Each Framework Activity
20
05
Active Learning Method: LTC

1
1

Talk Discussion
Class diagram for Bank ATM
Discussion
Session Number:7
Session Outcome:
1. Building a requirement model
2. Apply negotiating requirements to the process model
Time(min)
Topic
BT
L
1
10
Recap/Introduction
20
Requirements Engineering
10
Identifying Stakeholders
20
Recognizing Multiple Viewpoints
10
Working toward Collaboration

Talk Discussion
Observe
Observe
Observe
20
05
Observe
Construct a Sequence
Laptop
Discussion
Session Number:8
Session Outcome:
1. Understand how requirement gathering is performed
2. Apply modeling requirements to process models
Time(min)
10
20
Topic
Recap/Introduction
Eliciting Requirements
BT
L
1
1
10
Developing Use Cases
20
Building the Requirements Model
20
Negotiating Requirements, Validating Requirements
10
05

2
1

Talk Discussion
Observe
Observe
Observe
Observe
Interaction, Quiz
Discussion
Session Number:9
Session Outcome:
1. Understand Scenario based modeling
2. Understand data modeling concepts
Time(min)
Topic
BT
L
1
10
Recap/Introduction
20
Requirements Analysis
10
Scenario-Based Modeling
20
Data Modeling Concepts
10
Class-Based Modeling, Class-Responsibility-Collaborator

(CRC) Modeling
20
05
Session Number:10
Session Outcome:

Talk Discussion
Construct a Use case
diagram for Library Scenario
in Laptop.
Discussion
1. Understand requirement modeling

2. Discuss on identifying events for a use case
Time(min)
Topic
BT
L
1
10
Recap/Introduction
20
Requirements Modeling Strategies
10
Creating a Behavioral Model
20
Patterns for Requirements Modeling
10
Identifying Events with the Use Case
20
Active Learning Method: LTC (Library Scenario)
05

Talk Discussion
in Laptop
Discussion
Session Number:11
Session Outcome: learn Design process Issues
Compare between process and product
Time(min)
10
20
40
20
05
Topic
Recap/Introduction
The Design Process
The Evolution of Software Design, Design Concepts
BT
L
1
1
1
2
1

Talk-Discussion
Chalk and Talk, PPTSs Observe
Chalk and Talk, PPTSs Observe
Construct Class diagram in
Laptop
Discussion
Session Number:12
Session Outcome: learn Architectural design elements
Study f various component level design
Time(min)
10
40
Topic
Recap/Introduction
The Design Model
BT
L
1
1
40
Architectural Design Elements, Component-Level Design

Elements
20
05

Talk - Discussion
diagram for library scenario
in Laptop
Discussion
Session Number:13
Session Outcome: learn software architecture and their styles
Understand architectural design for data flow
Time(min)
10
20
10
20
BT
L
1
Topic
Recap/Introduction
Software Architecture
Architectural Styles
Architectural Design
25
Assessing Alternative Architectural Designs, Mapping

Using Data Flow
15
05

Talk Discussion
Construct a State chart
in Laptop
Discussion
Session Number:14
Session Outcome: Study of Class-based Components
Time(min)
10
BT
L
1
Topic
20
Component-Based Development
10
Active Learning Method:
Talk Discussion
Discussion on state and
activity diagrams
05
Discussion
20
10
20
Recap/Introduction
What
Is
a
Component?,
Designing
Components
Component-Level Design for WebApps
Designing Traditional Components
Class-Based
1
1
1
Session Number:15
Session Outcome: Study of Golden rules
How to design a user interface
Time(min)
10
20
20
20
15
05
Topic
Recap/Introduction
The Golden Rules
User Interface Analysis and Design
Interface Analysis and Design Models
Session Number:16
Session Outcome: Study interface design steps
BT
L
1
1
1
2
2
1

Talk Discussion
Q&A (One minute paper)
Discussion
Learn interface design steps

Time(min)
10
30
Topic
Recap/Introduction
Interface Analysis
BT
L
1
1
10
Task Analysis and Modeling
20
Interface Design Steps
20
05

Talk Discussion
Discussion on Sequence and
activity diagrams
Discussion
Session Number:17
Session Outcome: Study elements involved in quality
Learn how quality placed a vital role in software
Time(min)
Topic
BT
L
1
10
Recap/Introduction
20
What Is Quality?, Software Quality
30
The Software Quality Dilemma
15
The Impact of Management Actions
15
Active Learning Method: LTC (Bank Scenario)
05

Talk Discussion
diagram for Bank Scenario
in Laptop
Discussion
Session Number:18
Session Outcome: Study Project Management techniques
Understand project management for achieving quality
Time(min)
Topic
10
Recap/Introduction
40
Achieving Software Quality
20
20
05
Project Management Techniques, Quality Control and

Assurance
BT
L
1
2
2
2
1

Talk Discussion
Q &A
Discussion
Session Number:19
Session Outcome: learn Formal Technical Reviews
Understand different metrics involved for software
Time(min)
Topic
BT
L
1
10
Recap/Introduction
20
Defect Amplification and Removal
20
Review Metrics and Their Use
20
Informal Reviews, Formal Technical Reviews
20
Active Learning Method: (LTC)
05

Talk Discussion
Construct Use case diagram
for school of engineering in
Laptop
Discussion
Session Number:20
Session Outcome: study the elements of software quality assurance
Time(min)
Topic
BT
L
1
10
Recap/Introduction
20
Elements of Software Quality Assurance
20
SQA Tasks, Goals, and Metrics
20
Formal Approaches to SQA, Software Reliability, quality

Talk Discussion
Chalk and Talk, PPTs -
standards
20
05
Observe
diagram for school of
engineering in Laptop
Discussion
Session Number:21
Session Outcome: examine the working of software testing
Study different testing strategies
Time(min)
Topic
BT
L
1
10
Recap/Introduction
20
A Strategic Approach to Software Testing
20
Strategic Issues
20
Test Strategies for Conventional Software, Object-Oriented

Software
20
05

Talk Discussion
Construct a Class diagram
for school of engineering in
Laptop
Discussion
Session Number:22
Session Outcome: Able to learn Testing concepts
Understand the validation and verification
Time(min)
Topic
BT
L
1
10
Recap/Introduction
20
Validation Testing
30
System Testing
15
The Art of Debugging
15
05

Talk Discussion
Discussion
Session Number:23
Session Outcome: learn White box testing concepts
Understand control structures
10
Recap/Introduction
BT
L
1
20
White-Box Testing
40
Basis Path Testing , Control Structure Testing
Time(min)
Topic

Talk Discussion
20
05

Discussion
Session Number:24
Session Outcome: : Study the testing concepts
Understand different patterns for testing
Time(min)
BT
L
1
Topic
10
Recap/Introduction
Talk Discussion
20
Black-Box Testing
20
Model-Based Testing
20
Testing for Specialized Environments, Architectures, and

Applications
20
Q &A
05
Discussion
EVALUATION PLAN:
Evaluati
on
Compon
ent
Weighta
ge/Mark
s
Date
Duratio
n
(Hours)
CO 1
CO 2
CO 3
CO 4
COI
Number
BTL
2.5
2.5
2.5
10
10
10
2.5
2.5
2.5
10
10
10
2.5
2.5
2.5
10
10
10
Test 1
Test 2
Test 3
Active
Learnin
g & L-T-C
Weighta
ge
(7.5%)
Weightag
e (7.5 %)
Max
Marks
(30)
1:30
Weightag
e (7.5 %)
Max
Marks
(30)
1:30
Weightag
e (7.5%)
Max
Marks
(30)
Weighta
ge
(7.5%)
1
Max
Marks
(25)
Internal
Lab Exam
1:30
Weightage
(5%)
Max Marks
(20)
2.5
0.1
0.2
0.3
0.5
0.5
0.5
0.5
0.5
0.5
0.5
0.5
0.5
Attendance
Sem end
Lab
Exam
Sem End
Project
exam
Semeste
r End
Exam
Weightage
(5%)
Weightage
(5%)
0.1
0.2
0.3
0.5
0.5
0.5
0.5
0.5
0.5
0.5
0.5
0.5
Max Marks
(20)
Weightage
(10%)
0.5
0.5
0.5
0.5
Max Marks
(30)
Weighta
ge
(45%)
Max
Marks(6
0)
Questio
n
Number
3
3:00
4
1
or
2
4
1
or
2
4
1
or
2
4
3
or
4
4
3
or
4
4
5
or
6
4
5
or
6
4
5
or
6
3
or
4
7
or
8
6
8
7
or
8
7
or
8
Course Team members, Chamber Consultation Hours and Chamber Venue details:
S.No.
Name of Faculty
Dr.V.Rama Krishna
Chamber
Consultatio
n Day(s)
Chamber
Chamber
Consultation
Consultatio
Timings for each n Room No:
day
Each Thursday Thursday - 5.00 to
CSE Ground
And Saturday 8.00 P.M
Floor Lab
Saturday:-9.00 to 11.00 C512
AM
Dr.G.Sridevi
Each Thursday Thursday - 5.00 to 8.00 CSE Ground

And Saturday P.M
Floor Lab
Saturday:-9.00 to 11.00 C5606
AM
Dr.K.V.D.KIRAN
Each Friday
Friday - 5.00 to 8.00 CSE Ground
And Saturday P.M
Floor Lab
Saturday:-9.00 to 11.00 C416
AM
Dr. C.V.P.R. Prasad
Each Thursday Thursday - 5.00 to 8.00 CSE Ground

And Saturday P.M
Floor Lab
Saturday:-9.00 to 11.00
AM
Mr.G.Siva Nageswara Each Thursday Thursday - 5.00 to

CSE Ground
Rao
And Saturday 8.00 P.M
Floor Lab
Saturday:-9.00 to 11.00 C413
AM
Mr.G.V.S.Prasad
Each
Wednesday - 5.00 to
CSE Ground
Wednesday
8.00 P.M
Floor Lab
And Saturday Saturday:-9.00 to 11.00 C 406
AM
Mrs.P.Vijaya Lakshmi Each
Wednesday - 5.00 to
CSE Ground
Wednesday
8.00 P.M
Floor Lab
And Saturday Saturday:-9.00 to 11.00 EEE 409
AM
Signature
of
Course faculty
Signature of COURSE COORDINATOR:
Recommended by HEAD OF DEPARTMENT:

Approved By: DEAN-ACADEMICS
(Sign with Office Seal)
(a) an ability to apply knowledge of mathematics, science,

to engineering
(b) an ability to design and conduct experiments, as well as
to analyze and interpret data
(e) an ability to identify, formulate, and solve engineering
problems

3-Se (13 CS 301) 14-06-2016

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3-Se (13 CS 301) 14-06-2016

Uploaded by

Copyright:

Available Formats

K L University

Department of Computer Science & Engineering

Course Teaching Associates

Examine Software Architecture, Software design and Demonstrate User Interface

COURSE OUTCOME INDICATORS (COI): Students will able to

SYLLABUS (As approved by BoS):

BoS Approved Reference Books:

COURSE DELIVERY PLAN:

Course Handout Explanation ,Introduction, Nature of

Process Models: Generic process model, Prescriptive

Specialized process models, Unified process model

Agile development: Agility, agile process

Extreme programming ,Other Agile Models

Core principles and principles that guide each

Experiment with user requirements, Identify

Building the requirement models, Eliciting ,validating

Requirement analysis and different modeling concepts

Requirement modeling strategies

Design process, concepts

Architecture styles and design, Assessing Alternative

Designing Class-Based Components, Component-Based

The Golden Rules, User Interface Analysis and Design

Interface Analysis & Design Steps

Software Quality, The Software Quality Dilemma

Achieving Software Quality

Chalk and Talk,

Review Metrics and Their Use, informal reviews,

Chalk and Talk,

SQA Tasks, Goals, and Metrics, Software Reliability, The

Chalk and Talk,

A Strategic Approach to Software Testing, Test

Chalk and Talk,

Chalk and Talk,

White box testing , black box testing

Chalk and Talk,

Model based testing , testing for specialized

Chalk and Talk,

Session wise Teaching Learning Plan

The Software Process, Software Myths

Active Learning Method

Teaching Learning Method

Teaching Learning Method

A Generic Process Model, Prescriptive Process Models

Chalk and Talk, PPTs

Specialized Process Models

The Unified Process

Personal and Team Process Models

Product and Process

Discussion and explaining the working of Star UML

Teaching Learning Method

Chalk and Talk, PPTs

The Politics of Agile Development

Active Learning Method: LTC (ATM)

Conclusion & Summary

Teaching Learning Method

Extreme Programming (XP)

Other Agile Process Models

A Tool Set for the Agile Process

Active Learning Method: LTC (ATM)

Conclusion & Summary

Teaching Learning Method

1. Identify stakeholders of each framework activity

Software Engineering Knowledge