Our company's growth has been the result of a dynamic and professional approach to our business during our years of operation. DCP is committed to continuous introduction of the latest Internet/Networking technologies and we will always offer the best services and solutions to match our customer needs. We strive to be your Technology Partner, rather than just a supplier.
Our Multi-Dimensional Strategy is based on the new core technology, The Multi- Business Systems, allowing extensibility, functionality, security, interactivity and flexibility for all sort of platforms and applications. As for website services our methodology is based on partnering with our customers to produce a professional work allowing them to meet their corporate objectives.

Our aim is not only to produce the solution to the client but also extends further to Quality-Assure it. We understand that in order to maintain your edge in this competitive market you need to take into consideration the possibility of expansion and further complexity added to the solutions we provide to the client.

• Risk Assessment and Management
• Program Crisis Resolution
• Commercial Phase
• Developmental Phase
• Deployment Phase
• Delivery and acceptance
• Operational Phase

Risk Assessment and Management:-
Our methodology recognizes the importance of planning for the unexpected. Changes in business needs, economics, user requirements, or force majeure can affect even the best project plans. A risk management plan helps identify potential risks before they occur and prepares for a quick response if they do occur. A well-conceived and proactive risk management plan offers these benefits:

Program Crisis Resolution:-
We take immediate action to help you regain control. Using our methodology, we establish an environment that helps you discover problem areas, initiate the necessary actions, and institutionalize processes that will keep the initiative on track.

Our methodology is based on the following steps :-

Commercial Phase:-

During the commercial phase the Account Manager (AM) is the main point of contact with the customer. Our Account Manager's task is to explore new leads in marketplace, qualify those leads, develop a viable proposal in response to this market's needs and turn those leads into orders. This phase can be divided into 2 processes:-

Lead Process :-
The lead qualification is based on an in-house set of criteria and the perceived score. Our business development criteria for new leads is:

a. Project size
b. Customer's name & reference value
c. Customer's economic situation (size, business sector…)
d. Customer's commitment to internet technology
e. Future possible extensions to project(s), to existing projects, new future projects, possibility for long term relationship
f. Technological fit with DCP's current and future competences
g. Project risks
h. Commercial effort needed versus possible return (references in this domain, estimated time to respond, allowed time for response, information requested)
i. Proposed contractual terms
j. Awareness of the Competition for this opportunity and their relative position of the competition vis-a-vis this customer
k. Rapport with the customer
l. Project vision and scope (i.e. already defined, supported by senior management etc.)

The lead capture and response ("offer") is very much dependent on the type of customer, the available input, the requested result by the client, the budget, the type of project and the available time. Order Process:-
The lead process ends with either a customer's GO or NO GO. In case of a GO the order process is initiated.

The lead process will culminate in a signature on the order form, and if needed, the contract. At either of these milestones (Ordered) the lead becomes a project and enters the project definition phase.

Project Definition Phase:-
The project definition phase is initiated by the signing of the order form and/or contract. This is when the project is born and the appointed Project Manager (PM) becomes the main driver of the activities.

Project start:-
The project manager starts with the preparatory tasks :

a. Creating the customer and project profiles in the planning and timesheet system
b. Resources are assessed and allocated to the project (art director, analyst/consultant, lead developer)
c. The project documentation is placed on the public project server
d. The initial progress sheet is created (complete with budget)
e. Arrange and host the first internal project meeting with the team (PM, AM, consultant, art director etc.)
f. Arrange and host the first external start-up meeting with the client's team (marketing and art director, IT and analyst, business users and analyst, customer's PM and PM & AM).
g. Plan the project definition phase
h. Occasionally: identify additional training requirements and plan.
i. Start purchase process if commercial software or additional hardware is needed - to ensure delivery for the development or deployment phase.

Project file:-
Next, the project manager will coordinate the team in creating the Project file.
The project file is the collection of the Project Diagram (PD), Graphic Concept (GC), Functional Analysis (FA) and Project plan (PP). The project file describes the project and is agreed on by both the integrator and customer. The completion of the project represents the milestone: (Defined)

