This step is also demoed with this video :

(ongoing...)

Step 6c : Capitalization process

As explained in step 6, capitalization process aims to specifically declare a user version as a validated version :

• • the version turns from vU to v###d###

  • the module is copied to a remote storage capability via network to make this version available for the community

Note that according to your organization, there might be a performance keeper saying wether a module can be capitalized or not.

In the context of this step 6c, module FB_LatAcc_vU9 and FB_YawRate_vU9 exist.

Assume that module FB_LatAcc_vU9 is good enough to be capitalized. After having selected the module, one can press the Capitalize button :

A rank 2 GUI opens saying that since there is no activated server, it is not possible to capitalize :

Indeed, on the main GUI, the ACTIVE SERVER field is empty :

The SERVERS view enables to manages servers :

As we can see :

• • a server must be first declared by its adress

  • and secondly, a server can be activated

In this context 6c, a kind of server has been locally created at C:\Users\FG\Documents\MATLAB\MTX_Server\

Remark : usually for a real remote storage capability, adress starts with \\

Then by pressing Creation in this view, a field must be filled with the adress of the server :

Once it's validated, there is this acknowledgment message :

Note that at this stage, there is no ckeck at all : the adress may not exist, or the server may not respond.

The server has been declared, it must be selected and activated by pressing the Des/Act button :

An acknowledgment message confirms the activation :

Now, the main GUI show the adress of the active server :

And now, it is possible to capitalize module 'FB_LatAcc_vU9' by :

The rank 2 GUI for capitalization appears :

User must enter a capitalized version as v###d### with # an integer.

Note that there are two Minor version and Major vestion buttons.

Theses two buttons propose a version according to the highest version on the server. Assume that this highest version of family FB_LatAcc is v005d103 :

• • Minor version will propose v005d104 : the right part is incremented of 1

  • Major version will propose v006d000 : the left part is incremented of 1 and the right part is set to 0

In this context 6c, since there is no existing capitalized versions for FB_LatAcc, both of the buttons will propose v000d000,

but the user can start with v123d456 if he will to, let's start with v000d000.

Once the action is executed, the acknowledgment message occurs :

Remark : capitalization process is quite long because of checks.

At this stage, capitalized module FB_LatAcc_v000d000 is available on the server for the community and locally :

Note that in the MODULES view, version vU9 has now an Origin version :

This Origin version will enable to trace versions, in order to avoid regression : this is specifically explained at step 6d.

Note that capitalization process is available for Modules, Assemblies and Architectures.

To be capitalized, following requirements has to be fulfilled :

• • for a module, it must be valid, cf. Step 0j

  • for an architecture, it must be valid, cf. Step 5b

  • for an assembly, the attached architecture (if any) must be a capitalized one, and its modules must be capitalized.

In this step 6c, we've seen how to capitalize a module :

Once it's done, the aim for other users is to get the new version : this is the Synchronization process. It is explained next step 6d

Published with MATLAB® R2013a