Author Topic: Step by step Guide  (Read 567 times)


  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Step by step Guide
« on: May 18, 2018, 12:33:29 am »

I am new to EA and I am struggling to find a tutorial...step by step guide on how to use the application.

My main focus will be on Requirement gathering (for software development) and also project management and test cases management( also software).

thank you for pointing me towards the right direction (documentation..) or even online training (I don't mind being it paid).



  • EA User
  • **
  • Posts: 749
  • Karma: +46/-17
    • View Profile
Re: Step by step Guide
« Reply #1 on: May 18, 2018, 01:07:59 am »
the information base is just huge. However I do not know any „beginners only guide“.

You might find some helpful stuff following the links below.
Best regards,

Peter Heintz


  • EA User
  • **
  • Posts: 85
  • Karma: +1/-0
    • View Profile
Re: Step by step Guide
« Reply #2 on: May 18, 2018, 01:57:55 am »
Or try Enterprise Architect for the Business Analyst - look on Leanpub -

or this one - it's new but I've not gone through it yet -

Or give this one a try - it's not complete yet though


  • EA User
  • **
  • Posts: 659
  • Karma: +19/-0
    • View Profile
Re: Step by step Guide
« Reply #4 on: May 18, 2018, 04:24:36 pm »
Hi Pierre,

For requirements gathering, it is very common to create a model with separate branches (packages in EA) for Functional and Non-Functional requirements (see FURPS for an example of requirements classification). Requirements can be updated in EA and/or via Excel export/import. It is also important to think about traceability with your other modelling artefacts.

With EA, you have all types of diagrams you need incl Requirements, but you always need to define a suitable Model structure. Good examples are shared by the users community or also provided by Sparx in the EA Example (with EA 13, open START > Help > Open the Example Model. In the project open Analysis and Business Modeling > Requirements Model). This is very often where Sparx partners come into action with advice & training services.
For some specific needs, requirements can be tailored with stereotypes (UML profile) e.g. to add additional fields such as RefID, Category, etc.

I don't use Project Management features as dedicated tools like JIRA and others are more suitable (EA is a very open tool making it possible to integrate with other tools).

For test cases, it can be used but again based on your need.

Please note about the upcoming EA users gathering on the 8th of June in London where you can follow useful presentations and meet experienced EA users and experts:



Blog: | Free utilities addin:

Richard Freggi

  • EA User
  • **
  • Posts: 108
  • Karma: +4/-3
    • View Profile
Re: Step by step Guide
« Reply #5 on: May 19, 2018, 12:34:50 pm »
how you use EA to document requirements depends mostly on how you are going to use the requirements.  There are several good ways to do this...
If you are going to use the requirements to drive UML based software design or system architecture, then the book "Applying use cases" by G. Schneider and J. Winters is more than enough to get you on your way.  It's a very easy read.  Then it will be obvious what to do in EA.
Good luck!