Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - eAndy

Pages: [1] 2
1
drag a requirement and drop it onto a another, it will fall under the one you dropped it onto.

if you link the parent to a use case via a realization you'll see in the hierarchy window that the parent requirement 'owns' the child requirement.

2
I think I am experiencing a similar or the same problem.

I have a requirement that owns other requirements.

The parent requirement is linked (via Realization) to a use case.

When the use case detail is dumped via RTF generation it shows the parent requirement but does not show the child (owned) requirements.

I think I have to explicitly link the child requirements to the use case.

3
well, I was thinking something like this would allow you to just blast stuff in. they'd need to have configurable defaults.

Let me have drop downs and check boxes for the 80% of what I do/need. As I tab past the last column add new row (like tables in word). Don't make me click add when more than likely I'm going to.



If I'm sitting with someone and using the tool to capture info I can't be doing 6 clicks per attribute. That'll drive me nuts. Let me brain dump. If I need to tweak something I'll come back to it. But more than likely it will be the exception.

4
Suggestions and Requests / Faster Entry of Attributes/Operations
« on: May 10, 2004, 07:09:14 am »
Please understand that I love the product but have a suggestion.

It would be great to be able to quickly dump in a bunch of attributes/operations without having to use the mouse.

The interface is a bit clumsy and requires you to use the mouse and multiple operations to complete something as adding an attribute as a property.

I'd be SOOO much more productive if I could add a new attribute and expose it as a property with one single operation that didn't require me to click or answer popups.

5
General Board / How to decorate with .NET WCF Attributes
« on: September 24, 2008, 09:33:43 pm »
I want to declare a class and decorate with WCF attributes. Can I do this from inside EA?

I can see that if I reverse the code and regenerate the attributes remain but I haven't found where in EA I can see them (other than view code).

For example, I want to decorate both the class and the methods as shown below. If i decorate, reverse and re-gen they remain.

I'd like to know how to do the decoration in EA. Right now I have to define class, generate, pop to VS.NET and decorate, reverse, tweak futher and keep iterating.

      [Serializable]
      [DataContract(Namespace = "http://MyComp.com/Accounts")]
      [KnownType(typeof(ComplexAccount))]
      [KnownType(typeof(SimpleAccount))]
      public class CommonAccount : BaseAccount
      {

            public CommonAccount(){}


            [DataMember]
            public long ID (get; set;)

            [DataMember]
            public string Name (get; set;)
      }

Thank you
Andy

6
General Board / Re: CodeGen: Prevent Finalizer in C#I
« on: March 27, 2007, 06:16:59 pm »
That was it.

There's an advanced button on the Code Generation window.

If you go into "code lifetimes" its a duplicate of the Tools - Options - code lifetimes but they're disconnected and not saving the data in the same place.

I'd say dumb only b/c I haven't found a good use for it yet and its been very frustrating finding it.

I'm certain there will be a day when I'm singing its praises and calling the designers genius.

Thanks

7
General Board / Re: CodeGen: Prevent Finalizer in C#I
« on: March 27, 2007, 01:26:41 pm »
have you tried this in C#?

I've turned off the option to generate a destructor in Tools | Options | Object Lifetime, and turned off Tools | Options | C# | Generate Finalizer and turned off the Generate Dispose on the same page.

Generate code.... Whoop! there it is! A dirty no good down low nasty old destructor/finalizer.

Any other ideas?

8
General Board / CodeGen: Prevent Finalizer in C#I
« on: March 24, 2007, 04:20:52 am »
Generating code in C#.

I always get a destructor/finalizer when generating C# code.

Drives me nuts. Has always worked this way.

Typically I have to mod the code template to exclude it.

This time I want an answer if any one has one.

In the code template I see this

%if genOptGenDestructor == "T" and classHasDestructor != "T" and classHasFinalizer != "T"%

I believe the getOptGenDestructor is the setting in the Tools-Options-ObjectLifetime

Where are the classHasDestructor and classHasFinalizer.

I'm guessing they're on the class but I'm certainly missing something.

9
General Board / Re: CodeGen: Extra Var created for  Abstract Prope
« on: March 27, 2007, 01:29:31 pm »
Ah, yes.

I was creating an attribute and then marking it as a property.

I went back and
1. created an operation
2. set the stereotype to "property"
3. marked it as abstract
4. gen'd code
5. Viola! exactly what I expected, duh!

Thanks much
eAndy

