|
Client meeting and Project planning
Before starting the information-gathering stage and project planning, it is necessary to meet the customer and to introduce our company and the way we work.
During this meeting we analyze the needs and problems that the company is having nowadays, we define the steps to follow during the implementation process of the new software and we establish the basis in order to start the development.
Contact references definition
Virtual Mind requires from the customer to assign responsible contact references to have periodical communications. These people should have a complete knowledge of the organization structure and the way it works. It is recommended to have a responsible group composed of 2 or 3 people with time availability and with motivation to participate in the project development.
The possible pre-established communication channels to have a fluid and efficient communication will be the telephone and the internet messengers like Skype or MSN.
Additionally, a system developed by Virtual Mind will be used to track each pending subject, which could be accessed by the client via Internet to know the status of every issue.
Needs analysis
This stage is mainly based on the interaction between Virtual Mind and the client, in order to understand his needs and requirements as much as the business rules he handles.
According to our previous experience and our work methodology, we consider that the analysis and capturing of requirements is a step of great relevance in the project, because this is where the bases for the development are stated. Only if we make an exhaustive analysis, we will be able to reach the best solution that adapts to the case.
Contract sign
Before starting the project, the representative of the client and Virtual Mind must sign a software development contract. This contract will define the requirements (functionalities that will and will not have), a non-disclosure agreement, a software development cooperation contract, payment options, delivery dates, guarantees and training description.
Whit this formality we keep as much the client as the supplier safe with the new project.
Solution design
Once the analysis of the company's requirement is finished, we continue with the technical solution and user interfaces design on the basis of the functional requirements obtained previously.
At this point, the structure of the system will be defined using different design tools, which will allow us to show the client a functional prototype of the product. In this way, the client will be able to make suggestions and commentaries about it, allowing a better appreciation, participation and tracking of the solution that is being developed.
Development / Unit testing
Once the design is finished, all the modules will be developed and all the systems will be integrated, fulfilling the required definitions and specifications. During the course of this stage, the developed modules will be delivered. This is useful for the user to analyze them and to get used to their operation.
Meanwhile, all the required tests will be made, including unit tests, integration tests, security tests and stress tests, ensuring the success of the software delivered.
Training
The training has the primary target of providing the necessary knowledge to work with the system to implement.
Here we try to make every user feel qualified, well trained and confident to use all the product functionalities in the best way.
In addition, the system will include help files where all the common questions and procedure explanations will be detailed. There will be also included user manuals and training courses for any user who wants to feel confident at the time of using the product.
Testing
This stage involves the use of the system under controlled conditions and the following result evaluation. To speak of controlled conditions implies to speak of testing under normal or abnormal conditions.
The Testing oriented to the errors detection must deliberately use erroneous procedures or sequences to verify that the system contemplates all possible inputs without making faults.
Final implementation and project start up
The main intention of this stage is to implement the software and to solve all pending subjects that had been left aside. This phase will change from the testing/QA environment (previous to the production) to real productive system operation.
That is why we will organize the way we will give support to the users for the first critical days of operations and the way we will provide support in the long term.
Ending this phase, users will be able to start working with the software daily in a production environment.
Maintenance
Once the solution is implemented and started being used, new enhancements, requirements and ideas come up to the client to extend the functionality of the system and to take advantage of the information generated on it.
In this stage we will act as consultants to advise about the integration of all new modules required by the user.
|
