Defining my own Project Structure

[jeshaw2]

Created a new project based on EABase.  Tried to rearrange the view packages and was told I couldn't do that.  Tried to delete the Use Case package , so I could recreate it where I wanted it,  but got a scary message that this was a "system defined" package...did I really want to delete it?  Well I did, but I didn't understand the consequences of doing that, so I backed off and wrote this messge.

Are the consequences of deleting a "System defined" view too terrible to document?  And just what are the consequences?

How does one tailor the Project Structure (Like they did in the EAExample project)?

[Martin Terreni]

no need to delete, you can just drug and drop.
any way it deleted fine for me and you can create new use case view.

[jeshaw2]

Thanks for your response Martin, however, what build are you using?  I'm using 744.  Was your project based on the EABase model?  I'm getting different results from yours.

When I attempt to drag and drop I get the message:  "You cannot drag a view level package to another location in the tree".  The drag and drop failed to execute.

When I attempt to delete the view level package I get the message:  "Warning! You have asked to delete a system defined package.  This package cannot be recreated or restored."  Yes, I was able to delete the package, but what else did I loose?  I believe the EA Developers put that warning in there for a reason; what is it?  What are the implications of a package being "System Defined"?  I don't think my deletion of the view went just fine. :-/

How does one recreate a "System Defined" Use Case View?

[Martin Terreni]

you're ritgh about DnD.
about deleteing the view - you can reconstruct it, i beleave it just want be recoginzed as default use case view when importing from a project.

[thomaskilian]

Don't be afraid of those messages. The view levels are "special" packages which can't be moved around. I dop not make use of this structure and only one ore two view levels for a project. The important project information I store as packages in the first view which is named after the project.

This frightening message when deleting a project root is funny since deleting a single package can also not be undone (and thus the effect might be nearly the same). You can re-create a new view and start from scratch any time. Deleting the root just kills the package contents below.

[jeshaw2]

OK, sounds like I can define my own project/documentation structure then.  Whew!

The fact that you loose child nodes in a heirarchy when the parant is deleted is obvious to most IT Techies.  What makes the messages scary is the use of the term "System Defined" which implys a lot of important  program logic and element behaviors.  Perhaps EA could rephrase the term?  

Thanks for hanging in there with me on this.

[Hans]

There's nothing to worry about: just delete what's in your way; btw it's the best you can do.

Hans