![]() |
subject > representation > coding technique > diagram > UML diagram > class diagram > informal class diagram |
![]() ![]() | ||||
informal class diagram | ||||
subject | fact |
informal class diagram | does not model software that will be developed | ![]() |
helps in understanding the domain | ![]() | |
is a subtopic of 5.8 - The Process Of Developing Class Diagrams | ![]() | |
is part of exploratory domain model | ![]() | |
is a kind of class diagram | ![]() | |
may be created while performing domain analysis | ![]() | |
usually contains classes, associations and attributes that are outside the scope of the system | ![]() | |
class diagram | can generate an infinite number of instance diagrams | ![]() |
describes the data found in a software system | ![]() | |
has part OCL statement in a class diagram | ![]() | |
is an important tool for requirements analysis and design of object oriented software systems | ![]() | |
may show attributes and operations contained in each class by dividing a class box into three smaller boxes: the top box contains the class name, the middle box lists the attributes, and the bottom box lists operations. | ![]() | |
may show that a class has no attributes or operations by showing an empty box | ![]() | |
shows the services offered by components and the main data to be stored | ![]() | |
UML diagram | see also Unified Modelling Language | ![]() |
diagram | has advantages it conveys or summarizes complex concepts or mechanisms more easily than other techniques | ![]() |
has problems | ![]() | |
should have a label if its meaning is not obvious, using a caption or pop-up label that appears when the user moves the mouse over it | ![]() |
Next class diagram: system model class diagram Up: class diagram