REAL TIME USECASE DOCCUMENT

ASSETS

1.                  Asset>Asset Category

Use case Name           : ASSET_ASSETCATEGORY

Use case ID                 : UC_ AMS_AST_ASTCAT01

Actor                          :  Admin, users and others,

Objective                     : To give assets details.

Pre-condition             : User should be logged into the system (in this

 Module) and should have privileges to navigate through Asset   tab.

Post-condition            : The web pages must be displayed with relevant details

Flow of events

Step	User Action	System Response	Relevant Data
1	User clicks on Assets in the home page of AMS	System will display the next page namely Asset category page	The fields CATEGORY_ID CATEGORY_NAME TOTAL_NUMBER Will be displayed with CATEGORY_ID has hyperlink
2	User click CATEGORY_ID field	A list box will appear	The list box consists of following fields SUBCATEGORY_NAME SUBCAT_TOTAL_NUMBER
3	User will choose one of them and clicks OK Button	System shall display ASSET_DETAILS page	This page consists of other sub links like DETAILS UPDATE PROJECTS HISTORY AUDIT DELETE TRANSFER
Alternate Course
4	User clicks on any of  the link	Pages may not be displayed
Exceptions
5	User clicks on any of the links application may hang

REVISION HISTORY

Date	Version	Description	Author

2.                  Asset>Asset Category>Details

Use case Name           : ASSET_ASSETCAT_DETAILS

Use case ID                 : UC_ AMS_AST_ASTCAT1.1_DETAILS

Actor                          :  Admin, users and others,

Objective                     : To give assets details.

Pre-condition             : User should be logged into the system (in this

 Module) and should have privileges to navigate through Asset   tab.

Post-condition            : The web pages must be displayed with relevant details

Flow of Events

Step	User Action	System Response	Relevant Data
4	User shall click on DETAILS link from the AssetCategory page	System displays DETAILS page with each individual asset Details	Data displayed are ASSET_ID CATEGORY_ID ASSET_NAME SUPPLIER_NAME USER_ID Where ASSET_ID and SUPPLIER_NAME are hyperlink
5	User shall select ASSET_ID	System will display ASSET_DETAILS_ASSET_ID Page	It consists of following fields ASSET_ID ASSET_NAME SUPPLIER_NAME USER PURCHASE_DATE PROPERTY_TYPE UNIT_COST DATE_OF_COMMISSION PROJECT_ID LIFE STATUS
6	If the user clicks on SUPPLIER_NAME hyperlink	System will establish link with SUPPLIER module	Supplier details are displayed
Alternate Course
7	User clicks on any of the  links	Application may not respond it may hang
Exceptions
8	All the different links must display the respective page when click action is performed

REVISION HISTORY

Date	Version	Description	Author

3.                  Asset>Asset Category>Update

Use case Name           : ASSET_ASSETCAT_UPDATE

Use case ID                 : UC_ AMS_AST_ASTCAT1.2_UPDATE

Actor                          :  Admin, users and others,

Objective                     : User can update the asset details.

Pre-condition             : User should be logged into the system (in this

 Module) and should have privileges to navigate through Asset   tab and perform updating.

Post-condition             : The web pages must be displayed with relevant details and            changes must reflected

Flow of Events

Step	User Action	System Response		Relevant Data
4	User shall click on UPDATE link from the Asset_Category page	System displays UPDATE page giving the users provision to update		Updation can be performed on the following fields ASSET_ID (auto generated), ASSET_NAME,  ASSET_CATEGORY, ASSET_CATEGORY_ID,ASSET_SUBCATEGORY, PURCHASE_DATE, DATE_OF_COMMISSIONING, PROPERTY_TYPE,SUPPLIER_NAME, UNIT_COST, LOCATION, PROJECT_ID, USER, LIFE, REGISTRATION_NO,MODEL_NO, SUPPLIER_ID, SUPPLIER_NAME, PURCHASE_DETAILS, INVOICE_NUMBER,TYPE_OF_TAX, TAX_PERCENTAGE, TOTAL_TAX, POLICY_NO, DURATION, STARTING_DATE, ENDING_DATE, POLICY_NAME, PREMIUM_AMOUNT, TOTAL_AMOUNT, DUE_DATE, MOUNT_AFTER_DUEDATE, MANUFACTURED_DATE, WARRANTY_PERIOD, START_WDATE, END_WDATE, AMC_COMPANY_NAME, AMC_PERIOD,AMC_STARTDATE,AMC_ENDDATE, AMC_RENEWALDATE, TOTAL_AMC_AMOUNT, AMC_PERSON,DEPRECIATION_BEGIN_DATE, DEPRECIATION_END_DATE, TOTAL_DEPRECIATION_PERIOD, CUMULATIVE_DEP_PERIOD,
5	User enter valid data for all the mandatory and optional fields and clicks on SUBMIT button	System shall save the updated asset details into the database		Update list shall be displayed
6	User can click on other links or return back to the homepage or logout
Alternate Course
7	User clicks on any of the links	System may not display the respective page.
8	User clicks on SUBMIT button	System may display error message	“Unable to save not possible to establish database connectivity”
9	User clicks on CANCEL or RESET button even before editing is completed	System should not perform any transaction
10	User enters invalid data to the fields	System accepts the invalid fields
Exceptions
11	Application may hang by the click of any hyperlinks
12	Unable to establish database connectivity

