Ikram-Solutions

MyJobs System
Use Case Specification: Register Job Seeker

Version 1.1
MyJobs System Version: 1.1
Use Case Specification: Register Job Seeker Issue Date: 30th March 2005
Document Identifier: - Author: Mansoor AbdulLateef

Revision History

Date Version Description Author

th
17 March , 2005 1.0 Mansoor AbdulLateef
30th March , 2005 1.1 ( Amending according to the IM Ikram) Mansoor AbdulLateef

Page 2 of 7
MyJobs System Version: 1.1
Use Case Specification: Register Job Seeker Issue Date: 30th March 2005
Document Identifier: - Author: Mansoor AbdulLateef

Table of Contents

1. Register Job Seeker 4

1.1 Brief Description 4

2. Pre-Condition(s) 4

3. Flow of Event(s) 4

3.1 Basic Flow(s) 4

3.2 Alternative Flow(s) 5
3.3 Exceptional Flow(s) 4

4. Constraint(s) 5

5. Post-Condition(s) 5

6. Fields and Rule(s) 5

7. Extension Point(s) 6

8. Note(s) 6

9. GUI(s) 5

Page 3 of 7
MyJobs System Version: 1.1
Use Case Specification: Register Job Seeker Issue Date: 30th March 2005
Document Identifier: - Author: Mansoor AbdulLateef

Use Case Specification: Register Job Seeker

1. Register Job Seeker

Register Job Seeker

Job Seeker
(f rom Job Seeker)
(f rom Actors)

Figure 1Registration Job Seeker User Case

1.1 Brief Description

This use case is used by Job Seekers to be registered as member in the System.

2. Pre-Condition(s)

The Register user name shouldn’t be existed in the System Database.

3. Flow of Event(s)

3.1 Basic Flow(s)

The System prompts the user to do the following activities:

i. Actor Enter the Username [A-1,E-2]
ii. Actor Enter the Password and Confirm it [FR-1, E-2]
iii. Actor Enter the Job Seeker Name [E-2]
iv. Actor Enter the Date of Birth [FR-2,E-2, E-3]
v. Actor Enter the email [FR-3, E-4, E-2]
vi. Actor Enter the country field [E-2]
vii. Actor submits the Data.
viii. System validates the data.
ix. The use case ends.

3.2 Alternative Flow(s)

Page 4 of 7
MyJobs System Version: 1.1
Use Case Specification: Register Job Seeker Issue Date: 30th March 2005
Document Identifier: - Author: Mansoor AbdulLateef

A-1: Exist Username

i. If the username is existed, the system will not allow an access to the other function of the
system and displays the message “User Name Is Exist”.
ii. The use case ends.

3.3 Exceptional Flow(s)

E-1: Empty fields

i. If the field is empty, the system will not allow an access to the other function of the
system and displays the message “Please fill all require fields.”.
ii. The use case ends.

E-2: Invalid date

i. If the date is invalid format, the system will not allow an access to the other function of
the system and displays the message “The date is Invalid”.
ii. The use case ends

E-3: Invalid email

i. If the email field string doesn’t contain ‘@’ and ‘.’, the system will not allow an access to
the other function of the system and displays the message “Invalid Email”.
ii. The use case ends.

4. Constraint(s)

Not applicable.

5. Post-Condition(s)

Post-condition of a use case is a list of possible states the system can be in immediately after a
use case has finished, as state below:

i. The user has registered into the system or access denied.

6. Fields and Rules

FR-1: Format of password

i. Length of password: six (6) characters
ii. Type of password : Alphanumeric

Page 5 of 7
MyJobs System Version: 1.1
Use Case Specification: Register Job Seeker Issue Date: 30th March 2005
Document Identifier: - Author: Mansoor AbdulLateef

FR-2: Format of date

i. Date : DD/MM/YYYY
ii. Type of Date : Numeric

FR-3: Format of email

The string of the email should contain ‘@’ and ‘.’ to be valid.

7. Extension Point(s)

Not applicable.

8. Note(s)

Not applicable
9. GUI(s)

G-1: Registration Form

Figure 2 Personal Field

G-2: Exist User Name

Page 6 of 7
MyJobs System Version: 1.1
Use Case Specification: Register Job Seeker Issue Date: 30th March 2005
Document Identifier: - Author: Mansoor AbdulLateef

Figure 3 Exist User Name

Page 7 of 7