Our basic philosophy of software development is that we should do what we can to maximize our effectiveness. Do the just the right amount--no more, and no less. This means thinking carefully about what processes we choose to apply during all phases of software production. Different approaches to design can have a profound effect on project success, as measured by timeliness, predictability, and level of quality. We want to be sure to choose the right approach to design. We recognize that deciding on the right design strategy may not guarantee success, but choosing the wrong one WILL guarantee failure.

There are many possible design strategies--as many as there are kinds of software, perhaps even more! Many software development organizations use only one--the one they know. That's OK if it is appropriate for the job at hand. If it isn't, your project is doomed to fail even before it starts. Many software projects have failed because the organization was trying to do a job that was different, and usually bigger, than what had been done before, and tried to use the old design strategy that doesn't scale up.

We study and practice many design approaches. Different ways to model requirements, designs, structured and object methods. Our goal is to help organizations succeed in delivering the software products they desire to produce in a timely and effective manner. If your organization is setting out to produce a more ambitious product, or you're having difficulty meeting you project objectives now, then perhaps we can help you.

E-mail: Brian Lawrence

Last updated: 20-Mar-1998

Copyright © 1998 by Brian Lawrence. All Rights Reserved.