1. Collection Inventory Software May06-04 (CIST) Eric Anderson Adam Kovar Dustin Lunde Matt Moeller Brian Steger February 28 th, 2006 Advisors Dr. J. Lamont P.E. Professor R.E. Patterson III Client Dr. D. Stuart

2. Presentation Overview Project Overview Project Overview Definitions Definitions Problem Statement Problem Statement Intended Users/Uses Intended Users/Uses Assumptions Assumptions Limitations Limitations Expected End Product Expected End Product Project Activities Project Activities Resources and Schedule Resources and Schedule Closure Materials Closure Materials

3. Definitions Attribute: A column in the database Attribute: A column in the database FreeDB: Free online database for CD information FreeDB: Free online database for CD information HSQLDB: Hyperthreaded Structured Query Language Database HSQLDB: Hyperthreaded Structured Query Language Database Item: A row in the database Item: A row in the database Phase I: Dec04-01 senior design team Phase I: Dec04-01 senior design team Phase II: May06-04 senior design team Phase II: May06-04 senior design team

4. Problem Statement People enjoy collecting items such as music, movies, and books People enjoy collecting items such as music, movies, and books There is a desire to organize and inventory what is wanted and what is already owned There is a desire to organize and inventory what is wanted and what is already owned Personal systems are often time-consuming and limited in use Personal systems are often time-consuming and limited in use

5. Intended Users Professional and amateur collectors Professional and amateur collectors Novice to advanced computer users Novice to advanced computer users Intended Uses Efficient collection management Efficient collection management Easy data retrieval through searching and sorting Easy data retrieval through searching and sorting Importing/exporting collection information Importing/exporting collection information

6. Assumptions The work and source code from Phase I will be made available The work and source code from Phase I will be made available Windows, Linux, and Mac platforms to be supported Windows, Linux, and Mac platforms to be supported Multiple collections will be available on one system Multiple collections will be available on one system Internet access will be available for the use of FreeDB Internet access will be available for the use of FreeDB

7. Limitations The work of Phase I will be used when possible The work of Phase I will be used when possible The level of user expertise will range from novice to advanced The level of user expertise will range from novice to advanced Collection size will be limited to available disk space on the user’s pc Collection size will be limited to available disk space on the user’s pc Software will only run on Java Runtime Environment 5.0 Software will only run on Java Runtime Environment 5.0

8. Expected End Product Fully functional and thoroughly tested Collection Inventory Software Fully functional and thoroughly tested Collection Inventory Software Incorporated user manual and help documentation Incorporated user manual and help documentation

9. Presentation Overview Project Overview Project Overview Project Activities Project Activities Present Accomplishments Present Accomplishments Approaches Considered Approaches Considered Activities Activities Resources and Schedule Resources and Schedule Closure Materials Closure Materials

10. Present Accomplishments (1/2) Review of the existing code Review of the existing code Focused the requirements Focused the requirements Design review and refinement Design review and refinement Finalized development platform Finalized development platform Primary functionality Primary functionality Finalized Finalized Implemented Implemented User manual developed User manual developed

11. Present Accomplishments (2/2) Interface redesign Interface redesign Detail Panel Detail Panel Search performed on main screen Search performed on main screen Working implementation of desired features Working implementation of desired features CD lookup CD lookup Dynamic importing/exporting Dynamic importing/exporting

12. Search Panel Attribute ListSearch Item Comparator

13. Detail Panel Action Buttons Collection Statistics Item Visibility Item Details

14. CD Lookup Search Options Search Results CD Details

15. Importer Import File File Structure Attributes & Separators Attribute Creator

16. Approaches Considered – Development Platform Approach 1 – Java Approach 1 – Java Pros: Pros: Multi-system compatibility Multi-system compatibility Familiarity Familiarity Cons: Cons: More difficult GUI development More difficult GUI development Approach 2 – C# Approach 2 – C# Pros: Pros: Easy GUI development Easy GUI development Cons: Cons: Bound to Windows Bound to Windows Less robust Less robust Selected – Java Selected – Java To fulfill requirement of multi-system support To fulfill requirement of multi-system support

17. Approach 1 – Editable table Approach 1 – Editable table Pros: Pros: Ease of use and understanding Ease of use and understanding Cons: Cons: Erratic behavior when sorting Erratic behavior when sorting Too many columns to display Too many columns to display Approaches Considered – User Input Approach 2 – Detail Panel Approach 2 – Detail Panel Pros: Pros: Clean display of all attributes Clean display of all attributes Consistent location for data entry Consistent location for data entry Cons: Cons: Increased user navigation Increased user navigation Selected – Detail Panel Selected – Detail Panel Provides the user with a consistent and easy method of data input Provides the user with a consistent and easy method of data input

