scholarly journals Centralised Cleanup Service for Kubernetes and Cloud Resources

2021 ◽  
Vol 9 (VII) ◽  
pp. 1545-1549
Author(s):  
Pranava Bhat
Keyword(s):  
Software Development ◽  
Virtual Machines ◽  
Software Development Process ◽  
Architectural Style ◽  
Software Application ◽  
Engineering Teams ◽  
Loosely Coupled ◽  
Agile Software ◽  
Container Orchestration ◽  
Cloud Resources

The architectural style of developing a software application using loosely coupled and highly cohesive services can be termed as microservices architecture. The microservices allow agile software development and enable businesses to build and deliver applications quickly. To achieve the benefits of microservices, an underlying infrastructure that supports them must exist. This includes CI/CD pipelines, execution environments like virtual machines and containers, logging and monitoring, communication mechanisms, and so on. Containers are lightweight, enable multiple execution environments to exist on a single operating system instance, and provide isolation. Container Orchestration Engines such as Docker swarm or Kubernetes automate deployment, scaling, fault tolerance, and container networking. Many organizations use containers to spawn resources in public or private clouds. Different engineering teams perform various kinds of tests by bundling the test code and dependencies into containers. However, cleaning up these containers is necessary for the efficient utilization of hardware resources. This paper discusses the need and benefits of a centralized cleanup service for Kubernetes and cloud resources. It analyzes the value additions this service can bring to the software development process of large organizations.

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.

A Test-Driven Approach to Behavioral Queries for Service Selection

2014 ◽  
pp. 381-400
Author(s):  
Laura Zavala ◽  
Benito Mendoza ◽  
Michael N. Huhns
Keyword(s):  
Software Development ◽  
Service Discovery ◽  
Service Selection ◽  
Behavioral Approach ◽  
Loosely Coupled ◽  
Functional Quality ◽  
Agile Software ◽  
Quality Of Service Parameters ◽  
Key Aspects ◽  
Service Discovery And Selection

Although the areas of Service-Oriented Computing (SOC) and Agile and Lean Software Development (LSD) have been evolving separately in the last few years, they share several commonalities. Both are intended to exploit reusability and exhibit adaptability. SOC in particular aims to facilitate the widespread and diverse use of small, loosely coupled units of functionality, called services. Such services have a decided agility advantage, because they allow for changing a service provider at runtime without affecting any of a group of diverse and possibly anonymous consumers. Moreover, they can be composed at both development-time and run-time to produce new functionalities. Automatic service discovery and selection are key aspects for composing services dynamically. Current approaches attempting to automate discovery and selection make use of only structural and functional aspects of the services, and in many situations, this does not suffice to discriminate between functionally similar but disparate services. Service behavior is difficult to specify prior to service execution and instead is better described based on experience with the execution of the service. In this chapter, the authors present a behavioral approach to service selection and runtime adaptation that, inspired by agile software development techniques, is based on behavioral queries specified as test cases. Behavior is evaluated through the analysis of execution values of functional and non-functional parameters. In addition to behavioral selection, the authors’ approach allows for real-time evaluation of non-functional quality-of-service parameters, such as response time, availability, and latency.

scholarly journals IMPLEMENTATION OF REUSE IN THE AGILE SOFTWARE DEVELOPMENT PROCESS SCRUM

2017 ◽  
Vol 10 (13) ◽  
pp. 143 ◽  
Author(s):  
Jayasudha R ◽  
Viswanathan V ◽  
Shanthi P
Keyword(s):  
Software Development ◽  
Development Process ◽  
Dynamic Change ◽  
Agile Software Development ◽  
Agile Development ◽  
Software Development Process ◽  
Customer Requirements ◽  
Waterfall Model ◽  
Agile Software ◽  
First Time

The concept of reuse is applied in one of the agile development methodologies called the scrum. Sprint is a single functionality and the result at the end of the sprint functionality is derived as the shippable or bugs. This paper makes an attempt to use the concept of reuse in the agile software development to meet the dynamic change of customer requirements in banks. A banking project is created using both waterfall model and scrum model, and the knowledge gained is stored in the ontology-based repository for the first time. Again, the same project is created for different vendors using the ontology-based repository. The result shows that maximum sprint is reused and all the knowledge gained is stored in the form of ontology. This ontology helps identify the shippable component of each sprint which is a small executable functionality. This leads to less cost and time to deliver the product. The main aim is to increase the availability of the reusable artifacts, which lead to increase the reusability of the developer. The experimental results show improvements in the performance of retrieving the components for the software development.  

scholarly journals Applications supporting utilization of agile methods in software development process