4.                  Asset>Asset Category>Projects

Use case Name           : ASSET_ASSETCAT_PROJECT

Use case ID                 : UC_ AMS_AST_ASTCAT1.3_PROJECT

Actor                          :  Admin, users and others,

Objective                     : User can view the assets in each projects

Pre-condition             : User should be logged into the system (in this

 Module) and should have privileges to navigate through out the application.

Post-condition             : Project details must be displayed

Flow of Events

Step	User Action	System Response	Relevant Data
4	User shall click on PROJECTS link	System displays Project page	The Project page consists of following fields PROJECT_ID PROJECT_NAME LOCATION PROJECT_HEAD STATUS DURATION Here PROJECT_ID is the hyperlink
5	User clicks on PROJECT_ID	System will display lists of assets  used in that particular project	It consists of following fields CATEGORY_ID TOTAL _NUMBER TOTAL _AMOUNT
6	If the user wants to transfer assets to project he/she will click on TRANSFER Tab which is available both at the top and bottom of the page	System shall provide link to the TRANSFER tab
7	User can click on any other link	System shall display corresponding web page
8	User clicks on Sign out	System logs out of the application
Alternate Course
7	User clicks on any of the  links	Application may not respond it may hang
Exceptions
8	All the different links must display the respective page when click action is performed

5.                  Asset>Asset Category>Transfer

Use case Name           : ASSET_ASSETCAT_TRANSFER

Use case ID                 : UC_ AMS_AST_ASTCAT1.4_PROJECT

Actor                          :  Admin, users

Objective                     :  This module transfers assets to surplus or retired and   from one       project to another

Pre-condition             : clear notification of to which project the assets should be transferred must be maintained

Post-condition            : Transfer of assets must be successfully carried out.

Step	User Action	System Response	Relevant Data
1	User shall click on TRANSFER link	System displays Transfer page	System will ask the user to enter ASSET_ID
5	User enters ASSET_ID on which transfer to be performed and clicks on OK button	System will display the details of the asset to be transferred and displays list box which has type of assets like SURPLUS, RETIRED, GENERAL ASSETS and PROJECT_ID list	ASSET_ID ASSET_NAME CATEGORY_NAME PROJECT_ID SUPPLIER_NAME PRICE DESCRIPTION
6	If the user shall the select the item in the list box and clicks on NEXT button	System shall display a calendar to enter transfer date	Calendar is displayed
7	User shall select the date of transfer and click NEXT button	System shall display the asset details and a list box of asset category appears	List box consists of different category name
8	User shall select the category or surplus from the list box	System displays the message for transfer notification	Message will be “ the request for transferring the asset is made on” TRANSFER_DATE shall be made.
7	User can click on any other link	System shall display corresponding web page
8	User clicks on Sign out	System logs out of the application
Alternate Course
9	User clicks on any of the  links	Link may not display the requested page
10	User click on NEXT button	Suitable modified action is not reflected on the page
Exceptions
8	All the users granted permission to transfer the asset

SUPPLIERS

1. SUPPLIER-PAGE

Usecase Name            :  Main Supplier Page

Usecase ID                  : UC_AMS_01_ SUPPLIER

Actor                          :  Admin, User (Employee)

Objective                     : To display the page of supplier.

Pre-condition             :  User should be logged into the system (in this

   Module) and should have privileges to view details.

Post-condition            : The details of supplier should be displayed.

  

                        Flow of events

Step	User Action	System Response	Relevant Data
1	User clicks on SUPPLIER hyperlink	System should display the Supplier Page.	Select the SUPPLIER or PROJECT tab. Select NEW tab to add new supplier or project.
Alternate Course
2
Exceptions
3	User clicks on SUPPLIER hyperlink, Page will not be displayed

REVISION HISTORY

Date	Version	Description	Author

2. SUPPLIER

Use case Name           : Supplier       

Use case ID                 : UC_AMS_02_SUPPLIER

Actor                          : Admin, User (Employee)

Objective                     : To display the list of suppliers.

Pre-condition             : User should be logged into the system (in this Module)

                                       and should have privileges to view/update/delete details.

Post-condition            : The list of suppliers should be displayed

Flow of events

Step	User Action	System Response	Relevant Data
1	User clicks on SUPPLIER Tab.	System should display the Supplier Page.	Select VENDOR (tab) or AGENT (tab).
Alternate Course
Exceptions
2	User clicks on SUPPLIER tab, Page will not be displayed

REVISION HISTORY

Date	Version	Description	Author

3. VENDOR

