<Company Name>

Lazada Management System

Use-Case Specification: Register New User

Version <1.0>
[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in
square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author
and should be deleted before publishing the document. A paragraph entered following this style will
automatically be set to normal (style=Body Text).]
[To customize automatic fields in Microsoft Word (which display a gray background when selected), select
File>Properties and replace the Title, Subject and Company fields with the appropriate information for
this document. After closing the dialog, automatic fields may be updated throughout the document by
selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field and press F9. This must
be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and the
field contents. See Word help for more information on working with fields.]
<Project Name> Version: <1.0>
Use-Case Specification: <Use-Case Name> Date: <dd/mmm/yy>
<document identifier>

Revision History
Date Version Description Author
<04/12/2021> <1.0> <details> Nguyen Thi Thanh Mai

Confidential ÓÓ<Company Name>, 2021 Page 2

 <Project Name> Version: <1.0>
Use-Case Specification: <Use-Case Name> Date: <dd/mmm/yy>
<document identifier>

Table of Contents
1. Use-Case Name 3
1.1 Brief Description 3

2. Flow of Events 3
2.1 Basic Flow 3
2.2 Alternative Flows 3
2.2.1 < First Alternative Flow > 3
2.2.2 < Second Alternative Flow > 3

3. Special Requirements 3
3.1 < First Special Requirement > 3

4. Preconditions 3
4.1 < Precondition One > 3

5. Postconditions 3
5.1 < Postcondition One > 3

6. Extension Points 3
6.1 <Name of Extension Point> 3
Use-Case Specification: <Use-Case Name>
[The following template is provided for a Use-Case Specification, which contains the textual properties of
the use case. This document is used with a requirements management tool, such as Rational RequisitePro,
for specifying and marking the requirements within the use-case properties.
The use-case diagrams can be developed in a visual modeling tool, such as Rational Rose. A use-case
report, with all properties, may be generated with Rational SoDA. For more information, see the tool
mentors in the Rational Unified Process.]

1. Use-Case Name
1.1 Brief Description
This use-case describes the steps of registering new user including filling up the register form and linking
the credit. Users can create an account to make transactions on Lazada easily.
1.2 Basic Flow
1. The user clicks to button “SIGNUP” on the top of homepage.
2. The pop up comes up and requires filling in the information.
3. The user fills all the required information.
3.1 The user inputs phone number
3.2 The user slides to get SMS Code
3.3 The user inputs SMS Code which is sent to the phone
3.4 The user inputs password
3.5 The user inputs birthday and gender

Confidential ÓÓ<Company Name>, 2021 Page 3

 <Project Name> Version: <1.0>
Use-Case Specification: <Use-Case Name> Date: <dd/mmm/yy>
<document identifier>

3.6 The user inputs full name

3.7 The user optionally ticks to agree the notification “I'd like to receive exclusive offers and
promotions via SMS”.
4. The user clicks to the button “SIGN UP”.
5. The pop up “Manage My Account” comes up and the system record that user create an account
successfully.

1.3 Alternative Flows

1. Sign up by email
1.1. The user clicks to the button “Sign up with Email”
1.2 The user fills all the required information.
1.2.1 The user inputs email
1.2.2 The user slides to get Email Code
1.2.3 The user inputs Email Code
1.2.4 The user inputs password
1.2.5 The user inputs birthday and gender
1.2.6 The user inputs full name
1.2.7 The user optionally ticks to agree the notification “I'd like to receive exclusive offers and
promotions via email”.
1.3 The user clicks to the button “SIGN UP”.
1.4 The pop up “Manage My Account” comes up and the system record that user create a Lazada
account successfully.

2. Sign up by Facebook account

2.1 The user clicks to button Facebook.
2.2 The pop up comes up and requires users to log in Facebook account
2.3 The pop up asks user whether continue with Facebook account.
2.4 The user clicks to button continue with Facebook account.
2.5 The pop up “Manage My Account” comes up and the system record that user create a Lazada
account successfully.

3. Sign up by Google account

2.1 The user clicks to button Google.
2.2 The pop up comes up and requires users to choose one Google account.
2.3 The user clicks to one Google account.
2.4 The pop up “Manage My Account” comes up and the system record that user creates a Lazada
account successfully.

Confidential ÓÓ<Company Name>, 2021 Page 4

 <Project Name> Version: <1.0>
Use-Case Specification: <Use-Case Name> Date: <dd/mmm/yy>
<document identifier>

2. Special Requirements
There are no special requirements.

3. Preconditions
- The user’s device connected to the Internet when user register a new account.
- Sign up by email: User has already had an email account.

- Sign up by Facebook account: User has already had a Facebook account.

- Sign up by Google account: User has already had a Google account.
4. Postconditions
User has a new Lazada account.
5. Extension Points
User do not login Facebook or Google account.

Confidential ÓÓ<Company Name>, 2021 Page 5