Professional Documents
Culture Documents
BRD Requirement For Softwares
BRD Requirement For Softwares
3. Input Data-
a) Structure-
i) Name of the Data Fields
ii) Type of the Data
iii) Length of the data field
iv) Mandatory/Non mandatory/Dependant
v) Required validation logic
vi) Other required information
b) Volume and Frequency-
i) Data upload frequency( per day/per week/per month) with future expected
changes
ii) Approximate size of the total data in single upload cycle
c) User Interaction-
i) Number of users responsible for Data Insertion
ii) How the users will send the data ( format and type of data file)
iii) How and who will verify the correctness of data
iv) The detail data insertion process to the system with necessary diagram
4. Output Data-
a) Structure-
i) Number and types of report required
ii) Data fields need to be shown in the reports
iii) History(time period) of the data viewable through report
iv) Any other info (e.g. user id, branch, bank, login info, date)
b) User Interaction-
i) Number of users responsible for Report view or Download
ii) How the users will download or view data(Searching criteria)
iii) The detail report generation process to the system with necessary diagram
5. Data management-
a) Data correction procedure
b) Data deletion process
c) Data archiving process
d) Emergency data insertion procedure
All the process and procedure must include the responsible user group, the request
process and approval procedure of the request
8. System Capabilities-
a) Availability of the service (example-24/7, up to 11.59 am everyday)
b) Different types of devices from which the system will be accessed
c) Technical capability of the end users and responsible organization
9. Constraints-
Define any conditions required to be followed during system development which is
not common-
Example-
1. The data will only be provided in text , no other format will be acceptable
2. report must be in pdf format
a. Identifies the highest and lowest estimated number of transactions and processing
frequency expected usage (including any seasonal peaks) for capacity planning
for storage and memory requirements for the application or project.