| mailto:HTMB | |||
|---|---|---|---|
| Hyoungsuk Kong | Taeho Kim | Mina Jeong | Bo Jin |
| kong@cs.utah.edu | taek@cs.utah.edu | jeong@cs.utah.edu | bojin@cs.utah.edu |
The product gets image pixel values from sponsor’s software, computes the values to GPS values, and save the output as a text file. Conversely, the product also gets RDDF file from sponsor’s software, draws corridors based on RDDF file, and saves as image files. For the product, the road must be a flat, but the camera head can have a tilt.
For this product, we assume that the road is flat, but camera can have an inclination itself (tilt). A suggestion for new features is to make the product for inclined, curved road.
The goals of our product were to deliver the complete product, gain experiences, and work with a real industry sponsor. Each team member had high respect to each other, and even though there was only one team leader, everyone had same responsibility, and respected for the team, and the project. Each member of team worked hard to fulfill one's duties, and helped with other's duties.
Our team will function in a democratic manner. Every member in the group will have an equal voice and impact in the decision-making of the project. We believe this will encourage more collaboration in the team. Each member's opinion will be taken place equally and then we will make a better decision with that. However, each member will be in charge of a specific area of responsibility
Project Roles Responsibilities Team Leader Responsible for overseeing progress within each of the subteams and informing the group of upcoming deadlines Programming Leader In charge of implementation of the client's requirements Client Liaison Responsible for establishing and maintaining communication with the client. Responsible for giving the client updates to the project scheduling appointments and passing any updates from the client to the team. Techical Writers Reponsible for creating documents required for the project Techical Editors Responsible for proofreading and revising any techical documents that have been written and are slated for submission. Webmaster Responsible for maintaining the team's website and ensuring that the directory structure complies with the S2S guidelines. Graphic Designer Responsible to evaluating and creating the user interface for the program that is easy to use, intuitive and within the expectations of the client. Code Reviewer Responsible for ensure that there are not any logic errors or other coding problems that might cause a failure in the future.
Team Member Role Hyoungsuk Kong Team Leader, Techical Writers Taeho Kim Programming Leader, Webmaster Mina Jeong Graphic Designer, Techical Editors Bo Jin Client Liaison, Code Reviewer Procedures for reviews, walkthroughts, inspections, and audits
Document reviews will be held during end of team meetings.During these reviews, each member will have a copy of the documentation, then revise according to given feedback.
Once the documentation have been revised, webmaster will update the documentation on the web and submit it.
Team meetings will be held at least three times a week. We will adjust the process of project. Discussions on documentation, implementation and testing procedures will be the focus of these meetings.
Code reviews will be held to ensure the implementation has any logic error or bug might be caused in the future.
Walkthrough procedures will also involve all team members, where individuals will explain the work completed. Each team members will then offer comments and suggestions.
Inspections will occur during client meetings, in order to maintain focus on the client's expectations. Audits are conducted by the CEO to ensure that the project is following specification before entering final release.
Schdule of reviews, walkthroughts, inspections, and audits
Document reviews will occur every week before any submission.
Code reviews and walkthrough procedures will occur during team meetings every week.
Client inspection will occur once a week.
Audits by the CEO will occur once a week.
We had at least 3-4 meetings with team member, a CEO meeting, a sponsor meeting. Each sponsor meetings, we showed what you had done to sponsor and if you had questions, asked him and solved problems. At middle of March, we were almost done but the sponsor suggested us one more thing to do which was to read the RDDF file and draw a path. So it made the team really busy, but it has done about middle of April. If anyone couln't join the meeting, that person sent email or gave the call to other team members. If anybody finished a part of the code, that person made a new version of the code and every team member shared the code.
Everytime we release new version, we tested if for the bug-free program. During testing, if anybody found any bugs or defects, we usually had a meeting or that person sent email to every team member. If you couln't fix it, we asked our sponsor and fixed it. Then we spent for 3 weeks to just test the project to make sure that was working properly and fix any problems that we found along the way.
Our clients will feed our project to their machine. So we followed their programming language(visual basic 6.0), and the program which was already built by them. We had a meeting once a week. While we were testing the project, the clients picked up what we needed to do more,or what we did wrong. So we could fixed the part whatever the clients wanted.
From the point of view of the student teams, our team have advice that we need to study computer science stuff and also geography, and math(especially GPS calculation) to get more accurate data. Also, if the program can handle inclined road, the program can be more useful.
None
Our team had lots of discussions and meetings with mentor and finished the basic program for the whole project. After that, we made more features which made the program more accurate. The accomplishment is satisfiable.
| Version | Release Date | Modification |
|---|---|---|
| 1.0 | 04/27/05 | Initial release of Final report |
Back to cs4500 Back to Home Back to Top Maintained by Taeho Kim |