Department of Information Technology SOFTWARE ENGINEERING III B.Tech -I Sem

NALINAKSHI M Asst. Professor

J.B.Institute of Engg & Technology Yenkapally, Moinabad(Mandal) Himathnagar(post),Hydreabad

JBIE

T

Dept o

f IT

Page: 2

Results Target Total Strength of the Class: 100

S. No Class / Division No. of Students

a. First Class with Distinction 60

b. First Class 30

c. Pass Class 10

Method of Evaluation

a. Internal Examination 2

b. Unit Wise Assignments 4

c. Descriptive Exam 2

d Objective 2

e. Final Examination 1

JBIE

T

Dept o

f IT

Page: 3

Course Objective In this course, students will gain a broad understanding of the discipline of software engineering and its application to the development of and management of software systems.

This includes:

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

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

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

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

and reviews. • An understanding of software testing approachs such as unit testing and integration

testing. • An understanding of software evolution and related issues such as version management. • An understanding on quality control and how to ensure good quality software. • An understanding of some ethical and professional issues that are important for

software engineers. • development of significant teamwork and project based experience

Course Aim and Approach After this course students should have general knowledge on Focus on practical software engineering techniques and tools for component-based object oriented system. The objective of this course is to learn how to design and construct OO systems. Main topic areas identified by IEEE Software Engineering Body of Knowledge: Software Engineering Process: Extreme Programming Software Design: Object oriented design with UML Software Construction: OO coding practices, design patterns, refactoring, concurrency, aspect oriented programming Software Testing: integrated testing Object Oriented Analysis and Design (using UML) Software Engineering Tools and Methods: formal specification techniques, design by contract, and tools

JBIE

T

Dept o

f IT

Page: 4

J.B.Institute of Engg & Technology Department of Information Technology

Syllabus

Subject Name : SOFTWARE ENGINEERING Subject Code : 55029 Class : III B.Tech

Sl.No Unit No: Details of the unit

01 Unit – I 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.

02 Unit – II 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.

03 Unit – III Requirements engineering process: Feasibility studies, Requirements elicitation and analysis, Requirements validation, Requirements management. System models: Context Models, Behavioral models, Data models, Object models, structured methods.

04 Unit – IV 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 styls and patterns, Architectural Design, assessing alternative architectural design, mapping data flow into a software architecture.

05 Unit – V 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,

JBIE

T

Dept o

f IT

Page: 5

Design evaluation.

06 Unit - VI 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.

07 Unit - VII 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.

08 Unit - VIII Quality M anagement: Quality concepts, Software quality assurance,Software Reviews, Formal technical reviews, Statistical Software quality Assurance, Software reliability, The ISO 9000 quality standards.

JBIE

T

Dept o

f IT

Page: 6

Guidelines to Students Where will this subject help?

In Software Technology Books / Material

Text Books (TB) TB 1 : Software Engineering: A Practictionar’s Approach, Roger S Pressman, six edition. McGrawHill International Edition, 2005. TB 2 : Software Engineering, Ian SommerVille, seventh edition, Pearson education, 2004.

Suggested / Reference Books (RB) RB 1 : Software Engineering: A Precise Approach, Pankaj Jalote, Wiley India,2010.

RB 2 : Software Engineering: A Primer, Waman S Jawadekar, Tata McGraw Hill, 2008. RB3: Software Engineering Pronciples and Practice, Hans van Vliet, 3rd edition, John Wiley & Sons Ltd. RB 4 : Fundamental of Software Engineering, RajibMall, PHI, 2005.

&&&&&&&

JBIE

T

Dept o

f IT

Page: 7

J.B.Institute of Engg & Technology Department of Information Technology

SUBJECT PLAN : Subject Name :SOFTWARE ENGINEERING Subject Code : 55029 Class : III B.Tech Faculty Name : M.Nalinakshi

Number of Hours / lectures available in this Semester / Year 65

Distribution of Hours Unit – Wise

Unit Topic Total No. of Hours

I

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.

11

II

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.

11

III

Requirements engineering process: Feasibility studies, Requirements elicitation and analysis, Requirements validation, Requirements management. System models: Context Models, Behavioral models, Data models, Object models, structured methods.

08

IV

Design Engineering: Design process and Design quality, Design concepts, The design model, pattern based software design. Creating an architectural design: software architecture, Data design,

08

JBIE

T

Dept o

f IT

Page: 8

&&&&&&&&

Architectural styls and patterns, Architectural Design, assessing alternative architectural design, mapping data flow into a software architecture.

V

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, Design evaluation.

06

VI

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.

06

VII

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.

08

VIII

Quality Management: Quality concepts, Software quality assurance,Software Reviews, Formal technical reviews, Statistical Software quality Assurance, Software reliability, The ISO 9000 quality standards.

09

Total 65 JBIE

T

Dept o

f IT

Page: 9

J.B.Institute of Engg & Technology Department of Information Technology

LESSON PLAN : Subject Name : SOFTWARE ENGINEERING Subject Code : 55029 Class : III B.Tech Faculty Name : M.Nalinakshi Unit I: Introduction to Software Engineering LECTURE PLAN: Total no_ of classes: 11

Unit #

Topic as per JNTU syllabus

Lesson #

Suggested Books ** (Refer the

list

Question Bank

Hand outs OQ DQ AQ

I Introduction to Software Engineering: The evolving role of software, Changing Nature of Software,

II legacy software, Software myths.

III A Generic view of process: Software engineering- Alayered technology

IV a process framework, The capability Maturity Model Integration(CMMI)

V Process patters,process assessment, personal and team process models.

VI Overview VII Conclusion

JBIE

T

Dept o

f IT

Page: 10

OBJECTIVE QUESTIONS :

1.Which question no longer concerns the modern software engineer?

A) Why does computer hardware cost so much?

B) Why does software take a long time to finish?

C) Why does it cost so much to develop a piece of software?

D) Why can't software errors be removed from products prior to delivery? 2. Today the increased power of the personal computer has brought about an

abandonment of the practice of team development of software.

A) True

B) False3 3.Software is a product and can be manufactured using the same technologies used for other engineering artifacts.

A) True

B) False4 4.Software deteriorates rather than wears out because

A) Software suffers from exposure to hostile environments

B) Defects are more likely to arise after software has been used often

C) Multiple change requests introduce errors in component interactions

D) Software spare parts become harder to order DESCRIPTIVE QUESTIONS : 1. What is software and software engineering? 2. what are the objectives of CMMI? ASSIGNMENT QUESTIONS: 1.Expalain Software engineering –Layered technology? 2. Explain Software Myths? &&&&&&&&

JBIE

T

Dept o

f IT

Page: 11

UNIT-III : Process models LECTURE PLAN: Total No_ of Classes: 11

S.No Name of the Topic Reference book code

No. of classes required

8 Process models: The waterfall model, Incremental process models,

1, 2 3

9 Evolutionary process models, Specialized process models, The Unified process.

1, 2 3

10 Software Requirements: Functional and non-fuctional requirements, User requirements, System requirements, Interface specification, the software requirements document.

1, 2 3

11 Overview and Conclusion 1, 2 2

JBIE

T

Dept o

f IT

Page: 12

OBJECTIVE QUESTIONS : 1. Evolutionary software process models a. Are iterative in nature b. Can easily accommodate product requirements changes c. Do not generally produce throwaway systemsd. d. All of the above 2. The incremental model of software development is a. A reasonable approach when requirements are well defined. b. A good approach when a working core product is required quickly. c. The best approach to use for projects with large development teams. d. A revolutionary model that is not used for commercial products.1 3. The spiral model of software development a. Ends with the delivery of the software product b. Is more chaotic than the incremental model c. Includes project risks evaluation during each iterationd. d. All of the above DESCRIPTIVE QUESTIONS : 1.What are the phases of waterfall model? 2.Briefly explain about Functional and non-functional requirements. ASSIGNMENT QUESTIONS: 1.Explain about Spiral and Incremental process models. 2.What is Software requirement document? &&&&&&

JBIE

T

Dept o

f IT

Page: 13

UNIT-III : Requirements engineering LECTURE PLAN: Total No_ of Classes: 08

S.No Reference book code

No. of classes required

12 Requirements engineering process: Feasibility studies, Requirements elicitation and analysis, Requirements validation,

1,2 2

13 Requirements elicitation and analysis, Requirements validation,

1,2 1

14 Requirements management. System models: Context Models,

1,2 1

15 Behavioral models, Data models, Object models, structured methods.

2

16 Overview 1,3 1 17 Conclusion 1,3 1

JBIE

T

Dept o

f IT

Page: 14

OBJECTIVE QUESTIONS : 1.Requirements engineering is a generic process that does not vary from one software project to another

A) True

B) False2 2.During project inception the intent of the of the tasks are to determine

A) basic problem understanding

C) people who want a solution

D) none of the bbove

E) a,b and c DESCRIPTIVE QUESTIONS : 1.What is Requirement validation and verification ? 2.Explain all System models. ASSIGNMENT QUESTIONS: 1.Briefly explain about the Requirements elicitation and analysis. 2.Write short notes on Object models and Structured methods. &&&&&&&&

JBIE

T

Dept o

f IT

Page: 15

UNIT-IV : Design Engineering LECTURE PLAN: Total No_ of Classes: 05

S.No Name of the Topic Reference book code

No. of classes required

