Transcript CS5111 - Spring 2006 Preliminary Presentation Project 3

CS511 - Spring 2006
Final Presentation
Project 3 - Team 1
Ching Chang
Panagiotis Papapetrou
Raymond Sweha
Outline

Project Management

Progress Diagrams

The system:

Requirements Specification

Type-checking

Web-site

Demo

Directions for Future Work
Purpose of the Project

Creation of a graphical "programming" interface for a sensor network
tasking language STEP (Sensor Task Execution Plan).

The graphical interface allows the user to specify a program
execution graphically and save the results as a properly formatted
STEP file.

The software can load a file in STEP format and convert to its
corresponding graphical representation.

During both phases a type-checker is activated on demand to ensure
that both the graphical representation and the STEP file are
syntactically correct.
Project Management (1/3)
Pert Diagram
Project Management (2/3)
Gantt Diagram
Project Management (3/3)
Team Work
Panagiotis
Papapetrou
Ching Chang
1. Requirements Specification.
2. Web-site Design and Maintenance.
3. External Documentation.
1. GUI Design.
2. STEP-to-GUI Conversion.
3. GUI-to-STEP Conversion.
4. GUI Maintenance.
CVS and
Meetings
Raymond Sweha
1. GUI Design.
2. Type-checker.
3. Internal Documentation.
Requirements Specification (1/2)
Functional Requirements

Design of a graphical “programming” interface for STEP.

Load STEP-formatted execution files and convert them
to a graphical representation.

Type-check the STEP file on demand.

Connects to SNBENCH and executes the graphical
representation.
Requirements Specification (2/2)
Interface Requirements


GUI

Menu that offers the user all the functionalities needed to design
the appropriate modules of a STEP program.

Area where the user designs the execution and where all the
objects are placed.

Current version of the STEP file.
INPUT


Graph or STEP-formatted file.
OUTPUT

A syntactically correct STEP file, created based on the graphical
execution design or the graph of the input STEP file.
Type-checker

Validates on demand using a “Compile” button.

When an error is detected, a message is shown.

Supports every type of STEP node.

Current version does not type-check “expression” nodes.
Testing our system

Used the STEP files available in testsuite.

Loaded the STEP files and produced the STEPGraph.

Converted the STEPGraph to its corresponding STEP file.

The original file and the new file were identical.
Web-site
http://cs-people.bu.edu/panagpap/511
Demo
Current Limitations and
Future Work

Type-check expressions:


More complex than the other STEP nodes.
Handling duplicate IDs in multiple STEP
programs.

Recognize SNAFU-formatted files