Application Design

Starting with the assumption that we want to provide application services which don't require anything special to be downloaded or installed on the client's PC, we will build our salary chart using web client architecture. End users won't need anything on their PC except a web browser and the Acrobat reader (which is included with many commercial products or has been previously downloaded).

This section works through the design decisions that need to be made and shows the application as it grows.

Subtopics:
Design parameters Functional Operational Life Thin pipes Execution cycle Usage scenarios Who does what - logical delegation What goes where - operational delegation Interfaces Collaboration Leaks Advantages of loosely-coupled design Avoiding "Analysis Paralysis"

Contents

Application Design

Previous: Web clients | Next: Design parameters

Application Design

Subtopics: