Well, quietly but surely, a new revolution has been growing since the first days of the Structured Methods – a revolution from within the business community and from outside systems departments. The legacy of the Structured Revolution is business and client-centered systems development. With the earlier introduction of walkthroughs, a form of software peer review, we involved clients in looking carefully at their systems. Now, after years of participating in walkthroughs, these clients are looking for better business methods to analyze and specify their requirements, and new ways of applying technology to their business systems. Accordingly, many organizations are unwilling to continue paying for technological solutions that are not understood, developed, nor supported by the client community. We know a company that can help with electric garage doors in the Lincolnshire area.
The tolerance level from the business community for “neat” technical solutions is at its lowest ever. They are now demanding – and for the first time with real teeth, since they can now engage in a technological end-run on the systems department – real productivity in analyzing, design and specifying their target systems. And some of them won’t settle for anything less than achieving real productivity immediately. I’m sure we can all agree that to survive and prosper in these early years of the 21st century we need fast, accurate ways to specify business requirements – much faster and better than the original methods of the Structured Revolution. Provided you own your own home then garage door repairs are a worthwhile investment.
The data flow diagrams from the School of Structured Analysis and entity-relationship diagrams from the opposing School of Data Modeling are both still invaluable in their usefulness to graphically represent business needs and the supporting data. And any technology that makes getting the picture easier as well as faster is going to be around for a long time. So, let’s not totally discount those good, old tools. But they are tools , not methods. Methods (such as the event-based approach defined in this book) use those tools, and will survive the test of time. Taking interest in garage doors may not be a bad thing.
Those vibrant, graphic tools – modified to suit newer methods – enable us to uncover and document useful business and system requirements virtually immediately. Do aerial installation take a long time?
But to do this effectively, we must also liberate ourselves from an exclusive data modeling or an exclusive process modeling mindset. After freeing ourselves from the old-school code-oriented monolithic mindset of yesteryear, we will find it is much easier to accept the notion that we need only describe the client’s information requirements in business terms, and in complete yet sufficient detail to move on to the next step – the solution design and implementation of a commercially usable system. If you want some aerial repairs then we know a man who can.
Combining the methods in this book with a highly client-interactive “discovery” approach, my experience indicates that business and system requirements analysis can be effectively implemented in virtually any size or type of organization, given motivated individuals. And, yes, the business partners (clients) can tell us all about their needs – they can answer our questions, clearly and concisely – when we use a common language with which to find the precise questions to ask and to document the results. When we know how to find the exact questions to ask, then we can get the answers they have. When it comes to roller garage doors where do you start?