Table 6.0 |
Use Case # | DATAENTRYPROJECTCUST-1009 |
Use Case name | Maintain Customer |
Description | This Use Case depicts full maintenance of customer from project "Data Entry". |
Scope and level | - Data Entry System (Internal)
- Credit Card System (External)
|
Level | User Goal Level (If this property is not understood, look at the reference for the book Writing Effective Use Cases (**PRE-PUB. DRAFT#3**): Alistair Cockburn Humans and technology) |
Primary and secondary actors | Data Entry operator. |
Stakeholders and interests | |
Trigger | Data entry operator clicks on menu: "Add New Customer" |
Preconditions | - Data entry operator should be logged in.
- Data entry operator should have access to Internet.
|
Assumptions | Customer information received is entered manually. No automated import routine is in the scope. |
Failed End condition | - Customer is not added to database and appropriate error message is displayed.
- Customer code already existing in the customer database.
- Customer code length limit is exceeded.
- Customer credit card limit is exceeded.
- Customer credit card validation failed with the payment gateway.
|
Action | Add new customer |
Main success scenario (or basic Flow): | - Data entry operator receives customer information.
- Data entry operator enters following information:
- Customer code
- Customer name
- Customer address
- Customer phone
- Customer code is checked if it exists in Customer table.
- If the customer code is existing then "Duplicate Customer Code" error is raised.
- If the customer code is more than 8 length, then "Customer code length limit crossed" error is raised.
- After step 3 is passed OK. Data entry operator enters credit card information. If the credit card length is more than 10 length, then "Credit card length limit crossed" error is raised.
- Credit card information is send to the external payment gateway. Appropriate APIs of the external payment gateway will be used for validity.
- External payment gateway returns "OK" if credit card is validated or else will return "NOT VALID" flag.
- Data entry operator then adds the customer in database.
|
Alternate scenario (Extensions): | Update Existing Customer - Data entry operator enters customer code to retrieve the customer who has to be updated.
- Data entry operator makes appropriate changes to the customer information. All steps and business validation from 1 to 6 of Add new Customer is repeated.
- Data Entry operator updates the customer information.
|
Alternate scenario (Extensions): | Delete Existing Customer - Data entry operator enters customer code to retrieve the customer who has to be deleted.
- Data entry operator deletes the customer. Data entry operator is alerted "Are you sure you want to delete the Customer?”
- If the data entry operator clicks "Yes", then the customer is deleted from the database.
- If the data entry operator clicks "NO", no action is taken.
|
Success Guarantee (Post conditions): | - Customer is added to Customer database.
- Customer is updated to Customer database.
- Customer is deleted from Customer database.
|
Special Requirements (including business rules): | |
Technology and Data Variations List: | If credit card payment gateway API changes, the interaction of the data entry customer module will have to be changed accordingly. |
Frequency of occurrence: | |
Notes and Open Issues: | |
相关推荐
用例描述文档模板 非常全面漂亮的用例描述文档模板
用例文档模板用例文档模板用例文档模板用例文档模板用例文档模板用例文档模板用例文档模板用例文档模板用例文档模板用例文档模板用例文档模板用例文档模板用例文档模板用例文档模板用例文档模板用例文档模板用例文档...
产品用例描述模板.doc
但应当强调的是 实用上更重要的是专注于写出完整的可理解的事件路径 而不是按指定的模板填写每个部分 ">是一种被广泛使用的用于发现和记录需求 特别是功能需求 的机制 写出用例是一种最好的理解和描述需求的技巧 ...
测试用例实例模板 测试用例实例模板 测试用例实例模板
软件系统通用测试用例模板
软件测试用例word模板 软件测试用例word模板 软件测试用例word模板
测试用例模板测试用例模板测试用例模板测试用例模板
测试用例模板 测试用例 模板测试用例模板 测试用例 模板
用例描述规约,包括一般用例描述所用的条目,office模板文件
UML用例需求,如何建立用例图,以及建立用例描述,用例描述建立的格式。UML用例需求,如何建立用例图,以及建立用例描述,用例描述建立的格式。UML用例需求,如何建立用例图,以及建立用例描述,用例描述建立的格式...
UML用例描述UML用例描述UML用例描述UML用例描述UML用例描述UML用例描述UML用例描述UML用例描述
修改他人创建的文件需要在修改处用红色字体,并填写最后一次修改信息 时间格式为:yyyy/mm/dd (将模板中的该说明删除后编写用例描述)XXXXX 用例描述编
测试用例(Test Case)是指对一项特定的软件产品进行测试任务的描述,体现测试方案、方法、技术和策略。其内容包括测试目标、测试环境、输入数据、测试步骤、预期结果、测试脚本等,最终形成文档。简单地认为,测试...
简单的测试用例模板
自动测试用例模板,自动测试用例模板,自动测试用例模板,
华为比赛case用例
自己参考使用的模板,51测试用例模板,word模式 可以作为参考使用,需求分析师,测试工程师写需求,写用例参考模板!
测试用例设计模板及例子 例子是登陆用例测试
XXXX用例描述参与者触发条件前置条件后置条件正常流程拓展流程特殊需求。