Architecting an application

After you determine the purpose and general features of an application, you need to consider the following topics:

What the object model should be
What types of Flex components you should use to represent the object model
What type of messaging strategy you should use to pass data between objects

This section uses a fairly simple e-commerce application called the Flex Store to illustrate general ways to approach object models, component types, and messaging strategies. The application demonstrates clear separation of model and view objects, and loose coupling of components. It uses a combination of standard Flex components, MXML components, SWC components, and ActionScript components.

The purpose of the Flex Store application is to display a catalog of items that the user can add to a shopping cart, and then order. The following list includes some of the things a user can do with the application:

Click a product thumbnail image to display a larger image and description.
Select a price range for products.
Add items to the shopping cart.
Place orders in a checkout form.

The Flex Store application is included in the samples.war file, which you can extract into your application server.

The following figure shows the catalog and shopping cart views of the Flex Store application:

Flex Store application.

Version 1.5

Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/flex/15/flex_docs_en/00000077.htm