CNC Project High Level Prepaid Electronic Contracts
Date Updated: 2006-12-18
Context of Use: This is a high level BUC for Prepaid Electronic Contracts process within the CNC Project. Either Buyer or Seller can initiate this Contract process so for this BUC scenario the Buyer is initiating the Prepaid Electronic Contract.
Scope: The process of sending and receiving the Prepaid Electronic ContractCreate and ContractResponse
Primary Actor: Seller
Stakeholders and Interests- Buyer:
Buyer of product
- Seller:
Seller of product
Success Guarantees: Contract has been sent and a response is sent that all that had been negotiated has been accurately recorded in the contract.
Trigger: Buyer and Seller wish to enter into a contract.
Preconditions- Buyer and Seller relationship has been previously established.
- Negotiation of contract details (such as pricing, volume, terms etc.)has been agreed to either verbally or in email.
Main Success Scenario
| 1. | Buyer sends the Seller a ContractCreate message with details of contract negotiations. This would be the "PrepaidOffer" type of ContractCreate.
Related Message (v4.0):
ContractCreate
Business Guidelines:
- A business guideline may need to be established as to what the timeframe should be from the time the contract has been verbally or email agreed to the transmission of the ContractCreate is sent.
|
| 2. | Buyer receives ContractCreate from Seller.
Business Guidelines:
- A business guideline may need to be established as to what the timeframe should be from the time the ContractCreate is sent/received until a ContractResponse is sent back.
|
| 3. | Seller validates the information.
Related Message (v4.0):
ContractResponse
Business Guidelines:
- A business guideline may need to be established as to what the timeframe should be from the time the ContractCreate is sent/received until a ContractResponse is sent back.
|
| 4. | Buyer sends to Seller an "accepted" ContractResponse
Related Message (v4.0):
ContractResponse |
| 5. | Seller sends Buyer invoice
Related Message (v4.0):
Invoice |
| 6. | Buyer receives invoice and makes payment |
Extensions
Extensions for Step 1
- Extension # 1: Seller server is down and transmission can't be sent.
| 1. | Seller should notify Buyer of issue with server and determine resolution steps. |
- Extension # 2: Buyer recognizes a human error (keying error, database synchronization error etc.)Prior to Seller rejecting or notifying Buyer of error.
| 1. | Seller to contact Buyer and determine resolution. |
Extensions for Step 2
- Extension # 1: Buyer's server is down and unable to receive ContractCreate.
| 1. | Buyer or Seller should contact trading partner to determine resolution. |
Extensions for Step 3
- Extension # 1: Information in ContractCreate is not able to be validated - some of the information is incorrect as to what was anticipated as being negotiated (such as timing not met, pricing, terms, misunderstanding, etc.)
| 1. | Seller send to Buyer a "reject" in the ContractResponse message. |
| 2. | Seller to contact Buyer to resolve differences |
| 3. | Buyer sends a modified ContractCreate with a type code "Modified" to Seller. |
| 4. | Seller receives modified ContractCreate. |
| 5. | Seller validates ContractCreate information. |
Extensions for Step 4
- Extension # 1: Buyer's ContractResponse is not received by Seller
| 1. | Buyer contacts Seller to determine resolution. |
Postconditions- Buyer makes payment on prepaid invoice. Seller updates contract to reflect payment
NotesAuthor: CNC B/T Team
Date Created: 2006-08-30This document generated using UseCase.xsl version 2004-09-13