複製鏈接
請複製以下鏈接發送給好友

編寫有效用例

鎖定
《編寫有效用例》是2002年機械工業出版社出版的圖書,作者是Cockburn。
書    名
編寫有效用例
作    者
Cockburn
出版社
機械工業出版社
出版時間
2002年7月
頁    數
270 頁
定    價
25 元
裝    幀
平裝
ISBN
9787111105374

目錄

編寫有效用例內容簡介

Highlights of the book include: A thorough discussion of the key elements;of use cases-actors. stakeholders.design scope. scenarios, and more A use case style guide with action steps and suggested formats An extensive list of time-saving use case writing tips A helpful presentation of use case templates. with commentary on when and where they should be employed A proven methodology for taking advantage of use cases With this book as your guide. you will learn the essential elements of use Case writing. Improve your use case writing skills, and be well on your way to employing use cases effectively for your next development project

編寫有效用例目錄

preface
acknowlegments
chapter 1 introduction
1.1 what is a use case (more or less)?
1.2 your use case is not my use case
steve adolph: "discovering" requirements in new territory
1.3 requirements and use cases
1.4 when use cases add value
1.5 manage your energy
1.6 warm up with a usage narrative
usage narative: getting "fast cash"
1.7 exercises
part 1 the use case body parts
chapter 2 the use case as a contract for behavior
2.1 interactions between actors with goals
2.2 contract between stakeholders with interests
2.3 the graphical model
chapter 3 scope
3.1 functional scope
3.2 design scope
3.3 the outermost use cases
3.4 using the scope-defining work products
3.5 exercises
chapter 4 stakeholders and actors
4.1 stakeholders
4.2 the primary actor
4.3 supporting actors
4.4 the system under discussion
4.5 internal actors and white-box use cases
4.6 exercises
chapter 5 three named goal levels
5.1 user goals (blue, sea-level)
5.2 summary level (white, cloud/kite)
5.3 subfunctions (indigo/black, underwater/clam)
5.4 using graphical icons to highlight goal levels
5.5 finding the right goal level
5.6 a longer writing sample: "handle a claim" at several leveis
5.7 exercises
chapter 6 preconditions, triggers, mld cuarantees
6.1 preconditions
6.2 ninimal guarantees
6.3 success guarantee
6.4 triggers
6.5 exercises
chapter 7 scenarios and steps
7.1 the main success scenario
7.2 action steps
7.3 exercises
chapter 8 extensions
8.1 extension 8asics
8.2 the extension conditions
8.3 extension handling
8.4 exercises
chapter 9 technology and data variations
chapter 10 linking use cases
10.1 sub use cases
10.2 extension use cases
10.3 exercises
chapter 11 use case formats
11.1 formats to choose from
11.2 forces affecting use case writing styles
11.3 standards for five project types
11.4 conclusion
11.5 exercise
part 2 frequently discussed topics
chapter 12 when are we done?
chapter 13 scaling up to many use gases
chapter 14 crud and parameterized use cases
14.1 crud use cases
14.2 parameterized use cases
chapter 15 business process modeling
15.1 modeling versus designing
15.2 linking business and system use cases
ruety walters: business modeling and system requirements
chapter 16 the missing requirements
16.1 precision in data requirements
16.2 cross-linking from use cases to other requirements
chapter 17 use cases in the overall process
17.1 use cases in projea organization.
17.2 use cases to task or feature lists
17.3 use cases to design
17.4 use cases to ui design
17.5 use cases to test cases
17.6 the actual writing
andy kraus: collecting use cases from a large, diverse lay group
chapter 18 use case briefs and extreme programming
chapter 19 mistakes fixed
19.1 no system
19.2 no primary actor
19.3 too many user interface details
19.4 very low goal levels
19.5 purpose and content not aligned
19.6 advanced example of too much ui
part 3 reminders for the busy
chapter 20 reminders for each use case
chapter 21 reminders for the use case set
chapter 22 reminders for working on the use cases
appendiees
appendix a use cases in uml
a.1 ellipses and stick figures
a.2 uml's includes relation
a.3 uml's extends relation
a.4 uml's generalizes relations
a.5 subordinate versus sub use cases
a.6 drawing use case diagrams
a.7 write text-based use cases instead
appendix b answers to (some) exercises
appendix c glossary
appendix d readings
index [1] 
參考資料