Vous êtes sur la page 1sur 16

K L Deemed to be University

Department of Computer Science & Engineering


Course Handout Template for Y18 Admitted Batch
A.Y.2019-20, Odd Semester

Course Title : Software Engineering


Course Code : 18CS2103R
L-T-P-S Structure : 2-1-0-0
Credits :3
Pre-requisite : NIL
Course Coordinator : Mr. Venkata Naresh Mandhala
Dr. V.Chandra Prakash
Dr. K. Subrahmanyam
Dr. Y.Prasanth
Dr. K.V.Durga Kiran
Dr. B. Chaitanya Krishna
Mr. P.S.V.S.Sridhar
Dr. Md.Moulana
Team of Instructors :
Dr. Pragnyaban Mishra
Mr. P.V.Vara Prasad
Mr. N.Rajesh
Mr. Ch.M.H. Sai Baba
Mr. J. Satish Babu
Mr. T. Praveen (OCC)
Mr. V.Deepak
Teaching Associates : NIL

Course Objective: 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 including the design of
interface, improve quality of software through 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 period 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 covers various methods and models
to train the student to learn the process of gathering user requirements, analyzing them, and design
models based on the analysis, emphasizing system constraints incorporating Quality assurance. The
students exposed to code and test the software with quality focus that can be delivered to the user so
that he can operate and maintain software.

1
COURSE OUTCOMES (COs):
Blooms
Course Outcome Taxonomy
CO No PO/PSO
(CO) Level
(BTL)
CO1 Understand the software development life cycle PO1, PO2 2
and associated process models and Reverse
Engineering.
CO2 Illustrate Requirement modelling and Agile and PO2, PO3 3
Extreme Programming.
CO3 Examine Agile Models such as Scrum, kanban PO1, PO2 4
and SAFe Methodology.
CO4 Categorize various testing strategies, Test PO1, PO2 4
Driven Development and
CMMI, Six Sigma techniques

COURSE OUTCOME INDICATORS (COIs):

Course
Highest COI-1 COI-2 COI-3 COI-4
Outcome
BTL (BTL1) (BTL2) (BTL3) (BTL4)
No.
CO 1 2 1 2

CO 2 3 1 2 3

CO 3 4 1 2 3 4

CO 4 4 1 2 3 4

PROGRAM OUTCOMES & PROGRAM SPECIFIC OUTCOMES (POs/PSOs)

PO1: Engineering Knowledge An Ability To Apply Knowledge Of Mathematics, Science,


Engineering Fundamentals And An Engineering Specialization For The Solution Of Complex
Engineering Problems.
PO2: Problem Analysis An Ability To Identify, Formulate, Research Literature, Analyze
Complex Engineering Problems In Mechanical Engineering Using First Principles Of Mathematics,
Natural Sciences And Engineering Sciences
PO3: Design/ Development Of Solutions An Ability To Design Solutions For Complex
Engineering Problems And System Component Or Processes That Meet The Specified Needs
Considering Public Health & Safety And Cultural, Societal & Environment

SYLLABUS: Software and Software Engineering: Nature of software, software application domains,
unique nature of web applications, software engineering, software process, software engineering
practice, software myths. Process Models: Generic process model, prescriptive process models,
specialized process models, unified process, personal and team process models, product and process,
Reverse Engineering: Reverse Engineering to Understand Data, Reverse Engineering to Understand
Processing, Reverse Engineering User Interfaces. Understanding Requirements: Identify stakeholders,
recognizing multiple viewpoints, eliciting requirements, Building requirement model, negotiating
requirements, validating requirements, SRS Vs User Stories. Agile Modeling, Extreme Programming,
Scrum, Kanban, SAFe Methodology. Test Driven Development: Basics, A strategic approach to
software testing, strategic issues, test strategies for conventional software, Black-Box and White-Box
testing, validation testing, system testing. Performing TDD Test, TDD Vs Traditional Testing,
Acceptance TDD and Developer TDD, Scaling TDD via Agile Model Driven Development (AMDD),
Test Driven Development (TDD) Vs. Agile Model Driven Development (AMDD), Examples of TDD,

