Professional Documents
Culture Documents
BUSINESS REQUIREMENTS
FOR INFOBASE
Superior Functionality Asphalt Pavement
Table of Contents
Document History
I.Business Process Flow / Overview
Dependencies ............................................................................................................................... 4
Current Business Flow Diagram.................................................................................................... 3
Proposed Business Flow Diagram................................................................................................. 4
II.Information Flow
Current System Context Diagram ................................................................................................. 6
Proposed System Context Diagram .............................................................................................. 5
III.Business Requirements
Security Requirements .................................................................. Error! Bookmark not defined.
Performance Requirements .......................................................... Error! Bookmark not defined.
Availability Requirements.............................................................. Error! Bookmark not defined.
IV.System Requirements and Processing Rules
Technical Services Impact Statement........................................................................................... 6
System Environment Needs.................................................................................................. 6
Questions............................................................................................................................. 7
Backup and Recovery Needs................................................................................................. 7
V.Solution Alternatives/ Preliminary architecture diagram
Solution #1: InfoBase using MS Access................................................................................. 8
Solution #2: InfoBase using .NET ........................................ 8
VI. Budget and Resource Estimates
VII.Glossary
Approvals
1
Created version 2.1 created on 11/25/2017
BRD InfoBase Renee Systems, NJ
Document History
2
Created version 2.1 created on 11/25/2017
BRD InfoBase Renee Systems, NJ
Dependencies:
The proposed system shall be a data oriented one. For the system to perform in the desired way
and to minimize technician’s effort in analyzing the test results, it will be dependent on the
Master Database which will combine results from the Field and Laboratory tests into a module
called Mix Module available to Sr. Technicians.
The system shall only be operated on Windows Operating system.
The proposed system shall get data from legacy system /existing system.
Until the delivery of the proposed application users shall be using the existing system,
called Legacy system from here on in the documentation.
Current:
The current system works efficiently but limits the user in uploading Excel Datasheets, the
technicians take help of data entry professionals to enter 100’s of results from various
equipment’s which is a time-consuming effort prone to error’s resulting in improper decisions.
The current system has technical limitations as well. It was initially built in Foxpro which has
minimum support now-a days.
Proposed:
The proposed system shall be able to save/edit/retrieve/delete test results and projects and
performs complex calculations to provide desired results on Business user’s computer. The
results are from either Field or Testing Laboratories. Users who are Technicians & experts in the
Asphalt testing methodology can create projects in different modules and edit the data if
necessary. The system shall be able to process complex Asphalt testing calculations and logics
for the technician to decide the quality of the Asphalt. User shall have one interface to bring
data from Field and Labs which is currently done manually. The system shall upload data from
excel or other formats and perform desired calculations and give outputs in the form of Reports,
Graphs and Data forms.
Currently, the results from the equipment are analyzed manually through excel
application. The technicians manually enter data in another module to get the desired
results.
4
Created version 2.1 created on 11/25/2017
BRD InfoBase Renee Systems, NJ
5
Created version 2.1 created on 11/25/2017
BRD InfoBase Renee Systems, NJ
all the complex calculations and the flow/chain that connects them. Documents related to
the system will be stored on a secured shared location provided by client and accessible
only by authorized personnel’s. System shall only be accessible to DOT employees and
federal contractor who develop the application.
Performance Requirements — The system will be error free in providing the end results
and should combine the data in Master Database efficiently, it should be readily available on
user machines as and when required.
Availability Requirements — The first module of the product after requirements gathering
must be available for user acceptance test in 3 months.
User Requirements – The finished product will have a UI which will let the users access
different modules
Forms should be available in different modules to
Create Projects
Add Binders
Insert/Edit and Delete Data
Upload data spread sheets
Generate customized reports
System environment
Backup and recovery
6
Created version 2.1 created on 11/25/2017
BRD InfoBase Renee Systems, NJ
Questions
Is this a new system or an upgrade of an existing system?
It is a New system which matches to the functionality of Legacy system with proposed
enhancements by the DOT.
How many users does the business expect for the proposed system?
It is an internal system which shall be on Users computer, the users may vary from 10-
100.
How many do you expect to be on the system concurrently?
Individuals use the systems concurrently on their individual machines and finally
connect to a Master DB.
7
Created version 2.1 created on 11/25/2017
BRD InfoBase Renee Systems, NJ
8
Created version 2.1 created on 11/25/2017
BRD InfoBase Renee Systems, NJ
VII. Glossary
The terms in this glossary are business or project-specific terms that might cause confusion. If
you have difficulty with any term in the project documentation, consult this glossary for
clarification:
Approvals
______________________________________________
Sponsor – DOT
______________________________________________
Business Analyst – Ramkrishna Apsingear
_______________________________________________
Project Manager – Dinesh
9
Created version 2.1 created on 11/25/2017