C1­ Informal Specification of Requirements
Acadia University ­ Comp 3663
“Rod & Reel 2007”
OutSource Inc. ­ Group A
January 21, 2007
Mike Mallinson ­ 100071936
Billy Logan ­ 100059371l
Richard Peters ­ 100071545
About Us
OutSource Inc. is a respected software development and IT consulting firm. With over 10 years experience in the IT world, we are one of the leaders in our field. Although we do software development in­house, we also outsource some projects to other companies who we know will complete the project to our standards.
Overview
We'd like to have a fishing role playing game created named “Rod & Reel 2007”, in which the user must try to make as much money as possible within a set number of days. This is done by catching and selling fish.
Basic Requirements
•
•
•
•
•
•
•
•
•
Must have at least five locations. The base location where the character begins is a tackle shop. The remainder of the locations are places where the character may fish. The tackle shop is the gateway to all other locations. The user cannot travel from one fishing area directly to another fishing area. They must always return to the tackle shop to sell off their current catch before proceeding to another location.
When changing locations a set amount of time should pass.
Each fishing area has a different difficulty. This difficulty affects the strength of the fish and the type of bait that works best for them. Harder areas require stronger fishing line, rods and more expensive bait. The naming of the locations should indicate which locations are easier and harder. For instance, the location named “the goldfish pond” would be an easy location.
Each fishing location should have another character present which the user can talk with, to learn about the fish in that particular location.
When at a fishing location the user should have the options to “cast”, “return to tackle shop”, and “talk to character”.
When the fish option is pressed it may take some time before a bite on the line is received depending on the type of bait used and the time of day.
The fishing portion of the game should consist of a tension meter and an indicator of the strength left in the fish. The meters can be animated or just text percentages that change. To fish the user should press and hold a button called reel which decreases the strength of the fish as well as increases the tension on the rod. When the tension on the rod reaches 100% the line snaps and the fish is lost. When the strength of the fish reaches 0% the fish has been caught.
The tackle shop has a store clerk that can be interacted with to purchase rods, line and gear. When the game begins you start with a small amount of money to purchase a rod, line and bait from the store. This should allow the user to customize their character through •
•
•
•
•
•
•
purchasing gear of their choosing.
In the initial game settings the user should be able to choose how many days they'd like to play for.
The time of day should affect how often fish bite on the line. Sunrise and dusk are the best time to catch fish.
Should only allow the user to fish from 7:00 am until 7:00 pm which is considered one day.
Alert the user when nearing the end of the last day and when bait runs low.
At the end of the game summarize all the fish caught, money earned, money spent and remaining money.
A scoreboard of high results is preferred but is not required.
A method for saving and loading games must be available.
Human Interface Requirements
•
•
Must be GUI based with efficient use of mouse point and click and menu features.
Must be user friendly and encourage player/game setup and interaction by providing, at minimum: •
Cut and paste and document content copying where possible to reduce repetitive typing. •
Intelligent display and sequencing of queries and menus. •
User oriented error and warning messages. •
On­line help information. Basic Non­functional Requirements
•
•
•
Must run on any Acadia Advantage laptop under Windows XP.
Is implemented in Java.
Can be downloaded and installed from a web homepage.
Undesirable Characteristics
•
•
Lengthy user manual ­ focus on great on­line help and reference documentation as well as innovative "getting started" tutorial. Ask yourself, how would I like to learn how to use the system.
Need for external components such as backup utility or DBMS that might have to be purchased by your customer.
Cost and Time Constraints
•
•
Deliverables must be received on time. No deliverable can be accepted before a previous deliverable has been received and approved.
The entire project must cost no more than 35 man­days (at 8 hours/day).