La traçabilité - Historique des versions

Francois.bernigaud le 30 avril 2012 à 13:15

2012-04-30T13:15:52Z

2012-04-30T13:15:29Z

2012-04-30T13:14:58Z

2012-04-30T13:13:17Z

Conclusion

2012-04-30T13:09:12Z

2012-04-30T13:05:59Z

Build the traceability matrix

2012-04-30T13:05:36Z

Build the traceability matrix

2012-04-30T13:02:32Z

2012-04-30T13:01:48Z

Input

2012-04-30T13:01:14Z

← Version précédente		Version du 30 avril 2012 à 13:15
Ligne 1 :		Ligne 1 :
−	~~{{...}}~~
	The following article deals with the traceability management with Enterprise Architect (EA). The main point of the traceability for a project, which is designed with EA, is to make sure the requirements of the project are in line with the models that you are building.		The following article deals with the traceability management with Enterprise Architect (EA). The main point of the traceability for a project, which is designed with EA, is to make sure the requirements of the project are in line with the models that you are building.

← Version précédente		Version du 30 avril 2012 à 13:15
Ligne 1 :		Ligne 1 :
		+	{{...}}
	The following article deals with the traceability management with Enterprise Architect (EA). The main point of the traceability for a project, which is designed with EA, is to make sure the requirements of the project are in line with the models that you are building.		The following article deals with the traceability management with Enterprise Architect (EA). The main point of the traceability for a project, which is designed with EA, is to make sure the requirements of the project are in line with the models that you are building.

@@ Ligne 3 : / Ligne 3 : @@
 For instance, when you complete your design, the traceability between your component model (part of design phase) and the requirement model will allow you to make sure the component model is covering all the requirements.
 ==Input==
-Goal of traceability in a project which follows a V-Cycle:
+Goal of traceability in a project which follows a Project Life Cycle:
 * Ensure the requirements traceability from specification to validation
 Input for a traceability between the requirements and the use cases:

← Version précédente		Version du 30 avril 2012 à 13:13
Ligne 40 :		Ligne 40 :

	So you will save time in using the use case rather than the requirement.		So you will save time in using the use case rather than the requirement.
		+	----
		+	Retour vers [[Le processus de développement]]

@@ Ligne 9 : / Ligne 9 : @@
 * Use case Model
 * Tracability diagram
-[[Fichier:trac_P1.png|left]]
+[[Fichier:trac_P1.png|thumb]]
 As traceability can be compared with a gap analysis between 2 models, the traceability will begin once you have the models completed.
 ===An example===
@@ Ligne 24 : / Ligne 24 : @@
 If you now go in EA to: « View -> Relationship Matrix »
 Select the source (Use Case) and the target (Requirement) with the « Link type » = Realization, you will obtain the following:
-[[Fichier:trac_P4.png]]NB: « Option » section allows you to extract in csv format the matrix.
+[[Fichier:trac_P4.png|thumb]]NB: « Option » section allows you to extract in csv format the matrix.
 Excel/csv extract:
-[[Fichier:trac_P5.png]]You are now able to compare the requirement and the use case. You can so be able to identify orphan requirement and/or orphan use case.
+[[Fichier:trac_P5.png|thumb]]You are now able to compare the requirement and the use case. You can so be able to identify orphan requirement and/or orphan use case.
 Traceability utility:
 # Allow you to be sure that there is no missing requirement that was not addressed in your specification.

@@ Ligne 26 : / Ligne 26 : @@
 [[Fichier:trac_P4.png]]NB: « Option » section allows you to extract in csv format the matrix.
 Excel/csv extract:
-[[Fichier:trac_p6.png]]You are now able to compare the requirement and the use case. You can so be able to identify orphan requirement and/or orphan use case.
+[[Fichier:trac_P6.png]]You are now able to compare the requirement and the use case. You can so be able to identify orphan requirement and/or orphan use case.
 Traceability utility:
 # Allow you to be sure that there is no missing requirement that was not addressed in your specification.
 # Allow you to know if some use case is not link to any requirement and so could be not needed.
 # Allow you to provide a report for your manager/client as a “proof of quality”. “As shown with this traceability matrix, no requirement is missing in our solution.”
 ==Conclusion==
 The above show a way to track the consistency of your specification. The same method can be used with the design, the integration and the validation phase of your project.

@@ Ligne 15 : / Ligne 15 : @@
 [[Fichier:trac_P2.png|thumb]]
 Now, to build the traceability model, you have to link every use case to a requirement in using the EA relationship called “realization”. Once this is done for all the use case you should have the following:
+[[Fichier:trac_P3.png|thumb]]Note: in this example the following color code was used for the requirements:
 * Yellow: Proposed
 * Orange: Mandatory
@@ Ligne 27 : / Ligne 24 : @@
 If you now go in EA to: « View -> Relationship Matrix »
 Select the source (Use Case) and the target (Requirement) with the « Link type » = Realization, you will obtain the following:
+[[Fichier:trac_P4.png]]NB: « Option » section allows you to extract in csv format the matrix.
 Excel/csv extract:
- <<pic5>>
+[[Fichier:trac_p6.png]]You are now able to compare the requirement and the use case. You can so be able to identify orphan requirement and/or orphan use case.
 Traceability utility:
 # Allow you to be sure that there is no missing requirement that was not addressed in your specification.