2015-2016 - Welcome To J.B.Institute of Engineering & … · · 2016-02-29COURSE PLAN 2015-2016...

2015-2016

FACULTY DETAILS:

Name of the Faculty:: Ch.Srinivasulu

Designation: Associate Professor

Department:: Information Technology

COURSE DETAILS

Name Of The Programme:: B.Tech Batch:: 2012

Designation:: Associate Professor

Year : III Semester : I


Title of The Subject Software Engineering Subject Code : 55029

No of Students 84

COURSE PLAN

2015-2016

Regulation: R12

COURSE PLAN

2015-2016

Regulation: R12

FACULTY DETAILS:

Name of the Faculty:: Ch.Srinivasulu Designation: Associate Professor


1. TARGET

a) Percentage Pass: 100

b) Percentage I class : 95

2. COURSE PLAN

The topics of Units are covered by lectures, guest lectures, design exercises, solving numerical problems (if it consists of), demonstration of models, and by assignments, etc.)

3. METHOD OF EVALUATION

3.1. Continuous Assessment Examinations (CAE 1, CAE 2)

3.2. Assignments / Seminars

3.3. Mini Projects

3.4. Quiz

3.5. Term End Examination

3.6. Others

4. List out any new topic(s) or any innovation you would like to introduce in teaching the subject in this Semester.

Signature of HOD Signature of Faculty Date: Date:

FACULTY DETAILS:




Guidelines for Preparing the Course:

Course Description:

Requirements, Analysis, Design, Implementation, Testing. Project Management. Applying a development design process to produce high quality software. Topics include: identifying user requirements; performing problem analysis to produce process oriented documentation; using UML notation to create design models and diagrams; investigating and applying design patterns, project management; configuration management. Completing software projects applying development processes using an object-oriented language.

Course Objectives:

1. knowledge of basic SW engineering methods and practices, and their appropriate application; 2. A general understanding of software process models such as the waterfall and evolutionary

models. 3. An understanding of the role of project management including planning, scheduling, risk

management, etc. 4. An understanding of software requirements and the SRS document. 5. An understanding of different software architectural styles. 6. An understanding of implementation issues such as modularity and coding standards. 7. An understanding of approaches to verification and validation including static analysis, and

reviews. 8. An understanding of software testing approaches such as unit testing and integration testing. 9. An understanding of software evolution and related issues such as version management. 10. An understanding on quality control and how to ensure good quality software.

Learning Outcomes:

1. Students will demonstrate knowledge of the distinction between critical and non-critical Systems.

2. Students will demonstrate the ability to manage a project including planning, scheduling and risk Assessment/management.

3. Students will author a software requirements document. 4. Students will demonstrate an understanding of the proper contents of a software

requirements Document. 5. Students will author a formal specification for a software system. 6. Students will demonstrate an understanding of distributed system architectures and

application architectures. 7. Students will demonstrate an understanding of the differences between real-time and non-

real Time systems. 8. Students will demonstrate proficiency in rapid software development techniques. 9. Students will be able to identify specific components of a software design that can be targeted 3. For reuse. 10. Students will demonstrate proficiency in software development cost estimation.

GUIDELINES TO STUDY THE SUBJECT

2015-2016

Regulation: R12

FACULTY DETAILS:




On completion of this Subject / Course the student shall be able to:

S.No. Objectives Outcomes 1.

knowledge of basic SW engineering methods and practices, and their appropriate application;

Students will demonstrate knowledge of the distinction between critical and non-critical Systems.

2.

A general understanding of software process models such as the waterfall and evolutionary models.

Students will demonstrate the ability to manage a project including planning, scheduling and risk Assessment/management.

3.

An understanding of the role of project management including planning, scheduling, risk management, etc.

Students will be able to create their own project planning accordingly.

4.

An understanding of software requirements and the SRS document.

Students will author a software & Hardware requirements document.

5.

An understanding of different software architectural styles.

Students will demonstrate an understanding of the proper contents of a software requirements .

6.

An understanding of implementation issues such as modularity and coding standards.

Students will demonstrate an understanding of distributed system architectures and application architectures.

7.

