Changes between Version 17 and Version 18 of LabassertUserGuide
- Timestamp:
- 05/25/09 08:53:32 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
LabassertUserGuide
v17 v18 1 1 [[PageOutline(1-4)]] 2 2 3 = Labassert User Guide = 3 __Labassert User Guide__ 4 4 Reference: ESA/ESTEC contract n°21166/07/NL/JK -8 Jan. 2008 5 5 … … 22 22 {{{ 23 23 #!comment 24 = = Table Of Content ==24 = Table Of Content = 25 25 1. [wiki:LabassertUserGuide#a1.Installation Installation] 26 26 1. [wiki:LabassertUserGuide#a2.ApplicationsDescription Applications Description] … … 50 50 }}} 51 51 52 = = 1. Installation ==52 = Installation = 53 53 Labassert 1.0 is available on Windows and Linux. Its installation requires no specific platform dependent procedure. The only action that may be required is to uncompress the archive with the appropriate utility if the distribution was provided as a zip or tar.gz file. 54 54 … … 67 67 Ellidiss Technologies can provide technical support to users of the Labassert tool. Please use the following address to send technical or commercial inquires: labassert@ellidiss.com 68 68 69 = = 2. Applications Description ==70 == = 2.1 Launcher ===69 = Applications Description = 70 == Launcher == 71 71 The launcher is used to open the functional, the interface and the deployment view editors. 72 72 73 === = 2.1.1. Screenshots ====73 === Screenshots === 74 74 [[Image(htdocs:UserGuide/img1.png)]] 75 75 76 == = 2.2 Functional View ===76 == Functional View == 77 77 The Functional View Editor manages the applicative functions that can be referred within the Interface View. 78 78 … … 83 83 Functional View models can be stored in separate Libraries (.lfv files). 84 84 85 === = 2.2.1. Screenshots ====85 === Screenshots === 86 86 [[Image(htdocs:UserGuide/img2.png)]] 87 87 88 === = 2.2.2. File menu description ====88 === File menu description === 89 89 * New Library : create a new functional view. 90 90 * Open Library : load an existing functional view (.lfv extension). … … 94 94 * Quit : close the application. 95 95 96 === = 2.2.3. Edit Menu Description ====96 === Edit Menu Description === 97 97 * New Function : create a function (functions appear in “Functions” notebook). 98 98 * Delete Function : delete the selected function. … … 104 104 * Delete Parameter : remove a parameter from an interface. 105 105 106 === = 2.2.4. “?” Menu Description ====106 === “?” Menu Description === 107 107 * About : about the Interface View Editor. 108 108 * Help : application description and accelerators available. 109 109 110 == = 2.3 Interface View ===110 == Interface View == 111 111 The Interface View Editor manages the grouping and the interaction of the applicative '''Functions''' within a hierarchy of '''Containers'''. 112 112 … … 117 117 Interface View models can be stored in separate Files (.liv files). 118 118 119 === = 2.3.1 Screenshots ====119 === Screenshots === 120 120 [[Image(htdocs:UserGuide/img3.png)]] 121 121 122 === = 2.3.2 File Menu Description ====122 === File Menu Description === 123 123 * New : create a new interface view. 124 124 * Load : load an existing interface view (.liv extension). … … 129 129 * Quit : close the application. 130 130 131 === = 2.3.3 Edit Menu Description ====131 === Edit Menu Description === 132 132 * New Container : create a Container on the work zone or in a Container. 133 133 * New Function : create a Function on the work zone or in a Container. … … 142 142 * Redo : redo the last modification. 143 143 144 === = 2.3.4 Tools Menu Description ====144 === Tools Menu Description === 145 145 * Edit Functional View : open a Functional View Editor with current Functions of the interface view (loaded and created). 146 146 * Generate Interface View : generate the AADL file of the current interface view. … … 153 153 * Option : launch Interface View Editor option dialog box. 154 154 155 === = 2.3.5 “?” Menu Description ====155 === “?” Menu Description === 156 156 * About : about the Interface View Editor. 157 157 * Help : application description and accelerators available. 158 158 159 == = 2.4 Deployment View ===159 == Deployment View == 160 160 The Deployment View Editor manages the description of the run-time hardware and the allocation of the software elements onto it. 161 161 … … 166 166 Deployment View models can be stored in separate Files (.ldv files). 167 167 168 === = 2.4.1 Screenshots ====168 === Screenshots === 169 169 [[Image(htdocs:UserGuide/img4.png)]] 170 170 171 === = 2.4.2 File Menu Description ====171 === File Menu Description === 172 172 * New : create a new diagram. 173 173 * Load : load an existing diagram (.ldv extension). … … 177 177 * Quit : close the application. 178 178 179 === = 2.4.3 Edit Menu Description ====179 === Edit Menu Description === 180 180 * New Processor : create a Processor on the work zone. 181 181 * New Partition : create a Partition on a Processor. … … 191 191 * Redo : redo the last modification. 192 192 193 === = 2.4.4 Tools Menu Description ====193 === Tools Menu Description === 194 194 * Generate Deployment View : generate the AADL file corresponding to the current deployment view. 195 195 * Navigation Panel : open the navigation panel in order to scroll and zoom the diagram. 196 196 * Option : launch Deployment View Editor option dialog box. 197 197 198 === = 2.4.5 "?” Menu Description ====198 === "?” Menu Description === 199 199 * About : about the Deployment View Editor. 200 200 * Help : application description and accelerators available. 201 201 202 = = 3. Tutorial ==202 = Tutorial = 203 203 This tutorial presents a classic way of using Functional View, Interface View and Deployment View Editors. 204 204 205 == = 3.1 Functional View Editor ===205 == Functional View Editor == 206 206 1. Launch the Functional View Editor. 207 207 1. Load a '''Data View''' (File → Load Data View):[[BR]] AADL representation of the Data View files must exist in the workspace. They are usually generated by the Asn2aadlPlus tool. However, a simplistic version of an AADL Data View can be created with any text editor for the purpose of the tutorial. Its contents should be the following: … … 236 236 Note : in the save as dialog box, a default name is proposed for the file : the previously given library name with the “.lfv” extension (Calc.lfv in our example). 237 237 238 == = 3.2 Interface View Editor ===238 == Interface View Editor == 239 239 1. Launch the Interface View Editor. 240 240 1. Load the previous '''Functional View''' (File → Load Functional View) : “Calc.lfv” file. … … 296 296 15.Generate the '''AADL''' file “Time_Conversion.aadl” (Tools → Generate Interface View). You can check the consistency of the result. 297 297 298 == = 3.3 Deployment View Editor ===298 == Deployment View Editor == 299 299 1. Launch the Deployment View Editor. 300 300 1. Load the previous '''Interface View''' (File → Load Interface View) : “Time_Conversion.liv” file.
