Book a Demo

Author Topic: Example to modelling  (Read 3863 times)

Naima

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Example to modelling
« on: July 21, 2009, 06:06:12 pm »
Hi, i look for an example where can i learn step by step to modelling an project with EA.
Thanks

ebeb

  • EA User
  • **
  • Posts: 169
  • Karma: +0/-0
    • View Profile
Re: Example to modelling
« Reply #1 on: July 21, 2009, 10:19:46 pm »
Hi,

it would be nice to know what you already know or had a look on... But if that's not the case, check these out:

Very good video tutorials:
http://www.sparxsystems.com/resources/demos/

Then you could read some specific white papers, according to your needs.

http://www.sparxsystems.com/resources/whitepapers/

See the UML tutoial if need UML guidance, or the Requirements Management e.g. for further steps.

This depends highly on what you plan to do in EA.

I just started using EA by myself for the first time one week ago. I watched the videos and read some white papers to get started.

Once you install EA, see the demo tutorial for an example. Otherwise you could create a new project and choos to add all available model. These models are not empy but will guide by by good structuring and a lot of included examples and note all over the place.

I hope I could help you,

Jan
« Last Edit: July 21, 2009, 10:21:20 pm by ebeb »

RoyC

  • EA Administrator
  • EA Practitioner
  • *****
  • Posts: 1297
  • Karma: +21/-4
  • Read The Help!
    • View Profile
Re: Example to modelling
« Reply #2 on: July 22, 2009, 09:03:51 am »
You could also look at this section of the User Guide:

http://www.sparxsystems.com/uml_tool_guide/start_uml_modeling/gettingstarted.html

I'd be interested in your comments on how useful it is to you.
Best Regards, Roy

Thelonius

  • EA User
  • **
  • Posts: 274
  • Karma: +6/-0
  • I think. Therefore I get paid.
    • View Profile
Re: Example to modelling
« Reply #3 on: July 22, 2009, 10:32:28 am »
Roy

The documentation for EA is excellent. And I think you do most of the heavy lifting in creating and maintaining it with each successive version. Not an easy task. My hat goes off to you.

The only suggestion I'd make is this.

EA documentation tends to focus on describing the many, many things I can do in EA. As in "how to make this function work".

What I would like to see more of in future is:

"Why would you want to do this?"
"When would you need to do this?"
"What benefit / advantage does using this function / feature give you?"
"Why would you want to use this function - as opposed to other, similar functions / features that EA also provides?"

Hijacking this thread, I know. It just occurred to me.

RoyC

  • EA Administrator
  • EA Practitioner
  • *****
  • Posts: 1297
  • Karma: +21/-4
  • Read The Help!
    • View Profile
Re: Example to modelling
« Reply #4 on: July 22, 2009, 12:01:14 pm »
Thanks - that is very valuable feedback. It aligns with our (unfortunately longer term) intent to re-cast the EA Help and other resources into a more integrated toolkit for finding out how to do things with EA. Our difficulty is that the Help (let alone the other resources) is a large beast to redirect; rather like trying to turn an enthusiastic elephant with a matchstick. But we keep prodding!
Best Regards, Roy

Thelonius

  • EA User
  • **
  • Posts: 274
  • Karma: +6/-0
  • I think. Therefore I get paid.
    • View Profile
Re: Example to modelling
« Reply #5 on: July 22, 2009, 12:54:04 pm »
Quote
Thanks - that is very valuable feedback. It aligns with our (unfortunately longer term) intent to re-cast the EA Help and other resources into a more integrated toolkit for finding out how to do things with EA. Our difficulty is that the Help (let alone the other resources) is a large beast to redirect; rather like trying to turn an enthusiastic elephant with a matchstick. But we keep prodding!

Isn't it a principle of software development that if you write one line of code, you have to write 10 lines of documentation?

Why not mod EA to automatically generate user documentation based on model-driven design?

Ironic isn't it that while the EA tool multiplies the effectiveness of software developers by automating generation of code based on conceptual models, you still have to create documentation the good old-fashioned way. Crafting it meticulously, line-by-line.