Object-oriented Systems Analysis and Design Using UML

  • 2 Want to read

My Reading Lists:

Create a new list

  • 2 Want to read

Buy this book

Last edited by Drini
September 22, 2025 | History

Object-oriented Systems Analysis and Design Using UML

  • 2 Want to read

This edition doesn't have a description yet. Can you add one?

Publish Date
Language
English
Pages
624

Buy this book

Previews available in: English

Edition Availability
Cover of: Object-oriented Systems Analysis and Design Using UML
Object-oriented Systems Analysis and Design Using UML
July 4, 2007, McGraw Hill Higher Education
in English

Add another edition?

Book Details


First Sentence

"Information systems have played an important part in human affairs since our most distant ancestors first became capable of organized collective action."

Table of Contents

About the Authors
Page x
Preface
Page xi
Background to the Book
Page xi
Who Should Read this Book?
Page xi
Case Studies
Page xii
Exercises for Readers
Page xiii
Structure of the Book
Page xiii
Pathways through the Book
Page xiv
Transferable Skills
Page xv
Web Site and Support Materials
Page xv
Latest Version of UML
Page xv
Changes in the Third Edition
Page xvi
Acknowledgments
Page xvii
Guided Tour
Page xix
1. Information Systems-What Are They?
Page 1
1.1. Introduction
Page 1
1.2. Information Systems in Practice
Page 4
1.3. General Systems Theory
Page 5
1.4. Information and Information Systems
Page 15
1.5. Strategies for Success
Page 19
1.6. Summary
Page 23
2. Problems in Information Systems Development
Page 26
2.1. Introduction
Page 26
2.2. What Are the Problems?
Page 27
2.3. Why Things Go Wrong
Page 35
2.4. The Ethical Dimension
Page 40
2.5. Costs of Failure
Page 43
2.6. Summary
Page 44
3. Avoiding the Problems
Page 47
3.1. Introduction
Page 47
3.2. Project Lifecycles
Page 49
3.3. Managing Information Systems Development
Page 58
3.4. User Involvement
Page 59
3.5. Methodological Approaches
Page 60
3.6. Agile Approaches
Page 61
3.7. CASE
Page 62
3.8. Summary
Page 65
4. What Is Object-Orientation?
Page 68
4.1. Introduction
Page 68
4.2. Basic Concepts
Page 69
4.3. The Origins of Object-Orientation
Page 83
4.4. Object-Oriented Languages Today
Page 87
4.5. Summary
Page 88
A1. Agate Ltd Case Study - Introduction
Page 91
A1.1. Introduction to Agate
Page 91
A1.2. Existing Computer Systems
Page 92
A1.3. Business Activities in the Current System
Page 93
A1.4. Summary of Requirements
Page 94
B1. FoodCo Ltd Case Study - Introduction
Page 95
B1.1. Introduction to FoodCo
Page 95
B1.2. FoodCo Today
Page 98
B1.3. The Proposal
Page 102
5. Modelling Concepts
Page 103
5.1. Introduction
Page 103
5.2. Models and Diagrams
Page 104
5.3. Drawing Activity Diagrams
Page 113
5.4. A Development Process
Page 119
5.5. Summary
Page 126
6. Requirements Capture
Page 128
6.1. Introduction
Page 128
6.2. User Requirements
Page 128
6.3. Fact-Finding Techniques
Page 132
6.4. User Involvement
Page 141
6.5. Documenting Requirements
Page 143
6.6. Use Cases
Page 145
6.7. Requirements Capture and Modelling
Page 154
6.8. Summary
Page 155
A2. Agate Ltd Case Study - Requirements Model
Page 160
A2.1. Introduction
Page 160
A2.2. Requirements List
Page 160
A2.3. Actors and Use Cases
Page 161
A2.4. Glossary
Page 167
A2.5. Initial Architecture
Page 168
A2.6. Activities of Requirements Modelling
Page 169
7. Requirements Analysis
Page 171
7.1. Introduction
Page 171
7.2. What Must a Requirements Model Do?
Page 172
7.3. Use Case Realization
Page 173
7.4. The Class Diagram
Page 179
7.5. Drawing a Class Diagram
Page 188
7.6. CRC (Class Responsibility Collaboration) Cards
Page 204
7.7. Assembling the Analysis Class Diagram
Page 207
7.8. Summary
Page 208
A3. Agate Ltd Case Study - Requirements Analysis
Page 213
A3.1. Introduction
Page 213
A3.2. Use Case Realizations
Page 213
A3.3. Assembling the Analysis Class Diagram
Page 219
A3.4. Activities of Requirements Analysis
Page 220
8. Refining the Requirements Model
Page 222
8.1. Introduction
Page 222
8.2. Software and Specification Reuse
Page 223
8.3. Adding Further Structure
Page 230
8.4. UML Support for Modelling Components
Page 239
8.5. Software Development Patterns
Page 244
8.6. Summary
Page 246
9. Object Interaction
Page 249
9.1. Introduction
Page 249
9.2. Object Interaction and Collaboration
Page 250
9.3. Interaction Sequence Diagrams
Page 252
9.4. Communication Diagrams
Page 271
9.5. Interaction Overview Diagrams
Page 275
9.6. Timing Diagrams
Page 278
9.7. Model Consistency
Page 279
9.8. Summary
Page 280
10. Specifying Operations
Page 282
10.1. Introduction
Page 282
10.2. The Role of Operation Specifications
Page 283
10.3. Contracts
Page 284
10.4. Describing Operation Logic
Page 286
10.5. Object Constraint Language
Page 295
10.6. Creating an Operation Specification
Page 299
10.7. Summary
Page 301
11. Specifying Control
Page 303
11.1. Introduction
Page 303
11.2. States and Events
Page 304
11.3. Basic Notation
Page 306
11.4. Further Notation
Page 311
11.5. Preparing a State Machine
Page 318
11.6. Protocol and Behavioural State Machines
Page 324
11.7. Consistency Checking
Page 325
11.8. Quality Guidelines
Page 325
11.9. Summary
Page 326
A4. Agate Ltd Case Study - Further Analysis
Page 328
A4.1. Introduction
Page 328
A4.2. Sequence Diagrams
Page 329
A4.3. State Machines
Page 330
A4.4. Operation Specifications
Page 330
A4.5. Further Refinement of the Class Diagram
Page 336
A4.6. Further Activities of Requirements Analysis
Page 336
12. System Architecture
Page 338
12.1. Introduction
Page 338
12.2. What Do We Mean by Architecture?
Page 339
12.3. Why Produce Architectural Models?
Page 342
12.4. Influences on System Architecture
Page 344
12.5. Architectural Styles
Page 348
12.6. Concurrency
Page 363
12.7. Processor Allocation
Page 365
12.8. Agate Software Architecture
Page 366
12.9. Summary
Page 368
13. Systems Design
Page 371
13.1. Introduction
Page 371
13.2. How is Design Different from Analysis?
Page 372
13.3. Logical and Physical Design
Page 374
13.4. System Design
Page 376
13.5. Qualities and Objectives of Analysis and Design
Page 377
13.6. Measurable Objectives in Design
Page 386
13.7. Data Management Issues
Page 387
13.8. Development Standards
Page 388
13.9. Prioritizing Design Trade-offs
Page 389
13.10. Design for Implementation
Page 391
13.11. Summary
Page 391
14. Detailed Design
Page 394
14.1. Introduction
Page 394
14.2. What Do We Add in O-O Detailed Design?
Page 395
14.3. Class Specification
Page 397
14.4. Interfaces
Page 402
14.5. Designing Associations
Page 404
14.6. Integrity Constraints
Page 409
14.7. Designing Operations
Page 412
14.8. Summary
Page 413
15. Design Patterns
Page 415
15.1. Introduction
Page 415
15.2. Software Development Patterns
Page 416
15.3. Documenting Patterns - Pattern Templates
Page 418
15.4. Design Patterns
Page 419
15.5. How to Use Design Patterns
Page 435
15.6. Benefits and Dangers of Using Patterns
Page 436
15.7. Summary
Page 437
16. Human-Computer Interaction
Page 440
16.1. Introduction
Page 440
16.2. The User Interface
Page 441
16.3. Approaches to User Interface Design
Page 450
16.4. Standards and Legal Requirements
Page 458
16.5. Summary
Page 461
17. Designing Boundary Classes
Page 463
17.1. Introduction
Page 463
17.2. The Architecture of the Presentation Layer
Page 464
17.3. Prototyping the User Interface
Page 466
17.4. Designing Classes
Page 469
17.5. Designing Interaction with Sequence Diagrams
Page 473
17.6. The Class Diagram Revisited
Page 481
17.7. User Interface Design Patterns
Page 482
17.8. Modelling the Interface Using State Machines
Page 483
17.9. Summary
Page 491
18. Data Management Design
Page 494
18.1. Introduction
Page 494
18.2. Persistence
Page 495
18.3. File Systems
Page 498
18.4. Database Management Systems
Page 505
18.5. Designing for Relational Database Management Systems
Page 511
18.6. Designing for Object Database Management Systems
Page 519
18.7. Distributed Databases
Page 521
18.8. Designing Data Management Classes
Page 523
18.9. Summary
Page 533
A5. Agate Ltd Case Study - Design
Page 536
A5.1. Introduction
Page 536
A5.2. Architecture
Page 536
A5.3. Sample Use Case
Page 538
A5.4. Class Diagrams
Page 538
A5.5. Sequence Diagrams
Page 544
A5.6. Database Design
Page 547
A5.7. State Machines
Page 547
A5.8. Activities of Design
Page 547
19. Implementation
Page 551
19.1. Introduction
Page 551
19.2. Software Implementation
Page 552
19.3. Component Diagrams
Page 557
19.4. Deployment Diagrams
Page 558
19.5. Software Testing
Page 561
19.6. Data Conversion
Page 565
19.7. User Documentation and Training
Page 567
19.8. Implementation Strategies
Page 568
19.9. Review and Maintenance
Page 570
19.10. Summary
Page 574
20. Reusable Components
Page 577
20.1. Introduction
Page 577
20.2. Why Reuse?
Page 578
20.3. Planning a Strategy for Reuse
Page 586
20.4. Commercially Available Componentware
Page 589
20.5. Case Study Example
Page 591
20.6. Summary
Page 599
21. Software Development Processes
Page 602
21.1. Introduction
Page 602
21.2. Process, Method and Methodology
Page 603
21.3. The Unified Software Development Process
Page 607
21.4. Participatory Design
Page 611
21.5. Dynamic Systems Development Method
Page 613
21.6. extreme Programming
Page 618
21.7. Issues in Choosing a Methodology
Page 619
21.8. Hard versus Soft Methodologies
Page 621
21.9. Summary
Page 624
Appendix A - Notation Summary
Page 626
Appendix B - Selected Solutions and Answer Pointers
Page 635
Glossary
Page 648
Bibliography
Page 659
Index
Page 667

Classifications

Library of Congress
QA402, QA76.9.O35 B46 2006

Edition Identifiers

Open Library
OL7308940M
Internet Archive
objectorientedsy0000benn_i1d1
ISBN 10
0077110005
ISBN 13
9780077110000
OCLC/WorldCat
225360148
LibraryThing
3256248
Goodreads
1077819

Work Identifiers

Work ID
OL21001865W

Community Reviews (0)

No community reviews have been submitted for this work.

Lists

History

Download catalog record: RDF / JSON / OPDS | Wikipedia citation
September 22, 2025 Edited by Drini Add TOC from Tocky
December 19, 2023 Edited by ImportBot import existing book
December 7, 2022 Edited by ImportBot import existing book
June 4, 2022 Edited by ImportBot import existing book
April 29, 2008 Created by an anonymous user Imported from amazon.com record