|
 Company Main
Objective: Visual Modeling.
...................................................................................................................................................
Core Topic: To manage complexity, to
communicate better, document the artifacts.
...................................................................................................................................................
Key Issues: Benefits of Visual modeling &
UML.
...................................................................................................................................................
Problem:
Though considering the team being strong in their respective domain
with their capabilities catering to the developmental activity, but
there was a sense of discomfort with the pace of different team
members, thus a modeling aspect had to be introduced so that a unified
process could be maintained with better communication and to properly
document the activities.
...................................................................................................................................................
Objective:
 Cost reduction
Though the management wanted a modeling means so that the complexity
could be comprehended with a modeling language but were also sensitive
about whether if anything introduced would shoot up their prices.
Quality
Concern was about whether the tool introduced could comprehend the
complexity at different levels (and whether they could map out between
the models).
...................................................................................................................................................
Approach:
Managing Change:
Taking into account the companies need to comprehend complexity of the
application being developed, the support provided at this point was to
make them understand the concept of visual modeling and the use of
Unified modeling language using rational tools.
By reverse engineering their previously done work
and helping shore them how this complexity could be better understood
by using Rational ROSE was done by taking them thoroughly through a one
day tutorial by considering their present application.
An approach of effective communication was also
presented to increase their team compatibility using the tool for the
entire modeling.
...................................................................................................................................................
Differences:
To help them bind the technologies which they
were using with the tool and also the connectivity with their databases
for the application to run smoothly.
...................................................................................................................................................
Scope:
To have a better communication among team members
with the complexity involved.
...................................................................................................................................................
Results:
Cost Reduction:
As the approach was considered to be
convenient and comfortable, the time in communicating was considered to
come down and also the complexity to be handled effectively.
Quality:
The boost was to the quality as lot many
factors could be taken into account in modeling such as reverse
engineering, use cases, object level modeling and component level
modeling which could determine their quality early in the design cycle
with effective time utilization and better deliverability.
Business Relationship:
A better understanding with the stakeholders could be built up and an
effective modeling management could be placed with a better
understanding of the traceability of the design life cycle.
The documentation of the various activities also
was a great feature to be added on.
...................................................................................................................................................
Critical Success Factors:
Transition:
The key performance indicator during transition was better
communication and reduction in man-hours thereby increasing their
standard.
Post Transition:
When the transition stage was finished, other key performance
indicators was mapping their technology related with UML, helping them
understand the traceabilty with the various tools and help them with
their data base connectivity.
...................................................................................................................................................
Bottom Line:
The transition from a traditional method to a use case driven
development approach was successfully integrated to their system.
|
