MVC Architecture

Written Component

A) The design / modeling ( UML ) components for your application as derived from the assignment specification:

B) A discussion of the MVC architecture and how it applies to web application development:

MVC architecture ( Model-View-Control pattern ( system ) ) actually was formulated in the late 1970s. It’s a software architecture pattern built on the basis of keeping the presentation of data separate from the methods that interact with the data. Well-developed MVC system should allow developers to work on the same system without changing any files of each other ( i.e. front-end developer won’t change any back-end developer’s files ).

MVC is a design pattern. A Design pattern is a code structure that allows for

The language and rules of communication are defined in a communications protocol. All client-server protocols operate in the application layer. The application layer protocol defines the basic patterns of the dialogue. To formalize the data exchange even further, the server may implement an application programming interface aka API.

The API is an abstraction layer for accessing a service. By restricting communication to a specific content format, it facilitates parsing. By abstracting access, it facilitates cross-platform data exchange. A computer ( Client by default ) can only perform a limited number of tasks at any moment, and relies on a scheduling system to prioritize incoming requests from clients to accommodate them. To prevent abuse and maximize availability, server software may limit the availability to clients.

A Server may receive requests from many distinct clients in a short period of time.

The general distinction between a dynamic Web page of any kind and a Web Application is unclear. Web Sites most likely to be referred to as Web Applications are those which have similar functionality to a desktop software application, or to a mobile application.

Protocols and

Applications have typically been categorized as either Client or Server applications. Traditional client/server interactions are often data-centric and combine most of the processing (or business) logic and user interface within the Client application. Client or Server applications have usually performed many of the functions of stand-alone systems and present a user interface, gather and process user input, perform the requested processing, and report the status of the request.

Without a standard framework to work with, each application can end up sharing very little of its control-flow logic with another application. This leads to buggier software and maintainability nightmares.

Patterns ( Designs ) of Web Applications: Multi-Tier is the new system design which logically divides computing tasks across the application ( like MVC ). Viewed from a purely functional standpoint, most applications perform the following three main tasks: gathering user input, storing the input as data, and manipulating the data as dictated by established operational procedures. These tasks can be grouped into three or more tiers, which is why the new system design provides Multi-Tier