OMG-OCSMP-MU100 & 200 Exams | 200 Questions And Answers Already Graded A+

What is the Purpose of an IBD? - Display the structure of a single block and display usages of a block with part properties and reference properties. What does an IBD convey? - The structure of a single block, services provided or required by parts, and types of matter data and energy that can flow across connections. 2 Diagrams that show complementary views of a block - IBD and BDD Allowable Model Element for IBD - block What is a connector? - Used to show specific connections among the internal part properties and their connections to external reference properties. What is a part property? - It is an internal structural element of a block. It is seen as a solid boundary rectangle with name : type [ ]. Multiplicity can either be in brackets or in the top right of the rectangle. What is a reference property? - It is a structure that is external to a block. It is needed by the block to invoke a behavior or service. It is represented by a dashed boundary rectangle with name : type [multiplicity]. Multiplicity can be shown in brackets or the UR corner of rectangle. What is an Item Flow? - It is used to display matter, data, or energy flowing between 2 connected flow ports. It is represented by a filled in arrowhead that is placed directly onto a connector. The type of the item flow is named in a label that floats near the arrowhead.What is Dot Notation? - It is a way to create nesting of a relationship. The block that types the property is NOT listed or the multiplicity. It conveys a structural hierarchy ownership of a property. What is the Purpose of a Use Case Diagram? - It is a black-box view of the system. It conveys the visible external structures that a system performs. It displays the actors that participate and invoke the use cases in the diagram during execution. What is a system boundary? - A system boundary is the subject of the diagram and NOT the namespace. It encapsulates use cases and actors in the diagram. It is represented as a large rectangle within the diagram frame. What is a Base Use Case? - A base use case is directly invoked by an actor. It is the primary goal of the actor. When invoked it will invoke a use case with the include relationship. It has an association relationship. What is the <<include>> relationship? - It is a UC relationship where the included use case behavior is required. Source = tail end Target = arrowhead end The use case at the source end is the base use case and the arrowhead end is the target included use case. What is the <<extend>> relationship? - It is a UC relationship where the extended use case is an OPTIONAL behavior that can be performed by the base use case. The source is the tail end Target is the arrowhead endThe use case at the source end is the extended use case and the use case at the target arrowhead end is the base use case. 3 Types of Behaviors and the Diagrams that represent them: - Activity = Activity Diagram Interaction = Sequence Diagram State Machine = State Machine Diagram 2 Elements on an Activity Diagram: - Nodes & Edges