The intent of this papers is to layout the specifications for the Fishkill Food Pantry Database system. In this papers you will happen a layout of information on the paradigm system. Throughout this papers you will happen our survey information on their concern. We describe the system constructs and vision, description and histrions, system boundaries and the full range of the system. We created informations faculties and other information demands. Please, refer to Appendix A for a glossary of footings and acronyms used in this papers.

2. System Concept

2.1 Project Vision

This system development is based on our squad ‘s collaborative work and the information we were given in our interviews with Mr. Murray Suggitt.

Fishkill Food Pantry would wish to make a database system in order to maintain path of the larder ‘s clients. The Food Pantry is managed by Mr. Murray Suggitt along with a group of voluntaries that reach out to people within the Fishkill country.

As caput of the Pantry organisation, Mr. Murray Suggitt will supervise the database system and find any alterations. Mr. Murray Suggitt, along with Judy VanNostard and Irene Zedo, will update the system information hebdomadally.

The ends of this undertaking include the development of a database system designed to:

Supply an easy to utilize system that allows voluntaries to entree client information through come ining the last four figures of the client ‘s societal security figure.

The system requires an array of information to be entered such as: Customer Name, Customer Address, # of household members per family and old documented assignments.

This system will make a user-friendly experience for both the voluntaries and the clients and will assist develop continuity of service.

Develop a strategic program for organizing instruction, community outreach and hungriness consciousness.

Will necessitate a checklist system in order to verify a client ‘s designation.

The strategic end of the Fishkill Food Pantry is to pull off patronages expeditiously and efficaciously in order to make a positive experience for both parties every bit good as aid the organisation to pull off their disbursals and client history

Better direction of client Numberss

Reduce overall costs and pull off budget more expeditiously

Better one-year records

2.2 Stakeholders Analysis

Person ( s )

Importance

Undertakings

Mr. Murray Suggitt

( 845 ) 476-9433

Judy VanNostard

( 845 ) 242-3269

Irene Zedo

( 845 ) 831-4726

Director Systems Administrators

Indentify chances to better service to local occupants.

Volunteers that work at that place

Volunteers/Front Desk Volunteer

Provide feedback on the current system and the degree of service to the clients

Richard Lanni

Computer Specialist

/Maintenance

Follow up on the new system and supply feedback

Other Local Pantries

Food Pantries

Provide resources to research strategic partnerships

Edith ‘Happy ‘ Schmidt

( 845 ) 831-0861

Secretary/Volunteer

Aid in assemblage and analysis of informations into the system

The Family Clients

Local country Residents

Provide feedback on the new system

Hudson Valley Food Bank

Hudson Area

Federal Food Bank

Provide aid to local communities nutrient larders

Government ( legal )

Federal

No undertaking

3. System Requirements

3.1 System Actors

These include each human and external system histrion that will interact with the system.

Primary Actors:

Person in Need of Food Servicess

The client that interacts with the Front Desk Volunteer to do an assignment for nutrient

pickup. ( Client )

Front Desk Volunteer

Volunteer that makes assignment and fills out information to give to the

administrative at the other computing machine. ( Edith Schmidt ) ( Donald Vanostrand )

System Administrators

Person that inputs information into system and makes certain that there is adequate nutrient.

( Mr. Murray Suggitt ) ( Ms. Judy VanNostard ) ( Ms. Irene Zedo )

Secondary Actors:

Care

Person that interacts and maintains the system. ( Richard Lanni )

External Actors:

Hudson Valley Food Bank

If there is non adequate nutrient in the Pantry, so nutrient is collected from the Hudson Food

Bank.

Government

The authorities assistance and financess. Regulation that need to be followed to be able to acquire

support.

3.2 Scope of Work

Shown below is a simple diagram of the entities and database that will be used in the Fishkill Food Pantry. This system will command the ingoing and surpassing information procedure. The Client or Person_in_need_of_food calls in to do an assignment. The Service supplier schedules an assignment and cheques that the client is in the system. The system keeps path of past assignments and information. It besides has the ability to track the voluntary ‘s personal information along with their hereafter agenda. From here the System Administrator processes the information and enters it into the database. For farther information, please refer to the more complex diagram in Appendix C and D.

The System will necessitate regular updating of information as it pertains to each client ; an decision maker representative will be responsible for adding and modifying the company ‘s information. The System Administrator will allow mandate.

Context Diagram

3.3 Functional Requirements

High Degree Events

1. Client contacts Fishkill Food Pantry.

2. Volunteer searches database to see if the client ‘s record is already in the database.

3. If the client is in the database, so the Volunteer looks into past assignments, to see if the client is eligible to come in.

4. Volunteer so will make assignment for client to come in to acquire nutrient.

5. If the client is non in the database so the voluntary will get down to take down information on file and manus off the phone call to one of the systems decision makers to make the client information.

6. After scheduling an assignment, the voluntary will publish out the elaborate choice up signifiers for when the client comes into get nutrient.

Use Cases

1. The voluntary log on to the system and performs a hunt for the client ‘s record utilizing the last 4 SSN or the client ‘s last name.

2. If the client is new to the Fishkill Food Pantry so the Systems Administrator must come in the new information into the database.

3. If the client ‘s record already exists in the database so the voluntary creates an assignment for the client to come in and pick up their nutrient.

4. The voluntary cheques when the last annual certification was shown and informs the client if they have to convey in their certification or non.

This usage instance diagram describes the basic functional demands for implementing the system. The usage instance diagram displayed in Appendix D shows how histrions interact with each of these events. The pointers entail the relationship between the histrions and the usage instance. When pointers travel from an histrion to a usage instance it indicates that the histrion triggered the usage instance, whereas arrows pointed from the system to an histrion indicate that the system triggered the usage instance. When the pointer is included, so the relationship shows that the behaviour occurs in more than one usage instance. The generalisation pointer indicates that the voluntary is made up of two different histrions.