18 Design Engineering: Design process and Design quality, Design concepts,

1,2,3 2

19 The design model, pattern based software design.

1,3 1

20 Creating an architectural design: software architecture, Data design, Architectural styls and patterns

1,2 1

21 assessing alternative architectural design, mapping data flow into a software architecture.

1,3 1

JBIE

T

Dept o

f IT

Page: 16

OBJECTIVE QUESTIONS : 1.In engineering, the design process begins when…

a. information about an existing product is gathered by an engineer

b. an engineering design team comes up with ideas for a new product

c. a design engineer recognizes the need for a solution to a problem 2. Which step of the engineering design loop distinguishes an engineer from a technician?

a. Construct a Prototype

b. Test and Evaluate a Prototype

c. Redesign 3.The engineering design process is iterative. This allows engineers to… a. become proficient at different engineering software applications

b. find the most optimal solution to a design problem

c. Incorporate both math and science concepts into a design problem 4. When finding the solution to an engineering design problem, there is/are usually… a. only one possible correct solution

b. a very limited number of possible correct solutions

c. many possible correct solutions DESCRIPTIVE QUESTIONS : 1.Explain Design process and Design quality? 2.what is Software architecture? Briefly explain with Architectural styls and patterns. ASSIGNMENT QUESTIONS: 1.What is prototype in software engineering? Mapping data flow into a software architecture. 2.Explain with DFD for all Design concept &&&&&&&&

JBIE

T

Dept o

f IT

Page: 17

UNIT-V: Modeling components level design LECTURE PLAN: Total No_ of Classes: 06 S.No Name of the Topic Reference book

code No. of classes required

22 Modeling components level design: Designing class-based components,

1,2 2

23 conducting component-level design. Object constraint language,

1,2,3 2

24 designing conventional components, Performing ,User interface design

1,2 2

25 Godlen rules, User interface analysis and design, interface analysis, interface design steps, Design evaluation.

1,3 2

26 Over view and Conclusion 1,3 1 &&&&&&&

JBIE

T

Dept o

f IT

Page: 18

OBJECTIVE QUESTIONS :

1. Which design model is equivalent to a set of detailed drawings for each room in a house?

A) Architectural design

B) Component-level design

C) Data design

D) Interface design 2.Which design model elements are used to depict a model of information represented from the user's view?

A) Architectural design elements

B) Component-level design elements

C) Data design elements

D) Interface design elements DESCRIPTIVE QUESTIONS : 1.Explain Golden rules in User interface design. 2.Briefly explain Design evaluation in Modeling component-level design. ASSIGNMENT QUESTIONS: 1.Write short notes on User interface analysis and design. 2.How the Golden rules are useful in User interface Design. &&&&&&&&

JBIE

T

Dept o

f IT

Page: 19

UNIT-VI: Testing Strategies LECTURE PLAN: Total No_ of Classes: 06 S.No Name of the Topic Reference

book code No. of Lecture classes required

27 Testing Strategies: Astrategic approach to software testing, test strategies for conventional software ,

1 2

28 Black-box and White-box testing, Validation testing, System testing, the art of Debugging.

1 2

29 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.

1 2

JBIE

T

Dept o

f IT

Page: 20

OBJECTIVE QUESTIONS : 1) What are the Testing Levels? a) Unit Testing b) Integration Testing c) System Testing and Acceptance Testing. d) All the above answer:d 2) Executing the same test case by giving the number of inputs on same build called as a) Regression Testing b) ReTesting c) Ad hoc Testing d) Sanity Testing answer: b 3) Control Charts is a statistical technique to assess, monitor, and maintain the stability of a process. a) True b) False answer:a 4) To check whether we are developing the right product according to the customer requirements are not. It is a static process a) Validation b) Verification c) Quality Assurance d) Quality Control answer: b DESCRIPTIVE QUESTIONS : 1.Explain about test strategies for conventional software. 2.what is the difference between product measurements and metrics? ASSIGNMENT QUESTIONS: 1. How can you explain about the Metrics for maintenance. 2. Give some Metrics for source code. &&&&&&&&&

JBIE

T

Dept o

f IT

Page: 21

UNIT-VII: Metrics for Process and Products LECTURE PLAN: Total No_ of Classes: 08

S.No Name of the Topic Reference book code

No. of classes required

30 Metrics for Process and Products: Software Measurement, Metrics for software quality.

1,3 1

31 Risk management: Reactive vs proactive Risk strategies,

1,3 2

32 software risks, Risk identification, Risk projection,

1,3 2

33 Risk refinement, RMMM,RMMM Plan.

1,3 2

34 Overview

1 1

35 Conclusion 1 1

JBIE

T

Dept o

f IT

Page: 22

