23 November 1999Sticky Technology for Augmented Reality Systems 1 2 15-413 Brian Parkison Workflow Team STARS Project Carnegie Mellon University 23 November.

Slides:



Advertisements
Similar presentations
Message Passing Vs Distributed Objects
Advertisements

1 Object-Oriented Software Development Project Aaron Christopher.
Team: Maya Zalcberg Diana Attar Levona Hershtik Academic advisor: Prof. Ehud Gudes ADD Presentation.
15 Chapter 15 Web Database Development Database Systems: Design, Implementation, and Management, Fifth Edition, Rob and Coronel.
The Architecture of Transaction Processing Systems
0-1 Team ?? Status Report (1 of 3) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team 1: Auraria.
Distributed Systems: Client/Server Computing
Client/Server Architecture
Client/Server Computing. Information processing is distributed among several workstations and servers on a network, with each function being assigned.
8/19/20151 Securing a Database Based on notes by Fei Li and Hong Li.
Copyright © 2007, SAS Institute Inc. All rights reserved. SAS Activity-Based Management Survey Kit (ASK): User Management & Security.
Web Based Applications
Selected Topics in Software Computing Distributed Software Development CVSQL Final Project Presentation.
Common Object Request Broker Architecture (CORBA) CS-328.
Bryce Rodgers Kent Warner Matt Heckman.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
Lecture On Database Analysis and Design By- Jesmin Akhter Lecturer, IIT, Jahangirnagar University.
Desktop Integration Rhidian Bramley PACS & Teleradiology Group Meeting November 2005.
Team 1 Jesus Weibo Mina Yunming. Client’s Needs  Short term, medium term, long term plans  Simulation of energy system to provide affordable future.
Tutorial 10 Adding Spry Elements and Database Functionality Dreamweaver CS3 Tutorial 101.
1 Chapter Client-Server Interaction. 2 Functionality  Transport layer and layers below  Basic communication  Reliability  Application layer.
CAA/CFA Review | Andrea Laruelo | ESTEC | May CFA Development Status CAA/CFA Review ESTEC, May 19 th 2011 European Space AgencyAndrea Laruelo.
WaveMaker Visual AJAX Studio 4.0 Training Authentication.
Example  Software for a virtual library (borrowing books using the Internet) Internt terminal DB.
© Dennis Shasha, Philippe Bonnet – 2013 Communicating with the Outside.
SWE © Solomon Seifu ELABORATION. SWE © Solomon Seifu Lesson 11 Subsystem Design.
GEON meeting - May 22, 2006 GAMA 2.0 Features and Status Kurt Mueller SDSC.
Computer Emergency Notification System (CENS)
1 Some initial Design suggestions… Getting started… where to begin? Find out whether your design architecture will work… as soon as possible. If you need.
CEN Advanced Software Engineering
DoG Ticket Trouble Ticket Web App By: David, Gabe, Trevor Group 4.
Team # 2 Members: Sowmya Krishnaswamy Hakan Terzioglu Manu Mehan Jerome Tunaya.
Information Management System “Good Practice Module" Information Management System “Good Practice Module" The Good Practice / Success Stories module is.
INTRODUCTION TO DBS Database: a collection of data describing the activities of one or more related organizations DBMS: software designed to assist in.
FTP Server API Implementing the FTP Server Registering FTP Command Callbacks Data and Control Port Close Callbacks Other Server Calls.
Virtual Real-time 3D Object Sharing for Supporting Distance Education and Training Hiroko Suzuki Faculty of Computer and Information Science, Hosei University,
JSP Server Integrated with Oracle8i Project2, CMSC691X Summer02 Ching-li Peng Ying Zhang.
Management System For Graduate Students Projects Day Presentation – June 2011.
FriendFinder Location-aware social networking on mobile phones.
Handling Semantic Data for Software Projects Data Management CSE G674 – SW Engineering Project.
Desktop Integration Rhidian Bramley PACS & Teleradiology Group Meeting November 2005.
The basics of knowing the difference CLIENT VS. SERVER.
Configuring and Deploying Web Applications Lesson 7.
Information Management System “Project Module" Information Management System “Project Module" The Project module is an integrated part of System. The back.
Biosolid Design Spec Brief April 21, Overview Design Overview Proposed System Architecture User Interface Subsystem Interfaces Package & File Organization.
Securing Web Applications Lesson 4B / Slide 1 of 34 J2EE Web Components Pre-assessment Questions 1. Identify the correct return type returned by the doStartTag()
Requirements Analysis Review Modeling Team Matt Weyant 26 Oct 1999.
Lab 301 Populating Template Data from a Third Party Data Source Justin Pava, Software Release Manager Andrew Schoonmaker, Software QA Engineer.
23 November 1999Sticky Technology for Augmented Reality Systems Tracey Wortham Inspection Team STARS Project Carnegie Mellon University 23 November.
Analysis Review of Workflow Subsystem Kaushik Merchant And The Workflow Team.
11 November 1999Sticky Technology for Augmented Reality Systems Robert Kurian Inspection Team STARS Project Carnegie Mellon University 11 November.
23 November 1999Sticky Technology for Augmented Reality Systems Rachel I. Goldstein Repair Team STARS Project Carnegie Mellon University 23.
2Operating Systems  Program that runs on a computer  Manages hardware resources  Allows for execution of programs  Acts as an intermediary between.
11 November 1999Sticky Technology for Augmented Reality Systems Daniel Heller Architecture Team STARS Project Carnegie Mellon University 11.
Architecture Review 10/11/2004
JDBC Database Management Database connectivity
File System Implementation
Software Architecture and Quality BY
Repair Requirements Analysis Review
Data Management Agenda
Boundary Conditions Samuel Chong Repair Team STARS Project
#01 Client/Server Computing
Hardware/Software Allocation
Object Design Michael Fortson Augmented Reality/UI Team STARS Project
Quality Center (QC) 11 Training Global IT QA Testing Team 2013
Introduction of Week 11 Return assignment 9-1 Collect assignment 10-1
Technical Integration Guide
Storing and Processing Sensor Networks Data in Public Clouds
#01 Client/Server Computing
Presentation transcript:

23 November 1999Sticky Technology for Augmented Reality Systems Brian Parkison Workflow Team STARS Project Carnegie Mellon University 23 November 1999 Object Design Review

23 November 1999Sticky Technology for Augmented Reality Systems 2 submitDocument Scenario Jack, an IETM author in Montana, finishes his first draft and needs to submit it to the Authoring Database for review. (submitDocument()) The DBClient notices that this is the first time Jack has accessed the database, and asks him to login. (authenticateUser(), which is not a public method)

23 November 1999Sticky Technology for Augmented Reality Systems 3 submitDocument (cont) After successful authentication, the DBClient initiates a call to the DBServer to carry out the submit request. (API undecided) Upon successful completion of the task, the ID of the newly submitted document is returned. Jack realizes this is the last thing he needs to do today, and logs out. (logout())

23 November 1999Sticky Technology for Augmented Reality Systems 4 DBClient NetworkClient 1 1 NetworkServer * 1 RMI DBServer 1 1 STARS DB 1 1 Authentication LotusServer Notification JDBC *1 Client MachineSTARS DB Server Object Model (Simplified)

23 November 1999Sticky Technology for Augmented Reality Systems 5 Notes on the Object Model Other subsystems should only interact with the DBClient. The DBServer creates threads for each connection from the NetworkServer. As a result, the authentication and notification subsystems will be thread-safe.

23 November 1999Sticky Technology for Augmented Reality Systems 6 Infamous Document It is an interface void addSubscriber(String username) String getDatatype() Collection getAuthorizedReaders() Collection getAuthorizedWriters() Collection getSubscribers() Collection getSearchableData()

23 November 1999Sticky Technology for Augmented Reality Systems 7 API int submitDocument(Document data) Document retrieveDocument(int docID, String datatype, boolean forReading) int updateDocument(int docID, Document data) Collection listDocuments(Collection criteria, Collection desiredFields)

23 November 1999Sticky Technology for Augmented Reality Systems 8 API (cont) void addSubscriber(String username, int DocID, String datatype) String getUsername() void logout() Javadoc:

23 November 1999Sticky Technology for Augmented Reality Systems 9 Hardware Requirements Client: PEDD, desktop – we’re not the bottleneck in hardware needs! Server: Dedicated STARS DB Server with GB of disk space. Client/Server: Any network connection, but the faster, the better.

23 November 1999Sticky Technology for Augmented Reality Systems 10 Software Requirements Client: JavaRMI Server: JavaRMI. Also, LotusNotes must be running for authentication and notification. The database subsystem also needs a database backend to store all of the data.

23 November 1999Sticky Technology for Augmented Reality Systems 11 Notes About the Database LotusNotes has a 254 character limit on field sizes when using JDBC. LotusNotes only supports JDBC 1.1. Workflow is currently looking at other DBMS’s to use as the backend.

23 November 1999Sticky Technology for Augmented Reality Systems 12 Database Fields The fields need to be specified to the Workflow team ahead of time. Workflow will be adding additional fields, mostly for internal management. These fields will be accessible by other subsystems.

23 November 1999Sticky Technology for Augmented Reality Systems 13 Added Fields previous_version current_writer serialized_data These field names cannot be used by other subsystems!

23 November 1999Sticky Technology for Augmented Reality Systems 14 Status of Subsystem Working on implementation Interface to front end is defined and ready to implement Back end server access to database is proceeding in earnest Authentication and Notification subsystem are somewhat lacking in code RMI is in the works

23 November 1999Sticky Technology for Augmented Reality Systems 15 Timeline Implementation Nov 23rdDec 5th Unit Testing Dec 1st Integration Testing Dec 9th We have not decided on the exact order of implementation for each subsystem. We’ll take whatever we can get.

23 November 1999Sticky Technology for Augmented Reality Systems 16 Open Issues Is RMI the best way to do the networking? What database will replace LotusNotes? How do we deal with dead network connections? How are we going to implement and test all of this in a timely manner?