Home > Articles

This chapter is from the book

Traditional Business Analysis

Traditional, or sequential, business analysis refers to writing a requirements document to serve as the foundation for the system development effort. The requirements document is usually completed, or mostly completed, before construction begins. At least, that’s what’s normally meant by traditional process. This is often known as waterfall—which is misleading—and far too many people spend far too much time telling you how evil, wasteful, calamitous the waterfall process is.

It doesn’t have to be.

Some amazing systems have been developed using the traditional approach, and there are often very good reasons for using it. For example, if you work in the pharmaceutical or medical arenas, or in aeronautical or the military, you are required to write the complete specification and be able to prove that the implementation matches the specification and that all the requirements have been tested.

Why these industries? Because human lives depend on their systems. Because all of them are audited by overseers who are charged with ensuring that the systems work, and work as intended. That’s comforting to know when you are at 39,000 feet or having a tumor treated by a linear accelerator.

Similarly, for most outsourcing projects or some government projects, there is a need for a complete and rigorous specification. There are also organizations that, for one reason or another, want to produce a specification.

Of course, there are many instances of noncritical development efforts that produced far too much documentation, but that does not mean that no documentation is the answer. Naturally, there have been specifications that were badly written and produced the wrong result. But blaming the specification because of the person who wrote it is wrong.

So what should you do if you are working in the traditional way?

Most of what we have written in this book also applies to the traditional business analyst. Let’s look at a traditional project.

Before reading further, please expunge from your mind the thought of a team of business analysts working for month after month producing a requirements document that is so thick it can only be moved using a forklift. And, once produced, the document is barely touched by the developers, who know that they will not be able to find what they need from it, and in any event, even if they deliver the wrong product, nobody will know because nobody can read the huge specification and prove them wrong. So who cares?

Those days are gone. Long gone. Nobody does it like that anymore. They haven’t for years.

Traditional Process

The traditional process produces a complete specification before starting construction, but what you should do to produce that specification is more or less the same as if you were using an agile approach.

You identify the customer segments and their problems You solve the right problem. You design a business solution that attracts its audience and slots neatly into its environment. You ensure the right product is developed.

The differences lie in the approach you take to these tasks. Consider the process shown in Figure 7.10: the discovery side of an agile process. You have seen this diagram in previous chapters, and we have written about the details in previous chapters, so there is no need to describe these activities again here.

Figure 7.10

Figure 7.10 The discovery activities. These are also appropriate for traditional projects.

Note in this figure the feedback and iteration arrows. These are the things that make the difference for traditional projects. Your aim is to produce the requirements document at the end, but you do not necessarily produce it all at once. The way you do it depends on the kind of problem you are solving.

Let’s start by dividing problems into routine, complicated, and complex.

Routine Problems

Routine problems exist in a well-understood domain and are the kind of problems that you and your organization have solved numerous times. You work for a logistics company; you have another logistics problem. You work for a movie distributor; this is another movie distribution problem. Moreover, you probably have only a few customer segments for routine problems.

How big is this problem? If you consider this to be a small to moderate problem, it’s possible to collect all the customer segments and their individual problems. You can then proceed with all of them at the same time, finding business solutions that solve the problem, moving through investigation and designing the solution. Design means designing the total package for all your segments, which you then specify in your requirements document.

  • Routine problems exist in a well-understood domain and are the kind of problems that you and your organization have solved numerous times.

If your routine problem is large, you would probably divide the customer segments at the time of identification and work through the activities producing the requirements document for a subset of segments. You might make use of business events to prioritize and partition further. The large iteration arrow shown in Figure 7.10 indicates that you iterate back and pick up the next segment, do the same again, and repeat until the solution for all the segments has been specified.

Complicated Problems

Let’s say that your problem is beyond routine. Complicated problems have lots of components interacting with each other. It’s a difficult problem in that it might be partly or wholly unknown to you, but you are still able to determine if it is working correctly. For example, a commercial airplane is complicated, as are some websites. Amazon’s site springs to mind as an example of a complicated problem—there are lots of components, and they need to work correctly together for you to pay and have your stuff delivered tomorrow.

  • Complicated problems have lots of components interacting with each other.

Let’s start with a medium-size complicated problem. As usual, you determine the customer segments and then select a few of the higher priority ones. Work through finding the best solutions, and investigate them as usual. Instead of designing the work for them, iterate. Go back and pick up the next set of segments and repeat the process. When you have finished investigating all the segments, you design the whole solution at the same time. It is necessary to do it this way because you must ensure that all the components of the complicated solution work together.

This is a large task. You can, of course, subdivide the design now that you know the whole of it, using pieces of the solution that have similar characteristics as your partitioning theme.

If your complicated problem is very large—say, something as big as air traffic control—then slicing and iterating is quite intricate. The difficulty lies in coordinating the various sections of the solution so that they work in harmony when you’ve finished.

Complex Problems

Complex or wicked problems are those with too many unknowns, or too many unpredictable effects, to be able to determine absolutely if any solution is working correctly. For example, the economy and mapping the seabed are complex problems. There are too many unpredictable causes and effects.

By way of illustration, suppose you are charged with building a solution to predict crime. Consider the number of variables that contribute to crime: criminals, their attitudes and upbringing, opportunities, financial situation, weather, locality, presence of police or security guards, and so on. Each of the variables has an effect on one or more others. This results in a level of complexity that makes it difficult, if not impossible, to determine if the results are accurate. The predictive policing systems in operation at the time of writing are good, but nobody can really say if the results are as accurate as they could be.

  • Complex problems are those with too many unknowns, or too many unpredictable effects, to be able to determine absolutely if any solution is working correctly.

For complex problems, the first step is to identify the known, or routine, parts of the problem. These are most likely the automated parts, which are more predictable than the human parts. Depending on the size of the problem, you would select a subset of the known problems and work the discovery activities up to and including design. Although you probably produce a requirements document for the design, it is important not to commit to developing it yet.

Iterate for the rest of the routine parts of the problem until they have all been designed.

Now it becomes both tricky and fascinating. You have to model the effects of the routine parts of the solution as they interact with the unpredictable elements of the problem. You are using something like the safe-to-fail probes we spoke of earlier to determine the feasibility of your complete solution.

Once you are satisfied that you have designed the optimal components, produce your requirements document and proceed to development. It might be that you have already developed some of the components of your complex system; you needed them to make your testing more realistic. This is often necessary, but it is also necessary to keep in mind that your developed components are, until proven, an experiment.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020