About the Book

Software Engineering is finally about application of concepts to efficiently engineer good software solutions.

This book focuses on imparting to students the knowledge and skills that are needed to successfully execute a commercial project of a few person-months effort while employing proper practices and techniques. A vast majority of the projects executed in the industry today fall in this scope.

The goal of this book is to introduce to the students a limited number of concepts and practices which will achieve the following two objectives:
•Teach the student the skills needed to execute a smallish commercial project.
•Provide the students necessary conceptual background for undertaking advanced studies in software engineering, through organized courses or on their own.

This book focuses on key tasks in two dimensions - engineering and project management - and discusses concepts and techniques that can be applied to effectively execute these tasks. The book is organized in a simple manner, with one chapter for each of the key tasks in a project. For engineering, these tasks are requirements analysis and specification, architecture design, module level design, coding and unit testing, and testing. For project management, the key tasks are project planning and project monitoring and control, but both are discussed together in one chapter on project planning as even monitoring has to be planned. In addition, one chapter clearly defines the problem domain of Software Engineering, and another Chapter discusses the central concept of software process which integrates the different tasks executed in a project.

Each chapter opens with some introduction and clearly lists the chapter goals, or what the reader can expect to learn from the chapter. For the task covered in the chapter, the important concepts are first discussed, followed by a discussion of the output of the task, the desired quality properties of the output, and some practical methods and notations for performing the task. The explanations are supported by examples, and the key learnings are summarized in the end for the reader. The chapter ends with some self-assessment exercises.

Finally, the book contains a question bank at the end which lists out questions with answers from major universities.

About the Author

Pankaj Jalote has recently joined as Director of the newly created Indraprastha Institute of Information Technology (IIIT) Delhi. Prior to this, he was the Microsoft Chair Professor at the Department of Computer Science and Engineering at IIT Delhi. He was also with the Department of Computer Science and Engineering at IIT Kanpur since 1989, where he was the Head of the Department from 1998 to 2002. Earlier he was an Assistant Professor in the Department of Computer Science at the University of Maryland, where he also held joint appointment in the Institute of Advanced Computer Studies. From 1996 to 1998, he was Vice President (quality) at Infosys Technologies Ltd., a large Bangalore-based company providing software solutions worldwide, where he spearheaded Infosys' successful move to high maturity levels of the CMM. From 2003 to 2004 he was a Visiting Researcher at Microsoft Corporation, Redmond, US. Pankaj Jalote is a fellow of the IEEE and on the Board of Advisors of many software companies in India and USA, is a Technical Advisory Board member for Microsoft Research, India, and is on the Editorial Board of IEEE Transactions on Software Engineering, and International Journal of Emperical Software Engineering. His research interest is in software engineering (software quality, software process improvement, software architecture analysis), and fault tolerant systems and reliability. He is a Fellow of the IEEE. He is the Program Chair of India Software Engineering Conference, ISEC2008. Earlier, he has been general chair of IEEE's International Requirements Engineering Conference, RE07, and program chair for APSEC06. He is on the Steering Committees of India Software Engineering Conference(ISEC), International Symposium of Software Reliability (ISSRE), and the Asia Pacific Software Engineering Conference (APSEC). He is also member of the SIGSOFT extended executive committee.

Table of Contents:
Chapter 1: The Software Problem Learning Objectives 1.1 Cost, Schedule, and Quality 1.2 Scale and Change Summary Self-Assessment Exercises Chapter 2: Software Processes Learning Objectives 2.1 Process and Project 2.2 Component Software Processes 2.3 Software Development Process Models Waterfall Model Prototyping Iterative Development Rational Unified Process Timeboxing Model Extreme Programming and Agile Processes Using Process Models in a Project 2.4 Project Management Process Summary Self-Assessment Exercises Chapter 3: Software Requirements Analysis and Specification Learning Objectives 3.1 Value of a Good SRS 3.2 Requirement Process 3.3 Requirements Specification Desirable Characteristics of an SRS Components of an SRS Structure of a Requirements Document 3.4 Functional Specification with Use Cases Basics Examples Extensions Developing Use Cases 3.5 Other Approaches for Analysis Data Flow Diagrams Entity Relationship Diagrams 3.6 Validation Summary Self-Assessment Exercises Chapter 4: Software Architecture Learning Objectives 4.1 Role of Software Architecture 4.2 Architecture Views 4.3 Component and Connector View Components Connectors An Example 4.4 Architecture Styles for C&C View Pipe and Filter Shared-Data Style Client-Server Style Some Other Styles 4.5 Documenting Architecture Design 4.6 Evaluating Architectures Summary Self-Assessment Exercises Chapter 5: Planning a Software Project-4 Learning Objectives 5.1 Effort Estimation Top-Down Estimation Approach Bottom-Up Estimation Approach 5.2 Project Schedule and Staffing 5.3 Quality Planning 5.4 Risk Management Planning Risk Management Concepts Risk Assessment Risk Control A Practical Risk Management Planning Approach 5.5 Project Monitoring Plan Measurements Project Monitoring and Tracking 5.6 Detailed Scheduling Summary Self-Assessment Exercises Chapter 6: Design Learning Objectives 6.1 Design Concepts Coupling Cohesion The Open-Closed Principle 6.2 Function-Oriented Design Structure Charts Structures Design Methodology An Example 6.3 Object-Oriented Design OO Concepts Unified Modeling Language (UML) A Design Methodology Examples 6.4 Detailed Design Logic/Algorithm Design State Modeling of Classes 6.5 Verification 6.6 Metrics Complexity Metrics for Function-Oriented Design Complexity Metrics for OO Design Summary Self-Assessment Exercises Chapter 7: Coding and Unit Testing Learning Objectives 7.1 Programming Principles and Guidelines Structured Programming Information Hiding Some Programming Practices Coding Standards 7.2 Incrementally Developing Code An Incremental Coding Process Test-Driven Development Pair Programming 7.3 Managing Evolving Code Source Code Control and Build Refactoring 7.4 Unit Testing Testing Procedural Units Unit Testing of Classes 7.5 Code Inspection Planning Self-Review Group Review Meeting 7.6 Metrics Size Measures Complexity Metrics Summary Self-Assessment Exercises Chapter 8: Testing Learning Objectives 8.1 Testing Concepts Error, Fault, and Failure Test Case, test Suite, and Test Harness Psychology of Testing Levels of Testing 8.2 Testing Process Test Plan Test Case Design Test Case Execution 8.3 Black-Box Testing Equivalence Class Partitioning Boundary Value Analysis Pairwise Testing Special Cases State-Based Testing 8.4 White-Box Testing Control Flow-Based Criteria Test Case Generation and Tool Support 8.5 Metrics Coverage Analysis Reliability Defect Removal Efficiency Summary Self-Assessment Exercises Frequently Asked Questions Bibliography Index