Team Awesome. The Five Ws of SUMS  What is SUMS? SUMS is a system designed to monitor sensors and display their information neatly.  Who is SUMS appealing.

Slides:

Advertisements

Similar presentations

Sliver Information system KITMaster. Sliver Information System KIT Real time production and quality monitoring –sliver count –sliver evenness –spectrogram.

Advertisements

SENG521 (Fall SENG 521 Software Reliability & Testing Operational Profiles (Part 5b) Department of Electrical & Computer Engineering,

Write Your Project Title Here VU Logo Here Group Members Introduction Write your group members introduction here with names and VU Id.

Setting up of condor scheduler on computing cluster Raman Sehgal NPD-BARC.

João Frazão Rescue Project Software Architecture João Frazão.

CS511 - Spring 2006 Final Presentation Project 3 - Team 1 Ching Chang Panagiotis Papapetrou Raymond Sweha.

RockSat-C 2011 SITR Payload Subsystem Integration and Testing Report University/Institution Team Members Date.

1 Remote Monitoring System EIN Systems Environmental Intelligence Network Systems Remote Monitoring System - Requirements Specification - Welcome Mr. Ken.

WVU TRANSPORTATION APP Group 10 Peter Kirkpatrick – Shane Welsh – Steven White Mentor: Dr. Bourlai.

Use cases and requirement specification - 1 Use case diagrams 3 use cases System boundaries Remember: Use case diagramming is a tool, not the requirements.

Requirements Specification MAJIK Software Solutions 1 Virtual Network Device Mapping System Requirements Specification By MAJIK Software Solutions October.

Welcome Ms. Jami Cotler & Dr. Scott Hunter NSG Software Development October 26, 2005 NSG Software Development October 26, Requirements Specifications.

The project plan. December 16, Agenda The project plan –Risks –Language decision –Schedule –Quality plan –Testing –Documentation Program architecture.

Smart Home Current Progress Summary. Main Processor – Stellaris.

Hands-On Microsoft Windows Server Connecting Through Terminal Services Terminal server – Enables clients to run services and software applications.

CORE 1: PROJECT MANAGEMENT Overview TECHNIQUES FOR MANAGING A PROJECT Communication Skills Active Listening Mirroring Paraphrasing Summarizing Clarifying.

Using The WDK For Windows Logo And Signature Testing Craig Rowland Program Manager Windows Driver Kits Microsoft Corporation.

N A managed approach to planning and controlling the implementation of complex application software. n A flexible tool kit, designed to support the Project.

Chapter 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps.

TMC Replicable Project Presented by Rachael Jarboe July 9, 2009 City Vision College.

RUP Requirements RUP Artifacts and Deliverables

Abdulmotaleb El Saddik Prof. Dr.-Ing., FIEEE, FCAE University Research Chair ELG 4913F ELG 4913F Electrical Engineering Design Project II

Analysis Modeling (cont’d) CpSc 372: Introduction to Software Engineering Jason O. Hallstrom Authorship Disclaimer. These slides.

Rational Unified Process Fundamentals Module 4: Disciplines II.

Business Analysis and Essential Competencies

Requirements Information and data which need to be displayed or accessible to the user Sitemapping (Site Map) Flow Chart models of site structure displaying.

Database Administration COMSATS INSTITUTE OF INFORMATION TECHNOLOGY, VEHARI.

WCMS Report Web Advisory Committee April Joining the Teams WCMS and Redesign Team collaborating extensively; –In May to develop functional requirements.

Deliverable #9 – Detail Design Subsystem Design and Realization ALL of your design class model elements must have the package or subsystem they are associated.

KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.

Students: Anurag Anjaria, Charles Hansen, Jin Bai, Mai Kanchanabal Professors: Dr. Edward J. Delp, Dr. Yung-Hsiang Lu CAM 2 Continuous Analysis of Many.

Sun SPOT Universal Mote System Team Awesome by Team Awesome.

Human Factors in Information Seeking and Use Wooseob Jeong.

CS 4850: Senior Project Fall 2014 Object-Oriented Design.

University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 Use Case 1 what are use cases? “A specification of sequences of actions, including variant.

Midterm Presentation Capstone Team#1, Spring 2011 Irshad Ahmad KhanBalaji Srinivasan Ramakrishna AtluruVideesh Gogineni Instructor: Dr. Kwok-Bun Yue Mentor:

OTEPAD SDS PRESENTATION

Unified Distributed (UDub Mail) Life Cycle Objectives Sachin Pradhan Gabriel Maganis.

Final Class Diagram for C++ Implementation Clickermatic Software Clicker.

A PPARC funded project Architecture Appeal Guy Rixon AstroGrid Consortium meeting April 2004.

Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.

Structural Design Software TYLER HUTCHISON. Requirements  Develop an interface to generate a text file.  The text file is then passed to one of five.

Computer Science 340 Software Design & Testing Software Architecture.

CIS 4910 Information Systems Development Project Project Documentation.

Copy to Tape TOI. 2 Copy to Tape TOI Agenda Overview1 Technical Feature Implementation2 Q&A3.

Clever Framework Name MARCH 27, Meeting Agenda  Framework Overview  Prototype 1 Design Goals  Prototype 1 Demo  Prototype 2 Design Goals  Timeline.

RockSat-C 2013 FMSTR Full Mission Simulation Report University/Institution Team Members Date.

Lecture 1: Introduction – Graduation Projects Topics to Discuss in Lectures 1. Project Deliverables 2. Course grading 3. Project Concept Writing.

Unit 17: SDLC. Systems Development Life Cycle Five Major Phases Plus Documentation throughout Plus Evaluation…

Physical Views Component: A component is a physical unit of implementation with well-defined interfaces that is intended to be used as a replaceable part.

Correlator GUI Sonja Vrcic Socorro, April 3, 2006.

1 Circuitscape Capstone Presentation Team Circuitscape Katie Rankin Mike Schulte Carl Reniker Sean Collins.

Stand-Alone and Mesh Networks of Dissolved Oxygen (DO) Monitors Sd-May11-20 Betty Nguyen Scott Mertz David Hansen Ashley Polkinghorn Advisors Joseph Shinar.

Project management Topic 2 Product based planning.

APRIL 10, Meeting Agenda  Prototype 2 Goals  Robust Connections Demo  System Diagnostics Tool Demo  Final Prototype Risk Mitigation  Final.

Chapter 7: Delivery, Installation, and Documentation Ronald J. Leach Copyright Ronald J. Leach, 1997, 2009, 2014,

SYSTEM ANALYSIS AND DESIGN LAB NARZU TARANNUM(NAT)

Supervisor: Tran Dinh Tri Group Members: Duong Ngoc Nhat-NhatDN01687 Nguyen Quang Minh-MinhNQ01717 Nguyen Quang Minh-MinhNQ01717 Duong Hoang Nam-NamDH01552.

1 SUMS Requirements Spot universal mote system Team Awesome.

Automatic manufacturing systems project I. KMAGP12ANC L: András Boráros-Bakucz.

SOFTWARE DESIGN AND ARCHITECTURE

Unified Modeling Language

GÉANT Multi-Domain Bandwidth-on-Demand Service

iLab new User Registration

CVM GUI Team #1 Final Presentation Barbara Espinoza Jorge Guerra

Software Development Process

Planning a Network Upgrade

Introduction to Software Planning and Design

Wide Area Workload Management Work Package DATAGRID project

Web Service Security support in the SSE Toolbox

Presentation transcript:

Team Awesome

The Five Ws of SUMS  What is SUMS? SUMS is a system designed to monitor sensors and display their information neatly.  Who is SUMS appealing to? SPOT developers who wish to test their sensors to ensure proper functionality and SPOT administrators who wish to monitor the usage of the SPOTs.  Where will the SUMS system be implemented? Here at TCU! We will use lab machines to ensure that the software serves its purpose.  When will SUMS be completed? The Final Presentation of the SUMS is tentatively scheduled for April 28, 2009

The Five Ws of SUMS  Why are we making SUMS? As we were experimenting with SPOTs, we found sample applications and reasons to program SPOTs but no environment in which to monitor multiple sensors on multiple motes.  How?

Design Review Outline  System Architecture  Interface Design  Use Cases

System Architecture: Topology

System Architecture: Class Diagram

Interface: User Interface Prototype

Interface: Connection Diagram

Interface: Data Flow Diagram

Use Cases

WAMM View Topology

WAMM Log Data

WAMM Disconnect Sequence

LAMM Connect to WAMM Sequence

LAMM View Topology

LAMM Configure Data

LAMM Log Data

LAMM Disconnect Sequence

Mote Join

Mote State Diagram

Mote Disconnect Sequence

To learn more or to view full documents, please come to our website: