NO speaking, gesturing, photos or drawing between Specifiers and Artists. Most teams do not create a way to change process on the fly. We need a way to evolve the process. Discuss and reflect: what went good and bad. Adjust your strategy for the next round. Alistair Cockburn Slide 41 Reflection technique: Write in this chart.
What worked? What might you try next time? As before, but use incremental technique Specifiers describe only ONE shape.
Advanced teams: two people one shape each. After Artists have drawn the shape, they cand send it or copy to the Specifiers to see. Specifiers can decide whether to correct that shape, or go on with the next shape. Alistair Cockburn Slide 43 Reflection technique: Write in this chart. Pause and reflect one more team.
Look for creative ways to cheat legally. What would be actually the Best way to work? Sitting together, multimodal communication help.
Communication has its limits. What you write depends on your shared vocabulary. A process needs to allow for its own evolution. Both Process and Product feedback are needed. One possible reflection workshop technique. Precision is expensive Control when you add it and how much you add. We work in four levels of precision with use cases: Level 1: Actor's name and goal. Level 2: The brief or the main success scenario.
Level 3: The extension conditions Level 4: The extension handling steps. Alistair Cockburn Slide 48 How to do it: 1. Identify the actors and their goals. An actor is anything with behavior. What computers, subsystems and people will drive our system? What does each actor need our system to do? Alistair Cockburn Slide 49 How to do it: For each use case Write the simple case: goal delivers. The main success scenario, the happy day case.
Capture each actors intent and responsibility, from trigger to goal delivery. Result: readable description of systems function. Alistair Cockburn Slide 50 How to do it: 3. Capture conditions needing other handling.
Usually, each step can fail. Note the condition after the main success scenario. The value of extension scenarios is completeness, detecting unusual situations. What if their credit is too low? What if they run over the extended credit limit? What if we cannot deliver the quantity? What if data is corrupt in the database? These are commonly overlooked situations Result: list of alternate scenarios to work out over time Alistair Cockburn Slide 51 How to do it: For each extension condition, 4.
Follow the extension till it ends or rejoins. Recoverable extensions rejoin main course. Non-recoverable extensions fail directly.
Each scenario goes from trigger to completion success or failure Result: Complete use case Alistair Cockburn Slide 52 Write the recoverable and failure scenarios as extensions to the ideal one. UC 4: Place an order 1. Clerk identifies the customer, each item and quantity.
Low on stock: Customer accepts reduced Value: overview of system, useful for prioritizing, estimating. Step 2. Value: team alignment on systems responsibilities. Step 3. Name the conditions needing other handling. Result: list of alternate scenarios to research over time. Value: beat the programmers to the resolution! Step 4.
Result: complete use case. Alistair Cockburn Slide 54 Place an Order 1. Clerk identifies customer 2. Identify Customer 1. Operator enters name. System finds near matches. Extensions: 2a. No match found Note the active verbs! A scenario refers to lower-level goals sub-use cases or common functions. Alistair Cockburn Slide 56 User Goals advertise order invoice set up promotion reference promotion monitor promotio n place order create invoice send invoice identify promotion identify customer register user identify product make money Summary Goals Subfunctions Level: Summary user-goal subfunction or kite sea-level fish The Altitude metaphor: User goals are at sea level.
Buyer researches on website, requests sales rep assistance. Webserver has ProcessServer send lead information to a salesperson. Salesperson establishes a new opportunity in SalesManager. Salesperson has SalesManager contact the lead, discusses with Buyer, and validates they could possibly provide a solution.
Salesperson using SalesSupport develops product recommendations based on analysis information and recommendation provided by Webserver. Salesperson develops presentation in SalesSupport and presents to buyer using SalesSupport. Buyer requests a proposal.
Salesperson develops a proposal and sends to buyer. Salesperson negotiates with the Buyer to close the deal as a win. Salesperson updates forecast and commission using SalesManager. Salesperson places an order for items using SalesSupport. The Company assembles and ships the products purchased. Company invoices buyer and buyer pays. Alistair Cockburn Slide 58 You will need all of kite, sea, and fish use cases at some point in the project.
A student will use a Palm and note when anyone enters or exits. The student shouldnt reset the device to zero -- a supervisor should do that each morning. Eventually, the handheld will notify a server every time the number changes. Write the use cases for the librarys user counter system.
For full system : Step 1. For "Register entry" : Step 1. Check stakeholders' interests Step 3. Display a blank schedule. Display a list of all classes in the following way: The left window lists all the courses in the system in alphabetical order. The lower window displays the times the highlighted course is available. The third window shows all the courses currently in the schedule. Student clicks on a course. Update the lower window to show the times the course is available.
Student clicks on a course time and then on the Add Course button. Check if the Student has the necessary prerequisites and that the course offering is open. If the course is open and the Student has the necessary prerequisites, add the Student to the course. Display the updated schedule showing the new course. If no, put up a message, You are missing the prerequisites. Choose another course. Mark the course offering as enrolled in the schedule. End do when the Student clicks on Save Schedule.
Save the schedule and return to the main selection screen. Student requests to construct a schedule. The system prepares a blank schedule form. The system gets available courses from the Course Catalog System. Student selects up to 4 primary and 2 alternate course offerings. For each course, the system verifies that the Student has the necessary prerequisites, adds the Student to the course, marking Student as enrolled for that course in the schedule.
When the Student indicates the schedule is complete, the system saves it. Student already has a schedule: System brings up the current version of the Students schedule for editing instead of creating a new one. Current semester is closed and next semester is not yet open: System lets Student look at existing schedules, but not create new ones.
Course Catalog System does not respond: The system notifies the Student and the use case ends. Course full or Student has not fulfilled all prerequisites: System disables selection of that course and notifies the Student. Just barely beat the programmers to the extension handling decisions Write just enough content for the team to understand.
Adjust your working habits each iteration to fit your particular situation! Alistair Cockburn Slide 65 Always question how much to write at any given time How much do we need to write at this time?
When do we need to write more? Who benefits from more information or more detail? Alistair Cockburn Slide 66 Take advantage of available degrees of freedom in your process 1. Write less more clearly always 2. Write less sometimes 3. Shortcut the use case structure sometimes 4. Alistair Cockburn Slide 68 2. Write less sometimes the economics of communication Fully dressed use cases exhaustive, numbered Casual use cases approximate, paragraph form Use case briefs sentences The correct form to use depends on your projects priorities and properties!
Guarantees: sufficient log information exists that PAF can detect what went wrong. Success Guarantees: remote web site acknowledged purchase, user's portfolio updated. Main success scenario: 1. User selects to buy stocks over the web. PAF opens web connection to the site, retaining control. User browses and buys stock from the web site.
PAF intercepts responses from the web site, and updates the user's portfolio. PAF shows the user the new portfolio standing. User wants a web site PAF does not support: 2a1. System gets new suggestion from user, with option to cancel use case. The Buyer finds the best vendor, initiates PO with Vendor. At any time prior to receiving goods, Requestor can change or cancel the request. Canceling it removes it from any active processing.
Note: spreadsheets again! Alistair Cockburn Slide 72 3. Shortcut the use case structure sometimes Use cases are not read by a compiler but by a human Sections have multiple pages.
You can see the list of pages for the current section on the right side of the window show me. Now you're editing! Rename the page or change commenting options show me if you like. You can save, preview or cancel your changes at any time by clicking the button on the right side show me. Content is divided into subsections, which each have a dotted border. You can delete or edit the contents of a subsection by clicking the or icons at the top right corner of the subsection.
To add new subsections, find and click the type of content you want to add in the options list on the right side of the page show me. PDF John Steele. Settings for Home Rename Delete Move to ISBN10 ISBN13 Bestsellers rank 95, It also discusses concepts in molecular biology and genetics, recent scientific and technological advances in modern pathology, the concept of "molecular pathogenesis" of disease, and how disease evolves from normal cells and tissues due to perturbations in molecular pathways.
Cancel Preview Save Page. Cancel Keep Editing Save Page. Rich Text Content. Page Comments. Click here to download. Using an ePortfolio Introduction ePortfolios are a place to demonstrate your work. They are made of sections and pages. The list of sections are along the left side of the window show me.
Each section can have multiple pages, shown on the right side of the window show me. The content you see on a page is the same content any visitors will see. To edit this content, click the " Edit This Page" link show me and the page will change to editing mode. To change the settings for your ePortfolio, click the "ePortfolio Settings" link show me.
You can rename the portfolio and also change whether it is public or private.
0コメント