project title€¦ · web viewcheck payments use case id cssc-23 author auditor general...

Catering S uppo r t S e rvi c e Compa n y

Software Requirements Specification

Version 1.0

Group Id: Supervisor Name : Sarfraz Ahmad Awan

Revision HistoryDate

(dd/mm/yyyy)Version Description Author

Current date 1.0 Catering Support Service Company is into a wide range of catering operations including workers camps, cafeterias, canteens, banquets and outdoor catering services, This company also operates different accommodation complexes that provide a complete package of serviced housing including catering, housekeeping, laundry and other hospitality services for a variety of customers. With its base at a city, the company’s operations are spread over a wide territory of a country. Following is an overview structure of our organization.

Mc110401925

Table of Contents

1. Scope (of the project)

2. Functional Requirements Non Functional requirements

3. Use Case Diagram

4. Usage Scenarios

5. Adopted Methodology

6. Work Plan (Use MS Project to create Schedule/Work Plan)

SRS DocumentScope of Project: The main aim of this project is to provide a better system to the sites to handle all their daily stock related activities digitally. So, that the stock can be managed at the individual sites and the performance of the sites can be monitored and can be audited as well. Also To produce a simple, yet suitably effective user friendly interface and a system that is easily maintainable, efficient and practical.

Functional Requirements: The system will allow the administrator to add/edit/delete area offices. The system will allow the administrator to add/edit/delete supervisor for each

area. The system will allow the administrator to add/edit/delete auditor which can audit

the all operation of every area. The system will allow the administrator to add/edit/delete accountant which can

audit the all operation of every area. The system will allow the store keeper to add/edit/delete items. The system will allow the store keeper to issue items according to advice of

operation manager. The system will allow the store keeper to issue items. Storekeeper can check all the balance of its items. Storekeeper will receive requests from operation manager. The system will allow the supervisor to check orders. The system will allow the supervisor to check payments of orders. The system will allow the supervisor to allot the projects. The supervisors will add/edit/delete the worker. The system will allow to add/edit/delete the project managers. The system will allow to add/edit/delete the operations manager. The system will allow operations manager to allot manpower. Operations manager will allot required items. The operations manager will view orders. The operations manager can make requests to store keeper. The general auditor can check the all orders. The general auditor can check consumption records of all items (food, non-food,

assets). The general auditor can check the all payments by the customers. The general auditor can check the balance sheets. The general auditor can mark on projects. The customer can make orders.

The customer selects occasion type, menu, date and time of the party/occasion. The customer can check the order status. The customer will be issued a voucher for payment.

Non Functional Requirements: The system will be easy to use (user friendly). The system will use less data and space. Data entry and search data entry. Information retrieval will be fast. Less manpower will be required when system will be deployed. All the operations will be accurate and accountable. Data of all projects can be imported and exported. System should be capable of supporting multiple users without affecting its

performance.

Use Case Diagram(s):

Usage Scenarios:

1. Add/Edit/Delete Area OfficeUse Case ID CSSC-01Author AdministratorDescription Administrator will be able to add/edit/delete the area offices.Pre-Conditions Administrator is logged in and database is connected.Post Conditions Success: The data about area office will be saved/deleted or

updated in database of the system.Failure: The database contents will remain unchanged.

Main Success Scenario The administrator will login first.The administrator will enter the all data about the office.The system will validate the information.A message will be displayed.Use case ends.

Alternative Scenario If administrator doesn’t want to save the records then he press the cancel button. The record is not saved in the database and use case is ended.

Exception The system will generate exception if the data is incorrect or data is already is present in the database.

2. Add/Edit/Delete SupervisorUse Case ID CSSC-02Author AdministratorDescription Administrator will be able to add/edit/delete the area

supervisor.Pre-Conditions Administrator is logged in and database is connected.Post Conditions Success: The data about area office will be saved/deleted or


Main Success Scenario The administrator will login first.The administrator will enter the all data about the supervisor.The system will validate the information.A message will be displayed.Use case ends.



3. Add/Edit/Delete General AuditorUse Case ID CSSC-03Author AdministratorDescription Administrator will be able to add/edit/delete the General

Auditor.Pre-Conditions Administrator is logged in and database is connected.Post Conditions Success: The data about area office will be saved/deleted or





4. Add/Edit/Delete StorekeeperUse Case ID CSSC-04Author AdministratorDescription Administrator will be able to add/edit/delete the storekeeper

of each area.Pre-Conditions Administrator is logged in and database is connected.Post Conditions Success: The data about area office will be saved/deleted or





5. Make OrderUse Case ID CSSC-05Author CustomerDescription The customer will be able to make order. Pre-Conditions The customer will visit the desired page.Post Conditions Success: The data about the order will be saved in database of

the system.Failure: The database contents will remain unchanged.

