Prior to any large-scale implementation, DOCOsoft Professional Services can deliver a proof of concept model, to ensure that the system will meet and exceed the objectives and expectations outlined by the original project.
By using this approach the clients can visualise at an entry level; how the system will work, the benefits that will be delivered and will also highlight any amendments that will be required prior to full-scale implementation.
DOCOsoft takes a continued development approach to bring improved functionality and usability to clients. This provides for a future-proof system that benefits clients in the long term.
If development is required, DOCOsoft uses the Spiral Development Model to ensure customer needs are met. This ensures that the customer is provided with:
- What they want,
- When they want,
- Within the budget they want.
The process begins with consultation to ascertain parameters for the upgraded system. Once agreed, the core product is developed using the Spiral Model.
The Spiral Development Model has two distinguishing features:
- It is a cyclic approach for incrementally growing a system’s degree of definition
- It has a set of anchor points [or milestones] for ensuring user input and commitment to mutually satisfactory system solutions
At pre-defined moments in the process, the user is demonstrated the progress of development to ensure it meets with parameters laid out during consultation.
The following stages make up the Spiral Model. Stages are repeated in a cycle until the pre-defined solution is achieved:
- Client Consultation
- Requirements Analysis
- Detailed Design
- Coding
- Unit Test
- System Test
There are many examples of this development cycle in operation at DOCOsoft reference sites.
The section will document our project approach
Define Methodology
In all professional services/consultancy projects, it is essential to have a structured approach to the delivery of a document management lifecycle solution/strategy.
To this end DOCOsoft has developed an integrated approach that makes the whole process of delivery, from the point of inception through to implementation and beyond, as transparent as possible.
Depending on the size and complexity of the project, different timescales are allocated to each stage. The analysis stage is a key phase of the project that aims to fully understand the application that the solution is required to perform and accurately defines the elements that will make up the solution.
Business Analysis Phase
Define the Business Requirements and Scope Project while waiting for approval.
Project Managers will engage consultants to analyse the specific functional and non-functional requirements of priority areas through user consultation. Any customisation required to the core build and general plug-ins is captured at this stage.
DOCOsoft will create a Statement of Works and its final version will signed by the customer and supplier to indicate scope agreement. The Statement of Works will then become a permanent record. There will be a Statement of Works for every service area.
Build & Test Phase
- Business Agreement dependency
- Business Requirements Signoff
- Solution Development
DOCOsoft will create a design document, again through consultation with senior users. The design document outlines the parameters for implementation and is used by Systems Integrators during Development or Implementation.
Once a design has been agreed, this document will be signed by customer and supplier alike and made a permanent record.
If customisation has been commissioned, DOCOsoft developers create and test the relevant modules.
When all necessary updates have been made to the core build, DOCOsoft Systems Integrators will install the relevant modules. Appropriate Customer Senior Users ideally participate in this for skills transfer reasons.
UAT Phase
The installed modules are tested. There may be a bedding-in period to allow for minor changes/issues to be resolved.
When delivering a new or enhanced application it is necessary for it to be tested by a nominated tester from the business before final release. This is to ensure that any anomalies with the application are addressed. This is known as user acceptance testing (UAT). UAT may vary from one application to another, but generally it should be tested under normal working practices.