Use cases: Project Creation

Index 1.1 Administration...........................................................................................................1 1.1.1 Description Users set up.....................................................................................1 1.2 Operations..................................................................................................................2 1.2.1 Description Order new project............................................................................2 1.2.2 Description Change project request data............................................................2 1.2.3 Description Approve new project request...........................................................3 1.2.4 Description View requests enetered by me.........................................................3 1.2.5 Description View requests to be executed by me...............................................3 1.2.6 Description Add milestones................................................................................4 1.2.7 Description Attach documents............................................................................4 1.2.8 Description Ask for more details/negotiations...................................................5 1.2.9 Description Close the request.............................................................................5 1.2.10 Description Update milestone status.................................................................6 1.3 Reports.......................................................................................................................6 1.3.1 Request details....................................................................................................6 1.1 Administration
Use Case a

1.1.1 Description Users set up

Actors Admin Assumptions Steps Admin logs into portal Admin goes to User set up option. System opens up screen where add/edit facilities are there. Admin adds user o Admin enters user code, name, employee no,manager code,cost center code, department o Admin adds access rights Can reject? Can approve? Can close? Admin edits user o Admin selcts the user code and system fetches data for that user code o Admin edits data o Admin saves data Variations Non-Functional Issues

Page 1 of 7

Use cases: Project Creation

1.2 Operations
Use Case 1.0

1.2.1 Description Order new project

Actors Project orderer Assumptions Steps User logs into portal User goes to optionorder new project System opens up a screen with following fields o Project desciption o Attach documents o Expected reply by date o Estimated projct cost budget o Estimated time lines o Other expectations o Priority User enters all these details and saves the data User then submits the page System checs for mandatory fields System checks if approval is needed for this type of request o From admin set up If approval needed, system forwards this request to manager of the user o Find manager from user set up If approval not needed, system forwards this request to the factory user. o System finds eligible user from user set up,access rights,current load Variations Non-Functional Issues Use Case 1.1

1.2.2 Description Change project request data

Actors Project orderer Assumptions Steps User logs into portal User goes to his worklist of project requests User selects the request which he wants to change System opens the screen with request details, system also shows the status of the request. User changes the data If the request was already approved, system again sends this request to the same manager for approval. If approval was not needed then system forwards the changes to the factory user who is working on this request. Variations Non-Functional Issues

Page 2 of 7

Use cases: Project Creation

Use Case 1.2

1.2.3 Description Approve new project request

Actors Manager-customer Assumptions Steps Manager logs into portal Manager goes to his worklist Manager sees a request for aprpoval Manager opens the request System shows the details in read only format Manager can enter remarks Manager can either accept or reject the request. Manager accepts the request o System forwards the request to the owner of this request in the factor Manager rejects the request o System notifies the project orderer by email Variations Non-Functional Issues Use Case 1.3

1.2.4 Description View requests enetered by me

Actors User/Customer Assumptions Steps User logs into portal User goes to his worklist User can see all the live requests enetered by him Rejected/cancelled/closed requests can be seen for x no of days.This x no of days is set up in admin module. User selects one of the requests. System opens details of the requests. o System shows all the request data o System shows current status of the request o System shows flow details of the request for the stages through which it has passed. Variations Non-Functional Issues Use Case 1.3

1.2.5 Description View requests to be executed by me

Actors User/factory Assumptions Steps User logs into portal

Page 3 of 7

Use cases: Project Creation

User goes to his worklist User can see all the live requests owned by him Rejected/cancelled/closed requests can be seen for x no of days.This x no of days is set up in admin module. User selects one of the requests. System opens details of the requests. o System shows all the request data o System shows current status of the request o System shows flow details of the request for the stages through which it has passed. Variations Non-Functional Issues Use Case 1.4

1.2.6 Description Add milestones

Actors User/factory Assumptions Steps User logs into portal User goes to his worklist User can see all the live requests owned by him Rejected/cancelled/closed requests can be seen for x no of days.This x no of days is set up in admin module. User selects one of the requests. System opens details of the requests. o System shows all the request data o System shows current status of the request o System shows flow details of the request for the stages through which it has passed. User add milestones o System shows a tabular format where rows can be added o Columns Description Start date End date Effort/cost Status Remarks User saves the data Variations Non-Functional Issues Use Case 1.5

1.2.7 Description Attach documents

Actors User/factory Assumptions Steps

Page 4 of 7

Use cases: Project Creation

User logs into portal User goes to his worklist User can see all the live requests owned by him Rejected/cancelled/closed requests can be seen for x no of days.This x no of days is set up in admin module. User selects one of the requests. System opens details of the requests. o System shows all the request data o System shows current status of the request o System shows flow details of the request for the stages through which it has passed. User adds documents User saves the data Variations Non-Functional Issues Use Case 1.6

1.2.8 Description Ask for more details/negotiations

Actors User/factory Assumptions Steps User logs into portal User goes to his worklist User can see all the live requests owned by him Rejected/cancelled/closed requests can be seen for x no of days.This x no of days is set up in admin module. User selects one of the requests. System opens details of the requests. o System shows all the request data o System shows current status of the request o System shows flow details of the request for the stages through which it has passed. User goes to Ask more details section User enters required item list User saves data and submits it System takes the request back to owner of the request Variations Non-Functional Issues Use Case 1.7

1.2.9 Description Close the request

Actors User/factory or Customer user Assumptions Steps User logs into portal User goes to his worklist User can see all the live requests owned by him

Page 5 of 7

Use cases: Project Creation

Rejected/cancelled/closed requests can be seen for x no of days.This x no of days is set up in admin module. User selects one of the requests. System opens details of the requests. o System shows all the request data o System shows current status of the request o System shows flow details of the request for the stages through which it has passed. System shows this option as per user rights. User clicks close request button User needs to enter reaosn for closure User saves the data System nottifies the related users Variations Non-Functional Issues Use Case 1.8

1.2.10 Description Update milestone status

Actors User/factory Assumptions Steps User logs into portal User goes to his worklist User can see all the live requests owned by him Rejected/cancelled/closed requests can be seen for x no of days.This x no of days is set up in admin module. User selects one of the requests. System opens details of the requests. o System shows all the request data o System shows current status of the request o System shows flow details of the request for the stages through which it has passed. User edits milestone information User saves data Variations Non-Functional Issues

1.3 Reports 1.3.1 Request details

Stage Created Apporved Initiated Milestone creation Owner John Richard Kiran Kiran Date-time 23.06.2009 14:00 24.06.2009 10:00 25.06.2009 13:00 26.06.2009 13:00 Remarks

Page 6 of 7

Use cases: Project Creation

More details asked Status changed

John Kiran

28.06.2009 09:30 29.06.2009 16:30

Page 7 of 7