About Requirements Analysis

Team-Fly    

 
Requirements Analysis: From Business Views to Architecture
By David C. Hay
Table of Contents
Introduction

About Requirements Analysis

How do we capture what is required of a new software product? How do we do so completely enough that the requirement will last at least until the product is completed, if not longer?

In 1993, after spending over half a billion dollars on it, the London Stock Exchange scrapped its "Taurus" project (intended to control the "Transfer and AUtomated Registration of Uncertified Stock"). It had been Europe's biggest new software undertaking. What went wrong?

The problem was failure to do an adequate analysis of requirements. Requirements for the project were not clearly defined, and they were changed constantly by the myriad of players in the project. "Share registrars, anxious to protect their jobs, demanded a redesign of the system to mimic today's paper-shuffling. Scrapping share certificates called for 200 pages of new regulations. Computer security, with all messages encrypted, went over the top. Companies' insistence on the ' name on register' principle, which allows them to identify their shareholders instantly, made design harder. And so on." [ Economist , "When the bull turned", 1993, p. 81]

The Economist , in an essay accompanying the story of the crash, discusses the reasons projects fail. "Software's intangibility makes it easy to think that the stuff has a Protean adaptability to changing needs. This brings with it a temptation to make things up as you go along, rather than starting with a proper design. [Even] if a proper design is there to begin with, it often gets changed for the worse half-way through. . . . Engineers in metal or plastic know better than to keep fiddling and so should software engineers .

"The fact that software 'devices' can have flexibility designed into them should not mislead anyone into the belief that the design process itself can be one of endless revision . . . .

"Successful software projects require two things: customers who can explain what sort of job needs doing, and engineers who can deliver a device that will do the job at a price that makes doing the job worthwhile. Lacking either, engineers must be honest enough to say that they are stymied." [ Economist , "All fall down", 1993, p. 89]

This book is about understanding an organization well enough to determine "what sort of job needs doing". This requires several things:

  • A close relationship with the project's customersideally via a project champion

  • Effective project management

  • A known and understood set of steps

Our first requirement is for development of a special sort of relationship with our customers, as well as skill in knowing how to capture and represent what we are told.

The second requirement, effective project management, means nothing other than assuring that you have chosen the most capable project manager available.

The third requirement is a clearly defined set of steps. This is where this book is especially helpful. Chapter 2 describes the steps required for success, and the remaining chapters describe the work to be done during those steps.

What is this company (or government agency)? [2] What is it about? How does it work? If we are to create a system significant enough to affect its infrastructure, we'd better know something about that infrastructure. This means that defining requirements for an enterprise begins by describing the enterprise itself. This book is primarily a compendium of techniques to do just that.

[2] Everything said about requirements analysis in this book applies equally to the public and the private sector. For this reason the word most commonly used will be "enterprise", meaning either a company or a government agency.

History

There are numerous ways to describe an enterprise: data models, data flow diagrams, state/transition diagrams, and so forth. Many people have been working for many years to develop the techniques we use today.

Structured Techniques

In the mid-1970s Ed Yourdon and Larry Constantine wrote their seminal book, Structured Design , [3] which for the first time laid out coherent criteria for the modular construction of programs. It presented the structure chart [4] and described what makes one modular structure effective and another not so effective.

[3] All of the works cited in this book are listed in the Bibliography. For this reason, and to minimize clutter, annotations will be given only for direct quotations, listing the page number of the quotation.

[4] All specialized terms introduced in this book are shown in boldfaced italic and are defined again in the Glossary.

Mr. Yourdon next collected around himself a number of other talented people who themselves contributed greatly to the body of system development knowledge. Among others, these included Tom DeMarco, Chris Gane, and Trish Sarson. In 1978, Mr. DeMarco wrote Structured Analysis and System Specification , and a year later, Ms. Sarson and Mr. Gane wrote Structured Systems Analysis: Tools and Techniques . Both books described the data flow diagram (albeit with different notations) as a technique for representing the flow of data through an organization. Later, in their book Essential Systems Analysis , Stephen McMenamin and John Palmer refined the data flow diagram technique with a formal way of arriving at the essential activities in a business.

Together with structured design these techniques became the industry standard for describing information systems, although their use was limited by lack of tools for producing the diagrams. Only those souls deeply dedicated to the principle of disciplined system development were willing to prepare the diagrams by hand. And once they were complete, these diagrams couldn't be changed. They had to be re-drawn if circumstances changed.

The first CASE (computer-aided systems engineering) tools appeared in about 1980, making the diagramming much easier to carry out and therefore more accessible to more people. Even so, it was clear that by organizing our efforts around the activities of a business, we were vulnerable to the fact that business processes often change. While the use of good structured design techniques made programs more adaptive to change, it was clear that it would be nice for them to accommodate change better in the first place.

