Welcome to the "PRIDE" Methodologies for Information Resource Management (IRM). This product includes three methodologies: "PRIDE"-EEM (Enterprise Engineering Methodology) - used by business analysts to model the business, determine information requirements, and calculate an Enterprise Information Strategy. "PRIDE"-ISEM (Information Systems Engineering Methodology) - used by Systems and Software Engineers to design enterprise-wide information systems. "PRIDE"-DBEM (Data Base Engineering Methodology) - used by Data Base Engineers and DBA's to design an integrated corporate data base. "PRIDE" also includes a Project Management (PM) system and an Information Resource Manager (IRM) to catalog and cross-reference information resources.
WHY WAS "PRIDE" CREATED?
"PRIDE" was created based on MBA's experiences in managing large
IS/IT departments where it was necessary to bring uniformity and
consistency to development efforts in order to improve productivity. The
problems experienced by IT organizations today are essentially no
different than they were in the early 1970's when "PRIDE" was first
introduced:
Understanding the enormity of the situation, MBA studied various
disciplines to develop other types of products that are much
more tangible than information resources. As such, MBA considered
the Five Basic Elements of Mass Production:
In studying production processes, MBA came to the conclusion that:
Productivity = Effectiveness X Efficiency
Most people fallaciously equate productivity with efficiency, which simply
gauges how fast we can perform a given task. Effectiveness, on the other hand,
validates the necessity of the task itself. There is nothing more unproductive
than to do something efficiently that should not have been done at all. An
industrial robot, for example, can efficiently perform tasks such as welding. However,
if it welds the wrong thing or at the wrong time, then it is counterproductive. It therefore
becomes important in the production of any product to define Who is to perform
What work, When, Where, Why, and How (we refer to this as "5W+H").
From this, MBA devised a set of integrated engineering/manufacturing concepts
for the development and control of information resources. These concepts
became the foundation of the "PRIDE" methodologies. MBA then played the role
of "Industrial Engineer" and detailed the production process (methodologies) in
terms of the steps and sequencing of work, defined deliverables, and review
points. By doing so, MBA defined the expert craftsman's rules for developing
information resources. In other words, "PRIDE" does not do anything more than
what a good IRM craftsman does already.
WHAT MAKES "PRIDE" UNIQUE?
The strength of "PRIDE" rests in its integration of concepts
and philosophies, all of which are based on common-sense engineering
and manufacturing concepts that have stood the test of time and have
been applied to just about every field of endeavor imaginable around
the world. This engineering/manufacturing approach is what distinguishes
"PRIDE" from other CPA-based or programming related methodologies. The
concepts embedded in "PRIDE" and its approach to development were also proven
unique in a court of law (Trade Secret litigation: M. Bryce &
Associates vs. Gladstone, et al ). Because of its integration, a
company can either use "PRIDE" in its entirety or in selective pieces
and evolve into other parts of the product over time.
The emphasis in "PRIDE" is on design correctness and the production of a
quality product. Each methodology consists of a work breakdown structure
consisting of phases, activities, and operational steps (tasks), each
specifying Who is to perform What work, When, Where, Why, and How
(5W+H). The work breakdown structure is based on producing
specific deliverables that can be reviewed and inspected to verify
completeness, thereby assuring a quality product is produced. The
deliverables can take many forms, be it a report, source code, data base
structures, etc.
The structure and sequencing of the methodologies were not randomly devised
such as the classic linear "water-fall" approach to programming. Instead,
the "PRIDE" methodologies are based in the information resources affected;
for example:
EEM - Phases map the logical and physical organizational structures.
ISEM - Phases map the system structure being developed.
DBEM - Phases map the logical/physical data base models.
Although "PRIDE" includes forms to document information
resources, flowcharts, and to estimate time and costs, it is most definitely not
a "forms driven" system. Instead, "PRIDE" is a way of thinking and
looking at information resources. This is why we refer to it as
"Software for the finest computer - the Mind." A "forms driven"
methodology implies that if you fill out forms in a specific sequence,
the desired work product, such as a system, will be automatically
produced. We consider this a fallacious concept. "PRIDE" views
documentation as a working tool and a by-product of the development
process, just as blueprinting is to an architect. The processing of
forms will not make a person a better Systems Engineer; the person must
understand the process and the rationale by which it is based. Only
then will they be able to channel their energies effectively and
produce superior results.
"PRIDE" is intellectually honest. We have gone to great extremes to
define our terms and concepts. We believe Information Resource Management
(IRM) to be a science, one that can be taught. To do so, one must define
their terminology and explain their concepts, which is why we have done
so. One by-product from defining our terms is that companies can standardize
and communicate with a common language, thereby avoiding the "Tower of Babel"
effect that commonly plaques most application development organizations.
"PRIDE" recognizes development tools and techniques will change over time
as technology changes. As such, it provides for a myriad of outside tools
and techniques to be used throughout the methodologies, just as an assembly
line allows such devices. Regardless of the marketing hyperbole of the computer
industry, there is no single product on the marketplace that can do everything
for everyone, in all situations. An overriding theme in "PRIDE" is that "if
there is anything in life that it constant, it is change." Techniques and tools will
come and go, but the assembly line process will remain constant.
"PRIDE" requires a change of focus and orientation. Instead of
concentrating on programming, "PRIDE" is concerned with the overall
architecture of a system. Due to its orientation towards
up-front work, programmers become the beneficiaries of better
specifications and, as such, improves their productivity. Due to
the organization and discipline of "PRIDE", it can even make
semi-skilled workers produce superior results. In the hands of
a competent manager, we have never seen "PRIDE" fail.
CORPORATE PROFILE
M. Bryce & Associates (MBA) is an international management consulting firm
specializing in Information Resource Management (IRM). The "PRIDE" methodologies
have been used worldwide in every field of endeavor imaginable:
Countries Served:
Industries Served:
In particular, "PRIDE" products have been used extensively by firms
throughout Japan, including several companies who have received the
prestigious Deming Prize for quality.
"PRIDE" is a universally applicable approach that can be used in any company,
on any information system, in any cultural environment, and is not restricted
to any particular computer platform, data base, language, or programming tool/technique.
Since 1971, MBA has never failed to meet a customer implementation commitment,
regardless of the customer's geographical location or training requirements.
Through the "PRIDE" product line, MBA has established several precedents and
introduced many new concepts to the industry:
While many of MBA's competitors have come and gone, the "PRIDE" product line enters
its fourth decade of use. This is a testament to the integrity and durability of
the product and the company who produced it.
"With almost 1,500 installations worldwide and the
fact MBA has existed in the methodology world for almost
20 years, it is fair to say that the company is well
capable of managing its revenues and balancing them off
with consistent research and development by investing
about 80 percent of those revenues into R&D."
- DATAPRO
IRM: THE CONCEPT
"PRIDE" is an important part of an overall corporate program
for Information Resource Management (IRM). The underlying
philosophy behind IRM is to design, inventory and control all of
the resources required to produce information. When
standardized and controlled, these resources can be shared
and re-used throughout the corporation, not just by a single user
or application.
There are three classes of information resources:
INFORMATION RESOURCES
These three classes of information resources provides the
rationale as to why there are three complementary
methodologies within "PRIDE".
3 METHODOLOGIES
Each methodology consists of a series of defined phases,
activities and operations. Laced throughout the methodologies
are defined deliverables and review points to substantiate
completeness and to provide an effective dialog between
management and developers. The methodologies promote design
correctness and the production of a quality product.
IRM/MRP ANALOGY
The concept of IRM is actually no different in intent than
"Materials Resource Planning" (MRP) as used in manufacturing.
Both are concerned with the efficient and cost effective use of
resources. The classification and control of resources are the
main objectives. Resources are classified to prove their
uniqueness so that redundancy is not introduced and to promote
sharing. Control is required to collect, inventory and retrieve
resources as required by the business.
Whereas MRP is concerned with managing products and the
parts required to produce them, IRM is concerned with managing
information and the resources required to produce it.
|
IRM/MRP ANALOGY
 |  |
