1. RUP Implementation and Testing
RUP Artifacts and Deliverables
RUP Implementation Workflow
RUP Test Workflow

2. Implementation Workflow

3. Structure Implementation Model Workflow

4. Structure Implementation Model - Purpose
The purpose of this workflow detail is to ensure that the implementation model is organized in such away as to make the development of components and the build process as conflict-free as possible.

5. Structure Implementation Model - Staffing
Architect has primary responsibility for the structure of the implementation model
Architect's experience needs to include that of an integrator at the system level.
Architect needs experience in software build management, configuration management, and experience in the programming language in which the components to be integrated are written

6. SAD Component Diagram

7. Implementation Workflow

8. Plan Integration Workflow

9. Plan Integration - Purpose
Plan which subsystems should be implemented, and the order in which the subsystems should be integrated in the current iteration.

10. Plan Integration - Staffing
Integration is typically carried out by a single person (for a small project on which the build process in simple) or a small team (for a large project on which the build process is complex).
Integrators need experience in software build management, configuration management, and experience in the programming language in which the components to be integrated are written.
Because integration often involves a high degree of automation, expertise in operating system shell or scripting languages and tools like 'make' (on Unix) is also essential.

11. Integration Build Plan
Shows Subsystems, Processes and Components Implemented in a Release
Shows Use Case Realizations, Subsystems and Components Implemented in Each Build of the Release

12. Implementation Workflow

13. Implement Component Workflow

14. Implement Component - Purpose
The implementers write source code, adapt existing components, compile, link and perform unit tests, as they implement the classes in the design model.
If defects in the design are discovered, the implementer submits rework feedback on the design.
The implementers also fix code defects and perform unit tests to verify the changes.
Then the code is reviewed to evaluate quality and compliance with the Programming Guidelines.

15. Implement Component - Staffing
These activities carried out by the implementer tend to be done by a single person.
The review activity is best carried out by a small team staffed by cross-functional team members, typically more senior members of technical staff with greater experience into common problems and pitfalls encountered in the programming language.
Special expertise may be required in the problem domain, as is often the case in systems involving telephony or devices with special interfaces.
Expertise in specific algorithms or programming techniques may also be required.

16. Implementation Workflow

17. Integrate Each Subsystem Workflow

18. Integrate Each Subsystem - Purpose
If several implementers work (as a team) in the same implementation subsystem, one of the team should be responsible for integrating the new and changed components from the individual implementers into a new version of the implementation subsystem.
The integration results in series of builds in a subsystem integration workspace. Each build is then integration tested by a tester.
Following testing, the implementation subsystem is delivered into the system integration workspace.

19. Integrate Each Subsystem - Staffing
Integration is typically carried out by a single person (for a small project on which the build process in simple) or a small team (for a large project on which the build process is complex).
The integrators need experience in software build management, configuration management, and experience in the programming language in which the components to be integrated are written.
Because integration often involves a high degree of automation, expertise in operating system shell or scripting languages and tools like 'make' (on Unix) is also essential.

20. Implementation Workflow

21. Integrate System Workflow

22. Integrate System - Purpose
The integrator integrates the system, in accordance with the integration build plan, by adding the delivered implementation subsystems into the system integration workspace and creating builds.
Each build is then integration tested by a tester. After the last increment, the build can be completely system tested by a tester.

23. Integrate System - Staffing
Integration is typically carried out by a single person (for a small project on which the build process in simple) or a small team (for a large project on which the build process is complex).
The integrators need experience in software build management, configuration management, and experience in the programming language in which the components to be integrated are written.
Because integration often involves a high degree of automation, expertise in operating system shell or scripting languages and tools like 'make' (on Unix) is also essential.

24. Implementation Workflow

25. Implementation Activity Overview

26. Implementation Artifact Overview

27. Test Workflow

28. Plan Test Workflow

29. Plan Test - Purpose
The purpose of this workflow detail is to identify and describe the testing that will be implemented and executed.
This is accomplished by generating a test plan which contains the requirements for test and test strategies.
A single test plan may be developed, describing all the different types of tests to be implemented and executed, or one test plan per type of test may be developed. Either is method is acceptable.

30. Plan Test - Staffing
The test designer is the principal worker involved in this workflow detail, with input from the end-user representative(s).

31. Test Plan
Contains testing types such as Data Testing, Function Testing, User Interface Testing, Load Testing, etc. and strategies used for each type
Describes worker and system resources required
Describes testing deliverables such as Test Model, Test Log, Defect Reports, etc.

32. Test Workflow

33. Design Test Workflow

34. Design Test - Purpose
The purpose of this workflow detail is to identify, describe and generate the test model and its reported artifacts (test procedures and test cases).
Design Test is done so the test implementation and execution efforts are efficient and effective.

35. Design Test - Staffing
The test designer is the principle worker involved in this workflow detail, with input from the use-case specifier.

36. Test Workflow

37. Implement Test Workflow

38. Implement Test - Purpose
The purpose of this workflow detail is to implement (record, generate, or program) the test procedures that were defined in Design Test.
The output artifact is a computer readable version of the test procedure, referred to as a test script.
The generation of test scripts can be done within the context of test automation tools or programming environments.

39. Implement Test - Staffing
The test designer uses the test model, and may additionally use the implemented components, to implement the tests.
The test designer also works closely with the Designer and Implementer to ensure that test-specific functions (stubs, drivers, etc.), elements that are not the focus of test, but which the target-of-test interacts with, are being implemented and tested.

40. Test Workflow

41. Evaluate Test Workflow

42. Evaluate Test - Purpose
The purpose of evaluating test is to generate and deliver the test evaluation summary.
This is accomplished by reviewing and evaluating the test results, identifying and logging change requests, and calculating the key measures of test.
The test evaluation summary presents the test results and key measures of test in an organized format and is used to assess the quality of the target-of-test and the quality of the test process.

43. Evaluate Test - Staffing
The test designer is responsible for reviewing and assessing the quality of the target-of-test and the test process.
A familiarity with test metrics and statistics is necessary.

44. Test Workflow

45. Execute Tests in Integration Test Stage – Workflow

46. Execute Tests in Integration Test Stage – Purpose
The purpose of the Integration Test Stage is to ensure that the assembly of the system's components collaborate as intended, as well as that the increment has the right behavior.
The system integrator compiles and links the system in increments.
Each increment needs to go through testing of the functionality that has been added, as well as all tests the previous builds went through (regression tests).

47. Execute Tests in Integration Test Stage – Staffing
The tester is the principle worker involved in this workflow detail, however there is interaction with the implementer and system integrator.
Additionally, if test classes and packages were necessary, there is additional interaction with these workers.

48. Test Workflow

49. Execute Tests in System Test Stage – Workflow

50. Execute Tests in System Test Stage – Purpose
The purpose of the System Test Stage is to ensure that the complete system functions as intended.
The system integrator compiles and links the system in increments.
Each increment needs to go through testing of the functionality that has been added, as well as all tests the previous builds went through (regression tests).
Within an iteration, you will execute system testing several times until the whole system (as defined by the goal of the iteration) functions as intended and meets the test's success or completion criteria.
The output artifact for this activity are the test results.

51. Execute Tests in System Test Stage – Staffing
The tester is the principle worker involved in this workflow detail, however there is interaction with the implementer and system integrator.
Additionally, if test classes and packages were necessary, there is additional interaction with these workers.

52. Test Workflow

53. Test Activity Overview

54. Test Artifact Overview

55. Questions?