360 likes | 494 Views
VDK-RIT InserterVision Report System. Presented By Adam Beck Greg Dicheck Kassidy Gerber Mike Young. Agenda. Project Sponsor Problem Our Solution 1 st Quarter 2 nd Quarter Design and Implementation Reflection Future Plans Demo. Our Team. Notables. Project Sponsor - Videk.
E N D
VDK-RITInserterVision Report System Presented By Adam Beck Greg Dicheck Kassidy Gerber Mike Young
Agenda • Project Sponsor • Problem • Our Solution • 1st Quarter • 2nd Quarter • Design and Implementation • Reflection • Future Plans • Demo
Project Sponsor - Videk • 15-year track record of innovation in the field of process control • Industry leader in factory automation • Real-time vision inspection solutions • OCR software with the industry’s fastest read rate and processing power • InserterVision: Single all-in-one solution for input scanning for machine control
Videk’s InserterVisionTM • Cameras scan mail jobs for data integrity • Reads names and addresses for verification • Diverts misprinted or incorrectly processed mail pieces • High-speed solution reduces costly and error-prone manual checking • Absolute quality assurance and reduced document liability
Problem • Anticipating customer needs • Increased traceability • Storage of mailing job results • Proposed add-on to InserterVision • Increase marketability of InserterVision • Generate revenue from sales of training • Videk approached RIT for a Senior Project
Our Solution • InserterVision Report System (IVRS) • Low-cost DBMS and reporting solution • Client-server architecture • Display, format, and print reports • Access over a company intranet • Uses data collected from the Videk camera system • Meant to be deployed with InserterVision • Implemented as a functional proof-of-concept
Project Deliverables • Functional program including source • System Documentation • User Manual • Installation Manual • Quick Start Card • Project Documentation • Project Vision & Scope • Software Requirements Specification • Software Design Specification
Project Process • Responsibilities assigned by task • Leveraged individual strengths of team members • Revisited task list weekly • All documents reviewed by the team • Formal Inspections • Inspection Checklists • Elicitation Sessions • Meetings between customer contact and the team • Email for clarifications
Project Process (2) • Coding Standards • Set forth in the Configuration Management Plan • Defect Tracking • Defects stored in the Issue Tracker spreadsheet • Quality Manager maintained the Issue Tracker • Test Manager closed the resolved defects
Project Process (3) • Change Control • All changes formally approved by the team according to the Change Control Process • Traceability • Requirements traced through the entire project using a Requirements Traceability Matrix
Project Process Tools • Task Plan • Used to assign and schedule team tasks • Issue Tracker • Used to file and track system defects and changes • Requirements Traceability Matrix • Used to trace project requirements through the project
1st Quarter Deliverables • Project Vision & Scope • Software Requirements Specification • Risk Management Plan • Configuration Management Plan • Software Quality Plan • Draft Acceptance Test Plan
1st Quarter Decisions • Authentication • Levels of access for different Users • System Administrator (All functionality) • Manager (Import/ Export/ Delete Data Sets) • User (View/ Save Reports) • Different Permissions given • Permission to create/ edit/ delete Templates • Adaptable to include more permission types
1st Quarter Decisions (2) • Configurable system logging • Administrator sets criteria • System records only log statements that match established criteria • Editors for customizing • Template Editors • User Account Editor
1st Quarter Decisions (3) • Templates for End-User Extensibility • Standard: Pre-defined, selectable filters • Advanced: Open-ended SQL filtering • Specialty: Missing Sequence, Combined, and Duplicates • Template Filters • Standard for data filtering on a specific field • Special (Count, Sum, Average)
2nd Quarter Deliverables • Software Design Specification • Alpha, Beta, and Gamma code builds • Project Documentation • User Manual • Installation Manual • Quick Start Card • Final Acceptance Test Plan • Senior Project Poster • Technical Paper
Implementation Decisions • Selected object-oriented PHP4 technology • Advantages • Familiarity with object-oriented (OO) languages • Inheritance • Modular design • PHP moving toward OO practices • Free development tools
Implementation Decisions (2) • Disadvantages • Lack of strong variable typing goes against some OO principles • More difficult error handling • No function overloading
IVRS Major Features • Store Data Sets for completed mailing jobs • Display selected Data Sets • Format data display according to templates • Sort display according to multiple sort keys • Printer-friendly reports
IVRS Major Features (2) • Accessible from web browsers • Controlled user access • Multiple levels of access • Editors for creating and modifying templates
IVRS Design Legend
IVRS Implementation • Implemented in three incremental builds • Alpha Build • User to select and display a single data set • Beta Build • Added ability for user to create, modify, and delete report templates • Fixed defects found in Alpha Build
IVRS Implementation (2) • Gamma Build • Implemented user permissions • Added all administrator functionality including system logging, user account creation and manipulation, and company header creation and manipulation • Fixed defects in the report template creation and modification • Added user help pages • Commented code to generate PHP Docs automatically
IVRS Quality • Unit Testing done informally by the developers • Integration Testing done informally by the Development Manager • System Tests performed by all developers and led by the Test Manager
Reflections - Positive • Team adapted well to changes in requirements and scheduling • Team leveraged abilities to complete tasks efficiently • Team created a well-documented system that will help in transition to Videk
Reflections - Negative • Document overhead • Scheduling conflicts • Less formal process in the 2nd Quarter • Not enough time to complete the Import/Export Data Sets feature
Future Plans • The IVRS system will be deployed with InserterVision • Maintenance and any future enhancements will be provided by Videk
Acknowledgements • Videk and Chris Haidvogel • Dr. Stephanie Ludi • Cohber