Standardize, Control, Share & Re-use
FACTORY CONCEPT
It is possible to apply the same discipline,
organization and automation as used
in an engineering/manufacturing facility.
These same disciplines can be utilized to develop and manage information resources:
Some people might argue that an "Information Factory" represents a much too rigorous environment that would stifle creativity. Far from it. An "Information Factory" is simply a recognition that the development of information resources can move from an art to a science. Ultimately, it represents organization, communications, and discipline. It also promotes teamwork and cooperation by sharing and re-using information resources. With its emphasis on defined deliverables, validation/acceptance criteria, and review points, "PRIDE" is compatible with a total quality assurance program, e.g., ISO-9000.
THE VOCABULARY OF "PRIDE"
The vendor has taken great care to keep the language
of the methodologies clear, consistent and easy to understand.
In fact, a comprehensive "Glossary of Terms"
is included. Despite this, there are some common expressions used in
"PRIDE" which the user will need to become familiar with. To illustrate:
RESOURCE refers to one of the many elements used
to produce information. As developers proceed through the
"PRIDE" methodologies, they will document (either manually or
mechanically) each resource and link it to other resources,
thereby creating a chain of relationships. Under "PRIDE," each
resource is identified by number and name (consult the "Establishing
a Repository" narrative under the "Supporting Narratives"
section). Most resources, follow a "Part Number" numbering convention
consisting of a two digit prefix denoting the type of
resource, followed by an alphanumeric control number
to identify the individual description. For example:
These resource prefixes (DD, PD, RD, etc.) will become a natural
part of the vernacular of the development organization.
Unlike the other resources, System resources follow a product
structure numbering convention reflecting the four levels in a
system/product hierarchy (a basic "PRIDE" concept):
NOTE: The XX-XX-XX-XX convention can be modified as required for
installation standards; for example: XXX-X-XX-XX,
XX-X-XXX-XX, etc.
The term "IRM" refers to the overall concept of
Information Resource Management, but it is also used throughout
"PRIDE" in reference to a "repository" where
information resources are documented and inventoried (either manually
or mechanically). Each resource is cataloged in the IRM by number and
name in the manner mentioned above. For a more complete description of
the organization of the IRM as a tool, consult the following
section: Establishing a Repository.
METHODOLOGY:
Other commonly used expressions associated with the
"PRIDE" methodologies include:
ACTIVITY - a unit of work consisting of one of
more operations.
OPERATION - the smallest unit of project work.
Sometimes referred to as "task" or "step".
DELIVERABLE - a report, file, or some other
object produced from a specific phase, activity or operation.
Deliverables are sometimes referred to as "work
products".
MOD/IMP - short for "Modification/Improvement";
refers to a business objective of any kind (small, medium,
large; new development, maintenance activity,
modification/improvements). The expression "Mod/Imp" is a
recognition that most development activity is devoted to
changing and enhancing existing information resources.
PRODUCT ORGANIZATION
The "PRIDE" documentation is organized into ten major sections:
The layout and structure of the methodologies contained herein are uniform
making it easy to learn and navigate. Once a person understands the
structure of one "PRIDE" methodology, he/she will be able to easily navigate
another. The methodology sections (EEM/ISEM/DBEM) are divided into sub-sections:
The Methodology section describes the concepts
implemented within it, along with narrative describing the
construction of the methodology and how to navigate through
it. Examples show sample deliverables produced from
the activities. Tools & Techniques describe the
various types of products and techniques that should be used
to perform each activity. Phase Functional Matrix
provides a table relating the phase's activities to the
developers assigned to perform the work. The Phase
Review Checklist provides the acceptance criteria for
the phase deliverables. These checklists have not been
included with the "Examples" sections so that the user can
view and/or print them separately. Supporting
Procedures includes special narratives related
exclusively to the respective methodology.
NOTE: Depending on the activity, there may not be sub-sections
for Examples and Tools & Techniques.
Considerable effort went into the development of the sample
deliverables included under the Examples sections. A
sample of each deliverable has been included as a guideline for
its preparation. Because some samples are re-used throughout
the methodologies, some examples will lack full continuity in
their presentation. Further, certain text narratives have been
abbreviated for conciseness. In addition, the examples reflect
a fictitious company with fictitious personnel. Any resemblance
to persons living or dead is coincidental.
The Project Management section includes
sub-sections related to the activities of Project Management
(Planning, Estimating, Scheduling, Reporting, and Control).
The sub-sections under Supporting Narratives
includes tutorials on such topics as: Establishing a
Technical Library, Quality Assurance, Establishing a
Repository, and Functional Descriptions.
|