Training:The 1000 steps program to MDriven Chapter 1

This is Chapter 1 of the 1000 Steps Program. Each step has been carefully thought out for easy understanding and progress and you will master the steps gradually and in detail.

Whenever you lose your way, you can backtrack to a step that touches upon your current main point and follow along from there.

Video 1: The Basics

To make your experience smooth, we set the main tags mentioned in the video to the right bar menu of this mini-player. Choose an interesting subtitle on the list and immediately get to the exact theme navigation item place in the video. Now you can pick any topic to be instructed on without watching the whole video.

Steps 1 - 40 Introduction Getting started Class, attribute, debugger Seeker and objects Search Association Multilink

Chapter 1: Start MDrivenDesigner, Basic Modeling, Classes, and Associations, Press Play

Throughout this training process, we'll familiriaze you with the MDriven Designer using the example of a car management sytem. This includes creating elements like cars and a car factory and adding people such as a Car Owner and Car Dealer. Every chapter adds a different piece to the overall system.

1. Start MDrivenDesigner by clicking the "Run with ClickOnce" link at: https://mdriven.net/designer.

• You have two options (See: MDriven Shorts| How to install MDriven Designer?):
  • You can choose to always run the MDriven Designer online using "Run with ClickOnce".
  • Or, you can decide to download and install the MDriven Designer, running it locally and making it available offline.
    • Download using either Google Chrome or Microsoft Edge (Internet Explorer is not a viable option).
      • Downloading may take some time if there is a new version.
    • If you're using Chrome, install the Cegid Peoplenet ClickOnce launcher extension from the Chrome Web Store (Microsoft Edge does not need a plug-in).

2. Create a new empty model. Save the file on your device as c:\temp\MDrivenEducation\Start.modlr or equivalent.

3. Create the class Person and save the model.

• From now on, save the model often, using "CTRL + S."

4. Create an attribute, Name, of type string in class Person. Remember to Save

5. Press the Play button on the left of the top menu. Choose XML persistence. Select "Start system", then "Show debugger".

6. In the debugger, in an Expression box, write the OCL expression to show all instances of your class Person with the operator "allinstances": person.allinstances

• Note the empty result list - you have no Person objects.

7. In the debugger, bring up a Seeker - Search will be empty. Create 2 Person objects by selecting "Create New" and adding 2 rows.

8. In the AutoForm for Person 1, give it your name. For Person 2, write some other name.

• In the Seeker for Person, select the first row, right-click, and press the word "Open."
• Click on the box under "Name" and input your name.
• Repeat this to add "SomeOtherDude" (or some other name) as Person 2.

9. Save the created Person objects from the save button in the Debugger.

10. Find the saved XML file on disk in the same location as your model file.

11. Open the XML file with Notepad or another app, find your name, and close the file.

12. In the Debugger Expression box, use the expression from Step 6 to find all persons: person.allinstances

• Note the result - two rows.

13. Close the Debugger, close the Play dialog, and close MDriven Designer. Save, if asked, then restart by performing Step 1.

14. Open recent files - select your file, press play, and go into the Debugger as in Step 5.

15. Perform Step 12. Check that your 2 person-objects survived.

16. Close the Debugger and close the play-dialog (system prototyper).

17. Find the class Person in the tree to the right by filling in the search box on top of the tree.

18. Note 2 rows: one is the class, and the other result is the property. Select Person in the tree. Look at the property inspector below the tree. Change its default color to cyan (or whatever looks nice).

19. In the search box, press escape or clear search box.

• Note the tree structure of the entire model in the tree. You can always find things in the model here.

20. Find Diagram1 in the tree - double click to open it.

21. Diagram1 may be empty - drag and drop the Person class from the tree onto the diagram.

22. Press the "Start!" in the top left corner to show the Start wizard if it does not already show.

23. Right-click the diagram. Choose "Add class."

24. Rename the new class to Car.

25. Use zoom buttons or ctr-wheel to zoom in on your diagram.

26. Enter AssociationMode by pressing the association arrow in the tool button.

27. Click-drag-hold association from Person - hold mouse - move to Car - release.

28. Rename the Cars association-end name to CarsIUsedToOwn. Make sure it has cardinality 0..* (zero to many).

29. Rename the Person association-end name to PreviousOwner. Make sure it has cardinality 0..1 (zero to one).

30. Add an attribute to class Car with the name RegistrationNumber of type string.

31. Find the Car in the tree by using the search box.

32. Double-click the Car in the tree. Note that the screen is not your diagram - it is an auto diagram.

33. Note the link in the auto diagram to class Person . Click class Person. Note, also, the auto diagram shifts to center Person and shows Car on the side.

34. Find your way back to Diagram1 by finding it in the tree.

35. Select the Play button, choose XML persistence, click on Debugger, and execute the expression to list all instances of Person (person.allinstances).

36. Click on the person with your name.

37. Note the new multilink button for CarsIUsedToOwn - click it.

38. Use the "Add New" button to create 3 CarsIUsedToOwn.

39. Click on the auto form for each car. Give them RegistrationNumber OldCar1, OldCar2, and OldCar3.

40. Save the Debugger data.

Next Chapter

The_1000_steps_program_to_MDriven_Chapter_2