scholarly journals Runtime metric meets developer - Building better cloud applications using feedback

2015 ◽  
Author(s):  
Jürgen Cito ◽  
Philipp Leitner ◽  
Harald C. Gall ◽  
Aryan Dadashi ◽  
Anne Keller ◽  
...  
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Feedback Loops ◽  
Runtime Monitoring ◽  
Code Optimization ◽  
Proof Of Concept ◽  
Software Products ◽  
Code Changes ◽  
Cost Implications ◽  
Cloud Applications

A unifying theme of many ongoing trends in software engineering is a blurring of the boundaries between building and operating software products. In this paper, we explore what we consider to be the logical next step in this succession: integrating runtime monitoring data from production deployments of the software into the tools developers utilize in their daily workflows (i.e., IDEs) to enable tighter feedback loops. We refer to this notion as feedback-driven development (FDD). This more abstract FDD concept can be instantiated in various ways, ranging from IDE plugins that implement feedback-driven refactoring and code optimization to plugins that predict performance and cost implications of code changes prior to even deploying the new version of the software. We demonstrate existing proof-of-concept realizations of these ideas and illustrate our vision of the future of FDD and cloud-based software development in general. Further, we discuss the major challenges that need to be solved before FDD can achieve mainstream adoption.

scholarly journals Runtime metric meets developer - Building better cloud applications using feedback

2015 ◽  
Author(s):  
Jürgen Cito ◽  
Philipp Leitner ◽  
Harald C. Gall ◽  
Aryan Dadashi ◽  
Anne Keller ◽  
...  
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Feedback Loops ◽  
Runtime Monitoring ◽  
Code Optimization ◽  
Proof Of Concept ◽  
Software Products ◽  
Code Changes ◽  
Cost Implications ◽  
Cloud Applications

A unifying theme of many ongoing trends in software engineering is a blurring of the boundaries between building and operating software products. In this paper, we explore what we consider to be the logical next step in this succession: integrating runtime monitoring data from production deployments of the software into the tools developers utilize in their daily workflows (i.e., IDEs) to enable tighter feedback loops. We refer to this notion as feedback-driven development (FDD). This more abstract FDD concept can be instantiated in various ways, ranging from IDE plugins that implement feedback-driven refactoring and code optimization to plugins that predict performance and cost implications of code changes prior to even deploying the new version of the software. We demonstrate existing proof-of-concept realizations of these ideas and illustrate our vision of the future of FDD and cloud-based software development in general. Further, we discuss the major challenges that need to be solved before FDD can achieve mainstream adoption.

Obstacles for the Integration of HCI Practices into Software Engineering Development Processes

2006 ◽  
pp. 422-428 ◽  
Author(s):  
Xavier Ferre ◽  
Natalia Juristo ◽  
Ana M. Moreno
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Computer Literacy ◽  
Software Process ◽  
Software Systems ◽  
Software Products ◽  
Software Market ◽  
Visible Part ◽  
Software Product ◽  
Development Processes

Usability has become a critical quality factor in software systems, and it has been receiving increasing attention over the last few years in the SE (software engineering) field. HCI techniques aim to increase the usability level of the final software product, but they are applied sparingly in mainstream software development, because there is very little knowledge about their existence and about how they can contribute to the activities already performed in the development process. There is a perception in the software development community that these usability-related techniques are to be applied only for the development of the visible part of the UI (user interface) after the most important part of the software system (the internals) has been designed and implemented. Nevertheless, the different paths taken by HCI and SE regarding software development have recently started to converge. First, we have noted that HCI methods are being described more formally in the direction of SE software process descriptions. Second, usability is becoming an important issue on the SE agenda, since the software products user base is ever increasing and the degree of user computer literacy is decreasing, leading to a greater demand for usability improvements in the software market. However, the convergence of HCI and SE has uncovered the need for an integration of the practices of both disciplines. This integration is a must for the development of highly usable systems. In the next two sections, we will look at how the SE field has viewed usability. Following upon this, we address the existing approaches to integration. We will then detail the pending issues that stand in the way of successful integration efforts, concluding with the presentation of an approach that might be successful in the integration endeavor.

scholarly journals Reuse Alternatives based on the Sources of Software Assets

2021 ◽  
Vol 10 (1) ◽  
Author(s):  
Anas AL-Badareen
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Software Reuse ◽  
Development Process ◽  
Software Systems ◽  
Software Development Process ◽  
Software Products ◽  
Engineering Discipline

    Abstract— Since the idea of software reuse appeared in 1968, software reuse has become a software engineering discipline. Software reuse is one of the main techniques used to enhance the productivity of software development, which it helps reducing the time, effort, and cost of developing software systems, and enhances the quality of software products. However, software reuse requires understanding, modifying, adapting and testing processes in order to be performed correctly and efficiently. This study aims to analyze and discuss the process of software reuse, identify its elements, sources and usages. The alternatives of acquiring and using software assets either normal or reusable assets are discussed. As a result of this study, four main methods are proposed in order to use the concept of reuse in the software development process. These methods are proposed based on the source of software assets regardless the types of software assets and their usages.