2
and Benefits of TDD. JUnit. The CMMI process improvement framework: CMMI, Levels, Staged
CMMI model, Continuous CMMI model, Six Sigma Model.

TEXT BOOKS:

1. Roger S.Pressman, “Software Engineering – A Practitioner’s Approach” 7th Edition, Mc


Graw Hill,(2014).
2. Ian Sommerville, “Software Engineering”, Tenth Edition, Pearson Education, (2015).
3. Agile and Iterative Development: A Manager's Guide, Craig Larman, Addison-Wesley

WEB REFERNCES/MOOCS:
1. https://www.digite.com/kanban/what-is-kanban/
2. http://www.scaledagileframework.com
3. https://www.guru99.com/test-driven-development.html
4. https://junit.org/junit5/

COURSE DELIVERY PLAN:


Teaching-
Sess. Book No[CH Web Evaluation
CO COI Topic (s) Learning
No. No][Page No] Resources Components
Methods
Marker and https://npt
Software and Software Engineering: 1, Nature T BOOK [1], Talk Test-1, Sem
el.ac.in/cou
1 1 of software 3, Software application domains 7, CH1.1,1.2, End Exam
rses/10610
Unique nature of web applications 10, Page no 1-11
1061/2
PPT, https://npt
Software engineering 12, software process 14, T BOOK [1], Marker and Test-1, Sem
el.ac.in/cou
2 2 Software engineering practice 17, Software CH1.3-1.6, Talk End Exam
rses/10610
myths 21. Page no 12-23
1061/2
PPT, https://ww
T BOOK [1], Marker and w.youtube. Test-1, Sem
Process Models 30: Generic process model 31, Talk
3 1 CH 2.1-2.3, com/watch End Exam
prescriptive process models 38,
Page no 30-49 ?v=1UD1P-
fDCiI
PPT, https://ww
1 T BOOK [1], Marker and w.youtube. Test-1, Sem
Specialized process models 50, unified process Talk
4 2 CH 2.4,2.5, com/watch End Exam
53,
Page no 50-55 ?v=1UD1P-
fDCiI
PPT, https://ww
T BOOK [1], Marker and w.youtube. Test-1, Sem
Personal and team process models 56, product Talk
5 2 CH 2.6,2.8, com/watch End Exam
and process 60.
Page no 56-61 ?v=1UD1P-
fDCiI
PPT, https://ww
Reverse Engineering 772: Reverse Engineering Marker and w.youtube.
T BOOK [1], Talk Test-1, Sem
to Understand Data 773, Reverse Engineering com/watch
6 2 CH 29.6, Page End Exam
to Understand Processing 774, Reverse ?v=3XQvax
no 772-776
Engineering User Interfaces 775. YEI48&pbjr
eload=10
PPT, https://ww
T BOOK [1], Marker and
Understanding Requirements 119: Identify w.youtube. Test-1, Sem
CH 5.1-5.3, Talk
7 2 1 stakeholders 125, recognizing multiple com/watch End Exam
Page no 120-
viewpoints 126, eliciting requirements 128. ?v=v5gMLC
133
ICpKE&pbjr

