Skip to content

High Level Overview

In the example below, a project has been broken down into 3 high level components.

diagram

The UI component connects to the Web Services component, which connects to Data Storage component for the project.

Highlights

  • This modular design allows each component to perform specific tasks.
  • Each component is replacable without a complete rewrite or major impact to the system.
  • Additional components can be brought on in parallel to provide additional functionality.

Component Details

UI Component

  • The primary purpose of the UI component is to accept input from the user and display responses requested by the user and those generated by the system.
  • The UI component should connect through web services to connect to the database.
  • The UI component should be pluggable/replaceable.
  • The UI component should depend on business rules to be processed by other components.
  • The UI component comprises of one or more subcomponents.

Web Services Component

  • The Web Services component handles interactions between the UI and the Data Storage component.
  • The Web Services component comprises of one or more subcomponents.

Data Storage Component

  • The Data Storage component handles reading and writing of data to and from a permanent datastore, usually a SQL database.
  • The Web Services component comprises of one or more subcomponents.
Back to top