Modelling Detailed Process

1. Take a Product Owner issue

Select an issue assigned by the Product Owner.

Make sure that the objective and expected outcome of the issue are sufficiently clear before starting the modelling process.

2. Create a development sub-issue

Create a new sub-issue linked to the selected Product Owner issue.

The sub-issue must:

• be labelled dev;
• keep the same name as the Product Owner issue, with the addition word tasks

3. Analyse the Product Owner issue

Analyse the requirements described in the Product Owner issue.

Discuss the requirements with the Product Owner to clarify any ambiguity or missing information.

4. Write and validate the business rules

Translate the requirements into explicit business rules.

The rules should describe the expected behaviour and constraints of the application.

Discuss and validate these rules with the Product Owner before moving to the next modelling step.

5. Create the data dictionary

Once the business rules are sufficiently clear, identify the data required by the application and document it in the data dictionary.

The data dictionary should define the meaning and characteristics of the main data used by the application.

6. Create the Merise MCD

Create the Merise Conceptual Data Model (MCD) based on the validated business rules and data dictionary.

The MCD should represent the main entities, their attributes, and their relationships. The MCD can be create by Looping software.

7. Create the MLD

If you used Looping for the MCD, you can convert it into the MLD. Next make sure there is no ambiguity between the properties names. Add Postgres data types

8. Create the zoning

Define the main areas of the user interface and organise the content into logical sections.

The zoning provides a structural view of the interface before creating the detailed wireframes.

9. Create the wireframes

Create the wireframes based on the validated requirements and zoning.

The wireframes should provide a visual representation of the main screens and their content before implementation begins.

The development should start only after the requirements and modelling elements necessary for the task have been sufficiently clarified.