Академический Документы
Профессиональный Документы
Культура Документы
: 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 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
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
Deviations (if any) from BoS approved syllabus and the topics planned:
NIL.
C
O
CO
I
Topic (s)
10
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
12
Design models
13
14
15
16
17
18
19
20
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
System Testing
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)
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
10
05
1
1
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
30
25
20
10
1
1
1
1
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
Recap / Introduction
10
20
10
10
30
05
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
Recap / Introduction
20
What Is Agility?
20
Agility Principles
20
20
05
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
10
20
20
05
Session Number:6
Session Outcome:
Time(min)
Topic
10
Introduction
25
15
Core Principles
BT
L
1
1
1
20
20
05
1
1
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
10
20
05
Observe
Construct a Sequence
diagram for Bank ATM in
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
20
20
10
05
2
1
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
10
20
05
Session Number:10
Session Outcome:
Topic
BT
L
1
10
Recap/Introduction
20
10
20
10
20
05
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
Active Learning Method: LTC (Library Scenario)
Conclusion & Summary
BT
L
1
1
1
2
1
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
20
05
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
15
05
Session Number:14
Session Outcome: Study of Class-based Components
Time(min)
10
BT
L
1
Topic
20
Component-Based Development
10
Talk Discussion
Chalk and Talk, PPTs Observe
Chalk and Talk, PPTs Observe
Chalk and Talk, PPTs Observe
Chalk and Talk, PPTs Observe
Discussion on state and
activity diagrams
05
Discussion
20
10
20
Recap/Introduction
What
Is
a
Component?,
Designing
Components
Component-Level Design for WebApps
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
Active Learning Method:
Conclusion & Summary
Session Number:16
Session Outcome: Study interface design steps
BT
L
1
1
1
2
2
1
Topic
Recap/Introduction
Interface Analysis
BT
L
1
1
10
20
20
05
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
30
15
15
05
Session Number:18
Session Outcome: Study Project Management techniques
Understand project management for achieving quality
Time(min)
Topic
10
Recap/Introduction
40
20
20
05
BT
L
1
2
2
2
1
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
20
20
20
05
Session Number:20
Session Outcome: study the elements of software quality assurance
Time(min)
Topic
BT
L
1
10
Recap/Introduction
20
20
20
standards
20
05
Observe
Construct an Activity
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
20
Strategic Issues
20
20
05
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
15
05
Session Number:23
Session Outcome: learn White box testing concepts
Understand control structures
10
Recap/Introduction
BT
L
1
20
White-Box Testing
40
Time(min)
Topic
20
05
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
Chalk and Talk, PPTs Observe
Chalk and Talk, PPTs Observe
Chalk and Talk, PPTs Observe
20
Black-Box Testing
20
Model-Based Testing
20
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
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
Signature
of
Course faculty