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.


Topics - DMT

Pages: 1 2 [3]
31
General Board / Searching HTML Documentation
« on: May 22, 2003, 06:17:40 am »
During QA, our test engineers will mark the bug with a unique identifier relating to (typically) the use case the bug refers to, or perhaps the requirement or UI element.

I'd like the developers to be able to use the HTML documentation instead of the Word-based documentation they use now, but they'd need to be able to search for "UC132" for example, since they may not know where the use case resides in the hierarchy

32
General Board / Specify Class Visibility in 'Type' List?
« on: May 20, 2003, 08:21:22 am »
Hello, all.  I am building a model using the ICONIX process. I've created a domain model using classes that represents my "domain vocabulary," used during the writing of my use case text.

Now, I'm starting work on my class model. There are two options here:

1. Create new classes that match the names on the domain model, but are not linked to the classes on the domain model. Benefit is that I can see a complete list in my class diagram, since there will be some classes that are not in the domain model. Drawback is that both classes in the domain model as well as the class diagram appear in the "Type" combo box when adding attributes.

2. Create links in my class diagram to the classes in my domain model. Benefit is that there is only one copy of each class that shows up in the Type list. Other benefit is that the names will match what's in the domain model. Drawback is that the package name appears in the title of the class, which I don't necessarily want to see. Other drawback is I have to manually change the appearance settings in the domain model to hide all of the attributes and operations. (In the domain model, I want to see a simple box with the class name and nothing else.)

My questions are:
1. What is the recommended method? 1 or 2?
2. If 1 is the recommended method, is there a way to specify visibility for classes in the Type combo box?
3. If 2 is the recommended method, is there any way of getting rid of the package name in the title of the class, or do I just deal with it? Also, is there an easy way to hide attributes and operations for more than one class at the same time in my domain model?

Thanks!

33
General Board / ICONIX Discussion Groups Anywhere?
« on: May 21, 2003, 05:55:29 am »
Does anyone know of any discussion groups specific to the ICONIX process?  I'm finding that I have lots of questions as I work through the process, and would love to be able to pick the brains of other people using the ICONIX process.

34
General Board / Any way to set default database type?
« on: May 15, 2003, 09:17:30 am »
I've searched the message board and haven't found an answer to this one, so I thought I'd ask.

Is there any way to set the default database type as a system option, preventing you from having to select it for each and every table you add?

It seems like this must be an option somewhere.  Perhaps I'm just missing it.

35
General Board / Where to place detailed UI requirements?
« on: May 15, 2003, 01:49:17 pm »
I've just started using EA, and I'm really excited about using this tool to manage our complete set of requirements and analysis information. For the first half of our project (really the 1st of 2 subsystems), I used use cases to some degree, but the vast majority of functionality was described by simply placing a screen capture in the document and describing all of the behavior and interactions in the context of the on-screen controls.

Now, with the use of MANY more use cases, I can see that about 90% of what I was outlining in the "UI-centric" requirements documents can be captured in the use cases. However, there are some things that still seem like they need to be described elsewhere. Examples:

- "The Total Cost text box shall be read-only and shall appear with a background color that matches the form's color."
- Describing the shortcut keys for all of the controls.  I.e., pressing ALT-N will place the focus in the Name text box.
- "The category combo box shall have two columns. The first shall display the category abbreviation. The second shall display the category name. The list shall be sorted alphabetically by category name."
- "When the employee list is displayed, the Vacation Time column shall be blank for any employee row where the employee has been employed for less than six months."

I've seen someone suggest "View XXX" use cases to capture this sort of information. For example, "View Category Drop-Down List."  However, this seems to break the "don't couple your use case descriptions to exactly how the UI is designed" rule.

Does anyone have any practical advice on how to capture these nuances (which are typically down to the individual control level) using EA? I'm really dreading creating a separate UI spec that is external to EA, since I then lose the ability to cross-reference within EA.

36
General Board / Customize Toolbox to Use "invokes" and &
« on: May 14, 2003, 08:18:38 am »
We're using EA with the ICONIX process, which utilizes "invokes" and "precedes" stereotypes in use case diagrams instead of "includes" and "extends."

Right now, I have to manually change the stereotype for each link I add in my use case diagrams. Is there a way to customize the toolbox somehow to allow me to select invokes and precedes as the link type?

Pages: 1 2 [3]