An integrated approach to software engineering/ (Record no. 1987)
[ view plain ]
| 000 -LEADER | |
|---|---|
| fixed length control field | 07513cam a22001934a 4500 |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| International Standard Book Number | 9788173197024 |
| 040 ## - CATALOGING SOURCE | |
| Transcribing agency | CUS |
| 082 00 - DEWEY DECIMAL CLASSIFICATION NUMBER | |
| Classification number | 005.1 |
| Item number | JAL/I |
| 100 ## - MAIN ENTRY--PERSONAL NAME | |
| Personal name | Jalote, Pankaj |
| 245 13 - TITLE STATEMENT | |
| Title | An integrated approach to software engineering/ |
| Statement of responsibility, etc. | Pankaj Jalote. |
| 250 ## - EDITION STATEMENT | |
| Edition statement | 3rd ed. |
| 260 ## - PUBLICATION, DISTRIBUTION, ETC. (IMPRINT) | |
| Place of publication, distribution, etc. | New York : |
| Name of publisher, distributor, etc. | Springer, |
| Date of publication, distribution, etc. | 2005. |
| 300 ## - PHYSICAL DESCRIPTION | |
| Extent | xiv, 495 p. : |
| Other physical details | ill. ; |
| Dimensions | 24 cm. |
| 440 #0 - SERIES | |
| Title | Texts in computer science |
| 504 ## - BIBLIOGRAPHY, ETC. NOTE | |
| Bibliography, etc | Includes bibliographical references and index. |
| 505 ## - FORMATTED CONTENTS NOTE | |
| Formatted contents note | 1.1 The Problem Domain --1.1.1 Industrial Strength Software --1.1.2 Software is Expensive -- 1.1.3 Late and Unreliable --1.1.4 Maintenance and Rework --1.2 The Software Engineering Challenges --1.2.1 Scale -- 1.2.2 Quality and Productivity -- 1.2.3 Consistency and Repeatability -- 1.2.4 Change -- 1.3 The Software Engineering Approach -- 1.3.1 Phased Development Process -- 1.3.2 Managing the Process -- 1.4 Summary -- Exercises Software Processes -- 2.1 Software Process -- 2.1.1 Processes and Process Models --2.1.2 Component Software Processes -- 2.1.3 ETVX Approach for Process Specification -- 2.2 , Desired Characteristics of Software Process -- 2.2.1 Predictability -- 2.2.2 Support Testability and Maintainability -- 2.2.3 Support Change -- 2.2.4 Early Defect Removal-- 2.5.5 Process Improvement and Feedback -- 2.3 Software Development Process Models -- 2.3.1 Waterfall Model -- 2.3.2 Prototyping -- 2.3.3 Iterative Development -- 2.3.4 Timeboxing Model -- 2.3.5 Comparision of Models-- 2.4 Other Software Processes -- 2.4.1 Project Management Process-- 2.4.2 The Inspection Process -- 2.4.3 Software Configuration Management Process -- 2.4.4 Requirements Change Management Process .-- 2.4.5 Process Management Process -- 2.5 Smnmary-- Exercises-- Software Requirements Analysis and Specification-- 3.1 Software Requirements -- 3.1.1 Need for SRS -- 3.1.2 Requirement Process -- 3.2 Problem Analysis -- 3.2.1 Informal Approach -- 3.2.2 Data Flow Modeling-- 3.2.3 Object-Oriented Modeling -- 3.2.4 Prototyping-- 3.3 Requirements Specification -- 3.3.1 Characteristics of an SRS-- 3.3.2 Components of an SRS -- 3.3.3 Specification Language -- 3.3.4 Structure of a Requirements Document -- 3.4 Functional Specification with Use Cases-- 3.4.1 Basics -- 3.4.2 Examples -- 3.4.3 Extensions-- 3.4.4 Developing Use Cases-- 3.5 Validation -- 3.6 Metrics-- 3.6.1 Size—Function Points-- 3.6.2 Quality Metrics-- 3.7 Summary-- Exercises -- Case Studies-- Software Architecture-- 4.1 Role of Software Architecture-- 4.2 Architecture Views--4.3 Component and Connector View -- 4.3.1 Components .-- 4.3.2 Connectors-- 4.3.3 An Example-- 4.4 Architecture Styles for C&C View-- 4.4.1 Pipe and Filter-- 4.4.2 Shared-Data Style--- 4.4.3 Client-Server Style-- 4.4.4 Some Other Styles-- 4.5 Discussion-- 4.5.1 Architecture and Design-- 4.5.2 Preserving the Integrity of an Architecture-- 4.5.3 Deployment View and Performance Analysis-- 4.5.4 Documenting -- Architecture Design-- 4.6 Evaluating Architectures-- 4.6.1 The ATAM Analysis Method-- 4.6.2 An Example-- 4.7 Sununary-- Exercises .-- Case Studies-- Planning a Software Project-- 5.1 Process Planning .-- 5.2 Effort Estimation-- 5.2.1 Uncertainties in EflFort Estimation-- 5.2.2 Building Effort Estimation Models-- 5.2.3 A Bottom-Up Estimation Approach-- 5.2.4 COCOMO Model-- 5.3 Project Scheduling and Staffing-- 5.3.1 Overall Scheduling-- 5.3.2 Detailed Scheduling .-- 5.3.3 An Example-- 5.3.4 Team Structure-- 5.4 Software Configuration Management Plan-- 5.5 Quality Plan-- 5.5.1 Defect Injection and Removal Cycle-- 5.5.2 Approaches to Quality Management . . .-- 5.5.3 Quality Plan-- CONTENT-- Risk Management-- 5.6.1 Risk Management Concepts-- 5.6.2 Risk Assessment-- -- .6.3 Risk Control-- 5.6.4 A Practical Risk Management Approach-- Project Monitoring Plan-- 5.7.1 Measurements-- 5.7.2 Project Monitoring and Tracking -- Summary-- Exercises -- Case Studies ...-- Function-Oriented Design-- 6.1 Design Principles-- 6.1.1 Problem Partitioning and Hierarchy-- 6.1.2 -- bstraction -- 6.1.3 Modularity-- 6 1.4 Top-Down and Bottom-Up Strategies-- Module-Level Concepts-- 6.2.1 Coupling-- 6.2.2 Cohesion-- Design Notation and Specification -- 6.3.1 Structure Charts-- 6.3.2 Specification-- Structured Design Methodology -- 6.4.1 Rotate the Problem as a Data Flow Diagram-- KFirrssttf -Lev el Factoring Output-- Branches-- Analysis-- Discussion-- Verification-- Metrics-- 6.6.1 Network Metrics-- 6.2 Stability Metrics-- 6.6.3 Information Flow Metrics-- Summary-- Exercises-- Case Studies-- Object-Oriented Design-- 7.1 00 Analysis and 00 Design-- 7.2 00 Concepts-- 7.2.1 Classes and Objects-- 7.2.2 Relationships Among Objects -- 7.2.3 Inheritance and Polymorphism-- 7.3 Design Concepts-- 7.3.1 Coupling-- 7.3.2 Cohesion-- 7.3.3 The Open-Closed Principle -- 7.3.4 Some Design Guidelines -- 7.4 Unified Modeling Language (UML)-- 7.4.1 Class Diagram •.-- 7.4.2 Sequence and Collaboration Diagrams-- -7.4.3 Other Diagrams and Capabilities -- 7.5 A Design Methodology-- 7.5.1 Dynamic Modeling-- 7.5.2 Functional Modeling-- 7.5.3 Defining Internal Classes and Operations-- 7.5.4 Optimize and Package -- 7.5.5 Examples-- 7.6 Metrics -- 7.7 Summary -- Exercises -- Case Studies-- 8 Detailed Design-- 8.1 Detailed Design and PDL-- 8.1.1 PDL-- 8.1.2 Logic/Algorithm Design -- 8.1.3 State Modeling of Classes-- 8.2 Verification .-- 8.2.1 Design Walkthroughs.-- 8.2.2 Critical Design Review -- ,8.2.3 Consistency Checkers-- 8.3 Metrics-- 8.3.1 Cyclomatic Complexity-- 8.3.2 Data Bindings -- 8.3.3 Cohesion Metric -- 8.4 Summary-- Exercises-- 9 Coding-- 9.1 Programming Principles and Guidelines-- 9.1.1 Common Coding Errors-- 9.1.2 Structured Programming -- 9.1.3 Information Hiding-- 9.1.4 Some Prograpiming Practices-- 9.1.5 Coding Standards-- 9.2 Coding Process-- 9.2.1 An Incremental Coding Process-- 9.2.2 Test Driven Development-- 9.2.3 Pair Programming-- 9.2.4 Source Code Control and Build-- 9.3 Refactoring-- 9.3.1 Basic Concepts-- 9.3.2 An example-- 3.3 Bad Smells -- 9.3.4 Common Refactorings-- 9.4 -- Verification-- 9.4.1 Code Inspections ,-- 9.4.2 Static Analysis-- 9.4.3 PrpVing Correctness-- 9.4.4 Unit Testing-- 9.4.5 Combining Different Techniques-- 9.5 Metrics-- 9.5.1 Size Measures-- 9.5.2 - Complexity Metrics-- 9.6 Summary-- Exercises .-- Case Studies-- 10 Testing-- 10.1 Testing Fundamentals-- 10.1.1 Error, Fault, and Failure -- 10.1.2 Test Oracles -- 10.1.3 Test Cases and Test Criteria .-- 10.1.4 Psychology of Testing -- 10.2 Black-Box Testing-- 10.2.1 Eqtiivalence Class Partitioning-- 10.2.2 Boundary Value Analysis-- 10.2.3 Cause-Effect Graphing-- 10.2.4 Pair-wise Testing-- 10.2.5 Special Cases-- 10.2.6 State-Based Testing-- 10.3 White-Box Testing-- 10.3.1 Control Flow-Based Criteria-- 10.3.2 Data Flow-Based Testing-- 10.3.3 An Example-- 10.3.4 Mutation Testing-- 10.3.5 Test Case Generation and Tool Support-- 10.4 Testing Process-- 10.4.1 Levels of Testing-- 10.4.2 Test Plan-- 10.4.3 Test Case Specifications -- 10.4.4 Test Case Execution and Analysis -- 10.4.5 Defect Logging and Tracking-- 10.5 Defect Analysis and Prevention-- 10.5.1 Pareto Analysis-- 10.5.2 Perform Causal Analysis-- 10.5.3 Develop and Implement Solutions -- 10.6 Metrics—Reliability Estimation-- 10.6.1 Basic Concepts and Definitionsn-- 10.6.2 A Reliability Model -- 10.6.3 Failure Data and Parameter Estimation-- 10.6.4 TVanslating to Calendar Time-- 10.6.5 An Example-- 10.7 Summary-- Exercises-- Case Studies |
| 650 #0 - SUBJECT | |
| Keyword | Software engineering. |
| 942 ## - ADDED ENTRY ELEMENTS (KOHA) | |
| Koha item type | General Books |
| Withdrawn status | Lost status | Damaged status | Not for loan | Home library | Current library | Shelving location | Date acquired | Full call number | Accession number | Date last seen | Date last checked out | Koha item type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Central Library, Sikkim University | Central Library, Sikkim University | General Book Section | 02/06/2016 | 005.1 JAL/I | P33289 | 14/07/2018 | 14/07/2018 | General Books | ||||
| Central Library, Sikkim University | Central Library, Sikkim University | General Book Section | 02/06/2016 | 005.1 JAL/I | P20677 | 14/07/2018 | 14/07/2018 | General Books | ||||
| Central Library, Sikkim University | Central Library, Sikkim University | General Book Section | 02/06/2016 | 005.1 JAL/I | P33290 | 15/06/2023 | 17/05/2023 | General Books | ||||
| Central Library, Sikkim University | Central Library, Sikkim University | General Book Section | 02/06/2016 | 005.1 JAL/I | P24448 | 14/07/2018 | 14/07/2018 | General Books | ||||
| Central Library, Sikkim University | Central Library, Sikkim University | General Book Section | 02/06/2016 | 005.1 JAL/I | P33287 | 14/07/2018 | 14/07/2018 | General Books | ||||
| Central Library, Sikkim University | Central Library, Sikkim University | General Book Section | 02/06/2016 | 005.1 JAL/I | P33288 | 14/07/2018 | 14/07/2018 | General Books |