Use Case ID: 5

Use Case Name: Employee Management Screen

Actor: Application User

Description: Employee Management Screen
Preconditions: 1. The user should have logged in to the Inventory
management system
2. The user should have clicked on Employee Management
tab
Postconditions: -Nil-
Priority: 1
Normal Course of Events: Following are the normal course of events.
1. Employee Management screen should contain the list of
Employees present and also a button named “Add
Employee” to enter new employee’s details
2. The SRl should have the “Name/Job Title”, “Employee
Code” “Designation”, “Mark as Inactive” “Edit Employee”
“Issue Assets”, “Return Assets” as the column headers.
(SRL should be blank initially with just the column names)
3. Button called “Mark as Inactive” should be present

Alternative Courses: -Nil-

Acceptance Criteria: 1. Given that the user logs into the application when the user
clicks on Employee Management button then the Employee
management screen should be seen. The screen should
contain the list of employees if any present and also a
button called Add Employee.
 Use Case ID: 6
Use Case Name: Creating a New Employee Profile

Actor: Application User

Description: Creating a New Employee Profile
Preconditions: 1. The user should have logged in to the Inventory
management system
2. The user should have clicked on Employee Management
tab
3. Department and Location field values should be fetched
from the database
Postconditions: -Nil-
Priority: 2
Normal Course of Events: Following are the normal course of events.
1. Clicking on the Add Employee button should open the
employee screen as seen in the mockup
2. The screen should have the below editable & Required
fields.
a. Text box with the label Employee Name
b. Text box with the label Employee Code
c. Dropdown with the list of the departments in the
company
d. Dropdown with the list of locations where the company
is present.
e. Date of Birth field with data format
f. A text box with the label name Designation
g. Text boxes with label names Address line 1,2,3
h. Dropdown to select State, Country and City
i. Text box with label Pin code
j. Email & Phone fields
k. Submit. Button to submit the details
3. Once all the details are filled the user can click on Submit
button.
4. The details should be saved successfully
Alternative Courses: -Nil-
Acceptance Criteria: 1. Given that the user is on the Employee management screen,
when the user clicks on Add Employee then the Employee
screen should be seen with the fields and their types
mentioned in the UC.
2. The fields should be required fields.
3. User should not be able to save the profile until all the
details are filled.
4. Once the profile is saved the employee details should be
seen in the employee list section
 Use Case ID: 7
Use Case Name: Editing an Employee Profile

Actor: Application User

Description: Editing an Employee Profile
Preconditions: 4. The user should have logged in to the Inventory
management system
5. The user should have clicked on Employee Management
tab
Postconditions: -Nil-
Priority: 3
Normal Course of Events: Following are the normal course of events.
1. In the Employee Management Screen. There should be a
list of Employees.
2. When the user clicks on the “Edit Employee” Icon the
Employee screen should open the employee screen in
editable format.
3. User should be able to edit any of the fields and then click
on Submit button. A message prompt should be given and
clicking on yes on the prompt should save the edited details
4. User should be able to edit only the employee,
Alternative Courses: Nil
Acceptance Criteria: 1. Given the user has clicked on the Edit button the employee
screen should open in the edit mode
2. Given that the user has edited fields and clicks on the
submit button then a prompt message and then the edited
details should be saved
 Use Case ID: 8
Use Case Name: Making an Employee Profile Inactive

Actor: Application User

Description: Making an Employee Profile Inactive
Preconditions: 1. The user should have logged in to the Inventory
management system
2, The user should have clicked on Employee Management tab
Postconditions: -Nil-
Priority: 4
Normal Course of Events: Following are the normal course of events.
1. In the employee management list, there should be a column
called Mark as Inactive with a butto. Once the button is
clicked, it should check if all the asset items are returned
for that particular employee
2. If all the asset items are returned, then a prompt displaying
“Are you sure you want to make this employee inactive”
should be seen. Clicking on yes should make the employee
inactive. Clicking on “No” should take the user back to the
list
3. If the assets are not returned for that particular employee,
then a prompt should be displayed to “Collect the particular
asset” back from the employee. Once this is done. User can
click on “Inactive” Button and step 2 should be followed
Alternative Courses: Nil
Acceptance Criteria: 1. When the button is clicked by the user firstly the
application should check if all the assets are returned, if
it’s not then a prompt should be displayed for collecting
the assets for that user
2. Once all the assets are returned then the user can make
the employee inactive.
3. Once the employee is inactive the user row should be
greyed out.
 Use Case ID: 9
Use Case Name: Issuing assets for a particular employee

Actor: Application User

Description: Issuing Assets for an employee
Preconditions: 1. The user should have logged in to the Inventory
management system
2. The user should have clicked on Employee Management
tab
Postconditions: -Nil-
Priority: 5
Normal Course of Events: Following are the normal course of events.
1. In the employee list, which is seen in the employee
management screen, when the user clicks on the Issue
Assets button then a new screen as shown in the
mockup should be seen
2. User can assign items to an employee by clicking on
the ‘+’ icon in the Items issued section
3. For a new employee there should be no assets and by
clicking on the ‘+’ icon it should add one row
4. There should be a dropdown under the asset item name
column from where the user can select the asset which
has to be assigned for the particular employee. This
field should be a combo box wherein the user can enter
the words and select from the dropdown also
5. The date of issue should be the default system date but
can also be changed it the user wants.
6. Once the details are entered the user can enter the
submit button to save the details. If the user does not
want to save the details the row can be deleted. Once
the entry is saved the row cannot be deleted
7. If the user wants to add another row, he has to click the
‘+’ icon, this should add another row. But the
previously added row should not be editable

Alternative Courses: A new asset type can be assigned to an employee from the
inventory tracker screen also. Assigning assets from both the places
should yield the same result
Acceptance Criteria: 1. The Asset item name field should be a combo box where in
the user can enter the asset item name and select the list from
the dropdown.
2. Adding multiple rows is allowed but the previously added
rows should be non-editable
 Use Case ID: 10
Use Case Name: Returning Asset

Actor: Application User

Description: Collecting an Asset already issued to an employee
Preconditions: 1. The user should have logged in to the Inventory
management system
2. The user should have clicked on Employee Management
tab
Postconditions: -Nil-
Priority: 6
Normal Course of Events: Following are the normal course of events
1. In the employee list, which is seen in the employee
management screen, when the user clicks on the Return
Asset button, return asset screen should be seen
2. The new screen should contain all the assets given to the
employee, and should contain the following columns
a. Asset code
b. Asset item name
c. Remarks
d. Return
e. Block Asset and a button called Return Asset Item
The name and code of the employee selected should be
displayed in the screen
3. The column “Return” should be checked by default for all
the assets, this can be changed by the user by clicking on
the checkbox. But by default, it should be checked
4. Remarks should be mandatory for returning the item
5. The user can click on the Return Asset Button and all the
assets returned should go back to the available pool of
assets
6. If the user clicks on “Block Assets” then the asset should be
listed out in the “Blocked Pool” and cannot be assigned to
any other employee
Alternative Courses: A new asset type can be returned from the inventory tracker screen
also. Assigning assets from both the places should yield the same
result
Acceptance Criteria: 1. Returning an asset should put the asset item back to the
available pool
2. If the asset is marked as blocked, then it should go the
blocked pool and then should not be available to be
assigned to any other employee
3. Remarks should be filled by the user before returning the
asset mandatorily