140 likes | 241 Views
The Collaborative Imaging Grid (CIG). Edward Marsh, Kurtis Heimerl, Andrew Urhausen, Paul Javid, Aneesa Awaludin, Austin Cargol. What is CIG?. Enables users to generate, aggregate, and disseminate about images. Images are coupled with metadata.
E N D
The Collaborative Imaging Grid(CIG) Edward Marsh, Kurtis Heimerl, Andrew Urhausen, Paul Javid, Aneesa Awaludin, Austin Cargol
What is CIG? • Enables users to generate, aggregate, and disseminate about images. • Images are coupled with metadata. • Goal : accumulate individual pieces of knowledge about different images and share them. • Analogy : Online Wiki communities • Research Agenda Examples : • Informal : Students collecting previous CSE 451 tests. • Formal : Cancer researchers comparing lung images that are cancerous.
Customers expectations • Who are our customers? EVERYBODY!! • Anyone who wants to easily view, edit, find and group images, • Anyone who wants to gather useful information about images. • Will be able to use the system quickly with little prior technical knowledge of the system.
Design Considerations • Intuitive GUI • Most used features will be accessible for a first time user. • Utilize representational icons and color coordinated task spaces. • System latency • User spends a majority of his time interacting with images, rather than waiting for system response.
Product Features • Basic features : • Add images / metadata • Edit metadata • Search images • Group images • Multiple images upload • Export text • Extra : • Username / password
Product Design • GNU Tomcat webserver • Build on Sun’s Java programming language • Spring Framework • Simplify the development of web application • Velocity • Generate XHTML output
Interfaces • Crucial interfaces : • Between controllers and velocity • HTTP form submissions • Smaller interfaces : • Metadata output • XML file server • XML initialization files
Team Structure • Everyone helps develop: • 3 members : Backend / Server Programming and Design • 2 members : Graphical User Interface design and Integration • 1 member : Testing • 1 Program Manager • 1 Lead Architect
Milestone • Week 1 (Apr 17 – Apr 23) • Functionality of main and search pages • Week 2 (Apr 24 – Apr 30) • Functionality of upload page and display page • Multiple File Upload • Testing and documentation starts • Week 3 (May 1- May 7) • File system implemented and integrated with pages • Beta webpage design
Milestone • Week 4 (May 8 – May 14) • Beta release!! • Full interaction between server and web pages • Week 5 (May 15 – May 21) • Server and GUI finalized and completed • Export text • Week 6 (May 22 – May 28) • Documentation complete. • Week 7 (May 29 – June 4) • Final release!!
Risks and their mitigation paths • Performance • Understanding • Tools • Extensibility • Unforeseeable changes
Tests And Documentation • JUnit testing • Components: • All controllers • Main page controller • Search page controller • Display page controller • Upload page controller • Documentation : • Installation / Setup guide • User Guide / Extensibility • Quick and Dirty Guide