← Publications
Documents and management decisions

From Requirement to EDMS Acceptance Record: A Worked Training Example for an IQusion Project

How a project manager on the client side can ensure the traceability of EDMS requirements and avoid the dilution of acceptance criteria.

Successful implementation of an Electronic Document Management System (EDMS) requires both a suitable product and clear requirements and checks. A project manager on the client side needs to connect a specific need to an expected test result. The following training example examines one requirement: returning a document for revision must include a reason. It helps prepare for discussions with IQusion IT LLC or another integrator; it does not describe a completed project or a verified feature of a particular product.

Recording Requirements as a Foundation for Future Acceptance

The first step in preparing for automation is turning requests into verifiable requirements. For each need, identify an owner who can explain the workflow and agree the verification criterion. Assign this role within the specific project: it may be the relevant department head or another authorized person. The IT team and users help clarify constraints, but job titles alone do not establish the authority to accept a result.

To prepare for discussions with an integrator such as IQusion, the client must clearly delineate their own responsibility for business logic and the supplier's technical scope. Euro Consulting recommends creating a catalog where each requirement has a unique identifier, version, and success criteria. This allows for avoiding situations where the supplier offers standard functionality that does not take into account the specifics of the file classification scheme or complex approval routes, which are critical for the institution.

Sources: [1], [2], [3]

Training Scenario: Requirement R-01 and its Lifecycle

Training requirement R-01 v1 states that a user must provide a reason when returning a document for revision. In this example, the head of the records office is assigned as the requirement owner. Test T-01 needs a test document in 'Pending Approval' status and a user authorized to return it. Positive check: enter a reason and submit the return; the expected result is 'Needs Revision' status with the reason retained. Negative check: on another document with the same prerequisites, leave the reason empty; the expected result is a blocked return, a required-field message, and unchanged 'Pending Approval' status. These are planned outcomes, not a report of an executed test.

The verification record links R-01 v1 to test T-01, its prerequisites, and two separate expected outcomes. Before execution, agree the requirement version, the decision owner, and how evidence will be recorded: for example, the tester will save a document-state screenshot and a log entry. Record the actual result, evidence location, deviations, and acceptance decision after execution. The test scenario describes planned actions; the completed record preserves what was actually observed.

The Impact of Changes on Testing Integrity

Imagine that after a month, there is a need to change the requirement: the reason for rejection must now be selected from a list rather than entered manually. This is recorded as a change request CR-01. The requirement version becomes R-01 v2. The previous test evidence (T-01 for v1) becomes insufficient because it does not check for the presence of a drop-down list. The old record is not deleted but archived as history, and a new test protocol is created for R-01 v2.

Such an approach allows for avoiding chaos during implementation. If you do not update the acceptance criteria after CR-01, you risk accepting a system that formally works (blocks rejection without a reason) but does not meet the new business needs. The project manager on the client side must require the integrator to update the test plan for every change that affects user logic, ensuring full traceability from the business need to the technical result.

The Role of the Integrator and the Solution Ecosystem

In its public document management implementation description, IQusion lists the configuration of routes, roles, and the document model for an organization's structure, and mentions the Megapolis.DocNet EDMS. This provides a basis for discussing R-01 with the integrator, but does not establish that a ready-made setting can implement it in every version. For the target version and configuration, verify the implementation approach: an existing setting, an additional module, or custom development. Record the selected option and its limitations before agreeing the test.

IQusion's public consulting description mentions comparing an organization's needs with UnityBase-based products and identifying required configuration, modules, or integrations. That description does not establish that R-01 is implemented in a particular configuration. During discussions with the integrator, clarify how the return reason is stored, who can see it, and whether it can be changed after the action. Include the answers in the agreed requirement and verify actual behavior in a test environment.

Sources: [1], [2]

Acceptance Protocol Structure: A Practical Template

For training requirement R-01 v2, the record contains: owner — head of the records office; change — CR-01; test — T-02; prerequisites — a test document in 'Pending Approval' status, return permission, and an agreed list of reasons. Positive check: select a reason from the list and return the document; expect 'Needs Revision' status and the selected value to be retained. Negative check: on a separate document with the same prerequisites, select no reason; expect the action to be blocked, a required-selection message, and unchanged status. Provide separate actual-result, evidence-location, and deviation fields for each check. Complete them after executing T-02, and record the authorized client's decision after the evidence has been assessed.

This structure covers one training rule and needs adaptation to the agreed process and environment. It distinguishes a missing result from a discrepancy: an empty actual-result field means that the check has not been recorded, not that it passed. If the status changes after the negative check, record the observation, document, and test conditions, then assign the discrepancy to the responsible person. Do not replace the actual result with the expected-outcome text.

Sources: [3]

Change Management and Responsibility for Results

After CR-01, the requirement owner first agrees R-01 v2 and the planned T-02 criteria. The team then executes the checks, preserves the evidence, and records discrepancies. Only after that does the authorized client representative record acceptance or the need for rework. This sequence reduces the risk of different interpretations of the result but does not guarantee that users will have no concerns. The parties agree responsibility for requirements, implementation, and acceptance for the specific project.

Before deciding on R-01, check four things: the requirement's current status, the agreed version, the retained test evidence, and the authority of the person accepting the result. If a discrepancy blocks an agreed criterion, assess it against that criterion and the agreed acceptance process, rather than the total number of comments. The decision record should preserve what has been accepted, which questions remain open, and who is responsible for the next action.

Sources: [2], [3]

Implementation checklist

  • An owner is assigned for every business requirement in the catalog.
  • Each requirement has a unique identifier and version number.
  • The test plan is separate from actual results and the acceptance decision.
  • Change requests (CR) undergo a procedure of updating the corresponding tests.
  • Record actual results after the relevant check has been performed; record the acceptance decision separately.
  • The business requirement owner confirms that the actual result meets expectations.

Questions and answers

How can shared quality criteria be combined with checking an individual requirement?

Shared quality criteria can be reused, but they should be supplemented with the prerequisites and expected outcome of the specific requirement. For R-01, this means separate expectations for returning a document with a reason and attempting a return without one; a general quality criterion does not replace those expectations.

How often should requirement versions be updated?

The version must be updated with every change that affects user logic or data structure. This is necessary to preserve the history of decisions made and the correctness of testing.

Is it mandatory to involve the integrator in writing acceptance protocols?

The integrator must confirm the technical feasibility of your requirements, but the business logic and success criteria must be defined by the client. Working together on protocols helps avoid misunderstandings regarding exactly what is considered completed work.

Sources

  1. Впровадження документообігу | Розумна компанія IQusion
  2. ІТ-консалтинг | Розумна компанія IQusion
  3. Бізнес-аналіз і вимоги до ІТ · Euro Consulting

Explore the related consulting service ↗

YOUR NEXT STEP

Turn the question into a plan.

Tell us which decision your team needs to make.

Discuss your challenge