For large projects, the project definition phase might take time (according to the number or complexity of modules). In these cases, the full project is divided into smaller parts all undergoing definition simultaneously, which can more easily be done with the functional analysis tasks.

In principle, we won't start development if there is no approved project file for the (part of the) project. This only occurs with the agreement of the executive manager and the customer representative's superior.

Developmental Phase:-
The development phase starts with a solid technical analysis. For the IT aspects of the project, the development, test and production environments are defined by the lead developer, including the configuration management architecture and requirements (we commonly use Visual Source Safe). For the graphic aspects of the job, the template build up, navigation system, and file organization is investigated by the graphic designer.

The lead developer elaborates if needed further the development methods, the algorithms, the internal object and data models, in order to have a consistent and functional system.

Software, and graphic development (Web designer) work in parallel on the project, with regular integration of the graphics and the software elements to allow internal module testing. During development the QA server is used by the development staff to do the first integration tests, and once the system has obtained some level of stability, we provide the customer the possibility for early feedback. This is how we achieve incremental development, ensuring client's visibility on the progress, and ensuring that the essential items are in place ASAP.

The Project Manager is responsible for the follow-up of the project internally and externally and problem resolution. Even the best prepared projects always experience something unexpected.

The Project Manager::-
a. Keeps the project focus clear for the team and support the customer's vision
b. Schedules and budgets the follow-up & tracking
c. Does the Risk Follow-up
d. Undertakes regular internal and external project meetings
e. Does reporting and action point follow-up
f. Handles problem & issue solving, including follow-up of results
g. Does the documentation plan follow-up and document update/change follow-up
h. Undertakes the configuration management audits and follow-up

Deployment Phase:-
The deployment phase has 2 main parts:

Quality Testing Phase:-
When modules have been tested by the development team they are delivered to the QA server for integration and QA testing by the Tester.

Based on the comments from QA (internal and customer) the modules and related documentation are adapted, retested and released to QA. I.e. modules may pass through this cycle a few times between development and deployment in order to attain the required quality.

During QA Testing bugs are tracked and logged, as are new releases between development and deployment. At the end of this phase the project has reached the milestone (tested) and it's ready for delivery to the customer.

Delivery and acceptance:-
Delivery and acceptance is when the project is installed in the client's production environment. Since this is probably the first time the project functions in its real environment with real interfaces and connections, a thorough testing is important.
After a first smoke test of all interfaces and functions by the integrator, customer and integrator can start the acceptance testing (which is a joined effort). The target of acceptance testing is to test the project on a functional level and evaluate compliance with the project file.

Bugs and problems reported during acceptance testing are collected and resolved.
At regular intervals update releases are installed and regression tested. At the end of the acceptance phase (when all problems have been solved or at least reported with a solution proposal) the provisional acceptance is signed-off, marking the milestone (delivered).

In parallel with the acceptance testing the documentation is finalized and technical, administrator, training and user documents are prepared and delivered during this phase.

The signature of the provisional acceptance starts a period of extended evaluation by the customer. Then we can begin the maintenance and administration training for the customer and other users, with the new system. During this period the system is also opened up to its public users, i.e. launched.

Each release out of the configuration management system is accompanied by a release note describing the changed files, the resolved problems and impact. After completion of the extended evaluation period the final acceptance is signed signifying the conclusion of the project, and the start of the warranty period.

The project manager plays a very important role during the deployment phase: timely and fast problem resolution is of prime importance, including follow-up of these problems and open communication with the customer.

The development team is kept in support for problem investigation and resolution during this period, and gives full priority to this.

Operational Phase:-

The operational phase consists of 2 streams :-

Warranty Related Activities:-
During the warranty period, any problems found are evaluated in the context of the requirements in the project file. If the reported problem is non-conformance with regards to the specifications and is blocking the normal functioning of the system, this is resolved by the integrator.

Reported problems not qualified as major (i.e. not blocking or not conflicting with the project file requirements) are resolved based on the decision of the customer, and will be invoiced. If after resolution, another major problem occurs, a new delivery is made, followed by a small acceptance test.

Project and Maintenance Extensions:-
Project and maintenance extensions are put through the same methodology as the initial project. But, for example, a graphic concept may be skipped since this is already defined in the existing project.