1 / 33

Collection Inventory Software

This project aims to develop a fully functional and user-friendly Collection Inventory Software that allows efficient collection management, easy data retrieval, and importing/exporting collection information.

ferma
Download Presentation

Collection Inventory Software

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

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

  4. Problem Statement • 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 • Personal systems are often time-consuming and limited in use

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

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

  7. Limitations • The work of Phase I will be used when possible • 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 • Software will only run on Java Runtime Environment 5.0

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

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

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

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

  12. Search Panel Attribute List Search Item Comparator

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

  14. CD Lookup Search Options Search Results CD Details

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

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

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

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

  19. Activities

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

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

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

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

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

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

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

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

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

  29. Lessons Learned • Phase I’s mistakes we plan not to repeat • Code had little documentation • We shall document the critical code to help future developers’ understanding • Code was unorganized • 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 • Resources and Schedule • Schedule • Personnel • Financial • Closure Materials • Lessons Learned • Risk Management • Project Overview • A collection management system • Usable by anyone and everyone • Project Activities • Present Accomplishments • Approaches Considered • Activities

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

More Related