1. Brethren Housing Association Berenice Vasquez-Dominguez Steve Salzone Levi Schmieg Jarred Neff Point of contact: Darrel Reinford

2. Presentation Overview 1. Executive Summary 2. Project Introduction 3. Project Overview 4. Application Demonstration 5. Application Impact 6. Project Strengths and Weaknesses 7. Sponsor Organization Assessment 8. Lessons Learned 9. Conclusion

3. Executive Summary The Brethren Housing Association is a Harrisburg-based non-profit organization that provides “transitional housing for individuals and families with housing needs in an atmosphere of hope, respect, humility, and patience.” The Brethren Housing Association is a Harrisburg-based non-profit organization that provides “transitional housing for individuals and families with housing needs in an atmosphere of hope, respect, humility, and patience.”

4. Executive Summary (cont.) Replaces ill-fitting, inefficient, off the shelf system (Church Membership Plus). Replaces ill-fitting, inefficient, off the shelf system (Church Membership Plus). We developed a Microsoft Access database system to manage and track information pertaining to: We developed a Microsoft Access database system to manage and track information pertaining to: Participants and their childrenParticipants and their children DonorsDonors VolunteersVolunteers User friendly GUI User friendly GUI Searchable, Scalable, Adaptable, Easy to update and expand Searchable, Scalable, Adaptable, Easy to update and expand

5. Project Introduction Practices and Methodologies Practices and Methodologies UML lifecycle approachUML lifecycle approach StoryboardingStoryboarding Use-case drivenUse-case driven Iterative and incrementalIterative and incremental Rapid application developmentRapid application development Sponsor feedback early and oftenSponsor feedback early and often Utilized strengths and weaknesses of team membersUtilized strengths and weaknesses of team members

6. Project Overview Milestone 1

7. Project Overview Milestone 1 Project Proposal Project Proposal Problem Statement Problem Statement As-Is system was designed to organize information relating church congregationsAs-Is system was designed to organize information relating church congregations As-Is system has a high learning curve, which discourages its use and its full potentialAs-Is system has a high learning curve, which discourages its use and its full potential Current system is too complex for what is accomplishesCurrent system is too complex for what is accomplishes Level of customization is too low to meet many basic needsLevel of customization is too low to meet many basic needs Approximately 1,300 records currentlyApproximately 1,300 records currently

8. Project Overview Milestone 1 Project objectives Project objectives Create functioning system to replace As-is systemCreate functioning system to replace As-is system Increased Functionality & FlexibilityIncreased Functionality & Flexibility Intuitive Aesthetically Pleasing UIIntuitive Aesthetically Pleasing UI Easily Generated Reports and Common QueriesEasily Generated Reports and Common Queries A simpler custom DB that has only what they need and is easy to use.A simpler custom DB that has only what they need and is easy to use. High scalability potentialHigh scalability potential

9. Project Overview Milestone 1 Project Scope and Constraints Project Scope and Constraints Focus on intuitive UIFocus on intuitive UI User needs to:User needs to: Add, store, and search personal information Add, store, and search personal information Use mail merge for labels and letters Use mail merge for labels and letters Track advanced info of Donors, Volunteers, and Participants and their children Track advanced info of Donors, Volunteers, and Participants and their children 2 Desktops, 1 Laptop –MS Windows 98, MS Office 20002 Desktops, 1 Laptop –MS Windows 98, MS Office 2000 Dial up InternetDial up Internet

10. Project Overview Milestone 1 Project Strategy Project Strategy Utilize the skills of the team membersUtilize the skills of the team members Create rapid iterations for approvalCreate rapid iterations for approval Storyboarding approach to UIStoryboarding approach to UI We will prioritize functions in order to guarantee a shippable productWe will prioritize functions in order to guarantee a shippable product Continue expanding functionality upon approval of completed versionsContinue expanding functionality upon approval of completed versions Incremental approachIncremental approach

11. Project Overview Milestone 2

12. Project Overview Milestone 2 Business Process Selection Analysis Business Process Selection Analysis We were improving an already automated processWe were improving an already automated process We were not re-engineering the business processWe were not re-engineering the business process Business Process Improvement (BPI)Business Process Improvement (BPI)

13. Project Overview Milestone 2 Increment Allocation Increment Allocation Increment I – Basic InformationIncrement I – Basic Information Record basic calling and mailing information for donors, volunteers, and participants Record basic calling and mailing information for donors, volunteers, and participants View all above information on one page View all above information on one page Search easily by selectable criteria Search easily by selectable criteria Mail merge Mail merge

