160 likes | 173 Views
This project report provides a review of the UmbrellaDB v0.5 project, including its goals, architecture, management, performance, reliability, evolution, and user manual. It also includes examples of the user interface and steps to start a new project.
E N D
UmbrellaDB v0.5Project Report #3 Integrated Heterogeneous Data Source Access Eric Matson – MSE Kansas State University
Agenda • Review • Project Review • Project Evolution • Project Management & Control • User Manual • Demonstration • Summary and Questions
Review - Purpose • Query heterogeneous data sources using standard SQL statements • Achieve database integration and access at the query level • Allow the data to be “black box” whereas users don’t need to have understanding to source, architecture, or technical details
Review - Goals • Complete the Requirements of CIS895 • Successfully Navigate Software Engineering Process • Prove UmbrellaDB Concept • Prove Ability to Process UmbrellaDB Queries • Create easy to use Graphical User Interface (GUI)
Review – Architecture Relational Database Parser D a t a C o n n e c t o r s Object Database API Splitter TCP/IP Text File Router Umbrella GUI Unifier KB File Profile Data Server Data Sources Engine
Project Review - Management • Goals • Developed Prototype of UmbrellaDB • Prove Concept • Integrate Data • GUI is easy to use • Used SE Processes and Tools to Completion
Project Review - Performance • Key Performance Areas • DataServer Response Time • Although not completely optimized, works well • Efficiencies added in future versions • Data Transmission via Network • Tests Created to Measure Response Time Varying • Network: Local, LAN, WAN • File Type: Delimited, Formatted • Performed 180 Tests to Measure Response Time • Most Results Within Acceptable Limits • DataServer Time consistent • Network transmission times variable
Project Review - Reliability • Most Important Factors • Network Related Components of the System • Data Connectors • Router • DataServer • Issues • Socket Dropped Unexpectedly • Delays over the Internet based TCP/IP Connection • Resolutions • Requirement to Build More Error Catching/Handling into Network Related Components
Project Evolution • Software Development Process (COMET) • 5 Iterations of Prototypes (v0.1 – v0.5) • Positive Effects • Better Class Model • More Efficient Design • Negative Effects • Extra time to refine • “Escalating Commitment” in areas (GUI) • So much time investment, hard to start over
Project Management and Control • Technology and Tools • Tools worked well • Good Cost Factor ($0) • Open Source Tools Worked Well • Large Learning Curve for the Project Manager • Processes • Concurrent Object Modeling and Architectural Design METhod (COMET) • Hassan Gomaa - Author • Good for: • Prototyping with Quick, But Not Final Results • Generating Further Requirements and Modeling Ideas • Bad for: • Communication • Tracking “process paper work”
Project Management and Control • Methods • Unified Modeling Language (UML) De Facto Industry Standard • Much to learn • 80/20 Tool Approach • Object Constraint Language (OCL) • More Intuitive (for me, at least) Than Other Formalisms • Still Hard to Learn, On an Individual Basis • Time Analysis • Planned 565.00 hours • Used 504.75 hours • Schedule Changed Due to Factors Outside of the Project • Less Time Used not Necessarily Positive
User Manual - Examples The window you will see when UmbrellaDB Workbench is started. On this window there is: 1 ) Menu 2) Toolbar
User Manual - Examples • To start a new Project: • 1) Click the File Menu • 2) Click Project • 3) A dialog will appear • 4) Enter a Project Name • 5) Enter a Project Description • 6) Enter the Project Author • 7) Click the OK button
User Manual - Examples The Project Tree will give a visual representation of all Connections, Data Sources, Data Fields and Queries that are part of the project’s virtual database schema. The Meta Data area will show metadata describing items in the project. The Status Bar will show what project is currently loaded and where it physically exists. The Query Data area is where data will appear when a query is successfully executed.
User Manual - Examples • A screen shot of the system in use after a simple query has been executed. This query returns: • First name • Last Name • Title • Salary • Program
Summary • Complete through Version 0.5 • Accomplished All Personal Project Goals • Next Steps • Questions • Feedback • Signoff • Print/Send to Binder