First steps

Sign in

Open the address of your Mirador server in the browser. You sign in via the account icon at the top right: it shows a question mark while nobody is signed in. Choose Sign in there and enter Username and Password.

An administrator creates your account. Once signed in, the account icon offers Profile: there you change your name and password (Change password – this signs you out on every device), create API tokens and see where you are signed in.

As long as Mirador has no connection to its server, or you are not signed in, it shows an example project with the note “Mock data only”. Nothing is saved there permanently.

Language and theme

The globe at the top right switches the interface between Deutsch and English. The button next to it cycles the theme: System, Light, Dark. Your browser remembers both.

Create a project

Projects are created by an administrator. From the project selector at the top left, or in the Projects view, they choose New project:

• Label – required, for example “Braking System ECU”,
• Description – optional,
• Project type – requirements or test specification,
• Type schema – the schema the project uses. This choice is final; a project cannot be moved to a different schema later.

Create project opens the new project. The administrator then adds the members – see Users and roles.

Structure and first requirements

In the Directory view:

1. Create a set. The plus in the header of the Project structure (Add element) opens the New artifact menu with the types of the schema. Only sets sit at the top level, such as a “Folder”. The new set appears with its name ready to rename.
2. Folders inside. With the plus on a set, or a right click, you create further folders or requirements of a given type inside it.
3. Write requirements. Choose a folder and then Add requirement: Mirador creates a requirement at once and opens its name for typing.
4. Fill in attributes. In the table by clicking into a cell, or in full in the detail panel (the arrow at the end of the row). Typed values are saved when you leave the field.

Link requirements

1. In the table, click the chain icon of a requirement (Manage relationships).
2. Under New relationship, choose the direction – outgoing (this requirement is the source) or incoming – and the relationship type, for example “Satisfaction”.
3. Search the target by id or name. You can pick several.
4. Add creates the relationships.

For many relationships at once, the context menu offers Create relationships – Link via ID… or Link via directory… – with a plan you check before anything is created.

Search

The search field in the top bar (Ctrl+K, on a Mac ⌘K) searches the current project by id and text. A hit jumps to its place in the directory.

Where to go next

• The traceability view shows whether every requirement is traced down to a test.
• A baseline freezes a state, a review judges it.
• Bring in existing requirements via import and export or from Jira and Jama.