colorssilikon.blogg.se - Acl audit software architecture

Containment - COM+ server process isolation.

recycling of server processes in IIS.6 ASP.NET /COM+ 1.5

Using preventive measures (administration) e.g.

The ability of the system to keep operating over time in the context of application and system errors and in situations of unexpected or incorrect usage (to perform in a predictable manner).

Amount of time it takes to complete a transaction.

Typical unit of measurement you could use:

Process isolation between OLTP and OLAP.

Caching – using a local copy of data to reduce access time.

Load balancing – spreading the load evenly between a set of resources.

Connection pooling - reducing the execution time overhead associated with establishing database connections by establishing a shared pool of connections.

Typical Design/Architectural principles to look for: The time required to respond to stimuli (events) or the number of events processed in some interval of time. Maybe you also have ideas that you would like to share. This list is not intended to be exhaustive. In the bullets below, I tried to sum up the different quality attributes together with some typical things to look for when you're conducting a review. An approach in evaluating software architecture is reasoning about the quality attributes a software architecture exhibits.

How does it meet the needs of all the stakeholders?įor an existing system, you can detect these key factors that will give you an idea of the software architecture.

How is it going to function? How do structural components of the architecture work together?.

What style are you going to use? What is the structure?.

The general tone in these definitions is that you need to make high-level decisions about the system you're going to build: If you want some formal definitions what a software architecture is, I recommend reading the information here. This text tries to bring together elements a reviewer can use in his/her software architecture review. They help you to spot faults before they become real disasters. But their primary goal is to increase software quality. Reviews are an opportunity for others to eyeball your documents/design/code/software architecture and for you to inspect others' work.