Scribd
Upload
5 views2 pages

Purchase Order Creation Use Case

The document outlines a use case for creating a purchase order, detailing the process for specifying items, vendors, and relevant codes. It identifies the primary actor as the Purchaser and lists stakeholders including A/P staff, Dept. Approver, Vendor, and the Company, each with specific interests in accurate data entry and adherence to business rules. The main success scenario includes steps for initiating a purchase order and entering item details, while also addressing potential variations and unresolved issues in the process.

Uploaded by

samacc121292
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
5 views2 pages

Purchase Order Creation Use Case

The document outlines a use case for creating a purchase order, detailing the process for specifying items, vendors, and relevant codes. It identifies the primary actor as the Purchaser and lists stakeholders including A/P staff, Dept. Approver, Vendor, and the Company, each with specific interests in accurate data entry and adherence to business rules. The main success scenario includes steps for initiating a purchase order and entering item details, while also addressing potential variations and unresolved issues in the process.

Uploaded by

samacc121292
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Example: Use Case

Use Case: Create purchase order


Brief Description: Create a new purchase order specifying items to be purchased,
vendor, as well as the applicable department and university codes for these items.
My comments about the use case are in blue. These comments are not part of the use
case and you don’t need to (and shouldn’t include them). This use case was written in
response to an assignment in another course, which is why the role of the Dept. Approver
is not explained below. If the stakeholders and steps of your use case are not self evident
you should add a bit more to the brief description to provide the necessary context.
Primary Actor: Purchaser

Stakeholders and Their Interests:


A/P staff: Data is entered accurately and follows business rules
Dept. Approver: Data is entered accurately and follows business rules
Vendor: Products are specified and contact information is listed
Purchaser: Wants accurate, fast entry, with no errors
Note that primary actor is also included as a stakeholder
Company: Wants business rules to be followed, and system to be updated and record
transactions accurately.

Supporting Actors and Their Roles:


None so far
Note: this may NOT be true for your use cases. For example, a use case involving credit
card processing would have a credit processing service as a supporting actor. In this
case, surprisingly, there are no supporting actors. The vendor and item information is
stored in the system and is not updated in real time. Clearly this data needs to be
obtained and entered into the system, but that is another use case. The Dept. Approver
will need to approve the PO, but this is done in another use case and happens later.

Main Success Scenario:


1. Purchaser starts a new PO
2. Purchaser specifies Vendor to purchase from.
3. Purchaser specifies item to purchase.
4. System displays item description, price, and University classification codes.
5. Purchaser specifies quantity to purchase and makes any necessary additions or
changes to department and University codes.
Steps 3 through 5 are repeated until all items are entered into the system
6. System assigns PO a number, records PO information, and displays PO details to user.

1
Example: Use Case
Variations:
If the budget is exceeded the system should warn the purchaser. Need to clarify the
business procedures. Do we allow overrides?
Need to allow the purchaser to cancel PO at any step before 6.
What do we do if purchaser needs to order from vendor not in our system?
What do we do if purchaser needs to order item that is not in our system?
Consider possibility in the future to access vendor information and item information from
vendor systems via web services.
Note that variations can include unresolved issues and future possibilities. The key thing
is to identify special cases and problems the system will need to deal with. There is no
need to be exhaustive but for full credit the list should include at least a few significant
business variations as illustrated in this use case.

You might also like