Module revision

Learn the Uniscale process of 'how-to' do module revisions and approving your functional specifications in the solution editor.

This article assumes that you have covered knowledge around Specification and concepts like Solution basics

Introduction to module revisions

A solution consists of modules, each having its own revision and approval flow.

As your product develops, your specification is written through multiple deliveries.

Whether you use agile, waterfall, or other methodologies, this way of creating module revisions will allow you to iteratively build your specification.

The four phases of module revisions

Every revision will go through the same flow of initiating;

  • Write content: Update, remove, or add new content.

  • Ready and Approve: Lock in your new changes.

  • New revision: To make a change, create a new revision.

  • Unlock content that you want to change.

Lockable cycle

Your modules, pages, sections, functional use cases, and UX flows are all subject to the locking cycle.

Exploring step by step the process, we have:

  • When a new item is created, it has the status of "edited"

  • Once all requirements are met, it can now be "marked as ready"

  • When the owning module is "Approved", all items are moved to "locked"

  • Later, when a new revision is made, all items are still in "locked"

  • From here, one can manually "unlock" the items that are intended for changes, and move them to "unlocked"

  • If any change is made to a "unlocked" item, it gets automatically moved to the status "edited"

Exploration with conceptual explanation

In the start you can have the following:

  • Content that is locked (marked as locked) - finished content

  • Unlocked - edited content

  • Untouched or just not locked (marked as edited) - draft content

  • And also items in ready

How to: Module revisions

When utilising services in your solution, service documentation occurs between content readiness and approval.

Edit an existing module

  1. Click on the name of your solution in the upper left corner.

  2. Select a module.

Approve a new module revision

When you are done editing your module revision you will begin to approve your new revision.

This option will allow you to manually select multiple items and ready at once.

  1. Click on "Ready all"

  2. Select desired items.

  3. Click "Set all to ready".

Explore previous revisions

You can look up all previous revisions to compare your content

  1. Select a specific module

  2. Click on the dropdown and get a list of all revisions


Summary of module revision flow

You iteratively define your module's functionality by starting, specifying, and approving revisions in your module. You can use unlocking to align with stakeholders on what is expected to change existing functions. You can also use readying as a way of tracking your progress against completing your revision. Through multiple iterations and gradually adding functionality to your solutions modules the specification will be the single source of truth for all intentions and decisions making your product what it is today. Through the module revision history, you can go back in time and look at all your historical decisions.

Want more of a deep dive? Watch this video and see the module flow process exemplified:

Last updated