Object oriented design includes the following activities: 1. Refining the use-case model to reflect the implementation environment.

2. Modeling object interactions and behaviors that support the use-case scenario. 3. Updating the object model to reflect the implementation environment. The manner in which the user accesses the system via a menu, window, button, bar code reader, printer, and so on should be described in detail. The contents of window, reports, and queries should also be specified within the use case. Use case type to reflect implementation details such as user interface constraints, tactical use cases called system design use cases are derived from the system analysis use cases. Window controls in system design use cases, window controls such as icons, links, check boxes, and buttons are explicitly stated. Window names the name of each user interface element (window name) is stated. If additional information about a user interface element exists, it is good practice to reference it. Otherwise, more detailed window specifications could be added to the use case. Navigation instructions directions on how the user navigates the user interface should be specified.

Use case name Use case id Priority Source Primary business actor Primary system actor Other participating actors: Other interested stakeholders:

Place new order Mss-suc002.00 High Requirement mss-r1.00 Requirements use case mss-buc002.00 Club member (alias active member, member) Club member (alias active member, member) Warehouse (alias distribution center)(external receiver) Accounts receivable (external server) Marketing interested in sales activity in order to plan new promotions Procurement interested in sales activity in order to replenish inventory. Management interested in order activity in order to evaluate company performance and customer (member) satisfaction. This use case describes the event of a member submitting a new order for soundstage products via the world wide web. The member selects the items he or she wishes to purchase. Once the member shas comleted shoppoing, the members demographic information as well as account standing will be validated. Once the products are verified as being in stock, a packing order is sent to the distribution center for it to prepare the shipment. For any product not in stock, a back order is created. On completion, the member will be sent and order confirmation

Description

Precondition

Trigger Typical course of events:

The individual must be a registered user of the system. The member must have logged in to the system, and the member home page is being displayed. This use case is initiated when the member slects the option to enter a new order. Actor action System response Step 1: the member clicks on the place new order icon (or link). Alt step 3a: if the member clicks on the item name, the system displays a pop-up window w15 product detail display This use case concludes when the member receives a confirmation of the order. The order has been recorded and, if the ordered products were available, released to the distribution center. For any product not available a back order has been created. Member must have a valid e-mail address to submit online orders Member is billed for products only when they are shipped Use case must be available to the member 24/7 Frequency it is estimated that this use case will be executed 3,500 times per day. It should support up to 50 concurrent members. Product can be transferred among distribution centers to fill orders Procurement will be notified of back orders by a daily report (separate use case). The member responding to a promotion or a member using credits may affect the price of each ordered item. The member can cancel the order at any time clicking the [cancel order] button. If member hits [back page] button at any time, refresh current window.

Alternate courses Conclusion Postcondition

Business rules Implementation constraints and specification: Assumptions: