Requirement-Document BMDC Reporting Application Ver 1 6

7/29/2019 Requirement-Document BMDC Reporting Application Ver 1 6

1/26

Netlink MIS Bio Metric Project

Software Requirement Specification

SynopsisThis document will provide a detailed summary & requirement specification

about BMDC reporting application, to the readers

Author(s) Ankur Shrivastava

Version 1.0.0

Date 11-Sep-2012

Location Bhopal


2/26

Contents

1 INTRODUCTION ............................................................................................................................................... 3

1.1 HIGH LEVEL VIEW OF THE SYSTEM ................................................................................................................ 31.2 ACRONYMS &RELATED TERMS ..................................................................................................................... 4

2 CATEGORIZATION OF THE USES ............................................................................................................... 5

3 SYSTEM REQUIREMENTS ............................................................................................................................. 6

3.1 DATA SECTIONS USE CASES DESCRIPTIONS................................................................................................... 63.1.1 CRUI User Master ................................................................................................................................. 63.1.2 CRUI Asset Master ..............................................................................................................................873.1.3 CRUI Expense Category Master ..........................................................................................................983.1.4 CRUI IFS Code Master .......... .......... ........... .......... ........... .......... ........... .......... ........... .......... .......... ..11103.1.5 CRUI Vendor Master .......................................................................................................................11103.1.6 Unit Master ......................................................................................................................................13123.1.7 CRUI Location Master.....................................................................................................................1312

3.2 TRANSACTION SECTION USE CASES DESCRIPTIONS .................................................................................14133.2.1 CRUI Expense Claim Form .............................................................................................................14133.2.2 CRUD New Resident Record ...........................................................................................................1514

3.2.3 Manage Attendance ......... ........... ........... .......... ........... .......... .......... ........... .......... .......... ........... .......16153.2.4 Manage Supervisor Team Assignment .......... .......... ........... .......... .......... ........... .......... ........... ..........16153.2.5 Manage Team Location Assignments ........... .......... ........... .......... .......... ........... .......... ........... ..........17163.2.6 Manage Operator Assignment ......... ........... .......... ........... .......... ........... .......... ........... .......... .......... ..17163.2.7 Manage Assets .......... ........... ........... .......... ........... .......... .......... ........... .......... ........... .......... ........... ...18173.2.8 Manage Expense Approval ........... .......... ........... .......... ........... .......... ........... .......... ........... .......... .....19183.2.9 Manage Expense Float .......... .......... ........... .......... ........... .......... ........... .......... ........... .......... .......... ..21203.2.10 Uploaded Data Status ......................................................................................................................22213.2.11 Manage Employee Payments CRUI .......... ........... .......... .......... ........... .......... ........... .......... ........... ...23223.2.12 Manage Vendor Payments CRUI ........... .......... ........... .......... .......... ........... .......... ........... .......... .......23223.2.13 Daily Entry Records............... .......... ........... .......... ........... .......... ........... .......... .......... ........... .......... ..2423

4 SPECIFICATION SIGN OFF SHEET .......... ........... .......... .......... ........... .......... ........... .......... ........... ..........2524


3/26

1 IntroductionThe purpose of this document is to present a detailed description of the MIS System for the BIO-Metric

Project. It will explain the purpose and features of the system, the interfaces of the system, what the

system will do, the constraints under which it will operate and how the system will react to external

stimuli.

MIS System will be an application or group of applications, integrated with each other to provide forms

and reports/ dashboards to Netlink Project Management team for monitoring & supervising the various

MET teams, which are working in several locations and levels for the execution of the UIDAI project.

The main objective of the application is to capture MIS data required for monitoring and to provide

several reports/dashboards to individual, group, team as an when appropriate to help in monitoring and

for successful completion of the BIO- Metric project by utilizing this MIS system.

1.1 High Level View of the systemThere will be mainly these 3 levels from where data will entered & Fetched into the application.

All the activities happening at MET can be monitored from BMDC, & thus of BMDC at corporate level

MET Units

These teams will be responsible for the Biometric Enrollment of all residents as per BIO-Metric Project Criteria. These unitswill be mobile and will be at diffferent locations at different point of time.

The Biometric data captured will be based on Camps at a village /town.

Mobile Units will be required to capture the Data from their specified Location

BMDC

Biometric Data Centre (BMDC) for data consolidation, storage and processing located within the districts coming under thecentre. Also, few data entering operators may be validating /cross checking 5-10% of the enteries done at MET level.

Data will be sent to BMDC through internet

BMDC can use that data for Auditing purpose.

Corporate

Corporate denotes Netlink Bhopal office in this application

Corporate user are the admin of this application & will always have a bird eye view about the activities happening at BMDC &MET Level

Corporate

BMDC

MET


4/26

1.2 Acronyms & Related Terms1. CRUD -: Create / Update / Retrieve / Delete2. CRUI -: Create/Update/ Retrieve/ Inactive3. BMDC -: Bio Metric Data Centre4. MET -: Mobile Enrollment Team5. Mobile Laptops -: Laptops provided to the Mobile team, In each Unit there may be up to 5

Laptops which are given, to capture the desired Information. Each Laptop will have a unique

Code for identification.

6. Asset-: A material of value, owned by a person or company (Netlink)7. DEO Data Entry Operator8. BMO Bio Metric Operator9. User -: User is a person who will have a login ID in this application10. Inactivate -: If any record is inactivated, it shall not be included in calculation.


5/26

2 Categorization of the usesIdentified Use cases are categorized into 2 different sections

Data Section-: These Use Cases shall allow user to Insert, Update or Inactivate the Master Dataof the application, this master data will be used to manage the various transactions in theapplication

Transaction Section-: These type of use cases shall allow users to manage the various datamodification & to perform several procedures on database, assisting user to manage a business

process


6/26

3 System RequirementsThis section of the SRS contains all software requirements to help management to take decision & also it

enables designers to design a system to satisfy those requirements, and testers to test that the

developed system & to make sure that system satisfies the requirements.

3.1 Data Sections Use Cases DescriptionsRequirement

IDSRS-1 Requirement

Type

Functional

Behavioral

Status 1st

Release

Design Done

Use Case Name3.1.1 CRUI User Master

Access Corporate level


7/26

Description System shall allow Corporate Admin to add a new user in a system, To start a newregistration, admin has to select

User Type : This corresponds to the type, that a user belongs to corporate or BMDC or MET

Based on the selected type user has to select the User Profile (Please refer to Access Excel

for the profile details), In case if user belongs to BMDC or MET, admin has to select the

BMDC name, where a respective user belongs to

Following information of user are required for successful user creation-:

Personal Information Details1. First Name -: Text Box (Alphanumeric)2. Last Name -: Text Box (Alphanumeric)3. Gender -: Drop Down with Male & Female options4. Profile-: Drop Down5. Select Vendor -: Drop Down6. Mobile # -:-: Text Box (Numeric)7. Phone # -: -: Text Box (Numeric)8. Address -: Free Flow Text Field (Alphanumeric)9. City / Village -: Text Box (Alphanumeric)10. District -: Drop Down11. State -: Drop Down12. E Mail ID -: Text Box (Alphanumeric)13. Postal Code -: Text Box (Numeric)14. UID Certification # (Alphanumeric)15. Login Status (Active In active) Drop Down15.16. Allow Login (Yes / No)

Banking Information Details

1. Accounts Holders Name (Alphabets)2. Account Number (Alphabets)3. Bank IFS code : User has to input the details of IFSC, & has to hit the validate

button, It will be correct rest of the field will be auto filled. (This Gap)4. Name of Bank (Alphabets) (Auto Filled)5. Branch Name (Alphanumeric) (Auto Filled)6. Address Details (Alphanumeric) (Auto Filled)


8/26

Business Rules 1. Name of Bank and Branch Name and Address will be READ ONLY and will befetched from the BANK IFS Code Master.

2. User Name & Password will be provided & added by the Admin.3. Banking Details Required (Y/N), After Select Information, If it is marked as Yes, Then

only system will show the Bank account details for filling

4. UID Certification # for user will be optional, but is mandatory for operators5. All the bold fields are mandatory to be filled6. Admin of user module will never be able to delete an user from the system, he will

only able to inactivate the user, In case of inactivation, user will not be able to

login, & will not be available in any of the elementary process for serving.

7. User will only able to view forms as per the details provided in the excel, which hasdirect association with profiles. No menus or link will be available to them, in which

they are not supposed to have access

8. While creating an operator, in MET level, system shall only allow to manage thedetails at personal information level, banking information shall be filled at

corporate or at BMDC level.

9. If user wants to create an user @ BMDC or at MET level, system shall allow user toselect the BMDC, where proposed user belongs to.

Dependencies 1. Vendor Master Table has to have data available for Vendors, For Netlink User,Vendor will be Netlink

2. District Master Table has to have data available3. State Master Table has to have data available

Assumptions To add a User for Netlink, Admin has to select Netlink Vendor, from Drop down list User will always have an login ID & Password. Only Operators profile user will not

have an login ID & Password

IFSC search functionally will be part of Next release

Requirement

IDSRS-2 Requirement

Type

Functional

Behavioral

Status Signed Off

Use Case Name3.1.2 CRUI Asset Master



9/26

Description System shall allow user to create a new assets in a system.

Following information is required for a successful submission

Assets Name (Mandatory) (Alphanumeric) Asset Category(Mandatory) (Alphanumeric) -: This filed shall be a drop down List,

user shall have to select, from assets category master list, Example Laptop, Server,Etc

Bar-Code (Mandatory)(Alphanumeric) Date of Purchase(Mandatory) Comments (Alphanumeric) Creator Name (Mandatory) (Auto Saved, Based on user login details) Date & Time Stamp (Mandatory)(Auto Saved) Description(Alphanumeric) Manufacturer Name (Mandatory)(Alphanumeric) Serial #(Alphanumeric) Status Ac/In (Mandatory)

Business Rules If either of the mandatory field is not filled, system shall show an appropriatewarning message, at the time of submit.

Asset Category field shall have data of have master data uploaded. Assets Category may not have master form, but details should be populated from

database

Creator Name needs to be read only Anything which Net link Purchases, has to have a bar code & Serial #, Filled by the

User here

Dependencies User shall have to know all the necessary details about a assets, since all the fields are

mandatory in this formAssumptions

Requirement

IDSRS2 Requirement

Type

Functional

Behavioral

Status Signed Off (May

be we will not

develop the

master form)

Use Case Name3.1.3 CRUI Expense Category Master



10/26

Description This use case shall allow corporate user to add, various expenses categories. This categorywill be used by various different users to add expenses type in their expense record form,

which will be further used in reports generation & managing the expenses.

Following information are required for a successful submission

Expense ID -: System Generated & Read Only Expense Super Category -: Mandatory(Alphabets) Expense Category-: Mandatory (Alphabets) Expense Sub Category -: Mandatory (Alphabets) Unit(Float) Comments

Business Rules If either of the mandatory field is not filled, system shall show an appropriatewarning message, at the time of submit.

Dependencies

Assumptions


11/26

Requirement

IDSRS 3 Requirement

Type

Functional

Behavioral

Status Proposed(May be

we will not

develop the

master form)

Use Case Name3.1.4 CRUI IFS Code Master


Description System Shall allow User to Add IFS Master Information, through a simple web interface

Following Information is required for a successful submission

These Details will be used in Creating / Updating the Banking Information Records of Users,

Vendors & Operators.

Business Rules 1. All The Fields are mandatory in this Form2. IFS Code needs to have unique constraint.

Dependencies

Assumptions

Requirement

IDSRS4 Requirement

Type

Functional

Behavioral

Status Signed Off

Use Case Name3.1.5 CRUI Vendor Master



12/26

Description System shall allow Corporate Admin to add a new Vendor in a systemFollowing information are required for successful submission

Personal

Company Name ( Mandatory) Contact Person ( Mandatory)

