1. Software Engineering Northeastern University Software Engineering A case study in Application Design

2. Software Engineering Northeastern University Screen representation of user tasks

3. Software Engineering Northeastern University User Login User: Password: Xerox Sales Console Role: login >> Login Screen represents Login Task action

4. Software Engineering Northeastern University Xerox Sales Console logout Activity: Manage Customers Serve customer >> Review sales order history >> Customer name Review sales commission >> John smith User Screens (contd.)

5. Software Engineering Northeastern University Customer Information summary Person Contact Information Book customer order >> Check order status >> Xerox Sales Console John smith Activity: Serve Customer View customer history Browse product catalog >> User Screens (contd.)

6. Software Engineering Northeastern University Xerox Sales Console John smith Activity: Book Customer Order Industrial Printers Catalog Product Id Product NameTarget Price Add >> Product IdProduct Name Order Items Actual Price Total Price My commission Cancel Order >>Submit Order >> Customer Information summary Person Contact Information Availability 20

7. Software Engineering Northeastern University Xerox Sales Console Sales person’s name: John smith Activity: Browse Product Catalog Printing Catalog Product Id Product NameTarget Price Done >> Customer Information summary Person Contact Information View Detail >> Description Product Description Find >> View Detail >>

8. Software Engineering Northeastern University Customer Information summary Person Contact Information Xerox Sales Console Sales person’s name: John smith Activity: Check Order Status Begin time Order Id Date started Status Action View Time frame Date completed End time Find >> Done >> Order List

9. Software Engineering Northeastern University 1.cServe customer 1.Manage Customers 1.c.cBook customer order 1.c.bCheck order status 1.c.aBrowse product catalog 1.bReview sales commission : 1.aReview sales order history Sales Process Use Case 1.c.c.aSubmit customer order 1.c.c.bCancel customer order 1.c.c.cSave customer order

10. Software Engineering Northeastern University 1.cServe customer 1. Manage Customers 1.c.cBook customer order 1.c.bCheck order status 1.c.aBrowse product catalog 1.bReview sales commission : 1.aReview sales order history Sales Person Sales Process Use Case Customer name Customer 1.c.c.aSubmit customer order 1.c.c.bCancel customer order 1.c.c.cSave customer order Product Catalog

11. Software Engineering Northeastern University 1.cServe customer Manage Customers 1.c.cBook customer order 1.c.bCheck order status 1.c.aBrowse product catalog 1.bReview sales commission 1.aReview sales order history 1.c.c.cSave customer order 1.c.c.aSubmit customer order 1.c.c.bCancel customer order Navigation Sequence

12. Software Engineering Northeastern University Implicit in the use case above is the fact that there is an authentication step that must be completed before the user is allowed to use the system 1. Manage Customers 1.bReview sales commission : 1.aReview sales order history 0. Login/validate the user 0.1Ask the security service if user has the right to use the system 0.2If user is valid then continue with next step