gogogo
Syndetics cover image
Image from Syndetics

Open modeling with UML Brian Henderson-Sellers and Bhuvan Unhelkar [foreword by Richard Soley]

By: Contributor(s): Material type: TextTextPublication details: Harlow, England New York Addison-Wesley 2000Description: xx, 245 p. ill. 24 cmISBN:
  • 0201675129
Subject(s): DDC classification:
  • 005.117 HEN
Holdings
Item type Current library Call number Copy number Status Date due Barcode
Standard Loan Moylish Library Main Collection 005.117 HEN (Browse shelf(Opens below)) 1 Available 39002000193319

Enhanced descriptions from Syndetics:

Aimed at modellers and developers, this book focuses on the specific activity of modelling the software development process using OPEN principles and the UML notation. An accompanying CD-ROM provides a demo CASE tool, which can be used to practice the exercises in the text.

Includes bibliographical references (p. [231]-232) and index

Table of contents provided by Syndetics

  • Foreword (p. xi)
  • Preface (p. xiii)
  • List of acronyms (p. xix)
  • 1 Introduction to OPEN (p. 1)
  • Abstract (p. 1)
  • 1.1 What is OPEN? (p. 1)
  • 1.2 Why is OPEN a tailorable process framework? (p. 8)
  • 1.3 What is UML? (p. 16)
  • 1.4 Tying it all together: OPEN with UML (p. 18)
  • Summary of key points (p. 19)
  • Discussion topics (p. 20)
  • Notes (p. 20)
  • 2 The modeling language to be used: UML (p. 21)
  • Abstract (p. 21)
  • 2.1 History of UML (p. 21)
  • 2.2 Static architectural elements (p. 25)
  • 2.3 Architectural diagram types (p. 30)
  • 2.4 Stereotypes (p. 33)
  • 2.5 Relationships (p. 36)
  • 2.5.1 Notation (p. 39)
  • 2.5.2 Further uses of associations (p. 41)
  • 2.6 Use cases (p. 43)
  • 2.7 Interaction diagrams (p. 48)
  • 2.8 Statechart diagrams (p. 50)
  • Summary of key points (p. 51)
  • Discussion topics (p. 51)
  • Bibliographic notes (p. 52)
  • 3 OPEN's Modeling Tasks and Techniques explained (p. 53)
  • Abstract (p. 53)
  • 3.1 Introduction (p. 53)
  • 3.2 Object identification and documentation (p. 57)
  • 3.3 Responsibilities (p. 65)
  • 3.4 Collaborations and patterns (p. 68)
  • 3.5 CRC card modeling (p. 73)
  • 3.6 Services (p. 75)
  • 3.7 Associations (p. 78)
  • 3.8 Whole-part relationship (p. 80)
  • 3.9 Assertions and contracts (p. 85)
  • 3.10 'Inheritance' (p. 87)
  • 3.11 Roles (p. 92)
  • 3.12 States (p. 95)
  • 3.13 Use cases (p. 96)
  • 3.14 Implementation (p. 108)
  • 3.15 Inspections and reviews (p. 110)
  • 3.15.1 VandV (p. 110)
  • 3.15.2 Reviews (p. 112)
  • 3.15.3 Quality (p. 112)
  • Summary of key points (p. 113)
  • Discussion topics (p. 113)
  • Bibliographic notes (p. 114)
  • 4 Case Study 1: Library Management (p. 115)
  • Abstract (p. 115)
  • 4.1 Scope of case study (p. 115)
  • 4.2 Project planning (p. 118)
  • 4.3 Build (p. 121)
  • 4.4 Modeling and implementation: OOA/D/P (p. 122)
  • 4.5 VandV (p. 138)
  • 4.6 User review (p. 139)
  • 4.7 Consolidation (p. 140)
  • 4.8 Evaluation (p. 140)
  • Summary of key points (p. 141)
  • 5 Case Study 2: Small Business Loans System-a use case study for the Web (p. 143)
  • Abstract (p. 143)
  • 5.1 Scope of the case study (p. 143)
  • 5.2 The OPEN process in practice (p. 145)
  • 5.3 The problem statement (p. 146)
  • 5.4 The subsystems of BLS (p. 149)
  • 5.4.1 Customer Information Subsystem (CISS) (p. 152)
  • 5.4.2 Security Asset Subsystem (SASS) (p. 152)
  • 5.4.3 Loan Approvals Subsystem (LASS) (p. 153)
  • 5.5 Tailoring the OPEN lifecycle (p. 154)
  • 5.5.1 The Activity-Task mapping (p. 157)
  • 5.5.2 Activity: Project initiation (p. 157)
  • 5.5.3 Activity: Requirements Engineering (p. 159)
  • 5.5.4 Activity: Project planning (p. 160)
  • 5.5.5 Activity: Analysis and business model refinement (p. 162)
  • 5.5.6 Activity: Build (p. 164)
  • 5.5.7 Activity: Evaluation (p. 165)
  • 5.5.8 Activity: Deployment (p. 165)
  • 5.5.9 Activity: Architecture (p. 166)
  • 5.5.10 The Task-Technique mapping (p. 168)
  • 5.5.11 A mini project plan (p. 169)
  • 5.6 Activity: Requirements Engineering (p. 172)
  • 5.6.1 A useful view of use cases (p. 173)
  • 5.6.2 Actors for the BLS (p. 176)
  • 5.6.3 Use case diagrams for the BLS (p. 183)
  • 5.6.4 Sample use case documentation (p. 189)
  • 5.7 Activity: Analysis and business model refinement (p. 196)
  • 5.7.1 Business Object Model (BOM) (p. 196)
  • 5.7.2 Business object definitions (p. 198)
  • 5.7.3 Class diagram for Customer Information Subsystem (p. 209)
  • 5.7.4 Class diagram for Security Assets Subsystem (p. 211)
  • 5.7.5 Class diagram for Loan Applications Subsystem (p. 213)
  • 5.7.6 Class diagram for Business Loan System (p. 214)
  • 5.7.7 Sequence diagram for applying for small business loan (p. 215)
  • 5.7.8 Sequence diagram for loan tracking by the small business borrower using the Internet (p. 217)
  • 5.7.9 Statechart diagram showing some states of LoanAccount (p. 218)
  • 5.8 User interface specification (Activity: Requirements Engineering) (p. 220)
  • 5.8.1 User interface-aspects (p. 221)
  • 5.8.2 U1010_Loan_Application_Form (p. 221)
  • 5.8.3 U1320_Web-Loan_Tracker (p. 222)
  • 5.9 Testing (Activity: evaluation) (p. 223)
  • 5.9.1 Test planning (p. 223)
  • 5.9.2 Testing architecture (p. 224)
  • 5.9.3 Testing approaches (p. 225)
  • 5.9.4 Risks in testing (p. 226)
  • Summary of key points (p. 227)
  • References (p. 229)
  • Bibliography (p. 231)
  • Appendix OPEN in a process tool (p. 233)
  • Index (p. 239)

Author notes provided by Syndetics

Brian Henderson-Sellers is Director of the Centre for Object Technology Applications and Research and Professor of Information Systems at the University of Technology, Sydney (UTS).

Powered by Koha