Main Success Scenario The customer visits the page.Enter all the information about the order.Enter his bio data.Presses the order button.

Alternative Scenario If customer doesn’t want to make order then he presses the cancel button and leaves the page.


6. Select Occasion/Menu/Date/TimeUse Case ID CSSC-06Author CustomerDescription The customer will select the occasion type like marriage,

party, engagement ceremony etc. The menu to be served , date and time will be selected by the customer.

Pre-Conditions The customer is on the order page.Post Conditions Success: The data about area order will be saved in database

of the system.Failure: The database contents will remain unchanged.

Main Success Scenario The customer visits the page.Customer selects the appropriate occasion, menu, date, time.Use case ends.



7. Generate VoucherUse Case ID CSSC-07Author CustomerDescription The customer will be able to generate voucher for the

payment of his order. Pre-Conditions The customer will visit the desired page. Saved all the

information about the order.Post Conditions Success: The voucher will be generated by the system.

Failure: The system will generate the exception.Main Success Scenario The customer visits the page.

Enter all the information about the order.Enter his bio data.Presses the order button.



8. Order StatusUse Case ID CSSC-08Author CustomerDescription The customer will visit the order page and enters his order ID

and presses view order.Pre-Conditions The customer is on the order page.Post Conditions Success: The data about the order will be displayed on the

page.Failure: The system will show an error message.

Main Success Scenario The customer visits the page.Customer enters the order ID and views its order details.Use case ends.

Alternative Scenario If customer doesn’t made any order previously then no data will be displayed.

Exception The system will generate exception in case of the error.

9. Check OrderUse Case ID CSSC-09Author SupervisorDescription The supervisor will be able to check order. Pre-Conditions The supervisor is logged in and database is connected.Post Conditions Success: The data about the order will be saved in database of


Main Success Scenario The supervisor visits the page.View all the information about the order.Enter his comments.Presses the save button.

Alternative Scenario If the supervisor doesn’t want to mark order then he presses the cancel button and leaves the page.


10. Check PaymentsUse Case ID CSSC-10Author SupervisorDescription The supervisor will be able to check payments made by the

customers.Pre-Conditions The supervisor is logged in and connected to database.Post Conditions Success: The supervisor will be able to check payments made

by the customers.Failure: The database contents will remain unchanged.

Main Success Scenario The customer visits the page.Customer selects the appropriate occasion, menu, date, time.Use case ends.



11. Add/Edit/Delete Operation ManagerUse Case ID CSSC-11Author SupervisorDescription The supervisor will be able to add/edit/delete operations

manager to each project. Pre-Conditions The supervisor is logged in and database is connected.Post Conditions Success: The data about the operation manager is

add/edit/deleted in the system.Failure: The database contents will remain unchanged.

Main Success Scenario The supervisor log in the page.The supervisor enters/selects the data about the operation manager to add/edit/delete.Supervisor press the button to add/edit/delete.Appropriate message is shown by the system.Use case ends.

Alternative Scenario If the supervisor does not want to add/edit/delete the operations manager he presses the cancel button.


12. Add/Edit/Delete WorkerUse Case ID CSSC-12Author SupervisorDescription The supervisor will be able to add/edit/delete worker to each

project. Pre-Conditions The supervisor is logged in and database is connected.Post Conditions Success: The data about the worker is add/edit/deleted in the

system.Failure: The database contents will remain unchanged.

Main Success Scenario The supervisor log in the page.The supervisor enters/selects the data about the worker to add/edit/delete.Supervisor press the button to add/edit/delete.Appropriate message is shown by the system.Use case ends.

Alternative Scenario If the supervisor does not want to add/edit/delete the worker he presses the cancel button.


13. Check OrderUse Case ID CSSC-13Author Operation ManagerDescription The Operation Manager will be able to check order. Pre-Conditions The Operation Manager is logged in and database is

connected.Post Conditions Success: The data about the order will be displayed the


Main Success Scenario The operation manager visits the page.View all the information about the order.Enter his comments.Presses the save button.

Alternative Scenario If the operation manager doesn’t want to mark order then he presses the cancel button and leaves the page.


14. Allot ManpowerUse Case ID CSSC-14Author Operation ManagerDescription The operation manager will be able to allot manpower for

each project. Pre-Conditions The operations manager is logged in and database is

connected.Post Conditions Success: The data about the allotment of workers is saved in


Main Success Scenario The operation manager visits the page.View all the information about the order.Enter the manpower information.Presses the save button.

Alternative Scenario If the operations manager doesn’t want to mark order then he presses the cancel button and leaves the page.


15. Allot ItemsUse Case ID CSSC-15Author Operation ManagerDescription The Operation Manager will be able to allot items to the

order. Pre-Conditions The Operation Manager is logged in and database is

connected.Post Conditions Success: The data about the items according to the order will

be marked by the operation manager.Failure: The database contents will remain unchanged.

Main Success Scenario The operation manager visits the page.View all the information about the order.Selects the items and its quantity.Presses the save button.

Alternative Scenario If the operation manager doesn’t want to allot items then he presses the cancel button and leaves the page.


16. Requests to StorekeeperUse Case ID CSSC-14Author Operation ManagerDescription The operation manager will be able to send request to the

store keeper for each project. Pre-Conditions The operations manager is logged in and database is

connected.Post Conditions Success: The data about the allotment items is saved in the


Main Success Scenario The operation manager visits the page.View all the information about the order.Enter the items information and quantity.Presses the save button.

Alternative Scenario If the operations manager doesn’t want to mark order then he presses the cancel button and leaves the page.


17. Receive ItemsUse Case ID CSSC-17Author StorekeeperDescription The storekeeper will receive the items and enter in the

system. Pre-Conditions The storekeeper is logged in and database is connected.Post Conditions Success: The data about the items according to the receive

items will be marked by the operation manager.Failure: The database contents will remain unchanged.

Main Success Scenario The storekeeper visits the page.Enter the all received items.Selects the items and its quantity.Presses the save button.

Alternative Scenario If the storekeeper doesn’t want to receive items then he presses the cancel button and leaves the page.


18. Issue ItemsUse Case ID CSSC-14Author StorekeeperDescription The storekeeper will be able to issue items to the working

manpower for each project. Pre-Conditions The storekeeper manager is logged in and database is

connected.Post Conditions Success: The data about the issued items is saved in the


Main Success Scenario The storekeeper visits the page.Enter the all issued items.Selects the items and its quantity.Presses the save button.

Alternative Scenario If the storekeeper doesn’t want to receive items then he presses the cancel button and leaves the page.


19. Check BalanceUse Case ID CSSC-19Author StorekeeperDescription The storekeeper will be able to check remaining items. Pre-Conditions The storekeeper is logged in and database is connected.Post Conditions Success: The data about the balance of items will be shown.

Failure: The database contents will remain unchanged.Main Success Scenario Storekeeper will view the remaining items.Alternative Scenario If the storekeeper doesn’t want to view balance of items then

he presses the cancel button and leaves the page. Exception The system will generate exception if the data is incorrect or

data is already is present in the database.

20. Add/Edit/Delete ItemsUse Case ID CSSC-20Author StorekeeperDescription This use case allows the storekeeper to add/edit/delete the

store items. Pre-Conditions The supervisor is logged in and database is connected.Post Conditions Success: The data about the items is add/edit/deleted in the


Main Success Scenario The storekeeper will log in the system.The storekeeper enters/selects the data about the items to add/edit/delete.Storekeeper presses the button to add/edit/delete.Appropriate message is shown by the system.Use case ends.

Alternative Scenario If the storekeeper does not want to add/edit/delete the items he presses the cancel button.


21. Make ObjectionUse Case ID CSSC-21Author Auditor GeneralDescription Using this use case auditor general can make objection.Pre-Conditions The Auditor General is logged in and database is connected.Post Conditions Success: The data about the audit objection is saved in the


Main Success Scenario Auditor General will login first.Will check order, consumption and payments.Evaluates them and put remarks on each project.Use case ends.

Alternative Scenario If the Auditor General does not want to do anything the Auditor General he presses the cancel button.


22. Check OrdersUse Case ID CSSC-22Author Auditor GeneralDescription Using this use case auditor general can check orders.Pre-Conditions The Auditor General is logged in and database is connected.Post Conditions Success: The data about the order is displayed by the system.

Failure: The database contents will remain unchanged.Main Success Scenario Auditor General will login first.

Will check orders. Use case ends.

Alternative Scenario If the Auditor General does not want to do anything the Auditor General will presses the cancel button.


23. Check Payments

Use Case ID CSSC-23Author Auditor GeneralDescription Using this use case auditor general can check payments

record.Pre-Conditions The Auditor General is logged in and database is connected.Post Conditions Success: The data about the payments is displayed by the


Main Success Scenario Auditor General will login first.Will check payments. Use case ends.



24. Consumption RecordUse Case ID CSSC-24Author Auditor GeneralDescription Using this use case auditor general can check consumption

records.Pre-Conditions The Auditor General is logged in and database is connected.Post Conditions Success: The data about the consumption record is displayed

by the system.Failure: The database contents will remain unchanged.

Main Success Scenario Auditor General will login first.Will check consumption record. Use case ends.



Adopted Methodology :

Adopted methodology of my project is the VU Process Model which is the combination of waterfall and the spiral model.

Work Plan :

Requirement Analysis

System & Software Design

Implantation & Testing

Integration & Testing

Ops & Maint

project title€¦ · web viewcheck payments use case id cssc-23 author auditor general...

Documents