scholarly journals Scrum: An Agile Process Reengineering in Software Engineering

2020 ◽  
Vol 9 (3) ◽  
pp. 840-848 ◽  
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Control Theory ◽  
Engineering Management ◽  
Vital Role ◽  
Team Members ◽  
Software Products ◽  
Development Organizations ◽  
Organizational Mechanism ◽  
Agile Process

BPR (Business Process Re-engineering) is an organizational mechanism leading organization towards change management as and when it is required. In the form BPR, Agile practices have had a remarkable impact on Software Engineering Management (SEM) in software development organizations across the world. It has enhanced collaboration and productivity of Software Engineering (SE) teams and improved the level of quality of software products. Nowadays Scrum has been trending into software development organizations as a standard SDLC approach. Scrum is the framework of the Agile methodology, built on empiricism control theory, asserts that experience brings knowledge and increases decision making capabilities. The empiricism control theory is built on three pillars: Adaptation, Inspection and Transparency. This research study presents Scrum as a trending SDLC framework using empirical analysis. We have analyzed literature reviews, case studies, and research surveys; and implemented Scrum in our software development unit and carried out the reasons, why Scrum is trending in software development organizations. How the scrum artifacts, events and values play a vital role in upholding the Scrum pillars and strengthen the capabilities of Scrum team members to address the software engineering management challenges; compared to traditional software development approaches.

scholarly journals End-User Software Development: Effectiveness of a Software Engineering-Centric Instructional Strategy

10.28945/4580 ◽  
2020 ◽  
Vol 19 ◽  
pp. 367-393 ◽  
Author(s):  
Ilenia Fronza ◽  
Luis Corral ◽  
Claus Pahl
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Instructional Strategies ◽  
Case Studies ◽  
Instructional Strategy ◽  
End Users ◽  
Assessment Framework ◽  
End User ◽  
Software Products ◽  
Software Product

Aim/Purpose: This work aims to introduce and evaluate an instructional strategy that aids end-users with developing their software products during intensive project-based events. Background: End-users produce software in the labor market, and one of the challenges for End-User Software Engineering (EUSE) is the need to create functional software products without a formal education in software development. Methodology: In this work, we present an instructional strategy to expose end-users to Agile-based Software Engineering (SE) practices and enhance their ability to developing high-quality software. Moreover, we introduce a SE approach for the collection of metrics to assess the effectiveness of the instructional strategy. We conducted two case studies to validate the effectiveness of our strategy; the comprehensive analysis of the outcome products evaluates the strategy and demonstrates how to interpret the collected metrics. Contribution: This work contributes to the research and practitioner body of knowledge by leveraging SE centric concepts to design an instructional strategy to lay the foundations of SE competencies in inexperienced developers. This work presents an instructional strategy to develop SE competencies through an intensive and time-bound structure that may be replicated. Moreover, the present work introduces a framework to evaluate these competencies from a product-centric approach, specialized for non-professional individuals. Finally, the framework contributes to understanding how to assess software quality when the software product is written in non-conventional, introductory programming languages. Findings: The results show the effectiveness of our instructional strategy: teams were successful in constructing a working software product. However, participants did not display a good command of source code order and structure. Recommendations for Practitioners: Our instructional strategy provides practitioners with a framework to lay foundations in SE competencies during intensive project-based events. Based on the results of our case studies, we provide a set of recommendations for educational practice. Recommendation for Researchers: We propose an assessment framework to analyze the effectiveness of the instructional strategy from a SE perspective. This analysis provides an overall picture of the participants’ performance; other researchers could use our framework to evaluate the effectiveness of their activities, which would contribute to increasing the possibility of comparing the effectiveness of different instructional strategies. Impact on Society: Given the number of end-user developers who create software products without a formal SE training, several professional and educational contexts can benefit from our proposed instructional strategy and assessment framework. Future Research: Further research can focus on improving the assessment framework by including both process and product metrics to shed light on the effectiveness of the instructional strategies.

Software Security Engineering – Part I

2015 ◽  
pp. 459-494
Author(s):  
Issa Traore ◽  
Isaac Woungang
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Development Process ◽  
Software Security ◽  
Security Assessment ◽  
Security Engineering ◽  
Model Driven ◽  
Software Vulnerabilities ◽  
Software Products ◽  
Assessment And Testing

It has been reported in the literature that about twenty new software vulnerabilities are reported weekly. This situation has increased the security awareness in the software community. Nowadays, software services are expected not only to satisfy functional requirements but also to resist malicious attacks. As demand for more trustworthy systems is increasing, the software industry is adjusting itself to security standards and practices by increasing security assessment and testing effort. Even though there is a consensus that better software engineering is to improve software quality in the early stage of software development, so far, various approaches that have been proposed to analyze and quantitatively measure the software security target, primarily show the finished software products in their operational life. There are few achievements on how to reduce or effectively mitigate the security risks faced by software products during the development process. In this chapter, the authors introduce a novel model-driven perspective on secure software engineering, which integrates seamlessly software security analysis with traditional software development activities. A systematic security engineering process that starts in the early stages of the software development process and spans the entire software lifecycle is presented. Fundamental software security concepts and analysis techniques are also introduced, and several illustrative examples are presented, with focus on security requirements and risk analysis.

A Quantitative Study of Waterfall and Agile Methodologies With the Perspective of Project Management

2022 ◽  
pp. 111-133
Author(s):  
Kenish Rajesh Halani ◽  
Kavita Jhajharia
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Extreme Programming ◽  
Prototype Model ◽  
Software Products ◽  
Customer Involvement ◽  
Waterfall Model ◽  
Almost All ◽  
Spiral Model ◽  
Agile Model

Software engineering is used in order to develop larger and complex software products. As software product is needed in almost all the industries, software engineering becomes really important. Software development can be done through various software development life cycle (SDLC) models like waterfall model, agile model, spiral model, prototype model, etc. SDLC is a framework that defines the tasks that to be performed at each step in the development process. Authors are mainly focusing on two models (i.e., waterfall and agile model). Waterfall model is a serial model which follows a strict sequence. Agile methodology can be divided into scrum methodology and extreme programming. Scrum methodology mainly focuses on how to manage tasks in a team-based environment. Scrum consists of three main roles. They are scrum master, product owner, and scrum team. While comparing both the models, the main difference obtained is waterfall does not allow any customer involvement while agile does allow it.

Software Security Engineering – Part I

2013 ◽  
pp. 221-255 ◽  
Author(s):  
Issa Traore ◽  
Isaac Woungang
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Development Process ◽  
Software Security ◽  
Security Assessment ◽  
Security Engineering ◽  
Model Driven ◽  
Software Vulnerabilities ◽  
Software Products ◽  
Assessment And Testing

It has been reported in the literature that about twenty new software vulnerabilities are reported weekly. This situation has increased the security awareness in the software community. Nowadays, software services are expected not only to satisfy functional requirements but also to resist malicious attacks. As demand for more trustworthy systems is increasing, the software industry is adjusting itself to security standards and practices by increasing security assessment and testing effort. Even though there is a consensus that better software engineering is to improve software quality in the early stage of software development, so far, various approaches that have been proposed to analyze and quantitatively measure the software security target, primarily show the finished software products in their operational life. There are few achievements on how to reduce or effectively mitigate the security risks faced by software products during the development process. In this chapter, the authors introduce a novel model-driven perspective on secure software engineering, which integrates seamlessly software security analysis with traditional software development activities. A systematic security engineering process that starts in the early stages of the software development process and spans the entire software lifecycle is presented. Fundamental software security concepts and analysis techniques are also introduced, and several illustrative examples are presented, with focus on security requirements and risk analysis.

scholarly journals Are UX Evaluation Methods Providing the Same Big Picture?

Sensors ◽  
2021 ◽  
Vol 21 (10) ◽  
pp. 3480
Author(s):  
Walter Takashi Nakamura ◽  
Iftekhar Ahmed ◽  
David Redmiles ◽  
Edson Oliveira ◽  
David Fernandes ◽  
...  
Keyword(s):  
Software Development ◽  
Decision Process ◽  
Development Process ◽  
Evaluation Methods ◽  
Sentence Completion ◽  
Software Development Process ◽  
Software Application ◽  
Software Products ◽  
Big Picture ◽  
The Impact

The success of a software application is related to users’ willingness to keep using it. In this sense, evaluating User eXperience (UX) became an important part of the software development process. Researchers have been carrying out studies by employing various methods to evaluate the UX of software products. Some studies reported varied and even contradictory results when applying different UX evaluation methods, making it difficult for practitioners to identify which results to rely upon. However, these works did not evaluate the developers’ perspectives and their impacts on the decision process. Moreover, such studies focused on one-shot evaluations, which cannot assess whether the methods provide the same big picture of the experience (i.e., deteriorating, improving, or stable). This paper presents a longitudinal study in which 68 students evaluated the UX of an online judge system by employing AttrakDiff, UEQ, and Sentence Completion methods at three moments along a semester. This study reveals contrasting results between the methods, which affected developers’ decisions and interpretations. With this work, we intend to draw the HCI community’s attention to the contrast between different UX evaluation methods and the impact of their outcomes in the software development process.

Sign in / Sign up

Export Citation Format

Share Document