For more information see "Pattern oriented software architecture" (ISBN: 0471958697
http://www.amazon.com/exec/obidos/ASIN/0471958697/o/qid=993042954/sr=2-2/ref=aps_sr_b_1_2/104-4374813-3651137)
Layer
========
One Layer is build on services of more foundational layer.
Examples: OSI, Windows NT (system layer, resource manager, kernel, hardware abstraction layer, hardware)
Advantage: independent development of each layer; controlled independence between layers
Disadvantage: management overhead; maybe problems on higher layers when changing a lower layer
Model View Controller
================
The model is the kernel (I hope I use this term right) of the application. The responsibility of the view is only to visualize the modelinformations. The controller takes events and calls services on the model to change thats state. The model informs the view and the controller by changing its state.
Examples: most GUIs, Microsoft Foundation Classes, Swing
Advantage: more than one view on the model (Webclient, Javaclient, ...)
Disadvantage: higher complexity; maybe performance (because the notification)
Pipes and Filters
============
Pipes transport Data and Filters manipulate them. (I like this pattern :-)
Examples: Unix Pipes, Apache Cocoon2 (the old cocoon is based on reactor pattern)
Advantage: easier parallelism; independent development of each filter; flexibility
Disadvantage: difficult error handling
Blackboard
=========
Informations on the "blackboard" are changed/added by "knowledge sources". (a very difficult pattern)
Examples: KI e.g. HEARSAY-II (never heard before), a system for speech analysis
Advantage: approximate solutions to problems without an algorithm.
Disadvantage: very difficult
These all are architectural pattern. Which are good for YOUR application, I don�t know. It depends on your application. Maybe the Layers or the Pipes&Filters.
I don�t unterstand your second question, so don�t answer on that. :-)
Mit freundlichen Gr��en
Jan Mat�rne
RZF NRW
Sachgebiet 314-P Software-Entwicklungs-Methoden
Fiscus AFG NW 42 SoftwareEntwicklungsUmgebung
Internet: [EMAIL PROTECTED]
-----Urspr�ngliche Nachricht-----
Von: Christine [SMTP:[EMAIL PROTECTED]]
Gesendet am: Mittwoch, 20. Juni 2001 11:18
An: 'Rose_Forum (E-mail)
Betreff: (ROSE) Architectural pattern & Analysis Mechanisms Characteristics
1 .There are some pattern for Architectural Pattern: Layers,
Model-view-controller(M-V-C), Pipes and filters, blackboard. Any body tell
me about the power and the weakness from each pattern ? Which pattern the
good one for Architectural Pattern ?
2. I had read about examples of analysis mechanisms characteristics :
Persistency mechanisms have characteristics are granuality, volume,
duration, access mechanism, access frequency and realiability. Any body tell
me about the detail of that Persistency mechanisms characteristics?
Thanks
Christine Widjaja
Sales Engineer
Asimetris Data Sentosa, PT.
Rational Software Consulting Partner
Ph: +6221 6269018 - Fax: +6221 6269011
http://www.asimetris.co.id/
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages: http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
