Messages

1

Suggestions and Requests / Re: More than one instance of the Project View

« on: May 09, 2006, 06:22:45 am »

Yes, we get the multiple views of the project as the way to organize the structure of the project - and we are buying into most of the defaults set by Sparx (business model, use case model).  Some we are elevating to the primary tier of "views" (actor catalogs, business rule catalogs) and some we do not use (project model).

However, I guess what I thought was being requested here was the ability to have multiple "project view" tabs, where each one would have it's default template of the project view tree structure.

In our discussions with our business analysts versus QA versus developers, the primary orientation of what each wants and expects to see is very different.  Developers prefer the structure presented by most of the templates delivered the tool; the technical view.  However, the business analysts prefer to have the first tier of "views" be each business process in the project and all related material to that business project as sub-views (folder, whatever).  Our QA analysts tend to side with the business analysts but usually want to attack the project by Use Cases.  It's a usability thing and just a re-sorting and redisplay of the information collected about the project stored in the repository.

Thus, our desire to have multiple template "project views" of the same project geared towards the end users.  Multiple "tabs" each with a different template of views that sorts the project different ways adn presents the information based on the end user.  What I'm hearing is that the EA Tool is limited to a single "project view" tab and we cannot extend nor would they consider an extension because of UML specifications.  I don't buy that.  If you want the tool to be flexible, allow for multiple instances of the project view tab to allow for the project model as a whole to be displayed using several different approaches at once.

2

Suggestions and Requests / Re: More than one instance of the Project View

« on: May 08, 2006, 08:55:12 am »

Me three ... out desire was to have multiple views of same project directed towards the user (business analysts versus quality assurance analysts versus developers) where each would want to see the project from different starting points.

3

General Board / Re: Create project and backend repositories

« on: May 01, 2006, 10:54:08 am »

David, thanks very much, but I'm still not getting it....

So, we create a project on a local (or networked) drive, set the base stuff up, then at some point we transfer the project model to the repository?

We do this for EVERY project we are creating?

ok, assuming I have 50 active projects and they are in the repository and now I want to open one up and do some work on it.  There is no way (other than me knowing the project's name) to get a list of what's in the repository ... no Browse the Repository to find a project ... feature?  

Ouch...

4

General Board / Create project and backend repositories

« on: May 01, 2006, 07:17:05 am »

We are new to EA and intend to implement using an Oracle DBMS repository.  We are completely confused about "create project" in the repository.  It's not an easy task.  Are we missing something?

We start with connect to server, this eventually end up wtih the Connection name and type dialog (although I complete this, I NEVER see this list of connections saved anywhere and each time I need to connect, I need to complete the connection dialog box over and over again).  We were under the assumption that by saving the connection, we could return to our list of connections (we intend to have the production repository, the training repository and the sandbox repository), choose one and be presented with a list of projects available from the repository defined by the connection.

Then, there are several paths to creating a project, some go straight to a file system view and ask where do I want to place my .eap file while other go into the what type of base model to I want to use to populate this project with.  If we are creating our project in the repository, why is it asking for a location to the eap file (or am I missing something fundamental here).

I cannot seem to find any white papers or help that clears this up for us.  We have over 100 developers and until we figure this out, we cannot deploy EA.

Help