Usecase Name            : Vendor                    

Usecase ID                  : UC_AMS_03_VENDOR

Actor                          : Admin, User (Employee)

Objective                     : To view the vendor details.

Pre-condition             :  User should be logged into the system (in this

                                         Module)

Post-condition            : The details of the vendor should be displayed.

Flow of events

Step	User Action	System Response	Relevant Data
1 2 3          4 5 6 7 8 9 10 11	User clicks on VENDOR tab. User clicks on particular vendor User clicks on DETAIL tab. User clicks on VENDOR ID User clicks on UPDATE User clicks on BACK User clicks on UPDATE User clicks on AUDIT tab User clicks on DELETE User clicks on YES User clicks on NO	List of vendors should be displayed. Vendor page should be displayed All details of selected vendor should be displayed Purchase details page for selected vendor should open Update page should be opened It should go to the previous page It should update the information Audit page should be opened it will ask for continuation System should delete all traces of selected vendor System should not delete the traces of selected vendor	Select DETAILS or UPDATE or AUDIT or DELETE VENDOR ID, Vendor Name, Items, Total Cost, Project Id And Notes No. Of Item, Description, UOM, Cost/Item, GST, Total. Vendor Name*, Address*,         Postal*, Town*, Country*, Contact Person, Phone, Fax, Mobile, E-Mail, Link, Comments Select BACK or UPDATE Select YES or NO
Alternate Course
12 13	User clicks on UPDATE and required (*) fields are not filled User other than admin click on DELETE	Pop up message should be displayed Pop up message should be displayed	Pop up message” required (*) fields are not been filled”. Pop up message “ No privileges to delete”
Exceptions
14 15	Clicking on VENDOR, the page is not been displayed. Clicking on BACK, previous page is not been displayed

REVISION HISTORY

Date	Version	Description	Author

4. AGENT

Usecase Name            : Agent                      

Usecase ID                  : UC_AMS_04_AGENT

Actor                          : Admin, User (Employee)

Objective                     : To view the agent details.

Pre-condition             :  User should be logged into the system (in this

                                         Module)

Post-condition            : The details of the agent should be displayed.

Flow of events

Step	User Action	System Response	Relevant Data
1 2 3          4 5 6 7 8 9 10 11	User clicks on AGENT tab. User clicks on particular agent User clicks on DETAIL tab. User clicks on AGENT ID User clicks on UPDATE User clicks on BACK User clicks on UPDATE User clicks on AUDIT tab User clicks on DELETE User clicks on YES User clicks on NO	List of agent should be displayed. Agent page should be displayed All details of selected agent should be displayed Purchase details page for selected agent should open Update page should be opened It should go to the previous page It should update the information Audit page should be opened it will ask for continuation System should delete all traces of selected agent System should not delete the traces of selected agent	Select DETAILS or UPDATE or AUDIT or DELETE AGENT ID, Agent Name, Items, Total Cost, Project Id And Notes No. Of Item, Description, UOM, Cost/Item, GST, Total. Agent Name*, Address*, Postal*, Town*, Country*, Contact Person, Phone, Fax, Mobile, E-Mail, Link, Comments Select BACK or UPDATE Select YES or NO
Alternate Course
12 13	User clicks on UPDATE and required (*) fields are not filled User other than admin click on DELETE	Pop up message should be displayed Pop up message should be displayed	Pop up message” required (*) fields are not been filled”. Pop up message “ No privileges to delete”
Exceptions
14 15	Clicking on AGENT, the page is not been displayed Clicking on BACK, previous page is not been displayed

REVISION HISTORY

Date	Version	Description	Author

PROJECT

Usecase Name            : Project                     

Usecase ID                  : UC_AMS_05_PROJECT

Actor                          : Admin, User (Employee)

Objective                     : To view the projects listed.

Pre-condition             :  User should be logged into the system (in this

                                         Module)

Post-condition            : The list of projects should be displayed.

Flow of events

Step	User Action	System Response	Relevant Data
1 2 3          4 5 6 7 8 9	User clicks on PROJECT tab. User clicks on particular project id User clicks on DETAIL tab. User clicks on UPDATE User clicks on BACK User clicks on UPDATE User clicks on DELETE User clicks on YES User clicks on NO	List of projects should be displayed Project page should be displayed All details of selected project should be displayed Update page should be opened It should go to the previous page It should update the information it will ask for continuation System should delete all traces of selected project System should not delete the traces of selected project	Select particular project Select DETAILS or UPDATE or DELETE Project id, Project Name, Status, Contact person, Location and Duration Project id*, Project Name*, Status, Contact person, Location, Client Select BACK or UPDATE Select YES or NO
Alternate Course
10 11	User clicks on UPDATE and required (*) fields are not filled User other than admin click on DELETE	Pop up message should be displayed Pop up message should be displayed	Pop up message” required (*) fields are not been filled”. Pop up message “ No privileges to delete”
Exceptions
12 13	Clicking on PROJECT, the page is not been displayed Clicking on BACK, previous page is not been displayed

