New Horizon College of Engineering, Bengaluru

EW HORIZONDepartmnent: MCA COLLEGE OF ENGINEERING AOOOs Coiiege ermanenty AMlated to VTU, Approved b

ACCFected by NAAC with 'A' Grade, Accredited by NBA

Academic Semester: February 2020 - May 2020

Course Code: Semester: Il Section: A Course: Software Engineering 18MCA25

Contact Hours Course Instructor: Dr. K.G. Madhwaraj # of credits: 03 /week: 04 CIE: 50 (25+25) SEE: 50 (25+25) Exam Hours: 03

Content delivery: Chalk and Talk, Power Point Presentation, Quiz and Assignments ncsn

www.mas

COURSE SYLLABUS:

Module Contents of Module Hrs CO's No

wwwww

INTRODUCTION

Software Engineering paradig - Waterfall Life cycle model -

18MCA25.1 Spiral Model - Prototype Model - fourth Generation Techniques

18MCA25.6 Planning- Software Project Scheduling, Risk analysis and

management Requirements and Specification Case Study for Project Plan and SRS.

wwwwww.w*****w**ww**************** SOFTWARE DESIGN

Abstraction Modularity Software Architecture Cohesion

Coupling-Various Design Concepts and notations - Real time and

18MCA25.2 Distributed System Design Documentation Dataflow Oriented design Jackson System development Designing for reuse -

9 2 18MCA25.6

Programming standards- Case Study for Design of any

Application Project.

SOFTWARE TESTING AND MAINTENANCE

Software Testing Fundamentals Software testing strategies

Black Box Testing - White Box Testing-- System Testing 0bject

State based Testing Testing Tools Test 18MCA25.3 Orientation Testing 3

18MCA25.6 Case Management Software Maintenance Organization

Case Study for Maintenance Report - Types of Maintenance

Testing Techniques.

SOFTWARE METRICS

Scope - Classification of metrics Measuring Process and Product 18MCA25.4

4 attributes - Direct and Indirect measures - Cost Estimation 9 18MCA25.6

ReliabilitySoftware Quality Assurance - Standards Case Study

for COCOMO model.

SCM & WEB ENGINEERING

Need for SCM Version Control - SCM process

Configuration Items Taxonomy CASE repository Features

Software 18MCA25.5 5 9

18MCA25.6

Web Engineering, SCM Case Study.

COURSE OUTCOMES: At the end of the Course, the Student will be able to: 18MCAZ5.1 Provide an insight into the processes of software development

18MCA25.2 Understand and practice the various fields such as analysis, design, development,

testing of Software Engineering

18MCA25.3 Develop skills to construct software of high quality with high reliability

18MCA25.4 Apply metrics and testing techniques to evaluate the software

18MCA25.5 Understand the Software Configuration Management

18MCA25.6 Understand the Software Maintenance Strategies and CASE Tools

Mapping of Course Outcomes to Program Outcomes:

P01 PO2 P03 P04 PO5 PO6 P07 P08 PO09 PO10 P011 PSO01 PS

1 CO1 3 2 2 3 2

CO2 2 3 2 1 3 1 3 2

3 1 3 2 C03 2 2 3

3 3 2 C04 2 2 3 2

CO5 3 1 2

3 3 CO6 2

Correlation levels: 1-Slight (Low) 2-Moderate (Medium) 3-Substantial (High)

Gap in the syllabus The current syllabus covers most of the basic software

engineering concepts that is very much needed for the students

to get industry-ready.

Topics to be covered 1. Introduction to the Agile Methodology

beyond syllabus 2. How agile models are used in the industry today

Assessment Methodologies:

Sl.1 No. Description Type

Student Assignment Direct

Internal assessment Direct

wwwo University exam Direct

4. Student feedback Indirect

Alumni feedback Indirect

6. Employers feedback Indirect

LESSON PLAN

Course Planned Faculty Sign

Lecture Module RBT Actual Remarks Topics Outcome

# # Levels Date Date Mapping

Introduction to Software 1 10-02-20 6-

Engineering Paradigms ShAad, Waterfall Model and the

11-02-20D Spiral Model

Prototype Model 12-02-20|--2 3

Fourth Generation 14-02-20 1-3- 4

Techniques

18MCA25.1 Software Planning L1, L2 17-02-20-2

18MCA25.2

Software Project

Scheduling 6 18-02-20

Risk Analysis and 19-02-20 0 Management

Requirements and

Specification 24-02-209-2 8

Case Study of Project Plan

and SRS 25-02-20

Software Design Concepts: Abstraction

and Modularity

26-02-20 6 9-2 10

Software Architecture, 11 Cohesion and Coupling 28-02-20-9-2

Various design concepts

02-03-20 3-2 and notations, real-time 12 and distributed system

design Software Documentation 03-03-20

-3-2 13 18MCA25.1

2 Dataflow Oriented L1, L3 18MCA25.2 04-03-20

14 Design 18MCAZ5.3

06-03-20 Jackson System Development 15

10-03-20 Designing for reuse o-30 16

11-03-20 Programming Standards

1-3-2 17

13-03-20 Design of any