3
Teaching-
Sess. Book No[CH Web Evaluation
CO COI Topic (s) Learning
No. No][Page No] Resources Components
Methods
eload=10
PPT, https://ww
Building requirement model 138, negotiating T BOOK [1], Marker and w.youtube.
Talk Test-1, Sem
requirements 142, validating requirements 144. CH 5.5-5.7, com/watch
8 2 End Exam
SRS Vs User Stories. Page no 138- ?v=iWDuY6
144 TB3HE&pbj
reload=10
PPT, https://ww
Agile: Agile Development 25, Classification of Marker and w.youtube.
Methods 26, The Agile Manifesto and T BOOK [3], Talk Test-1, Sem
com/watch
9 2 Principles 27, Agile Project Management 29, CH 3, Page no End Exam
?v=NpCEjtK
Embrace Communication and Feedback 30, 25-30
Aa20&pbjr
eload=10
PPT, https://ww
Marker and w.youtube.
Simple Practices and Project Tools 31, Talk
T BOOK [3], com/watch Test-1, Sem
Empirical vs. Defined & Prescriptive
10 2 CH 3, Page no ?v=HY1m- End Exam
Process32, Principle-Based versus Rule-Based
31-38 WxNCk8&p
33, Agile Hype? 34, Specific Agile Methods 35
bjreload=1
0
PPT, https://ww
Marker and w.youtube.
Extreme Programming: Method Overview 138, T BOOK [3], Talk Test-1, Sem
com/watch
11 3 Lifecycle 142, Workproducts, Roles, and CH 8, Page no End Exam
?v=I6CbU4
Practices 144, 138-154
g5Ed0&pbj
reload=10
PPT, https://ww
Marker and w.youtube.
T BOOK [3], Talk Test-1, Sem
Adoption Strategies 165, Fact versus Fantasy com/watch
12 3 CH 8, Page no End Exam
167,Strengths versus "Other 168, History 170 ?v=LkhLZ7_
165-170
KZ5w&pbjr
eload=10
PPT, https://ww
Scrum: Method Overview 110, Lifecycle 113, Marker and w.youtube.
T BOOK [3], Talk
Workproducts, Roles, and Practices 114, com/watch Test-2, Sem
13 1 CH 7, Page no
Values 126, Common Mistakes and ?v=9TycLR0 End Exam
109-129
Misunderstandings 127. TqFA&pbjr
eload=10
PPT, https://ww
Marker and w.youtube.
Sample Projects 130, Process Mixtures 131, T BOOK [3], Talk com/watch Test-2, Sem
14 2 Adoption Strategies 132, Fact versus Fantasy CH 7, Page no
?v=2Q5E0Q End Exam
133, Strengths versus "Otter" 134, History 135. 130-135
3 h774M&pb
jreload=10
PPT, https://ww
Marker and w.digite.co
Kanban: Origin, Foundational Principles, 6 Web Talk Test-2, Sem
15 2 m/kanban/
Core Practices, WIP Limits, Reference [1] End Exam
what-is-
kanban/
PPT, https://ww
Web
Its usage in IT & Software, Kanban in Lean/ Marker and w.digite.co Test-2, Sem
16 3 Reference [1] Talk
Agile development. m/kanban/ End Exam
what-is-

4
Teaching-
Sess. Book No[CH Web Evaluation
CO COI Topic (s) Learning
No. No][Page No] Resources Components
Methods
kanban/
PPT, http://ww
SAFe Methodology: Definition, Foundations of Web
Marker and w.scaledagi Test-2, Sem
17 4 Scaled Agile Framework, Scaled Agile Reference [2] Talk leframewor End Exam
Framework usage,
k.com
PPT, http://ww
Differences with other agile practices, Different Web Marker and w.scaledagi Test-2, Sem
18 4 Talk
Levels in SAFe. Reference [2] leframewor End Exam
k.com
PPT, https://ww
T BOOK [1], Marker and w.software
Software testing 449: A strategic approach to Talk
CH17.1-17.3 testingmat Test-2, Sem
19 1 software testing 450, Strategic issues 455.
Page no 450- erial.com/s End Exam
test strategies for conventional software 456,
464 oftware-
testing/
T BOOK [1], PPT, http://ww
CH17.7,17.7,1 Marker and w.professio
Black-Box 495 and White-Box testing 485, Talk Test-2, Sem
20 2 8.3,18.6 Page nalqa.com/
Validation testing 467, system testing 470, End Exam
no 467-472, black-box-
485, 495-501 testing
PPT, https://ww
Performing TDD Test, TDD Vs Traditional Marker and w.guru99.c
Testing, Acceptance TDD and Developer TDD, Web Talk om/test- Test-2, Sem
21 3
Scaling TDD via Agile Model Driven Reference [3] driven- End Exam
4 Development (AMDD), developme
nt.html
PPT, https://ww
Marker and w.guru99.c
Test Driven Development (TDD) Vs. Agile Talk
Web om/test- Test-2, Sem
22 3 Model Driven Development (AMDD),
Reference [3] driven- End Exam
Examples of TDD, and Benefits of TDD.
developme
nt.html
PPT, https://juni
Web Marker and Test-2, Sem
23 4 JUnit. t.org/junit5
Reference [4] Talk End Exam
/
T BOOK [1], PPT, https://slid
T BOOK [2], Marker and eplayer.co Test-2, Sem
24 4 The CMMI 797. Six Sigma Model Talk
CH30.3, Page m/slide/48 End Exam
no 787-790 50802/

