Database and Web Search Application for Disabled Adults and Children

1
Database and Web Search Application for Disabled
Adults and Children

• Faculty Advisor Manimaran Govindarasu
• Client Iowa Department of Human Services
• Dec06-05
• Kyle Curran
• Seth Gillespie
• Carlos Ortiz
• Ryan Wiegel
• Presented On November 9, 2006

2
Acknowledgements

• Marion Kresse
• Professor Manimaran Govindarasu

3
Presentation Outline

• Problem Description
• Definitions
• Approaches Considered
• Detailed design
• Resource and Schedules
• Project Evaluation
• Closing Summary

4
Problem Description

• Lack of a centralized source of information on
  various services offered by aid agencies within
  Iowa
• Many people do not know that programs exist to
  offer them aid
• Too many programs for one person to keep track
• Iowa COMPASS database can overwhelm users
• Existing search site is not user friendly

5
General Approach

• Web application with backend databases
• XML database to store services that are
  searchable
• Interface with Iowa Compass database to get
  service contact information
• Management software to add/remove/edit services
• Map of results for which user might be eligible

6
Definitions

• ASP.NET Active Server Pages
• BOBBY - A specification for web sites that are
  easily accessible by people with disabilities
• HIPAA Health Insurance Portability and
  Accountability Act
• PHP - A scripting language used for creating web
  applications
• SQL - Scripted Query Language
• GIS - Geographical Information System
• Iowa COMPASS Referral service for people in
  Iowa with disabilities.
• IDHS Iowa Department of Human Services
• Taxonomy - Collection of database entries that
  offer similar services
• WIC/Head Start Two taxonomies included in
  initial web application

7
Intended Users

• Employees of IDHS and Iowa COMPASS
• Employees of other public assistance services
• People with disabilities in search of services
• Families or friends of people with disabilities
• Administrators of the Iowa COMPASS website

8
Intended Uses

• To find services for which a person might be
  eligible
• To locate general and support services
• To locate services based on location
• Add/Remove/Edit services in the XML database

9
Assumptions

• The users are assumed to possess basic internet
  navigation skills.
• The user will be able to read at a middle school
  level.
• The user will have access to a computer with
  internet access.
• The list of survey questions will be provided.

10
Limitations

• The end product must be BOBBY compliant.
• The web page must be HIPAA compliant.
• The initial version will include 18 different
  services.

11
End product and other deliverables

• Software Application
• ASP.NET files
• XML Schema files
• Website Documentation
• Users Manual
• Link on website

12
Present accomplishments

• Software application complete
• Creation of web forms
• Creation/Implementation of XML database
• Integration with Iowa COMPASS database
• Alpha Testing
• Website Documentation
• Completed
• User Manual
• Completed

13
Approaches Considered
14
Development Technology Considerations

• PHP
• Advantages
• Open Source
• Cross Platform
• Disadvantages
• Very little support for connecting to SQL server
  databases

• ASP.NET
• Advantages
• Microsoft Product
• Good libraries to connect to SQL server databases
• Disadvantages
• Only runs in Windows

Selection ASP.NET
15
IDE Considerations

• Microsoft Visual Studio .NET 2005
• Advantages
• Native support for ASP.Net
• Includes support for VC, C, etc.
• Disadvantages
• Only runs in Windows

• Eclipse
• Advantages
• Open Source
• Disadvantages
• Needs plug-in for ASP.Net
• No support for open source plug-ins

• Selection Visual Studio .NET 2005

16
GIS Software Considerations

• Google Maps API
• Advantages
• Dynamic Maps
• Allows Navigation
• Disadvantages
• Beta service
• Google reserves right to advertise or cancel
  service

• Mapzoom
• Advantages
• No remote connection
• No advertisement or service cancellation risks
• Disadvantages
• Uses Static Maps which need to be updated

Selection Google Maps API
17
Programming Language Considerations

• Visual C
• Advantages
• Team was very familiar with C
• Disadvantages
• Not many examples or documentation available for
  reference

• C
• Advantages
• Lots of examples and documentation available for
  reference
• Disadvantages
• Team had no experience with the language

Selection C
18
Project Definition Activities

• Met with client
• Redefined the project definition
• Discussed additional features to add complexity
• Finalized project definition and additional
  features

19
Research Activities

