Book a Demo

Author Topic: Project / Model structure example  (Read 4857 times)

TZ

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Project / Model structure example
« on: May 01, 2018, 08:22:04 pm »
Hi All,

I make my first steps with modeling using EA and I would be thankful with some tips:
  • Can you recommend project structure? (items to include/consider in project)
    • Core project / Sandbox
    • As-Is / To-Be models + define transition steps/scenarios
    • Functional decomposition levels (which could include as-is/to-be or/and vise verse - as-is/to-be could include functional decomposition
  • How would you recommend use version control in this case?

Context:
  • Enterprise Architect v13.5 (Business and Software Engineering Edition)
  • File-based repository

NOTE: I have reviewed essential articles with simplistic examples (like this one: http://www.sparxsystems.com/enterprise_architect_user_guide/13.5/model_repository/what_is_a_project.html), but real examples would be more beneficial.

Can you share your thoughts / examples please?

Many thanks,
TZ
Good specifications will always improve programmer productivity far better than any programming tool or technique.

Glassboy

  • EA Practitioner
  • ***
  • Posts: 1367
  • Karma: +112/-75
    • View Profile
Re: Project / Model structure example
« Reply #1 on: May 02, 2018, 11:51:38 am »
Hi I suggest you have a look at the TOGAF Architecture Content Metamodel.  I don't endorse TOGAF itself but the content metamodel is a good starting point for a discussion on what you want to achieve. 

Nizam

  • Prolab Moderator
  • EA User
  • *
  • Posts: 320
  • Karma: +15/-2
  • Model Sharing - Simplified
    • View Profile
    • Professional Model Collaboration
Re: Project / Model structure example
« Reply #2 on: May 02, 2018, 12:07:43 pm »
There are a number of aspects in your question
  • Model Structure
  • Branching / Merging
  • Keeping track of states - Current and Future States
This is highly subjective based on your team structure and working pattern. This is also quite an important phase and making the right choice will reduce the number of reworks / shuffling around.

I would suggest you have a session with one of the consultants to discuss this in detail and base your decisions accordingly.