5
SESSION WISE TEACHING – LEARNING PLAN
SESSION NUMBER: 01
Session Outcome: 1. Software and Software Engineering and Nature of software
2. Software application domains
3. Unique nature of web applications.
Time Teaching- Active Learning
Topic BTL
(min) Learning Methods Methods
5 Attendance

Overview of the Course, Introduction to Software


10 engineering, Nature of S/w, application domains. 1 Talk – Discussion

Overview of the Course Outcomes (Handout) Brain Storming


10 1 PPT’s – Observe
Session
10 Conclusion Talk – Discussion
10 Summary Discussion
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

SESSION NUMBER: 02
Session Outcome: 1. Software engineering and software process.
2. Software engineering practice.
3. Software myths.
Time Teaching- Active Learning
Topic BTL
(min) Learning Methods Methods
5 Attendance

10 Software engineering and software process 1 Talk – Discussion


Discussion on Software engineering practice, Software Brain Storming
10 myths. 2 PPT’s – Observe Session

10 Conclusion Talk – Discussion


10 Summary Discussion
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

SESSION NUMBER: 03
Session Outcome: 1. Various Process Models
2. Generic process models
3. Prescriptive process models
Time Teaching- Active Learning
Topic BTL
(min) Learning Methods Methods
5 Attendance

10 Various Process Models and Generic process models 1 Talk – Discussion


Discussion on Prescriptive process models . Brain Storming
10 1 PPT’s – Observe
Session
10 Conclusion Talk – Discussion
10 Summary Discussion
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

6
SESSION NUMBER: 04
Session Outcome: 1. Specialized process models
2. Unified process model
Time Teaching- Active Learning
Topic BTL
(min) Learning Methods Methods
5 Attendance

10 Discussion on Specialized process models 2 Talk – Discussion


Brain Storming
10 Discussion on Unified process model. 2 PPT’s – Observe
Session
10 Conclusion Talk – Discussion
10 Summary Discussion
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

SESSION NUMBER: 05
Session Outcome: 1. Personal and team process models
2. Product and process
Time Teaching- Active Learning
Topic BTL
(min) Learning Methods Methods
5 Attendance

10 Discussion on Personal and team process models 2 Talk – Discussion


Brain Storming
10 Discussion on Unified process model. 2 PPT’s – Observe
Session
10 Conclusion Talk – Discussion
10 Summary Discussion
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

SESSION NUMBER: 06
Session Outcome: 1. Reverse Engineering to Understand Data
2. Reverse Engineering to Understand Processing
3. Reverse Engineering User Interfaces
Time Teaching- Active Learning
Topic BTL
(min) Learning Methods Methods
5 Attendance

Discussion on Reverse Engineering to Understand Data


10 2 Talk – Discussion
and processing.
Brain Storming
10 Discussion on Reverse Engineering User Interfaces. 2 PPT’s – Observe
Session
10 Conclusion Talk – Discussion
10 Summary Discussion
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

SESSION NUMBER: 07
Session Outcome: 1.Understanding the basic need of software Requirements
2. Describe the software requirements and types
Time Teaching- Active
Topic BTL
(min) Learning Methods LearningMethods
10 Recap of the previous class Discussion
10 What is software requirements 1 Marker &Talk, PPT
10 Types of software requirements 1 Marker &Talk, PPT Seminar
10 Identify stakeholders & eliciting requirements 1 Marker &Talk, PPT
5 Summary & Conclusions Discussion
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