REVISION HISTORY

Date	Version	Description	Author

IMPORT

Use case Name:          Import

Use case ID                 : UC_ AMS_07_IMPORT

Actor                          :  Admin, User (Employee)

Objective                     : To import information from spreadsheets

Pre-condition             : User should log on the system (in this

   Module) and should have privileges to import details.

Post-condition            : Information should be imported

Flow of events

Step	User Action	System Response	Relevant Data
1	User clicks on IMPORT	System should displays the list of information that can be imported	IMPORT EMPLOYEE INFORMATION, IMPORT ASSET INFORMATION, IMPORT SUPPLIER INFORMATION, IMPORT PROJECT INFORMATION
2	User clicks on required link	System should display a page containing the different import fields.	Import file (list box), File name (edit box),  BROWSE (button), PREVIEW (button), OK (button), CANCEL (button)
Alternate Course
3	Click on PREVIEW button	Preview page  should    not be displayed	Error message shall be displayed “ Unable to display the preview”
4	User clicks on IMPORT	Page  should  not be displayed	Error message “Response time is very low”
Exceptions
5	User clicks on OK and the file will not be imported
8	User clicks on cancel rather than OK after browsing the file

REVISION HISTORY

Date	Version	Description	Author

HELP

Use case Name           : Help

Use case ID                 : UC_ AMS_08_HELP

Actor                          :  Admin, User (Employee), other user

Objective                     : To find required information

Pre-condition             : Help tab should be present

Post-condition            : pages containing relevant information should be displayed.

Flow of events

Step	User Action	System Response	Relevant Data
1 2 3 4 5	User clicks on HELP User clicks on  FEATURES link User clicks on  FAQ link User clicks on  COMMON PROCESS link User clicks on   Search edit box	System  should  displays the help page System  should  display a page containing the user and admin privileges System  should  display a page containing the FAQ about software System  should  display a page containing the information about Software handling Cursor should be present in the search edit box	FEATURES, FAQ, COMMON PROCESS, Search(edit box), GO(button)

6	User enters the required query in edit box and clicks on GO	System should display the relevant information
Alternate Course
7	User clicks on GO without entering any query in edit box	Page will not be displayed
Exceptions
8	Clicking on HELP , relevant page is not displayed

REVISION HISTORY

Date	Version	Description	Author

REPORT

Use case Name           : Report

Use case ID                 : UC_ AMS_09_REPORT

Actor                          :  Admin, User (Employee)

Objective                     : To find required reports

Pre-condition             : User should log on the system (in this

   Module) and should have privileges.

Post-condition            : pages containing relevant reports should be displayed.

Flow of events

Step	User Action	System Response	Relevant Data
1 2 3 4 5 6 7 8 9	User clicks on REPORT User clicks on  Detailed asset report User clicks on   Asset report project wise User clicks on   Asset report location wise User clicks on   Transfer report - Surplus to retired User clicks on   Transfer report - Surplus to general asset User clicks on   Transfer report - General asset to Surplus User clicks on   Transfer report - General asset to retired User clicks on employees report	System  should  displays the page containing reports System  should  displays the relevant report System  should  displays the relevant report System  should  displays the relevant report System  should  displays the relevant report System  should  displays the relevant report System  should  displays the relevant report System  should  displays the relevant report System  should  displays the relevant report	Detailed asset report, Asset report project wise, Asset report location wise, Transfer report - Surplus to retired, Transfer report - Surplus to general asset Transfer report - General asset to Surplus, Transfer report - General asset to retired, Employees report, Detailed supplier report, Project report, Depreciation report Audit report- asset wise Audit report- location wise Audit report- project wise Audit report- supplier wise Asset Tag, Asset Name, Asset Type, Price, Date Of Purchase Asset Tag, Asset Name, Project id, project name Asset Tag, Asset Name, location id Asset tag, asset name Asset Tag, Asset Name Asset Tag, Asset Name Asset Tag, Asset Name Employee Id , Employee Name, Location, Project name

10 11 12 13 14 15 16

User clicks on Detailed supplier report User clicks on   Project report User clicks on    depreciation report User clicks on  Audit report- asset wise   User clicks on  Audit report- location wise   User clicks on  Audit report- project wise User clicks on  Audit report- supplier wise

system should displays the relevant report System  should  displays the relevant report System  should  displays the relevant report System  should  displays the relevant report System  should  displays the relevant report System  should  displays the relevant report System  should  displays the relevant report

Suppler id, supplier name (vendor or agent), project name, no of items supplied, total cost. Project id, project name, status, employee id, asset id Asset name, cost, method, category, period beginning and ending total period, depreciation rate, cumulative depreciation- annually/ monthly/ quarterly,  net amount Asset id, asset name, changed by, changed on Asset id, asset name, changed by, changed on, location Asset id, asset name,  project id , project name, changed by, changed on Asset id, asset name, supplier id, supplier name, changed by, changed on

Alternate Course
Exceptions
17	Clicking on REPORT, relevant page is not displayed

REVISION HISTORY

Date	Version	Description	Author

DEPRECIATION

1. DEPRECIATION PAGE

Use case Name           : Depreciation Page

Use case ID                 : UC_AMS_DP_01

Actor                          :  User

Objective                     : To open the depreciation calculator.

Pre-condition             : Depreciation link should be there in main page.

Post-condition            : It should calculate the depreciation for a given period and should

                                        Give the cumulative depreciation, net amount, annual amount.

                                       

  

    Flow of events

Step	User Action	System Response	Relevant Data
1	User clicks on ‘Depreciation’ link in main page.	System will display the ‘Depreciation’ Page.	“Depreciation” link should be present in main page Page should be contain following mandatory fields. Ø  Cost Ø  Method Ø  Asset Name Ø  Category And optional fields are Ø  Period beginning Ø  Period Ending Auto generate fields Ø  Depreciation Rate Ø  Cumulative                       Depreciation Ø  Net Amount Ø  Annual Amount Ø  Depreciation Table
Alternate Course
2	User may highlight the link & clicks the enter button.	System will display the ‘Depreciation’ Page.
Exceptions
3	The ‘Depreciation’ page may not be displayed.

REVISION HISTORY

Date	Version	Description	Author

2. Depreciation Calculation

Use case Name           : Depreciation Calculation    

Use case ID                 : UC_AMS _DP_02

Actor                          : User

Objective                     : To calculate the depreciation.

Pre-condition             :   User should know asset name, cost, category method.

Post-condition            :  Calculator should calculate depreciation rate.

Flow of events

Step	User Action	System Response	Relevant Data
1 2	User enters valid cost, method, category, asset name User enters valid data in period beginning, period ending & clicks on calculate	System will accept all the data System will calculate total period, depreciation in the table along with annual amount, cumulative depreciation  & net amount.	The default values should be present in the period beginning & period ending( i.e. system rate). Depreciation table should be empty. After depreciation calculation the export print & report button will be enabled & it prompts user to choose any one.
Alternate Course
1 2 3 4 5	User enters invalid data into mandatory fields. User enters invalid data into optional fields User enters valid data in all the fields & press “export” button User enters valid data into mandatory fields & press “print report” button User clicks close button in the middle	System will gives error message. System will gives error message. System will give the error message “cannot export without calculating” System will give the error message “ cannot print without calculating” Depreciation calculation closes without saving the data.
Exceptions
1 2 3	It will not calculate depreciation. It will not print the report. It will not export the sheet.

REVISION HISTORY

Date	Version	Description	Author

3. DEPERCIATION EXPORT

Use case Name           : Depreciation Export            

Use case ID                 : UC_AMS_DP _03

Actor                          :  User

Objective                     :  To export the calculated depreciation

Pre-condition             :  Should calculate depreciation for an existing assets

Post-condition            :  Successful export of the depreciation details

Flow of events

Step	User Action	System Response	Relevant Data
1	User enters valid data in all the fields ,calculates the Dep’n & clicks “Export” button	System will export all the Depreciation details to the particular asset page	We can see the Depreciation details in the particular asset page
Alternate Course
1.
Exceptions
1	It will not export the depreciation sheet to Assets
2

REVISION HISTORY

Date	Version	Description	Author

4. PRINT REPORT

Use case Name           : Print Report            

Use case ID                 : UC_AMS_DP _04

Actor                          : User

Pre-condition             :  Depreciation should be calculated, Printer should be connected

                                        To the system.

Post-condition            :   Successful printing of Depreciation report.

Flow of events

Step	User Action	System Response	Relevant Data
1	User enters valid data in all the fields ,calculates the Dep’n & clicks “Print Report” button	Printer will prompts the user to printing option & the requested page will be printed	Various printing option can be seen with print preview
Alternate Course
2.
Exceptions
1. 2 3.	Printer will not be connected to the system . Papers will not be inserted . Printer will be switched off.

REVISION HISTORY

Date	Version	Description	Author

NEW

Adding Assets, Projects, Users and Suppliers

                                  

Usecase Name            : Adding New Asset             

Usecase ID                  : UC_ AMS_NEW_ASSET

Actor                          :  .SuperAdmin, Admin,User (Employee) and others

Objective                     : To add new asset details

Pre-condition             : User should log on the system (in this

   Module) and should have privileges to add Asset details.

Post-condition            : Asset should be created and should be displayed.

Flow of events