Contact Person # ( Mandatory) Address ( Mandatory) Company PAN # ( Mandatory) Company TIN # Company Servl0ice Tax Number Company Address, City, State, Pin code ( Mandatory) Company email ID 1,2 (At least 1 Mandatory) Company Phone # 1, 2, 3 (At least 1 ) Company Fax 1, 2, 3 Status Active/ Inactive ( Mandatory)

Banking Info

Bank IFS Code ( Mandatory) Account Holders / Company Name ( Mandatory) Account # ( Mandatory) Bank Name Rd Only Bank Address Rd Only

Business Rules 1. All the Bold Fields are Mandatory for user.2. Name of the Bank, Branch Name and Address will be read only and will be picked

up from BANK IFS Code master.

For View From

Vendor ID Field shall be a searchable option, On clicking the browse link, system shall open a

window in pop, allowing user to search a user through following parameters

First Name Last Name Status

Dependencies

Assumptions


13/26

Requirement

IDSRS5 Requirement

Type

Functional

Behavioral

Status Signed off (May

be we will not

develop the

master form)

Use Case Name3.1.6 Unit Master


Description This use case shall allow corporate user to add, various Unit of Measures types. Thiscategory will be used by MET users to add unit of measure in their expense record form, for

each expenses, which will be further used in reports generation.

Following information are required for a successful submission

Unit ID -: (Mandatory)(Auto Saved), System Generated Unit-: (Mandatory)-: (Alphanumeric) Name of the measure like, Ltr, Pt, Kg ETC.

Business Rules

Dependencies

Assumptions

Requirement

IDSRS6 Requirement

Type

Functional

Behavioral

Status Sign off

Use Case Name3.1.7 CRUI Location Master

Access Corporate Level

Description This form shall allow Users to add a new Location, in the database.

1. Place UR/RU @ first Place2. Location Code3. Village / Mohalla4. Tehsil / Ward #5. Pin code6. BMDC- Drop Down7. State -> Will be a drop Down Field, Shall be maintained from database8. District -> Will be a drop Down Field, Shall be maintained from database9. Status Ac / In

Business Rules All the Bold fields are mandatory in this form

Dependencies

Assumptions


14/26

3.2 Transaction Section Use Cases DescriptionsRequirement

IDSRS8 Requirement

Type

Functional

Behavioral

Status 1st Release.

Design Done

Use Case Name3.2.1 CRUI Expense Claim Form

Access Corporate, BMDC & MET levelDescription MET Users has to fill an expense from, as & when asked by the BMDC & corporate. This

detail will help Management to have a bird eye view in the occurring expenses.

Following information are required for successful submission

Date Expense Super Category -: Mandatory Expense Category-: Mandatory Expense Sub Category -: Mandatory Unit (Dropdown) Unit Price(Float) Quantity (Float) Location Code -: Read Only field Mandatory Claimed Amount (Auto Calculated) Rd only

Expense Categories & Unit of Measure shall be an drop down, with all the data populated

from their master table (Please refer SRS ID 2 & 5 )

View Claims details shall have following information for viewing

Date Expense Super Category -: Mandatory

Expense Category-: Mandatory Expense Sub Category -: Mandatory Unit Unit Price Quantity Location Code -: Read Only field Mandatory Claimed Amount (Auto Calculated) Rd only Claim Status Read only Fields Approved Amount Read only Fields Rejected Amount Read only Fields Approval / Rejection comments -: Read only { 100 characters}
http://e/BMDC/HTML%20Report/EARoot/EA1/EA4/EA157.htmhttp://e/BMDC/HTML%20Report/EARoot/EA1/EA4/EA157.htm


15/26

Business Rules All the fields are mandatory in this form Amount shall be calculated automatically by (Unit Price * Quantity) At MET level, a user will only able to view the record, which are created by him,

but at BMDC Level, User shall be able to view the all the recorded information of all

the MET users.

Till status is initiated, User can modify his claims, & also will be able to inactivatethem; once the status is changed from initiated, MET user should not be able to

update the status.

Dependencies

Assumptions Will be a URL based form, Assume that Internet Connection will be available to the User atMET Level

Requirement

IDSRS9 Requirement

Type

Functional

Behavioral

Status Signed off

Design Done

Use Case Name 3.2.2 CRUD New Resident RecordAccess Corporate, BMDC & MET level

Description System shall have a webpage available to allow MET Users for filling the information on NewResident Record

System will facilitate user to store following information about a resident

Business Rules First Name, Last Name & DOB are mandatory fields All other fields are optional At MET level, a user will only able to view the record, which are created by him,

but at BMDC Level, User shall be able to view the all the recorded information of all

the MET users.

Date & Time Stamp must be saved at each record creationAdd Pin Code Field in this form

DependenciesAssumptions

Requirement

IDSRS14 Requirement

Type

Functional

Behavioral

Status Signed Off

Design Done
http://e/BMDC/HTML%20Report/EARoot/EA1/EA4/EA158.htmhttp://e/BMDC/HTML%20Report/EARoot/EA1/EA4/EA158.htmhttp://e/BMDC/HTML%20Report/EARoot/EA1/EA4/EA158.htm


16/26

Use Case Name3.2.3 Manage Attendance

Access BMDC & MET Level

Description System shall have a separate webpage available at corporate level, to add the attendancedetails about Employees & Operators.

Operator ID @ MET Level / User ID @ BMDC Level (Search from First & Last Namefrom Vendor Master or User Master)

First & Last Name will be auto reflected, based on the selected ID Date P -: Present WPD -: without Pay day Leave Holiday

Business Rules Develop this form in Tabular way There will be 2 different forms for BMDC & MET

Dependencies

Assumptions

Requirement

IDSRS18 Requirement

Type

Functional

Behavioral

Status Signed Off

Use Case Name3.2.4 Manage Supervisor Team Assignment

Access Corporate, BMDC


17/26

Description Facilitate Supervisors to Assign an User with an particular team,Has to be in tabular format

1. User ID Search2. Team Code (Alphanumeric) -: Example BRB1PT01 Will be pulled from database3. From Date4. To Date

Business Rules

Dependencies

Assumptions

Requirement

IDSRS16 Requirement

Type

Functional

Behavioral

Status Signed Off

Design Done

Use Case Name3.2.5 Manage Team LocationSupervisor Assignments to locations

Access Corporate, BMDC & MET Level

DescriptionAllows Supervisor to assign a user to a particular location, for a specified time.

Radio Buttons Corporate / Vendor

If Vendor is selected allow user to select a specific vendor from a drop down list

1. Team Code -: Search from ( Team code details & assigned supervisor ID)2.1.Supervisor ID -: It is a search functionality (Name shall appear)Read only -:

Corporate shall be able to view all the user details with profile type Supervisor /

DBA, but vendor will see only their respective supervisors / DBA

3.2.Location Code (Alphanumeric)4.3.From & To date

Business Rules Note -: if vendor users is logged into the system & access this page, then radio button will beauto selected to vendor & vendor dropdown will be auto default to his vendor company

name, both radio button & vendor drop down will be read only to avoid any facility to

change.

For a particular date, 1 user id cannot be assigned to 2 or multiple locations

Dependencies

Assumptions

Requirement

IDSRS17 Requirement

Type

Functional

Behavioral

Status Proposed

Use Case Name3.2.6 Manage Operator Assignment



18/26

DescriptionAllows Supervisor to assign an Operator to a particular User, for a specified time.

Has to be in Tabular / Grid Form

Supervisor has to select an user ID & Operator ID from this form, Team code & Location

code will be an auto populated field, based on the data, provided on Team assignment &

User Location Assignment form, (Refer SRS 18 & 16)

User ID, Team Code & Location code at the top of the page, Then show rest of the fields in

tabular format

Operator ID

From date

To Date

Business Rules User ID has 1 to many relation with Operators

Dependencies

Assumptions

Requirement

IDSRS11 Requirement

Type

Functional

Behavioral

Status Signed Off

Working

Use Case Name3.2.7 Manage Assets

Access Corporate, & BMDC Level
http://e/BMDC/HTML%20Report/EARoot/EA1/EA2/EA34.htmhttp://e/BMDC/HTML%20Report/EARoot/EA1/EA2/EA34.htmhttp://e/BMDC/HTML%20Report/EARoot/EA1/EA2/EA34.htm


19/26

Description System shall have a separate webpage for user to assign an asset to an user

Following Information is required for a successful submit.

User ID - Search -: (Search From First Name / Last name from user master Table) Team Code -: Read Only field (Alphanumeric)

Asset Name -: (Alphanumeric) Shall have a search option for users to search AssetsID from Asset Master, User shall be able to search an assets , based on Asset Name

& Asset Category

From Date -: Mandatory To Date -: Read only field Issued By -: Will be a auto managed field, system shall add the user id of the issuer

by an auto mechanism

Business Rules

Dependencies

Assumptions

Requirement

IDSRS19 Requirement

Type

Functional

Behavioral

Status 1st

Release

Design done

Use Case Name3.2.8 Manage Expense Approval

Access Corporate,


20/26

DescriptionSearch Options for users:

1. ALL.2. BMDC3. Team code4. Status

Form Fields

1. User id Read Only2. Team Code Read Only3. Location Code Read Only4. Date Read only5. Expense Category Read only -: Expense Super Category , Expense category &

Expense sub category

6. Unit Price Read only7. Unit Read Only8. Quantity Read Only9. Claimed Expense Amount Read Only10.

Status (Initiated, Approved, Rejected, Partial Approved, Paid)

a) If Partially Approved then show Approved Claimed Expense AmountFields to enter Valve to user

11. Date/Time Read Only12. Approved / Rejected Comments

Initially Status will be initiated

Business Rules 1. At corporate level, users will always be able to update the expense status; systemshall allow them to change the status, even if it is in paid condition. But system

shall always keep a log about the changes, with a user id of the actor for the

elementary process.

2. In case of Partial approved, system shall update the partially approved amount inapproved id & rest of the left amount in Rejected id

Dependencies

Assumptions


21/26

Requirement

IDSRS20 Requirement

Type

Functional

Behavioral

Status 1st Release

Design done

Use Case Name3.2.9 Manage Expense Float


Description Search Options for users:

1. ALL.2. Total Amt Disbursed Claimed Expns = -ve. User IDs3. Total Amt DisbursedApproved Expns = -ve User IDs

Fields - In Tabular Form

1. User ID Read Only2. Team Code Read Only3. Location Code RD4. Total Amount Disbursed RD5. Total Claimed Expenses RD6. Total Approved Expenses RD7. Cash in Hand (as per Claimed Expenses)8. Cash in Hand (as per Approved Expenses)9. New Disbursement Amount ((Float)) (User Has to Enter This manually)10. Date / Time Stamp & User id RD

Business Rules 1. RD is read only here.2. System shall keep track of each New Disbursement Amount, entry with date & time

stamp along with a user id of the actor

Dependencies

Assumptions


22/26

Requirement

IDSRS11 Requirement

Type

Functional

Behavioral

Status 1st Release

Use Case Name3.2.10 Uploaded Data Status

Access Corporate & BMDC Level

Description This user activity will be initiated, when packets data from Govt Softwares is handed toBMDC,

An employee in BMDC has to upload those packets into Govt servers, & after that has to fill

the details about the upload details in the MIS system.

System shall have a separate webpage for user to upload transaction status data, happening

in MET, about an operator

Following Information is required for a successful submit.

1. Select Team Code -: Drop Down2. Enumeration Date -: Date Control, to select From & To date

On Button Click User shall get the following details

3. Dates -: Drop Down4. Operators List -: Drop Down, as per the team code selected -: User shall have to

select an date and Operators, then have to proceed & add the new records

5. # of Accepted (Numeric) -> User Has to add the number of accepted entries fromthe Govt Software

6. # of Rejected (Numeric) -> User Has to add the number of Rejected entries fromthe Govt Software

7. Date Stamp Auto ManagedBusiness Rules All the fields are mandatory to be filled, in this form.

There should not be 2 entries of an operator on a selected date.

Details filled here will be reflected in Manage Operator Payments CRUI Page, Please refer

SRS 13.

Dependencies

Assumptions
http://e/BMDC/HTML%20Report/EARoot/EA1/EA3/EA111.htmhttp://e/BMDC/HTML%20Report/EARoot/EA1/EA3/EA111.htm


23/26

Requirement

IDSRS12 Requirement

Type

Functional

Behavioral

Status Signed off

Design Done

Use Case Name3.2.11 Manage Employee Payments CRUI


Description System shall have a separate webpage available at corporate level, to add the payments

details about a user.

Form will be in Tabular format

Search :

On Dates -: From & To date Vendor Selection BMDC

Following will be the fields

User Name - Read Only / Name

Profile - Read Only / Name Supervisor Name - Read Only / Name Team Code - Read Only # OF Days Present RD # of Leaves RD # OF Days WPD RD # of Holiday RD # of Pay Days Present + Leaves + Holiday (Auto calculated) Per Day Amt.- Entry Box for user, Numeric fields, Text Box Amt. as per Attendance = # of Pay Days * Per Day Amt (Auto calculated) Total Accepted Entries RD Total Rejected Entries RD Per Entry Amt Entry Box for user, Numeric fields, Text Box Amt. as per Accepted Entries -: Total Accepted Entries * Per Entry Amt (Auto

calculated)

User can save, edit the recorded Information

Business Rules

Dependencies

Assumptions

Requirement

IDSRS14 Requirement

Type

Functional

Behavioral

Status Signed off

Working

Use Case Name3.2.12 Manage Vendor Payments CRUI
http://e/BMDC/HTML%20Report/EARoot/EA1/EA3/EA111.htmhttp://e/BMDC/HTML%20Report/EARoot/EA1/EA3/EA111.htmhttp://e/BMDC/HTML%20Report/EARoot/EA1/EA3/EA111.htmhttp://e/BMDC/HTML%20Report/EARoot/EA1/EA3/EA111.htmhttp://e/BMDC/HTML%20Report/EARoot/EA1/EA3/EA111.htm


24/26


Description System shall have a separate webpage available at corporate level, to add the paymentsdetails about a Vendor.

Search

1. Vendor Name / ID2. BMDC (All or Specific BMDC)3. From & To Date

Vendor & Vendor Details - RD

Date -RD

Total Accepted Records - RD

Total Rejected Records - RD

Amount as per Accepted record (Float Data Type) User has to Enter this

New Disbursement Amount (Float Data Type) User has to Enter this

Comments User has to Enter this

Tabular form - RD

1. User Name -: with Both Roles of Operator & Supervisor2. Profile3. Location Code4. Supervisor Name5. Total Accepted Records6. Total Rejected Records

Business Rules

Dependencies

Assumptions

RequirementID

SRSXX RequirementType

FunctionalBehavioral

Status Signed off

Use Case Name3.2.13 Daily Entry Records

Access MET Level

Description Operator ID -: with Both Roles of Operator & Supervisor-: Search Feature,

with First & Last Name

Operator Name -: Read only Enumeration Date Number of Accepted Records (Numeric)

Business Rules Enumeration Date cannot be less than todays date

Dependencies

Assumptions


25/26

4 SPECIFICATION SIGN OFF SHEET

Requirement Specifications Document Client Name NetlinkProject Name BMDC Reporting Application

Document last modified by: Ankur Shrivastava

Version Number 1.0.0 Date of last revision 16/09/2012

Approval

I hereby agree and approve that the specifications in this document constitute the complete scope of this

project and will consequently meet the business & functional needs. Any requirement not explicitly

mentioned in the specifications will be considered out of scope for this project. After approval, any

additions and changes to this document or referred objects will be pursued through the change request

process.

Approver: _________________________________

Title: _____________________________________________________

Company Netlink

Date: ___/____/_____

Signature: ___________


26/26

Documents

Requirement-Document BMDC Reporting Application Ver 1 6