Boone Cemetery Management Software May0536

1
Boone Cemetery Management Software May05-36

• Greg Thede, Director, Boone Parks Department

Client
Faculty Advisor
Dr. Kothari
Team Members
Joseph Heiniger, Roderic Henry, Adam Lorensen,
Andrew Mueller
10 February 2005
2
Presentation Outline

• Introduction
• Project Activity Descriptions
• Resources and Schedules
• Closing

3
Definitions

• CVS Concurrent Versioning System
• IDE Integrated Development Environment

4
Acknowledgements

• Dr. Kothari
• Greg Thede and David Briley

5
General Problem Statement

• Difficulty locating plots
• Multiple software solutions
• Direct access to database
• Redundant hand-written forms

6
General Solution Approach

• Simple interface to coordinate all operations
• Automated form population printing
• Reminders program
• Queries Allow users to easily search the entire
  database

7
Operating Environment

• Windows XP operating system
• Small office environment
• A few users
• Sporadic interaction with system

8
Intended Uses Users

• Users A few select Boone employees
• Uses
• Manage operational data for cemetery
• Provide support for searching cemetery records
• Print summary reports

9
Assumptions

• The software will not communicate with any other
  systems
• The database will always fit on a single local
  hard disk
• The number of burial records will not exceed
  100,000
• Only one instance of the program will be run at
  one time
• The workstation will have a printer to print the
  forms

10
Limitations

• Software must work on existing workstation.
• Software deliverable must be of appropriate size
  and format to be distributed on one CD.
• Software must work in isolation from external
  actors.
• The product must not prohibit the normal
  operation of other systems on the workstation.
• The forms to be printed must operate in a
  standard format accepted by most printers.

11
Deliverable

• Software package
• CD distribution
• Documentation including tutorials, screenshots
  and references

12
Project Activities
13
Present Accomplishments

• Decided on platform
• Defined scope and requirements
• Developed loose design
• Set up development environment

14
Approaches Considered

• Java - portable, more difficult to build GUI
• Visual Basic - simple to build GUI
• C - more comprehensive than VB

15
Project Definition Activities

• Meetings with Boone personnel
• Requirements definition
• Use-case development

16
Research Activities

• Mapping software integration
• Automatic business form printing
• Software testing frameworks explored
• Software repository configuration

17
Design Activities

• Domain modeling
• Database organization
• Software object definitions

18
Implementation Activities

• Set up source code repository
• Started implementing a single use-case scenario
  (Burial Plot Sale)

19
Testing and its Results

• No completed code modules so no testing thus far
• Testing software researched, tentatively decided
  on NUnit test framework

20
Resources and Schedules
21
Personal Efforts
Hours broken down by task
22
Other Resource Efforts
23
Total Financial Requirements
24
Tasks Schedule
25
Deliverable Schedule
26
Closing Material
27
Project Evaluation

• Scheduling and milestones
• Personal effort requirements
• Financial requirements

28
Milestones

• Project plan
• Project poster
• Design document
• Screenshots

• Working prototype
• End product user documentation
• Final report

29
Commercialization

• Operations of cemetery are not standard
• Software design customized to the clients needs
• No plans to commercialize

30
Recommendations for Future Work

• E-mail notifications for payment reminders
• Automated e-mail billing
• Additional payment options
• More options for client to customize software

31
Lessons Learned What went well

• Repository creation
• Development Environment setup
• Clients availability

32
Lessons Learned What did not go well

• Integrating mapping software
• Existing records have no standard data format

33
Lessons LearnedTechnical knowledge gained

• C programming language
• Subversion (SVN)
• Business format printing
• Software engineering processes
• Product integration

34
Lessons LearnedNon-technical knowledge gained

• Project management
• Communicating with non-technical clients
• Working with other teams

35
Lessons LearnedWhat would be done differently

• Researched mapping product earlier
• Started development earlier

36
Risks and Risk Management

• Loss of team member
• Proposed IDE
• Proposed solution
• No anticipated risks were encountered
• Unanticipated risk
• Software integration with mapping software
• No changes to risk management

37
Closing Summary Problem

• Information in database not easy to retrieve
• Multiple (unnecessary) data entries
• Needed a way to be reminded when payments are due

38
Closing Summary Approach

• Software solution
• Simple GUI interface
• Single data entry
• Easy to query database
• C Microsoft Access
• Visual Studio .NET

39
Closing Summary Resultant Solution

• Simple, easy-to-use software application
• Prints required forms
• Reminders feature
• Summary reports

40
Questions
41
Thank You