Home > Articles > Software Development & Management > Agile

Agile Modeling

  • Print
  • + Share This
This chapter is from the book

Using Agile Modeling in a Sample Session

So far, this hour has covered mainly concepts and practices. Now's the time to see how these might work on an XP project! We'll take a sample user story and work through a series of models until we're ready to begin development (or we run out of time). We will do the following in our sample session:

  • Get a user story from the customer

  • Create a workflow model to better understand the user story

  • Remodel as a flow diagram to further refine our understanding

  • Write new user stories that flow from our new understanding

  • Develop some screen mockups

  • Use the screen mockups and our workflow diagram to create a physical data model

Our customer runs a small library and is interested in offering library users a service whereby they can order books over the phone. The library will then mail the book or books out to the customer. Who knows how they will get them back! Phase 2 of this project will be to extend the system's functionality to online ordering over the Internet. For now we'll start with the basic system. Table 23.7 lists our customer's user story.

Table 23.7 Sample User Story for Library System

Title

Ordering books over the telephone

Description

The system should allow users to search for books based on customer criteria and then allow ordering of any book.


Our customer's user story looks like it might need to be split into three or four stories; we'll leave that question mark and see what pops out as we begin to model.

TIP

Remember, we are using modeling to further our understanding of requirements; the goal is to write software that meets our customer needs. Modeling is our means to that end.

Our user story in Table 23.7 is, by definition, pretty vague. We begin by discussing with the customer the steps involved in ordering and selecting a book. Our job is made easier by the fact that the business domain (library systems) is common and easily understood. Try to visualize; we take turns at the whiteboard, drawing, sketching, erasing, and redrawing, until we arrive at a common understanding. We can expect that at this stage we'll be mixing business or process flow with system-related information. No need to become worried about this; having a big picture of business processes will always be helpful. Figure 23.1 is the result of our discussions.

Figure 23.1 The business process for our library sample.

Our diagram is a little rough around the edges, but it has highlighted some interesting workflows and issues for us. Notice the use of metaphors—house for customer, Rolodex for index, and mailbox for postal service. This looks like the kind of diagram that customer and developer alike could understand! One problem with it is that it's hard to get the correct order or sequence of events. In fact a diagram like this would likely be used as basis of to iterate from; in the end, it's thrown away. This is a great example of the AM practice of Iterate to Another Artifact. To get some sense of sequence, we'll create a simple flow diagram.

It turns out that your hotshot Visio expert has been modeling the flow while you were evolving your whiteboard sketch. Both diagrams tell different sides of the same story and this demonstrates the AM practice of Create Several Models in Parallel. Figure 23.2 is our much tidier flow diagram.

Figure 23.2 Using a flow diagram to capture business process flow.

Now the team will distill the diagram down a little further, using an interface prototype model. Are you seeing new user stories appear from the woodwork as we model and discuss? Here are some that you might have noticed:

  • Search for book

  • List books

  • Get customer details

  • Get book order details

  • Process order

Back to the whiteboard again to get a sense of what screens we might need to build. Figure 23.3 is the team's sketch of the probable screens they'll need.

Figure 23.3 Modeling the screen flow.

Without getting into detail we can see the need for the following screens:

  • Search screen to capture criteria

  • Results screen that lists books and authors

  • Book details screen that displays status of the book, reviews, summary, and location in the library

  • An order details screen where customer contact information is added and the order is accepted for processing

By the way, we added the option to go straight from the list into the order detail.

Let's take a first pass at defining the likely screen layout. Figure 23.4 illustrates our whiteboard sketch. Notice how we captured some useful information about values in the drop-down box and the length (50 characters) of the text box.

Figure 23.4 Search screen mockup sketch.

From here we can go our next screen, which is the list results screen displayed in Figure 23.5.

Figure 23.5 List screen mockup sketch.

We're demonstrating the AM practice of Create Simple Content here by only displaying the barest requirements. For example, we will take sketches and then build HTML mockups; our model has to be good enough to get us started on the right track and no more. We showed lines under each header (title, author, and order); the team knows these refer to hyperlinked text. If we were going to transmit the image to a satellite team or site, we'd need to produce more accurate drawings.

Figure 23.6 illustrates the book detail screen.

Figure 23.6 Book detail screen mockup sketch.

Our last mockup screen is the order detail where we take down the customer's address and then accept the order for processing. We uncovered a user interface question while doing this mockup; how do we handle ZIP code, state, and city? Should they be saved as text or in some kind of lookup? We'd probably figure this out before we start on the screen because it will affect our database design. Most likely we'll make the state a lookup and leave the rest as text. Figure 23.7 illustrates the book detail screen.

Figure 23.7 Order detail screen mockup sketch.

So, we now have some rather impressive screen mockups and a good feel for the overall system flow. We've been uncovering database-related issues as we worked through our models. In reality, we could argue that we can go right to our database-modeling tool, as the structure seems simple enough.

TIP

Modeling tools are not evil! Agile Modeling doesn't mean always use paper and whiteboard, and applications such as CASE or database modelers can be used when it makes sense. The trick is knowing when to use them; that is Agile Modeling!

In our case we could have assigned the task of coming up with a data model to a single developer. This developer would then report back to the group for feedback, as shown in Figure 23.8.

Figure 23.8 Library system physical data model.

We're now at the point where at least some development can begin. Here are some of the things we have achieved in our session:

  • Clear understanding of the business problem

  • Decomposition of the base user story into more specific stories

  • Screen mockups ready for conversion into HTML

  • Draft physical data model completed

In the process we switched back and forth between software application tool and paper. This pattern will continue as development starts and programmers need to grasp more technical issues; they will select modeling tools and techniques that communicate best in their own situation.

  • + Share This
  • 🔖 Save To Your 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