14. Project Overview Milestone 2 Increment Allocation Increment Allocation Increment II – Advanced TrackingIncrement II – Advanced Tracking Donors Donors Volunteers Volunteers Participants and their children Participants and their children

15. Project Overview Milestone 2 Increment Allocation Increment Allocation Increment III – Button FunctionsIncrement III – Button Functions All functions put into Buttons All functions put into Buttons Mail Merge Mail Merge Queries Queries Reports Reports

16. Project Overview Milestone 2

17. Project Overview Milestone 2 Feature Vector Diagram

19. Project Overview Milestone 3

20. Milestone Overview Milestone 3 UML Structural Model UML Structural Model UML Behavioral Model UML Behavioral Model Low fidelity prototype Low fidelity prototype Physical design Physical design Technology rational Technology rational

21. Milestone Overview Milestone 3 Personal Info Donations VolsHours Participants Children * 1 1 1 * * 1 1 UML Structural Model

22. Milestone Overview Milestone 3 Low fidelity prototype Low fidelity prototype

23. Milestone Overview Milestone 3 Technology Rational Technology Rational Microsoft Access 2000Microsoft Access 2000 Sponsor organization already has itSponsor organization already has it Team knowledge and background lends itself to AccessTeam knowledge and background lends itself to Access

24. Milestone Overview Milestone 4

25. Milestone Overview Milestone 4.1 Increment I functionality Increment I functionality CRUD for Personal Info TableCRUD for Personal Info Table Met with sponsorMet with sponsor Approved design with added changesApproved design with added changes Increment 1 CompletedIncrement 1 Completed

26. Milestone Overview Milestone 4.2 Increment 2 functionality Increment 2 functionality Advanced tracking information Advanced tracking information Donor Donor Volunteer Volunteer Participant and children Participant and children Met with sponsorMet with sponsor Approved design with added changesApproved design with added changes Increment 2 completedIncrement 2 completed

27. Milestone Overview Milestone 4.3 Increment 3 functionality Increment 3 functionality Created Buttons for functions Created Buttons for functions Mail Merge Mail Merge Queries Queries Reports Reports Test cases created with 100% passingTest cases created with 100% passing Met with sponsorMet with sponsor Approved design with no added changesApproved design with no added changes Increment 3 completedIncrement 3 completed

28. Milestone Overview Milestone 5

29. Milestone Overview Milestone 5 We plan to deliver the system Friday May 7 th We plan to deliver the system Friday May 7 th We will train Darrel and the new Executive Director We will train Darrel and the new Executive Director

30. Application Demonstration

31. Application Impact Organization is not 100% sure of implementation Organization is not 100% sure of implementation New Executive Director as of May 1 New Executive Director as of May 1 Will at least serve as a benchmark for new system purchases Will at least serve as a benchmark for new system purchases System has all necessary functionality for full scale implemented System has all necessary functionality for full scale implemented

32. Project Strengths & Weaknesses Strengths Strengths Point of contactPoint of contact Technical knowledge & Availability Technical knowledge & Availability Team dynamicsTeam dynamics Got along well Got along well No major conflicts No major conflicts PerformancePerformance Met ALL planned increments Met ALL planned increments

33. Project Strengths & Weaknesses Weaknesses Weaknesses Levi in NYLevi in NY Documentation overloadDocumentation overload Limited knowledge of Access and VBALimited knowledge of Access and VBA We learned as worked, which took time We learned as worked, which took time

34. Sponsor Organization Assessment Sponsor was very accepting of our efforts Sponsor was very accepting of our efforts System may or may not be used System may or may not be used Sponsor agrees our developed system is better than their current system Sponsor agrees our developed system is better than their current system Data migration is time consuming Data migration is time consuming New Executive Director New Executive Director

35. Sponsor Organization Assessment Here’s what our Point of Contact, Darrel Reinford had to say: Here’s what our Point of Contact, Darrel Reinford had to say:

37. Lessons Learned Access is powerful and complicated Access is powerful and complicated Importance of team members Importance of team members Save and backup often Save and backup often Version and configuration management Version and configuration management Receive customer feedback early and often Receive customer feedback early and often Details and finishing touches are very time consuming Details and finishing touches are very time consuming

38. Lessons Learned It takes hard work… It takes hard work…

39. Lessons Learned It takes long hours… It takes long hours…

40. Lessons Learned Expect frustrations… Expect frustrations…

41. Lessons Learned Success is rewarding… Success is rewarding…

42. Conclusion There is nothing like real world experience There is nothing like real world experience