4.8 KiB
Each role is defined in (can be downloaded for Faculty computers):
Borges`` ``P.,`` ``Monteiro`` ``P.,`` ``Machado`` ``R.J.`` ``(2012)`` ``Mapping`` ``RUP`` ``Roles`` ``to`` ``Small`` ``Software`` ``Development`` ``Teams.`` ``In:`` ``Biffl`` ``S.,`` ``Winkler`` ``D.,`` ``Bergsmann`` ``J.`` ``(eds)`` ``Software`` ``Quality.`` ``Process`` ``Automation`` ``in`` ``Software`` ``Development.`` ``SWQD`` ``2012.`` ``Lecture`` ``Notes`` ``in`` ``Business`` ``Information`` ``Processing,`` ``vol`` ``94.`` ``Springer,`` ``Berlin,`` ``Heidelberg
More detailed descriptions of roles can be found in books about RUP and in RUP manuals.
- 1x Project Manager.
2x Customer Satisfaction, 1x Schedule&Budget, 1x Team Management
- 1x Process Engineer.
1x Customer Satisfaction, 2x RUP compliance, 1x Team Training
- 2x System analyst.
2x Customer Satisfaction, 1x Communication with Customer, 1x Scope&Use Cases
- 2x Software Architect(+Database designer).
1x Customer Satisfaction, 1x Stack, 1x General architecture, 1x UML
- 1x Integrator.
1x Customer Satisfaction, 1x Code review, 1x Coordination of submodules, 1x API documentation
- 1x System Administrator.
1x Customer Satisfaction, 1x Infrastructure, 2x Deployment
- 1x Test Manager.
1x Customer Satisfaction, 1x System reliability, 1x Test Plan, 1x Manual Tests
- 1x User-interface Designer.
2x Customer Satisfaction, 1x UX design, 1x Usability
- 2x Course developer(+Project reviewer).
1x Customer Satisfaction, 1x User manual, 1x Development documentation, 1x Documentation quality and review
- 2x System tester.
1x Customer Satisfaction, 1x Manual tests, 1x Automatic tests, 1x System reliability
- 2-4x Implementator. Two teams for each of two submodules.
1x Customer Satisfaction, 1x Realization of architecture, 1x Code quality (review), 1x Automatic tests
Total 16-18 persons.
Grading criteria
Up to 5 points per each criteria:
- Customer Satisfaction: subjectively evaluated by Customer
- Schedule&Budget: in time realisation of project phases. Realization of 3 iterations according to prepared schedule (evaluated by Teacher)
- Team Management: Team satisfaction (evaluated by all Team members)
- RUP compliance: Was project performed according to RUP process (evaluated by Teacher)
- Team Training: Organisation of training sessions for Team members (evaluated by all Team members)
- Code review: How much percentage of code was reviewed (1 point per started 20%)
- Coordination of submodules: Whether submodules teams were able to work separately (evaluated by Implementators)
- API documentation: Documentation presence and quality (evaluated by Implementators and Course developers)
- Communication with Customer: Quality and frequency of communication (evaluated by Customer)
- Scope&Use Cases: Presence and quality of documents (evaluated by Software Architects and Course developers)
- Stack: selection and documentation of software stack (evaluated by Integrator)
- General architecture: general description of system structure(evaluated by Integrator and Course developers)
- UML: diagrams presenting operation of main places in the system (evaluated by Implementators)
- Infrastructure: description of required infrastructure and getting access to it (evaluated by Teacher)
- Deployment: whether infrastructure was configured to enable easy deployment of system and documentation of the process (evaluated by Teacher and Integrator)
- System reliability: whether system works without visible errors (evaluated by Customer)
- Test Plan: presence and quality of Test Plan (evaluated by System testers and Course developers)
- Manual Tests: presence and quality of Test Report, conduction of Manual tests (evaluated by Teacher)
- Automatic tests: How much percentage of code is covered by Unit tests (1 point per started 20%)
- UX design: presence, quality and usage of UX design (evaluated by Customer)
- Usability: whether and quality of Usability tests (evaluated by Teacher)
- User manual: presence and quality of User Manual (evaluated by Customer)
- Development documentation: presence and quality of development documentation (evaluated by Integrator)
- Documentation quality and review: general quality of all documentation in project (evaluated by Teacher)
- Realization of architecture: (evaluated by Software Architects)
- Code quality (review): (evaluated by Integrator)
Schedule outline
- Inception: 1 week
- Elaboration: 2 weeks
- Implementation: 2 weeks
- Transition: 1 week