Step	User Action	System Response	Relevant Data
1	User clicks on the hyperlink NEW	System will displays the list of items that can be added	Items are ASSETS, SUPPLIERS, USERS and PROJECTS
2	User then clicks on Asset link	System will display a blank web page containing the different blank fields.	ASSET_ID (auto generated), ASSET_NAME, ASSET_CATEGORY, ASSET_CATEGORY_ID,ASSET_SUBCATEGORY, PURCHASE_DATE, DATE_OF_COMMISSIONING, PROPERTY_TYPE,SUPPLIER_NAME, UNIT_COST, LOCATION, PROJECT_ID, USER, LIFE, REGISTRATION_NO,MODEL_NO, SUPPLIER_ID, SUPPLIER_NAME, PURCHASE_DETAILS, INVOICE_NUMBER,TYPE_OF_TAX, TAX_PERCENTAGE, TOTAL_TAX, POLICY_NO, DURATION, STARTING_DATE, ENDING_DATE, POLICY_NAME, PREMIUM_AMOUNT, TOTAL_AMOUNT, DUE_DATE, AMOUNT_AFTER_DUEDATE, MANUFACTURED_DATE, WARRANTY_PERIOD, START_WDATE, END_WDATE, AMC_COMPANY_NAME, AMC_PERIOD,AMC_STARTDATE,AMC_ENDDATE, AMC_RENEWALDATE, TOTAL_AMC_AMOUNT, AMC_PERSON,DEPRECIATION_BEGIN_DATE, DEPRECIATION_END_DATE, TOTAL_DEPRECIATION_PERIOD, CUMULATIVE_DEP_PERIOD, DEP_NET_AMOUNT, DEP_METHOD_USED, DEP_RATE
3	User enters all the mandatory and optional fields with valid data and clicks on SAVE button	All the fields pertaining ASSET is saved in the database	All the Asset Details are displayed for view.
Alternate Course
4	Adding NEW ASSET Failed	System will not display the ASSET page	Message is displayed as “Unable to open the web page”
5	Clicking on NEW link or trying to save	Application may hang
6	Click on save button	Unable to save in the database	Error message shall be displayed “Unable to save in the database or database not found”
7	User clicks on Asset hyperlink	Page will not be displayed	Error message “Response time is very low”
Exceptions
8	User clicking on adds NEW-Asset, the screen will not appear.
9	Does not  allow Editing New Asset Content
10	Wrong Validated data can be accepted
11	Unable to save even after click on save button action is performed
12	User clicks on cancel or reset button even before save button is clicked

REVISION HISTORY

Date	Version	Description	Author

NEW- PROJECTS

Use case Name           : Adding New Project                       

Use case ID                 : UC_ AMS_NEW_PROJECTS

Actor                          :  Admin, User (Employee)

Objective                     : To add new Project details

Pre-condition             : User should log on the system (in this

   Module) and should have privileges to add Asset details.

Post-condition            : Project should be created and should be displayed

Step	User Action	System Response	Relevant Data
1	User clicks on the hyperlink NEW	System will displays the list of items that can be added	Items are ASSETS, SUPPLIERS, USERS and PROJECTS
2	User then clicks on Projects link	System will display a blank web page containing the different fields.	PROJECT_ID (auto generated), PROJECT_NAME, LOCATION, PROJECT_HEAD
3	User shall enter all the mandatory and optional valid fields and clicks on save button	All the fields are saved in the database	All the project details are displayed for view
Alternate Course
4	Adding NEW ASSET Failed	System will not the  add new courses
5	Clicking on NEW link or trying to save	Application may hang
6	Click on save button	Unable to save in the database	Error message shall be displayed “Unable to save in the database or database not found”
7	User clicks on Project Hyperlink	Page will not be displayed	Error message “Response time is very low”
Exceptions
5	User clicks on add NEW-Project, the screen will not appear.
6	Does not  allow Editing New Project Content
7	Validation for each field not maintained
8	User clicks on cancel or reset button even before the contents are saved

REVISION HISTORY

Date	Version	Description	Author

3. NEW-EMPLOYEE

Usecase Name            :  New

Usecase ID                  : UC_AMS_06_ NEW

Actor                          :  Admin, User (Employee)

Objective                     : To display the page of supplier.

Pre-condition             :  User should be logged into the system (in this

   Module) and should have privileges to add new supplier and project.

Post-condition            : The new supplier and project should be added.

  

Flow of Events

Step	User Action	System Response	Relevant Data
1 2 3 4 5 6 7 8 9 10 11 12 13 14	User clicks on NEW Tab User clicks on NEW SUPPLIER User clicks on New Vendor User clicks on RESET User clicks on ADD User clicks on CANCEL User clicks on New Agent User clicks on RESET User clicks on ADD User clicks on CANCEL User clicks on NEW PROJECT User clicks on RESET User clicks on ADD User clicks on CANCEL	System should display the page for adding new supplier and project Page for adding New Supplier should be displayed Page for adding New Vendor should be displayed It should reset all the fields It should add new vendor It should go to the previous page Page for adding New Agent should be displayed It should reset all the fields It should add new agent It should go to the previous page Page for adding New Project should be displayed It should reset all the fields It should add new project It should go to the previous page	Select the NEW SUPPLIER or NEW PROJECT. Select New Vendor or New Agent Vendor Name*, Address*, Postal*, Town*, Country*, Contact Person, Phone, Fax, Mobile, E-Mail, Link, Comments Click on RESET or ADD or CANCEL Agent Name*, Address*, Postal*, Town*, Country*, Contact Person, Phone, Fax, Mobile, E-Mail, Link, Comments Click on RESET or ADD or CANCEL Project id*, Project Name*, Status, Contact person, Location, Client Click on RESET or ADD or CANCEL
Alternate Course
Exceptions

