Home > Articles > Programming > Visual Basic

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

This chapter is from the book

Test Application Architecture

A prototype can test the application's preliminary architecture. While building the prototype, you can implement the overall framework that you think you will need to build the final application. If it doesn't work for the prototype, it probably won't work for the final application, either.

Two of the most common application design strategies are object-oriented design and stepwise refinement. The following two sections explain how a prototype can help you refine a project design using these two approaches.

Object-Oriented Design

In an object-oriented architecture, you begin by identifying the programming objects that make up the system. You determine how those objects interact and what sorts of features they must have to do their work individually and as a group.

For example, a point-of-sale system might have objects representing customers, orders, order items, and inventory items. These objects have properties and methods for dealing with their own abstract data. The Customer object contains information about a customer: name, billing address, shipping address, account number, account balance, and so on. The objects also must know how to work together. The Customer object needs to know how to create a new Order object representing an order created by that customer. The Order object needs to know how to make OrderItem objects representing the items in the customer's order. One of these objects needs to know how to combine all the OrderItems to produce a bill for the customer.

Other objects might deal with controlling the application rather than the domain. These objects might include User, Privilege, Form, Printer, and Report objects.

In this kind of object-oriented architecture, the prototype should implement the most important objects. In this case, those would probably be the Customer, Order, and OrderItem classes. The prototype should define the main interactions among those objects and provide enough detail that it can display a reasonable imitation of the final application.

Some objects may provide only enough features to let the prototype work. When a user wants to create a new order for a customer, the new Order object might contain exactly four OrderItems. The final application would let the user add and remove OrderItems as needed, but the prototype just needs to show what OrderItems look like. The prototype may even omit some less important objects. In this example, the prototype might not provide real user name and password checking. It also might not verify permissions before allowing the user to generate reports and view certain screens.

A prototype should definitely include any objects that you don't understand completely. If you plan to interact with a data acquisition system and you have not done so before, include the data acquisition classes in the prototype. The prototype gives you a chance to test things that you don't understand in miniature before you try to implement them in the full-blown application. If you don't investigate these issues now in the prototype, you will have to handle them later when changing the system's design will be much harder.

As you build the prototype, you will learn more about the interactions among the objects. You may discover new features that an object should provide. You may find that some objects are unnecessary or that you need a new type of object that you didn't anticipate. Building the prototype will help you finalize your object architecture.

If you start making too many changes to the original design, you should probably step back and reevaluate it. You will probably get a better result if you rewrite the design from scratch rather than incrementally patching it up to make the prototype work. When you have revised the design, you can start a new prototype.

When you have finished building the prototype, you should have the object model fairly well tested, at least at a high level. If the prototype uses at least partial implementations of the system's most important classes, then your design is probably on track.

Stepwise Refinement

In the stepwise refinement development approach, you begin with a general statement of the program's design. For a point-of-sale system, this might be something like the following:

    Store records describing customers, orders, and order items. Allow the user to create a new order and generate a bill automatically. Provide lots of reports.

You then add more detail to this description to explain more about how the tasks will be accomplished. For example, you might mention that users need to log on with user names and passwords, and that you will store data in a relational database.

When the system's description becomes too unwieldy, you group related tasks and break them into subsystems. You then add more detail to the descriptions of the subsystems. You continue this process—adding more detail and breaking the pieces of the system into smaller pieces—until you reach some level where you think you understand the complete solution. At this point, you could start writing code to handle the smallest tasks. You could then combine them to solve higher-level problems, and so on until you had completed the entire application.

When you build a prototype, you need to decide which of the tasks you have defined should be included in the prototype. Usually those tasks include a large part of the application's user interface. That lets customers understand how they will interact with the program. Building menus, buttons, and forms is relatively easy in Visual Basic, so including a lot of user interface in the prototype is not too difficult. This also lets you test any interface elements that are not part of the standard Visual Basic toolkit. For example, if you will be using a new ActiveX control that you just bought, you can try it out in the prototype to see if it can do everything you need. The user interface also provides a starting point for demonstrating deeper parts of the application. Pushing a button can launch code that tests pieces of the system that you need to study in greater detail.

You should include pieces of the design that you don't fully understand in the prototype. For example, if the final program must update a database on a Web server, the prototype should demonstrate that capability. The prototype need not implement every detail of this operation, but it should prove to you that you could accomplish the task. In this case, the prototype might connect to a database on a Web server and update a specific record. If you can do that much in the prototype, you will have some confidence that you can update records more generally in the final application.

As you build the prototype, you will probably discover new tools that you need to build that you hadn't thought of before. You may also find that you don't need other utilities that you thought would be necessary. Building the prototype will help you finalize your project architecture.

If you start making too many changes to the original design, you should probably step back and reevaluate it. You will probably get a better result if you rebuild the design from scratch rather than incrementally patching it up to make the prototype work. When you have revised the design, you can start a new prototype.

When you have finished building the prototype, you should have the overall architecture fairly well tested. If the prototype demonstrates basic features from each of the program's major subsystems, then your design is probably on track.

  • + 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.


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