• Made list of possible technologies
• Researched listed technologies
• Compared pros and cons
• Made technology selections

20
Design Activities
21
Design Constraints

• Locally Stored Information
• Services in database will be in the state of Iowa
• Questions are provided by client
• Web pages must be BOBBY compliant

22
Design Constraints (contd)

• Initially implement 18 programs
• Phase Implementation
• Phase I Questionnaire forms and Administration
  application
• Phase II Google Map API Implementation

23
Phase I
24
Screen Flow Diagrams
Page flow for administration console
Page flow of end user general use
25
Top Level Data Interaction
26
End User Web Forms

• Personal Information Page
• Income
• Age
• Size of household
• Zip Code and County
• Dynamic Questionnaire
• Based on personal information
• Formed from the database

27
(No Transcript)
28
System Architecture
29
Administration Functions

• Add Program
• Enter valid program id and name
• Create new personal information tables
• Maximum income per number of people in house
• Select from a list of questions
• Create new questions
• Build solutions
• Based on information tables and questions

30
Administration Functions (cont)

• Remove Program
• Select from a list of existing programs
• Delete program XML file
• Able to de-activate and activate programs

31
Administration Functions (cont)

• Edit Program
• Select from a list of existing programs
• Add/remove/edit personal information tables
• Add/remove questions
• Add/remove/edit solutions

32
Phase II
33
Phase II End User Page Flow
34
Implementation Activities

• Database schema that we received was incomplete
• Had to make changes to support taxonomies
• A taxonomy is a collection of entries that offer
  similar services. Ex. Head Start, WIC
• Had to make changes to support multiple service
  entries
• Many services have multiple locations that only
  service their immediate area

35
Testing and Modification Activities

• Unit Testing
• Black-Box Testing
• Regression Testing
• Integration Testing
• Alpha-Testing on local test server

36
Testing and Modification Activities Contd

• Initial Client Feedback
• Teleconference with Iowa Compass Contact, Jane
  Gay
• Implemented on clients server for site testing

37
Resources and Schedules
38
Resources
39
Resources (contd)
Final Financial Requirements Final Financial Requirements Final Financial Requirements
Item W/O Labor With labor
Project Poster 23.00 23.00
Poster Board 10.00 10.00
Glue 3.00 3.00
Printing Free Free
Lamination 10.00 10.00
Bound Documentation 25.00 25.00
Labor (at 10 per hour) 7,090
Seth Gillespie 1,720
Carlos Ortiz 1,830
Kyle Curran 1,790
Ryan Wiegel 1,750
Total Project Costs 48.00 7,138
40
Project Schedule
41
Project evaluation

• Software package is completed
• Compiling of all team documentation and help
  screens for software is done
• Software will be implemented within Iowa
  Compasss new web site and released to the public
  along with the release of the web site by site
  developer
• Successful Project

42
Commercialization

• No commercialization has been planned as the
  software is specifically designed to work with
  the customized setup at Iowa Compass
• Product meets the specific goals of the client
  and is suited to be upgraded for the clients
  needs in the future

43
Recommendations for Additional Work

• Additional functionalities could be added to the
  system if the client would desire it in the
  future
• These functionalities could be implemented by
  either a private sector programming firm or a
  future senior design team

44
Lessons Learned

• Create more specific individual goals
• Increase accountability
• ASP.NET/C development
• Client interaction
• Solidified overall software development skills

45
Possible Risks

• Loss of important data such as source code or
  user data
• Loss of a team member to unforeseen circumstances
• Lack of expertise when related to implementation
  of elements of the project
• Missed deadlines

46
Risk Management

• Source code and documentation backups stored in
  multiple locations
• Each team member was required to understand the
  whole of the project
• Thorough research
• Stay ahead of schedule
• Allow for flexibility within deadlines

47
Closing Summary

• Currently it is difficult for persons with
  disabilities to find information on available
  services
• Creation of a web application to determine
  possible services for which a person may be
  eligible will facilitate location of information
• The team has successfully created a web
  application that meets the client specifications

48
Screen Shots
49
(No Transcript)
50
(No Transcript)
51
(No Transcript)
52
(No Transcript)
53
(No Transcript)
54
(No Transcript)
55
(No Transcript)
56
(No Transcript)
57
(No Transcript)
58
Questions