Mapping Business Requirements to Technical Requirements

Once the business requirements for your Drupal site are documented, DPCI will translate them into technical requirements for the Web content management system. The technical lead for the project will review the business requirements and plan which Drupal modules will be leveraged, as well as which modules will need to be enhanced or custom-built by DPCI. If integration with third-party applications is required, these requirements are also incorporated into the system design.

The product of this process is a technical specification document that serves as the blueprint for the Drupal system during development, as well as for any enhancements that are planned for later projects. During this stage, DPCI will delve deep into the detailed requirements for your Website, from the system architecture down to the specific fields needed for each content type. At this point, DPCI may also help you define the taxonomy that you will use to categorize content, if you have not already established it.

DPCI’s technical team is staffed with creative minds who know there is always more than one solution to a problem. The process of mapping business requirements to technical requirements is a crucial step in the planning and execution of your Drupal Website. Once the design is complete, the team can more forward confidently into the implementation phase.

Case study:
Drupal Consulting for Production Management Group

DPCI implemented the Drupal Web content management system for PMG to provide a robust framework that expedites deployment of micro-sites for fundraising groups. > more

All case studies


Press Release:

DPCI Nominated as an Adobe Digital Publishing Suite Reseller
DPCI will focus on implementation, training and support services as well as integrating Adobe Digital Publishing Suite with InDesign Server, K4 Publishing System, and customer Web content management and digital asset management systems. > more