SRM UNIVERSITY

FACULTY OF ENGINEERING AND TECHNOLOGY

SCHOOL OF COMPUTING
DEPARTMENT OF SWE
COURSE PLAN
Course Code : SE1004
Course Title : Software Engineering
Semester : III
Course Time : July-Dec 2014

Day Hour Timing

1 5
1.30-2.20
2 - -
3 2 9.35-10.25
4 - -
5 1,6 ¤ 8.45-9.35,2.20-3.10

Location : S.R.M.E.C – University Block

Faculty Details

Office
Sec. Name Office hour Mail id

II
[Link] UNIVERSITY
h-B BLOCK
sec [Link] 12TH FLOOR Mon – Fri jothi.b@[Link]

Text Book (s):

1. Roger Pressman, “Software Engineering”, Mc Graw Hill, Fifth edition, 2000.

Reference Book (s):

• Ian Somerville, “Software Engineering”, Addison Wesley, Sixth Edition, 2002.

Fairley, “Software Engineering Concepts”, Mc Graw Hill

Web resources
• [Link]/
• [Link]
Objectives:

1. Understand Process methodologies and Project Management concepts

2. Understand Planning and Scheduling concepts and determine an appropriate
estimation model for a software development project
3. Understand Data modeling and come up with Data Flow diagrams and Entity
Relationship diagrams which leads to an effective design
4. Understand software testing methodologies and determine the test strategy for
a software development project, design test plans and test cases
5. Understand Maintenance Process and design Metrics Plan and interpret maintenance
metrics

Detailed Session Plan

UNIT I - INTRODUCTION (9 hours)

Software Engineering-Software Process- Generic process model-Prescriptiveprocess
model-specialized, unified process-Agile development-Agile Process-Extreme
Programming- Other agile Process models-Software engineeringKnowledge-core
Principles-Principles that guide each framework Activity.

SESSION TOPICS TO BE TIME REF TEACHING TESTING METHOD

NO COVERED (MIN) METHOD
1 Software 50 1 BB Discussion
Engineering-
Software Process
2 Generic process 50 1 BB Discussion ,Quiz
model- ,Objective type
Prescriptiveproces questions
s model
specialized
3 unified process. 50 1 BB Discussion
4 Agile development 50 1 BB Discussion
5 Agile Process- 50 1 BB Discussion
Extreme
Programming
6 Other agile 50 1 BB Discussion
Process models
7 Software 50 1 BB Discussion
engineeringKnowle
dge-core
Principles
8 Principles that 50 1 BB Discussion
guide each
framework Activity
UNIT II-REQUIREMENTS (9 hours)
Requirements Engineering-Establishing the Groundwork-Eliciting Requirements-Developing use
cases-Building the requirements model-Negotiating, validatingRequirements-Requirements
Analysis-Requirements Modeling Strategies.

SESSIO TOPICS TO BE TIME RE TEACHIN TESTING METHOD

N NO COVERED (MIN F G
) METHOD
9 Requirements 50 1 BB Discussion
Engineering
10 Establishing the 50 1 BB Quiz ,Objective type
Groundwork questions
11 50 1 BB Discusssion,Comparitiv
Eliciting Requirements e study
12 Developing use cases 50 1 BB Discussion
13 Building the 50 1 BB Discussion /
requirements model- Quiz,Assignment.
Negotiating
14 validatingRequirements 50 1 BB Quiz
-
15 Requirements Analysis- 50 1 BB Quiz,Objective type
Requirements Modeling questions
Strategies.

UNIT III-DESIGN (9 hours)

MODELING WITH UML: Modeling Concepts and Diagrams - Use Case Diagrams- Class
Diagrams - Interaction Diagrams - State chart Diagrams - ActivityDiagrams - Package Diagrams
- Component Diagrams – Deployment Diagrams -Diagram Organization- Diagram Extensions.
Design Process- Design concepts:Abstraction, Architecture, patterns, Separation of Concerns,
Modularity,Information Hiding, Functional Independence, Refinement, Aspects,
Refactoring,Object Oriented Design Concepts, Design Classes- Design Model:
Data,Architectural, Interface, Component, Deployment Level Design Elements .

SESSION TOPICS TO BE TIME REF TEACHING TESTING METHOD

