WebSVN – DevTools – Diff – /EA_ReqPro/trunk/EA_ReqPro/ImportReqProDatabase.cs

+                  {
                      ea_req_matched[i_ea_req] = true;
                      EA.Element ea_req = ((EA.Element)ea_reqs[i_ea_req]);
+                     rq_obj.ea_element_ID = ea_req.ElementID;
                      // This ReqPro requirement already has a counterpart in EA, so we must simply
                      // update the counterpart. But, to aid the designer, we need to try to tell them
                      // how the requirement has changed, which could ofcoarse change the meaning
                      // of the requirement and require design changes to be done.
                      // create the new EA requirement in the import package
                      EA.Element ea_req = (EA.Element)importPackage.Elements.AddNew( rq_obj.tag + " " + rq_obj.name, "Requirement");
                      ea_req.Notes = rq_obj.text;
+                     rq_obj.ea_element_ID = ea_req.ElementID;
                      ea_req.Difficulty = rq_obj.difficulty;
                      ea_req.Priority   = rq_obj.priority;
                      ea_req.Version    = rq_obj.version;
                      ea_req.Status     = rq_obj.status;
             displayChangeLog(ea_repository, changeLog);
             ea_repository.RefreshModelView(parentPackage.PackageID);
+            // Setup the internal requirement to requirement connectivity. This is seperate from the browser
+            // organisation of elements in EA, but since in ReqPro, that organisation tells part of the story
+            // of requirement to requirement connectivity, it is mirrored in the internal connectivity, along
+            // with explicit trace relationships setup in ReqPro.
+            // The purpose of this internal connectivity is to support relationship matrix tables in documentation
+            // generated by EA_DocGen, or to support diagrammatic representations of the requirements in EA,
+            // where the connectivity will become apparent through links ajoining the requirement elements in the
+            // diagram.
+            ea_repository.WriteOutput( Main.GUI_OUTPUT_TAB_NAME, "Writing Trace Information", -1);
+            foreach( ReqPro_object sub_obj in rq_root_package.ReqPro_objects )
+            {
+               write_traces(ea_repository, sub_obj);
+            }
             // display summary stats
             ea_repository.WriteOutput( Main.GUI_OUTPUT_TAB_NAME, newRequirementCount.ToString() + " new requirements", -1);
             ea_repository.WriteOutput( Main.GUI_OUTPUT_TAB_NAME, modifiedRequirementCount.ToString() + " requirements modified", -1);
             ea_repository.WriteOutput( Main.GUI_OUTPUT_TAB_NAME, statusUpdatedRequirementCount.ToString() + " requirements had status changes", -1);
             ea_repository.WriteOutput( Main.GUI_OUTPUT_TAB_NAME, orphanedCount.ToString() + " requirements were orphaned", -1);
             if ( ! (reqTypeIsFiltered(rq_obj) || reqStatusTypeIsFiltered(rq_obj)) )
+            {
                // Add this requirement to the flattened list we are accumulating
                rq_req_collection.Add(rq_obj);
+               // In ReqPro, a requirement can be related to another requirement in several ways:
+               // 1. By virtue of its position relative to another in the browser display. That is,
+               //    if you place a requirement beneath a parent requirement, you are establishing a
+               //    parent-child relationship.
+               // 2. By virtue of a specific TraceTo relationship being made via the Traceability menu
+               //    option.
+               // Interestingly, ReqPro prevents you creating a relationship of one of the above types,
+               // if a relationship of the other type already exists. This implies that the relationship
+               // between a parent and child requirement must be singular and is important regardless
+               // of the manner in which it was created or represented.
+               // The CopyReqProDatabaseToMemory base class will already have taken care of recording
+               // relationships detected from ReqPro made using method 2 above. What we need to do here is
+               // take care of those apparent from the browser based hierarchical organisation (ie. made
+               // in ReqPro using method 1).
+               // All we need to do is grab the parent object (if any) and add the GUID of the child to
+               // its list of trace-to's. Later on, the write_traces() class method will turn these into
+               // EA based connection objects that belong to the parent requirement elements.
+               if (rq_obj.parent != null)
+               {
+                  rq_obj.parent.ReqPro_traces.Add(rq_obj.guid);
+               }
                // Using recursion, scan this objects sub-objects, which in practise will all
                // be requirement objects. At this time requirement objects cannot have packages
                // as children.
                foreach( ReqPro_object sub_obj in rq_obj.ReqPro_objects )
+               {

Subversion Repositories DevTools

(root)/EA_ReqPro/trunk/EA_ReqPro/ImportReqProDatabase.cs – Rev 2147 → 2149