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

Pages: 1 ... 17 18 [19] 20 21 ... 23
271
Bugs and Issues / Re: Structured Scenarios in documentation
« on: June 17, 2010, 10:32:46 am »
I hate to answer my own question, but...

...I've raised a registered user support request on this.

272
Bugs and Issues / Re: Structured Scenarios in documentation
« on: June 16, 2010, 04:36:50 pm »
I am seeing the same problem.

Structured scenarios are not exporting in version 8.0.856

Has anyone raised a bug on this yet?

273
Bugs and Issues / Re: EA V8.0 - Doc Generation
« on: April 20, 2010, 05:19:43 pm »
I'm not sure that you're seeing the same bug/feature as me...

...in Project Explorer, are your diagrams "inside" the use cases?

I've just noticed that if diagrams are contained in a use case, they don't appear in generated documentation.

If you lift them out to the same level as the use case they do appear...

Is this the same issue?

Please note I'm using 7.5.848

274
Uml Process / Re: UML vs BPMN for detailed design documentation
« on: September 25, 2015, 03:30:12 pm »
My preference is to have a jumping off point, where the modelling switches from BPMN down to UML (Use Case).

For example, on the BPMN diagram you have an Activity "Purchasing Clerk Creates Purchase Order" which is linked by a message to the "Purchasing System" lane, and an Object called "Purchase Order".

Any occurrence of a Human interfacing with a System is potential for a Use Case.

If you BPMN diagram has activities like (Add Line to Purchase Order) I'd suggest that it has gone down too low into the weeds.

I can see reasons why someone would like to create that kind of duplication across different modelling paradigms, but I'd prefer not to.

Andy

275
Uml Process / Re: Alternative to DFD diagram with UML
« on: May 22, 2015, 02:35:58 pm »
I typically put information flows on a deployment diagram to explain that sort of information.

Most complex recent example had systems on different networks, and boundaries to identify those networks.

Firewalls were represented as devices, nodes and components that overlapped boundaries.

I'm not sure that was technically sound modelling, but it was sufficient for explaining the complexity to the users.

276
Uml Process / Re: Objects with unique attributes
« on: September 05, 2014, 01:34:39 pm »
In case that was a bit too abstract...

1. Find your class in the project browser.
2. Drag your class on to a new diagram - choose to create an "instance" of this class.
3. Right-click on the class and choose "Features and Properties" then "Set Run State"
4. For each attribute, (this is named "variable" in the dialog) you can choose to set an Operator, Value and Note.

 :)

277
Uml Process / Re: files and package organization
« on: July 03, 2014, 08:49:01 am »
Because of the size and complexity of the current project, we have separate packages for each team (business areas mainly, but also some system functionality teams i.e. Integration).

Within those packages we've added Business Process Model, Domain Model, Requirements Model, Use Case Model, etc. as required.

It doesn't matter much where something is, you can always find it with search.

 :)

Andy

278
Uml Process / Re: Capturing port details on switches, routers, e
« on: November 04, 2013, 08:37:21 am »
I'm probably not following this thread very well but...

If you're trying to show the things that make this instance of an object an instance, have a look in the help for "Run State"

You can create a set of variables and then give them specific values for each instance.

Does that help?

Andy

279
Uml Process / Re:  How can I generate class diagrams from a php
« on: October 17, 2013, 09:54:37 am »
After you have imported all your classes...

Try creating a new class diagram, and drag and drop one class into it.

Then right-click on that class and select "Add" and then "Related Elements"

Whee!


280
Uml Process / Re: How to create a simple Domain Model. Tutorial
« on: May 01, 2013, 08:06:33 am »
As a general rule, we do not generate code from the domain models.

Our domain models represent the user experience rather than the software behind the scenes.

Andy

281
Uml Process / Re: How to create a simple Domain Model. Tutorial
« on: April 30, 2013, 09:05:34 am »
Hi Henrik,

I would probably display the "association" between OfferType and ExpirationType <<enumeration>> in a different way. I'm not sure about having an association between attributes and enumerations.

In my case, I'd add an attribute called "Expiration" to the class "OfferType" and then type that attribute as ExpirationType.

Then that attribute would appear as Expiration:ExpirationType in the OfferType class.

Andy

282
Uml Process / Re: help me please
« on: April 30, 2013, 09:57:09 am »
It seems obvious to me, but I've seen many examples where the details are crammed into the scenario steps, and no domain model is built.

Andy

283
Uml Process / Re: help me please
« on: April 30, 2013, 09:19:13 am »
I'd also suggest that use cases may be appropriate when designing other systems (i.e. non-ICT systems).

Examples:
TV Dinner
The cook selects a package from the freezer
The cook places the package into the microwave
...

Hmm... if this is the most common "use case" for the microwave, maybe it should be located near the freezer?

Washing
Laundry basket is placed near the washing machine
Washing is selected by colour and fabric to make up a "load"
Load is placed into washing machine
...

Hmm... maybe there should be a place for the washing basket, and a benchtop (or some other facility) near the washing machine to facilitate sorting of loads?

 :)

Andy

284
Uml Process / Re: help me please
« on: April 30, 2013, 09:13:43 am »
I've fallen into a method where the domain model is created while building the use cases.

For example: the customer has to log in. (Use Case: Log In)

The Customer fills in their Log in Details

Suddenly you have a need for a class on the domain model which explains what Log in Details are.

e.g. Class: LogInDetails
Attribute: UserName
Attribute: Password

 :)

Wherever details like that are needed, they appear in the domain model, and relevant parts of the domain model are included in the printed form of the use case.

Andy

285
Uml Process / Re: Values for an instantiated class
« on: October 20, 2011, 08:12:29 am »
Thanks people,

<hangs head in shame>

I believe that I have been shown this before.

:)

Andy

Pages: 1 ... 17 18 [19] 20 21 ... 23