Home > Articles > Software Development & Management

Like this article? We recommend

Analyzing the Problem: Task/Message Flow

So what is a task/message flow? An example is illustrated in Figure 1.

Figure 1 A task/message flow for the original application.

If you know UML, you will recognize that the diagramming conventions are very similar to a UML sequence diagram (but it is about applications, not objects). Time flows down the page, and the diagram shows messages being sent from the user on the left side of the page to the application in the middle of the diagram. The little circles represent the state of the order form object that the application creates and updates. The black circle represents object creation; the orange circle represents object update. I also use a white circle to represent objects being read, and a black circle with a white circle around it to represent object deletion. From the information expressed in a task/message flow, it is usually possible to figure out what session state needs to be held.

Figure 2 illustrates the proposed solution to the Web order-entry project, also expressed in a task/message flow diagram.

Figure 2 Web solution task/message flow.

The dotted rectangles in this example indicate tasks. There are two tasks: a "become a member task" and a "make an order" task. The two tasks can be separated in time and are not linked by the system, except that the membership data is used in the order-entry process. The square with a Q in it represents a queue to another system—in this case, it could be the manufacturing system.

Of course, there are other ways of implementing a Web order-entry system. This is an example solution, not the only solution. However, this decision is crucial to the implementation. The advantage of using a task/message diagram is that it provides a technique for discussing the alternatives before going further in the implementation.

The problem set out in this article is to make the new interface a front end to the old system. By comparing Figures 1 and 2, we can see the extent of the problem. For instance, the old application has no notion of membership, and billing details can't be entered outside the context of entering an order. The simplest solution is to hang on to the membership data in the Web server and pass it to the back end only later. This, too, can be illustrated using a task/message diagram, as shown in Figure 3.

Figure 3 Proposed solution.

The gray rectangles represent computers (the rectangle on the right represents the computer running the original order-entry application). Again there are many other options. For instance, you could do all the old application calls from the last "complete" action.

The primary purpose of the task/message flow is to show the structure of the solution. The secondary purpose is to allow us to analyze the solution.

At least seven aspects of the application need analysis:

  • Ease of implementation
  • Scalability and performance
  • End-to-end data integrity
  • Security
  • System management
  • Flexibility analysis
  • Future positioning

Typically, I don't do the analysis phase until we have chosen the technology (usually people are so eager to choose the technology that I can't get their attention until it's done). In some cases, there might be several technology options for analysis, as well as even several alternative task/message flows. The purpose of the analysis is threefold:

  • Identify cost and risk factors that might lead the project to be refocused or even cancelled
  • Critique and correct the task/message flow
  • List additional factors that must be handled by the implementation

I will now describe each of the analysis tasks in more detail.

Ease of implementation is largely about whether the IT organization has the skills and resources to do the task. Whether there are existing components that can be reused in this project also comes into play.

Scalability and performance start with an analysis of the task/message flow to determine how many messages need to be sent at each point and how many transactions are processed. As a separate exercise, the data volumes need to be calculated. With this information, you can make a first estimate of the systems required and also can identify at least some of the potential bottlenecks. For actual sizing, it is always best to make the sizing estimate by projecting from similar systems of similar complexity rather than trying to calculate it from first principles.

End-to-end data integrity also starts from the task/message flow. Trace through the flow, step by step. At every point, ask, "What happens if there is a failure?" This is the key analysis step for critiquing the task/message flow, and it normally gives rise to a long list of points for the programmer to consider.

Security analysis starts from asking who needs to use the system. In a system-integration project, the existing systems will have their own security mechanisms. Suppose that you are integrating System A with System B. The question then becomes, how should users of System A be represented on System B? Broadly speaking, you can propagate the user information from System A to System B, or you can represent all users of System A as a single user to System B. These issues need to be sorted out early.

System management has many of the same concerns. The analysis done on performance, data integrity, and security will have given rise to a list of possible problematic scenarios. The question for system management is how to trap the key events early, report them accurately, and possibly fix them automatically. For instance, there should be monitors for every potential performance bottleneck.

The last two analysis points look to the future. Flexibility analysis involves thinking about how the system might need to change after the initial release. The technique is to brainstorm possible future extensions to the application. In this example, I would expect this analysis to consider whether the back-end interface is appropriate for other new interfaces, such as orders taken from a call center or from a mobile phone. They should also consider what would happen if the application was extended to other kinds of product. Note: I do not recommend trying to anticipate any future changes in the code, but I do recommend seeing whether there are structural impediments in the design to possible future change.

The final point is to consider the IT organization's long-term architecture goals. If IT strategy is for J2EE but the project calls for a .NET implementation, then perhaps the technology choice should be reconsidered. Alternatively, if the reasons for .NET are good ones, then perhaps the long-term strategy should be questioned. The second issue to address in this section of the analysis is whether this project could be used as an opportunity to move along on some long-term infrastructure plan. Of course, the impact on time scales and budget must be taken into account.

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.

Overview


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.

Surveys

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.

Newsletters

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.

Security


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

Children


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

Marketing


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.

Choice/Opt-out


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.

Links


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