subglobal1 link | subglobal1 link | subglobal1 link | subglobal1 link | subglobal1 link | subglobal1 link | subglobal1 link
subglobal2 link | subglobal2 link | subglobal2 link | subglobal2 link | subglobal2 link | subglobal2 link | subglobal2 link
subglobal3 link | subglobal3 link | subglobal3 link | subglobal3 link | subglobal3 link | subglobal3 link | subglobal3 link
subglobal4 link | subglobal4 link | subglobal4 link | subglobal4 link | subglobal4 link | subglobal4 link | subglobal4 link
subglobal5 link | subglobal5 link | subglobal5 link | subglobal5 link | subglobal5 link | subglobal5 link | subglobal5 link
subglobal6 link | subglobal6 link | subglobal6 link | subglobal6 link | subglobal6 link | subglobal6 link | subglobal6 link
subglobal7 link | subglobal7 link | subglobal7 link | subglobal7 link | subglobal7 link | subglobal7 link | subglobal7 link
subglobal8 link | subglobal8 link | subglobal8 link | subglobal8 link | subglobal8 link | subglobal8 link | subglobal8 link

Software Project Outline

 

Software Project Outline

Version 1.0

 

December 06, 2004

 

 


  1. Overview

 

Team Evolution has been contracted to create a set of controls that will enhance the control for the School of Engineering robot “Taz”. The project has been named the Robotics Orientation and Mapping Project or R.O.M.P. Our clients have deemed it necessary to add controls to the current user interface that will allow users to zoom, pan, and tilt the front-mounted camera on the robot. In addition they have requested that a mapping feature be added so that users will know the location and orientation of the robot in the engineering building.

 

Our clients for this project are Dr. Jerry Weinberg, Associate Professor for the Computer Science Department at SIUE, and Andrew Lamonica, Instructional Support Specialist for the Computer Science Department. At their request, we will be developing software that will be integrated into the current system. We must have a software design, complete with prototype by the conclusion of the fall semester 2004, with final delivery scheduled for the conclusion of the Spring Semester 2005.

 

  1. High-Level Functionality

 

The software that we will be developing will consist of a JAVA applet that will be integrated into the Applet portion of the current system. Our software will introduce controls that allow users to tilt, zoom, and pan the front-mounted camera. Their will also be a map display added that will show the robot's position and orientation in the building.

 

The zoom control will give users the ability to zoom the camera in and out as they navigate through the engineering building. This feature will enhance the overall experience for users giving them added sight distance as they control the robot.

 

The panning feature that will be added allows users to turn the camera left or right. The purpose of this feature is to give users a better view of the robot's surroundings, as the current camera only allows a straight-ahead view.

 

The tilt feature allows the camera to tilt up and down up to a specific angle. This feature adds more visibility for the user, and in combination with the zoom, and panning features should allow the user to be able to visualize the robot's surrounding environment in a more complete, and human-like manner than at present.

 

The mapping feature is an essential addition to the user interface. It allows users to see their location and orientation in the building. This is very important because the users of the system will be school aged children, and these children will not have a familiarity with the building. The mapping feature will allow them to navigate more easily throughout the building.

 

  1. Stake Holders

 

The most recognizable stake holder in this project is our development team, Team Evolution. Our success in CS 425 Senior Project, and ultimately our graduation are directly affected by the outcome of this project. Our clients Dr. Weinberg and Andrew Lamonica are also stake holders in the project. As our clients they are depending on us to deliver their requested software to them complete and on time. Upper management, Dr. Weinberg and Dr. Blythe, hold stake in the project as well. The success of the project is a reflection of their management and instruction. The CS department and the School Of Engineering as a whole benefit from the success of each of the senior projects. In particular our project will improve the robotics website, which will in turn improve the public image of the school of engineering as a whole.

 

  1. Project Needs

 

There are a few things that will be needed for the successful completion of our project. Perhaps the most important thing necessary for project success is the productivity of our team. This coupled with the necessary development tools, and support should allow us to successfully complete our task.

 

The things that will be needed from the team are simple; good communication, clear tasking, informed decision making, and quick and effective conflict resolution. Each of these points follows from one another. First we must have clear lines of communication. Each member should know the progress of the others, and the short and long term goals of the project. This is easily accomplished by regular team meetings, and regular correspondence. Good communication will allow the team to have clear tasking. This is important so that we all know what is needed of us and we can accomplish our goals and stay on schedule. Good communication and clear tasking make way to informed decisions. If each member is up to date on their task and know the status of the rest of the team's tasks, we can make good plans and decisions to keep the project running smoothly. Finally with all the afore mentioned points we will be able to resolve conflicts in a timely manner, because we will all be aware of project status and the direction that we are going with the project.

 

In addition to a good team dynamic we will need to have readily available the proper software tools, hardware tools, and support. None of these pose a problem since we do have the necessary tools for successful completion of the project. Our software will be written in Java, and we have the instructional books, and software necessary to produce it. The hardware that we will need is already part of the current system. For support we have our clients, and upper management readily available to answer questions and provide guidance.

 

 

 

  1. Project Risks

 

The risks associated with our project should be confined to the normal risks associated with any project. The risk that will be specific to our project is training in the Java language. The team is inexperienced with Java so we will have to learn as we go.

 

  1. Project Payoffs

 

There are several payoffs that will come with the successful completion of this project. First for our clients, they will receive software that will enhance their website. The payoff to our development team will be successful completion of our senior project, and software that can be showcased as being developed by us. Upper management is paid off in that the more successful projects that are completed; the more possible projects will result.

 

  1. Conclusion

 

The software project that our team has been assigned to will provide a valuable experience for us. The software that we will be developing will be a valuable addition to our client's current system. The software will provide users with additional features that will enhance their user experience. Our team, our clients, and the School of Engineering will all benefit from our project's success. The tools needed for our success are basic and readily available. The payoffs include experience for our team, and a good product for our clients. The project risks are easily managed with proper planning. Good communication and good work habits will ensure the success of our project.

 

 

About Us |Contact Us | ©2004 Team Evolution