OBJECTIVE QUESTIONS : 1.It measures the quality of a product It is a specific part of the QA procedure, It is a corrective process, It applies for particular product & Deals with the product. a) Validation b) Verification c) Quality Assurance d) Quality Control answer: d 2. A metric used to measure the characteristic of documentation and code called as a) Process metric b) Product Metric c) Test metrics answer: b 3.An Important metric is the number of defects found in internal testing compared to the defects found in customer tests, Status of test activities against the plan, Test coverage achieved so far, comes under a) Process Metric b) Product Metric c) Test Metric answer:c DESCRIPTIVE QUESTIONS : 1. Discuss about software tools for test case design 2. How should we use metrics during the project itself 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. &&&&&&&

JBIE

T

Dept o

f IT

Page: 23

UNITVIII: Quality Management LECTURE PLAN: Total No_ of Classes: 09 S.No Name of the Topic Reference

book code No. of classes required

36 Quality M anagement: Quality concepts, Software quality assurance,

1,2,3 2

37 Software Reviews, Formal technical reviews,

1 2

38 Statistical Software quality Assurance, Software reliability,

1 1

39 The ISO 9000 quality standards. 1,2 2 40 Overview and Conclusion 1,2 2

JBIE

T

Dept o

f IT

Page: 24

OBJECTIVE QUESTIONS : 1.Cost of quality = Prevention Cost + Appraisal cost + Failure cost a) True b) False answer: a 2. It measures the quality of a product It is a specific part of the QA procedure, It is a corrective process, It applies for particular product & Deals with the product. a) Validation b) Verification c) Quality Assurance d) Quality Control answer: d 3.SPICE Means a) Software Process Improvement and Capability Determination b) Software Process Improvement and Compatibility Determination. c) Software Process Invention and Compatibility Determination. d) Software Process Improvement and Control Determinatio answer: a DESCRIPTIVE QUESTIONS : 1. Is it possible asses the quality of software if the customer keeps changing? 2. Can a program be correct and still not exhibit good quality? Explain. 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? &&&&&&&&&&

JBIE

T

Dept o

f IT

Page: 25

DEPARTMENT OF INFORMATION TECHNOLOGY INDIVIDUAL TIME TABLE NAME OF THE FACULTY: Nalinakshi M

Period 1 2 3 4 5 6 7 Day/Ti

me 9.00-9.50 9.50-10.40 10.40-11.30 11.30-12.20 L

U N C H

12.50-1.40 1.40-2.30 2.30-3.20

Mon Tue Wed Thu Fri Sat

Software Engineering(SE): Total no of theory classes : 10 Total no of practical classes : 12 Total no of classes : 22

JBIE

T

Dept o

f IT

Page: 26

J. B. Institute of Engineering & Technology II B.Tech -2009-Batch/I SEM (Sample I-MID DESCRIPTIVE)

BRANCH: INFORMATION TECHNOLOGY SUB: Computer Networks

TIME: 60 MINUTES Marks: 10

SECTION-A Answer any TWO of the following: (2x5=20M)

1. (a) Discuss various management myths and realities. (b) Elaborate on software crisis.

2. (a) What is water fall model? How is it different from other engineering process models? (b) Explain various types of evolutionary development.

3. Using your own knowledge of how an ATM is used, develop a set of use-cases that could be used to derive the requirements for an ATM system.

4. (a) Illustrate about component level design elements in detail. (b) What is deployment diagram? Draw a deployment diagram for Safe Home system in UML.

&&&&&&&&&&

JBIE

T

Dept o

f IT

Page: 27

J. B.Institue of Engineering & Techology II B.Tech -2009-Batch/I SEM (Sample I-MID DESCRIPTIVE)

BRANCH: INFORMATION TECHNOLOGY SUB: Software Engineering

TIME: 90 MINUTES Marks: 10

SECTION-A Answer any TWO of the following: (2x5=20M)

1.(a) What is meant by User Interface? What are the three areas that user interface design focuses? Explain them. (b) Discuss the importance of user interface design? [10+6]

2. (a) What is meant by Validation testing? Discuss the validation test criteria. (b) Explain clearly the Alpha and Beta testing. (c) What is meant by configuration review?

3.(a) Discuss clearly how to asses overall project risk? (b) Discuss about risk components and drivers. [10+6]

4. (a) Is it possible asses the quality of software if the customer keeps changing?What it is supposed to do? (b) Can a program be correct and still not exhibit good quality? Explain.

&&&&&&&&&

JBIE

T

Dept o

f IT

Page: 28

Marks for Internal Theory Examination

********************************THE END*************************************

ROLL.NO NAME OF THE STUDENT I MID (Des+Obj+Assign))

II MID Des+Obj+Assign))

JBIE

T

Dept o

f IT