Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
Tham khảo tài liệu 'addison wesley writing effective use cases phần 6', ngoại ngữ, ngữ pháp tiếng anh phục vụ nhu cầu học tập, nghiên cứu và làm việc hiệu quả | Chapter 11. Use Case Formats Page 123 - Formats to choose from 2 . 3 EXTENSIONS Step Branching Action 1a condition causing branching action or name of sub-use case TECHNOLOGY DATA VARIA- TIONS 1 list of variation s Two-column table Rebecca Wirfs-Brock invented the idea of a conversation whose distinguishing visual characteristic is the use of two columns. The primary actor s actions are in the left-hand column the system s actions are in the right-hand column. Conversations are most often written in preparation to designing the user interface so they may pay contain more detail on the user s movements. You can write a use case using the two-column table form. The result is clear but often quite long even exceeding three pages see for example Use Case 36 Research a solution - Before on page 190 . Usually by the time we revise the text to fit into 3-9 steps at appropriate goal levels the writing is so simple and clear that people no longer find the need for the two columns. Constantine and Lockwood adopt the format of the conversation in their essential use cases as described in their book Software for Use. The difference is that in an essential use case all of the user movements dialog description are left out of the writing so the result is very short exactly as described in this book. The one difficulty with using the two-column format to capture behavioral requirements once you deal with the length is that there is no place to write about the supporting actors. One could add a third column for them but I have never heard it suggested nor seen it done. I think this is because conversations and essential use cases are aimed at capture user interface requirements rather overall system behavioral requirements. All of the above taken into account many people do find the two-column form attractive while they are learning about use cases and want to make the actions clear or when they are analyzing and partitioning the requirements use cases. Experiment with it if you .