3.4 Non-Functional Requirements

Security:

For security intents, the Food Pantry will be utilizing a Secure Network Access, which includes a username and watchword for system users. The System Administrator has to allow entree to modify the database.

Performance:

The Food Pantry will be utilizing high velocity Internet, with a fast processor every bit good as Ram memory.

Capacity:

The capacity for the database system is a upper limit of 50 minutess per twenty-four hours. This manner, there is proper storage infinite for informations on the system.

Handiness:

Our System will be available from 8am to 6pm and is unfastened Monday-Friday and closed on weekends. The database will run 50-75 % of the twenty-four hours.

Recovery:

In order to guarantee recovery, the system will be backed up daily.

Compatibility:

Our system is compatible with Microsoft Access and Wave Maker. It is besides compatible with current hardware such as HP, Windows 7, and i7 Core.

Maintainability:

In order to keep our system, it will be updated whenever needed. The care coordinator will be in charge of updating the system sporadically.

Serviceability:

It is easy to utilize Interface with our system. We will utilize standard hardware and package demands.

3.5 Mandated Constraints

After our initial meeting with Mr. Murray Suggitt, it was clear what some of the restraints to this undertaking were. The chief restraint is that the system must be user-friendly. The voluntaries that work within the Fishkill Food Pantry are non computing machine understanding and will hold trouble with a more complicated system. By making a simple system, this allows Mr. Suggitt and his voluntaries to utilize the system comfortably. The system will hive away a great trade of information but will be easy to voyage.

Our following restraint that we felt was of import was system handiness for the decision makers. The chief decision maker, Mr. Murray Suggitt, must be able to command who has entree to the system for security intents. Other than Mr. Murray Suggitt, merely Judy VanNostard, Irene Zedo, and Richard Lanni will hold entree. Our last restraint is a manner to verify the client ‘s individuality. Within the database system there will be an country for the voluntaries to look into off how they verified the individuality. Within the cheque box country there will be a driver ‘s licence, tribunal paperss, phone measure, recognition card, power measure, 1041 papers, and other.

3.6 Relevant Facts and Premises

Some premises must be made when incorporating our system with the Fishkill Food Pantry. One of the premises that our squad has made is that after the system is installed the Systems Administrator Mr. Murray Suggitt will be able to develop the staying Volunteers on how to utilize the system. We assume that the system will be updated sporadically by Mr. Murray Suggitt, Judy VanNostard, Irene Zedo and Richard Lanni, who are the systems decision makers and care coordinator. When the system is operational it will be user friendly and all information will be accessible through it. We besides assume that clients for the Fishkill Food Panty will ne’er vanish.

Some facts that our squad of analysis has gathered while developing this system are that Mr. Murray Suggitt, along with Irene Zedo and Judy VanNostard, will be the System Administrators. They will be able to update the system sporadically and change the system if needed. The Fishkill Food Pantry has increased in concern because of the economic adversities in this current universe. The Fishkill Food Pantry merely has a certain sum of grants from the authorities and hence can merely take a certain sum of household ‘s within their country. The System will back up English-speaking users.

4. Information Model

4.1 Data Dictionary

1. Table Client

Purpose: Contains all information on each Client.

Column Name

Aliass

Description

Data Type

Size

Client_SSN

Clients Last 4 SSN

Clients Last 4 SSN

Char

4

ClientLastName

Clients Last Name

Clients Last Name

VARCHAR

30

ClientFirstName

Clients First Name

Clients First Name

VARCHAR

30

Contact_Num

Clients Phone Number

Clients Phone Number

VARCHAR

15

Street address

Street Residence

Street Address of Client

VARCHAR

30

City

Occupied City

City Address of Client

VARCHAR

30

State

Occupied City

State Address of Client

Char

2

Zip code

Zip Code Area

Zip Code Area

Char

7

Special_Need

Food Preference

Food the Client penchant

Text

A

Allergy

Food Allergies

Allergies to any Food

Text

A

2. Table Family Detail

Purpose: Contains all information on Family

Column Name

Aliass

Description

Data Type

Size

House_ID

House Id Number

Specific ID Number for

each family

Char

5

Num_of_People

Number of Peoples

Number of People per House

Char

3

Client_SSN

Client Last 4 SSN

Clients Last 4 SSN Foreign Key

Char

4

Num_Children

Number of Children

Number of Children per House

Char

3

Num_Seniors

Number of Seniors

Number of Seniors per House

Char

3

A

A

A

A

A

3. Table Volunteer

Purpose: Contains all information on Volunteers

Column Name

Aliass

Description

Data Type

Size

Volunteer_Num

Volunteer Number

Specific Number assigned for each Volunteer

VARCHAR

5

Volunteer_Position

Volunteer Position

Position Volunteer working

VARCHAR

10

VolunteerLastName

Volunteer Last Name

Volunteer Last Name

VARCHAR

30

VolunteerFirstName

Volunteer First Name

Volunteer First Name

VARCHAR

30

Phone_Num

Telephone Number

Volunteers Phone Number

VARCHAR

15

Available_Day

Dayss Available

Dayss Available to work

VARCHAR

10

Department

A

Department working in

Text

A

4. Table Visit

Purpose: Contains all Visit Information.

Column Name

Aliass

Description

Data Type

Size

Visit_Num

Visit Number

Unique Visit Number

INT IDENTITY

1,1

Client_SSN

Client Last 4 SSN

Clients Last 4 SSN Foreign Key

Char

4

Volunteer_Num

Volunteer Number

Specific Number assigned for each Volunteer, Foreign Key

VARCHAR

5

Visit_Date

Visit Date

Visit Day

Date

A

Verfiy_ID

Verify Client ID

Check off Verify ID of Client

Spot

A

