|
|
| |
| |
Authors: Dan Drislane & Neal McWhorter
Today’s business analyst is
expected to do much more than just document business requirements
and perform rudimentary analysis tasks. The BA is now equipped
with the skills and tools required to thoroughly express
the requirements for a new system to be built (or a legacy
system to be enhanced) without any loss of business vision,
intended business behavior of the system, business policies
to be observed and user experience to be realized.
|
 |
| |
Authors: Neal McWhorter
With organizations giving high priority
to maturing their business analysts’ skills, opportunities
exist to reflect on the maturity of today’s business
analysis best practices and their relation to an organization’s
capabilities. A business analysis maturity model is helpful
to organizations as they work to increase business analysis
capabilities in ways that directly impact their bottom-line..
|
|
| |
Authors: David Heidt
This white paper discusses the increased
pressures on today’s business analysts and introduces
the concept of a business analysis framework and related
components. It ties this new framework approach for business
analysis with the need to have a maturity model to help
organizations progress towards business level specifications
development.
|
|
| |
Authors: Neal McWhorter
This chapter of the recent book,
Business Rules Revolution, outlines an integrated approach
that works to obliterate the old business/IT divide and
bring the business back into direct control of its business
specifications for increased business agility and reduce
IT rework.
|
|
| |
Authors: Vince Beggs & David Heidt
How can organizations eliminate a
gap that causes significant business risk and unnecessary
expense: the gap between Business Process Analysis (BPA)
and Object-Oriented Analysis and Design? It has been difficult
for businesses to efficiently design and describe their
business processes for easy use by IT departments and contractors.
Enterprise Agility calls this problem the Language Barrier,
and it has far-reaching and significant effects on organizations.
Enterprise Agility utilizes a method to help organizations
break this barrier down through the consistent use of modeling
techniques and communication mechanisms. Recently have tools
like Casewise’s Corporate Modeler and IBM’s
Rational Requisite Pro have matured enough in their integration
capabilities to allow the practical, full-scale integration
of BPA and OOAD techniques and methods.
|
|
| |
Author: Daniel Drislane
What every organization shares in
common is something almost all professionals recognize but
surprisingly few truly grasp: business rules. Rules are
the most pervasive operational component of virtually every
organization in the world, whether for profit or not, whether
mom-and-pop or global player. But to say this shouldn’t
imply that every organization understands the rules governing
their business, or even how rules are developed and deployed.
Few companies realize how they can harness rules to deepen
their customer relationships, improve quality, and increase
profit. This paper summarizes how Enterprise Agility has
leveraged Rational Rose to help our clients model and analyze
their business rules. We explain the benefits of using Rose,
how we have adopted Rose to meet our clients’ specific needs,
and how the Rose analysis environment fits into a larger
business rules program. |
|
| |
Author: Daniel Drislane
Organizations today face a variety
of challenges when endeavoring to plan and implement a software
development lifecycle methodology and the many best practices
that can make up such a methodology. Despite a plethora
of innovative analysis and planning tools, some of which
are well integrated, IT organizations face a daunting task
when trying to meld these tools into a cohesive and well
understood development methodology. This paper is about
why software development methodologies don’t work and why
they sometimes do, including a few ideas about how to turn
around your own methodology efforts. The author identifies
eight common myths and explains in detail how to avoid common
pitfalls when implementing methodology in an IT organization. |
|
|
|
Author: Daniel Drislane
While a project must have good analysis,
pragmatic risk assessment, a sound business case and reliable
measurement tools if it is to have any hope of succeeding,
business processes and business requirements are also a
key to success because they are inextricably linked to a
company’s vision and the project itself. Closely coupling
business processes and the business requirements of a new
application are not only desirable, they are inherently
critical. Business software applications are tools to aid
business processes. This important relationship is a key
factor in successfully completing software projects, and
why its most prominent stumbling block, the communication
gap between users and the IT community, is responsible for
a large proportion of project failures.
|
|
| |
Author: David Heidt |
|
| |
Author: Daniel Drislane
This paper discusses a few of the
obstacles that companies must overcome if they wish to be
successful with Customer Relationship Management. It also
discusses the importance of the voice of the customer and
how this trait should thread its way through the entire
CRM development process, which is discussed in detail. Last,
it explains the role of the voice of the customer in powering
a different brand of CRM: Personalized Relationship Management. |
|
|
