Application Architecture Guide 2.0 BETA 1 - Willy .Net

Peer-To-Peer
Saas/S+S
SOA
Takes advantage of ad-hoc networking between multiple client computers to
expand processing, storage or communication capacity.
Software as a service is an application that runs in the cloud, relies on other
services in the cloud, and may provide a service that other applications can
consume. Software plus Services is an application that runs on the client but
comes to life when connected to the cloud, offering capabilities that are not
available when it is disconnected.
Service-oriented architecture is a message based system composed of one or
more applications that consume or expose Web services.
Quality Attributes
Use the quality attributes to focus your thinking around critical problems that your design
should solve. Addressing quality attributes in your design rather than during development will
improve the likelihood that your application will be successful in the long term. Use the table
below to review and understand each quality attribute.
Category
Availability
Conceptual Integrity
Flexibility
Interoperability
Maintainability
Manageability
Performance
Reliability
Reusability
Description
The application should be available and operating at all times specified
in an SLA, and when users will expect to be able to access it. Availability
includes both software and infrastructure concerns.
The application should avoid concrete dependencies on other systems
and applications where possible, and provide features that allow it and
any data it holds to be upgraded, migrated, and refactored.
The application should be configurable to allow use in varying
environments and situations, and to cope with changes to business
policies and rules.
The application should interoperate with other associated applications,
including sending and receiving data and using services. It should also
continue to interoperate when other applications are refactored or
upgraded.
The application should be designed and constructed in such a way as to
allow changes to components, services, features, and interfaces as may
be required when adding or changing the functionality, fixing bugs, and
meeting new business requirements.
The application should be easy to manage, by exposing sufficient and
useful instrumentation for use in monitoring systems, and for
debugging and performance tuning.
The application should perform to requirements and expectations, making
efficient use of resources and infrastructure.
The application should continue to work correctly, and work without
interruption where possible, when encountering issues such as invalid input
data, survivable infrastructure faults, varying network bandwidth and
availability, and other external factors.
The components and services in the application should be designed in such a
30