Presentation–abstraction–control

Presentation–abstraction–control (PAC) is a software architectural pattern. It is an interaction-oriented software architecture, and is somewhat similar to model–view–controller (MVC) in that it separates an interactive system into three types of components responsible for specific aspects of the application's functionality. The abstraction component retrieves and processes the data, the presentation component formats the visual and audio presentation of data, and the control component handles things such as the flow of control and communication between the other two components .^[1]

In contrast to MVC, PAC is used as a hierarchical structure of agents, each consisting of a triad of presentation, abstraction and control parts. The agents (or triads) communicate with each other only through the control part of each triad. It also differs from MVC in that within each triad, it completely insulates the presentation (view in MVC) and the abstraction (model in MVC), this provides the option to separately multithread the model and view which can give the user experience of very short program start times, as the user interface (presentation) can be shown before the abstraction has fully initialized.

Hierarchical model–view–controller (HMVC)

A variation of MVC similar to PAC was published in an article^[2] in JavaWorld Magazine, the authors apparently unaware^[3] of PAC which was published 13 years earlier. The main difference between HMVC and PAC is that HMVC is less strict in that it allows the view and model of each agent to communicate directly, thus bypassing the controller.

The controller has some oversight. The controller selects the model and then selects the view, so there is an approval mechanism by the controller. The model prevents the view from accessing the data source directly.

See also

• Model–view–presenter
• Model view viewmodel
• Presenter First
• PAC-Amodeus,^[4][5][6]
• PAC*
• Drupal web application framework

References

• Coutaz, Joëlle (1987). "PAC: an Implementation Model for Dialog Design". In H-J. Bullinger, B. Shackel (ed.). Proceedings of the Interact'87 conference, September 1–4, 1987, Stuttgart, Germany. North-Holland. pp. 431–436. http://www.interaction-design.org/references/conferences/interact_87_-_2nd_ifip_international_conference_on_human-computer_interaction.html. 
• Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, Michael Stal (1996). Pattern-Oriented Software Architecture Vol 1: A System of Patterns. John Wiley and Sons. pp. 145–168. ISBN 0-471-95869-7. 
• Gaëlle Calvary; Joëlle Coutaz, Laurence Nigay (1997). "From Single-User Architectural Design to PAC*: a Generic Software Architecture Model for CSCW". In Pemberton, Steven (ed.). Proceedings of the ACM CHI 97 Human Factors in Computing Systems Conference. March 22–27, 1997, Atlanta, Georgia.. pp. 242–249. http://www1.acm.org/sigs/sigchi/chi97/proceedings/paper/jcc.htm. 
• Joëlle Coutaz (1997). "PAC-ing the Architecture of Your User Interface". DSV-IS’97, 4th Eurographics Workshop on Design, Specification and Verification of Interactive Systems. Springer Verlag. pp. 15–32. http://iihm.imag.fr/publs/1997/DSVIS97_PACing.pdf. 
• Markopoulos, Panagiotis (1997) (pdf). A compositional model for the formal specification of user interface software. PhD thesis, Queen Mary and Westfield College, University of London. p. 26. http://www.idemployee.id.tue.nl/p.markopoulos/downloadablePapers/PhDThesisPanosMarkopoulos.pdf. Retrieved 2006-05-25. 
• Paris Avgeriou; Uwe Zdun (2005). "Architectural patterns revisited – a pattern language". Proceedings of 10th European Conference on Pattern Languages of Programs (EuroPlop 2005), Irsee, Germany, July 2005. pp. 1–39. http://www.daimi.au.dk/MultiCore/attachment/wiki/StudyGroup08/Plan/. 

Notes

1. ^ Kai, Qian (2009). "Interaction-oriented Software Architectures". Software Architecture and Design Illuminated. Jones and Bartlett Illuminated. pp. 200. ISBN 9780763754204. 
2. ^ Jason Cai, Ranjit Kapila, and Gaurav Pal (July 2000). "HMVC: The layered pattern for developing strong client tiers". JavaWorld. http://www.javaworld.com/javaworld/jw-07-2000/jw-0721-hmvc.html. Retrieved 2006-05-25. 
3. ^ "TP" (2000). "Is HMVC PAC? (letter to the editor)". JavaWorld. Archived from the original on 2005-02-05. http://web.archive.org/web/20050205080537/http://www.javaworld.com/javaworld/jw-09-2000/jw-0908-letters.html. Retrieved 2006-05-25. 
4. ^ Laurence Nigay; Joëlle Coutaz (1991). "Building User Interfaces: Organizing Software Agents.". ESPRIT '91 Conference. Brussels, Belgium: November 1991. http://citeseer.ist.psu.edu/nigay91building.html. 
5. ^ Laurence Nigay (January 1994) (in French, with abstract in English) (PDF). Conception et modélisation logicielles des systèmes interactifs : application aux interfaces multimodales. PhD dissertation, 315 pages, University of Grenoble, France. pp. 131–268. http://iihm.imag.fr/publs/1994/THESE1994_Nigay.pdf. 
6. ^ Nigay, Laurence; Joëlle Coutaz (1997). "Software Architecture Modelling: Bridging Two Worlds Using Ergonomics and Software Properties.". Formal Methods in Human-Computer Interaction. Springer-Verlag. chapter 3, pp. 49–73. ISBN 3-540-76158-6. http://iihm.imag.fr/publs/1997/FormalMethodChapNigay97.pdf. 

External links

• Architectural outline for the game Warcraft as it might be implemented using the PAC Architectural Pattern: Programming of the application PACcraft:Architecture (in french)
• Pattern:Presentation-Abstraction-Control (pattern description)
• PAC description in the Portland Pattern Repository
• WengoPhone is a free software VoIP application that is written using the PAC design pattern.
  • description of PAC and motivation for use in WengoPhone.
  • demonstration code, courtesy of the OpenWengo community.
• HMVC: The layered pattern for developing strong client tiers