Information Engineering

In 1970 Dr. E. H. Codd published "A Relational Model of Data for Large Shared Data Banks", defining the relational model for organizing data. While the technology for taking advantage of his ideas would not be practical for another fifteen years, he planted the seed that there was a way to understand and organize data which was far superior to any that had gone before. The process of normalization is a profound way to understand the true nature of a body of data. It provides a set of rules for assuring that each piece of information is understood once and only once, in terms of the one thing that it describes. Databases organized around this principle can now keep data redundancy to an absolute minimum. In such databases, moreover, it is now possible easily to determine where each datum belongs.

From this came Peter Chen's work in 1976, "The Entity-Relationship Model: Towards a Unified View of Data", in which he was the first to describe the entity/relationship model (a kind of data model ). Here you had a drawing that represented not the flow of information through an organization, but its structure .

Inspired by his work, Clive Finkelstein created a notation derived from Mr. Chen's and went on to create what he called information engineering , which recognized that data structure was much more stable than data flows when it came to forming the foundation for computer systems. [5] He also recognized that the process of building systems had to begin with the strategic plans of the enterprise and had to include detailed analysis of the requirements for information. Only after taking these two steps was it appropriate for a system designer to bring specific technologies into play.

[5] Indeed, in the years that followed, "computer systems" were gradually replaced by "information systems"in the popular language at least.

Mr. Finkelstein collaborated with James Martin to create the first publication about information engineering in 1981. This was the Savant Institute's Technical Report , "Information Engineering". Mr. Martin then popularized information engineering throughout the 1980s. With the appearance of viable relational database management systems and better CASE tools, information engineering, with its orientation toward data in systems analysis and design, became the standard for the industry by the end of the decade .

Object orientation

As these things were going on in the methodology field, object-oriented programming was developing. Whereas programs originally tended to be organized around the processes they performed, the real-time systems and simulation languages developed in the 1960s revealed that organizing these programs instead around the data they manipulated made them more efficient and easier to develop.

All data described "objects", so identifying objects and defining the data describing those objects provided a more robust program structure. In the late 1970s Messrs. Yourdon's and Constantine's ideas about modularization also contributed to this approach to program architecture.

As business programs became more and more oriented toward " windows " or screen displays, it became clear that they shared many characteristics with real-time systems, so the object-oriented approach fit there as well.

In 1988 Sally Shlaer and Stephen J. Mellor brought the concepts underlying object-oriented programming together with information engineering and its data-centric approach to system architecture. In their 1988 book, Object-oriented Systems Analysis: Modeling the World in Data , they renamed entity/relationship diagrams "object models" and created their own notation for them. Thus, for the first time, a data model could be either an entity/relationship model or an object model. Then in 1991 James Rumbaugh and his colleagues followed with Object-oriented Modeling and Design , again referring to object modeling but adding their own notation. In 1990 Ed Yourdon and Peter Coad added their object-modeling notation in Object-oriented Analysis . Other books added yet more notation schemes.

Then, in 1997, the first version of the Unified Modeling Language (" the UML ") was published by the Object Management Group. It was intended to replace all of the object modeling notation schemes with a single technique for entity/object modeling. This was brought about through the collaboration of James Rumbaugh, Grady Booch, and Ivar Jacobson, but it was in fact based on the work of David Embley, Barry Kurtz, and Scott Woodfield ( Object-oriented Systems Analysis: A Model-Driven Approach , first published in 1992). The UML has since been the basis for yet more books on the subject of object-oriented modeling.

Note that this "object-oriented analysis" is not significantly different from information engineering. Both are concerned with entities and entity types that are "things of significance to the enterprise" (called "objects" and "object classes" by the object-oriented community). That is, both view systems development from a data-centric point of view.

What is new in object-oriented modeling is the combination of entity/relationship models and behavioral models. In the object-oriented world, each object class (entity type) has defined for it a set of activities that it can "do". This made more sense, however, in the world of object-oriented programming, where the object and the behavior were both bits of program code. The activities of an enterprise are often far more complex than can be described on an entity-type by entity-type basis. The idea is not unreasonable, but it cannot readily be done with a kind of pseudocode typically associated with object classes. Behavior of entities in analysis is better described with a technique called "entity life histories". (See Chapter 7.)


Team-Fly    
Top
 


Requirements Analysis. From Business Views to Architecture
Requirements Analysis: From Business Views to Architecture
ISBN: 0132762005
EAN: 2147483647
Year: 2001
Pages: 129
Authors: David C. Hay

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net