A

A

A

A

A

5. Table Appointment

Purpose: Contains all Appointment Information.

Column Name

Aliass

Description

Data Type

Size

Appointment_Num

Appointment Number

Unique Appointment Number

INT IDENTITY

1,1

Volunteer_Num

Volunteer Number

Specific Number assigned for each Volunteer, Foreign Key

VARCHAR

5

Client_SSN

Client Last 4 SSN

Clients Last 4 SSN Foreign Key

Char

4

Verified_Document

Verify Yearly Documents

Date Yearly Documents where

verified

Date

A

Appointment_Date

Appointment Day

Schedules Appointment Date

Date

A

Appointment_Time

Appointment Time

Time of Appointment

Time

A

A

A

A

A

A

6. Table Document

Purpose: Contains all Document Information.

Column Name

Aliass

Description

Data Type

Size

Visit_Num

Visit Number

Unique Visit Number,

Foreign Key

INT IDENTITY

1,1

Diver_Licencse

Drivers License

Check off if Client has

Drivers License

Spot

A

Court_Document

Court Document

Check off if Client has

Court Document

Spot

A

Utility_Bill

Utility Bill

Check off if Client has Utility Bill

Spot

A

Other

A

Extra Area

Text

A

A

A

A

A

A

4.2 Datas Shop

DATA STORE DESCRIPTION FORM

Idaho: D1

Name: Client Maestro

Aliass: Customer Master

Description: Contains a record for each Client.

Data Store Features

File Type { Ten } Computer i??Manual

File Format { X } Database iˆ File

Record Size ( Characters ) :200

Block Size:4000

Average Number of Records:250 per month

Maximal Number of Records:8000

Percent Growth per Year:10

Datas Structure:

Client Maestro Record

Primary key: Client SSN

Secondary keys: Telephone Number / Address

Remarks:

The Client Master Record registers new clients and keeps path of present clients. Besides this database tracks the visit day of the months and income. If income is greater than 35,000 the system decision maker will be notified and the client will be put into the hold country until farther probe.

DATA STORE DESCRIPTION FORM

Idaho: D2

Name: Food Maestro

Aliass: Food Database

Description: Holds the record of the measure of nutrient.

Data Store Features

File Type i??Computer { X } Manual

File Format i??Database { Ten } File

Record Size ( Characters ) :

Block Size:

Average Number of Records:

Maximal Number of Records:

Percent Growth per Year:

Datas Structure:

Food Record

Primary key: Food Number

Secondary keys: Type

Remarks:

This Database will maintain path of the measure and type of nutrient distributed. If the measure is low, so the systems decision maker will be notified and the nutrient will hold to be replenished.

DATA STORE DESCRIPTION FORM

Idaho: D3

Name: Client Verification Documentation Master

Aliass: Check List Records

Description: Record of all the client ‘s certification produced at clip of visit.

Data Store Features

File Type { Ten } Computer { X } Manual

File Format { X } Database { Ten } File

Record Size ( Characters ) :200

Block Size:4000

Average Number of Records: 250 per month

Maximal Number of Records:10,000

Percent Growth per Year:5-8 %

Datas Structure:

A file record of all information produced annually for authorities confirmation. A checklist inside the database to verify two types of paper work to verify individuality. Last known day of the month of annual certification to be recorded inside database.

Primary key: Visit Number

Secondary keys: Client_SSN/Volunteer_Num

Remarks:

This File construction allows the Volunteer to verify the client ‘s individuality by look intoing off what signifier of designation the client has produced at clip of visit. If the information for client designation is non produced when requested than the system decision makers will be notified and the nutrient will be withheld.

4.3 Data Flows

DATA FLOW DESCRIPTION

ID:1

Name: Call In

Description: Contains a client who would wish to put an assignment.

Beginning

Person in Need of Food/Client

Finish

Procedure 1

Type of Data Flow

i‚?File i‚? Screen i‚? Report i?? Form i‚? Internal

Data Structure Traveling with the Flow

Client Information

Volume/Time

15/minutes

Remarks: The client will name in to put an assignment to pick up nutrient.

DATA FLOW DESCRIPTION

ID:2

Name: Connects

Description: Contains a client who would wish to put an assignment.

Beginning

Procedure 1

Finish

Person Service Provider

Type of Data Flow

i‚?File i‚? Screen i‚? Report i?? Form i‚? Internal

Data Structure Traveling with the Flow

Client petition an assignment

Volume/Time

30/minutes

Remarks: The client will name in and link with a voluntary who will put the assignment.

DATA FLOW DESCRIPTION

ID:3

Name: Verify Client

Description: Contains client information to verify which will be used to update the client maestro and to put up for an assignment to pick up.

Beginning

Person Service Provider

Finish

Procedure 2

Type of Data Flow

i‚?File i?? Screen i‚? Report i‚? Form i‚? Internal

Data Structure Traveling with the Flow

Client Information

Volume/Time

30/minutes

Remarks: The individual service supplier will verify if the client lives in the local country and meets income criterions in order to have nutrient aids.

DATA FLOW DESCRIPTION

ID:4

Name: New Client

Description: Contains new client information to add to the system.

Beginning

Procedure 2

Finish

Procedure 3

Type of Data Flow

i‚?File i‚? Screen i‚? Report i‚? Form i?? Internal

Data Structure Traveling with the Flow

New client Information

Volume/Time

30/minutes

Remarks: Client information for one new client to be added to the system. The client information can merely be received by facsimile, coming to the location or by the client naming into the nutrient larder straight.

DATA FLOW DESCRIPTION

ID:5

Name: Receive The Request

Description: Contains a petition to add a new client.

Beginning

Procedure 3

Finish

System Administrator

Type of Data Flow

i?? File i‚? Screen i‚? Report i‚? Form i‚? Internal

Data Structure Traveling with the Flow

