| CHANGE METHODOLOGY |
| Our Strategic Consulting
service helps' companies select the business performance change
management methodology necessary to realise their objectives. |
| Size, complexity
and activities are all-part of the evaluation process in selecting
the best methodology to make happen your project. |
| Questions that we
can assist with: |
 |
What Needs to change? |
|
The
Type of change? |
|
The Culture? |
|
You need change Audits? |
|
The change Strategy
& Approches? |
|
The level of Resitance to change in the Organization? |
|
Need to revive a Stalled Change effort? |
|
|
|
|
| |
| Strategic
step-by step Process? |
| We help our clients by
providing one-on-one service that will help your organization develop
a framework for Transition to drive business transformation and realize
tangible, measurable Return on Investment. |
| This 8-step process will
facilitate your Change strategies and turns economic, technological,
social and political trends' to your advantage; |
| 1 |
Establish
a Sense of Urgency, |
| 2 |
Create
the Guiding Coalition, |
| 3 |
Develop
a Vision and Strategy, |
| 4 |
Communicate
the Change Vision, |
| 5 |
Empower
Employees for Broad-Based Action, |
| 6 |
Generate
Short-Term Wins, |
| 7 |
Consolidate
Gains and Produce More Change, |
| 8 |
Anchor
New Approaches in the Culture. |
|
| |
| BUSINESS/TECHNOLOGY
METHODOLOGY |
| WebTech Management Business
Methodology is Driven by two (2) activities. Business principles and
Object-oriented programming that as become the software industry standard.
WebTechManagement as merged these two activities into a six (6) phases
Business Driven Object-oriented development methodology. |
| If you are involved in
the area of computer science and the Internet you should be aware
of the fact that this methodology is so important to your success. |
| Of prime importance in
software developed by object-oriented programming is the ability to
reuse. You can adapt an object which was used in another context.
This can speed up the development of the software considerably. |
| Object-oriented programming
has a visual and interactive element which consists of two parts,
first to define the windows, forms, Internet pages and links, reports
etc. which have a role to play in the information system and second
to place objects inside these windows. |
| Three main principles of
program design are: |
| 1. |
Modularity: |
| |
Modularity is the
division of one complex and large system into smaller and simpler
parts. In other words "Divide and conquer" But how
do we decide where to divide? |
| 2. |
Abstraction: |
| |
Abstraction is focusing
on what a part of the system does and leaving out the details
of how it's done. |
| 3. |
Encapsulation: |
| |
As an outgrowth of
abstraction, if two parts of a system need to interact, the
objective is not to have either one of them know the details
of what the other one does (just the abstraction). One reason
why this is a desirable result is the details of one routine
could change and you don't want to look all over the place for
interactions with it. |
|
| These 3 ideas are intertwined
- minimum interaction among modules is one measure of good module
division thus encapsulation which depends on abstraction is good for modularity. |
| These three ideas are important
in procedural programming as well, but with object-oriented programming
there is a tendency to think of the objects in a structurally independent
way. |
|
| How to use the methodology? |
| We have identified six
(6) phases in the object-oriented design process which we have represented
with icons. |
| A summary of the six (6)
phases of the design follows: |
 |
| PHASE
1: Preliminary project definition and feasibility study |
| At
this time, you establish contact with the client. Usually, several
meetings are necessary to sound the client out and establish his needs.
After these information meetings and an evaluation of the situation,
you should sit down with your Group and think out what solutions to
bring to his problem and evaluate his project. A business decision
should be made of the feasibility of the project and the presentation
of one or more solutions to the clients needs. Then you can meet with
the client and give him a report on feasibility of the design project.
Once he has accepted verbally, you confirm the acceptance with a written agreement from him. |
|
 |
| PHASE
2: Analysis of the project |
| If
the first phase acceptance is complete you can start with the second
- the detailed analysis of the project. This step is crucial to the
object-oriented design process. The work done in this phase determines
the success of the whole project. You can save a lot of time, effort
and money on phases 3 and 4 if you are conscientious in phase 2. |
| This is the phase where
the objects are defined: forms, subform, reports, subreports, tables,
queries and macros and determined and designed with all their characteristics.
This step determines the relationship among the objects and thus confirms
the actions that are required. |
| After this phase you can
establish the tasks to be done for the design of each object and the
time necessary to accomplish those tasks. As well, you and your team
must prepare a summarised project to show your client. Acceptance
of this summary is necessary before you can go on with the work. |
| This analysis is still
important when you are using a language or a programming tool that
says you can work without a plan. |
|
|
 |
| PHASE
3: Development of a prototype |
| After
your client accepts phase 2, you proceed with the next step - starting
the prototype design. Since the acceptance of phase 2, you have agreed
with your client on the level of sophistication of the prototype you
have to present to him. |
| The next step is to meet
with your programming team to establish the steps that will lead you
to design the prototype. The documents produced in phase 2 will help
you develop the prototype according to the analysis. When the prototype
is finished, you show it to the client for acceptance. Only when he
has accepted it do you start with phase 4. |
|
 |
| PHASE
4: Finalisation |
| This
phase is similar to the 3rd because your team will work together to
transform the prototype into an application program. In this stage
you put the final touches on the product. The programmers debug and
finalise the software in this stage. Following the design technique,
allows you to gather helpful technical documentation. In addition,
you have to write more technical documentation and the user's documentation. |
|
 |
| PHASE
5: Installation |
| After
the software is installed, test whether the software runs on the minimum
configuration which you have recommended. There is a list of tasks
that you must complete to do an installation of ISO 9000 quality.
You can modify the example document(XX) to fit your own installation.
This list also has the different levels of training and tests that
are needed for the client's acceptance. |
|
 |
| PHASE
6: Service |
| After
the client has accepted the software installation the after-sales
service contract that you have agreed with the client comes into force. |
|
|
| |
|
(French only!) |
|
|