10
General Board / CodeGen: Extra Var created for  Abstract Property
« on: March 24, 2007, 05:08:33 am »
Code generating in C#

Create an abstract readonly property.

When I code gen it still creates the private variable

private float _NPV;  // this shouldn't be created!!
public abstract float NPV
{

get;
}

I tried modifying the code template as shown in the red below but it doesn't work. What am I missing?

%if attStereotype == "property" and opAbstract != "T"%
\n{\npop\t//read property\n\tget{;}\n\t//write property\n\tset{;}\n}
%endTemplate%

11
General Board / C# Code Gen - Duplicate attributes
« on: October 01, 2004, 05:20:51 am »
It seems each time I generate code EA duplicates the attribute definitions.

Has any one seen this?

I've tweaked the code template and wonder if maybe its having trouble recognizing what it generated the previous round.

Properties/methods aren't duplicated, just the attribute definitions.

12
General Board / MDG Link with Multiple Projects.
« on: September 20, 2004, 06:59:19 am »
I have a VS.nET solution with 3 projects.

They all share a common root name space. SC.Platform.

I have the following package hierarchy in EA
SC
- Platform
- Business
- Data
- BPC

and once connected to VS.NET want the following pacakage structure in EA ( implies that there are a lot more projects that I want to hook up but I'm focusing on the 3 project solution dealing with SC.Platform for the purposes here)

SC (root)
- Platform
- Common ( SC.Platform.Common.CSPROJ)
- WebUI ( SC.Platform.WebUI.CSProj)
- WebControls (SC.Platform.WebControls)
- Business
- BnO (SC.Business.BnO)
- Accounting (SC.Business.Accounting)
- Data
- BnO (SC.Data.BnO)
- Accounting (SC.Data.Accounting)
- BPC
- BnO (SC.BPC.BnO)
- Accounting (SC.BPC.Accounting)

problems:
1. when I connect one of the projects in the solution to the EA model I the connect button is disabled and I can't connect the other projects in the solution to the EA Model. And unless each project in teh solution has to be connected to a different pacakage in EA I can't see how multiple projects will work. If each project has to be linked to a separate package in EA and the tool is going to do what I list here in #2 I'm screwed. It will create such a crappy structure it will be unusable. I'm hoping I'm wrong here on either account.
2. When a project is connected to the SC.Platform package in EA, the tool re-creates the SC.Platform packages under the package where its connecting so I end up with SC.Platform.SC.Platform.Common instead of it realizing that its already under SC.Platform and just creating the Common package under where its connecting.
3. when working in a team will the links to vs.net projects be maintained on other team members machines as long as they have the projects in the same places on their drives?

i think this tool has a lot of potential. It appears that some simple scenarios are given in the documentation to get the product out. It would be really nice if the some advanced scenarios could be detailed.  

We have a large project and plan to use db repository with controlled pacakage for pushing things back and forth to remote teams. I'd love to see this work but having some trouble and questions right now.

Any help is appreciated.

Thank you

13
General Board / Project Structure
« on: June 10, 2004, 11:13:15 am »
I'm looking for people experienced with large project use of EA.

We have a distributed team and we all need to stay productive.

I don't care for the default project layout that EA sets up. I realize that this is a template and I've already made a couple of other model template and used them successfully.

My questions for those experienced with large projects is how do you group your work?

My thought is to create packages and put everything underneath the package (ie. requirements, BPM, class diagrams, sequence diagrams etc.

that would allow the people working on the module to work within one specific area of the project. If they need to use classes from another model its pretty straightforward where they need to go.

Alternatively, to use it the way it comes out of the box everyone will doing massivie drill down to get to what they want and need.

MyComp
  /Module1
         /Requirements
         /BusinessComponents
         /DataComponents
         /BusinessProcessComponents
         /UI

thoughts?

Our plan is to store things in the database. Not sure how this affects things.

14
General Board / Re: Name Spaces
« on: June 10, 2004, 06:09:44 pm »
Yes, I knew that. But I thought there might have been a way to modify it.

It would be nice if the default project was more reflective of how you need to structure your project to get code compiliation to work properly with the way namespaces works.

15
General Board / Name Spaces
« on: June 10, 2004, 11:15:29 am »
I dont' understand why the default project is shaped the way it is especially given the way that code generation works.

If I put my classes under logicalView/LogicalModel the code generation puts all that crap as the namespace.

So I have to create a new root package and build my namespaces out from there.

Little whacky. Please tell me I'm wrong and that there's a simple mechanism for editing the namespace

Pages: [1] 2