-
Notifications
You must be signed in to change notification settings - Fork 0
Technical Specifications Studio
Describe what the specification is about and give a summary of the technical implications.
This should cover the why: why is this change being proposed or feature being implemented. This should not simply state "because the user wants it". If it's a user requirement, it should describe the user's rationale.
Describe simply who is doing what and how to obtain the result.
| # | Who | What | How | Result |
|---|---|---|---|---|
| 1 | ||||
| 2 | ||||
| ... |
Affected technical material.
This section should describe a plan of action (the "how") to implement the changes discussed.
How can the feature be tested or demonstrated. It is important to describe this in fairly great details so anyone can perform the demo or test.
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.