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 - timoc

Pages: 1 ... 10 11 [12]
166
Uml Process / Re: Requirements Models and 'Construct' reports.
« on: May 13, 2019, 07:13:28 pm »
I did try to use Archimate3 motivation and requirement elements, as i want to build Work Packages from them: http://pubs.opengroup.org/architecture/archimate3-doc/chap13.html#_Toc489946119

Unfortunately compartment visibility seems to be broken in the Archimate symbols (at least on Goal elements in v14.latest), so no notes, tags, maintenance items, etc can be shown (Info view kinda works but looses color and symbol).

It's not broken.  Those concepts don't exist in ArchiMate.  But the ArchiMate and TOGAF folks don't see that as an issue.

It actually sounds like you want to build your own meta-model and MDG for modelling.
I'm sure i will have to. That's where all of the signs point. I have been hoping to avoild it until i need to do it.

167
Bugs and Issues / Re: Diagram strip Arrow controls need rework
« on: May 09, 2019, 06:42:19 pm »
Works with crossover too - works with right and left control keys.

Tim,
What keyboard does have a right control key?

q.
Dell KB 522:https://tweakers.net/pricewatch/365392/dell-kb522-(qwerty-us).html

168
Uml Process / Re: Requirements Models and 'Construct' reports.
« on: May 09, 2019, 06:07:33 pm »
I am a TOGAF and Agile practitioner. I need to use EA as an architecture/requirements repository. I want to understand the 'out of the box' capabilities because i do not want to spend too much of my time setting it up. I want to get a repository working and then evolve it (as per TOGAF/Agile best practice!) into something that better fits my needs, as understanding will come with use.

It sounds like you should be modeling requirements at the motivation level then, not the functional level.  http://pubs.opengroup.org/architecture/archimate3-doc/chap06.html#_Toc489946009
I did try to use Archimate3 motivation and requirement elements, as i want to build Work Packages from them: http://pubs.opengroup.org/architecture/archimate3-doc/chap13.html#_Toc489946119

Unfortunately compartment visibility seems to be broken in the Archimate symbols (at least on Goal elements in v14.latest), so no notes, tags, maintenance items, etc can be shown (Info view kinda works but looses color and symbol).

The Archimate approach started to become a rabbit hole, so rather than spend effort building something from scratch (reports, searches, documenting workflows, and creating training material etc)  In the common toolbox there are Requirement/Issue/Change elements, which implied to me that they are there to easily allow you to capture by diagram annotation etc. I started looking for the 'out of the box' requirements workflow as defined by EA and the common elements in the toolbox, for use alongside Archimate diagrams.

So, by 'out of the box capabilities' i am looking for the whatever the full REPL of capture, organize and reporting is for EA's basic requirements management workflow. I started with the assumption that the UI default searches and reports should be linked to these 'out of the box' capture capabilities as defined in the 'common' part of the toolbox.

It is confusing when you have so many of the same terms used in what seem to be different overlapping domains, all with their own assumptions. It has not been simple or basic, as you can tell by my initial post, but i am starting to sort things out in my head. I hope to have enough to deduce what is an EA basic requirements management REPL. All part of the EA learning experience :)

Do you (or anyone else!) have a working Archimate3 based REPL for requirements management/work packages in EA?



169
Bugs and Issues / Re: Diagram strip Arrow controls need rework
« on: May 09, 2019, 05:00:45 pm »
Works with crossover too - works with right and left control keys.

Tim,

170
General Board / Dependencies in Gantt View
« on: May 09, 2019, 04:56:02 pm »
Hi,

Background: I want to use Gantt charts to visualise the dependency relationship between Tasks. I cannot find where i set/choose the dependency relationship to show. Gantt charts (and Construct->Task Management ribbon actions) only work with 'Tasked elements'. I am coining the term 'Tasked elements' here, they are defined by EA as any elements or packages that have resources allocated to them.

Setup:
created a package, and in the package i have diagram and three Tasked elements.
show package as a gantt chart from project browser - it shows the elements with resources allocated,
set up a dependency relationship between two of task elements in the diagram.
I refresh the Gantt chart but the dependency does not show up.

What am i missing?

Tim.
For searchers on 'tasks'- Task elements should not to be confused with an element's Tasks, which are defined as a maintenance Items properties of an element.


171
Uml Process / Re: Requirements Models and 'Construct' reports.
« on: May 08, 2019, 08:30:47 pm »
Timoc, my thinking is that you are in a common situation, many people find themselves in this quagmire when they ignore proven/robust methodology.
My advice is NOT to rely on EA tool functionalities to help you manage requirements, but the other way round - decide how you are going to manage requirements based on a robust methodology, and then use the EA functionalities that support that methodology.
This is where i am confused. There is an obvious presumption of fixed workflow/usage in the design of the main element properties Dialogs (e.g. Start->Properties->Construct or Start->Properties->Requirements) because the major features (e.g. Construct ribbon) seem to be designed to support element properties based workflows. Ironically i have yet to find a diagram visualising these implied workflows and how they relate to one another. Any ideas if there is one?