Client Information

Volume/Time

30/minutes

Remarks: Service supplier is bespeaking from the decision maker to add a new client into the system.

DATA FLOW DESCRIPTION

ID:6

Name: Authorizes The Client

Description: The system decision maker will supply the service supplier entree to add a new client.

Beginning

System Administrator

Finish

Procedure 4

Type of Data Flow

i?? File i‚? Screen i‚? Report i‚? Form i‚? Internal

Data Structure Traveling with the Flow

New client Information to be added

Volume/Time

30/minutes

Remarks: After the system decision maker verifies a new client reference and income, it will authorise the service supplier to add the new client.

DATA FLOW DESCRIPTION

ID:7

Name: Add new client in System

Description: The service supplier is granted entree to add a new client into the system. The client will be added to the client maestro.

Beginning

Procedure 4

Finish

Database 1

Type of Data Flow

i?? File i‚? Screen i‚? Report i‚? Form i‚? Internal

Data Structure Traveling with the Flow

New client Information to be added

Volume/Time

30/minutes

Remarks: After the system decision maker verifies a new client reference and income so it will authorise the service supplier to add the new client.

DATA FLOW DESCRIPTION

ID:8

Name: Client Record

Description: Contains client information that is stored in the database.

Beginning

Client Maestro

Finish

Procedure 2

Type of Data Flow

i?? File i‚? Screen i‚? Report i‚? Form i‚? Internal

Data Structure Traveling with the Flow

Client Information and agenda assignment

Volume/Time

30/minutes

Remarks: The client information will be accessed from the database. It will be updated with a new agenda assignment for each client record. It will besides incorporate the file of a new client who is added to the database.

DATA FLOW DESCRIPTION

ID:9

Name: Set Appointment To Pick Up

Description: Contains client agenda assignment.

Beginning

Procedure 2

Finish

Procedure 5

Type of Data Flow

i‚? File i‚? Screen i‚? Report i‚? Form i?? Internal

Data Structure Traveling with the Flow

Client Information

Volume/Time

30/minutes

Remarks: The client will have a agenda assignment to pick up the nutrient.

DATA FLOW DESCRIPTION

ID:10

Name: On client Visits

Description: Contains client agenda assignment and information.

Beginning

Procedure 5

Finish

Procedure 6

Type of Data Flow

i‚? File i‚? Screen i‚? Report i‚? Form i?? Internal

Data Structure Traveling with the Flow

Client Information and agenda

Volume/Time

30/minutes

Remarks: The client will get during their agenda assignment to pick up the points.

DATA FLOW DESCRIPTION

ID:11

Name: Food Quantity

Description: Contains the measure sum of each nutrient point at the larder.

Beginning

Food Maestro

Finish

Procedure 5

Type of Data Flow

i‚? File i‚? Screen i‚? Report i‚? Form i?? Internal

Data Structure Traveling with the Flow

Client Information

Volume/Time

30/minutes

Remarks: The Service supplier will put up a bag for each scheduled client. Then the measure of each nutrient point will be updated in the system.

DATA FLOW DESCRIPTION

ID:12

Name: Clients Information

Description: Contains the certification for each client. For governmental demands the client designation must be verified each clip they come.

Beginning

Documentation Verification Master

Finish

Procedure 6

Type of Data Flow

i?? File i‚? Screen i‚? Report i‚? Form i‚? Internal

Data Structure Traveling with the Flow

Client signature

Volume/Time

30/minutes

Remarks: The client will show at least two signifiers of designation to verify that they are the right individual who receives the nutrient points each clip.

DATA FLOW DESCRIPTION

ID:13

Name: Food Set Up

Description: Contains the certification confirmation of each client and the list of nutrient points the client will have.

Beginning

Procedure 6

Finish

Procedure 7

Type of Data Flow

i‚? File i‚? Screen i‚? Report i‚? Form i?? Internal

Data Structure Traveling with the Flow

Client signature

Volume/Time

30/minutes

Remarks: The Service supplier will setup the client nutrient before the client arrives. If the client has childs, so the client will have extra points.

DATA FLOW DESCRIPTION

ID:14

Name: Update Client File

Description: Contains the client information on file.

Beginning

Client Maestro

Finish

Procedure 7

Type of Data Flow

i?? File i‚? Screen i‚? Report i‚? Form i‚? Internal

Data Structure Traveling with the Flow

Client Information

Volume/Time

30/minutes

Remarks: The Service supplier will update each client file after the client agenda assignment.

DATA FLOW DESCRIPTION

ID:15

Name: Client Picks Up Food

Description: Contains the nutrient points the client receives.

Beginning

Procedure 7

Finish

Person in Need of Food/Client

Type of Data Flow

i‚? File i‚? Screen i‚? Report i‚? Form i?? Internal

Data Structure Traveling with the Flow

List of nutrient that the client receives.

Volume/Time

30/minutes

Remarks: The client will subscribe and pick up the nutrient that is set up for them.

4.4 Data Structure

Adding new client in the database

Client= Client SSN+

Client Name+

Address+

Telephone Number+

Household Information+

( Particular Need ) +

( Allergy ) +

Legal Document+

( Client Picture )

Client Name = First Name+

( Middle Initial ) +

Last Name

Address = Street+

( Apartment ) +

City+

State+

Nothing

Phone Number = Area Code+

Local Number

Household Information = Number of People+

Seniors+

Childs

Legal Document= [ Credit card measure: Court paperss: Utility Bill: Driver License ]

Particular Need= [ Vegetarian: Vegan: Non-vegetarian ]

Adding Volunteer Information into System

Volunteer= Volunteer Number+

Volunteer Name+

Telephone Number+

( Position ) +

( Department ) +

( Available Day )

Volunteer Name = First Name+

( Middle Initial ) +

Last Name

Phone Number = Area Code+

