REQUIREMENTS ENGINEERING

A document version. Its changes. The people behind it.

Save named document versions with a change note. The history links each version to its author and timestamp and gives you access to earlier document states.

Real product recording · Silent, with text hints · Fictional ECG smartwatch project and demo team.

The workflow, step by step

01 · Refine the content

Maya adds what the contact-loss notification should explain in the software architecture document. The change is made in the document itself.

02 · Name the version and change

She assigns version 0.3 and describes the update. The note explains why a new document version was created.

03 · Find earlier versions

The document history lists Maya’s version beside Lena’s previous version. The versions-only filter narrows the list to named document states.

Change history and document versions

A work item’s history records changes to that record. Named document versions additionally identify a particular document state. Both views help the team follow content and development steps.

Compare selected versions

Select two entries in the document history to compare them. Version comparison supports reviewing changed content. The video on this page shows version creation and the author overview.

Questions about this feature

What should a change note explain?

Describe what changed and why the new version matters. In the example, the notification for contact loss is clarified.

Can I open earlier versions?

The document history provides earlier versions for viewing. Authors and timestamps help you identify the version you need.

Continue through the workflow

Bring your requirements to the demo.

Discuss how your team could organize documents, requirements and reviews in Medioora.