NEW-   CLIENT

5. Client Registration link

Use case Name           : Client Registration link                   

Use case ID                 : UC_AMS_CL _01

Actor                          : User

Pre-condition             :  Client registration link should be present.

Post-condition            : .Client registration page should open.

Flow of events

Step	User Action	System Response	Relevant Data
1	User clicks on “Register me as client” link	System opens client registration page	“Register me as client “ link should be presenting main page.and page should contain following fields Client ID, client name, Address, country, state, Phone no , Zip, E-mail, Fax, Contact person.
Alternate Course
2.
Exceptions
1. 2	The Client registration page will not open. The system may crash.

REVISION HISTORY

Date	Version	Description	Author

                                                                  

                                                                  

6. Client Registration.

Use case Name           : Client Registration .            

Use case ID                 : UC_AMS_CL _02

Actor                          : User

Pre-condition             :  Client registration page should be present.

Post-condition            : .Client registration request should go to Super Administrator.

Flow of events

Step	User Action	System Response	Relevant Data
1 2.	User enters all the fields in client registration form with valid data and clicks on “ok” button. User clicks on “submit” button	System accepts all the data and validates it System sends all the data to Super Administer’s page.	“ok” button should be present. Registration page should contain following fields Client ID, client name, Address, country, state, Phone no , Zip, E-mail, Fax, Contact person. “ok” and  “submit” buttons should be enabled “Submit” button should present.
Alternate Course
2.	User enters invalid data in to fields and clicks on “ok”, ”submit” button	System will give proper error message.
Exceptions
1. 2 3.	The edit fields will not take the values entered. When you press “submit” button data will not be sent to Super admin When “cancel” button is pressed the page will be closed.

REVISION HISTORY

Date	Version	Description	Author

                                                                  

7. Client Registration conformation.

Use case Name           : Client Registration conformation.              

Use case ID                 : UC_AMS_CL _03

Actor                          : User

Pre-condition             :  Client should  register all the relevant data.

Post-condition            : .Client registration request should be processed and he should get   

                                         a mail , an URL should be created for client in main page.

Flow of events

Step	User Action	System Response	Relevant Data
1	User enters all the fields in client registration form with valid data and clicks on “ok” and “submit” button	Super Administrator validates all the data  sends a mail to client and creates a new link in main page .	“ok”  and “submit” buttons should be present.
Alternate Course
2.	User enters invalid data in to fields and clicks on “ok”, ”submit” button	Super Administrator invalidates the data  sends a mail to client .
Exceptions
1. 2. 3. 3.	User enters the valid data click on submit button but Super admin will not get the information. User will not get the conformation mail. The new URL will not be created. When “cancel” button is pressed the page will be closed.

REVISION HISTORY

Date	Version	Description	Author

RETIRED ASSETS

DETAILS

Use case Name           : Details of Assets

Use case ID                 : UC_AMS_RA_01_DETAILS

Actor                          : Admin, Manager

Objective                     : Gives the assets details

Pre-condition             : User should be logged into the system (in Assets Management

                                       Module)

Post-condition            : The assets should be show the details

Flow of events

Step	User Action	System Response	Relevant Data
1	User selects the assets_id from the list.	System will display the related data for that assets_id.	·     Assets_id ·     Assets  Name ·     Supplier Name ·      Description ·      Day ·     Date
2.	User clicks on the Details button.	System Will Display details of the assets.
Alternate Course
3	details assets fails in Step 2	System will display a message on why the assets details are not appear.	System still displays the assets name.
Exceptions

REVISION HISTORY

Date	Version	Description	Author

TRANSFER

Use case Name           : Transfer of Assets

Use case ID                 : UC_AMS_RA_02_TRANSFER

Actor                          : Admin, Manager, User

Objective                     : To transfer the assets details

Pre-condition             : Clear notification of to which project the assets should be      

                                        transferred must be maintained.

Post-condition            : Transfer of assets must be successfully carried out.

Flow of events

Step	User Action	System Response	Relevant Data
1	User shall click on TRANSFER link	System displays Transfer page	System will ask the user to select ASSET_ID
2	User selects the assets_id on which transfer to be performed and click on OK button.	System will display the related data for that assets_id.	Assets_id Assets Type Supplier Name Module Reg. No. Description  Day  Date Time
Alternate Course
Exceptions
5	Confirmation message window is not displayed

REVISION HISTORY

Date	Version	Description	Author

HISTORY

Use case Name           : History

Use case ID                 : UC_AMS_RA__03_HISTORY    

Actor                          : Admin, Manager.                