Local Number

Position= [ Supervisor: Clerk ]

Entering information to make an assignment

Appointment= Appointment Number+

Volunteer Number+

Client SSN+

Legal Documents to Verify+

Appointment Date+

Appointment Time

Appointment Date= Month+

Day+

Year

Appointment Time= Hour+

Minutes+

( Seconds )

Adding The Information on Client ‘s Visit

Visit= Visit Number+

Client SSN+

Volunteer Number+

Visit Date+

Verify ID+

Signature

Visit Date= Month+

Day+

Year

VisitTime= Hour+

Minutes+

( Seconds )

Verify ID= [ Credit card measure: Court paperss: Utility Bill: Driver License ]

4.5 Elementss Description

ELEMENT DESCRIPTION FORM

Name: Client_SSN

Aliass: Customer SSN

Description:

Uniquely identify clients who are being served by the Fishkill Food Pantry.

Component Features

Length: 4

Input Format: 4 ( 4 )

Output Format: 4 ( 4 )

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i‚“Date

i??Numeric

i??Base or i‚“Derived

Validation Standards

Continuous

Upper Limit

& lt ; 10,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

Merely requires last four of SSN for security intents. The Client SSN must be right and contain no infinites. It is a base because it is non generated by the system.

ELEMENT DESCRIPTION FORM

Name: ClientLastName

Aliass: Client legal Last name

Description:

Identifies the client and relates to the signature confirmation procedure.

Component Features

Length: 11

Input Format: 30 ( 11 )

Output Format: 30 ( 11 )

Default Value:

i??Alphabetic

i‚“Alphanumeric

i‚“Date

i‚“Numeric

i??Base or i‚“Derived

Validation Standards

Continuous

Upper Limit

& lt ; 10,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

Must be a valid Idaho so that signature confirmation can be processed. If client does non retrieve SSN, Last Name will be entered into hunt.

ELEMENT DESCRIPTION FORM

Name: ClientFirstName

Aliass: Client legal First name

Description:

Identifies the client and relates to the signature confirmation procedure.

Component Features

Length: 11

Input Format: 30 ( 11 )

Output Format: 30 ( 11 )

Default Value:

i??Alphabetic

i‚“Alphanumeric

i‚“Date

i‚“Numeric

i??Base or i‚“Derived

Validation Standards

Continuous

Upper Limit

& lt ; 10,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

Must be a valid Idaho so that signature confirmation can be processed. If client does non retrieve SSN Last Name will be entered into hunt.

ELEMENT DESCRIPTION FORM

Name: Street address

Aliass: Address of Client

Description:

The Street the Client resides on.

Component Features

Length: 18

Input Format: 30 ( 18 )

Output Format: 30 ( 18 )

Default Value:

i‚“Alphabetic

i??Alphanumeric

i‚“Date

i‚“Numeric

i??Base or i‚“Derived

Validation Standards

Continuous

Upper Limit

& lt ; 10,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

ELEMENT DESCRIPTION FORM

Name: City

Aliass: Client City Address

Description:

The City of where the client resides in.

Component Features

Length: 18

Input Format: 30 ( 18 )

Output Format: 30 ( 18 )

Default Value:

i??Alphabetic

i‚“Alphanumeric

i‚“Date

i‚“Numeric

i??Base or i‚“Derived

Validation Standards

Continuous

Upper Limit

& lt ; 10,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

ELEMENT DESCRIPTION FORM

Name: Nothing

Aliass: Client Zip Code

Description:

The Zip codification of where the client lives to contract down the country.

Component Features

Length: 5

Input Format: 7 ( 5 )

Output Format: 7 ( 5 )

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i‚“Date

i??Numeric

i??Base or i‚“Derived

Validation Standards

Continuous

Upper Limit

& lt ; 10,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

Client Must be within certain Zip codification country to be serviced.

ELEMENT DESCRIPTION FORM

Name: Contact_Num

Aliass: Client Phone Number

Description:

The Clients place phone figure.

Component Features

Length: 14

Input Format: 15 ( 14 )

Output Format: 15 ( 14 )

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i‚“Date

i??Numeric

i??Base or i‚“Derived

Validation Standards

Continuous

Upper Limit

& lt ; 10,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

Necessitate this information to be able to verify assignment. Area codification must be written inside learners. Number besides must incorporate elans to divide. For illustration ( 516 ) -516-4579

ELEMENT DESCRIPTION FORM

Name: Special_Need

Aliass: Client penchant

Description:

Clients penchant on nutrient.

Component Features

Length:

Input Format:

Output Format:

Default Value:

i??Alphabetic

i‚“Alphanumeric

i‚“Date

i‚“Numeric

i??Base or i‚“Derived

Validation Standards

Continuous

Upper Limit

& lt ; 10,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

Volunteer can type a text of what the client prefer nutrient is. Example: Vegetarian, Vegan, and Non-Vegetarian.

ELEMENT DESCRIPTION FORM

Name: Allergy

Aliass: Client ‘s allergic reactions

Description:

Clients Allergies

Component Features

Length:

Input Format:

Output Format:

Default Value:

i??Alphabetic

i‚“Alphanumeric

i‚“Date

i‚“Numeric

i??Base or i‚“Derived

Validation Standards

Continuous

Upper Limit

& lt ; 10,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

Volunteer can type a text of what the client ‘s allergic reactions are. Example lactose intolerant, peanuts, ECT.

ELEMENT DESCRIPTION FORM

Name: Num_of_People

Aliass: Number of People in House Hold

Description:

The Amount of people to be services in one specific house clasp.

Component Features

Length: 2

Input Format: 3 ( 2 )

Output Format: 3 ( 2 )

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i‚“Date

i??Numeric

i‚“Base or i??Derived

Validation Standards

Continuous

Upper Limit

& lt ; 10,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