7
SESSION NUMBER: 08
Session Outcome: 1. Describe requirement model
2. Explaining the importance and use SRS
Time Teaching- Active
Topic BTL
(min) Learning Methods LearningMethods
10 Recap of the previous class - Discussion
20 Building requirement model 2 Marker &Talk, PPT
10 Types of requirements, SRS 1 Marker &Talk, PPT Brain storming
5 Summary & Conclusions - Discussion
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

SESSION NUMBER: 09
Session Outcome: 1. Explaining and introduction to Agile Development
2. Describe procedure and methods of Agile Development project
Time Teaching- Active
Topic BTL
(min) Learning Methods LearningMethods
10 Recap of the previous class - Discussion
10 Introduction to Agile Development 1 Marker &Talk, PPT
10 The Agile Manifesto and Principles 2 Marker &Talk, PPT
Marker &Talk, PPT Collaborative Virtual
10 Agile Project Management 2
Classrooms
5 Summary & Conclusions - Discussion
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

SESSION NUMBER: 10
Session Outcome: 1. Explain the difference between Empirical vs. Defined
2. Explain the difference between Principle-Based versus Rule-Based
Time Teaching- Active
Topic BTL
(min) Learning Methods LearningMethods
10 Recap of the previous class - Discussion
10 Agile Project Management with example 1 Marker &Talk, PPT
10 Empirical vs. Defined & Prescriptive Process 2 Marker &Talk, PPT
10 Principle-Based versus Rule-Based 2 Marker &Talk, PPT Discussion
5 Summary & Conclusions - Discussion
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

SESSION NUMBER: 11
Session Outcome: 1. Give an introduction to Extreme Programming
2. Explain the types and methods of Adoption Strategies
Time Teaching-Learning Active
Topic BTL
(min) Methods LearningMethods
10 Recap of the previous class - Discussion
Marker &Talk, PPT Learning by
10 Introduction to Extreme Programming 1
Teaching
10 Work products, Roles, and Practices 3 Marker &Talk, PPT
10 Introduction to Adoption Strategies 1 Marker &Talk, PPT
5 Summary & Conclusions - Discussion
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

8
SESSION NUMBER: 12
Session Outcome: 1. Explain in detail about Adoption Strategies
2. Explain the difference between Fact versus Fantasy
Time Teaching-Learning Active
Topic BTL
(min) Methods LearningMethods
10 Recap of the previous class - Discussion
10 Adoption Strategies process with example 2 Marker &Talk, PPT
10 Fact versus Fantasy 3 Marker &Talk, PPT Discussion
10 Strengths versus Other and history 3 Marker &Talk, PPT
5 Summary & Conclusions - Discussion
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

SESSION NUMBER: 13
Session Outcome: 1. Basic understanding of SCRUM
2. What is Life Cycle and Values
3. Reasons for Misunderstandings
Time Teaching- Active
Topic BTL
(min) Learning Methods LearningMethods
SCRUM: Method Overview- Life Cycle and Key
10 1 PPT
Practices
10 Work Products, Roles and Practices 1 PPT
10 Values 1 PPT
10 Common Mistakes and Misunderstandings 1 PPT
5 Summary of SCRUM 1 PPT
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

SESSION NUMBER: 14
Session Outcome: 1. Basic understanding of SCRUM History and Adoption Strategies
2. Compare Facts Vs Fantasy and Strength Vs Other
Time Teaching- Active
Topic BTL
(min) Learning Methods LearningMethods
10 Sample Projects, Process Mixtures 2 PPT
Learning by
10 Adoption Strategies 2 PPT
Teaching
10 Fact versus Fantasy, Strengths versus "Other" 2 PPT
10 History 2 PPT
5 Summary 2 PPT
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

