Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Robert Sheridan

Pages: 1 2 [3] 4 5 ... 7
General Board / Re: Document a package reference
« on: January 24, 2013, 02:04:36 am »
A work around I have used to acheive something similar is to use diagrams only in a sub package and drag onto the diagrams the elements from other packages that you want to appear at that point in your document.

This works because there is an option in the document template to include elements that are on diagrams as well as any actual elements.

If you create your templates with this capability you can override it when you run the report using the relevant switch on the document generation screen.

The downside is that it will apply to all the packages in the scope of the report so any elements in diagrams elsewhere which you might not have wanted to be included will be..  The only work around I have found for this is to use virtual documents with different sections for the diagram only packages.

General Board / Re: Synching windows user with EA user
« on: January 30, 2013, 04:17:18 am »
If the users have the windows domain in front of their login name (e.g. TheDomain\rsheridan) and 'Accept Windows Authentication' is checked then they do not need to have a password set up in EA.

General Board / Re: Manage Baselines / Version Control
« on: January 17, 2013, 10:17:14 pm »
The organisations I have worked in have been using basic EAP repositories or have not been willing to buy another tool so I have been using the manage baselines a fair bit.

It does, as Geert implies, require a discipline to create the baselines and in where to create them as you have to know what package they are created in as there is no way of finding them otherwise (unless maybe you do some sort of underthe covers SQL search).

As I have been using EA for business requirements and process modelling and we have to generate documents we have a protocol of creating a baseline each time a document is generated and that works well.

If you can get that discipline in place I find the baseline comparison tool a better way of seeing what has been changed when rather than using the audit facility.

General Board / Re: Heading levels in RTF
« on: January 23, 2013, 08:48:32 pm »
I have got heading levels to work OK.  It is best if you start from a blank report format which you retain as your base template for all subsequent reports.  Set this template up with the section headings and numbering overrides as described in the user guide (a tedious process but you have to follow it).

You do have to set the level numbering separately to the section level (right click on the section heading and select paragraph - list numbering).  When you use the template it automatically recurses and so if it is outputting a sub element or package it will automatically go to the next level down

General Board / Re: EA and Agile methodology (SCRUM)
« on: January 18, 2013, 07:10:01 pm »
EA will do the job: user stories can be implemented as use cases. The next hurdle is how you capture the supporting detail for the user stories, we create requirements under the user story so that everything moves together.  

To manage the user stories we have a standard package hierarchy which we use to create User stories under.  User stories start of in a project model, move into a release model when they are accepted for development and end up in a live model when they are delivered.  As a user story passes through the life cycle we update its status and the status of any associated requirements and other artefacts.

The next problem is how you share the user stories with the other teams.  Ideally they all use the EA repository; however, this seems to be often not the case. We generate a rtf document and baseline the relevant part of the model whenever a new or updated set of user stories are released to a team.

If user stories are allocated to a release but not implemented they are moved into a backlog model and which is reviewed when the next release is being planned.

We evaluated the SCRUM extension and it looks great for doing standard SCRUM; however, the local working practises mean that it is not suitable.  This is a common problem as transitioning people to a standard way of working using a tool is difficult (but essential to using the tool as Stroppy says).

As always the devil is in the detail.  Keep it simple and evolve and you should get there.

General Board / Re: Doc Gen Requirements Realized by Embedded Elem
« on: December 29, 2012, 01:17:32 am »
I suspect that the embedded element tag pair will work in the same way as the child element tag pair.

Have you had a look at the template fragments in v10?  I have just used it to output requirements below the requirements that have a dependency on them.

General Board / Re: Doc Gen Requirements Realized by Embedded Elem
« on: December 19, 2012, 01:37:16 am »
You may have run into the same problem I had when I wanted to recursively output child requirements in a different format to other requirements, the answer from Sparx was:

With the Child Elements Section - this is normally set as un-populated - in this mode the Package::Element section is used to report it and there is recursive run of the hierarchy.
However if the Child Element section is populated the reporting is only for the current level.

General Board / Re: Delete A Document Template
« on: December 20, 2012, 12:39:30 am »
F8 and then the templates tab.  Select a template and then click on the delete button at the bottom of the screen

General Board / Re: IIS / SharePoint - Attach to process
« on: December 19, 2012, 01:34:13 am »
There are some past threads on integrating with Sharepoint.  If I remember correctly the essence of them was that it wont work!

General Board / Re: Alternate path of alternate path
« on: December 19, 2012, 01:32:51 am »
I use activity or BPMN diagram to show flow between use cases, try to keep the use cases simple and (as suggested) use an extends from an alternate flow to another use case when a complex alternate process is needed.

You would then have test cases for each scenario in each use case and an end to end test case which stitchs together the relevant scenarios.

General Board / Re: Reporting: relevant packages only
« on: December 19, 2012, 01:41:13 am »
I achieved something similar by dragging the packages I was interested in into a virtual document section.

General Board / Re: automatically show inherited associations
« on: November 25, 2012, 05:47:38 pm »
If you right click on an element on a diagram and select 'Add' one of the options is related element which will add all elements related to the selected element.  Additionally you can set the depth, type of element and type of connector.


General Board / Managing use case requirements
« on: November 09, 2012, 12:08:33 am »
We are identifying our requirements in advance and mapping them to use cases that will deliver them using realisation links.  In some cases these are existing use cases that will need to be updated when the new requirements come into scope so these use cases have delivered and pending requirements associated with them.

I am looking for a way of when we generate documents they only include the pending requirments and was wondering if anyone had any suggestions.  I had thought to make the delivered requirements internal but have not found a way to move an external requirement into a use case.


General Board / Re: Just starting....
« on: March 14, 2012, 04:37:23 am »
I have introduced EA into various organisations.  Here is a brain dump of things to get to grips with at a general level:
1. The repository is the source of knowledge, not the documents generated from it - there is always more info in the repository than in the docs.
2. In a team it is a more disciplined way of working as you all need to work in the same way.
3. Use baselines and the audit log to track changes, dont create copies in the model for posterity
4. Be prepared to refine your EA usage
5. Start simple there is a lot there.
6. Collaborative working is SO much easier with EA.
7. The model view can give you short cuts into your repository

The help, learning centre, tutorials and white papers are all very helpful.

Go for it

General Board / Re: Auto Numbering Based On Level Numbering
« on: October 02, 2012, 11:36:26 pm »
I use autonumber to uniquely identify and level numbering to help show the hierarchy of elements (usually requirements).  They are not interchangeable in my view.

I agree with Qwerty, I find myself lost in the features on occaisons; more is not necessarily better.

Pages: 1 2 [3] 4 5 ... 7