Volunteers are able to cognize how much nutrient is to be provided to a specific family.

ELEMENT DESCRIPTION FORM

Name: Num_Children

Aliass: Number of Children in House Hold

Description:

The Amount of Children to be services in one specific house clasp.

Component Features

Length: 2

Input Format: 3 ( 2 )

Output Format: 3 ( 2 )

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i‚“Date

i??Numeric

i‚“Base or i??Derived

Validation Standards

Continuous

Upper Limit

& lt ; 10,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

Volunteers are able to cognize how much nutrient and what sort of nutrient is to be provided to a specific family.

ELEMENT DESCRIPTION FORM

Name: Num_Seniors

Aliass: Number of Seniors in House Hold

Description:

The Amount of Senior occupants to be services in one specific house clasp.

Component Features

Length: 2

Input Format: 3 ( 2 )

Output Format: 3 ( 2 )

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i‚“Date

i??Numeric

i‚“Base or i??Derived

Validation Standards

Continuous

Upper Limit

& lt ; 10,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

Volunteers are able to cognize how many people over a certain age live in the family and how much nutrient will be provided.

ELEMENT DESCRIPTION FORM

Name: Volunteer_Num

Aliass: Volunteer ID Number

Description:

Uniquely identify voluntaries within the Fishkill Food Pantry.

Component Features

Length: 2

Input Format: 5 ( 2 )

Output Format: 5 ( 2 )

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i‚“Date

i??Numeric

i‚“Base or i??Derived

Validation Standards

Continuous

Upper Limit

& lt ; 100

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

Each Volunteer must hold an assigned figure to be allowed to utilize the web.

ELEMENT DESCRIPTION FORM

Name: VolunteerLastName

Aliass: Volunteer Last Name

Description:

Uniquely identify voluntaries if there is non a figure assigned

Component Features

Length: 11

Input Format: 11 ( 30 )

Output Format: 11 ( 30 )

Default Value:

i??Alphabetic

i‚“Alphanumeric

i‚“Date

i‚“Numeric

i??Base or i‚“Derived

Validation Standards

Continuous

Upper Limit

& lt ; 100

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

ELEMENT DESCRIPTION FORM

Name: VolunteerFirstName

Aliass: Volunteer First Name

Description:

Uniquely identify voluntaries if there is non a figure assigned

Component Features

Length: 11

Input Format: 11 ( 30 )

Output Format: 11 ( 30 )

Default Value:

i??Alphabetic

i‚“Alphanumeric

i‚“Date

i‚“Numeric

i??Base or i‚“Derived

Validation Standards

Continuous

Upper Limit

& lt ; 100

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

ELEMENT DESCRIPTION FORM

Name: Phone_num

Aliass: Volunteer Phone Number

Description:

Allows the system administers and other voluntary to reach each other

Component Features

Length: 14

Input Format: 15 ( 14 )

Output Format: 15 ( 14 )

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i‚“Date

i??Numeric

i??Base or i‚“Derived

Validation Standards

Continuous

Upper Limit

& lt ; 100

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

Volunteers so can reach each other to work certain yearss.

ELEMENT DESCRIPTION FORM

Name: Available_Day

Aliass: Volunteer ‘s Availably

Description:

Allows the system administers and other voluntary to see when others are available to work.

Component Features

Length: 9

Input Format: 10 ( 9 )

Output Format: 10 ( 9 )

Default Value:

i??Alphabetic

i‚“Alphanumeric

i‚“Date

i‚“Numeric

i‚“Base or i??Derived

Validation Standards

Continuous

Upper Limit

& lt ; 100

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

Volunteers can see when others are able to cover their displacement.

ELEMENT DESCRIPTION FORM

Name: Visit_Num

Aliass: Visit Number

Description:

Uniquely place the twenty-four hours a client came in to acquire nutrient.

Component Features

Length:

Input Format:

Output Format:

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i‚“Date

i‚“Numeric

i??Int Identity

i‚“Base or i??Derived

Validation Standards

Continuous

Upper Limit

& lt ; 100,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

Volunteers can so see when the last clip a client came in and what was picked up.

ELEMENT DESCRIPTION FORM

Name: Visit_Date

Aliass: Visit Date

Description:

The twenty-four hours a client came in to pick up nutrient.

Component Features

Length:

Input Format:

Output Format:

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i??Date

i‚“Numeric

i‚“Base or i??Derived

Validation Standards

Continuous

Upper Limit

& lt ; 100,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

Volunteers can so see when the last clip a client came in.

ELEMENT DESCRIPTION FORM

Name: Verify_Id

Aliass: Verify the clients designation

Description:

The voluntary cheques certification to verify the designation of the client.

Component Features

Length: 1

Input Format: 1

Output Format: 1

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i‚“Date

i??Numeric

i‚“Base or i??Derived

Validation Standards

Continuous

Upper Limit

& lt ; 100,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

Volunteers must look over certification and information to verify the designation of the client who is picking up the nutrient.

ELEMENT DESCRIPTION FORM

Name: Appointment_Num

Aliass: Appointment Number

Description:

Uniquely place the assignment. Who made and assignment and when it was made.

Component Features

Length:

Input Format:

Output Format:

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i‚“Date

i‚“Numeric

i??Int Identity

i‚“Base or i??Derived

Validation Standards

Continuous

Upper Limit

& lt ; 100,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

Volunteers create assignments for when the clients come in to pick up nutrient.

ELEMENT DESCRIPTION FORM

Name: Verified_Document

Aliass: When the annual Documentation was Verified

Description:

Shows when the last clip the annual certification was verified.

Component Features

Length:

Input Format:

Output Format:

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i??Date

i‚“Numeric

i‚“Base or i??Derived

Validation Standards

Continuous

Upper Limit

& lt ; 100,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

