Record Management Sytem
Project Stage : Analysis
Project Title : Requirements Specifications and Conceptual Data Model
Deadline : 15 July 2013
I. REQUIREMENTS SPECIFICATION
1. Introduction
The system that we are about to design is the Record Management System that could cater the needs of information of every member in Davao City Alliance Gospel Church. It is an institution which accepts members whole heartedly. An institution wherein they keep confidential records regarding the profile of each member.
On the said office, their administration is using Microsoft Word file and Microsoft Excel just to make a list and store data of every member. It is burden on their part to store the profile in MS Word of each member of their institution. It has many instances that could misplace, replace or worst delete in this kind of storing data.
2. Current System Overview The following functions are manually performed by the owner:
Viewing the member’s information.
The administrator views the member’s information or profile through scanning a Microsoft Word file, one MS Word file is equivalent to one member.
Listing members.
The administrator or her secretary list all down the names of the members types into a Microsoft Excel file.
Answering a form.
The encoder types all the questions to be answered and the answers of the members repeatedly using Microsoft Word.
Printing different kinds of forms.
If the administrator asks for a copy of list of members, or a copy of a form of a specific member, or asks to print a member’s information they manually search the MS Word files in the computer and if not found, the encoder will type a copy of it to print.
3. Identified Risks
Loss of Records
Due to hustle way of keeping the files, it would be possible to lose some lists of information and forms of the members. A missing record would be a hustle to the encoder’s part to type it again.
Files saved in a MS Word can be corrupted and deleted unintentionally.
4. User Requirements
The
Project Title : Requirements Specifications and Conceptual Data Model
Deadline : 15 July 2013
I. REQUIREMENTS SPECIFICATION
1. Introduction
The system that we are about to design is the Record Management System that could cater the needs of information of every member in Davao City Alliance Gospel Church. It is an institution which accepts members whole heartedly. An institution wherein they keep confidential records regarding the profile of each member.
On the said office, their administration is using Microsoft Word file and Microsoft Excel just to make a list and store data of every member. It is burden on their part to store the profile in MS Word of each member of their institution. It has many instances that could misplace, replace or worst delete in this kind of storing data.
2. Current System Overview The following functions are manually performed by the owner:
Viewing the member’s information.
The administrator views the member’s information or profile through scanning a Microsoft Word file, one MS Word file is equivalent to one member.
Listing members.
The administrator or her secretary list all down the names of the members types into a Microsoft Excel file.
Answering a form.
The encoder types all the questions to be answered and the answers of the members repeatedly using Microsoft Word.
Printing different kinds of forms.
If the administrator asks for a copy of list of members, or a copy of a form of a specific member, or asks to print a member’s information they manually search the MS Word files in the computer and if not found, the encoder will type a copy of it to print.
3. Identified Risks
Loss of Records
Due to hustle way of keeping the files, it would be possible to lose some lists of information and forms of the members. A missing record would be a hustle to the encoder’s part to type it again.
Files saved in a MS Word can be corrupted and deleted unintentionally.
4. User Requirements
The