Evolution of Web Systems

Kienle, Holger M.; Distante, Damiano

doi:10.1007/978-3-642-45398-4_7

Cited by 8 publications

(4 citation statements)

References 88 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As an example of this impact, it is worth mentioning the many research works that has been done and the several approaches that have been proposed for the reverse engineering and the evolution of existing Web applications adopting MDWE methods, models, and techniques. A survey on this research can be found in [47].…”

Section: Technical Recognitionmentioning

confidence: 99%

“…In this sense, Web Engineering uses techniques of information engineering, hypertext and hypermedia design, information retrieval and data mining, graphic and interaction design, etc. Both Software Engineering and Web Engineering involve software development and its life cycle (including maintenance and evolution [47]), and so they share an important theoretical and practical corpus; however, Web Engineering must go beyond this. One of the most important common problems of both disciplines is the need to describe and build systems using models as a way to solve some of the previously discussed problems.…”

Section: -Introduction and Motivationmentioning

confidence: 99%

See 1 more Smart Citation

25 Years of Model-Driven Web Engineering: What we achieved, What is missing

Rossi¹,

Urbieta²,

Distante

et al. 2016

CLEIej

Self Cite

View full text Add to dashboard Cite

Model-Driven Web Engineering (MDWE) approaches aim to improve the Web applications development process by focusing on modeling instead of coding, and deriving the running application by transformations from conceptual models to code. The emergence of the Interaction Flow Modeling Language (IFML) has been an important milestone in the evolution of Web modeling languages, indicating not only the maturity of the field but also a final convergence of languages. In this paper we explain the evolution of modeling and design approaches since the early years (in the 90’s) detailing the forces which drove that evolution and discussing the strengths and weaknesses of some of those approaches. A brief presentation of the IFML is accompanied with a thorough analysis of the most important achievements of the MDWE community as well as the problems and obstacles that hinder the dissemination of model-driven techniques in the Web engineering field.

show abstract

Section: Technical Recognitionmentioning

confidence: 99%

Section: -Introduction and Motivationmentioning

confidence: 99%

25 Years of Model-Driven Web Engineering: What we achieved, What is missing

Rossi¹,

Urbieta²,

Distante

et al. 2016

CLEIej

Self Cite

View full text Add to dashboard Cite

show abstract

“…This information, which is easily accessible via the Internet, is considered an invaluable asset for software developers and service providers, to help them understand how to improve their software application or service, and get inspiration for new functionalities and products [1,2]. This information deliberately provided by the users is generally called explicit user feedback and can be used as a complement to implicit user feedback, i.e.…”

Section: Introductionmentioning

confidence: 99%

Providing Foundation for User Feedback Concepts by Extending a Communication Ontology

Morales-Ramirez

Perini

Guizzardi

2014

Conceptual Modeling

View full text Add to dashboard Cite

Abstract. The term user feedback is becoming widely used in requirements engineering (RE) research to refer to the comments and evaluations that users express upon having experienced the use of a software application or service. This explicit feedback takes place in virtual spaces (e.g., issue tracking systems, app stores), aiming, for instance, at reporting on discovered bugs or requesting new features. Founding the notion of explicit user feedback with the use of an ontology may support a deep understanding of the feedback nature, as well as contribute to the development of tool-components for its analysis at use of requirements analysts. In this paper, we present a user feedback ontology as an extension of an existing communication ontology. We describe how we built it, along with a set of competency questions, and illustrate its applicability on an example taken from a collaborative communication related to RE for software evolution.

show abstract

“…Due to the technological advances as well as changes in website design, a typical website nowadays looks different to a website from 5 years ago (Kienle and Distante, 2014;O'Reilly and Battelle, 2009;Trends in web technology, 2015). It remains unclear, however, if users' expectations and mental representation of websites have changed as well.…”

Section: Introductionmentioning

confidence: 99%

Is It Still Where I Expect It?—Users’ Current Expectations of Interface Elements on the Most Frequent Types of Websites

et al. 2016

View full text Add to dashboard Cite

Knowing users' expectations about what they expect on a website and where they expect to find it is crucial for the success of a website. For the last decade, technological advances have entailed major changes in website design but the impact of these changes on users' mental representations of websites remains unclear. In an online study (N = 841), we asked users to sketch their prototypical version of an online shop, a news website and a company page, thereby indicating the interface elements they expect on the website and their expected location. We compared our results to those of a previous study to investigate changes in users' mental representations of websites over time. This comparison suggests that interface elements such as the logo, main content and navigation area are still expected in the same location although others have shifted to the rich footer area at the bottom of the website. In addition, new elements such as links to social networks have been incorporated into users' mental representations whereas other interface elements have disappeared. By providing updated consolidated blueprint models for all three website types, we help designers to create expectation-based websites. Further implications for research and practitioners are discussed. RESEARCH HIGHLIGHTS• Measuring current expectations about the location of interface elements, • Website layout: composition and expected location of interface elements,• Gain insights into developments in users' expectations over time.

show abstract

Evolution of Web Systems

Cited by 8 publications

References 88 publications

25 Years of Model-Driven Web Engineering: What we achieved, What is missing

25 Years of Model-Driven Web Engineering: What we achieved, What is missing

Providing Foundation for User Feedback Concepts by Extending a Communication Ontology

Is It Still Where I Expect It?—Users’ Current Expectations of Interface Elements on the Most Frequent Types of Websites

Contact Info

Product

Resources

About