1 / 12

CS511 - Spring 2006 Preliminary Presentation Project 3 - Team 1

CS511 - Spring 2006 Preliminary Presentation Project 3 - Team 1. Ching Chang Panagiotis Papapetrou Raymond Sweha. Outline. Project Management Progress Diagrams Requirements Specification Web-site Demo Conclusions. Purpose of the Project.

rosalyn-britt
Download Presentation

CS511 - Spring 2006 Preliminary Presentation Project 3 - Team 1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CS511 - Spring 2006Preliminary PresentationProject 3 - Team 1 Ching Chang Panagiotis Papapetrou Raymond Sweha

  2. Outline • Project Management • Progress Diagrams • Requirements Specification • Web-site • Demo • Conclusions

  3. 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 will be able to load a file in STEP format and convert it to the corresponding graphical representation.  • During both phases a type-checker will be running on the background to ensure that both the graphical representation and the STEP file are syntactically correct. 

  4. Project Management (1/3)The Waterfall Model

  5. Project Management (2/3)Pert Diagram

  6. Project Management (3/3) Gantt Diagram

  7. Requirements Specification (1/2)Functional Requirements • Design of a graphical “programming” interface for STEP. • Recognize STEP-formatted execution files. • Have the ability to handle syntax errors online. • Recognize SNAFU-formatted execution files.

  8. Requirements Specification (2/2)Interface Requirements • GUI • Set of buttons that offer 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. • Area where the syntax errors are shown. • INPUT • STEP-formatted file or SNAFU-formatted file. • OUTPUT • A syntactically correct STEP file, created based on the graphical execution design.

  9. Type-checker • One function – two : • Validate online after each step • Validate on demand • Types of Exceptions: • IllegalChildException: • ForwardIllegalChildException: a node links to the wrong forward child. • BackwardIllegalChildException: a node links to the wrong backward child (feedback). • UnlinkedNodeException: a node is not linked (has no children or parent or both). • RepeatedIdException: the id of a node already exists. • InvalidLeafException: the type of a Leaf node should be: LastTriggerEval, Value, Constant, ... • InvalidRootTypeException: the type of the Root should be "stepgraph".

  10. Web-site http://cs-people.bu.edu/panagpap/511

  11. Demo

  12. Conclusions • So far… • Preliminary GUI design • GUI-to-STEP • Type-checker (preliminary version) • Next… • Step-to-GUI • Complete Type-checker • Recognize SNAFU files

More Related