An understanding of approaches to verification and validation including static analysis, and reviews.

Students will demonstrate an understanding of the differences between real-time and non-real

8.

An understanding of software testing approaches such as unit &integration testing.

Students will demonstrate proficiency in rapid software development techniques.

9.

An understanding of software evolution and related issues such as version management.

Students will be able to identify specific components of a software design that can be targeted For reuse.

10.

An understanding on quality control and how to ensure good quality software.

Students will demonstrate proficiency in software development cost estimation.

Signature of Faculty Date:

Note: For each of the OBJECTIVE indicate the appropriate OUTCOMES to be achieved. Kindly refer Page 16, to know the illustrative verbs that can be used to state the objectives.

COURSE OBJECTIVES

2015-2016

Regulation: R12

FACULTY DETAILS:


Designation: Associatte Professor


The expected outcomes of the Course / Subject are:

S.No. General Categories of Outcomes Specific Outcomes of the Course

A. An ability to apply knowledge of mathematics,

science, and engineering

B. An ability to design and conduct experiments, as

well as to analyze and interpret data

An ability to design a system, component, or

C. process to meet desired needs within realistic

Constraints such as economic, environmental,

social, political, ethical, health and safety,

Manufacturability and sustainability

D. An ability to function on multi-disciplinary teams

E. An ability to identify, formulate, and solve

engineering problems

F. An understanding of professional and ethical

responsibility

G. An ability to communicate effectively

The broad education necessary to understand the

H. impact of engineering solutions in a global,

economic, environmental, and societal context

I. A recognition of the need for, and an ability to

engage in life-long learning

J. A knowledge of contemporary issues

An ability to use the techniques, skills, and

K. modern engineering tools necessary for

engineering practice.

Objectives – Outcome Relationship Matrix (Indicate the relationships by mark).

Outcomes A B C D E F G H I J K

Objectives

1.

2.

3.

4.

5.

6.

7.

8.

9.

10.

5

COURSE OUTCOMES

2015-2016

Regulation: R12

FACULTY DETAILS:




The Schedule for the whole Course / Subject is::

S. No. Description Duration (Date) Total No.

From To of Periods

1.

Introduction to Software Engineering: The

evolving role of software, Changing Nature of

Software, legacy software, Software myths.A

Generic view of process: Software

engineering- Alayered technology, a process

framework, The capability Maturity Model

Integration(CMMI), Process patters,process

assessment, personal and team process

models.

10

2.

Process models: The waterfall model,

Incremental process models,Evolutionary

process models, Specialized process models,

The Unified process.Software Requirements:

Functional and non-fuctional requirements,

User requirements, System requirements,

Interface specification, the software

requirements document.

6

3.

Requirements engineering process: Feasibility

studies, Requirements elicitation and analysis,

Requirements validation, Requirements

management. System models: Context

Models, Behavioural models, Data models,

Object models, structured methods.

8

4.

Design Engineering: Design process and

Design quality, Design concepts, The design

model, pattern based software design. Creating

an architectural design: software architecture,

Data design, Architectural styles and patterns,

Architectural Design, assessing alternative

architectural design, mapping data flow into a

software architecture.

5

5.

Modeling components level design: Designing

class-based components, conducting

component-level design.Object constraint

language, designing conventional components,

Performing User interface design: Godlen

rules, User interface analysis and design,

interface analysis, interface design steps,

13

COURSE SCHEDULE

2015-2016

Regulation: R12

Design evaluation.

6.

Testing Strategies: Astrategic approach to

software testing, test strategies for

conventional software , Black-box and White-

box testing, Validation testing, System testing,

the art of Debugging.Product metrics:Software

Quality, Frame work for Product metrics,

Metrics for Analysis Model, Metrics for

Design Model, Metrics for source code.

Metrics for testing, Metrics for maintenance.

9

7

Metrics for Process and Products: Software

Measurement, Metrics for software

quality.Risk management: Reactive vs

proactive Risk strategies, software risks, Risk

identification, Risk projection, Risk

refinement, RMMM,RMMM Plan.

8

8

Quality M anagement: Quality concepts,

Software quality assurance,Software Reviews,

Formal technical reviews, Statistical Software

quality Assurance, Software reliability, The

ISO 9000 quality standards.

7

Total No. of Instructional periods available for the course: Hours / Periods

SCHEDULE OF INSTRUCTIONS

2015-2016

UNIT - I Regulation: R12

Ch.Srinivasulu

Associate Professor

Information Technology

SI. No. of Objectives & References

Topics / Sub - Topics Outcome (Text Book, Journal…)

No. Periods

Nos. Page No___ to ___

1

3

Introduction to Software Engineering:

The evolving role of software, Changing

Nature of Software,

1

Software Engineering: A Practictionar’s Approach, Roger S Pressman, six edition. McGrawHill International Edition, 2005. (TB1)

2

1

legacy software, Software myths.

Software Engineering, Ian

SommerVille, seventh

edition, Pearson

education, 2004. (TB2)

3

2

A Generic view of process: Software

engineering- Alayered technology

4

2

a process framework, The capability

Maturity Model Integration(CMMI)

5

2

Process patters,process assessment,

personal and team process models.

6

1

Overview

7

1

Conclusion

Signature of Faculty Date

Note: 1. ENSURE THAT ALL TOPICS SPECIFIED IN THE COURSE ARE MENTIONED. 2. ADDITIONAL TOPICS COVERED, IF ANY, MAY ALSO BE SPECIFIED BOLDLY. 3. MENTION THE CORRESPONDING COURSE OBJECTIVE AND OUT COME NUMBERS AGAINST EACH TOPIC.


2015-2016

UNIT - II Regulation: R12

Ch.Srinivasulu

Associate Professor




No. Periods


1 3

Process models: The waterfall model,

Incremental process models,

2 (TB1), (TB2)

2 1

Evolutionary process models,

Specialized process models, The Unified

process.

3 1

Software Requirements: Functional and

non-fuctional requirements,

User requirements, System

requirements, Interface specification,

the software requirements document.

4 1

Overview and Conclusion


Note: 1. ENSURE THAT ALL TOPICS SPECIFIED IN THE COURSE ARE MENTIONED. 2. ADDITIONAL TOPICS COVERED, IF ANY, MAY ALSO BE SPECIFIED BOLDLY.

MENTION THE CORRESPONDING COURSE OBJECTIVE AND OUT COME NUMBERS AGAINST EACH TOPIC.


2015-2016

UNIT - III Regulation: R12

Ch.Srinivasulu

Associate Professor


SI. Objectives & References


No.


1

Requirements engineering process:

Feasibility studies, Requirements

elicitation and analysis, Requirements

validation,

3 (TB1), (TB2)

2

Requirements elicitation and analysis,

Requirements validation,

3

Requirements management.

System models: Context Models,

4

Behavioural models, Data models,

Object models, structured methods.

5

Overview

6

Conclusion





2015-2016

UNIT - IV Regulation: R12

Ch.Srinivasulu

Associate Professor




No. Periods


1 2

Design Engineering: Design process and

Design quality, Design concepts,

4 (TB1), (TB2)

2 1

The design model, pattern based

software design.

3 1

Creating an architectural design:

software architecture, Data design,

Architectural styls and patterns

4 1

assessing alternative architectural

design, mapping data flow into a

software architecture.





2015-2016

UNIT - V Regulation: R12

Ch.Srinivasulu

Associate Professor




No. Periods


1 3

Modeling components level design:

Designing class-based components,

5 (TB1), (TB2)

2 3

conducting component-level design.

Object constraint language,

3 3

designing conventional components,

Performing ,User interface design

4 2

Godlen rules, User interface analysis and

design, interface analysis, interface

design steps, Design evaluation.

5 2

Over view and Conclusion





2015-2016

UNIT - VI Regulation: R12

Ch.Srinivasulu

Associate Professor


SI.

No. of Objectives & References

Topics / Sub - Topics

Outcome (Text Book, Journal…)

No. Periods


1 3

Testing Strategies: A strategic approach

to software testing, test strategies for

conventional software ,

6 (TB1), (TB2)

2 2

Black-box and White-box testing,

Validation testing, System testing, the

art of Debugging.

3 2

Product metrics: Software Quality,

Frame work for Product metrics, Metrics

for Analysis Model.

4 2

Metrics for Design Model, Metrics for source code. Metrics for testing, Metrics for maintenance.





2015-2016

UNIT - VII Regulation: R12

Ch.Srinivasulu

Associate Professor




No. Periods


1 2 Metrics for Process and Products:

Software Measurement, Metrics for

software quality. 7 (TB1), (TB2)

2 2 Risk management: Reactive vs proactive

Risk strategies,

3 2 software risks, Risk identification, Risk

projection,

4 2 Risk refinement, RMMM,RMMM Plan.

5 1 Overview

6 Conclusion





2015-2016

UNIT - VIII Regulation: R12

Ch.Srinivasulu

Associatet Professor




No. Periods


1 2 Quality Management: Quality concepts, Software quality assurance,

8,9,

10 (TB1), (TB2)

2 2 Software Reviews, Formal technical

reviews,

3 2 Statistical Software quality Assurance,

Software reliability,

4 2 The ISO 9000 quality standards.

5 1 Overview and Conclusion




COURSE COMPLETION STATUS

2015-2016

Regulation: R12

FACULTY DETAILS:


Subject:: Software Engineering

Subject Code: 6755029


Actual Date of Completion & Remarks, if any

Nos. of

Units Remarks Objectives

Achieved

Unit 1

Unit 2

Unit 3

Unit 4

Unit 5

Unit 6

Unit 7

Unit 8

Signature of Dean of School Signature of Faculty Date: Date:

NOTE: AFTER THE COMPLETION OF EACH UNIT MENTION THE NUMBER OF OBJECTIVES ACHIEVED.

FACULTY DETAILS:


Designation: Associate professor



Date:

This Tutorial corresponds to Unit Nos. Time:

Q1. What is software and software engineering?

Q2. what are the objectives of CMMI?

Q3. What are the phases of waterfall model?

Q4. Briefly explain about Functional and non-functional requirements.

Q5. What is Requirement validation and verification ?

Please write the Questions / Problems / Exercises which you would like to give to the students and also mention the

objectives to which these questions / Problems are related.


TUTORIAL SHEETS - I

2015-2016

Regulation: R12

2015-2016

FACULTY DETAILS:





Date:


Q1. Explain all System models.

Q2. Explain Design process and Design quality?

Q3. what is Software architecture? Briefly explain with Architectural styls and patterns.

Q4. Explain Golden rules in User interface design.

Q5. Briefly explain Design evaluation in Modeling component-level design.




Regulation: R12

FACULTY DETAILS:


Designation: Associate t Professor


Date:


Q1. Explain about test strategies for conventional software.

Q2. what is the difference between product measurements and metrics?

Q3. Discuss about software tools for test case design

Q4. How should we use metrics during the project itself

Q5.




TUTORIAL SHEETS - II

2015-2016

Regulation: R12

These verbs can also be used while framing questions for Continuous Assessment Examinations as well as for End – Semester (final) Examinations.

ILLUSTRATIVE VERBS FOR STATING GENERAL OBJECTIVES

Know Understand Analyze Generate

Comprehend Apply Design Evaluate

ILLUSTRATIVE VERBS FOR STATING SPECIFIC OBJECTIVES:

A. Cognitive Domain

1 2 3 4 5 6

Knowledge

Comprehension Application

Analysis

Synthesis Evaluation

Understanding

of knowledge & of whole w.r.t. its combination of judgement

comprehension

constituents ideas/constituents

Define Convert Change Breakdown Categorize Appraise

Identify Defend Compute Differentiate Combine Compare

Label Describe (a Demonstrate Discriminate Compile Conclude

List procedure) Deduce Distinguish Compose Contrast

Match Distinguish Manipulate Separate Create Criticize

Reproduce Estimate Modify Subdivide Devise Justify

Select Explain why/how Predict Design Interpret

State Extend Prepare Generate Support

Generalize Relate Organize

Give examples Show Plan

Illustrate Solve Rearrange

Infer Reconstruct

Summarize Reorganize

Revise

B. Affective Domain C. Psychomotor Domain (skill development)

Adhere Resolve Bend Dissect Insert Perform Straighten

Assist Select Calibrate Draw Keep Prepare Strengthen

Attend Serve Compress Extend Elongate Remove Time

Change Share Conduct Feed Limit Replace Transfer

Develop Connect File Manipulate Report Type

Help Convert Grow Move preciselyReset Weigh

Influence Decrease Handle Operate Run

Initiate Demonstrate Increase Paint Set

ILLUSTRATIVE VERBS

FOR STATING

INSTRUCTIONAL OBJECTIVES

2015-2016

Regulation: R12

LESSON PLAN

Unit-1

2015-2016

Regulation: R12

Name of the Faculty: Ch.Srinivasulu

Subject Software Engineering

Subject Code 55029

Unit I

INSTRUCTIONAL OBJECTIVES:

On completion of this lesson the student shall be able to (Outcomes)

1. Students will demonstrate knowledge of the distinction between critical and non-critical Systems.

2. Students will demonstrate the ability to manage a project including planning, scheduling and risk Assessment/management.

3. Students will author a software requirements document.

4 Students will demonstrate an understanding of the proper contents of a software requirements

Session

No Topics to be covered

Time

Ref

Teaching

Method

1

Introduction to Software Engineering: The evolving role of

software, Changing Nature of Software,

50min TB1,TB 2 Black Board

2

legacy software, Software myths.

3

A Generic view of process: Software engineering- Alayered

technology

4

a process framework, The capability Maturity Model

Integration(CMMI)

5

Process patters,process assessment, personal and team process

models.

6 Overview

7 Conclusion

ASSIGNMENT

Unit-I

2015-2016

Regulation: R12

Assignment / Questions

1. Explain Software engineering –Layered technology?

Objectives: Students will demonstrate knowledge of the distinction between critical and non-

critical Systems.

2. Explain Software Myths?

Signature of Faculty Note: Mention for each question the relevant objectives and outcomes.

LESSON PLAN

Unit-II

2015-2016

Regulation: R12



Subject Code 55029

Unit II


On completion of this lesson the student shall be able to

1. Different types of models

2. Identify functional and non-functional requirements.

3. User requirements, system requirements

4. Prepare the documentation.

Session


Time

Ref

Teaching

Method

1

Process models: The waterfall model, Incremental process

models,


2

Evolutionary process models, Specialized process models, The

Unified process.

50min

3

Software Requirements: Functional and non-fuctional

requirements,

User requirements, System requirements, Interface

specification, the software requirements document.

50min

4 Overview and Conclusion 50min

ASSIGNMENT

Unit-II

2015-2016

Regulation: R12

Assignment / Questions 1.Explain about Spiral and Incremental process models.

2.What is Software requirement document?

Outcomes: Students will author a software requirements document.


LESSON PLAN

Unit-III

2015-2016

Regulation: R12



Subject Code 55029

Unit III


On completion of this lesson the student shall be able to(Outcomes)

1. Know about what consists under Requirements elicitation and analysis

2. Know the difference between verification and validation

3. Different types of models

4. Structured methods.

Session


Time

Ref

Teaching

Method

1

Requirements engineering process: Feasibility studies,

Requirements elicitation and analysis, Requirements validation,


2 Requirements elicitation and analysis, Requirements validation,

3

Requirements management.

System models: Context Models,

4

Behavioral models, Data models, Object models, structured

methods.

5 Overview

6 Conclusion

ASSIGNMENT

Unit-III

2015-2016

Regulation: R12

Assignment / Questions 1.Briefly explain about the Requirements elicitation and analysis.

2.Write short notes on

(a) Object models and

(b) Structured methods.

Objective: Students will author a formal specification for a software system.


LESSON PLAN

Unit-IV

2015-2016

Regulation: R12



Subject Code 55029

Unit IV



1. Students will demonstrate an understanding of distributed system architectures and

application architectures.

2. Make selection different architectural style patterns

3. Assessing alternative architectural design

4. Mapping data flow into a software architecture.

Session