When a client calls in, a voluntary can look up when the last clip the annual certification was reviewed and state the client what they need to convey in.

ELEMENT DESCRIPTION FORM

Name: Appointment_Date

Aliass: When the Appointment was scheduled

Description:

Shows when the assignment was scheduled and lets the other voluntaries know to put up the nutrient for their choice up.

Component Features

Length:

Input Format:

Output Format:

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i??Date

i‚“Numeric

i‚“Base or i??Derived

Validation Standards

Continuous

Upper Limit

& lt ; 100,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

When the assignment was created for and when the client is expected to come in.

ELEMENT DESCRIPTION FORM

Name: Appointment_Time

Aliass: When the Appointment was scheduled

Description:

Shows when the assignment was scheduled and lets the other voluntaries know to put up the nutrient for their choice up.

Component Features

Length:

Input Format:

Output Format:

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i‚“Date

i‚“Numeric

i??Time

i‚“Base or i??Derived

Validation Standards

Continuous

Upper Limit

& lt ; 100,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

When the client is expected to come in.

ELEMENT DESCRIPTION FORM

Name: Driver_License

Aliass: Drivers License

Description:

Verify the client has produced their Divers License.

Component Features

Length: 1

Input Format: 1

Output Format: 1

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i‚“Date

i?? Numeric

i??Base or i‚“Derived

Validation Standards

Continuous

Upper Limit

& lt ; 100,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

ELEMENT DESCRIPTION FORM

Name: Court_Document

Aliass: Court Document

Description:

Verify that the client has produced a tribunal papers

Component Features

Length: 1

Input Format: 1

Output Format: 1

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i‚“Date

i?? Numeric

i??Base or i‚“Derived

Validation Standards

Continuous

Upper Limit

& lt ; 100,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

ELEMENT DESCRIPTION FORM

Name: Utility_Bill

Aliass: Utility Bill

Description:

Verify that the client has produced a public-service corporation measure for designation.

Component Features

Length: 1

Input Format: 1

Output Format: 1

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i‚“Date

i?? Numeric

i??Base or i‚“Derived

Validation Standards

Continuous

Upper Limit

& lt ; 100,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

ELEMENT DESCRIPTION FORM

Name: Other

Aliass: Other Ext.

Description:

Separate subdivision where voluntaries can come in if there is another manner the identified the client.

Component Features

Length:

Input Format:

Output Format:

Default Value:

i‚“Alphabetic

i‚“Alphanumeric

i‚“Date

i?? Text

i‚“Numeric

i‚“Base or i??Derived

Validation Standards

Continuous

Upper Limit

& lt ; 100,000

Lower Limit

& gt ; 0

Discrete

Value Meaning

Remarks:

4.6 Input and Output Analysis Form

INPUT AND OUTPUT ANALYSIS FORM

Input/Output name: Adding New Client into Database System

User Contact: Mani Singh

i‚“i??Input i‚“Output

i‚“i??Form i‚“Report i‚“Screen i‚“Undetermined

Sequencing Element ( s ) Zip Code ( Page Sequence )

Component Name

Length

B/D

Edit Standards

Current Date

6

Bacillus

( System Supplied )

Client SSN

4

Bacillus

Numeral

Client First Name

30

Bacillus

Not Spaces

Client Last Name

30

Bacillus

Not Spaces

Client Middle Initial

1

Bacillus

A through Z or Space

Street

30

Bacillus

Not Spaces, alphanumeric

Apartment

30

Bacillus

Not Spaces

City

30

Bacillus

Not Spaces

State

2

Bacillus

Valid State Abbr.

Nothing

9

Bacillus

Numeric, Last 4 Opt

Telephone Number

14

Bacillus

Numeral

Number of Peoples

3

Calciferol

Numeral

Seniors

4

Calciferol

Numeral

Childs

3

Calciferol

Numeral

Credit Card Bill

1

Bacillus

BIT1=yes/or true, 0=false/no

Household ID

5

Bacillus

Numeral

Court Documents

1

Bacillus

BIT 1=yes/or true, 0=false/no

Utility Bill

1

Bacillus

BIT 1=yes/or true, 0=false/no

Particular Need

30

Bacillus

Text

Allergy

30

Bacillus

Text

Remarks: Print 1 page for each client

INPUT AND OUTPUT ANALYSIS FORM

Input/Output name: Adding Volunteer Information into System

User Contact: Sarah Reid

i‚“i??Input i‚“Output

i‚“Form i‚“Report i‚“Screen i‚“Undetermined

Sequencing Element ( s )

Component Name

Length

B/D

Edit Standards

Volunteer figure

5

Calciferol

Numeral

Volunteer First Name

30

Bacillus

Not Spaces

Volunteer Last Name

30

Bacillus

Not Spaces

Volunteer Middle Initial

1

Bacillus

A through Z or Space

Position

20

Bacillus

Not Spaces

Department

20

Bacillus

Not Spaces

Handiness

10

Calciferol

Not Spaces

Telephone Number

15

Bacillus

Numeral

Remarks:

INPUT AND OUTPUT ANALYSIS FORM

Input/Output name: Entering information to make an assignment

User Contact: Mani Singh

i‚“Input i‚“Output

i‚“Form i‚“Report i‚“Screen i‚“Undetermined

Sequencing Element ( s )

Component Name

Length

B/D

Edit Standards

Appointment figure

5

Bacillus

Numeral

Volunteer Number

5

Calciferol

Numeral

Client SSN

4

Bacillus

Numeral

Legal Documents to Verify

1

Bacillus

BIT 1=yes/or true, 0=false/no

Appointment Date

6

Bacillus

Numeral

Appointment Time

2

Bacillus

Numeric, Includes hour/min/sec

Remarks

INPUT AND OUTPUT ANALYSIS FORM

Input/Output name: Adding Information on Client Visit

User Contact:

