MVC Architecture Analysis

1774 Words8 Pages
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…show more content…
It won’t do anything without users requests. The Controller is also only connected to a single View and Model Components which allows data flow only in one way. The most common mistake made by developers is confusing the Controller Components with a Model Components ( Assigning functions in Controller Component which View Component should receive ). MVC default ( with some additions ) folder template: The main one what you should know about MVC is that this model is used for pure business / domain logic and MVC can and should be so much more than data management of an application. C) A discussion of client and server interaction within web applications, discussing both client and server technology: The client and server interaction withing Web Applications means structure that partitions tasks between the providers of a resources or services, called ( web ) servers, and ( browsers ) service requesters ( data requesters ) - the clients. Usually clients and server communicates via different hardware, but they are over computer network which means that both of them are in the same system. The main meaning: The main meaning ( more complicated…show more content…
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

More about MVC Architecture Analysis

Open Document