may05-36: boone cemetery management software boone cemetery management software may05-36 greg thede,...

May05-36: Boone Cemetery Management Software

Boone Cemetery Management Boone Cemetery Management SoftwareSoftware May05-36May05-36

Greg Thede, Director, Greg Thede, Director, Boone Parks Boone Parks DepartmentDepartmentDr. KothariDr. Kothari

Joseph Heiniger, Roderic Joseph Heiniger, Roderic Henry, Adam Lorensen, Henry, Adam Lorensen, Andrew MuellerAndrew Mueller

10 February 2005

Client:

Faculty Advisor:Team Members:


Presentation OutlinePresentation Outline

• IntroductionIntroduction

• Project Activity DescriptionsProject Activity Descriptions

• Resources and SchedulesResources and Schedules

• Closing Closing


DefinitionsDefinitions

• CVS = Concurrent Versioning SystemCVS = Concurrent Versioning System

• IDE = Integrated Development IDE = Integrated Development EnvironmentEnvironment


AcknowledgementsAcknowledgements

• Dr. KothariDr. Kothari

• Greg Thede and David BrileyGreg Thede and David Briley


General Problem StatementGeneral Problem Statement

• Difficulty locating plotsDifficulty locating plots

• Multiple software solutionsMultiple software solutions

• Direct access to databaseDirect access to database

• Redundant hand-written formsRedundant hand-written forms


General Solution ApproachGeneral Solution Approach

• Simple interface to coordinate all Simple interface to coordinate all operationsoperations

• Automated form population & printingAutomated form population & printing

• Reminders programReminders program

• Queries – Allow users to easily search Queries – Allow users to easily search the entire databasethe entire database


Operating EnvironmentOperating Environment

• Windows XP operating systemWindows XP operating system

• Small office environmentSmall office environment

• A few usersA few users

• Sporadic interaction with systemSporadic interaction with system


Intended Uses & UsersIntended Uses & Users

• Users: A few select Boone employeesUsers: A few select Boone employees

• Uses:Uses:– Manage operational data for cemeteryManage operational data for cemetery– Provide support for searching cemetery Provide support for searching cemetery

recordsrecords– Print summary reportsPrint summary reports


AssumptionsAssumptions

• The software will not communicate with any other systemsThe software will not communicate with any other systems

• The database will always fit on a single local hard diskThe database will always fit on a single local hard disk

• The number of burial records will not exceed 100,000The number of burial records will not exceed 100,000

• Only one instance of the program will be run at one timeOnly one instance of the program will be run at one time

• The workstation will have a printer to print the formsThe workstation will have a printer to print the forms


LimitationsLimitations

• Software must work on existing workstation.Software must work on existing workstation.

• Software deliverable must be of appropriate size Software deliverable must be of appropriate size and format to be distributed on one CD.and format to be distributed on one CD.

• Software must work in isolation from external Software must work in isolation from external actors.actors.

• The product must not prohibit the normal The product must not prohibit the normal operation of other systems on the workstation.operation of other systems on the workstation.

• The forms to be printed must operate in a The forms to be printed must operate in a standard format accepted by most printers.standard format accepted by most printers.


DeliverableDeliverable

• Software packageSoftware package

• CD distributionCD distribution

• Documentation including tutorials, Documentation including tutorials, screenshots and referencesscreenshots and references


Project ActivitiesProject Activities


Present Accomplishments Present Accomplishments

• Decided on platformDecided on platform

• Defined scope and requirementsDefined scope and requirements

• Developed loose designDeveloped loose design

• Set up development Set up development environmentenvironment


Approaches ConsideredApproaches Considered

• Java - portable, more difficult to build Java - portable, more difficult to build GUIGUI

• Visual Basic - simple to build GUIVisual Basic - simple to build GUI

• C# - more comprehensive than VBC# - more comprehensive than VB


Project Definition ActivitiesProject Definition Activities

• Meetings with Boone personnelMeetings with Boone personnel

• Requirements definitionRequirements definition

• Use-case developmentUse-case development


Research ActivitiesResearch Activities

• Mapping software integrationMapping software integration

• Automatic business form printingAutomatic business form printing

• Software testing frameworks Software testing frameworks exploredexplored

• Software repository configurationSoftware repository configuration


Design ActivitiesDesign Activities

• Domain modelingDomain modeling

• Database organizationDatabase organization

• Software object definitionsSoftware object definitions


Implementation ActivitiesImplementation Activities

• Set up source code repositorySet up source code repository

• Started implementing a single use-Started implementing a single use-case scenario (Burial Plot Sale)case scenario (Burial Plot Sale)


Testing and its ResultsTesting and its Results

• No completed code modules so no No completed code modules so no testing thus fartesting thus far

• Testing software researched, Testing software researched, tentatively decided on NUnit test tentatively decided on NUnit test frameworkframework


Resources and SchedulesResources and Schedules


Personal EffortsPersonal Efforts

Prob Def

Tech Cons.

End Prod.

Implem TestingProd Doc

Demo Doc. Total

