1 / 7

Supplier Selection

Supplier Selection. Soren Lauesen , February 2013 See more: Guide to Requirements SL-07, http://www.itu.dk/people/slauesen. 2 . T radition al requirements – hospital roster planning. Req 148: The system must be able to record the actual work hours for each employee.

lacy
Download Presentation

Supplier Selection

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Supplier Selection Soren Lauesen, February 2013 See more: Guide to Requirements SL-07,http://www.itu.dk/people/slauesen

  2. 2. Traditional requirements – hospital roster planning Req 148: The system must be able to record the actual work hours for each employee. Req 475: The system must be able to calculate the financial consequences of a given duty roster - in hours and in $. Mandatory reqs? Only req 148. We can do without req 475. Classical IEEE 830 The solution is useless in practice Is the requirement met? Strictly speaking not After signing the contract, A delivers the notice board solution instead?

  3. 3. Lessons learned? What is best: Good solution to req 148 and bad to req 475? Or the opposite? Meeting requirements is not yes/no, but degrees of value. Mandatory/optional requirements not suited in practice. The solution must be part of the contract.

  4. 4. Write it as use cases? Oops-trigger: When is it used and for what? Use case 475: Calculate the financial consequences of a roster. Trigger: The user wants to calculate the consequences. Precondition: The user is logged on. 1. The system shows a list of rosters. 2. The user selects a roster. 3. The user selects "Calculate consequences" 4. The system calculates the consequences. 5. The system shows the consequences. Exception: No rosters in the list. Invented dialog. Would be harmful here. Trivial details - seduced by the template. No real value added. Use cases cannot catch problems without a known solution – but here is the business value

  5. Example solutions: Automatically from last plan . . . System checks the vacation rules. System can record several years ahead. System suggests staffing of unstaffed duties. Warns in case violated rules and excess pay. Supports the "jigsaw puzzle" with Undo and several trial versions. Shows free staff from other depts. 5. Better requirements: Support tasks C1, C2 . . . C2: Make roster Frequency: Every 14 day. In some departments . . . Start: Calm point in the duty. End: When we get busy. Customer: Help - we bought the wrong system Subtasks and variants: 1. Create new roster. 2. Record leave. Two kinds . . . 3. Allocate staff. Ensure competence level, leave, union agreements. Avoid extra pay. 3a. Substitute not yet in the system. 3b. Get staff from other department. 4. Distribute plan for comments. 5. Park the plan or release it. Present problem: Recorded on stickers many months ahead. Pres. problem: Difficult manually. Errors and too much extra pay. Done by human plus computer Example of computer's part - not requirements

  6. Example solutions: Automatically from last plan . . . System checks the vacation rules. Only one year ahead. System suggests staffing of unstaffed duties. Separate batch calculation, 24 hours. Several versions cumbersome. Can show free staff from neighbor hospitals. 6. Requirements verification - assessing solutions C2: Make roster Frequency: Every 14 day. In some departments . . . Start: Calm point in the duty. End: When we get busy. Total points: 0 (as today) Subtasks and variants: 1. Create new roster. 2. Record leave. Two kinds . . . 3. Allocate staff. Ensure competence level, leave, union agreements. Avoid extra pay. 3a. Substitute not yet in the system. 3b. Get staff from other department. 4. Distribute plan for comments. 5. Park the plan or release it. Present problem: Recorded on stickers many months ahead. Pres. problem: Difficult manually. Errors and too much extra pay.

  7. User: Planner in department C1. Monthly report to personnel dept. C2. Make roster User: Staff in department C10. Record actual work hours C11. Swop duties C12. Staff illness User: Personnel department C20. Check rosters C21. Payroll amendments C22. Record new employees User tasks Business value Employees: 5000 Overtime pay: 20% til 10% Present IT costs: 30 mio/år Saved Mio DKK person years in 5 years 7 15 7 15 ? 5 ? 10 (soft factor) (400) 800 7 15 (soft factor) 50 Business goals 7. Business goals and how to meet them Not hierarchical, but many-to-many Personnel department: Automate some tasks Remove error sources Observe the 120 day rule Less trivial work and stress Hospital department: Reduce over-time pay etc. Faster roster planning Improve roster quality

More Related