Requirements Types for IGSTK
From IGSTK
Requirements Types for IGSTK
In the January review meetings the team agreed on three general requirements types:
- (Application) Requirements - these requirements are provided by end users of IGSTK-based applications
- Style Guidelines - these document developer "best practices", including recommended design constraints (e.g. "8 methods per class"), coding conventions (from the style guide), or implementations of specific design patterns (e.g. IoC type 2 "SetLogger").
- Design Guidelines - these derive from the needs of the architecture itself. These will help document and describe the architectural metaphors for the system. Expect a fair amount of documentation on infrastructure classes such as Spatial Objects, Events, and State Machines.
This is merely a starting point for understanding different categories of requirements. In keeping with an Agile approach, we started with the simplest model, and will "refactor" as needed.
We should always keep in mind that we are developing a toolkit for a community of developers trying to build robust applications in a complex environment. We should seek the feedback and validation of that community whenever and wherever possible. We must also identify situations where decisions are made that have their roots all the way back to the application layer - in which case we should get the validation of domain experts.
The original requirements categorized in the above fashion can be viewed in
