Depending on the complexity of the project, its level of criticality and the number of actors, we will plan its number of iterations and each element of them.
This workflow is intended to create a model of the system architecture.
Needs and use cases collection
This workflow is intended to create a clear picture of what the system is intended to accomplish.
This workflow is intended to create a model of the system to be at a level of abstraction where it is not linked to a particular coding language.
This workflow is intended to generate a language specific code from both the analysis results and the architecture findings.
Intended to run the conceived system on its platform.
To test the system at various levels - e.g. component test, integration test, system test and finally acceptance test.
This phase is intended to deploy the application and tackle intrinsic aspects of this phase -e.g. fail-over procedures, load balancing, ...
Change and configuration management
This workflow is intended to tackle the change factor during the project and integrate it efficiently inside the loops of a project.