Software Engineering

When computer software succeeds- when it meets the needs of the people who use it,when it performs flawlessly over a long period of time,when it is easy to modify and even easier to use- it can change things for the better.But when software fails-when users are dissatisfied,when it is error prone,when it is difficult to change and even harder to use-bad things can and do happen.We all want to build software that makes things better,avoiding the bad things that lurk in the shadow of failed efforts.To succeed,we need discipline when software is designed and built.We need an engineering approach.

Sunday, January 16, 2011

Chapter 1

Software and Software Engineering

Chapter 2

Process: A Generic View

Chapter 3

Process Models

Chapter 5

Practice: A Generic View

Chapters 6-7

System Engineering

Chapter 8

Analysis Engineering

Chapter 9

Design Engineering

Chapter 10

Architectural Design

Chapter 11

Component Level Design

Chapter 12

User Interface Design

Chapters 13-14

Software Testing Strategies
Software Testing Techniques

Chapter 15

Product Metrics

Chapter 16

Web Engineering

Chapter 17

Formulating and Planning for Web Engineering

Chapter 19

Design Modelling for WebApps

Chapters 21-23

Managing Software Projects:
Chapters Covered:
Project Management
Metrics for Process and Projects
Estimation

Chapters 24-25

Chapters Covered:
Project Scheduling
Risk Management

Chapters 26-27

Chapters Covered:
Quality Management
Change Management

Chapters 28-32

Chapters Covered:
Formal Methods,
Cleanroom Software Engineering,
Component Based Development,
Reengineering
The Road Ahead