tiistai 6. toukokuuta 2014

Software developing - Definition

Software developing process always starts from business persons view. Business person first defines how the program should work and what they want it to do. After that use cases are identified. Use case describes step by step how process should work. It can also describe data flow between system without human interaction. "In software and systems engineering, a use case is a list of steps, typically defining interactions between a role (known in Unified Modeling Language (UML) as an "actor") and a system, to achieve a goal. The actor can be a human or an external system."

Read more: http://en.wikipedia.org/wiki/Use_case

Here is example use case template how to do an order from web-shop.

Use case template

CONTENTS


Name documents like this: UC_Name.doc. Please note that UC is short for ‘Use case, put UC in the beginning for the sake of consistency.

Use case name
Frequency of use
<UC number>
12
Place Order
<times per day for example>500

Brief description
<Short description (one or two sentences) of what takes place>
After the user has selected items to purchase and then order the items. The user will provide payment and shipping information. The system will respond with confirmation of the order and a tracking number that the user can use to check on order status in the future. The system will also provide the user with an estimated delivery date for the order, which will include all selected items. The user may already have an account with the company with billing and shipping information.

1                                  Actors

User role
User rights
<User roles that participate in this use case.>
Registered Shopper
Has an existing account, possibly with billing and shipping information)
Non-registered Shopper
Does not have an existing account
Fulfillment System
(processes orders for delivery to customers)
Billing System
bills customers for orders that have been placed

2                                  Triggers (Not mandatory step)

The user indicates that she wants to purchase items that she has selected.

3                                  Preconditions

Describe what is already known at the beginning of the use case and what must have been done before.


Precondition
User has selected the items to be purchased.

4                                  Post-conditions

Describe what the result is both from the user’s and the system’s viewpoint.

Description
The order will be placed in the system.
The user will have a tracking ID for the order.
The user will know the estimated delivery date for the order.

5                                  Functional description

Normal flow for the case

Description
<Verbal description of use case step by step>
1.      The user will indicate that she wants to order the items that have already been selected.
2.      The system will present the billing and shipping information that the user previously stored.
3.      The user will confirm that the existing billing and shipping information should be used for this order.
4.      The system will present the amount that the order will cost, including applicable taxes and shipping charges.
5.      The user will confirm that the order information is accurate.
6.      The system will provide the user with a tracking ID for the order.
7.      The system will submit the order to the fulfillment system for evaluation.
8.      The fulfillment system will provide the system with an estimated delivery date.
9.      The system will present the estimated delivery date to the user.
10.   The user will indicate that the order should be placed.
11.   The system will request that the billing system should charge the user for the order.
12.   The billing system will confirm that the charge has been placed for the order.
13.   The system will submit the order to the fulfillment system for processing.
14.   The fulfillment system will confirm that the order is being processed.
15.   The system will indicate to the user that the user has been charged for the order.
16.   The system will indicate to the user that the order has been placed.
17.   The user will exit the system.

 Step by step

Identifier
Step by step
P1



6                                  Alternative flows

Enter here any alternative sequence of events. As an identifier for these, use ‘A’.

Identifier
Alternative
<A1, A2>
3A1: The user enters billing and shipping information for the order. The user desires to use shipping and billing information that differs from the information stored in her account. This alternate flow also applies if the user does not maintain billing and / or shipping information in their account, or if the user does not have an account.
The user will indicate that this order should use alternate billing or shipping information.
The user will enter billing and shipping information for this order.
The system will validate the billing and shipping information.
The use case continues
5A1: The user will discover an error in the billing or shipping information associated with their account, and will change it.
The user will indicate that the billing and shipping information is incorrect.
The user will edit the billing and shipping information associated with their account.
The system will validate the billing and shipping information.
The use case returns to step 2 and continues.
5A2: The user will discover an error in the billing or shipping information that is uniquely being used for this order, and will change it.
The user will indicate that the billing and shipping information is incorrect.
The user will edit the billing and shipping information for this order.
The use case returns to step 3A1 step 3.
10A1: The user will determine that the order is not acceptable (perhaps due to disatisfaction with the estimated delivery date) and will cancel the order.
The user will request that the order be cancelled.
The system will confirm that the order has been cancelled.
The use case ends.

7                                  Exceptions

Enter here exceptions to the use case, such as error situations. As an identifier for exceptions, use 'E’.

Identifier
Exception
<E1, E2>
 <System exception>


8                                  Additional information

Identifier
Additional information
Reference
<Ai1, Ai2>
<Additional information>




9                                  Open issues

Identifier
Open issue
Reference
<OI1, OI2>
<Open issues that still have to be solved.>




10                               Change history

Version
Date
Change
Change made by










Ei kommentteja:

Lähetä kommentti