Download as pdf or txt
Download as pdf or txt
You are on page 1of 3

1.

The purpose and scope of the project-


a) Purpose-
What is the necessity of implementation of this project?
b) Scope –
i) List of problems solved by the project
ii) The broad definition of users and owner of the system

2. Laws and regulations-


Specify relevant applicable laws, regulations, policies, and standards that will affect the
operation and performance of the system, as well as any relevant external regulatory
requirements, or constraints imposed by normal business practices.

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

6. User Level for Data management (Internal)-


a) Level of different users
b) Functional responsibilities of different level of users
c) Hierarchy of the users( in case of approval procedure)

7. User level (External)-


a) Types of users based on function, location and type of accessing device(three separate
category)
b) Number of users for each types of users
c) Functional description of system usage by each types of users
d) Hierarchy of the users( in case of approval procedure)

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

10. Other system Integration-


Specify the dependency and relationship requirements of the system to other
enterprise/external systems. Include any interface to a future system or one under
development.
11. Security-
Specify security requirement for users of the system.
Example-
1. Length of minimum password
2. Days of password change
3. Multiple device login

12. Initial Capacity Requirements-


Specify the initial capacity requirements for the system. An initial estimation can be
established using current data amounts, planned number of users, and estimated
number of transactions.

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.

13. System Acceptance Criteria-


Specify the general system acceptance criteria specified and agreed upon by the
project sponsor and key stakeholders that will be used to accept the final end
product.

14. Current System Analysis-


If a current system exists, perform analysis on the system and describe how the
current system is used by the business. Specify data conversion requirements,
relevant data flows, system interfaces to existing systems, reporting capability,
etc.

You might also like