Time

Ref

Teaching

Method

1

Design Engineering: Design process and Design quality, Design

concepts,


2

The design model, pattern based software design.

3

Creating an architectural design: software architecture, Data

design,

Architectural styles and patterns

4

Assessing alternative architectural design, mapping data flow

into software architecture.

5.

ASSIGNMENT

Unit-IV

2015-2016

Regulation: R12

Assignment / Questions 1.What is prototype in software engineering? Mapping data flow into a software architecture.

2.Explain with DFD for all Design concept

Objective: Students will demonstrate an understanding of distributed system architectures and application architectures.


LESSON PLAN

Unit-V

2015-2016

Regulation: R12



Subject Code 55029

Unit V



1.Modeling design with class and object

2.user interface design

3.importance of golden rules

4 interface design steps and design evaluation.

Session


Time

Ref

Teaching

Method

1

Modeling components level design: Designing class-based

components,


2

conducting component-level design.

Object constraint language,

3

designing conventional components, Performing ,User interface

design

4

Godlen rules, User interface analysis and design, interface

analysis, interface design steps, Design evaluation.

5 Over view and Conclusion

ASSIGNMENT

Unit-V

2015-2016

Regulation: R12

Assignment / Questions 1.Write short notes on User interface analysis and design.

2.How the Golden rules are useful in User interface Design.


LESSON PLAN

Unit-VI

2015-2016

Regulation: R12



Subject Code 55029

Unit VI



1.Strategic approach on software testing

2.different types of testing

3.product metrics

4 metrics on all phases.

Session


Time

Ref

Teaching

Method

1

Testing Strategies: Astrategic approach to software testing, test

strategies for conventional software ,


2

Black-box and White-box testing, Validation testing, System

testing, the art of Debugging.

3

Product metrics:Software Quality, Frame work for Product

metrics, Metrics for Analysis Model, Metrics for Design Model,

Metrics for source code. Metrics for testing, Metrics for

maintenance.

ASSIGNMENT

Unit-VI

2015-2016

Regulation: R12

Assignment / Questions 1. How can you explain about the Metrics for maintenance?

2. Give some Metrics for source code.

Objective : Students will be able to identify specific components of a software design that can be targeted with implementation and then testing.


LESSON PLAN

Unit-VII

2015-2016

Regulation: R12



Subject Code 55029

Unit VII



1.Measure the software products

2.find metrics for software quality

3.Identify risks

4 RMMM plan.

Session


Time

Ref

Teaching

Method

1

Metrics for Process and Products: Software Measurement,

Metrics for software quality.


2 Risk management: Reactive vs proactive Risk strategies,

3 software risks, Risk identification, Risk projection,

4 Risk refinement, RMMM,RMMM Plan.

5 Overview

6 Conclusion

ASSIGNMENT

Unit-VII

2015-2016

Regulation: R12

Assignment / Questions 1. Discuss the direct and indirect measures of software process and product

2. What is meant by BVA? Discuss the guidelines to create BVA test cases.

Objective: Students will demonstrate proficiency in software development cost estimation.


LESSON PLAN

Unit-VIII

2015-2016

Regulation: R12



Subject Code 55029

Unit VIII



1.Know about SQA

2.How are the reviews

3. ISO 9000 quality standards

4. Statistical Software quality Assurance

Session


Time

Ref

Teaching

Method

1 Quality Management: Quality concepts, Software quality assurance,


2 Software Reviews, Formal technical reviews, 50min

3 Statistical Software quality Assurance, Software reliability, 50min

4 The ISO 9000 quality standards. 50min

5 Overview and Conclusion 50min

ASSIGNMENT

Unit-VIII

2015-2016

Regulation: R12

Assignment / Questions 1. The Mean-Time-Between-Failure(MTBF)concept for software is open to criticism.

2. Can a program be correct and still not be reliable?


2015-2016 - Welcome To J.B.Institute of Engineering & … · · 2016-02-29COURSE PLAN 2015-2016...

Documents

Transcript of 2015-2016 - Welcome To J.B.Institute of Engineering & … · · 2016-02-29COURSE PLAN 2015-2016...