SESSION NUMBER: 15
Session Outcome: 1. Basic understanding o Kanban
2. Understand Core Practices and Principles
Time Teaching- Active
Topic BTL
(min) Learning Methods LearningMethods
10 Kanban: Origin 2 PPT
10 Foundational Principles 2 PPT
10 Core Practices 2 PPT Discussion
10 WIP Limits 2 PPT
5 Summary 2 PPT
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

9
SESSION NUMBER: 16
Session Outcome: 1. Kanban in Lean/ Agile development models student can understand
2. With WIP the bottle neck problem is identified and resolving with above methods.
Time Teaching- Active
Topic BTL
(min) Learning Methods LearningMethods
10 WIP usage in IT & Software 3 Chalk and talk/ppt
Chalk and talk/ppt
10 Kanban method 3
Chalk and talk/ppt
10 Agile method 3
Chalk and talk/ppt
10 Developments of the methods 3
Chalk and talk/ppt
5 Summary of methods principles 3
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

SESSION NUMBER: 17
Session Outcome: 1. Why we have to SAFe
2. in which case SAFe is applicable
3.Foundations of Scaled Agile Frame work
Time Teaching- Active
Topic BTL
(min) Learning Methods LearningMethods
SAFe Methodology: Definition, how it is different
10 2 PPT
from Agile framework
10 Principles of SAFe 3 PPT
10 Foundations of Scaled Agile Framework 3 PPT
10 Scaled Agile Framework usage 4 PPT
5 Summary of SAFe 2 PPT
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

SESSION NUMBER: 18
Session Outcome: 1. Student is able to find out the Differences with other agile practices, Different Levels
in SAFe.
Time Teaching- Active
Topic BTL
(min) Learning Methods LearningMethods
10 Agile practices, principles 3 Marker &Talk, PPT
20 Different levels in SAFe 3 Marker &Talk, PPT
Brain Storming
10 Differences of SAFe with other methods 4 Marker &Talk, PPT
Session
5 Summary of SAFe 3 Marker &Talk, PPT
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

SESSION NUMBER: 19
Session Outcome: 1. Describe Software testing
2. Identify strategic approach to software testing
Time Teaching- Active
Topic BTL
(min) Learning Methods LearningMethods
10 Recap of the previous class Discussion
5 Software testing 1 Marker &Talk, PPT
10 A strategic approach to software testing, 1 Marker &Talk, PPT Seminar
10 Strategic issues 1 Marker &Talk, PPT
5 test strategies for conventional software 1 Marker &Talk, PPT
5 Summary & Conclusions
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

10
SESSION NUMBER: 20
Session Outcome: 1. Compare black and white box testing
2. Demonstrate validation and system testing
Time Teaching- Active
Topic BTL
(min) Learning Methods LearningMethods
10 Recap of the previous class - Discussion
10 Black-Box and White-Box testing 2 Marker &Talk, PPT
10 Validation testing 2 Marker & talk,PPT Brain storming
10 system testing 2 Marker & talk,PPT
5 Summary & Conclusions - Discussion
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

SESSION NUMBER: 21
Session Outcome: 1. Organize TDD test
2. Summerize TDD via Model driven development
Time Teaching-Learning Active
Topic BTL
(min) Methods LearningMethods
10 Recap of the previous class - Discussion
5 Performing TDD Test 2 Marker &Talk, PPT
Collaborative
10 TDD Vs Traditional Testing 2 Marker & talk,PPT
Virtual Classrooms
10 Acceptance TDD and Developer TDD Scaling 3 Marker & talk,PPT
5 TDD via Agile Model Driven Development (AMDD) 2 Marker & talk,PPT
5 Summary & Conclusions - Discussion
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

SESSION NUMBER: 22
Session Outcome: 1. Compare Test Driven Development (TDD) Vs. Agile Model Driven Development
(AMDD)
2. Apply TDD technique on examples
Time Teaching-Learning Active
Topic BTL
(min) Methods LearningMethods
10 Recap of the previous class - Discussion
Test Driven Development (TDD) Vs. Agile Model
10 3 Marker &Talk, PPT
Driven Development (AMDD)
10 Examples of TDD 3 Marker & talk,PPT Discussion
10 and Benefits of TDD 3 Marker & talk,PPT
5 Summary & Conclusions - Discussion
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

