5 replies to this topic

[Christopher87]

Hi there folks,

I recently introduced myself to the community and it was suggested that I open a new thread to discuss UML (Unified Modelling Language).

I have had some experience of UML in the past, but it has completely slipped my memory due to a shear lack of use. I would be grateful to hear of some quick and easy ways to get back into the idea of using diagrams to represent programs prior to coding.

Chris

[LuthfiHakim]

Hi Christ,

UML was designed to address the need for communication of different roles in software projects with people of different backgrounds. Therefore there is no single diagram "language" in UML. For example, there is a class diagram "language", which people in marketing department will not care. But there is diagram to show specifications, the basic components of the projects, and use case (which showing how users could use the project) which can easily read by people from marketing to "translate" into their area.

Based on your post, I believe you are approaching from programmer's point of view. In this case I believe you need to start with Requirement model, and then continued by Use Case model. Some would find Component model also helpful in planning stage. Note that this is not official, just my best practice from my own experience.

[Christopher87]

Unfortunately, the model references you mentioned ring no bells in my memory. Obviously, they'll be covered in the book that I have. However, I don't really have the time to absorb the UML book and study my current university modules.

Do you know of any quick-start references on the web?

Many thanks

Chris

[LuthfiHakim]

I don't know if this tutorial helpful, I haven't read it in a long time. Note that the tutorial is from a company producing commercial UML tool. Although I like the tool, but I don't have any relation with them except as an ordinary user of their product.

[Christopher87]

LuthfiHakim said:

I don't know if this tutorial helpful, I haven't read it in a long time. Note that the tutorial is from a company producing commercial UML tool. Although I like the tool, but I don't have any relation with them except as an ordinary user of their product.

Thank you for the reference. However, I don't think UML is going to be something to focus on too much in the next two weeks. I have a small programming project due to be handed in in the middle of January at university. Small enough that psuedo-code should cover the design. I would find tips on psuedo-code more useful perhaps. I'll look around the forum.

[artificial]

Try this website: Link :p

Greets,
artificial