After spending time in understanding syntax of OOPS languages, it becomes imperative to enter the real world and understand how efficiently problems are mapped to behavior of OOPS objects. At many workstations, this is achieved via a language platform UML.
UML stands for unified modelling language, which via pictorial representations tries to resolve the possible states of the process.To appreciate this language more, lets have a quick recap of some important terms:
1. Abstract Class: No implementation method defined for an operation
2. Actor: Role taken by user while invoking a use case
3. Classifier: A category of UML elements that have some common features
4. Containment by Value: An object contains another object
5. Containment by Reference: An object contains a pointer to another object
6. Join: A point in an activity diagram where several concurrent flows synchronize, waiting until all are complete before continuing with a single flow
7. Namespace : A context in which an identifier exists
8. Package: Grouping of classes with related functionality
9. Template: A class that accepts a compile-time parameter defining the type to be used within the class
Links for reference:
1. Discuss the interacting objects while writing SW for a telephone answering machine.
2. Will this technique be helpful for dynamic or digital models?