Lab Assessment – 10

Slot : A1
Name of the Student : ANCHIT AGARWAL
Registration Number : 19BCE2279
Title: Agile Modeling
Objective: To identify the various aspects of Agile Modeling (AM) viz. Purpose Fulfilment,
Understandable, Accurate Sufficiently, Consistent and Provide Positive Value for the given
scenarios

Background:
To understand AM you need to understand the difference between a model and an agile model. A
model is an abstraction that describes one or more aspects of a problem or a potential solution
addressing a problem. Traditionally, models are thought of as zero or more diagrams plus any
corresponding documentation. However, non-visual artifacts such as collections of CRC cards, a
textual description of one or more business rules, or the structured English description of a
business process are also considered models. An agile model is a model that is just barely good
enough. But how do you know when a model is good enough?

All activities are collectively termed Agile Modeling activities.

Problem Description:
Identify the Agile Modeling activities associated with each of the following scenarios:

A. Sometimes you model to communicate; perhaps you need to communicate the scope of your
effort to senior management; and sometimes you model to understand; perhaps you need to
determine a design strategy to implement a collection of Java classes.
B. A requirements model will be written in the language of the business that your users
comprehend, whereas a technical architecture model will likely use technical terms that
developers are familiar with.
C. If a street map is missing a street, or it shows that a street is open but you discover it’s closed
 for repairs, do you throw away your map and start driving mayhem through the city? Likely
not. You might decide to update your map.
D. If a use case clearly invokes another in one of its steps, then the corresponding use case
diagram should indicate that with an association between the two use cases that is tagged
with the UML stereotype of <<include>>.
E. An architecture model helps to solidify the vision to which your project team is working,
which clearly has value. Perhaps it was unwise to invest $100,000 developing a detailed and
heavily documented architecture model when a $5,000 investment resulting in whiteboard
diagrams that you took digital snapshots of would have done the job.

Scenario Suitable Aspects of Justification

Agile Modeling

A To be effective, an agile model must

Purpose Fulfilment
specifically serve the function for which it
was designed. Hence, “purpose fulfilment”
would be the best aspect of agile modeling
for this scenario.

B Agile models are better understood by their

Understandable
target audience. Notations used in the
documentation should be understood by
intended people. Hence, “understandable” is
best suited for this scenario

C The reason you don't throw away your street

Accurate Sufficiently
map the moment you notice an error is that
you don't intend or want it to be errorless.
Sufficient accuracy is determined by both the
model's intended audience and the problems
that it is attempting to resolve. Hence,
“accurate sufficiently” is best suited for this
scenario.
D To be efficient, an agile model does not need
Consistent
to be completely compatible with itself or
with other things. There may be some
inconsistencies e.g. using different names for
actors in a use case diagram. Inconsistencies
can be ignored based on their impact in the
understanding of the diagram. “Consistent”
suits this scenario the best.

E The most basic aspect of any agile model is

Provide Positive Value
whether it’s providing any positive value or
for the given scenarios not. We should think if the advantage which
the architectural model is giving, exceeds the
expense of building it and maintaining it.
Hence, for the given scenario, “Provide
Positive Value for the given scenarios” suits
best.