2020 ◽  
Vol 14 ◽  
pp. 8-13
Author(s):  
Tomasz Bławucki ◽  
Siarhei Ramanovich ◽  
Maria Skublewska-Paszkowska
Keyword(s):  
Software Development ◽  
Development Process ◽  
Agile Software Development ◽  
Agile Methods ◽  
Tabular Form ◽  
Software Development Process ◽  
Internet Applications ◽  
Technical Requirements ◽  
Development Processes ◽  
Agile Software

The article presents a comparison in terms of hardware requirements of applications that supports the agile software development processes. For research purposes, popular mobile and internet applications supporting agile software development were chosen. In order to determine the significance of individual technical requirements for end-users, a series of research experiments, based on scenarios of typical and boundary use was conducted. In addition to research, the application supporting agile software development process was implemented. The results of research were recorded by specialized monitoring and profiling tools. The results of performed work are presented in tabular form.

A CRITICAL ANALYSIS AND COMPARISON OF AGILE WITH TRADITIONAL SOFTWARE DEVELOPMENT PROCESS

2017 ◽  
Vol 5 (4) ◽  
pp. 88-93
Author(s):  
Priyanka Kataria ◽  
Shweta Shrivas ◽  
Ishita Shukla ◽  
A. Hemlata
Keyword(s):  
Software Development ◽  
Creative Thinking ◽  
Development Process ◽  
Software Development Process ◽  
Agile Methodology ◽  
Short Period ◽  
Marginal Prices ◽  
Agile Software ◽  
New Software Development

During the past years, new software development approaches were introduced to suit within the new trend of the software development corporations. Most Software Corporation’s today aim to provide valuable software in short period of time with marginal prices and among unstable, ever-changing environments. Agile methodology focuses on the challenges of unpredictability of the real world by relying on individuals and their creative thinking instead of method. In this paper we tend to explore about the current agile methods, strengths and weaknesses of agile strategies and numerous problems with their relevancy. We have conjointly enclosed comparison between traditional software development process and agile software development process. This paper also includes brief discussion about the benefits and problems associated with these methodologies by performing case study of two corporations.

Component-based software development for integrated construction management software applications

2001 ◽  
Vol 15 (2) ◽  
pp. 173-187 ◽  
Author(s):  
FENIOSKY PEÑA-MORA ◽  
SANJEEV VADHAVKAR ◽  
SIVA KUMAR DIRISALA
Keyword(s):  
Software Development ◽  
Construction Management ◽  
Design Patterns ◽  
Development Process ◽  
Software Components ◽  
Design Rationale ◽  
Software Development Process ◽  
Software Application ◽  
Software Applications ◽  
Specific Implementation

This paper presents a framework and a prototype for designing Integrated Construction Management (ICM) software applications using reusable components. The framework supports the collaborative development of ICM software applications by a group of ICM application developers from a library of software components. The framework focuses on the use of an explicit software development process to capture and disseminate specialized knowledge that augments the description of the ICM software application components in a library. The importance of preserving and using this knowledge has become apparent with the recent trend of combining the software development process with the software application code. There are three main components in the framework: design patterns, design rationale model, and intelligent search algorithms. Design patterns have been chosen to represent, record, and reuse the recurring design structures and associated design experience in object-oriented software development. The Design Recommendation and Intent Model (DRIM) was extended in the current research effort to capture the specific implementation of reusable software components. DRIM provides a method by which design rationale from multiple ICM application designers can be partially generated, stored, and later retrieved by a computer system. To address the issues of retrieval, the paper presents a unique representation of a software component, and a search mechanism based on Reggia's setcover algorithm to retrieve a set of components that can be combined to get the required functionality is presented. This paper also details an initial, proof-of-concept prototype based on the framework. By supporting nonobtrusive capture as well as effective access of vital design rationale information regarding the ICM application development process, the framework described in this paper is expected to provide a strong information base for designing ICM software.

scholarly journals Several Ideas on Integration of SCRUM Practices within Microsoft Solutions Framework

2017 ◽  
Vol 21 (1) ◽  
pp. 71-79
Author(s):  
Jai Vigneshwar Alavandhar ◽  
Oksana Ņikiforova
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Software Project ◽  
Software Development Process ◽  
Engineering Process ◽  
Question Mark ◽  
Development Organisation ◽  
Software Engineering Process ◽  
Agile Software ◽  
New Software Development

Abstract In order to develop and deliver a software project successfully, any software development organisation has to follow a well-known and recognised software engineering process for successful delivery and maintenance of the software. However, when the organisation is willing to follow a new software development process, the success rate of adopting a new software engineering process is a question mark. In the paper, we aim at studying and comparing two software engineering processes, which are based on different paradigms or models, and proposing a hybrid methodology, which integrates advantages of both compared methods. They are Microsoft Solutions Framework as a representative for an iterative methodology and SCRUM for agile software development. The comparative analysis will help a software development company to make the transition easier from Microsoft Solutions Framework to SCRUM or vice versa.

Sign in / Sign up

Export Citation Format

Share Document