Adam Lorensen 3 9 30 28 38 16 7 30 161Andy Mueller 5 12 29 20 36 16 7 26 151Roderic Henry 2 8 30 26 36 16 7 26 151Joseph Heiniger 3 10 25 26 42 20 7 35 168Totals 13 39 114 100 152 68 28 117 631

Hours broken down by task


Other Resource EffortsOther Resource Efforts

EstimatedEstimated ActualActual DifferenceDifferencePosterPoster $60.00$60.00 $73.00$73.00 $13.00$13.00

PrintingPrinting $40.00$40.00 $45.00$45.00 $5.00$5.00

LaminationLamination $15.00$15.00 $20.00$20.00 $5.00$5.00

Misc.Misc. $5.00$5.00 $8.00$8.00 $3.00$3.00

FuelFuel $20.00$20.00 $25.00$25.00 $5.00$5.00

Documentation Documentation Binding & PrintingBinding & Printing

$0.00$0.00 $9.00$9.00 $9.00$9.00

TotalTotal $140.00$140.00 $187.00$187.00


Total Financial Total Financial RequirementsRequirements

CostCostPosterPoster $70.00$70.00

FuelFuel $25.00$25.00

Documentation Binding & PrintingDocumentation Binding & Printing $9.00$9.00

Work @ $10/hrWork @ $10/hrAdam LorensenAdam Lorensen $1610.00$1610.00

Andrew MuellerAndrew Mueller $1510.00$1510.00

Joe HeinigerJoe Heiniger $1680.00$1680.00

Roderic HenryRoderic Henry $1510.00$1510.00

Total w/o LaborTotal w/o Labor $140.00$140.00

TotalTotal $6450.00$6450.00


Tasks ScheduleTasks Schedule


Deliverable ScheduleDeliverable Schedule


Closing MaterialClosing Material


Project EvaluationProject Evaluation

• Scheduling and milestonesScheduling and milestones

• Personal effort requirementsPersonal effort requirements

• Financial requirementsFinancial requirements


• Project planProject plan

• Project posterProject poster

• Design documentDesign document

• ScreenshotsScreenshots

MilestonesMilestones

• Working prototypeWorking prototype

• End product & user End product & user documentationdocumentation

• Final reportFinal report


CommercializationCommercialization

• Operations of cemetery are not Operations of cemetery are not standardstandard

• Software design customized to the Software design customized to the client’s needsclient’s needs

• No plans to commercialize No plans to commercialize


Recommendations for Future Recommendations for Future WorkWork

• E-mail notifications for payment E-mail notifications for payment remindersreminders

• Automated e-mail billingAutomated e-mail billing

• Additional payment optionsAdditional payment options

• More options for client to customize More options for client to customize softwaresoftware


Lessons Learned: What went Lessons Learned: What went wellwell

• Repository creationRepository creation

• Development Environment setupDevelopment Environment setup

• Client’s availabilityClient’s availability


Lessons Learned: What did not go Lessons Learned: What did not go wellwell

• Integrating mapping software Integrating mapping software

• Existing records have no standard Existing records have no standard data formatdata format


Lessons Learned:Lessons Learned:Technical knowledge gainedTechnical knowledge gained

• C# programming languageC# programming language

• Subversion (SVN)Subversion (SVN)

• Business format printingBusiness format printing

• Software engineering processesSoftware engineering processes

• Product integrationProduct integration


Lessons Learned:Lessons Learned:Non-technical knowledge Non-technical knowledge

gainedgained

• Project managementProject management

• Communicating with non-technical Communicating with non-technical clientsclients

• Working with other teams Working with other teams


Lessons Learned:Lessons Learned:What would be done differentlyWhat would be done differently

• Researched mapping product earlierResearched mapping product earlier

• Started development earlierStarted development earlier


Risks and Risk ManagementRisks and Risk Management

• Loss of team memberLoss of team member

• Proposed IDEProposed IDE

• Proposed solutionProposed solution

• No anticipated risks were encounteredNo anticipated risks were encountered

• Unanticipated risk:Unanticipated risk:– Software integration with mapping softwareSoftware integration with mapping software

• No changes to risk managementNo changes to risk management


Closing Summary: ProblemClosing Summary: Problem

• Information in database not easy to Information in database not easy to retrieveretrieve

• Multiple (unnecessary) data entriesMultiple (unnecessary) data entries

• Needed a way to be reminded when Needed a way to be reminded when payments are duepayments are due


Closing Summary: ApproachClosing Summary: Approach

• Software solutionSoftware solution– Simple GUI interfaceSimple GUI interface– Single data entrySingle data entry– Easy to query databaseEasy to query database

• C# + Microsoft AccessC# + Microsoft Access

• Visual Studio .NETVisual Studio .NET


Closing Summary: Resultant Closing Summary: Resultant SolutionSolution

• Simple, easy-to-use software Simple, easy-to-use software applicationapplication

• Prints required formsPrints required forms

• Reminders featureReminders feature

• Summary reportsSummary reports


QuestionsQuestions


Thank YouThank You

may05-36: boone cemetery management software boone cemetery management software may05-36 greg thede,...

Documents