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
1
Thanks, have made a note of it for when I am doing model maintenance.

Robert

2
Baselines can currently be viewed only by selecting packages.  This means that users have to remember which packages they have created baselines in, which can be a problem if more than one person uses a project file.  As baselines use up a significant amount of space it would be useful if, as a minimum, it was possible to see a list of all baselines grouped by package.  Ideally all baselines could be managed in one place regardless of their root package.

thanks
Robert

3
Suggestions and Requests / Text search and replace
« on: May 01, 2009, 06:02:00 pm »
Ability to find a replace words or phrases in the notes and name fields.  An example would be the ability to replace a TLA in a set of requirements.

4
Suggestions and Requests / Viewing tag values on locked records
« on: April 29, 2008, 12:53:31 am »
I am using <memo> fields for Tagged values.  When the record is locked it does not appear to be possible to launch the pop and there is no scroll par on the Tagged values window which makes viewing long text a poor experience without unlocking the fields, which may not be possible if it has  been locked by someone else.

5
Suggestions and Requests / RTF Reporting for requirements enhancement
« on: September 14, 2007, 01:54:52 am »
It would be a big help if multi level requirements could be output via the RTF reporting tool with indenting to reflect their place in the hierarchy (i.e. displayed in a similar way to the project browser tree).  

At present I acheive this to some extent by using packages, but when decomposing requirements a package is not always appropriate and so I have to manually edit the RTF output to make it clear to readers which requirements are children of another requirement.

Robert

6
General Board / Re: Heading requirements and traceability
« on: July 07, 2009, 11:25:13 pm »
I keep on finding that the structure which worked for one project does not quite do it on the next, picked up some great tips from the responses above.

Another way I have been handling requirments is to create a package hierarchy which reflects the broad functionality to be delivered (might even map to components in a sales orientated component diagram) with a dependency diagram.  I create requirements within the relevant package and turn on level numbering.

I have also been using custom stereotypes to capture additional information, e.g. business priority, which did not fit in the defaults and you could create a stereotype or tag so that you could flag a requirement as a heading or what ever and even % complete and then use the improved filtering in the reports to get it to output it as you wish - not sure if this is actually that relevant to you but may be of interest.

Robert

7
General Board / Re: Business Rules - Decision Tables
« on: April 28, 2009, 07:50:50 pm »
I had a play with the rule composer as we have rules based decision making and it looked as if it would be a big help in defining the rules from the requirements in a form the developers can easily interpret.

8
General Board / Re: Visibility of Tagged values of Attribute
« on: February 12, 2009, 09:00:44 pm »
Use 'feature visibility' on the diagram and/or the elements.

9
General Board / Re: managing requirements - using the baseline feature
« on: April 28, 2008, 07:40:27 pm »
Have you upgraded to 7.1?  I do requirements management and I believe that this problem has gone away as the Audit trail enables me to track every change to a requirement and the baseline feature allows me to generate and compare baselines so that I can see changes between specific points in time/releases.

I have been versioning off the database as we do releases and was able to generate a baseline in a archived copy of the model and compare it to the current model.

Regards
Robert

10
General Board / Generating indented requirements hierarchy
« on: September 10, 2007, 06:37:13 am »
I would like to be able to generate a report which displays requirements in much the same way as they appear in the project browser (child requirements indented under their parent).

I have switched on the child element and child packge options and experimented with numbering paragraphs, indenting the child elements, including level numbering and anything else that I can think off all to no evail, the best I can get is a straight forward list of all the requirements and can not get the level numbering to display.

I have tried putting indented fields in the child element section, but that limits the output to a two level hierarchy.

Does anyone have a solution to this?

Thanks
Robert

11
Bugs and Issues / Re: BPMN SubProcess Expansion/Collapse not working
« on: February 05, 2009, 12:18:22 am »
The BPMN functionality is in Tags not the standard properties, you need to change the Activity type to 'Sub-Process' and hopefully that (plus changing any of the other tags as needed) should sort this for you.

Robert

12
Bugs and Issues / Unlock not working on Packages
« on: June 18, 2008, 12:29:02 am »
I am using 7.1 build 828.
I just tried to update the notes on some of the packages in the model after locking them but when I tried the packages were still locked, though the elements underneath them were not.
No other locks are in place (I double checked).
The package above is locked by me.
I have tried reloading the package.
Am I missing something?  I have been using locking succesfully for some months up to now.

Thanks
Robert

13
Uml Process / Re: Scope: Essential Use Cases
« on: May 23, 2009, 12:11:11 am »
Is this similar to business use cases v system use cases? What you are describing sounds like system use cases and you could map them back to the generic business use case (we are looking to do something similar for reimplementing business functionality in different phases of a project).
I have also looked at using includes, extends and inheritance for handling variations on basically the same process.
Alternatively, you could just jump to activity diagrams.

Robert

14
Uml Process / Re: BPMN Profile an observation
« on: May 23, 2009, 12:14:31 am »
You can also drag and drop the element from the tool bar onto an existing element on a screen and it will update it - just been using this after moving from BPMN 1 to 1.1.  Works for any element and is also a good way of applying your own stereotypes retrospectively to individual elements.

15
Uml Process / Re: How should we model test plans?
« on: March 28, 2009, 01:45:08 am »
Very useful post.  I am not as advanced as use but have been exploring the business - system use case relationship and how we can reuse them both in future iterations and current testing.

Going to share this link with our testers and see where we go from there.

Robert

Pages: [1] 2