Phases
- requirements
- analysis
- design
- development
- testing
- deployment
- workflow
- access control
How To...
Projects
start a project
Requirements
add a requirement
Use-Cases
add a use-case
Designs
add a design
Coding
check for new tasks
enter initial estimate
revise an estimate
revise task status
finish a task
generate a burn-down chart
generate a gantt chart
Testing
add a test plan
add a defect
Deployment
complete a release
Nuts and Bolts of Adding a Requirement
- click on the requirements link under the workspace
- click the Add button
- fill out the form
- requirement type is important because it helps you understand the context of the description
- code is important because that will appear in the drop downs for anything that relates to your requirement
- user is important as that identifies you the requirement creator
- keywords are important to have your requirement appear in search results
- importance is important as it helps you prioritize
- you must associate this requirement with a release
- sequence is important because it gives order to the requirements
- the description is where you actually state the requirement
- click the Add button
- click the display link
- click the Hierarchy link
- click the Add button
- fill out the form
- either select a currently existing need or click the New Need link
- fill out all fields
- chat room isn't necessary
- click the Add button
- click the ReqPersona link in the Recently Visited box
- either select a currently existing persona or click the New Persona link
- fill out all fields
- click the Add button
- click the ReqPersona link in the Recently Visited box
- select the relevant importance
- select the newly created requirement
- click the add button
Questions?
You might find some real time human help in the Code Roller Chat Room.