1 SUMS Requirements Spot universal mote system Team Awesome.

Slides:



Advertisements
Similar presentations
© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Advertisements

UML: Use Cases Michael L. Collard, Ph.D. Department of Computer Science Kent State University.
Wireless Magnetic Tracking Preliminary Design Review Team Members Ying W. Moy Mohammed A. Dastigir Hassan Malik Advisors Prof. Moritz Prof. Krishna Prof.
Use cases and requirement specification - 1 Use case diagrams 3 use cases System boundaries Remember: Use case diagramming is a tool, not the requirements.
L/O/G/O Prepared By Abdullah Mustafa Abu Nada Hussian Abd-Jaleel Shaalan Nael Wael Skaik Supervised By.
1 Introduction to UML DIAGRAMS & CLASS DIAGRAM Chapter 7,8 主講人 : 許勝杰
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.
Lesson 7 Guide for Software Design Description (SDD)
Wireless Sensor Networks MOTE-KITS TinyOS Crossbow UC Berkeley.
Requirements Documentation CSCI 5801: Software Engineering.
Status Report #2 Automatic Child Safety Gate: Corry Winslow Roger Battles Philip So Description: A telescoping gate with sensor technology through the.
1 SMART Training Update – May 2011 Michaela Butterworth.
Sun SPOT Universal Mote System Team Awesome by Team Awesome.
1 ECCF Training 2.0 Implemental Perspective (IP) ECCF Training Working Group January 2011.
Defect Classes and the defect repository
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Name Of The College & Dept
4+1 View Model of Software Architecture
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 6/6/2016 1/25 IT076IU Software Engineering Project Review 2.
Chapter 1 Vocabulary Mr. Greaser. Geography The study of the earth and its people.
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Discussion of Course Syllabus Class will start momentarily. Please Stand By … CS 8532: Advanced.
CS 8532: Adv. Software Eng. – Spring 2009 Dr. Hisham Haddad , Monday Class will start momentarily. Please Stand By … CS 8532: Advanced Software.
START. A room full of computers Two or more computers connected together in order to communicate A computer that can communicate with every living thing.
Future Lock Security Group Member Nguy ễ n V ă n Tuy ề n – SE02119 Vũ Ng ọ c Linh – Vũ V ă n An – SE02207 Supervisor Hoàng Xuân S ơ n Project Code.
Automatic manufacturing systems project I. KMAGP12ANC L: András Boráros-Bakucz.
A monitoring system for the beam-based feedbacks in the LHC
Yard Management for Inbound Deliveries
ELECTRONIC NOTICE BOARD WITH MULTIPOINT RECEIVERS
Department of Computer Science
SUBMITTED BY EDGEFX TEAM
Chapter 2- Visual Basic Schneider
Dynamic Modeling of Banking System Case Study - II
DBS INSTITUTE OF TECHNOLOGY
System Design.
Deconstruction of the Wilderness Weather Station Case Study
The Next Stage in Analysis: Systems Use Case Diagrams
IoT Network Monitor.
System Requirements Specification
Unix access in the 1970s-1980s Each monitor+keyboard directly connected to server HW (serial line) Multi-user Program on mainframe that lets you “talk”
JPL Autonomous Space Mission Simulation
University Event Management System
PMIS Initiating a Project Application of Project Management Processes Project Charter Stakeholder Analysis and Stakeholder Register 2. Planning.
Stand-Alone and Mesh Networks of Dissolved Oxygen (DO) Monitors
Fig. 1 Conceptual Block Diagram
Smart Doorbell Using Raspberry Pi
Common computer terminology
C69 - Service Order Management (ERP Integration)
Team 2 Yimin Xiao Jintao Zhang Bo Yuan Yang Yang
Team # 13 Touch 2 Order.
Student’s Name with USN No.
Chapter 2- Visual Basic Schneider
Project Management Scenario Overview
Software Design Lecture : 15.
Chapter 2- Visual Basic Schneider
Training Module Introduction to the TB9100/P25 CG/P25 TAG Customer Service Software (CSS) Describes Release 3.95 for Trunked TB9100 and P25 TAG Release.
Introduction to Software Planning and Design
ECE 477 Final Presentation Team 15  Spring 2010
CEN 5035, Software Engineering
Design Challenge.
<Project Title>
Use Case Analysis – continued
Tools for the Automation of large distributed control systems
Chapter 1 Vocabulary Mr. Greaser.
Designed by Hwandong Joo
TECHNOLOGY GUIDE TWO Software.
Project Management Unit #2
Web Programming : Building Internet Applications Chris Bates CSE :
SRS : Software Requirement Specification. How to Write a Software Requirements Specification (SRS Document)  A software requirements specification (SRS)
1B8 - Executing the Payroll Process as Payroll Process Manager
Presentation transcript:

1 SUMS Requirements Spot universal mote system Team Awesome

2 Outline  Overall Description  System Features WAMM LAMM Base stations Motes  Interface Requirements

3 Overall Description  Purpose Provide a means for SPOT users to monitor sensor data on SPOTs from a graphical console  Scope Monitor the overall topology of motes connected to SUMS Read and display sensor values from motes

4 Product Perspective & Features  Product Perspective  Product Features

5 System Features  WAMM - Wide Area Motes Monitor Monitor all LAMMs as well as display the data being sent from the motes

6 System Features  LAMM - Local Area Motes Monitor Monitor up to eight motes as well as display the data being sent from them

7 System Features  Motes Monitor all LAMMs as well as display the data being sent from the motes Stimulus/Response Sequences Functional Requirements Non-functional Requirements

8 System Features  Motes Send Sensor Data Dynamically and Automatically Connect to SUMS Stimulus/Response Sequences Functional Requirements Non – functional Requirements

9 System Features  Base stations Connect to Motes in Range Send data to LAMM Stimulus/Response Sequences Functional Requirements Non – functional Requirements

Interface Requirements  Hardware Interfaces  Communications Interfaces TCP/IPInternal socketRadioStream

Data Flow Diagram

12 TEAM AWESOME To view the full document, please come to our website: