Which of the following is not presented in an activity diagram with swim lanes? 1. The actors which participate in the scenario. 2. The decision points and possible paths though the business logic being illustrated.
3. The steps that mark the beginning and end of the activity.
4. The dependence of the scenario being illustrated on other scenarios or requirements. 5. Short explanations of the activity performed at each step. - -4 - The dependence of the scenario being illustrated on other scenarios or requirements.
-True | False An activity diagram can have multiple entry and exit points. - -False: An activity diagram has
a single entry point denoted by a single filled circle. The diagram has one or more exit points, each denoted by two concentric circles.
-What are the four reasons for utilizing UML modeling in a software development process? - -"A picture is worth a thousand words". Compared to written word, the graphical representation of the system's structure is much easier to build and communicate.
UML models provide a medium for team problem solving. The models provide a basis for describing the software system among design team.
UML models allow the team to easily experiment with different design solutions. Modeling is an inexpensive way to describe and contrast different design alternatives.
Modeling reduces risk and development costs. Problems with the design can be identified (visualized) before code is written.
-Discuss in a short paragraph what the arrowhead on the following relationship suggests. - -The arrowhead indicates direction of navigation of the relationship also called navigability. The driver can reach, or navigate, to its vehicle, but the vehicle cannot navigate to its driver. During construction, the significance is that the Driver class will maintain an instance variable referencing an instance of the Vehicle but the Vehicle will not be able to reach its associated Driver instance.
-Discuss in a short paragraph the most significance difference between these two relationships from a modeling point of view. Not from the domain point of view although you can illustrate you point using these objects as an example. - -Driver - Vehicle: describes an association relationship between Driver and Vehicle. This is a more relaxed relationship. Although the driver maintains a reference to the vehicle, it does not imply that the vehicle is "part of" the driver. When we remove the driver, we do not need to remove its associated vehicle. Vehicle - Engine: describes a composition relationship between Vehicle and Engine. Composition implies "part of" or "owns". This means that when the owning object is removed, each of its composite (owned) object should also be removed. In this example, when the vehicle is removed, its engine should also be removed.