locked
UML do i really have to? RRS feed

  • Question

  • User-1562954909 posted

    i mean what if i add my classes to the project whenever i have to without documenting my work,i'm still a junior i dont have to give orders etc ,so what do you think according to your experience in the field

    thanks
     

    Tuesday, April 20, 2010 5:21 AM

Answers

All replies

  • User-1535021499 posted

    You should document all newly added or updated classes. What if you yourself do not remember which classes were added or modified and for what, other scenario is what if your peer wants’ to add similar class how will he come to know which ones are added or modified.. This will spoil your project and lead to  redundant and corrupt code to some level.  Finally managing/maintaining the project in future will be a nightmare.

     

    Tuesday, April 20, 2010 8:38 AM
  • User-389939489 posted

    i mean what if i add my classes to the project whenever i have to without documenting my work,i'm still a junior i dont have to give orders etc ,so what do you think according to your experience in the field

    There is a threashold, quasi-proportional to how many lines of code there are in the project, past which even the original coder is no more able to cope with the "mess". That is why, UML or not UML, if you want to develop anything non-trivial, you need a disciplined approach.

    That said, about UML: surely useful for modelling some aspects of a system, OTOH I'd remind Ambler's "Just Barely Good Enough": http://www.agilemodeling.com/essays/barelyGoodEnough.html

    Best luck,

    -LV

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, April 20, 2010 8:57 AM
  • User-952121411 posted

    In my experience there are a select number of UML diagrams that are quite useful and do help give a visual design of the system.  There are even some fancy tools from the IBM Rational Suite (Rational Rose) that will engineer the code from a well constructed UML diagram.  These tools are expensive and may only be used with larger software teams, but they do have their place if used correctly.  You might be thinking of the "Class Diagram" which I do find useful in explaining the design.  Of coarse with anything there are pros and cons.  I might not get into modeling a system that is a 1 page ASP.NET application with a finite scope; it is not worth the effort with a huge workload to accomplish. There is a ton of buzz on people's opinion as to if UML is useful; take a look at a few of these links to help you shape your own opinion:

    Is UML Important?

    http://codebetter.com/blogs/jeremy.miller/archive/2006/07/05/147119.aspx

    Is UML on the way out?

    http://www.codingthearchitecture.com/2008/04/03/is_uml_on_the_way_out.html

    Do you find UML useful?

    http://forums.devx.com/archive/index.php/t-19556.html

    UML: The Positive Spin:

    http://archive.eiffel.com/doc/manuals/technology/bmarticles/uml/page.html

    Are UML tools useful?

    http://discuss.joelonsoftware.com/default.asp?joel.3.202235.27

    Is Uml Useful:

    http://www.dreamincode.net/forums/topic/159182-uml-how-useful-is-it-really/

    ...and a MSDN reference site:

    Developing Models for Software Design:

    http://msdn.microsoft.com/en-us/library/dd409436(v=VS.100).aspx

     

     

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, April 20, 2010 10:56 AM
  • User-389939489 posted

    Informatics shouldn't be a matter of opinion or buzz, nor you will learn it by reading the blogs, the vendors' sites, and the fake gurus.

    Best luck,

    -LV

    Wednesday, April 21, 2010 7:09 AM