CisLunarFreighter/UML case diagrams
Use Cases for CisLunarFreighter learning project.
A standard form of use cases have a title, preconditions, steps, postconditions, who benefits.
MUD operator
editInstall the central seed client necessary to coordinate applet activity
Preconditions:
- Seed must work at x level, distribution developed, and tested incrementally so crashes of operator's environment are rare.
- Find or develop Java MUD server and client classes adequate for initial login and security requirements.
- Install and test on project developers servers and machines
- Test it with jFreeRail and CisLunarFreighter applets
- Package the releases for easy install and publish at SourceForge
- Begin modding and importing new applets after rigorous code walkthroughs and testing.
Postconditions:
- Feedback
- Bug reports.
Actors who benefit. Players, Developers, Modders, Mud Operators
Player
editDownload, play, feedback.
Pre Conditions: PreAlpha is ready for incremental testing
- Hear about game environment and decide to try it out
- Download from Sourceforce and install
- Beginner's orientation or interface is intuitive
- Begin playing/learning
- Provide suggestions for gameplay enhancement and bug reports.
Post Conditions: Learned all possible from game or bored with gameplay or community. Feeback processed into environment Bugs fixed or resolved somehow.
Benefits: Players, Developers, Modders, Mud Operators
Modder
editPreconditions:
- Specifications available
- Tools are available (Hence, reliance on free^2 tools and components)
- Source and intermediate data products (3D models) are available
- Downloads and plays / looks over
- Decides to tweak
- Discusses intentions with developers
- Implements and tests
- Submits for developer evaluation
Postconditions:
- Incorporation into baseline product
- Published as tested mod
Benefits: Players, Developers, Modders, Mud Operators