CSC 333 spring, 2004
Professor Brian Nejmeh
Software Requirements Specification (SRS)
SRS Version Number: 4.0
Date of Publication:
HELP Ministries Project
Team Members: Dave Hess, Ria Ghose, Bobby Lusk
Team Lead for Milestone 5: Bobby
Sponsor Organization and Contact Information
Address:
E-mail: salacrum@aol.com
Phone: 717- 238 – 2851
Name of Point of Contact:
John Scarpato, III
SRS Approved by:
________________________________________________________
Authorized Person from Sponsor Organization
1. Introduction
1.1 Vision:
The team objectives for this project are to remodel the data model and custom build a new DBMS using either Microsoft Access or MySQL that will conform to HELP Ministries specific needs. Additional and new features shall be added to accompany the newly customized database, allowing it to have a higher efficiency than the one currently in use. This higher efficiency should allow a greater ease of use for the HELP Ministries Team and a more professional look in any outputs created by the database.
1.2 System Goals:
· Organize Customer Information
· Provide Security
· Run Efficiently
· Provide Professional Report Print Outs & Vouchers
1.3 System Concepts of Operation
Secretary HELP Staff
* Enters initial client info… * Search to find existing records
Name, Date, SS#, Family, Etc… * Enter all client info.
* One of Main Areas
DataBase
Laptop Synchronization Business Office
* Staff can take a copy of DB to remote * Searches DB to retrieve
Locations, and create new records which unpaid records, and matches
May be added to the DB upon returning. Requests to a funding source.
1.4 System Overview
GUI
Enter New Record Queries
Reports Vouchers
DataBase
Client Record
Vendor
Record
1.5 User Types:
· Administrator – has rights to create/delete/modify tables and print out reports
· Standard User – has rights to add/modify data into the tables. These would be the majority of the people at HELP ministries, who enter all the client information and perform queries.
· Limited User – This would be the secretary who enters the initial client information when they come in, but doesn’t have access to the rest of the database.
1.6 Constraints:
· Keeping User Interface essentially the same
· Discovering Relationship Model still within the database (Alpha Five)
Assumptions
· That we can convert all information in the current Alpha Five database into the newly constructed DBMS.
· Current equipment and networking capabilities owned by HELP Ministries will integrate with the new DBMS.
2. Software
Requirements
2.1 Requirements Overview of Feature Areas
With the
consent of HELP and Prof Nejmeh, we have decided to migrate
the HELP database from Alpha 5 to Access. However, this will not just be the
transfer of data from one system to another. At first we will be reverse
engineering a data model from the existing Alpha 5 database and our
understanding of the system from talking to John Scarpato. Further down the
road we will be changing the model after we get feedback from HELP ministries.
We will be implementing a relation database based on the data model. This will
be followed by populating the db with some of the data and testing it, which
will be like a prototype 1. We will continue populating and testing the db. In
the mean while it is important that HELP has the Technology stack installed
since we will transfer the second prototype to HELP and continue to test and
modify thereof. The last phase of the requirements area involves training HELP
ministry users to use the new Database and its several functionalities and
continue testing before we finally deploy the project to HELP.
2.2
Functional Requirements:
2.2.1 GUI using the MA Access front end
2.2.1.1 Drop-Down Lists (high): The GUI will consist of many drop-down list which help categorize the client. The following is a list of the drop down lists.
Service Request for HELP Office: rent assistance for first month, food, fuel, furniture, HELP rent, medication, PERM, PPL, RAP- first month, RAP- black, RAP- case management, RAP- security, shelter resource, shelter case management, translation, travel, shower vouchers, picture ID, clothing,
Service Request for Outreach Location: local travel, distance travel, shower, food, clothing, medication, ID, other- describe.
Relationship: spouse, son, daughter, grandchild, other blood relative, significant other, roommate
Ethnicity: Asian, African-American, Hispanic/Latino, White, Native and other.
Sources of Income and Expenses: full-time employment, part-time employment, temporary employment, unemployment, VA benefits, child support, alimony, welfare, SSI, SSDI, SS, worker’s compensation, none, gift, projected, estimated.
File Status: first time HELP client, previous HELP client, discharged/ case closed, listed in another file.
Current Living Situation: Renting home, owns home, homeless shelter, hotel/ motel, boarding housing, MH facility, D&A facility, abandoned/ condemned, Doubled-up/ lease violation, facing foster care placement, on the street, other temporary, housing, automobile, DV shelter, prison release, family/ friends, unknown
2.2.1.2 System modifications (medium): The system should be able to add new fields, delete fields and update fields when necessary.
2.2.1.3 Not a current issue: Linking website to database (medium): The database should be available to users through server pages.
2.2.2 History Records: HELP wants to maintain history of the client’s employment and service request
2.2.2.1 Employment History (medium): will show the following:
List of all the places of employments
Add new employment
Update the table for a new employment
2.2.2.2 Service Request History (high)
For a client maintain the services requested
Add a new request
List of the services granted or pending
Services provided by HELP or a local outreach
2.2.3 Intake forms: This will be used to get information from the client initially
2.2.3.1 Client information (high)
First name
Last name
Address
City
State,
Zip
County
Birth date
Social security number
Phone number
Case worker
Age
Gender
Marital status
Ethnicity
Date of first contact
File status
Living situation
City/State of Residence 6 month ago
City/State of Residence 1 year ago
2.2.4 Queries: HELP should be able to look up different information from the database
2.2.4.1 To search for people by (high)
Last name
First name
Social security number
Address
Phone Number
Service request placed
Grant Code Used
Date file opened
Date voucher paid
2.2.4.2 To search for service request by (medium)
Client
Granted by HELP or local outreach
2.2.4.3 To search for Vouchers by (low)
Grant code
Date paid
Open (unpaid)
Client Name
2.2.5 Reports: HELP wants to print out reports periodically
2.2.5.1 Voucher Reports by (medium)
Date
Grant Code
Open (unpaid)
2.2.5.2 Grant Reports by (medium): HELP needs to report back to various government (state and local) agencies on where their monies are going.
Date
Vendor
Grant Code
2.2.6 Vouchers: HELP prints out the vouchers which are then given to the clients
2.2.6.1 Create/Print (high): This will create and print a voucher for a client based on the service request placed and Vendor chosen
2.2.6.2 Update Database (high): After voucher is printed and /or used, changes should be made to the database:
Service request should be changed to met from pending/unfilled
2.2.7 Laptop Synchronization: HELP has a laptop which they sometime take to the site with them.
2.2.7.1 Laptop Synchronization (low): To be able to take client information on site and later update the main database to reflect those changes made while on site.
3. Increments
3.1 Increment 1
This
increment will consist of Creating the Tables for our
Database, focusing on the lookup tables for our drop-down lists, and the
ability to search through the records for people and service requests.
2.2.1.1 Drop-Down Lists
2.2.3.1 Client information
2.2.2.1 Employment History
2.2.2.2 Service Request History
3.2 Increment 2
This
increment will expend the database, working on the storing of the histories
needed, and getting the web interface working correctly. We will also work on the design of the
reports at this time.
2.2.4.1 To search for people
2.2.4.2 To search for service request
2.2.6.1 Create/Print
3.3 Increment 3
This
increment will finalize some of the searching ability of the database, as well
as incorporating a way for the database to be easily modified through the GUI,
things such as modifying lookup tables and drop-down lists. We will also look into a way of implementing
Laptop Synchronization as time allows.
2.2.1.2 System modifications: add and delete fields, records
2.2.6.2 Update Database
2.2.5.2 Grant Reports
2.2.7.1 Laptop Synchronization
4. Open Issues
· We do not yet know exactly how we are going to export the data out of the current database (Alpha 5) and populate it into the current database.
5. References
n/a
6. Glossary of Terms
UML – Unified Modeling Language
Synchronization – Allowing records to be created remotely, and then incorporating all those changes into the main database later.
GUI – Graphical User Interface
VA – Veterans
MH – Mental Health
D&A – Drug and Alcohol
DV – Domestic Violence