This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Tooling Project Role Descriptions"
Jump to navigation
Jump to search
(Created page with "Tooling development projects have a set of deliverables that may require a range of skills, not necessarily all available in a single individual. The following table identifies ...") |
|||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Tooling development projects have a set of deliverables that may require a range of skills, not necessarily all available in a single individual. The following table identifies the roles, the needed skills and the deliverables that each role should be responsible for. | Tooling development projects have a set of deliverables that may require a range of skills, not necessarily all available in a single individual. The following table identifies the roles, the needed skills and the deliverables that each role should be responsible for. | ||
| + | <table border=1> | ||
| + | |||
| + | <tr><td> '''Role Name''' </td><td> Skillset </td><td>Deliverables</td></tr> | ||
| + | <tr><td>Software Developer</td><td>Programming expertise in the chosen technology</td><td>Software Code (deployed ready for testing)</td></tr> | ||
| + | <tr><td>Solution Architect</td><td>Architectural expertise encompassing business, information, application and technology</td><td>Overarching solution design including data and software component structure and interfaces</td></tr> | ||
| + | <tr><td>Requirements Documenter</td><td>Written communication skills and relevant domain experience</td><td>Informal functional and non-functional requirements</td></tr> | ||
| + | <tr><td>Systems Analyst</td><td>Written communication skills and relevant domain and methodology experience</td><td>Formal requirements documentation such as use cases, data models, etc.</td></tr> | ||
| + | <tr><td>Software Documenter</td><td>Written communication skills and relevant domain and methodology experience</td><td>Software System and User Documentation</td></tr> | ||
| + | <tr><td>Testing Manager</td><td>Written communication skills and relevant domain and thechodology experience</td><td>Test plans, test cases and test script management</td></tr> | ||
| + | <tr><td>Test Case Developer</td><td>Written communication skills and relevant domain and methodology experience</td><td>Test Cases and Test Scripts</td></tr> | ||
| + | <tr><td>Testers</td><td>Relevant domain and methodology experience</td><td>Tested software releases</td></tr> | ||
| + | |||
| + | </table> | ||
| + | [[Tooling Work Group|back to Tooling main page]] | ||
Latest revision as of 19:29, 3 February 2012
Tooling development projects have a set of deliverables that may require a range of skills, not necessarily all available in a single individual. The following table identifies the roles, the needed skills and the deliverables that each role should be responsible for.
| Role Name | Skillset | Deliverables |
| Software Developer | Programming expertise in the chosen technology | Software Code (deployed ready for testing) |
| Solution Architect | Architectural expertise encompassing business, information, application and technology | Overarching solution design including data and software component structure and interfaces |
| Requirements Documenter | Written communication skills and relevant domain experience | Informal functional and non-functional requirements |
| Systems Analyst | Written communication skills and relevant domain and methodology experience | Formal requirements documentation such as use cases, data models, etc. |
| Software Documenter | Written communication skills and relevant domain and methodology experience | Software System and User Documentation |
| Testing Manager | Written communication skills and relevant domain and thechodology experience | Test plans, test cases and test script management |
| Test Case Developer | Written communication skills and relevant domain and methodology experience | Test Cases and Test Scripts |
| Testers | Relevant domain and methodology experience | Tested software releases |