SESSION NUMBER: 23
Session Outcome: 1. Apply JUnit on examples
Time Teaching-Learning Active
Topic BTL
(min) Methods LearningMethods
10 Recap of the previous class - Discussion
Interactive Example
30 JUnit 4 Marker &Talk, PPT
with practicles
5 Summary & Conclusions - Discussion
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

11
SESSION NUMBER: 24
Session Outcome: 1. Analyze CMMI
2. Examine Six sigma model
Time Teaching-Learning Active
Topic BTL
(min) Methods LearningMethods
10 Recap of the previous class - Discussion

15 The CMMI 4 Marker &Talk, PPT

15 Six Sigma Model 4 Marker & talk,PPT Discussion


5 Summary & Conclusions - Discussion
45 minutes Total Contact Session + 5 minutes for Attendance and Transition activities = 50 Minutes

LIST OF TUTORIALS:
Tutorial CO-
Topics
session no Mapping
1. Describe the importance of software Engineering? CO1
2. Explain the principles which play a major role in development of
1 software.
3. What is SRS? SRS for Library Management
1. What are the benefits of metrics in software engineering?
2 2. Use case diagram for Library Management System
CO1
1. Explain the various types of models which used in software
3 Engineering. CO1
2. Data Flow Diagram for Payroll Process
1. What is the process of implementation of a software?
4 2. Explain the term, software maintenance. CO1
3. Class diagram for Admission Process
1. Discuss the principles of Agility.
5 2. Discuss the activities involved in Extreme Programming. CO2
3. Activity diagram for online railway reservation booking system
1. Difference between the functional and non-functional requirements
6 2. Sequence Diagram for ATM Transaction
CO2
1. Outline Scrum, Kanban
7 2. State Chart Diagram for Bank ATM
CO3
1. Outline SAFe Methodology
8 2. Flow chart using Raptor tool for given program and structured program CO3
principles
1. List the Testing Types, Explain Test Driven Development
9 2. Cyclomatic Complexity CO4
3. Validation testing example
1. What is Six SIgma
10 2. Elaborate CMMI CO4
3. McCall’s Quality Factors --example

12
WEEKLY HOMEWORK ASSIGNMENTS/ PROBLEM SETS/OPEN ENDEDED PROBLEM-
SOLVING EXERCISES etc.
Week Assignment Topic Details CO
2 A01 Software Process Model CO1
4 A02 Reverse Engineering and CO1 & CO2
Agile Modleing
6 A03 Extreme Programming CO2

8 A04 Scrum and Kanban CO3

10 A05 Safe Methodology and CO3 & CO4


Testing Strategies
12 A06 TDD, CMM and Six Sigma CO4

COURSE TIME TABLE


Course Conduct
Theory Lecture 19 Sections | 72 Students each | Class 2 Lectures per week
Room | Course Coordinator
Tutorial 19 Sections | 72 Students each | Class 1 per week
Room | Course Coordinator
Practical Sections | 72 Students each | Batches | 1 P per week | each 2 hrs.
Instructors | 72 Computers 70 minutes Experiment |
30 minutes Evaluation for 25 students per instructor

Hour 1 2 3 4 5 6 7 8 9
Day Component 9:00-9:50 9:50-10:40 11:00-11:50 11:50-12:40 12:40-1:30 1:30-2:20 2:20-3:10 3:20-4:10 4:10-5:00
Theory S1, S11
Mon Lab S4, S13, S23
Theory
Tue Lab
Theory
Wed Lab
Theory
Thu Lab
Theory
Fri Lab
Theory
Sat Lab

REMEDIAL CLASSES:
Supplement course handout, which may perhaps include special lectures and discussions that would be
planned, and schedule notified accordingly.

