Author Topic: User Interface Diagram Common Menus Question  (Read 1910 times)

mmahon512

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
  • TriathlonJunkie
    • View Profile
User Interface Diagram Common Menus Question
« on: July 31, 2007, 05:20:04 am »
Hi, I am working on a user interface design document for a web application.  My question is my forms will have a few common menus across all screens.  What is the best way to go about representing that using the extended user interface diagram?

I am not sure if this is the right way to do this but I went through my customers initial request and created a requirements model.  I created and grouped all the requirements in a semi-logical fashion, commenting heavily my thoughts on each requirements.  After that I started working up an Data Model laying out the tables and columns required to capture the needed requirements.  Now I am working on screen shots for the customer and I found out that I can link the screens to the requirement that it fulfills on the requirements document.  That in turn lets me also display the requirement being fulfilled on the UI diagram for the corresponding screen.  It creates a Realizes line?!?  I am assuming that means that this screen realizes or fulfills the requirement.  If I am not using this in the right way please someone help me out.  If feels logical and relevant though, being able to show the customer the UI model and also emphasize how the screen fulfills the requirement.

Thanks,
Mike
« Last Edit: July 31, 2007, 06:51:15 am by mmahon512 »

Martin Terreni

  • EA User
  • **
  • Posts: 672
  • Karma: +0/-0
  • Sorry, I can't write
    • View Profile
Re: User Interface Diagram Common Menus Question
« Reply #1 on: August 01, 2007, 06:54:53 am »
1) As for the common UI elements, we use a "foundations" root model with all common controls and forms of our systems (including tool bars and so). Then to reuse it we copy and paste it as link, if we wont the diagram to be updated with every change of the source, or as new, if it is a variance not to be directly related to the source.This way we can reuse a lot of UI design through the models.

2) As for the requirements connection, IMHO it is the right way. Also if you try to create a requirements from within the element and then export it this is the link you'll get.

Enjoy :)
Martin
Recursion definition:
If you don’t understand the definition read "Recursion definition".