@conference {2021:icwe:fullstack, title = {Full Stack is Not What It Used to Be}, booktitle = {21st International Conference on Web Engineering (ICWE2021)}, year = {2021}, month = {May}, publisher = {Springer}, organization = {Springer}, address = {Biarritz, France}, abstract = {The traditional definition of full stack development refers to a skill set that is required for writing software both for the frontend and backend of a web application or site. In recent years, the scope of full stack development has expanded significantly, though. Today, a full stack software developer is assumed to master various additional areas especially related to cloud infrastructure and deployment, message brokers and data analytics technologies. In addition, the emergence of Internet of Things (IoT) and the rapidly spreading use of AI/ML technologies are introducing additional skill set requirements. In this paper, we discuss the expectations for a modern full stack developer based on our industry observations, and argue that these expectations have significant implications for software and web engineering education.}, keywords = {Cloud, Education, Internet of Things, IoT, Programmable World, software architecture, software engineering, Web engineering}, doi = {10.1007/978-3-030-74296-6_28}, author = {Antero Taivalsaari and Tommi Mikkonen and Cesare Pautasso and Kari Systa} } @conference {2017:icsa:web, title = {Comparing the Built-In Application Architecture Models in the Web Browser}, booktitle = {1st IEEE International Conference on Software Architecture (ICSA 2017)}, year = {2017}, month = {April}, publisher = {IEEE}, organization = {IEEE}, address = {Gothenburg, Sweden}, abstract = {Depending on one{\textquoteright}s viewpoint, a generic standards-compatible web browser supports three, four or five built-in application rendering and programming models. In this paper, we provide an overview of the built-in client-side web application architectures. While the dominance of the base HTML/CSS/JS technologies cannot be ignored, we foresee Web Components and WebGL gaining popularity as the world moves towards more complex and even richer web applications, including systems supporting virtual and augmented reality.}, keywords = {Web application architecture, Web development, Web engineering}, author = {Antero Taivalsaari and Tommi Mikkonen and Cesare Pautasso and Kari Systa} } @proceedings {2016:icwe, title = {Web Engineering}, volume = {9671}, year = {2016}, month = {June}, pages = {XXVI, 626}, publisher = {Springer}, address = {Lugano, Switzerland}, keywords = {Web engineering}, issn = {978-3-319-38790-1}, doi = {10.1007/978-3-319-38791-8}, url = {http://icwe2016.webengineering.org}, author = {Alessandro Bozzon and Philippe Cudr{\'e}-Mauroux and Cesare Pautasso} } @proceedings {2016:icwe:workshop, title = {Web Engineering Workshops}, volume = {9881}, year = {2016}, month = {June}, pages = {209}, publisher = {Springer}, address = {Lugano, Switzerland}, keywords = {Web engineering}, issn = {978-3-319-46962-1}, doi = {10.1007/978-3-319-46963-8}, url = {http://icwe2016.webengineering.org}, author = {Sven Casteleyn and Peter Dolog and Cesare Pautasso} } @article {triglianos2013www, title = {ASQ: Interactive Web Presentations for Hybrid MOOCs}, year = {2013}, month = {May}, address = {Rio de Janeiro, Brazil}, abstract = {ASQ is a Web application for creating and delivering interactive HTML5 presentations. It is designed to support teachers that need to gather real-time feedback from the students while delivering their lectures. Presentation slides are delivered to viewers that can answer the questions embedded in the slides. The objective is to maximize the efficiency of bi-directional communication between the lecturer and a large audience. More specifically, in the context of a hybrid MOOC classroom, a teacher can use ASQ to get feedback in real time about the level of comprehension of the presented material while reducing the time for gathering survey data, monitoring attendance and assessing solutions.}, keywords = {ASQ, hybrid MOOC, Web engineering}, url = {http://dl.acm.org/citation.cfm?id=2487894}, author = {Vasileios Triglianos and Cesare Pautasso} } @article {babazadeh2013www, title = {The Atomic Web Browser}, year = {2013}, month = {May}, pages = {217-218}, address = {Rio de Janeiro, Brazil}, abstract = {The Atomic Web Browser achieves atomicity for distributed transactions across multiple RESTful APIs. Assuming that the participant APIs feature support for the Try-Confirm/Cancel pattern, the user may navigate with the Atomic Web Browser among multiple Web sites to perform local resource state transitions (e.g., reservations or bookings). Once the user indicates that the navigation has successfully completed, the Atomic Web browser takes care of confirming the local transitions to achieve the atomicity of the global transaction.}, keywords = {REST, REST transactions, try-confirm-cancel, Web engineering}, url = {http://dl.acm.org/citation.cfm?id=2487788.2487899}, author = {Cesare Pautasso and Masiar Babazadeh} }