• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

SCEA Part 2: Questions regarding UML diagrams and assignment submission

 
Saurabh Gokhale
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I have following questions regarding SCEA Part 2 project work:

1> How many UML diagrams are expected or considered to be enough to fulfill the requirements
-- I know it would depend on the problem statement but in general is there a "good/enough" count?
-- Is it expected to have only 1 class diagram capturing entire system or we can break it down into multiple class diagrams. If we can break down, how can we display the relationship between them. (NOTE: Deliverable section says Create "a" class diagram ...
-- Assignment specifies multiple use case scenarios so those many use case diagrams are must but can we have any addition to those diagrams or can we merge those diagrams due to their logical grouping?

2> Also as per assignment requirements, the submissions should have HTML pages only. Can we add an explanation in plain English for the diagram below the diagram itself on the page?

3> Can there be only 1 big HTML page or every diagram type can have its own page ? or it doesn't matter?

4> In general what precautions should be taken while submitting assignment?
 
k space
Ranch Hand
Posts: 104
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In general, you should keep your solution clean and precise, i.e. don't make your solution too complex - use good assumption. The difference between an architect and a designer is who knows when to stop.

In my case, I have
  • 1 x class diagram
  • 4 x component diagrams
  • 7 x sequence diagrams
  • 1 x deployment diagram

  • Other than these diagrams, I have also included sections for the overview, revised use cases, and risks.
     
    Saurabh Gokhale
    Greenhorn
    Posts: 25
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Thanks... this information is really helpful
     
    Deepak Bala
    Bartender
    Posts: 6663
    5
    Firefox Browser Linux MyEclipse IDE
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator

    In my case, I have
    # 1 x class diagram
    # 4 x component diagrams
    # 7 x sequence diagrams
    # 1 x deployment diagram

    Other than these diagrams, I have also included sections for the overview, revised use cases, and risks.


    Ditto. Also my sequence diagrams were pretty detailed. The width was pretty HUGE and I spent about 40% of my time on them.
     
    Prasanna Wamanacharya
    Ranch Hand
    Posts: 143
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Other than these diagrams, I have also included sections for the overview, revised use cases, and risks.


    What exactly did you mean by "revised use cases"? Aren't we supposed to not change anything (domain model, use cases, etc.) from the problem statement of the assignment?
     
    k space
    Ranch Hand
    Posts: 104
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Based on my knowledge of the domain business, the given use-cases seemed to be missing something. With reasonable assumption and justification, I revised the use cases diagram to clarify my thought and the proposed solution.

    The bottom-line is you must justify everything you put into your solution.
     
    P Das
    Ranch Hand
    Posts: 123
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    from my experience: better keep your class diagrams in one place (instead of dividing into manageable units as we normally do in real practice) because it may attract penalty although there is no UML guideline against "fragmenting" or specifying what is "good fragmenting".
     
    • Post Reply
    • Bookmark Topic Watch Topic
    • New Topic