Campus Locator – Definition Phase (May04-04) Iowa State University, being a large campus, would do well to implement an on-campus locator system. Right now it is very up in the air regarding how this system would take shape. Some factors include who would use it, how it could be used, and what hardware would be necessary. Because there are so many considerations, a senior design team, familiar with the process of software engineering, has been chosen to study the feasibility of such a system. They plan to thoroughly investigate all possible users and uses of an on-campus locator system, by first researching possible interested groups, and then interviewing representatives from those groups. Based on the interviewees input, the team’s own opinions and experiences, and research on various types of hardware, the team will prepare two reports on their findings. Each will be written for a different audience and have different purposes. The first, a proposal report, will be targeted at an administrative audience, to explain the system to them. The other, a specifications report, is aimed at the team that actually designs the system. Abstract Acknowledgements Our team would like to acknowledge the initial work which was performed on the project by a previous team, as well as the guidance and support provided by Dr. Lamont and Prof. Patterson. We would also like to thank the groups and individuals on campus who are providing the project with invaluable information. Problem Statement This team has been tasked with designing an on-campus locator system.  This system will be composed of -- but not limited to -- several main features.  These include on-campus route finding, location identification and information, and predefined tours.  The delivery may include any of several mediums; these include PDAs, desktop computers, and stand-alone kiosks. A formal study of the requirements of such a system must first be completed.  The team must use the knowledge of software engineering and the requirements process to elaborate and specify the design of a locator system.  Additionally, possible clients and sponsors will be interviewed to determine the most likely use-cases as well as to discover new possibilities for implementation.  The most likely solutions, whether they be hardware or software oriented, will be investigated and their respective advantages and disadvantages weighed for the final specifications document. General Problem Solution Approach Users and Uses Matrix The table below shows a preliminary list of users and intended uses of the campus locator. This list is by no means complete, and will grow throughout the definition phase. Below are listed the Assumptions for the end products of the definition phase: There is an interest in implementing an on-campus locator system from one or more campus groups Future funding will make it possible to implement the system The readers of both reports will be able to read English Other senior design teams will come after this team to carry on the actual implementation Below are listed the Limitations for the end products of the definition phase: The future teams must be skilled in the language and principles of software engineering The implementation recommendations must consider the limited financial resources of future teams Data updatability must be accounted for in all recommendations made during the definition phase All research must be completed and documented by May 2004 Assumptions and Limitations Operating Environment The operating environment of the Campus Locator will include, but is not limited to the following: World Wide Web Server Personal Digital Assistant (PDA) Kiosks (Currently have for Access+) CD-ROM Outdoor Permanent Displays Project Requirements Proposed Approach For the definition phase, the team will collect data from a variety of sources concerning a variety of technologies, uses, and other implementations.  These sources will include brainstorming sessions, interviews with possible clients, online sources, and personal experience.  The data will be run through a review process to determine the best options available for the Locater project.  The end result will be a specifications document, as previously described. Design Objectives Build the system as cost efficiently as possible The system must be easily maintainable Must be easy to use quickly Must be easy to learn quickly Functional Requirements Mapping Route Finding Building/Room Finding Design Constraints There will be a limited amount of financial resources dedicated to the project Weather issues for outdoors parts of the system Measurable Milestones Interviews Scheduled Interviews Completed Follow-up Contacts Requirements Document/Final Report Special Thanks to Jason McElhiney for use of his Dell Axim in this prototype screenshot Technologies Considered During the definition phase, the team indends to make use of some of the technological candidates for the Locater project for evaluation purposes.  These may include various positioning equipment, PDA or computer hardware, andsoftware packages.  Additionally, recording equipment will be used in interview portions of the project. The end product of this team's project will consist of a specifications document for another senior design project.  This document will describe in detail the recommended course of action for creating a practical, useful Campus Locator Project using the most appropriate hardware, software, and logistical means available.  It will also include all data considered by this team during its research, as well as information which may be useful: client interview excerpts, any pseudocode or algorithms, and alternate product information. Defininition Phase End Product Testing Considerations When evaluating methods and technologies, certain things will be taken into consideration.  Cost to purchase or implement, difficulty to implement, reliability in various operating environments, practicality, and overall utility towards the project's goals are all such points of consideration.  Others may be added as research progresses and the options become more clear. Iowa State University Senior Design Client Project Schedule This team's work, fully researching and specifying the needs of the on-campus locator system, is very important for long-term success. Without a far-reaching study into the requirements of the system, it will not benefit as many end users. It is also crucial that this system has the support of ISU administration, hence the need for the proposal report to really sell the idea.  Finally, the need for the requirements document for the implementation team is substantial, because engineers need to talk to engineers in their own language. The current team will take the needs and wants of the end users, and turn that into a blueprint for a functioning system. The teams plan is to talk to interested groups, research hardware/software for implementation, and select an approach for the final specifications document.  They will also create a proposal report to sell the locator system ideas to a non-technical audience. Closing Summary Dr. John Lamont Prof. Ralph Patterson III Faculty Advisors Team Members All team members are Computer Engineers