Studies in the Imagery of the Ramayana - Prof. K.a. Subrahmanya Iyer
1 R.O.M.P Robot Orientation Mapping Project (Project Plan) Team Evolution Peri Subrahmanya: Lead...
-
Upload
alison-sherman -
Category
Documents
-
view
214 -
download
0
Transcript of 1 R.O.M.P Robot Orientation Mapping Project (Project Plan) Team Evolution Peri Subrahmanya: Lead...
1
R.O.M.PRobot Orientation Mapping Project
(Project Plan)
Team Evolution
Peri Subrahmanya:
Lead Designer
Michael Lazar:
Project Manager
Sean Hogan:
Lead Designer
Joe Hackstadt:
Lead Programmer
Sean Williams:
Documentation & Testing
Overview
• Lifecycle Choice
• Project Timeline
• Deliverables
• Plans
• Development Tools/Support
• Project Status
• Questions
Team Evolution
Evolutionary Delivery
Control and Mapping
implementation
Control and Mapping interface
Team Evolution
Evolutionary Delivery with Subprojects
• Design of Architecture and System Core– Mapping architecture– Control architecture
Detailed Design
Coding and Debugging
Subsystem Testing
Detailed Design
Coding and Debugging
Subsystem Testing
Control Subproject
Mapping Subproject
Team Evolution
Project Timeline
Deliverables
• A working web interface• Pan control (Move Camera Up or Down)• Zoom Control (Zoom in or Zoom out)• Camera Control (Move camera left or right)• Mapping Feature (Positional Information)
Prototype (#1)
Team Evolution
Design Decisions
• Camera Control– Flat Panel or– Arch Dial
• Mapping Feature– Zoomed View or– Full View with zoom option
Team Evolution
Organization Chart
Peri Subrahmanya
Lead Designer/Web Administrator
Sean WilliamsDocumentation/Testing
Mike LazarProject Manager
Joe HackstadtLead Programmer
Sean HoganLead Designer
Andrew Lamonica
Client
Dr. BlytheUpper Management
Dr. WeinbergUpper Management/Client
Team Evolution
Conflict Resolution
• In the Event of a Conflict– Members will present their case to team– All team members will then vote for solution– Team leader has final say in case of a tie– Extreme cases taken to upper management
Team Evolution
Risk Management
• Difficult Learning Curve– Reading Java and graphics books– Reading existing code– Working With Andrew Lamonica
• Incompatibility with Aria– Working with Andrew Lamonica
• Video Streaming Issues– Researching streaming methods
• Unforeseen Dependencies– Adequate buffer time scheduled
Team Evolution
Test Plan
• Module Testing– Test each individual module
• Integration Testing– Test each time multiple modules are combined
• System Testing– Test entire system once all modules are
implemented and combined– Test system on emulation server– Test system on Marvin before moving to Taz
Team Evolution
Documentation Plan
• Follow standards and naming conventions team determined
• Keep a running document of all changes and revisions
• Document all test cases and results
Team Evolution
Review Plan
• Scheduled Code Walkthroughs – Coder explains his code to the team– Explains why/how what was done
• Scheduled Code Inspections– Other team members inspect the code– Try to understand without coder explaining
Team Evolution
Installation Plan
User Workstation- No installation necessary
- Web server will serve up applet to user
Applet & Middleman (Team Evolution & Andrew Lamonica)
- Modifying existing system
- Changes will be implemented for Marvin during development
- Once complete, system will be transferred to Taz.
Robot Server (Andrew Lamonica)
- Switch from Saphira to Aria robot control system
Team Evolution
Development Tools
• Languages– JAVA
• Development Software– Eclipse
• Support Software– Microsoft Word– MS Project 2003
Team Evolution
Activities to Support Development
• Learning the Current System– The Applet– The Middle Man– Remote Control
Server
• Learning JAVA
Project Status
• Finalizing Camera Control Design
• Finalizing Mapping Design
• Finalizing Documentation
• Working on Prototype
Team Evolution
QuestionsTeam Evolution