SELF-LEARNING:
Assignments to promote self-learning, survey of contents from multiple sources.

S.No Topics CO ALM References/MOOCS

13
EVALUATION PLAN: Regular

Evaluation Evaluation Assessment Duration


Weightage/Marks CO1 CO2 CO3 CO4 CO5
Type Component Dates (Hours)

Blooms Taxonomy Level


Weightage 12.5
In-Sem
Max Test 1 Dates 2
Exam-I 50M 25 25
Marks
In-Semester
Weightage 12.5
Summative In-Sem
Max Test 2 Dates 2
Evaluation Exam -II 50M 25 25
Total =28 % Marks
Weightage 3
Surprise
Max 20 Min
Quiz 40M 10 10 10 10
Marks
Weightage 10
ALMs Max Continuous Evaluation
100M 25 25 25 25
Marks
Formative Home Weightage 5+2
Evaluation Assignment Max Continuous Evaluation
Total =22 % + Textbook 40M 10 10 10 10
Marks
Weightage 5
Attendance Max Continuous evaluation
5M
Marks
End- Weightage 50
Semester End Sem
Semester
Summative Max Exam 3 hrs
End Exam 100M 25 25 25 25
Evaluation Marks Dates
Total =50 %

ATTENDANCE POLICY
Every student is expected to be responsible for regularity of his/her attendance in class rooms and laboratories,
to appear in scheduled tests and examinations and fulfill all other tasks assigned to him/her in every course. For
Promotion, a Minimum of 50% of internal marks must be obtained. In every course, student has to maintain a
minimum of 85% attendance to be eligible for appearing in Semester end examination of the course, for cases of
medical issues and other unavoidable circumstances the students will be condoned if their attendance is between
75% to 85% in every course, subjected to submission of medical certificates, medical case file and other needful
documental proof to the concerned departments.

DETENTION POLICY
In any course, a student has to maintain a minimum of 85% attendance and must secure a minimum of 50%
marks in In-Semester Examinations to be eligible for appearing to the Semester End Examination, failing to
fulfill these conditions will deem such student to have been detained in that course.

PLAGIARISM POLICY
Use of unfair means in any of the evaluation components will be dealt with strictly, and the case will be
reported to the examination committee.

COURSE TEAM MEMBERS, CHAMBER CONSULTATION HOURS AND CHAMBER


VENUE DETAILS:
Each instructor will specify his / her chamber consultation hours during which the student can contact him / her in
his / her chamber for consultation.

14
Chamber
Chamber Chamber
Consultation Signature of
S.No. Name of Faculty Consultation Consultation
Timings for Course faculty
Day (s) Room No:
each day
Dr. V.CHANDRA
1 PRAKASH L601

Dr. K. SUBRAHMANYAM C513


2
Dr. Y.PRASANTH C312
3
Dr. K.V.DURGA KIRAN C315
4
Dr. B. CHAITANYA
5 KRISHNA C104

6 Mr. P.S.V.S.SRIDHAR C112

7 Dr. MD.MOULANA C305

Dr. PRAGNYABAN
8 MISHRA C305

9 Mr. P.V.VARA PRASAD C601

10 Mr .N.RAJESH C424

11 Mr. M.VENKATA NARESH C105

12 Mr. CH. SAI BABA C305

13 Mr. J. SATISH BABU C221A

14 Mr. T. PRAVEEN C321A

15 Mr. V.DEEPAK C321A

GENERAL INSTRUCTIONS
Students should come prepared for classes and carry the text book(s) or material(s) as prescribed by the Course
Faculty to the class.

NOTICES
Most of the notices are available on the LMS platform.
All notices will be communicated through the institution email.
All notices concerning the course will be displayed on the respective Notice Boards.

15
Signature of COURSE COORDINATOR:

Signature of Department Prof.Incharge Academics & Vetting Team Member:

HEAD OF DEPARTMENT:

Approval from: DEAN-ACADEMICS


(Sign with Office Seal)

16

Vous aimerez peut-être aussi