Author Topic: Documenting Business Rules in EA  (Read 4372 times)

Dorian Workman

  • EA User
  • **
  • Posts: 194
  • Karma: +0/-0
    • View Profile
Re: Documenting Business Rules in EA
« Reply #30 on: February 12, 2009, 12:24:57 pm »
Also, Version 7.5 (currently in beta) introduces a new Element type called 'BusinessRule' (I'm pretty sure I got the name right, from memory).
<a href="http://www.linkedin.com/in/dorianworkman" ><img src="http://www.linkedin.com/img/webpromo/btn_liprofile_blue_80x15.gif" width="80" height="15" border="0" alt="View Dorian Workman

RoyC

  • EA Administrator
  • EA Practitioner
  • *****
  • Posts: 1166
  • Karma: +9/-3
  • Read The Help!
    • View Profile
Re: Documenting Business Rules in EA
« Reply #31 on: February 12, 2009, 01:53:20 pm »
There are three of them: Rule Task, Rule Flow, and Business Rule.
Best Regards, Roy

Henrique Narciso

  • EA User
  • **
  • Posts: 86
  • Karma: +0/-0
    • View Profile
Re: Documenting Business Rules in EA
« Reply #32 on: February 13, 2009, 04:15:36 am »
The work arround sounds good.
in the 7.5 i have tried to use the business rule but it is linked to the requirement auto name counter, so it's back to the drawing board.

David

  • EA User
  • **
  • Posts: 30
  • Karma: +0/-0
    • View Profile
Re: Documenting Business Rules in EA
« Reply #33 on: February 18, 2009, 12:49:35 am »
With regard to Auto Name Counters. I received the following reply from Sparx Support back in Oct 2008 for "Registered Support Request - Auto Numbering from merged .EAP files."

Unfortunately Auto Name Counters cannot be applied to individual Stereotypes (only element types), therefore only one can be applied to Requirement type elements.  The Auto Name settings are saved in the EAP file.  Unfortunately there is also no option to Export/Import the Auto Name settings.  I will raise two feature requests on your behalf so that this functionality is considered for implementation in a future release of EA.

Currently the Auto Name setting would need to be manually changed (via Setting | Auto Name Counters) depending on which type of Requirements are being created.  If necessary you can rename a number of elements fairly easily by exporting to CSV, editing in a spreadsheet and importing back into EA (see "CSV Import and Export" in EA help).

Sorry we can't be of more help.


Hope this helps.

Regards  

David

bioform

  • EA User
  • **
  • Posts: 230
  • Karma: +0/-0
  • Forty-Two?
    • View Profile
Re: Documenting Business Rules in EA
« Reply #34 on: February 18, 2009, 01:45:12 am »
To work around some of these things, I use SQL against the project file (.eap) or a project hosted on a RDBMS (I use SQL Desktop Edition)

Remember: if your EA project is a stand-alone project file, you can rename it to mdb (data is stored in an access database), then connect to the project.mdb file and update away..., then change it back to .eap so you can use it in EA)

David
« Last Edit: February 18, 2009, 01:46:21 am by bioform »
Time is what keeps everything from happening at once, Space is what keeps it all from happening to you. <unknown>

bioform

  • EA User
  • **
  • Posts: 230
  • Karma: +0/-0
  • Forty-Two?
    • View Profile
Re: Documenting Business Rules in EA
« Reply #35 on: February 18, 2009, 02:22:28 am »
On another note: Back to actually modeling a business rule using EA as of release 7.1

Let's say we are modeling the requirements for a Order/Invoice/Shipping system.

The current business has a business practice of not pulling stock for new orders, when the customer has unpaid purchases, totaling $1000 or more, and the order(s) are more than 30 days past due.

Assumptions about the system under discussion (SUD)
  • We have a vision statement,
  • We have a stakeholder model,
  • We have a use case model, and
  • We have an analysis domain model.
I might approach this problem by identifying the following (and usually in this order. Notice I don't bother with identifying the actual business rules until the end...)

  • Which stakeholders want this practice implemented, and what are their needs that this practice will protect?
  • What are the scenarios we will use to validate we got this right?
  • What business and/or system use cases will play a part?
  • What domain elements will play a part?
  • What are the business rules?

Comments, suggestions, anyone want this to move further?

David
Time is what keeps everything from happening at once, Space is what keeps it all from happening to you. <unknown>

Flexyware

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: Documenting Business Rules in EA
« Reply #36 on: February 18, 2009, 06:06:33 am »
David,

From fairly new guy when it comes to business rule modeling you certainly touched on a few very good questions wich I never thought of while attmpting this,

Well done, and certainly will be interested in see it moving further.

thanks for the input, it is certainly valuable.
 ::)