Po Management

Only available on StudyMode
  • Download(s): 178
  • Published: April 18, 2013
Read full document
Text Preview
[pic]

Software Requirements Specification

DOCUMENT REVISION HISTORY

|Ver. No. |Ver. Date |Prepared By |Reviewed By |Review date |Approved By |Affected Section & Summary of Change | | 1.0 | | | | | |Initial Version | | | | | | | | | | | | | | | | |

[Template Version History (not to be modified by project teams)]

|Ver. No. |Ver. Date |Prepared By |Reviewed By |Review |Approved By |Affected Section & Summary of |PIF No. | | | | | |Date | |Change | | |1.0 |3-Sep-12 |Sailaja |SEPG |3-Sep-12 |SEPG |Initial Version |NA | | | | | | | | | |

Table of Contents:

1. Software / System Scope …………………………………………………………………….4 1. System/ Application Boundary………………………………………………………..4 2. System/ Software Requirements…………………………………………………………….5 1. Functional requirements…………………………………………………………..4 to 9 1. Data Requirements…………………………………………………………………............9 2. Model Reference………………………………………………………………………10-11 2. Non Functional Requirements………………………………………………………...12 1. Look and Feel Requirements……………………………………………………………...12 2. Usability Requirements……………………………………………………………...........12 3. Performance Requirements ……………………………………………………………....12 4. Reliability Requirements…………………………………………………………….........13 5. Portability Requirements…………………………………………………………….........13 6. Security Requirements…………………………………………………………….............13 7. Other Requirements ……………………………………………………………................13 3. Constraints and Assumptions…………………………………………………...14 to 17 3. Off-the Shelf Solutions………………………………………………………………………18 4. User Documentation and Training ………………………………………………………...18 5. Acceptance Criteria …………………………………………………………………………18 6. References ……………………………………………………………………………………18

1. Software / System Scope:
The purpose of this PO Management project is to gather and maintain the information of contract between consultant and client/vendor.

➢ Storing all the contract information.
➢ It keeps track of consulting company, consultant information, and client/vendor information and the contract information.

1. System/Application Boundary:

Maintain all the information regarding the contract i.e. Consultant is working for Client within a certain period. Alerts for LCA, EAD, MSA and Passport Details should be kept before 6 months of expiry date.

2. System/Software Requirements

1. Functional Requirements

|Requirement No. |Req_01 | |Requirement Type |Functional Requirement | |User Requirement/Use Case No. |Generate Temporary POID | |Description |It captures Our Company Name, Consultant Name, contracting Company Name, contract start date and | | |generates Temporary POID for the...
tracking img