Software Architectural Style Free essay! Download now
Home > A Level > Computing > Software Architectural Style
Software Architectural Style
You can download this essay for free. All you need to do is register and submit at least one of your essays to us.
Or you can purchase this essay for just $2 instantly without registering
Downloads to date:
| Words: 4114 | Submitted: 05-Apr-2011
97.2% | Number of pages: 26 | Filetype: Word .doc
This is what the first 3 pages of the essay look like
DescriptionSoftware Architectural Style
Software Architectural Style
An architecture has a data flow aspect and a control flow aspect. The data flow describes functional modules and data transfers. The control flow describes the way control is passed from one part of the system to the other.
Frequently used architectures
- Layered Systems
- Client-Server and N-Tier Systems
- Process Control
- Call and Return
- Implicit Invocation (Event Based)
Control flow describes the way activity flows through the application. For starters, an application may consist of a single process that performs sequential executions, subroutine calls and loops. But the application may also consist of several asynchronous processes.
Even though a single thread can at the lowest level only do loops and subroutine calls, at a higher level of abstraction it can create all sorts of control flows. In Implicit invocation for example, At the lowest level it's just subroutine calls. At a higher level it's modules that become active when they receive an event that was sent earlier on by a different module.
Two characteristics stand out to describe control flow:
Command structure (Control Tree or Control Loop) and
Order of execution (Parallel or Sequential)
Architecture determines the fundamental structure of a system. Architectural styles guide choice of architecture: encode common patterns for achieving certain quality goals.
An architectural pattern is a set of architectural design decisions that are applicable to a recurring design problem, and parameterized to account for different software development contexts in which that problem appears. Architectural patterns are similar to design patterns but applied “at a much higher level”
This architecture is used in simple GUI applications. The architecture is event-driven, which means that all activity starts by some event and is propagated by some other events. The architecture usually contains a large number of components (MVC components), each of which is built out of these three items:
1. The Model
2. The View
3. The Controller
The model is the information contents of the component. It can be as simple as an integer or a string, and as complex as an interface to an external database. The MVC component does not need to contain the model itself. It may contain just a link to the model. And this is common if multiple MVC components are connected to a model.
In a MVC architecture, where the model is shared by multiple MVC components, the model should keep track of any number of views. These views need be notified of changes that occur in the model.
The view is the visual representation of the component, usually on a computer screen. It can be a textbox or a button in a form on the screen, anything ...
Download this essay in full now!
Just upload at one of your essays to our database and instantly download your selection! Registration takes seconds
Comments and reviews
Reviews are written by members who have downloaded the essay
No comments yet. If you download the essay you can review it afterwards.