Applying use cases : a practical guide
著者
書誌事項
Applying use cases : a practical guide
(The Addison-Wesley object technology series / Grady Booch, Ivan Jacobson, James Rumbaugh)
Addison-Wesley, c1998
大学図書館所蔵 全7件
  青森
  岩手
  宮城
  秋田
  山形
  福島
  茨城
  栃木
  群馬
  埼玉
  千葉
  東京
  神奈川
  新潟
  富山
  石川
  福井
  山梨
  長野
  岐阜
  静岡
  愛知
  三重
  滋賀
  京都
  大阪
  兵庫
  奈良
  和歌山
  鳥取
  島根
  岡山
  広島
  山口
  徳島
  香川
  愛媛
  高知
  福岡
  佐賀
  長崎
  熊本
  大分
  宮崎
  鹿児島
  沖縄
  韓国
  中国
  タイ
  イギリス
  ドイツ
  スイス
  フランス
  ベルギー
  オランダ
  スウェーデン
  ノルウェー
  アメリカ
注記
Includes bibliographical references (p. 169-171) and index
内容説明・目次
内容説明
Many projects struggle to define the specific functions of software, and end users often find that the final product does not perform as expected. Use cases allow analysts to identify the required features of a software system based on how each end user will use the system. This efficient and straightforward analysis process gives end users direct input into the design of the system that will serve them. Applying Use Cases provides a practical and clear introduction to developing use cases, demonstrating their use via a continuing case study. Using the Unified Software Development Process as a framework and the Unified Modeling Language (UML) as a notation, the authors step the reader through applying use cases in the different phases of the process, focusing on where and how use cases are best applied.Other highlights include: *A collection of realistic examples showing how to apply use cases, drawn from the authors' extensive experience in this area *A case study that offers insight into the common mistakes and pitfalls that can plague an object-oriented project *An illustration of the latest version of the UML notation for diagramming use cases *A practical "how-to" discussion on applying use cases to identify system requirements 0201309815B04062001
目次
(All chapters, except 7 and 9, conclude with a Chapter Review.)
Foreword.
Preface.
Acknowledgments.
1. Getting Started.
An Iterative Software Process.
An Example Project.
The Project Description.
Starting Risk Analysis.
2. Identifying System Boundaries.
Identifying Actors.
Identifying Use Cases.
Describing Actors and Use Cases.
Handling Time.
Potential Boundary Problems.
Scoping the Project.
3. Primary Scenarios.
The Complete Use Case.
Handling Complex Use Cases.
Scenarios.
The Primary Scenario.
Guidelines for Correctness and Completeness.
Other Requirements.
Presentation Styles.
4. Secondary Scenarios.
Finding Secondary Scenarios.
Detailing Significant Behavior.
Use Case Description Revisited.
5. Diagramming Use Cases.
Activity Diagrams.
Diagramming the User Interface.
6. Dividing Large Systems.
Architectural Patterns.
Testing the Architecture with Use Cases.
Defining Interfaces Between Subsystems.
Allocating Use Cases to Subsystems.
Creating Subsystem Documentation.
7. Documenting Use Cases.
Documentation Templates.
Order-Processing System Use Cases.
Order Processing System.
System Level Use Cases.
8. Use Cases and the Project Plan.
Planning the Project.
Estimating Work with Use Cases.
9. Reviews.
Review for Completeness.
Review for Potential Problems.
Review with End Users.
Review with Customers.
Review with Development.
Reviewers.
Adding Flexibility to Your System.
10. Constructing and Delivering a System.
Key Abstractions of the Domain.
The Iteration Schedule.
Delivery and Beyond.
Final Wrap-Up.
Appendix A. Resource List.
Appendix B. Documentation Templates.
System or Subsystem Documents.
Use Case Document.
Scenario Document.
Appendix C. UML Notation Used in This Book.
Appendix D. Reply Form for the Use Case Estimator.
Index.
「Nielsen BookData」 より