<p> Uncle Sam’s America Project Plan Ongo8c</p><p>Faculty Advisors: Dr. John Lamont Professor Ralph Patterson</p><p>Client: Ames Community Schools</p><p>CprE/EE 492 Team Members:</p><p>David Schwenker, CprE Robert Sailer, EE</p><p>CprE/EE 491 Team Members:</p><p>Jeff Russell, CprE Dimitry Berg, CprE</p><p>REPORT DISCLAIMER NOTICE</p><p>DISCLAIMER: This document was developed as a part of the requirements of an electrical and computer engineering course at Iowa State University, Ames, Iowa. This document does not constitute a professional engineering design or a professional land surveying document. Although the information is intended to be accurate, the associated students, faculty, and Iowa State University make no claims, promises, or guarantees about the accuracy, completeness, quality, or adequacy of the information. The user of this document shall ensure that any such use does not violate any laws with regard to professional licensing and certification requirements. This use includes any work resulting from this student-prepared document that is required to be under the responsible charge of a licensed engineer or surveyor. This document is copyrighted by the students who produced this document and the associated faculty advisors. No part may be reproduced without the written permission of the senior design course coordinator.</p><p>17 September 2004 Table of Contents</p><p>LISTS OF FIGURES……………………………………………………………...…….iv</p><p>LIST OF TABLES…………………………………………………………………...…..v</p><p>LIST OF DEFINITIONS………………………………………………….…..………...vi INTRODUCTION...... 1 Abstract...... 1 Acknowledgements...... 1 Problem Statement...... 1 General Problem Statement...... 1 General Solution-Approach Statement...... 2 Operating Environment...... 2 Intended Users and Uses...... 3 Intended Users...... 3 Intended Uses...... 3 Assumptions and Limitations...... 3 Assumptions...... 3 Limitations...... 4 Expected End-Product...... 4 PROPOSED APPROACH AND STATEMENT OF WORK...... 6 Proposed Approach...... 6 Functional Requirements...... 6 Constraint Considerations...... 7 Technology Considerations...... 7 Technical Approach Considerations...... 7 Testing Requirements Considerations...... 7 Security Considerations...... 9 Intellectual Property Considerations...... 9 Commercialization Considerations...... 9 Possible Risks and Risk Management...... 9 Proposed Milestones and Evaluation Criteria...... 10 Project Tracking Procedures...... 11 Statement of Work...... 11 ESTIMATED RESOURCES AND SCHEDULE...... 14 Estimated Resource Requirements...... 14 Personnel Effort Requirements...... 14 Other Required Resources...... 15 Financial Requirements...... 15 Schedule...... 16 CONCLUSION...... 18 Project Team Information...... 18 Client Information...... 18 Faculty Advisor Information...... 18 Team Member Information...... 18 Summary...... 19 References...... 19 List of Figures</p><p>Figure 1: Client-Server Relationship...... 2 Figure 2: Database Framework...... 6 Figure 3: Degrees of Testing...... 8 Figure 4: Schedule...... 17 Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p>List of Tables</p><p>Table 1: List of Acronyms and Definitions...... vi Table 2: Milestones and Current Status...... 11 Table 3: Estimated Personnel Effort (Hours)...... 15 Table 4: Other Required Resources...... 15 Table 5: Estimated Financial Budget...... 16</p><p> ii Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p>List of Definitions The following table will help define technical and project-specific terms used throughout this document.</p><p>Table 1: List of Acronyms and Definitions</p><p>Acronym Definition ACS Ames Community Schools Apache A software product that serves web pages to clients requesting them. Apache can be used in conjunction with PHP in order to produce dynamic web pages that are built and delivered to the requesting client on the fly GUI Graphical user interface—what the user sees and interacts with while using the software HTML Hyper Text Markup Language—the language used to describe the formatting and presentation of a web page LAMP A development environment utilizing Linux, Apache, MySQL, and PHP Linux An open-source operating system that is optimized for use as a web application server MySQL An open-source implementation of an SQL server PC-compatible Personal computers that run a Microsoft Windows operating system PHP Pseudo-acronym for Hypertext Preprocessor. A computer language that enables Apache web server to dynamically generate HTML documents SQL Structured Query Language—a language used to retrieve information from SQL-compliant databases USA Uncle Sam’s America</p><p> iii Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p>Introduction This section will introduce the background information behind Uncle Sam’s America and includes the problem statement, operating environment, intended users and uses, assumptions and limitations, and expected end product description.</p><p>Abstract Ames Community Schools (ACS) has been concerned with the performance of their students’ problem solving abilities on a nationally standardized exam. While ACS traditionally scores in the 90+% on traditional math skills, results from the problem- solving section were around 40+%. The purpose of the Ongo08 project is to provide software that supplements classroom learning, particularly in the areas of mathematics and geography while stressing the improvement of problem-solving skills. To this end, a web application is being produced. The final product will allow students to solve problems and allow teachers to view the results. By utilizing the software to extend classroom learning, the students of ACS will be better prepared for standardized tests, ultimately resulting in higher test scores.</p><p>Acknowledgements Thanks to faculty advisors Dr. John Lamont and Professor Ralph Patterson for their past and continued guidance throughout this project. Also thanks to the CprE/EE 492 team members for their invaluable help and advice. Lastly, thanks go to the project client, the teachers of the Ames Community School District, for their guidance toward the final product.</p><p>Problem Statement This section includes both a general problem statement and the general solution- approach statement that will respectively provide a general overview of the problem and the approach that will be used to solve the problem.</p><p>General Problem Statement The project objective is to develop software for third through sixth grade students to learn more about United States geography using a computer-based environment. In order for students to properly operate the software, it has to be user-friendly and highly interactive. It shall provide up-to-date geographical information, such as population, land area, state flag, state song, natural resources, religions, and manufactured products for each state. Thus, it will receive this information from a database. The software shall include exercises for practice and performance examinations. It will also have to be user-friendly for teachers and instructors who will be operating the system, assisting the students, and conducting the examinations.</p><p>Internet-based teaching software will provide children in upper elementary school the opportunity to learn core subjects while exercising computer skills. The software system shall provide lessons to students and privileged access to teachers and</p><p>Page 1 Ongo8c Project Plan CprE/EE 491 Revision 1.0 administrators with which they can monitor student progress and customize lessons. It will have an interface where students can click on states to learn more about them and will provide exercises for the students to practice learning about different states while at the same time developing their mathematical skills through comparison of state statistics.</p><p>A software framework capable of managing user accounts, allowing teachers to customize their lessons, and maintaining information about each student's performance shall support the application. The system as a whole will make access and maintenance of lessons easy for teachers, and the feedback provided from the system will assist teachers in evaluating student performance. This function will be provided with the help of ongo08d, the framework team.</p><p>General Solution-Approach Statement A server or main computer shall store the software and database. The database shall contain the information for United States geography, practice exercises, questions for performance examinations, and student results. Each student will operate from their own computer, called a client, where they will learn about U. S. geography and apply what they have learned to solve problems. The server shall talk to the clients via the Internet. This relationship is shown in Figure 1. Based on the information provided by the client, the server shall generate a customized web page for that particular client. This way, each student can work at his/her own pace.</p><p>Figure 1: Client-Server Relationship</p><p>The software solution shall utilize dynamic web pages written using Hypertext Preprocessor (PHP), Structured Query Language (SQL), and Hyper-Text Markup Language (HTML).</p><p>Operating Environment Uncle Sam's America (USA) shall exist and run on LAMP (Linux-Apache-MySQL- PHP) architecture. The web application code will be written in PHP, which runs as a module to the popular and powerful Apache web server. The software will use MySQL as its database backend and run on the Linux operating system. This structure will provide a powerful open-standards environment for the web applications.</p><p>Page 2 Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p>USA will need to function on both PC-compatible and Macintosh-compatible machines. This limitation can be bypassed by using platform-independent HTML. The central server will need to be running Linux and must be capable of making many computations simultaneously. If adopted by all ACS elementary schools, USA must have the hardware to support a large number of simultaneous clients (students). </p><p>Intended Users and Uses This section identifies the intended users and uses of USA and characteristics of each.</p><p>Intended Users The intended users of USA are students in grades 3-6 as well as teachers presenting the software to the students. Other users include the school computer administrators, and also parents who will be aiding the learning process from home.</p><p>Intended Uses The main purpose of this software is to enable students to learn U.S. geography more easily using a computer-based environment. The primary use of USA will take place in computer labs in the elementary schools. The teacher will have introduced the topic before the approximately twenty or more students in a single class are allowed to explore the topic further on the computer. </p><p>A secondary use of USA will be in the homes of the students, perhaps even as part of a homework assignment. This use allows the parents to have an interactive role in their child's education. </p><p>Other uses include the following:  Managing user information.  Reviewing the results of the students' activities.  Collaborating work between the teacher and the computer administrator to add/modify/delete problems and their interactive components.</p><p>Assumptions and Limitations This section provides information about the project assumptions (engineering inferences) and limitations (physical limits imposed by the client or technology).</p><p>Assumptions Non-technical assumptions include the following:  There will be adequate supervision with computer experience to assist the students when they are operating the system.  This software shall be a supplement to classroom instruction as not all families have Internet access in their homes.  The students have been exposed to U.S. geography topics prior to their initial use.</p><p>Page 3 Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p>Technical assumptions include the following:  All client computers are connected to the Internet.  Clients have Internet Explorer 5.0 or Netscape 5.0, or later versions.  Final builds of the application will be hosted on a computer managed by the Department of Electrical and Computer Engineering.  The team will have access to a development environment on a separate machine from the production environment.  The USA application will have write-access to the server.  The application will have a developed PHP framework to support a set of Internet educational activities.</p><p>Limitations Challenges and limitations to development include the following:  Primary students may not have much prior experience using computers. The client software must be easy to understand and use.  Younger students may not know how to type. USA should provide a means for feedback appropriate to their age level.  Computers are not really interactive. They only respond to pre-defined commands. The commands available to students must make the computer appear alive. For example, when asked for a hint, the computer should supply one it has not supplied before, up to a maximum of three.  Team members must learn and become comfortable with PHP and MySQL in order to be compatible with the entire Ongo8 project team.</p><p>Other technical limitations include:  Internet connection and Internet bandwidth.  Computer/processor speed of the client machines.  MySQL database is not an enterprise database solution; so advanced features such as sub queries will not be possible.</p><p>Expected End-Product At project completion, the end product will be a web application that allows teachers to supplement classroom learning of U.S. geography. Students will be able to log in and use any of the application. They will be able to learn about geography and solve problems based on that topic. Teachers will be able to access student statistics in order to gauge student performance. Teachers will also be able to add to the applications by creating additional problems for students to solve.</p><p>At semester completion, the end product will be a web application that contains a map of the United States of America wherein each state will be a link to an information page about that state. There will also be a function to compare the states to each other in given categories, and a quiz page. This semester main concern, however, will be the comparisons page. </p><p>Page 4 Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p>A web solution allows the pages of generated HTML to be viewed on any platform. Teachers will be able to compare information obtained from all participating students. These students do not necessarily need to be in the same classroom with the teacher. Because this solution is web-based, students will have the opportunity to work on math problems associated with geography at home with their parents. This flexibility can indirectly have a large effect on parental involvement with the education process.</p><p>Page 5 Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p>Proposed Approach and Statement of Work This section includes both the proposed approach and a statement of work meant to help insure project success.</p><p>Proposed Approach The proposed approach includes the following eleven components: functional requirements, constraint considerations, technology considerations, technical approach considerations, testing requirements considerations, security considerations, intellectual property considerations, commercialization considerations, possible risks and risk management, project proposed milestones and evaluation criteria, and project tracking procedures.</p><p>Functional Requirements The following functional requirements apply to the USA software package:  The program should be accessible to students via the Internet.  The program should allow the student to choose a state using an easily navigable map of the United States.  The program should display information on a chosen state of interest upon request.  The program should integrate mathematics problem solving in meaningful ways.  The program should store results in a database as shown in Figure 2 of each student for teachers to retrieve and review.  The program should be compatible with the framework program.</p><p>Figure 2: Database Framework The user table will hold the username, password, permission settings, etc for anyone that has official access to the USA web site. Users without official access to the web site may still use the program under a general user name. No record keeping will take place in this case. The permission settings are set to allow restrictions to users, such as not allowing students to edit/create problems, and letting teachers view</p><p>Page 6 Ongo8c Project Plan CprE/EE 491 Revision 1.0 class and individual statistics. The problems table will store the problems that will be used for the students to solve. The statistics table stores the results of problems per student. </p><p>Constraint Considerations The following design constraints apply to all aspects of the project:  The program will be web-based to allow for multiple platform use (PC as well as Macintosh).  The program must be easy for third to sixth grade students to understand and operate.  Basic help instructions must be available to provide for those users that do not know how to operate computers.</p><p>Technology Considerations The technology to use for this project is largely mandated based on the imposed requirements and limitations. The application must be accessible to computers in the Ames Community Schools system over the Internet, which mandates the use of HTML to be sent from the server to the client machines.</p><p>For server technology, the use of PHP and MySQL is required because of the architecture of the machine that the software will run on. Other technologies such as ASP.NET and SQL Server 2000 cannot be used because the machine is not a Microsoft server.</p><p>Technical Approach Considerations Software design will be done using PHP/MySQL as the base language. The project will have a number of components, including database design and population, HTML design, graphic design, and application code design.</p><p>Team members will be assigned for each component of the project and will primarily be responsible for the completion of that component of the project. The team leader may decide to assign other duties to team members beyond their area of expertise, but primarily each team member will do most of his or her work in one or two areas of specialization.</p><p>Testing Requirements Considerations Quality assurance is not only important; it is an integral step of the software development process. In order to assure quality in the software products, testing will be performed according to the degrees of the testing pyramid, as shown in Figure 3 on the following page.</p><p>Page 7 Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p>Usability Testing</p><p>Stress (Performance & Load) Testing</p><p>Diagnostic Testing (“Boundary” or “Negative” Testing)</p><p>“Good Path” or “Positive” Functional Testing</p><p>Install Testing</p><p>Development (Unit) Testing</p><p>Figure 3: Degrees of Testing</p><p>This project follows the testing pyramid as follows:  As development progresses, individual team members will test small chunks of code as they write them. This step is shown at the bottom of the pyramid as development or unit testing.  Next, builds of the product shall be created and installed onto the target system and tested for installation failures.  The next step is “good path” or “positive” functional testing. In this step of the pyramid, the tester exposes the application to expected inputs and verifies that the expected outputs are achieved. This includes such things as clicking a link and making sure that the appropriate page is displayed.  The fourth step in the testing pyramid is diagnostic testing, which is commonly referred to as boundary or negative testing. In this approach, unexpected inputs are applied to the application (such as entering character data in a field that expects numbers) to make sure that the application can recover gracefully from such errors.  The next step of the testing pyramid does not really apply to this project. Stress testing involves engaging the server in a multitude of requests to verify that it can keep up with a high load. Because the project has a relatively small user base (ACS), this should not be an issue. This step would become increasingly necessary if large-scale commercialization were to be seriously considered.  The last step of the testing pyramid is usability testing, which involves a high- level walkthrough of the application to see if there are areas that could be improved from a usability standpoint.</p><p>The testing methodology will include a test plan where members will test other members’ components. Better testing is accomplished if an independent person tests the software that he or she was not involved in creating. A metaphor for this statement is an audit firm that independently verifies the accounting practices of a corporation. Only by employing an independent test group can excellent quality be assured.</p><p>Page 8 Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p>Overall and most important, the software will be tested for functionality, reliability, and ease of use. Group members will initially test the USA software. People outside the group will conduct further testing, preferably ACS teachers and instructors. Finally, third through sixth grade students will test the software. The system will be evaluated by feedback from students and teachers.</p><p>Security Considerations There shall be measures taken during the course of the project to ensure that no security concerns arise. This consideration is accomplished by being open and transparent with the client, ACS, to ensure the best education for third through sixth grade students in Iowa. The client has no competitor, thus there is little possibility of a security breach for the client to worry about.</p><p>There is a security consideration related to the operation of the end project. Since all the answers to the examination questions are contained in the server database, security measures must be taken to ensure that students do not gain illegal access to the database.</p><p>Intellectual Property Considerations ACS does not have any intellectual property considerations. Application code belongs to the authors of the team. The source information used for the geography has been acknowledged and approved for use. However, the character of Uncle Sam for the application will be verified as public domain before use.</p><p>Commercialization Considerations There is no intention of commercialization at this point, thus there is no impact on project activities. Commercialization may be considered at a later date depending upon the quality of the results. The end product is a copyright of Iowa State University.</p><p>Possible Risks and Risk Management Below are seven major issues/risks that represent possible setbacks that could occur in the course of the project’s lifetime:  Risk: Due to unforeseen circumstances, a group member leaves the project. Mitigation: The team has four members, so in the event that a team member is lost, the remaining members will shoulder the increased workload. If the person leaving were a critical member, the team would work with him/her to ensure that his/her knowledge and responsibilities were adequately disseminated among the remaining group members. If more than one group member must leave the team, the team will decide whether a member from another project group could volunteer for double duty with or switch groups all together to maintain proper productivity levels.  Risk: The PC with the project’s software is stolen, it crashes, or the software is maliciously tampered with or otherwise modified. Mitigation: Since the project is entirely software, it is imperative that the source files are kept secure. In addition to limiting access to the machine to</p><p>Page 9 Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p>Ongo8 group members via user permissions on the Linux box, the source code and databases shall be backed up regularly.  Risk: An update to the software makes it cease to function correctly. Mitigation: Backups will be made of the incomplete but functional software so that a running version of the software is always available. The source code and databases will be assigned version numbers with notes on their capabilities in a file accessible to all group members.  Risk: The clients at the ACS request certain elements of the software implemented differently or want additional functionality not originally specified. Mitigation: The group will make an effort to keep members of the ACS informed with the progress and abilities of the project. ACS is currently satisfied with the direction and feature set of the proposed and partially implemented software. Additional requests will be considered and fulfilled if the project leader deems enough time exists to add the requested parts while still maintaining enough time for quality control, testing, and debugging.  Risk: There is a loss of contacts at ACS. The current contacts might retire or change jobs and be replaced by new personnel. Mitigation: The group will need to involve the new personnel or maybe even new instructors in the project. Other schools could be approached for help if necessary.  Risk: The technical approach fails. Mitigation: The group will need to determine cause of failure and redefine the technical approach to compensate. If the failure is due to server problems, other server platforms can be investigated. If a web solution is not adequate, other options can be explored such as integrating individually installed software packages on Windows-only machines capable of running VB.  Risk: The testing methods fail. Mitigation: The group will need to determine the cause of the failure and redesign the test scripts accordingly. Part of the solution might require the group to write inline scripts to monitor the health and status of the program for further in-depth testing. The group might also need to write additional scripts that can help monitor the performance of the software from the viewpoint of client machines.</p><p>Proposed Milestones and Evaluation Criteria The following table is a list of proposed milestones for the project and its current status, following its status from the previous semester. Evaluation of the current status results in one of the following: greatly exceeded, exceeded, met, almost met, partially met, did not meet, did not attempt. “Did not attempt” means the work towards the milestone has not yet begun.</p><p>Page 10 Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p>Table 2: Milestones and Current Status Current Rating Milestone Importance Product (Score) Project definition Met (100%) 10% 10% Technology selection Met (100%) 8% 8% PHP/MySQL education Partially Met (100%) 5% 5% Database population Almost Met (95%) 10% 9.5% Base software coding Partially Met (80%) 10% 8% Base development testing Partially Met (80%) 5% 4.5% Advanced features coding Did not attempt (0%) 10% 0% Advanced features testing Did not attempt (0%) 5% 0% Installation and testing Partially Met (80%) 5% 4% Functional testing Partially Met (85%) 5% 4.25% Client testing Did not attempt (0%) 5% 0% Client demonstration Did not attempt (0%) 5% 0% Industrial review panel 5% 0% Did not attempt (0%) demonstration Project plan Met (100%) 4% 4% Project poster Did Not Attempt (0%) 4% 0% Status report Did Not Attempt (0%) 4% 0% Total 100% 57.25%</p><p>The success of the aforementioned milestones will be evaluated throughout the project based upon timeliness, thoroughness, overall cost, and functionality. The milestones will be assigned an evaluation mechanism and a team member to evaluate the performance and define what constitutes success.</p><p>Project Tracking Procedures Meeting the project requirements, keeping the project on schedule, and keeping it within the budget are three of the critical elements for project success. Having a good forecast or estimate for each of these three items is essential, as is knowledge of where the project is with respect to the schedule or estimate. This project’s approved tracking procedure involves the creation and maintenance of a Gantt chart for the schedule and tables to track personnel effort, miscellaneous required resources, and financial resources. These items are described in more detail later in this plan. Other tracking procedures include reviews of the project on a weekly basis by e-mail reports and weekly meetings with team advisors.</p><p>Statement of Work The statement of work is based upon the semester milestones for this project. Five tasks have been defined below to illustrate how the project is being conducted.</p><p>Task 1 - Problem Definition Subtask 1a: Problem Definition Completion</p><p>Page 11 Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p>Objective: To clearly define the two separate components of the problem: general problem statement and general solution-approach statement. Approach: The problem definition from previous Ongo8c project plans was reviewed, and changes were made according to the new requirements. Results: The revised problem definition is stated earlier in this project plan.</p><p>Task 2 – Application Development Subtask 2a: PHP/MySQL Education Objective: To educate group members about the technologies involved in this project. Approach: Two short seminars shall be conducted to instruct members about PHP and MySQL as they pertain to project requirements. Results: Group members will acquire the minimum skills to successfully meet the requirements.</p><p>Subtask 2b: Coding Objective: To begin development of the software application. Approach: Individual tasks shall be assigned and coding shall occur that meets the requirements listed previously. Results: The software application will progress towards its finished state.</p><p>Task 3 - Project Testing Subtask 3a: Development Testing Objective: To test the small chunks of code for errors. Approach: As development progresses, individual team members will test small chunks of code as they are written. Results: Individual components of the code should have few errors.</p><p>Subtask 3b: Installation Testing Objective: To test the installation of the code. Approach: The project installation shall be tested for quality and overall successfulness. Results: The program installation shall be tested for errors.</p><p>Subtask 3c: Functional Testing Objective: To test the expected inputs and outputs of the program. Approach: The code shall be tested by exposure to proper inputs and verifying that the expected outputs are achieved. Results: The program shall output correctly according to the inputs.</p><p>Task 4 - Project Demonstration Subtask 4a: Class Presentation Objective: To demonstrate the project to the Senior Design class Approach: There shall be discussion, coordination, and practice among all team members and meetings with the course coordinator and faculty</p><p>Page 12 Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p> advisors. The PowerPoint slides from the previous semester will be reviewed and a new set of slides produced. Results: There shall be an in-class presentation using PowerPoint slides.</p><p>Subtask 4b: Client Demonstration Objective: To demonstrate the end-product to the client, ACS Approach: There shall be discussion, coordination, and practice among all team members and meetings with the course coordinator and faculty advisors. Results: There shall be an on-site demonstration to the client.</p><p>Subtask 4c: Industrial Review Panel Objective: To demonstrate the end-product to the industrial review panel Approach: There shall be discussion, coordination, and practice among all team members and meetings with the course coordinator and faculty advisors. Results: There shall be an oral presentation to the panel.</p><p>Task 5 - Project Reporting Subtask 5a: Project Plan Objective: The basis for conducting the project, providing a checklist to ensure that the project accomplishes what it was supposed to achieve within its approved schedule and financial budget. Approach: An idea of what needs to be done was gained from reading previous project plans, followed by a discussion with the project team and faculty advisors. Also, the criteria for the project plan as listed in the senior design notes packet was analyzed and met by coordinating with other group members. Result: A well-documented semester plan was generated that meets its objective.</p><p>Subtask 5b: Project Poster Objective: A large, single sheet that describes the project and exhibits its high quality. Approach: Reading previous projects posters and analyzing award-winning posters from previous years will generate ideas, as well as discussing and coordinating with the team. Results: A full-color, descriptive and professional-looking project poster shall be generated.</p><p>Subtask 5c: Status Report Objective: Reports the status and progress for the project and its end product. It summarizes the results of the project to date, remaining work to be done, and forecasts project completion. Approach: As stated in the senior design requirements packet, the status report is generally an update of the previous status report, so the previous</p><p>Page 13 Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p> status report shall be reviewed and updates made in the form of the new status report. It shall also document the research, thought, and effort that have been accomplished. Results: A well-documented status report shall be generated.</p><p>Subtask 5d: Weekly Email Reporting Objective: To review the progress of each team member related to the projects, the team’s recent accomplishments, its planned near-term activities, its resource utilization, and any outstanding problems. A second objective is to ensure that all members of the team, the client, the team’s faculty advisors, and the course coordinator are aware of this same information. Approach: Input from each team member shall be sent to the communications coordinator that meets the first objective above. Results: A weekly email report to all the people involved in the project shall be delivered. Estimated Resources and Schedule This section includes estimates of project resources and the project schedule.</p><p>Estimated Resource Requirements The estimated resource requirements section is composed of the following three components: personnel effort requirements, other resource requirements, and financial requirements.</p><p>Personnel Effort Requirements The table below shows the estimated effort given by each team member during the spring 2004 semester. The team leader will monitor time expenditures and adjust member assignments to try to maintain equality. The attributes of the table and their descriptions include:  Class: Hours spent attending class lectures  Meetings: Hours spent attending weekly advising meeting as well as smaller group meetings  Presentation: Hours spent working on the industrial review panel presentation and client demonstration. Effort includes preparing, practicing, and delivering the presentation.  Research: Hours spent conducting research for the project.  Documentation: Hours spent working on the project plan, project poster, project status report, and weekly project updates.  Coding: Hours spent working on the actual development of the application. An example of coding is populating the USA database.  Overall: Total hours spent by each team member</p><p>Page 14 Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p>Table 3: Estimated Personnel Effort (Hours)</p><p>Member Class Meetings Presentation Research Documentation Coding Overall Schwenker 15 32 6 18 8 25 104 , David Sailer, 15 32 6 18 8 20 99 Robert Russell, 15 30 6 20 14 13 96 Jeffrey Berg, 15 28 6 20 16 13 98 Dimitry Totals 60 122 24 76 46 71 399</p><p>Other Required Resources The table below shows the estimates of other required resources during the spring 2004 semester. “Other required resources” include items such as parts and materials required to conduct the project. The attributes of the table and their descriptions include:  Resource: A description of the resource  Team Hours: Total team hours dedicated to the resource  Other Hours: Non-team hours dedicated to the resource  Cost: Cost of the resource, not including man-hours</p><p>Table 4: Other Required Resources</p><p>Resource Team Hours Other Hours Cost Design and Printing of Project Poster 10 0 $45.00 Totals 10 0 $45.00</p><p>Financial Requirements The table below shows the estimated financial budget during the spring 2004 semester. The budget includes items such as parts and materials required to conduct the project, and also estimated labor costs based upon departmental senior undergraduate wages. The attributes of the table and their descriptions include:  Item: A description of the item grouped into the categories of parts and materials and labor  W/O Labor: Cost of the item not figuring in labor charges  With Labor: Cost of the item figuring in labor charges</p><p>Page 15 Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p>Table 5: Estimated Financial Budget Fall 2004</p><p>Item W/O Labor With Labor Parts and Materials Poster $45.00 $45.00 Miscellaneous Binding $5.00 $5.00 Copying $10.00 $10.00 Subtotal $60.00 $60.00 Labor at $10.50 per hour Schwenker, David $1092.00 Sailer, Robert $1039.50 Russell, Jeffrey $1029.00 Berg, Dimitry $1029.00 Subtotal $4231.50 Total $60.00 $4189.5</p><p>Table 6: Estimated Financial Budget Spring 2004</p><p>Item W/O Labor With Labor Parts and Materials Poster $45.00 $45.00 Miscellaneous Binding $5.00 $5.00 Copying $10.00 $10.00 Subtotal $60.00 $60.00 Labor at $10.50 per hour Low, Li-Wei $1113.00 Longoria, Laura $1008.00 Schwenker, David $1081.50 Sailer, Robert $1029.00 Subtotal $4231.50 Total $60.00 $4291.50</p><p>Table 7: Estimated Financial Budget Fall 2003</p><p>Item W/O Labor With Labor Parts and Materials Poster $45.00 $45.00 Miscellaneous Binding $5.00 $5.00 Copying $10.00 $10.00 Subtotal $60.00 $60.00 Labor at $10.50 per hour Tan, Ricky $1270.50 Longoria, Laura $1270.50 Low, Li-Wei $1270.50 Subtotal $3,811.50 Total $60.00 $3,871.50</p><p>Page 16 Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p>Schedule Figure 4 shows a timeline of events for Ongo8c. This chart will serve as a guideline for overall project progress. Several elements run simultaneously, such as coding and development testing. Figure 4: Schedule</p><p>Page 17 Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p>Conclusion This section includes project team information, a project summary, and the project references.</p><p>Project Team Information Client Information Ames Community Schools Administrative Offices 1921 Ames High Drive Ames, IA 50010 Phone: 515-268-6600</p><p>Faculty Advisor Information Dr. John Lamont Professor Ralph Patterson, III 324 Town Engineering 326 Town Engineering Ames, IA 50011-3230 Ames, IA 50011-3230 Phone: 515-294-3600 Phone: 515-294-2428 Fax: 515-294-6760 Fax: 515-294-6760 [email protected] [email protected]</p><p>Team Member Information CprE/EE 491 Member Jeff Russell Dimitry Berg Computer Engineering Computer Engineering 1713 Amherst Dr. 2407 Knapp St. Ames, IA 50014 Ames, IA 50014 515-292-2526 515-451-9383 [email protected] [email protected] CprE/EE 492 Members David Schwenker Robert Sailer Computer Engineering Electrical Engineering 3105 Woodland St 2902 Lincoln Way Ames, IA 50014 Ames, IA 50014 515-268-4288 712-251-3916 [email protected] [email protected]</p><p>Page 18 Ongo8c Project Plan CprE/EE 491 Revision 1.0</p><p>Summary Test results and discussions with ACS teachers have shown that additional resources are needed to boost the district’s performance in the problem solving sections of standardized tests. This project will provide the supplementary instruction and drills that ACS students need to meet and exceed the goals of the school and the community. Since the software is platform independent, it will be accessible by all computers with an Internet connection. The statistical analysis modules will provide invaluable insight to the teachers and administrators by highlighting the strengths and weaknesses of the students.</p><p>ACS teachers have pinpointed a need for geographic help for students in grades three through six. The program will allow students to “travel” around the United States, learning facts about the states and territories along the way. Math problem solving will also be incorporated into this program wherever possible. </p><p>References The following references were, or will be, utilized by the Ongo8c team:  ACS teachers and administration  Iowa State University Department of Education  Des Moines Public Schools Policies  Dike-New Hartford Community School District Policies  US World Almanac  United States Official Websites</p><p>Page 19</p>