V4.4.3_Safety3

Third version of Safety model (functional) and CLs associated to System
version V4.4.3

model/.project

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <projectDescription>
-	<name>AIDASystem_SimfiaNeoModel_System4_2_Safety2</name>
+	<name>AIDASystem_SimfiaNeoModel_443_Safety3</name>
 	<comment></comment>
 	<projects>
 	</projects>

readme.txt

@@ -29,7 +29,7 @@ The quadcopter drone can be piloted in automated or manual mode. In manual mode,
 the pilot guides the inspection of the aircraft by the drone. 
 In automated mode, the drone follows a flight plan and records the video of the inspected zone.
 
-Corresponding SE version (see AIDA Architecture repository): V4.2
+Corresponding SE version (see AIDA Architecture repository): V4.4.3
 
 ************************************************************************
 * 2. Motivation and intended use
@@ -55,13 +55,11 @@ https://doi.org/10.1007/978-3-319-64119-5_2
 - CL_set : contains the description of the Consistency Links (CL) set
 defined for the study of the MBSE-MBSA structural consistency according to the SSR method
 (see deliverable LIV-S085L02-023 / ISX-S2C-DOC-436 from S2C project).
-Two versions of the CL set are available here : 
+The CL set is defined in the following files :
-	- an excel version, used for the MOISE project and at the beginning of the S2C project
+	- primary_aliases : mapping between the primary model (the MBSE model) objects and the CLs
-	- the tooled version established in S2C, contained in the following files :
+	- secondary_aliases : mapping between the secondary model (the MBSA model) objects and the CLs
-		- primary_aliases : mapping between the primary model (the MBSE model) objects and the CLs
+	- CL_model : relation links between the CLs_function and the CLs_flows
-		- secondary_aliases : mapping between the secondary model (the MBSA model) objects and the CLs
+	- CL_metadata : meta-data associated to each CL.
-		- CL_model : relation links between the CLs_function and the CLs_flows
-		- CL_metadata : meta-data associated to each CL.
 
 ************************************************************************
 * 4. Licensing information