Boundary Conditions Samuel Chong Repair Team STARS Project

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

Testing. Why bother? Rigorous testing is essential! It determines whether or not developers have met requirements set by the client at the very start.
The Petroleum Registry of Alberta The Petroleum Registry of Alberta Energizing the flow of information Registry Information Session January 24, 2006.
Use Case & Use Case Diagram
Database Management System MIS 520 – Database Theory Fall 2001 (Day) Lecture 13.
1 Postdelivery Maintenance Xiaojun Qi. 2 Why Postdelivery Maintenance Is Necessary Corrective maintenance: To correct residual faults –Analysis, design,
Chapter 8 : Transaction Management. u Function and importance of transactions. u Properties of transactions. u Concurrency Control – Meaning of serializability.
Slide 1 FAA’s Special Technical Audit of Boeing and the Audit Resolution Plan.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Transaction Management WXES 2103 Database. Content What is transaction Transaction properties Transaction management with SQL Transaction log DBMS Transaction.
Agenda  Overview  Configuring the database for basic Backup and Recovery  Backing up your database  Restore and Recovery Operations  Managing your.
Workflow Framework There are many open-source workflow frameworks available such as: –OS Workflow -
Business Intelligence: Data and Text Management Instructor: Bajuna Salehe Web:
THE SYSTEMS LIFE CYCLE ANALYSE DESIGN IMPLEMENT MAINTENANCE IDENTIFY/INVESTIGATE.
Microsoft SharePoint 2010 Upgrade Preview FSU SharePoint Users Group Presents: Thursday, December 1 st, 2011.
Motivation. Part of Deutsche Telekom project:
Administering Windows 7 Lesson 11. Objectives Troubleshoot Windows 7 Use remote access technologies Troubleshoot installation and startup issues Understand.
SSIS Over DTS Sagayaraj Putti (139460). 5 September What is DTS?  Data Transformation Services (DTS)  DTS is a set of objects and utilities that.
ONLINE TECHNICAL REPORT SYSTEM Team Crash Course Ryan Ashe, Eileen Balci, James Kirk, Taylor Paschal.
Role of Account Management at ERCOT Market Participant Identity Management Overview (MPIM)
Systems Development Lifecycle Testing and Documentation.
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
Mark A. Magumba Storage Management. What is storage An electronic place where computer may store data and instructions for retrieval The objective of.
Document Imaging and Workflow. An electronic file cabinet Rather than maintain paper documents, Feith allows for electronic files to be stored and sorted.
Compatibility and Interoperability Requirements
Diagnostic Pathfinder for Instructors. Diagnostic Pathfinder Local File vs. Database Normal operations Expert operations Admin operations.
Databases.
1 Introduction to Software Testing. Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Chapter 1 2.
Topics Covered: Software testing Software testing Levels of testing Levels of testing  Unit testing Unit testing Unit testing  Integration testing Integration.
MTF - Travellers 28/2/2001 S. Mallon + P. Martel EDMS Doc Id Contents Problem and scope Timing of MTF usage Definition of a standard MTF Creation.
1 Figure 10-4: Intrusion Detection Systems (IDSs) Actions  Alarms  Interactive analysis Manual event inspection of raw log file Pattern retrieval 
Chapter 15: Reliability and Security in Database Servers Neyha Amar CS 157B May 6, 2008.
Backing Up and Restoring Databases by Using the SQL Server 2000.
Business Continuity Planning for OPEN OPEN Development Conference September 18, 2008 Ravi Rajaram IT Development Manager.
Alert types EUM Alerts (aka Event Based Alerts)  BPM Transaction Alerts  RUM Application Alerts  RUM Event Alerts  RUM Transaction Alerts CI Status.
GCSE ICT 3 rd Edition The system life cycle 18 The system life cycle is a series of stages that are worked through during the development of a new information.
Testing Overview Software Reliability Techniques Testing Concepts CEN 4010 Class 24 – 11/17.
Requirements Analysis Review Modeling Team Matt Weyant 26 Oct 1999.
SDJ INFOSOFT PVT. LTD. 2 BROWSERBROWSER JSP JavaBean DB Req Res Application Layer Enterprise server/Data Sources.
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.
Troubleshooting Windows Vista Lesson 11. Skills Matrix Technology SkillObjective DomainObjective # Troubleshooting Installation and Startup Issues Troubleshoot.
23 November 1999Sticky Technology for Augmented Reality Systems Brian Parkison Workflow Team STARS Project Carnegie Mellon University 23 November.
Click anywhere to start the presentation. Steps to Resolve Error Code "17099" in MS Outlook Mac 2011 Fix Mac Outlook Corruption Issues OLM to PST Converter.
11 November 1999Sticky Technology for Augmented Reality Systems Daniel Heller Architecture Team STARS Project Carnegie Mellon University 11.
Advanced Higher Computing Science
Oracle Database High Availability
Cameron Blashka | Informer Implementation Specialist
Using Use Case Diagrams
Requirements Analysis Document
MODULE 10 – PROJECT SERVER
Review of Authoring Subsystem
Repair Requirements Analysis Review
Data Management Agenda
Leveraging the Power of Collaboration
Oracle Database High Availability
PRELIMINARY DESIGN Stage Gate Reviews
Management of Change Report Errors to Management.
Hardware/Software Allocation
Design and Programming
Azure Information Protection
Azure Information Protection
SAD ::: Spring 2018 Sabbir Muhammad Saleh
SpiraTest/Plan/Team Deployment Considerations
Object Design Michael Fortson Augmented Reality/UI Team STARS Project
Registry Information Session
Using Use Case Diagrams
5 POINT PLAN THE SYSTEMS LIFE CYCLE ANALYSE DESIGN
Presentation transcript:

Boundary Conditions Samuel Chong Repair Team STARS Project 15-413 Boundary Conditions Samuel Chong Repair Team STARS Project Carnegie Mellon University 11 November 1999 2 11 November 1999 Sticky Technology for Augmented Reality Systems

Sticky Technology for Augmented Reality Systems Subsystem Breakdown Augmented Reality Authoring Inspection Modeling Repair Workflow 11 November 1999 Sticky Technology for Augmented Reality Systems

Subsystem Dependencies 11 November 1999 Sticky Technology for Augmented Reality Systems

Sticky Technology for Augmented Reality Systems Initialization Augmented Reality UI service provider No data required, no other systems required Expects widgets from Modeling, Inspection, and Repair Authoring Access into the workflow database must be available An initialization data file must be available Paper document sources must be available 11 November 1999 Sticky Technology for Augmented Reality Systems

Initialization (cont) Inspection Augmented Reality must provide its services Modeling Workflow database must be available for data on the airplane 11 November 1999 Sticky Technology for Augmented Reality Systems

Initialization (cont) Repair Inspection should provide its visual UI for workorder and sticky navigation Workflow database should provide documents such as workorders and IETMs Workflow Server requires a user data file for authorization purposes Client has no initialization dependencies 11 November 1999 Sticky Technology for Augmented Reality Systems

Sticky Technology for Augmented Reality Systems Termination Workflow Database should be highly available; i.e. termination is not a normal occurrence Client has no restrictions on termination Workflow is unaffected by the termination of other systems Authoring System is only required during creation and modification of digital documents, and will terminate once that is done Termination does not affect other subsystems 11 November 1999 Sticky Technology for Augmented Reality Systems

Sticky Technology for Augmented Reality Systems Termination Augmented Reality Should terminate only when PEDD is not being used If terminated, other subsystems running on the PEDD will no longer receive input events except through speech Repair Should terminate once the repair is done If terminated, other subsystems running on the PEDD can no longer be speech-controlled 11 November 1999 Sticky Technology for Augmented Reality Systems

Sticky Technology for Augmented Reality Systems Termination Modeling Will terminate when maintenance is over Does not affect other subsystems when terminated Inspection Will terminate once maintenance is over Data must be saved to Workflow database Termination will render Repair subsystem non-functional 11 November 1999 Sticky Technology for Augmented Reality Systems

Sticky Technology for Augmented Reality Systems Failure Overview Communications failure Likely to be a common problem because of the environment Wireless communication, if it is not available, should be covered by a wired alternative Data loss True robust error recovery is beyond the scope of this phase of the project Reinitialization of each system is the easy solution for crash recovery 11 November 1999 Sticky Technology for Augmented Reality Systems

Sticky Technology for Augmented Reality Systems Failure Workflow Notifications Other subsystems will have to wait until communications are restored to retrieve data Augmented Reality No external communications requirements No persistent data to back up 11 November 1999 Sticky Technology for Augmented Reality Systems

Sticky Technology for Augmented Reality Systems Failure Authoring If workflow is unavailable, no submissions are possible Version control can provide limited protection from data loss Modeling Relies somewhat on the Workflow database for some necessary information No persistent data to back up 11 November 1999 Sticky Technology for Augmented Reality Systems

Sticky Technology for Augmented Reality Systems Failure Inspection and Repair If Workflow database is down, no data can be retrieved or submitted All persistent data is stored in Workflow database 11 November 1999 Sticky Technology for Augmented Reality Systems