Jeremiah Genest ([info]jeregenest) wrote,
@ 2006-03-28 13:11:00
Previous Entry  Add to memories!  Tell a Friend!  Next Entry
Current mood: frustrated
Entry tags:game design, gaming

Functional Requirements Specifications
So I'm sitting here reading a Functional Requirements Specification for a project I'm on, and I can't help thinking (because to be honest my mind is drifting) that its a pity that rpgs don't come with one of these. Or maybe what I want is a User Requirements document. Or maybe a merge between the two. I know I'd appreciate one of these with HeroQuest (or any other games) as I often wonder just what a certain statement, example or rule was meant to actually do.

Seriously it doesn't need to be a different document but I'd love it if a designer was to break out the following for each aspect of system:


  • Purpose - What the function is intended to accomplish.
  • Input - What inputs will be accepted, in what format the inputs arrive, sources for the inputs, and other input characteristics.
  • Process -The steps to be performed
  • Output


(Post a new comment)


[info]sben
2006-03-28 06:20 pm UTC (link)
Very nice.

This would serve several purposes:

  • Designers could use this to clarify their thinking, and (for example) help make sure they don't forget something over the process of tweaking rules to make them work better in play.

  • Peer review of the rules would be simplified -- reviewers would know how they should pound on a given rule, and might be able to infer situations the designer never thought of.

  • Owners would have a clearer idea of how to modify the ruleset to suit their own needs.


(Reply to this)


Create an Account
Forgot your login?
Login w/ OpenID
English • Español • Deutsch • Русский…