Vecsoft Software acts with project management approach in all of its projects and monitors all processes in digital environment by using various tools or documents in accordance with quality standards. Contract and conceptual design processes are run for each project and all processes are carried out with mutual agreement. Software, project and support teams use Teamwork Project Management application for project, task and support management.
You see below the steps and processes in a standard project in detail.
Project Phases
- Project Engineering ( %10 of Total Project Duration) (PE) Software work and identification of missing/surplus modules.
- Requirements Analysis (%25 of Total Project Duration) (RA) Mutually approved conceptual design document.
- Implementation and Additional Module developmetent (%30 of Total Project Duration) (IM) Uncompleted and untested state of the system./li>
- Customer Test and Approval (%15 of Total Project Duration) (CTA) System installed and tested on customer site.
- Deployment Preparation (%10 of Total Project Duration) (DP) Approved ready to deploy system.
- Deployment Support (%10 Total Project Duration) (DS) Live migration and live operation support.
Project Engineering (PE)
The aim of this phase is to define the project scope, to create an implementation plan, and to prepare a work plan document.
Outputs :
Project Organization Plan : determination of rules, procedures, organizational structure and objectives of the project
Project Scope Plan : Explains the technical infrastructure and the framework of the project.
Project Timetable : Features of the stages of the project which are prepared on MS Project.
Project Detail Plan : etailed planning of day-to-day activities and responsibilities
Goal : An Implemented Project
Requirements Analysis (RA)
The aim of this phase is to define the implementation needs and processes of the project that will provide the basis of the conceptual design document.
Outputs :
Introductory meeting : The client project team reviews the software in detail. The first meeting where the logic, terminology and package concepts of the system are introduced. This meeting is expected to take a full day.
Q&A Meetings : Module by module definition meetings between the client project team, Vecsoft project team and key users. In these meetings the company's business methods will be discussed, additional modules will be identified and finnaly project analysis requirements report will be put forward.
Conceptual Design Document : The standard modules of the software will be changed according to the operating modes of the customer. They are added, edited or removed. The modules are explained in detail and submitted to the approval of the project manager of both companies.
Goal : Signed Conceptual Design Document (CDD)
Implementation and Additional Module developmetent (IM)
The purpose of this phase is to add additional modules determined in CDD to the software, to make functional changes on the software side and to close more modules if redundant.
Conclusion :
System Configuration : Making the necessary arrangements for the test, indicating changes, deletions and additions
System Configuration Document : A document specifying the arrangements for the final version of the system specified in the CDD
Hardware Configuration Document : A document describing expected hardware requirements for the server side and the client side of the project
Functional Specifications : Additional reports, labels, and software additions in the software if need be
Unit Test :Determining the necessary data for testing each work module, preparing case studies
Integration Works : Determination of integration with other software or systems, table structures, integration method, data flow directions, determination of data flow frequency
Integration Document : The document describing the decisions taken as a result of the integration study the structures of the table and the integration method
Train-The-Trainer Trainings : Key users are trained on the last version of the system
Goal : End of Unpublished System
Customer Test and Approval (CTA)
The aim at this stage is to test the system by the client project team to validate software and procedures. This phase includes three different steps :
- Testing the functionality of the system
- Integration test
- Volume data test (Stress Test)
When the customer project team achieves successful results after the tests, the System Acceptance Form is signed. This form concludes the delivery of the system.
Conclusion :
Customer Approval Support : At this stage, the project team gives troubleshooting support to solve software related issues . As a result is a key user structure that is well-trained and well versed on operations is built, aware of the previous stages of the project.
System Acceptance Form : A signed form indicating that the system and procedures within the framework of the project have been accepted by the client project team.
Goal : Tested and Approved Systems and Procedures
Deployment Preparation Phase (DP)
The purpose of this phase is to make the necessary preparations to turn the software into a functional part of the operation. At this stage, the client project team plays a more decisive role. At this stage, Trinox provides consultancy on the necessary identifications or transfers for succesful operation of the software.
Conclusion :
Preparation Support : Prior to the start-up of the system, the project team provides support for issues such as the solution of existing problems, the bottlenecks that may occur if there is any, and the working duration of the system.
Transition Plan : The plan which describes the passage of the software to live. This includes procedures such as making definitions or providing transfers that will be necessary for the operation of the software.
Start-Wait Meeting : Before the deployment of the system, it is the meeting where both project teams will decide to start deployment.Iif there are unresolved issues, they are determined and the decision to resume or to postpone is taken. It is the meeting where the final decision will be made on whether the system will start or not.
Goal : System deployment
Deployment Support Phase (DS)
The aim of this phase is to enable the software deployment and to provide on-site support during initial use. This step can include three different steps :
- The project team may provide support at the location of the project (Vecsoft project team and client project team)
- Software and database support with phone and remote connection method through numbers given by Vecsoft, first diagnosis and solution
Conclusion :
Additional Requests List : A list of additional module, report requests that are not included in the first scope of the project and which are encountered during the transition phase.
Goal : A functioning system
Project Team Breakdown
- Project Leader (Team Manager)
- Software Development Specialist (Software Engineer)
- Implementation and Support Specialist (Business Analyst)
- Sales and Process Manager (Sales Specialist)
- Hardware Specialist (Technical Staff)
Persons mentioned in the project team may be the same employees in different stages. For example, the software development element may also be a support staff. The number of resources mentioned in the project team depends on the project.
