• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

How to simplify sequence diagram?

 
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I found my sequence diagrams are very long and in a mess. I will be crazy soon. Dear experts with successful SCEA experience, how to simplify sequence diagram?

1 Should I list every relevant JSPs's name in a sequence diagram? Or can I give them a uniform name: JSP(or web pages, or frontend)?

2 Should I involve every relevant VOs or List of Vos?

3 Should I omit not important return arrow?

4 Should I omit detailed alternative? E.g. if system cannot search out flights which are according with search conditions, have to return previous web page

5 Should I omit not important validation? E.g. user does not input for mandantory fields.

6 I do not know the taste of the person who will mark my submission, but you know already. If I know what is they really want to see in sequence diagram, I will do it better.
 
Ranch Hand
Posts: 1902
Hibernate Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Aside from the fact that I won't answer #6 since that would seem to me (even if I were to know the answer) like giving you too much help...

My advice is to do as much detail as is necessary to be both UML compliant and to explain what you're trying to diagram. Any less will certainly lose you credit for the diagrams (as you will not be explaining what your developers need to do) and any more probably won't hurt, but will be extra effort on your part.

Use your judgement as your guide.
 
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
My suggestion would to take a step back and think from a higher level. If the different possible answers to those questions affect your architecture then you should depict your answers to those questions in your design.

Just my 2 cents...

Regards,
Sourav
 
Vichy Yao
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks.

Theodore, I don't agree with you. Architect is not designer. If architect need do the detail design, what will designer do? As an architect, you must focus on service level requirements, in addtion with business requirements.

I read this paragraph of Cade & Simon's book again...
What does it mean to create an architecture? It means that you have created a software infrastructure that addresses the service-level requirements that have been identified for the system. For example, if the system has a service-level requirement that states no user response time will be greater than three seconds, then the software infrastructure you create must ensure that the system can meet this requirement. It also means that you have given the designers an infrastructure that allows them to design and code the system without worrying about compromising this service-level requirement.
 
Theodore Casser
Ranch Hand
Posts: 1902
Hibernate Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by vichy baby:
Thanks.

Theodore, I don't agree with you. Architect is not designer. If architect need do the detail design, what will designer do? As an architect, you must focus on service level requirements, in addtion with business requirements.



If you'd look at what I said, I simply suggested to include the amount of detail that you feel you need to convey what you're trying to diagram. I did not suggest doing 'the detail design' that is the developer's job, but rather including the amount of detail to your information that is needed to convey the structure sufficiently.

I happen to agree - the architect is not the same role as the developer. I think you just misunderstood what I was trying to say.
 
Why fit in when you were born to stand out? - Seuss. Tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic