Design_teamB_Fall08 - Design Document Version 1.0 CS 307 Team B October 8 2008 Yahoo Project Code Name MirrorWeave Charles Durham Immanuel

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Charles Durham, Immanuel Alexander, Leo Tanady, Andrew Prasetyo Jo, AJ Arora Design Document: Version 1.0 Yahoo! Project Code Name: MirrorWeave CS 307 Team B October 8, 2008 [email protected] Introduction Document Scope The purpose of this document is to provide a design overview of features of the Yahoo data quality widget project. Its coverage ranges from the high level deployment view to descriptions of the functions necessary to be describing at this point in the design process. This is however not a complete description of the low level details as this was not our intention, we instead feature the most important functions as to not distract the reader from the main design aspects of this product. This document first features a quintet of diagrams which are all very related to each other but vary in depth. These diagrams start with the high level deployment view and each proceeding diagram is a zoomed in version of the previous. This quintet of diagrams are the high level deployment view, the high level component view, the detailed component view, the logical view of the “Widget GUI” component, and the logical view of the “Data Access” component. The next diagram is a UI flow diagram followed by the process view and finally the “Use Case” diagram with some potentially important action/response use cases. Intended audience The intended audience for this document is the Yahoo SDS Data Quality team, including any sub team(s) directly related to the Yahoo SDS Data Quality team. Project Overview The main goal of the project is in building a graphical user interface that interacts with the data quality database to obtain data and provide graphical representation of the data. In addition, the project will allow the user to provide feedback about a bug or anomaly. Access to the data quality database is not restricted since it is in the Yahoo internal network, so there is not much concern about how to access the database and issues in security. For additional information see the previous requirements document. High ­ Level Design Goals and Guidelines The main goal of the design is to have a Yahoo widget with a streamlined GUI design. We will feature two tabs, with the first tab containing property views and the second tab containing issues regarding the individual properties. We have two tabs in order to properly separate the different requirements of our
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
project in order to increase the user’s productivity in his/her interaction with our product. The property view will be meant for analysis of data and the data issues view will be fulfilling the user’s desire to inspect and manipulate reported issues in regards to their requested properties and regions. Architectural Strategies One of the design decisions includes providing a user friendly interface by using tabs to separate different components, data and issues. The first thing the widget does is to obtain the user login information and then connect to the database for authorization. We decided to provide a separate
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 02/23/2012 for the course CS 307 taught by Professor Staff during the Summer '08 term at Purdue University-West Lafayette.

Page1 / 14

Design_teamB_Fall08 - Design Document Version 1.0 CS 307 Team B October 8 2008 Yahoo Project Code Name MirrorWeave Charles Durham Immanuel

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online