Objective                     : To display the history of all activities by assets.

Pre-condition             : should be logged into the system.

Post-condition            : view of history of all activities.

Flow of events

Step	User Action	System Response	Relevant Data
1	User clicks on assets-id.	System will display the history of all activities.
Alternate Course
2	System will fails in step 1	System will display a message on why the link failed.
Exceptions
3.	Not present

REVISION HISTORY

Date	Version	Description	Author

DELETE

Use case Name           : Delete Assets

Use case ID                 : UC_AMS_RA_05_DELETE

Actor                          : Super admin, Admin, Manager

Objective                     : To delete assets details.

Pre-condition             : User should be logged into the system (in Assets Management

                                       Module) and should have privileges to delete assets details.

Post-condition            : The assets should be deleted and should not be present in    

                                        other module.

Flow of events

Step	User Action	System Response	Relevant Data
1	User selects the assets_id from the list.	System will display the related data for that assets_id.	Assets_id Assets Type Supplier Name  Description  Day Date Time
2.	User clicks on the Delete button.	System Will Display a dialog box for Confirmation.
3.	User click on yes button on confirm message window	System will display an message “ Deleted Successfully “
4.	User click on No button for “confirm message” window.	System Will return to assets Modification Screen	All Field data will be retained.
Alternate Course
5	Delete assets fails in Step 3	System will display a message on why the Delete failed and no assets details are deleted.	System still displays the assets Details.
Exceptions
6.	Confirmation message window is not displayed

REVISION HISTORY

Date	Version	Description	Author

 LOGIN

1) Main Login Page

Usecase Name            : Main login page

Usecase ID                  : UC_AMS_01_Mloginpage

Actor                          :  Super Admin

Objective                     : To add list of Clients.

Pre-condition             : Client should register in the website.

Post-condition             : Client should be added in the hyperlink list successfully..

                        Flow of events

Step	User Action	System Response	Relevant Data
1	User clicks on list of Clients User clicks on Register Tab User clicks on Submit button	System displays the clients in the drop down list System will display the Registration form. System displays message to reconfirm the details	First name, Last name, Client Name, Address, State, Zip, Phone number, Mobile number, Email, Fax
Alternate Course
2	User may click on cancel while filling the registration form. User has left the fields blank in the form	Unable to generate hyperlink for client System throws message to enter details in all the fields
Exceptions
3	User clicks on links and it does not open page

REVISION HISTORY

Date	Version	Description	Author

2) Login Page for Client, Users and Other users

Usecase Name            : Login page for Clients                    

Usecase ID                  : UC_AMS_02_Loginpage

Actor                          : Admin, Users and Other users

Objective                     : Creation of Accounts for Users and Other users

Pre-condition             :  User should have valid username and password.

Post-condition            : User should be successfully logged into the Application.

Flow of events

Step	User Action	System Response	Relevant Data
1	User enters username and password and clicks on login button User clicks on Change password User enters password and clicks on confirm	System validates username and password and displays home page System displays the change password screen System sets to new password	Old password, New password and Retype password
Alternate Course
2	User clicks on cancel button before completely entering login information User has entered invalid data for retype password	System closes the login page System gives error message “retype password”
Exceptions
3

REVISION HISTORY

Date	Version	Description	Author

3. Users

Usecase Name            : User details

Usecase ID                  : UC_AMS_03_User details

Actor                          : Admin,User and Other Users

Objective                     : To View and Update user information

Pre-condition             :  User should be logged into the system  and should have the                                                  

                                         Privileges.

Post-condition            : User should be able to View and Update details successfully.

Flow of events

Step	User Action	System Response	Relevant Data
1	User clicks on Users link in the home page User clicks on Details tab User clicks on Update tab User clicks on Update button User clicks on Delete tab	System will display the Users screen System displays the user details System displays details for user to update the required data System updates the user details System displays error message “Access denied” to Users and Other Users	Screen has Details, Update and Delete tabs Employee ID, First name, Last name, List of Clients handled Employee Id, First name, Last name, Address, Phone number, Mobile number, Email, Fax number, Department, List of clients handled
Alternate Course
2.	User does not click on update button User may click on Reset or Cancel button while updating the details	System will not update the user detail changes System does not update the user detail changes
Exceptions
3	User has entered incorrect information and clicked on update

REVISION HISTORY

Date	Version	Description	Author

4) About US

Usecase Name            : Information about AMS     

Usecase ID                  : UC_AMS_04_About US page

Actor                          : Admin, Users and Other users

Objective                     :

Pre-condition             :  User should have valid username and password.

Post-condition            : Information page should be displayed

Flow of events

Step	User Action	System Response	Relevant Data
1	User enters username and password and clicks on login button User clicks on About US	System validates username and password and displays home page System displays the Information page
Alternate Course
2	User enters invalid data	System gives error message “enter valid data”
Exceptions
3	User clicks on About us link and page does not open

REVISION HISTORY

Date	Version	Description	Author