Document & Record Lifecycle Software

Document Management >> Software >> Workflow Solutions

Document Management Workflow Software- Customized Solutions


Document management workflow can be described as a set of relationships between all the activities in the document creation process, from start to finish. Workflow specifically involves the movement of documents around an organization for various activities or business processes including evaluation, performing activities in a process, collaborative writing, review, sign-off / approval and ultimately publication.

Business processes are activities undertaken by an organization in pursuit of a common goal. Typical business processes include receiving orders, marketing services, selling products, delivering services, distributing products, invoicing for services, accounting for money received. A business process usually depends upon several business functions for support, e.g. IT, personnel, accommodation. A business process rarely operates in isolation, i.e. other business processes will depend on it and it will depend on other processes.

FileHold consulting are experts in designing and developing customized document management workflow software solutions - using the FileHold '08 library - to streamline your business process activities. For a "budgetary" price quotation on your workflow solution contact sales@filehold.com or call us at (604) 734-5653


The following are steps we take when defining and developing customized workflow document management software solutions on behalf of our customers;


Requirements Gathering Phase

A workflow engagement initially involves mapping out existing business processes, interviewing stakeholders and gathering requirements for a custom workflow implementation. The consulting team creates the product requirements document using functional requirements, end user input (focus groups), use cases and mock-up screenshots to communicate the features of the solution. The client's representatives collaboratively provide input and approval throughout the creation of the requirements document.


Design Documentation and Specification Phase

The design phase consists of design documentation of the signed off features/functionality, pseudo code, and prototyping where applicable. This is required to ensure that the manner in which the feature is to be implemented has been thoroughly thought out and all necessary changes to the existing design are identified. This design specification enforces traceability back to the product requirements document.


Implementation Phase

The coding phase of the process allows the Engineers to implement the feature in the language to meet the design objectives and requirements. As implementation phase progresses unit testing is conducted to ensure the implemented feature meets the requirement.


Testing Phase

The last phase in the development process allows all features, modules, protocols, user interfaces, database, business logic to be integrated and tested before deployment. The Integration Testing phase consists of installation, configuration, feature testing, documenting test results, creating engineering release notes.


Deployment Phase

Deployment of the of the customization application components consists of two methods; Remote installation through a Virtual Private Network or Onsite installation.


This development process allows our organization's ability to deliver quality product meeting the requirements that are captured during the requirements gathering phase, this includes the solicitation of input from end users, sales, technical support, and market analysis.

 

"Companies are spending 6-15% of annual revenues on documents and document related processes."
(source: docume.nt magazine June 2004)

  document management home  |   privacy  |   resources  |   site map  |  blog