For Enterprise Architecture Professionals

Primary Analyst Photo	Document Information	Rate this Document
	February 12, 2008 Process-Views-Services: A Better Design Paradigm For Applications Step Aside, Model-View-Controller — PVS Must Take Center Stage by Randy Heffner with Jeffrey S. Hammond, John R. Rymer, Kahini Ranade	Average: 9  (7 ratings)

This is an excerpt

Executive Summary

It is time for a major shift in the top-level design model for applications. Model-view-controller (MVC) has been the dominant framework for tying together the user interface and business logic of an application. But flexible, process-focused applications, now and in the future, require a new top-level design model, which Forrester calls Process-Views-Services (PVS). MVC is a programming framework focused strictly on application design for application flexibility. PVS is both a conceptual model for solutions portfolio and an application framework focused on business design and business flexibility, built on a foundation of application flexibility. MVC will still be useful within individual applications, but to increase their focus on business results, architects should move PVS to the center of their application strategies and reorient their conceptual models, architectures, platforms, and planning processes around PVS.

TABLE OF CONTENTS

• MVC Has Been The Dominant Design Model For Application Design
• The Industry Needs A New Top-Level Design Model
• PVS Targets Business Optimization And Flexibility

RECOMMENDATIONS

• Elevate Your Architecture Strategy To Business-Centered Design And PVS
• Related Research Documents

This is an excerpt

Buy Risk-Free

Price: US $499

Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.

Already a Forrester Client?
Log in to read this document.