I. Introduction
| A. Information System: | Olympic Information Database |
| B. Group Weekly Meeting Time: | Thursdays 2:00PM - 3:15PM |
| C. Document Format: | All documents shall follow the same template and design which will be posted online. |
II. Group Members and Roles
| A. Project Manager: | John Zenger - [email protected]
John’s job as project manager is to keep the group interested and active on the project. He needs to be a good communicator for thoughts within the group or ideas which could improve the overall project. |
| B. Technical Writer: | Rob Hagan - [email protected]
Rob’s duties as technical writer are to coordinate, design and write the group’s documents throughout the project. He must be up to date with his formal writing skills and must work closely with the web master to keep the web page updated. |
| C. Programmer: | Rob Hagan - [email protected]
As programmer, Rob encodes the system into programming language for actual use. His problem solving skills must be acute. |
| D. Quality Assurance: | Tim Hodges - [email protected]
Tim’s responsibilities as our quality assurance man is to proof read all completed group documents for grammar, spelling, or any other errors they might contain. He needs to be quick and accurate in his assessments so that corrections can be made well ahead of the assignment due dates. |
| E. Model Architect: | George McMonigole - [email protected]
Being the model architect, Scott must prepare all designs for the different aspects of the system. His designs are crucial since they will be the models our group goes by for all stages of developing our system. |
| F. Web Master: | Brenda Ley - [email protected]
Brenda will be taking care of our group’s web page. She will be updating our online documents as we design new versions of them and creating an overall appealing web site for any of our visitors interested in the system. |
III. Feasibility Analysis
| A. External Inputs: | 1. Input Screens - complex
2. Data updates following events - average |
| B. External Outputs: | 1. Display of medals table - simple
2. Display of athlete profile - simple 3. Display of statistics by country/athlete/event - simple 4. Display of relevant information (weather) - average |
| C. External Inquiries: | 1. Committee wanting reports on athletes - simple
2. User touching kiosk screen - simple |
| D. Logical Internal Files: | 1. Athlete database - simple
2. Event database - simple 3. Medal database - simple 4. Historical database - simple 5. Relevant information (weather, re-scheduling) - complex |
| E. External Interface | None |
IV. Systems Descriptions
A. The problem we are addressing at Worldwide Sports Incorporated is to create a sports information system for the Olympic Games in Tampa in 2012. This system will contain all the pertinent information regarding the Olympic events, medals won, up to date winners and losers of the events, and any breaking information surrounding the athletes.
B. The information system we are designing is a sports information system, concentrating on a simple interface with the user, so that they may have our whole database of Olympic information at their fingertips. The system will be easy to use for both the users of the information and the persons keeping the data current.
C. To solve the problem we are facing, we will be designing all aspects
of the system and keeping them posted online at our web site: http://soleil.acomp.usf.edu/~bley/ism_3113.html
The goals of our company are to create the best sports information system
on the best budget possible.
This web site was created for a systems analysis class (ism 3113). It is intended for educational purposes only.