“Goal-Oriented Modeling”

“Goal-Oriented Modeling” Please respond to the following:

• Suppose someone made the claim, “There is no difference between modeling the system-as-is and the system-to-be”. Provide three reasons to support or refute this claim.
• From the e-Activity, provide your opinion as to whether the extension from the article makes it easier or harder to build models compared to using plain UML. Provide a rationale.
•  The purpose of use-case models is to provide a description of the problem domain.  The use case descriptions and diagrams provide a formal definition of the external behavior or functionality of the business processes.  These provide a logical view of the system.  In the design phase a physical view of the internals of the new system are modeled.

Classmate:

Suppose someone made the claim, “There is no difference between modeling the system-as-is and the system-to-be”. Provide three reasons to support or refute this claim.

There is a difference between modeling a system-as-is and modeling a system-to-be.  First, the system-as-is is a system that is no longer useful because it is not meeting all the needs of end-users.  For example, the system-as-is may be meeting needs for which it was intended but, due to change in business directions, end-users have new needs that need to be satisfied.  Second, it allows the requirements engineer (RE) to define a preliminary model of the stable business goals that must be incorporated into every system (Lamsweerde, 2009).  Third, modeling the system-to-be, by expanding on the preliminary model, enables the RE to build a new system that can better meet user needs and enable the organization to achieve new business objectives.

From the e-Activity, provide your opinion as to whether the extension from the article makes it easier or harder to build models compared to using plain UML. Provide a rationale.

The profile extension in the article does make model building easier.  It uses symbols that are more distinctive but also have similarities to UML diagrams.  For example, one of the three main concepts are actors (Abid, Amyot, Som´e, & Mussbacher, n.d.).  They are considered to be similar to actors within use case diagrams that interact with the system in some way.  The profile extension also defines categories of links for different types of relationships. For example, decomposition links are used to break down elements into sub-elements for better understanding and contribution links indicate qualitative or quantitative impacts between one element andanother.  In addition, the extension profiles dependency links to describe the dependencies that one actor has on another (Abid, Amyot, Som´e, & Mussbacher, n.d.).