18. Approach 1 – Main window Approach 1 – Main window Pros: Pros: Ease of use Ease of use Cons: Cons: Developmental difficulties Developmental difficulties Approaches Considered – Search Approach 2 – Alternate window Approach 2 – Alternate window Pros: Pros: Distinct search results Distinct search results Cons: Cons: Increased user navigation Increased user navigation Selected – Main window Selected – Main window Provides an easily understood search mechanism Provides an easily understood search mechanism

19. Activities Name of Activity Completed Project definition 100% Research/Phase I code review 100% Project design 100% Implementation85% Testing50% Other (user manual, documentation, etc.) 70%

20. Presentation Overview Project Overview Project Overview Project Activities Project Activities Resources and Schedule Resources and Schedule Estimated Resources Estimated Resources Schedule Schedule Personnel Personnel Financial Financial Closure Materials Closure Materials

21. Estimated Resources (1/4) Project Schedule - Overview Project Schedule - Overview Completed activities (green): Definition, Technology Considerations and Selection, Design Completed activities (green): Definition, Technology Considerations and Selection, Design Current activities (blue): Product Implementation, Testing, Documentation, Reporting Current activities (blue): Product Implementation, Testing, Documentation, Reporting Remaining activities (red): Demonstration Remaining activities (red): Demonstration

22. Estimated Resources (2/4) Project Schedule - Detailed Project Schedule - Detailed

23. Estimated Resources (3/4) Personnel - Hours Personnel - Hours

24. Estimated Resources (4/4) Financial Financial Expenses: Expenses: Report binding and printing Report binding and printing Poster board and lamination Poster board and lamination Labor @ $12.00/hr. Labor @ $12.00/hr. Free Resources: Free Resources: Java development Java development Computer labs/personal computers Computer labs/personal computers

25. Presentation Overview Project Overview Project Overview Project Activities Project Activities Resources and Schedule Resources and Schedule Closure Materials Closure Materials Evaluation Evaluation Commercialization Commercialization Additional Work Additional Work Lessoned Learned Lessoned Learned Risk Management Risk Management

26. Project Evaluation Testing program functionality Testing program functionality Test cases Test cases Beta testing Beta testing What lessons were learned What lessons were learned Where did we succeed? Where did we succeed? Where could we have done better? Where could we have done better?

27. Commercialization Decided by Phase I and Phase II (separately) to be offered as freeware Decided by Phase I and Phase II (separately) to be offered as freeware Hypothetical commercialization: Hypothetical commercialization: Cost of Production (including labor): $10,000 Cost of Production (including labor): $10,000 Maintenance (including labor): less than $2000 per year Maintenance (including labor): less than $2000 per year Cost of Product: $19.99 Cost of Product: $19.99 Potential Market: Collectors with computer access Potential Market: Collectors with computer access

28. Additional Work Product redesign and additions: Base level database structure Base level database structure Port to a personal digital assistant (PDA) Port to a personal digital assistant (PDA) Enhanced importer and exporter for xml and html formats Enhanced importer and exporter for xml and html formats Enhanced printing functionality Enhanced printing functionality

29. Lessons Learned Phase I’s mistakes we plan not to repeat Phase I’s mistakes we plan not to repeat Code had little documentation Code had little documentation We shall document the critical code to help future developers’ understanding We shall document the critical code to help future developers’ understanding Code was unorganized Code was unorganized We shall organize the code into correct packages and move methods into separate classes to allow for robustness We shall organize the code into correct packages and move methods into separate classes to allow for robustness

30. Risk Management (1/2) Risk: Loss of team member Solution: The remaining work will be divided among the remaining members Risk: Loss of pertinent data Solution: All data related to the project (source code, documentation, manuals) shall be stored in a CVS repository The repository will track all changes and different versions that the software and documents go though

31. Risk Management (2/2) Risk: The client may not be satisfied with the end product Solution: Multiple client/advisor feedback opportunities Software prototypes and quality documentation made available to all stakeholders

32. Conclusion Project Overview Project Overview A collection management system A collection management system Usable by anyone and everyone Usable by anyone and everyone Project Activities Project Activities Present Accomplishments Present Accomplishments Approaches Considered Approaches Considered Activities Activities Resources and Schedule Resources and Schedule Schedule Schedule Personnel Personnel Financial Financial Closure Materials Closure Materials Lessons Learned Lessons Learned Risk Management Risk Management

33. Questions? Application available at: http://seniord.ece.iastate.edu/may0604/