UML per se does not have much to say about requirements, besides the fact that you can develop stereotypes for them.  But if you look into methodologies like TOGAF or Agile they will tell you how to manage requirements, and you will find EA features that support that methodology (not always 100%, but still make your life easier).
I am a TOGAF and Agile practitioner. I need to use EA as an architecture/requirements repository. I want to understand the 'out of the box' capabilities because i do not want to spend too much of my time setting it up. I want to get a repository working and then evolve it (as per TOGAF/Agile best practice!) into something that better fits my needs, as understanding will come with use.

Good luck!
Thanks, but If i need luck then maybe i have already lost ;)



172
Uml Process / Requirements Models and 'Construct' reports.
« on: May 08, 2019, 05:34:46 pm »
Hi EA gurus,

I have been trying to figure out how to use EA for requirements management. There seem to be multiple overlapping (but mutually exclusive) methods for this.
Requirements models and Maintenance diagrams are a good example, as they are similar to the 'internal item' vs 'external element' with requirements.

I create a maintenance diagram, and add some change elements in a diagram to represent changes to go into a Kanban. I then try to use the Construct ribbon, (or the search drop-down) to get a simple report of all of these changes and it comes up empty. If i add a change item to an element (via properties->construct->maintenance->changes) it appears.

Which begs so many questions:

If you have to use the <element>[change item]? What then is a <common Change element>[change item]?, or a <common Issue element>[issue item]?
Are there existing searches that work for maintenance elements?
How are people using EA in this way? is the best practice to use the <element>[change item]? How does Specification Manager support this?
Can someone explain to me the utility of this split/overlap? are they supposed to be orthogonal to one another?

Any and all answers appreciated, as i cannot yet see the 'hard edges' i expected for requirements management enough to use it with confidence.



173
If i invested in the tool you describe, one that promised to help me optimize my drinking habits - that is from opening bottles in the evening though to needing coffee in the morning (the full drinking lifecycle  ;D ). Now if it had integrated hammering features, i would want to know how the designer thought it related to the optimal drinking life. I might also want to check to see if it can be used to break empty bottles...

Rather than extend the metaphor past breaking point, back to something related to this topic. I admit i am still reading the fine manual(s), looking for best practice, testing the workflows, and trying to choose well supported features. I'm not trying to overdo the manual reading, as the EA 14 Guidebooks alone weigh-in at about 600 PDF pages, with the whole documentation set coming in at about ~6300 PDF pages. Who has the time or inclination?

This is where it gets tricky, using ea in 'measure twice cut once' scenarios. Say i am defining my repository content meta-model, and I want to be able to plan and record project events in my architecture repository. I can do that in (at least) 3 different ways, all of which are similar but are supported by different diagrams, workflows and UI.

But question answered there is as yet no canonical list of legacy like features.


174
I would honeslty love to be able to know how (and why?!) to use those obscure features, as long as they are supported. I am currently trying to figure out how to use the Calendar.

175
I am exploring Maintenance Diagrams, and Kanban Diagrams, and how they relate to the default searches in the Construct ribbon. I admit i am still reading the fine manual(s), but still seem to be missing some fundamental insight. Maybe some of the older and wiser heads here can tell me why some things are so?

Element maintenance properties like Changes, Defects, Issues, and Tasks i can kind of understand, as a kind of typed thing, but i do not understand why they do not show up in the properties dialog as a kind of inside requirement or similar, as there are external Change. Defect, Feature and 'User Story' elements associated with the Kanban. They show up in the element browser, but that seems like an odd way to have to find or create these maintenance things.

I do not get Element maintenance Events and Decisions. Events have a "Type" Property that does not seem to be shared anywhere. I assumed it was related to the Event in the calendar but there is no relationship.  Maintenance Decisions i cannot find any reasonable documentation for. The why of the Calendar Tasks vs Element maintenance tasks is itself another topic.

Also all of the status/type fields maintenance record types are freetext, and not maintained anywhere. I can use any status or type i want (e.g. 'context', 'complenessness') if i do not mind retyping every time. It looks like a hard coded dropdown, not a normalized table of types? or is that configurable somewhere?

Finally the EA 14 construct ribbon works with element maintenance properties - so it is a Tier 1 feature, yet the other Tier 1 features - Maintenance and Kanban Diagrams, work with elements and cannot display element maintenance properties. What is the use case here? are Maintenance elements and properties different domain concepts? if so how so?

176
I came across "problem type" project settings dialog  while exploring EA14.1, while trying to figure out the what and how of maintenance and what is the difference/benefit of inside and outside requirements. I spent some time trying to use "problem type", and I was scratching my head trying to find where they are used.

Now i've come across this post from 2002 ["Re: Where is Problem Type used?"] explaining they are not used, and its better if you just ignore/disable it.

So if these types have not been used in 15 years, and they are still there in EA, i have to ask if there a list somewhere of unused/unusable/to avoid out features?


Pages: 1 ... 10 11 [12]