ISYS 620 Appendix A
Terms in this set (37)
Unified Modeling Language
Notation that allows the modeler to specify, visualize, and construct the artifacts of software systems, as well as business models. Techniques and notations include:
1. Use cases--represent the functional requirements or the "what" of the system
2. Class diagrams--show the static structure of data and the operations that act on the data
3. State diagrams--represent dynamic models of how objects change their states in response to events
4. Sequence diagrams--represent dynamic models of interactions between objects
Allows the modeler to specify, visualize, and construct the artifacts of software systems, as well as business models. Builds upon and unifies the semantics and notations of leading object-oriented methods and has been adopted as an industry standard
Apart of Use-Case Modeling. External entity that interacts with the system. Think of DFD. Someone or something that exchanges information with the system. Represents the role the user can play. Name should indicate that role. Help you to identify the use cases they carry out
A part of Use-Case Modeling. Sequence of related actions initiated by an actor. Represents the specific way to use the system. Functions that users want from the system. Always initiated by an actor. Can interact with actors other than the one initiated by it. Represents a complex functionality. May participate in relationships with others of these.
Diagram that depicts the use cases and actors for a system
In use-case diagramming when one use-case extends a use-case by adding new behaviors or actions
In use-case diagramming which arises when one use-case references another use case.
In Class Diagrams. Entity that has a well-defined role in the application domain and has state, behavior, and identity. Is a concept, abstraction, or thing that makes sense in an application context. Could be a tangible or visible entity. It could be a concept or event. It could be an artifact of the design process. It has a state and exhibits behavior through operations that can examine or affect its state
In Class Diagrams. Condition that encompasses an object's properties and the values those properties have. Determined by its attribute values and links to other objects. Condition during the life of an object during which it satisfies some condition(s), performs some action(s), or waits for some event(s). Changes when the object receives some event. Spans a period of time. An object will remain in one for some long period of time before transitioning. Shown like a rectangle with rounded corners.
In Class Diagrams. Represents how an object acts and reacts. Depends on its state and the operation being performed.
In Class Diagrams. Set of objects that shares a common structure and a common behavior
In Class Diagrams. Diagram that shows the static structure of an object-oriented model: the object classes, their internal structure, and the relationship in which they participate. Class is represented by a rectangle with three compartments separated by a horizontal line
AKA instance diagram. Graph of instances that are compatible with a given class diagram. Instance of a class diagram-->providing a snapshot of the detailed state of the system at any time. Object is represented by a rectangle with two compartments.
Function or a service that is provided by all the instances of a class. EX=calc-gpa in student. Only through these that other objects can access or manipulate the information stored in an object. Provide an external interface to a class without showing its internal structure or how its operations or implemented.
Technique of hiding the internal implementation details of an object from its external view. AKA information hiding.
Relationship among object classes. Can be unary, binary or ternary. Depicted as a solid line between the participating classes.
End of an association where it connects to a class. May be explicitly named with a label near the end of the association. Indicates the role played by the class attached to the near end which the name appears.
Indication of how many objects participate in a given relationship. specification is shown as a text string representing an interval if integers as a lower bound and an upper bound. Range is considered to be bound other than the upper bound when it is a * which means infinity. The options are:
1. 0...1 meaning zero to one
2. 1 meaning one and only one
which means zero to inifinity (or just
4. 1...* which means one to infinity
Process of abstracting the common features among multiple classes, as well as the relationships they participate in, into a more general class. Shown with a solid line from the subclass to the superclass with a hollow arrowhead at the end pointing to the superclass
Classes that are generalized
Class they are generalized into
Shows which property of an object class is being abstracted by a particular generalization relationship
Class that has no direct instances but whose descendants may have direct instances
Class that can have direct instances
Every instance must be an instance of the superclass only
Instance may be an instance of the superclass only
No instance can be an instance of more than one subclass at the same time
Allows a concurrent participation in multiple subclasses
Part-of relationship between a component object and an aggregate option. Stronger form of an association relationship and is represented by a hollow diamond at the aggregate end. Involves a set of distinct object instances, one of which contains or is composed of the others.
Part of State Diagrams. Changes in the attributes of an object or in the links an object has with other objects.
Part of State Diagrams. Something that takes places at a certain point in time; it is a note-worthy occurrence that triggers a state transition. EX=customer places an order. Considered to be instantaneous
Depiction of the interactions among objects during a certain period of time. Each shows only the interactions pertinent to a specific use case. Shows the participating objects by their lifelines and the interactions among those objects--arranged by time sequence--by the messages they exchange with one another.
A part of Sequence Diagrams. Depicts an object. Vertical line. Represents the object's existence over a certain period of time.
A part of Sequence Diagrams. Time period during which an object performs an operation. Thin rectangle superimposed on the lifeline of an object. Could be directly or though a call to some subordinate operation. The top of the rectangle indicates the initiation of the activation and the bottom its completion of the operation.
A part of Sequence Diagrams. Shown as a solid arrow from the sending object to the receiving object.
A part of Sequence Diagrams. A type of message in which the caller has to wait for the receiving object to finish executing the called operation before it can resume execution itself. EX=checkIfOpen. Will return with a value of "true" or "false". Always has an associated return message. Message may provide the caller with some return value(s) or simply acknowledge to the caller that the operation has been successfully completed. Some return messages are not depicted as they are implicit to the command.
A part of Sequence Diagrams. Message that transfers control from the sender to the recipient without describing the details of the communication. EX=open
Diagram that shows the software components or modules and their dependencies