i‚“i??Input i‚“Output

i‚“Form i‚“Report i‚“Screen i‚“Undetermined

Sequencing Element ( s )

Component Name

Length

B/D

Edit Standards

Visit figure

4

Bacillus

Numeral

Client SSN

4

Bacillus

Numeral

Volunteer Number

5

Bacillus

Numeral

Visit Date

6

Bacillus

Includes month/day/year

Verify ID

1

Bacillus

BIT 1=yes/or true, 0=false/no

Signature

1

Bacillus

BIT 1=yes/or true, 0=false/no

Visit clip

6

Bacillus

Numeric, Includes hour/min/sec

Legal Documents to Verify

1

Bacillus

BIT 1=yes/or true, 0=false/no

Remarks

Appendix A: Glossary of Footings and Acronyms

Entree

A database direction system from Microsoft

Actor

A user of the system in UML. The ‘Actor ‘ can be a system, a human, or a device such as a keyboard that exists outside the system and interacts in a specific manner with the system.

Datas

Facts and statistics collected together for mention or analysis. Often organized into rows and columns and can typically be visualized by graphs or images

Database

It is a aggregation of informations stored electronically, centrally stored and used to pattern certain facets of world

Data Dictionary

Data Dictionary is created by systems analysts who base information off of informations flow diagrams. It is a aggregation of informations about informations that is derived from roll uping and organizing specific nomenclature

Data Component

A simple aggregation of informations, which can be either establish or derived, and clearly defined in the information lexicon.

Data Flow Diagram ( DFD )

In a concern system, a graphical illustration of information flows, informations shops, and informations procedures

Datas Shop

Datas that is represented utilizing an open-ended rectangle in a DFD.

Functional Requirements

A set of maps that define what a system is suppose to carry through. These could be a set of inputs, end products, every bit good as behaviours. For illustration: computations, use of informations, proficient inside informations every bit good as other specific functionalities

IT ( Information Technology )

The country of pull offing engineering, this covers a big scope of countries such as information systems and computing machine package

Nonfunctional Requirements

Is a demand that specifies standards, which can be used to find the operation of a system.

Primary Key

A Primary Key ( PK ) is a key that unambiguously identifies a record

SQL ( Structured Query Language )

It is a coding linguistic communication that is designed to pull off informations in Relational Database Management

SQL Server

A relational database waiter in which its primary map is to hive away and recover information. This is requested by other package applications, either on the same computing machine or those running on another computing machine across a web. Developed by Microsoft

UML ( Unified Modeling Language )

Unified Modeling Language provides a standardised set of tools to make ocular theoretical accounts of a system and document the object-oriented design and analysis of a package system under development

Use Case

In Unified Modeling Language, a list of stairss which typically define interactions between an Actor and a system to bring forth something of value and accomplish a end. In Use Cases, histrions utilizing the system normally initiate an event that will get down a series of interactions in the system

Appendix B: Actor Card games

Actor Specification

Actor Name: Murray Suggitt

Type: Primary

Personality: Tocopherol

Abstraction: No

Role Description: Person that inputs information into system and makes certain that there is adequate nutrient.

Actor Goals:

Improve service to local occupants

Use Cases Involved with:

Add Client

View Clients Information

Update Client Information

Actor Specification

Actor Name: Judy Van Nostard

Type: Primary

Personality: Tocopherol

Abstraction: No

Role Description: Person that inputs information into system and makes certain that there is adequate nutrient.

Actor Goals:

Improve service to local occupants

Use Cases Involved with:

Add Client

View Clients Information

Update Client Information

Actor Specification

Actor Name: Irene Zedo

Type: Primary

Personality: Tocopherol

Abstraction: No

Role Description: Person that inputs information into system and makes certain that there is adequate nutrient.

Actor Goals:

Improve services to local occupants

Use Cases Involved with:

Add Client

View Clients Information

Update Client Information

Actor Specification

Actor Name: Richard Lanni

Type: Secondary

Personality: Tocopherol

Abstraction: No

Role Description: Person that interacts and maintains the system.

Actor Goals:

Update systems

Provide good feedback

Use Cases Involved with:

Update System

Actor Specification

Actor Name: Edith Schmidt

Type: Primary

Personality: Tocopherol

Abstraction: No

Role Description: Volunteer that makes assignment and fills out information to give to the decision maker at the other computing machine.

Actor Goals:

Provide high degree of service to client

Provide good feedback

Use Cases Involved with:

View Clients Information

Make assignment

Update Client information

Verify signature

Actor Specification

Actor Name: Donald Vanostrand

Type: Primary

Personality: Tocopherol

Abstraction: No

Role Description: Volunteer that makes assignment and fills out information to give to the decision maker at the other computing machine.

Actor Goals:

Provide high degree of service to client

Provide good feedback

Use Cases Involved with:

View Clients Information

Make assignment

Update Client information

Verify signature

Actor Specification

Actor Name: Client

Type: Primary

Personality: Tocopherol

Abstraction: No

Role Description: The client that interact with the Front Desk Volunteer to do an assignment for nutrient pickup.

Actor Goals:

To be treated in an timely mode

Use Cases Involved with:

Verify signature

Make Appointment

Actor Specification

Actor Name: Hudson Valley Food Bank

Type: External

Personality: None

Abstraction: Yes

Role Description: If there is non adequate nutrient in the Panty so nutrient is collected from the Hudson Food Bank.

Actor Goals: None

Use Cases Involved with: None

Actor Specification

Actor Name: Government

Type: External

Personality: None

Abstraction: Yes

Role Description: The authorities adjutant and financess. Regulation that need to be followed to be able to acquire support.

Actor Goals:

Provide assistance to local concerns

Use Cases Involved with: None

Appendix C: Scope of Work

Context Diagram

Diagram Level 0

Diagram Level 1

2

3

4