NO COVERED (MIN) METHOD
16 Modeling Concepts 50 1 BB Discussion
and Diagrams - Use
Case Diagrams
17 Class Diagrams - 50 1 BB Objective type test,Quiz
Interaction Diagrams -
State chart Diagrams
18 ActivityDiagrams - 50 1 BB Discusssion,Comparitive
Package Diagrams - study
Component Diagrams
19 Deployment Diagrams 50 1 BB Discussion
-Diagram
Organization-
Diagram Extensions
20 Design Process- 50 1 BB Discusssion,Comparitive
Design concepts study
21 Abstraction, 50 1 BB Discusssion,Comparitive
Architecture, patterns, study
Separation of
Concerns
22 Modularity,Information 50 1 BB Discusssion,Comparitive
Hiding, Functional study
Independence
23 Refinement, Aspects, 50 1 BB Discussion
Refactoring,Object
Oriented Design
Concepts
24 Design Classes 50 1 BB Discusssion,Comparitive
study
25 Design Model: 50 1 BB Discusssion,Comparitive
Data,Architectural, study
Interface
26 Interface, Component 50 1 BB Discusssion,Comparitive
study
27 Deployment Level 50 1 BB Discussion
Design Elements

UNIT IV-SOFTWARE IMPLEMENTATION (9 hours)

Structured coding Techniques-Coding Styles-Standards and Guidelines-Documentation
Guidelines-Modern Programming Language Features: Typechecking-User defined data types-
Data Abstraction-Exception Handling-Concurrency Mechanism.

SESSIO TOPICS TO BE TIME RE TEACHING TESTING METHOD

N NO COVERED (MIN) F METHOD
28 Structured coding 50 1 BB Discussion
Techniques
29 Coding Styles 50 1 BB Quiz,Objective type
test
30 Standards and 50 1 BB Discusssion,Compa
Guidelines ritive study
31 Documentation Guidelines 50 1 BB Discussion
32 Modern Programming 50 1 BB Discusssion,Compa
Language Features ritive study
33 Typechecking-User 50 1 BB Discusssion,Compa
defined data types ritive study
34 Data Abstraction 50 1 BB Discusssion,Compa
ritive
study,Assgnment.
35 Exception Handling 50 1 BB Group Discussion
36 Concurrency Mechanism 50 1 BB Group Discussion

UNIT V-TESTING AND MAINTENANCE (9 hours)

TESTING: Software Quality- Software Quality Dilemma- Achieving SoftwareQuality- Testing:
Strategic Approach to software Testing- Strategic Issues-Testing: Strategies for Conventional
Software, Object oriented software, WebApps-Validating Testing- System Testing- Art of
Debugging.
MAINTENANCE: Software Maintenance-Software Supportability- Reengineering-Business
Process Reengineering- Software Reengineering- Reverse Engineering-Restructuring- Forward
Engineering- Economics of Reengineering

SESSION TOPICS TO BE TIME REF TEACHIN TESTING METHOD

NO COVERED (MIN) G
METHOD
37 Software Quality- 50 1 BB Discusssion,Comparitive
Software Quality study.
Dilemma
38 Achieving 50 1 BB Discusssion,Comparitive
SoftwareQuality study ,Assignment
39 Testing: Strategic 50 1 BB Discusssion,Comparitive
Approach to software study.
Testing
40 Strategic Issues- 50 1 BB Discusssion,Comparitive
Testing: Strategies study, Assignment
for Conventional
Software
41 Object oriented 50 1 BB Discusssion,Comparitive
software, study.
WebApps
42 WebApps- 50 1 BB Discusssion,Comparitive
Validating Testing- study.
System Testing
43 Art of Debugging 50 1 BB Discusssion,Comparitive
study.
44 Software 1 BB Discusssion,Comparitive
Maintenance- study, Assignment
Software
Supportability
45 Reengineering- 50 1 BB Discusssion,Comparitive
Business Process study.
Reengineering
46 Software 50 1 BB Discusssion,Comparitive
Reengineering- study.
Reverse
Engineering
47 Restructuring- 50 1 BB Discusssion,Comparitive
Forward study.
Engineering-
Economics of
Reengineering

48 Economics of 50 1 BB Discusssion,Comparitive
Reengineering study, Assignment
BB – Black Board
PP – Power Point
Staff In Charge Signature of the HOD

Assessment Details
Attendance : 5 Marks
Cycle Test – I : 10 Marks
Cycle Test – II : 10 Marks
Surprise Test – I : 5 Marks
Surprise Test - II : 5 Marks
Model Exam : 15 Marks

Test Schedule

[Link]. DATE TEST TOPICS DURATION

1
Cycle Test - I Unit I & II 2 periods
AUG
2 SEP Cycle Test - II Unit III & IV 2 periods
3 NOV Model Exam All 5 units 3 Hrs

Outcomes
Students who have successfully completed this course will have full understanding
of the following concepts

Course outcome Program outcome

To learn
To learn software quality factors An ability to understand components of
software quality assurance.
About common software testing strategies.
To have enough knowledge in
About project process control and software implementation in testing and assuring
software quality maintenance
metrics.
To have knowledge about software
About standards and certifications. quality costs.
To understand SQA standards and
software process assesments