Book a Demo

Author Topic: Requirement Document Version Control  (Read 2955 times)

Hamid

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Requirement Document Version Control
« on: October 26, 2012, 02:01:16 am »
I am a new user of EA.
I am trying to figure out how to generate requirement documentation with software version control. In other words. suppose I have a baseline release 1.0 of my system with all the associated requirement artifacts in EA. I can generate an rtf that will include all these as my requirement document 1.0. When I start working on the next release 1.1 that causes me to add/modify/delete artifacts from the 1.0 version of the requirement model, how can a generate a release 1.1 document to give to the developers that only includes the deltas?

Dermot

  • EA Administrator
  • EA User
  • *****
  • Posts: 591
  • Karma: +7/-0
    • View Profile
Re: Requirement Document Version Control
« Reply #1 on: October 26, 2012, 04:17:08 pm »
The RTF Docuement Generation supports reporting Differences recorded using the Audit feature, but it does not direclty support differences between Baselines.
However what you can do is export the Baseline to XMI and import it into a New model. Then run two reports from the same template - one on the Updated model and one on the Baseline model. Open these in Word or Open office - using the the Compare Documents option - this will highlight the differences as one document.
« Last Edit: October 26, 2012, 04:17:56 pm by Dermot »

Stefan Bolleininger

  • EA User
  • **
  • Posts: 308
  • Karma: +0/-0
    • View Profile
Re: Requirement Document Version Control
« Reply #2 on: October 26, 2012, 06:05:44 pm »
Hi,

you may reset the changed elements status into something like "changed" and just report the changed elements with an model search.

or more simple: select an model search on the desired package which just gives you the elements based on the field "last modified"

then you just have the delta in any form you want to have :-).

Additional information about it:

to have controlled models and prevent unattended changes you may either have a version controll system, or something like that:

Code: [Select]
public virtual void EA_OnNotifyContextItemModified(EA.Repository Repository, string GUID, EA.ObjectType ot)
        {
                if (ot == EA.ObjectType.otElement)
                {
                    EA.Element changedelement = Repository.GetElementByGuid(GUID);
                    if ((changedelement.Type == "Requirement") || (changedelement.Type == "Risk") || (changedelement.Type == "Issue") || (changedelement.Stereotype == "testcase"))
                    {
                        if ((changedelement.Status == "Proposed") || (changedelement.Status == "Mandatory") || (changedelement.Status == "Denied") || (changedelement.Status == "Invalid"))
                       {
                        }
                        else
                        {
                            changedelement.Status = "Changed";
                            changedelement.Update();
                        }

                    }
                    else
                    {
                    }
                }
                else
                {
                }
        }  


Best regards

Stefan
Enterprise Architect in "safetycritical development" like medical device industry. My free Add-in at my Website