1. BabysPit Order Fullfillment Current situation BabysPit is Norway’s premier supplier of baby products Deliver 100 orders daily from each of 30 warehouses in 3 Norwegian cities Yearly revenue of almost 1 billion NOK The secret to our success: Competition between warehouses Currently expanding the number of warehouses in our network Electronic Order Fullfillment Business case Currently, delivery costs are 150 million NOK. Delivery time is 24-48 hours We want to establish our own delivery service to save money and time We have tried a pilot implementation with one warehouse You’re here to deliver proposals for the IT-system for the delivery service Current use case 1.Customer places order in WebShop (outside scope) 2.Warehouse finds open orders in WebShop backend Pilot: WebShop pushes all orders to pilot system 3.Warehouse updates order status (pilot automates) 4.Warehouse manually updates inventory system (pilot automates) 5.Warehouse packs orders and readies for postal pickup Pilot: Warehouse sends order with one of three drivers The assigment Create three diagrams The processing steps for an order The context and components of the order fullfillment system The deployment components of the order fullfillment system Group should give five minute presentation, describing in terms of diagrams Scenario: Normal order flow Scenario: Items not in warehouse Scenario: Acquisition of new warehouse Scenario: Purchases and employments to go live 2 scenarios of your own choosing Key differensiator

2. Example diagrams Pilot context Target Possible deployment Pilot domain

3. Plan Introduction to the problem domain and task State/activity diagram: Order processing – Purpose: Understand functionality, identify problematic scenarios – Stickies on a flip-over Review CRC architecture diagram of internal and external logical components – Create a solution – Stickies on a flipover CRC architecture diagram of deployment components – Become specific about what is to be made and bought – Stickies on a flipover Presentation of solutions – Architecture is presentation Exploration of solutions using scenarios – Scenaios verify and break architectures Retrospective – Surprise or revelations/Next learning goals/Changes to you work – Workshop more of/less of