2004
DOI: 10.1147/rd.485.0797
|View full text |Cite
|
Sign up to set email alerts
|

Model-driven development of large-scale Web applications

Abstract: This paper describes our approach to support the development of large-scale Web applications. Large development efforts have to be divided into a number of smaller tasks of different kinds that can be performed by multiple developers. Once this process has taken place, it is important to manage the consistency among the artifacts in an efficient and systematic manner. Our model-driven approach makes this possible. In this paper, we discuss how a metamodel is used to describe part of the specification as a cent… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2005
2005
2020
2020

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 9 publications
(2 citation statements)
references
References 4 publications
0
2
0
Order By: Relevance
“…The system was designed using one of the most accepted Web application architectures, the model-view-controller (MVC) pattern [ 20 , 21 ]. This design provides extensive flexibility and scalability because of 1) re-use of model components: the separation of model and view components allows multiple views to use the same enterprise model; 2) easy support for new UI/clients: to support a new UI/client, the view and some controller logic can be simply written and wired into the existing enterprise application; and 3) increased design complexity: the separation of model, view, and controller allows for the introduction of additional classes (Figure 10 ).…”
Section: Resultsmentioning
confidence: 99%
“…The system was designed using one of the most accepted Web application architectures, the model-view-controller (MVC) pattern [ 20 , 21 ]. This design provides extensive flexibility and scalability because of 1) re-use of model components: the separation of model and view components allows multiple views to use the same enterprise model; 2) easy support for new UI/clients: to support a new UI/client, the view and some controller logic can be simply written and wired into the existing enterprise application; and 3) increased design complexity: the separation of model, view, and controller allows for the introduction of additional classes (Figure 10 ).…”
Section: Resultsmentioning
confidence: 99%
“…Any user-oriented web application can be decomposed to a number of steps, each one concerned with a specific portion of user-application interaction. Furthermore, the wide adoption of the Model-View-Controller (MVC) pattern that is considered to be the standard for web application development provides sufficient decomposition of the application into a number of components whose roles are specialized [24]. MVC frameworks (e.g.…”
Section: Introductionmentioning
confidence: 99%