Book a Demo

Author Topic: Style question  (Read 5608 times)

ceatley

  • EA User
  • **
  • Posts: 27
  • Karma: +0/-0
    • View Profile
Style question
« on: September 09, 2004, 09:41:38 pm »
I am developing an application (C#) with several assemblies (components) , an .exe and several dll's. My question is how to best orginize my EA project.  I have come up with two possibilities. I would like to hear from everybody on what they think.
  My ideas are:
!. Create a Project Root node for each assembly and at least one more that ties everything together.  Under each Root have each of the needed views for the assembly (Use case, Class view, etc.) Packages would be used for functional seperation of the design within the assembly
2. Have one Project Root for the Solution and under each of the views have packages for each assembly.
So all of the class diagrams for the entire solution would be under the same view with different packages for the .exe and each .dll. My assemblies divide the application across tier and business requirements.  Security, datalayer, business objects, reports, GUI. etc. Any comments?


« Last Edit: September 09, 2004, 09:46:39 pm by ceatley »

sargasso

  • EA Practitioner
  • ***
  • Posts: 1406
  • Karma: +1/-2
  • 10 COMFROM 30; 20 HALT; 30 ONSUB(50,90,10)
    • View Profile
Re: Style question
« Reply #1 on: September 09, 2004, 09:53:43 pm »
I would suggest you consult with your audience to find out the best way to arrange the presentation of your material.

There are many threads in this forum on this topic. They are usually quite active so look for threads with lots of reads.

hth
Bruce
"It is not so expressed, but what of that?
'Twere good you do so much for charity."

Oh I forgot, we aren't doing him are we.

ontherun

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Style question
« Reply #2 on: January 07, 2005, 09:44:28 am »
It really depends on what your goals are.  In your case, it seems like that you already have a design, and you are using EA for documenting your design???  I say that because you already know your components -- this is something I usually do not figure out until I have gone throgh a requirements analysis, use case analysis, object discovery, etc. etc.