application project- Case study

13-3- 18

.w.w

Introduction to software 19 16-03-206-3 testing fundamentals

Software testing

17-03-20 I-J- strategies: Black box testing

20

Software testing

18-03-20 8-3-1 strategies : White box

testing 21

System testing, Object Orientation testing and -3- 22 20-03-20

State-based testing 18MCAZ5.1

3 Testing tools and test L2, L3 23 18MCA25.4 23-03-20R3-3-9 D0 case management

Software Maintenance

24 24-03-204 1- Organization

Introduction to

25 30-03-20 J- W Maintenance Reports

Types of Maintenance 26 31-03-20 -3-3 0

Case Study - Testing

27 technique 01-04-20 -

28 Introduction and sCope I.5, L6 03-04-20 J-1

of software metrics

18MCA25.1 Classification of

29 18MCAZ5.5 06-04-20 6-2 software metrics

Measuring process and 30 product attributes 07-04-20 1-4-2

Direct and indirect

31 08-04-20& 0 measures

Introduction to Cost

32 13-04-2034-2 estimation

Software Reliability 33 15-04-20 S-L9

Introduction to software34 17-04-20 114- quality assurance

Quality Standards 20-04-20 o 35

Cocomo model - Case

21-04-201-4-2 36 Study

Need for Software 22-04-2024-10 Configuration

Management Version Control System

37

24-04-20 M4-3 38

The SCM Process 39 04-05-20 -S-

Introduction to the

activities and items in 05-05-20-S 0 40

SCM 18MCA25.1

Taxonomny L4, L6 41 18MCA25.6 06-05-20 S-2

CASE repository 42 08-05-20 8 s-

Features of CASE

43 11-05-20 t-s-2 repository

Introduction to Web 12-05-20 9- -2 D 44 Engineering

SCM Case Study 13-05-20 13-s- 45

wwww.w itr

46 Revision Unit 1 15-05-20 K-S-2

18-05-20 9-S- 47 Revision Unit 2

Revision Unit 3 48 19-05-20 1-S

49 Revision Unit 4 20-05-20 P5- 50 Revision Unit 5 26-05-20 --

wwwwww.an

51 Discussion on Important

Questions 27-05-20 |31-5-

*L1- Remembering; L2 - Understanding; L3 - Applying; L4 - Analysing; L5 - Evaluating; L6- Creating

Text Books:

1. Roger S. Pressman, "Software Engineering: A Practitioner Approach", Seventh

edition, McGraw-Hill, 2010. 2. Richard Fairley, " Software Engineering Concepts", Tata McGraw Hill Edition, 2008

Reference Books:

1. Ali Behforroz, Frederick Hudson, "Software Engineering Fundamentals", Oxford

Indian Reprint, 2012. 2. Sommerville, "Software Engineering", Sixth Edition, Addison Wesley-Longman, 2004.

3. Kassem A. Saleh, "Software Engineering'", First Edition, J. Ross Publishing, 2009.

4. Pankaj Jalote, "An Integrated approach to Software Engineering", Third Edition,

Springer Verlag, 2005. 5. Roger S. Pressman, David Lowe, "Web Engineering: A Practitioner's Approach",

Special Indian edition, McGraw-Hill, 2008. 6. Jibitesh Mishra, Ashok Mohanty, "Software Engineering'", Pearson Education, First

Edition, 2012.

Sample Questions: wwww.wwww wwwwwwwwwwwww.wwwwwwwwwwww wwwww

Question Questions No.

Q1 (a) Why does software engineering follow a layered technology ? Explain its importance.

Q1 (b) The waterfall model is a primary model that is used to develop software. Give your

thoughts on this.

Q2 (a) List down any three important design concepts with proper illustrations and

programming examples.

Q2 (b) Differentiate between functional dependence and functional independence with proper

examples.

(a) Justify the importance of white-box testing and its different techniques with good

examples.

Q3 (b) Why is software maintenance an important concept in the software industry? Illustrate

the benefits of adoptng a good software maintenance standard.

How does software metrics help in improving the productivity ofa software? List a few 00 metrics that are used in the industry today.

www.wo

4 (a)

List any three process and product metrics with sufficient explanation and examples. 04 (b)

Q5 (a) List the activities that need to be followed while adopting a proper SCM methodology.

Q5 (b) Perform an SCM case study for a typical software development scenario.

Assessment rubrics that is going to be adopted for direct attainment is depicted in below table

Level of

Bench Mark

AchievementElaboration on Course Grading Description Set

(Out of 50)

Excellent (A) The Student's performance is outstanding in almost all the

intended course learning outcomes 40 to 50

The student's performance is good in most of the intended

course learning outcomes.

30 to 39

Good (B)

Maroinal (C he student s performance is barely satisfactory. It marginally

Marginal (C)meets the intendedcourse learning outcomes

20 to 29

The Students performance is inadequate. Student fails to meet

many of the intended course learning outcomes

Less than 20

Fail (F)

NOTE: Have different Assesment pattern for tests, assignments, quizzes etc.

HOD

Staff In-charge NHCE/LPT/O03

ncet, S:2ndur Post, Pangai S50