A consistent Ivalua design package from your discovery material
Axl turns workshop notes, requirements and the current Ivalua configuration into a design package whose parts agree with each other. A Modali consultant drives it and reviews what it produces.
Where it stands
Modali has used Axl's design document engine on two public-sector Ivalua programs. It runs with a Modali consultant driving it, and what it produces is a draft for that consultant to review. There is no self-service design module yet.
What a package contains
- Design document — A Word document with a section for each object and screen, written to Modali's design standard.
- Workflow diagrams — Diagrams of each process, consistent with the document.
- Field workbook — The fields the design touches, grounded in the tables and columns that exist.
- User stories and traceability — User stories and a requirements traceability matrix that line up with the document.
- UI mockups — Screens based on the current configuration, with the proposed changes marked.
- Assumptions and open items — Anything not yet agreed is kept in its own workbook, out of the confirmed design text.
- Technical design — For integrations: mappings, payloads, and sequence and data-flow diagrams.
Checked before a person reads it
Axl checks that the parts of each package agree with each other. These checks catch inconsistencies. They don't prove the design is right, which is why a consultant reviews it.
The link to testing
Axl Test writes its scenarios from a design package of this kind: the requirements, user stories and field dictionary. A clear design gives the tests a clear target.
Starting the design phase of an Ivalua program? Let's talk about what Axl can draft for you.