Data Communications and Networking (Record no. 1629)
[ view plain ]
000 -LEADER | |
---|---|
fixed length control field | 07534nam a22001577a 4500 |
020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
International Standard Book Number | 9781259064753 |
040 ## - CATALOGING SOURCE | |
Transcribing agency | CUS |
082 ## - DEWEY DECIMAL CLASSIFICATION NUMBER | |
Classification number | 004.6 |
Item number | FOR/D |
100 ## - MAIN ENTRY--PERSONAL NAME | |
Personal name | Forouzan, Behrouz A. |
245 ## - TITLE STATEMENT | |
Title | Data Communications and Networking |
Statement of responsibility, etc. | Behrouz A.Forouzan |
250 ## - EDITION STATEMENT | |
Edition statement | 5th ed. |
260 ## - PUBLICATION, DISTRIBUTION, ETC. (IMPRINT) | |
Place of publication, distribution, etc. | New Delhi |
Name of publisher, distributor, etc. | Mcgraw Hill education |
Date of publication, distribution, etc. | 2013 |
300 ## - PHYSICAL DESCRIPTION | |
Extent | 1226p. ill. : |
505 ## - FORMATTED CONTENTS NOTE | |
Formatted contents note | 1.1 The Problem Domain<br/>1.1.1 Industrial Strength Software<br/>1.1.2 Software is Expensive<br/>1.1.3 Late and Unreliable .<br/>1.1.4 Maintenance and Rework<br/>1.2 The Software Engineering Challenges<br/>1.2.1 Scale .<br/>1.2.2 Quality and Productivity<br/>1.2.3 Consistency and Repeatability<br/>1.2.4 Change<br/>1.3 The Software Engineering Approach<br/>1.3.1 Phased Development Process<br/>1.3.2 Managing the Process<br/>1.4 Summary<br/>Exercises<br/>Software Processes<br/>2.1 Software Process<br/>2.1.1 Processes and Process Models<br/>2.1.2 Component Software Processes .<br/>2.1.3 ETVX Approach for Process Specification<br/>2.2 , Desired Characteristics of Software Process . . .<br/>2.2.1 Predictability<br/>2.2.2 Support Testability and Maintainability .<br/>2.2.3 Support Change . . .<br/>2.2.4 Early Defect Removal<br/>2.5.5 Process Improvement and Feedback<br/>2.3 Software Development Process Models .<br/>Vll<br/>UUJVi<br/>2.3.1 Waterfall Model ... .<br/>2.3.2 Prototyping ...... .<br/>2.3.3 Iterative Development .<br/>2.3.4 Timeboxing Model . .<br/>2.3.5 Comparision of Models<br/>2.4 Other Software Processes . .<br/>2.4.1 Project Management Process<br/>2.4.2 The Inspection Process . . .<br/>2.4.3 Software Configuration Management Process<br/>2.4.4 Requirements Change Management Process .<br/>2.4.5 Process Management Process<br/>2.5 Smnmary<br/>Exercises<br/>Software Requirements Analysis and Specification<br/>3.1 Software Requirements . . .<br/>3.1.1 Need for SRS . . . .<br/>3.1.2 Requirement Process<br/>3.2 Problem Analysis<br/>3.2.1 Informal Approach .<br/>3.2.2 Data Flow Modeling<br/>3.2.3 Object-Oriented Modeling<br/>3.2.4 Prototyping<br/>3.3 Requirements Specification . . .<br/>3.3.1 Characteristics of an SRS<br/>3.3.2 Components of an SRS .<br/>3.3.3 Specification Language . .<br/>3.3.4 Structure of a Requirements Document<br/>3.4 Functional Specification with Use Cases<br/>3.4.1 Basics . .. .<br/>3.4.2 Examples . .<br/>3.4.3 Extensions<br/>3.4.4 Developing Use Cases<br/>3.5 Validation .<br/>3.6 Metrics . .<br/>3.6.1 Size—Function Points<br/>3.6.2 Quality Metrics .. ..<br/>3.7 Summary . .<br/>Exercises . •<br/>Case Studies<br/>Software Architecture<br/>4.1 Role of Software Architecture<br/>4.2 Architecture Views<br/>4.3 Component and Connector View<br/>4.3.1 Components .<br/>4.3.2 Connectors<br/>4.3.3 An Example<br/>4.4 Architecture Styles for C&C View<br/>4.4.1 Pipe and Filter<br/>4.4.2 Shared-Data Style-<br/>4.4.3 Client-Server Style . ,<br/>4.4.4 Some Other Styles<br/>4.5 Discussion<br/>4.5.1 Architecture and Design<br/>4.5.2 Preserving the Integrity of an Architecture<br/>4.5.3 Deployment View and Performance Analysis<br/>4.5.4 Documenting Architecture Design<br/>4.6 Evaluating Architectures<br/>4.6.1 The ATAM Analysis Method<br/>4.6.2 An Example<br/>4.7 Sununary<br/>Exercises .<br/>Case Studies<br/>Planning a Software Project<br/>5.1 Process Planning .<br/>5.2 Effort Estimation<br/>5.2.1 Uncertainties in EflFort Estimation<br/>5.2.2 Building Effort Estimation Models<br/>5.2.3 A Bottom-Up Estimation Approach<br/>5.2.4 COCOMO Model<br/>5.3 Project Scheduling and Staffing<br/>5.3.1 Overall Scheduling<br/>5.3.2 Detailed Scheduling .<br/>5.3.3 An Example<br/>5.3.4 Team Structure<br/>5.4 Software Configuration Management Plan<br/>5.5 Quality Plan<br/>5.5.1 Defect Injection and Removal Cycle<br/>5.5.2 Approaches to Quality Management . . .<br/>5.5.3 Quality Plan . .<br/>CONTEIS<br/>5.6<br/>5.7<br/>5.8<br/>Risk Management<br/>5.6.1 Risk Management Concepts<br/>5.6.2 Risk Assessment<br/>5.6.3 Risk Control<br/>5.6.4 A Practical Risk Management Approach<br/>Project Monitoring Plan<br/>5.7.1 Measurements<br/>5.7.2 Project Monitoring and Tracking . . . .<br/>Summary<br/>Exercises .<br/>Case Studies ...<br/>Function-Oriented Design<br/>6.1 Design Principles . . . .<br/>6.1.1 Problem Partitioning and Hierarchy<br/>6.1.2 Abstraction . .<br/>6.2<br/>6.3<br/>6.4<br/>6.5<br/>6.6<br/>6.1.3 Modularity<br/>6 1.4 Top-Down and Bottom-Up Strategies<br/>Module-Level Concepts<br/>6.2.1 Coupling<br/>6.2.2 Cohesion<br/>Design Notation and Specification . . . . ." i i " 6.3.1 Structure Charts<br/>6.3.2 Specification<br/>Structured Design Methodology . . . . i<br/>6.4.1 Rotate the Problem as a Data Flow Diagram<br/>KFirrssttf -Lev el Factoring Output<br/>Branches<br/>^ansaction Analysis<br/>Discussion .<br/>Verification<br/>Metrics . . ,<br/>6.6.1 Network Metrics<br/>6.4.2<br/>6.4.3<br/>6.4.4<br/>6.4.5<br/>6.4.6<br/>6.4.7<br/>Data El<br/>6<br/>ements<br/>6.7<br/>.6.2 Stability Metrics<br/>6.6.3 Infomration Flow Metrics<br/>Summary<br/>Exercises<br/>Case Studies<br/>Object-Oriented Design<br/>7.1 00 Analysis and 00 Design . . .<br/>7.2 00 Concepts<br/>7.2.1 Classes and Objects . ...<br/>7.2.2 Relationships Among Objects .<br/>7.2.3 Inheritance and Polymorphism<br/>7.3 Design Concepts<br/>7.3.1 CoupUng<br/>7.3.2 Cohesion<br/>7.3.3 The Open-Closed Principle . .<br/>7.3.4 Some Design Guidelines . ...<br/>7.4 Unified Modeling Language (UML) . .<br/>7.4.1 Class Diagram •.<br/>7.4.2 Sequence and Collaboration Diagrams<br/>7.4.3 Other Diagrams and Capabilities . . .<br/>7.5 A Design Methodology<br/>7.5.1 Dynamic Modeling<br/>7.5.2 Functional Modeling<br/>7.5.3 Defining Internal Classes and Operations<br/>7.5.4 Optimize and Package .<br/>7.5.5 Examples<br/>7.6 Metrics . ...<br/>7.7 Summary . . .<br/>Exercises . . .<br/>Case Studies .<br/>8 Detailed Design<br/>8.1 Detailed Design and PDL ...<br/>8.1.1 PDL<br/>8.1.2 Logic/Algorithm Design .<br/>8.1.3 State Modeling of Classes<br/>8.2 Verification .<br/>8.2.1 Design Walkthroughs .<br/>8.2.2 Critical Design Review .<br/>,8.2.3 Consistency Checkers .<br/>8.3 Metrics<br/>8.3.1 Cyclomatic Complexity<br/>8.3.2 Data Bindings .....<br/>8.3.3 Cohesion Metric ....<br/>8.4 Summary<br/>Exercises<br/>9 Co4ing<br/>9.1 Programming Principles and Guidelines<br/>9.1.1 Common Coding Errors ....<br/>9.1.2 Structured Programming . .<br/>9.1.3 Information Hiding<br/>9.1.4 Some Prograpiming Practices .<br/>9.1.5 Coding Standards .<br/>9.2 Coding Process<br/>9.2.1 An Incremental Coding Process<br/>9.2.2 Test Driven Development . . .<br/>9.2.3 Pair Programming<br/>9.2.4 Source Code Control and Build<br/>9.3 Refactoring<br/>9.3.1 Basic Concepts<br/>9.3.2 An example<br/>9.3.3 Bad Smells ........ .. ..<br/>9.3.4 Common Refactorings<br/>9.4 Verification<br/>9.4.1 Code Inspections ,<br/>9.4.2 Static Analysis<br/>9.4.3 PrpVing Correctness ......<br/>9.4.4 Unit Testing<br/>9.4.5 Combining Different Techniques<br/>9.5 Metrics<br/>9.5.1 Size Measures<br/>9.5.2 - Complexity Metrics<br/>9.6 Summary<br/>Exercises . . .<br/>Case Studies<br/>10 Testing<br/>10.1 Testing Fundamentals<br/>10.1.1 Error, Fault, and Failure . . . .<br/>10.1.2 Test Oracles . . . .<br/>10.1.3 Test Cases and Test Criteria .<br/>10.1.4 Psychology of Testing . . . . .<br/>10.2 Black-Box Testing<br/>10.2.1 Eqtiivalence Class Partitioning<br/>10.2.2 Boundary Value Analysis . . .<br/>10.2.3 Cause-Effect Graphing<br/>10.2.4 Pair-wise Testing . . . . . ...<br/>10.2.5 Special Cases<br/>10.2.6 State-Based Testing<br/>10.3 White-Box Testing<br/>10.3.1 Control Flow-Based Criteria<br/>10.3.2 Data Flow-Based Testing<br/>10.3.3 An Example<br/>10.3.4 Mutation Testing<br/>10.3.5 Test Case Generation and Tool Support<br/>10.4 Testing Process<br/>10.4.1 Levels of Testing<br/>10.4.2 Test Plan<br/>10.4.3 Test Case Specifications . . . ,<br/>10.4.4 Test Case Execution and Analysis . . .<br/>10.4.5 Defect Logging and Tracking<br/>10.5 Defect Analysis and Prevention<br/>10.5.1 Pareto Analysis<br/>10.5.2 Perform Causal Analysis<br/>10.5.3 Develop and Implement Solutions . . . .<br/>10.6 Metrics—Reliability Estimation<br/>10.6.1 Basic Concepts and Definitions n<br/>10.6.2 A Reliability Model<br/>10.6.3 Failure Data and Parameter Estimation<br/>10.6.4 TVanslating to Calendar Time<br/>10.6.5 An Example<br/>10.7 Summary<br/>Exercises _<br/>Case Studies |
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 | 31/05/2016 | 004.6 FOR/D | P33339 | 30/03/2023 | 25/02/2023 | General Books | ||||
Central Library, Sikkim University | Central Library, Sikkim University | General Book Section | 31/05/2016 | 004.6 FOR/D | P33340 | 27/03/2023 | 11/02/2023 | General Books | ||||
Central Library, Sikkim University | Central Library, Sikkim University | General Book Section | 31/05/2016 | 004.6 FOR/D | P33336 | 17/03/2023 | 18/02/2023 | General Books | ||||
Central Library, Sikkim University | Central Library, Sikkim University | General Book Section | 31/05/2016 | 004.6 FOR/D | P33338 | 15/03/2023 | 21/02/2023 | General Books |