Agile Development Model Research Articles

Partial Least Square Structural Equation Modeling in the Final Phase of Product and Instrument Development Using Universal Design and Agile Development Model

The partial least squares path modeling or PLS-PM, is best known as the partial least squares structural equation modeling or PLS-SEM. It is a method of structural equation modeling. This method allow the estimation of complex cause and effect relationship models with latent variables. This paper explain how this method can be use in the final stage of a product design and development study. In the study, learning outcome becomes the center for universal design, development and implementation processes. There are two stages of major processes. First is the instructional design processes while the second is the development processes. The development processes ends with usability test. The next phase is the evaluation phase. Last phase is the modeling processes. The paper will first explain about the localized model of product design and development procedure. Subsequently it will elaborate the final phase of the second stage processes, which is important in impact study of product design and development. While at this, the partial least square structural equation modeling will be explain. It is a powerful statistical technique yet misconceptions happen a lot. Proper techniques is essential for methodological assumptions in order to attain robust results. Using latest software alone is not enough.

Sistema web de solicitudes de acceso a la información

The Secretariat of the Comptroller and Government Transparency of the State of Oaxaca (SCTGEO) has an objective with the development of the project called Web System of Requests for Access to Information. This objective is to contribute to internal control of the Requests for Access to Information that are sent to the dependencies, entities, auxiliary bodies, and, escrows that integrate State Public Administration. It also follows up that the Requests are attended to and are fulfilled within the terms established by the Law of Transparency and Access to Public Information for the State of Oaxaca (LGTAIPO). The web system has the following functionalities: a history of requests and responses, it allows the use of different response formats; it generates reports based on a period defined by the user; it allows you to schedule meetings, and it follows up if necessary. In addition, it has a Request, Dependencies module and an internal chat so that they can communicate with each other. The web system was based on the agile development model using Extreme Programming (XP) and the MySql database manager was used.

Identification and integration of security activities for secure agile development

Agile software development is receiving the attention of software developers and researchers thanks to its fast software delivery and flexible development plan capabilities. The fast release and simplified documentation thus leads to the preference of the agile development model over several other traditional models. This, however, also raises critical concerns about the security issues. In this research work, we propose a framework for secure agile development. The selection of development methodology among agile versus plan driven approaches and the particular agile development method among Extreme Programming (XP), Crystal Clear, Scrum, Lean Development, Dynamic Software Development Method and Feature-Driven Development is made on the basis of the specific requirements of the project using empirical methods like AHP and PROMETHEE. Systematic Literature Review (SLR) and survey study are used to obtain the authentic industrial feedback, followed by the application of non-parametric statistical tests to identify and select the most suitable and beneficial security activities from well known security engineering processes like CLASP, Common Criteria, Cigital Touchpoints and Microsoft’s SDL. A lightweight method is also introduced for integrating these security activities identified from SLR and survey study, using a dynamic integration algorithm without compromising the agility of the process. The proposed framework for integration of these security activities is implemented in java to automate the entire process and provides maximum benefit at a low integration cost.

Novel Approach for Mobile Based App Development Incorporating MAAF

Increased dominance of mobile applications (henceforth, app) over conventional software applications is quite apparent; however, there is a lack of structured mechanisms for efficient mobile application development. Classical software development models were successfully used with conventional applications with or without adaptations, but due to the distinctive characteristics of apps, these development models are not suitable to rely upon. Agile development models proved themselves worthy of using in different development environments and team traits irrespective of the software application size. It is evident that incorporating agility in the software development paradigm not only speeds up the development process, but it also eases the communication flow between the client and the development team. It is also observed that peculiar characteristic of an app development project is the constant negotiations between the client and the team. Thus, agile and mobile forms a ridge-and-groove formation and deem fit to fulfill various parameters of mobile application development—if applied appropriately. The objective of this paper is to determine the agility of an app project in the subject and to propose a recommendation framework based on this agility and other project characteristics. For convenience, we call this framework as MAAF—Mobile Application Agility Framework. This framework is validated by assigning the same project to be built by four different agile teams. Out of the four agile teams, one team used the technique recommended by the proposed framework, and the other three teams adopted agile methods of their choice. This process is repeated for five different mobile app projects. The developed apps were later presented to the user community for ratings. The rating reports suggest that the proposed recommendation framework based on agility indeed works satisfactorily. The outcome of this work will help app developers and project managers deliver solutions in time and with utmost customer satisfaction.

Applying Continuous Integration for Increasing the Maintenance Quality and Efficiency of Web App

In order to project resource management and time control, software system needs to be decomposed into subsystems, functional modules and basis components. Finally, all tested components have to integrate to be the complete system. Applying IID (Iterative Incremental Development) mechanism, agile development model becomes the practical method to reduce software project failure rate. Continuous integration (CI) is an IID implementation concept which can effectively reduce software development risk. Web app with high change characteristic is suitable to use agile development model as the development and maintenance methodology. The paper depth surveys CI operating environment and advantages. Introducing CI concept can make up the moving target problems to impact of Web app. For this, the paper proposes a Continuous Integration based Web Applications Maintenance Procedure (CIWAMP) to assist the system integration operating. Based on CI characteristics, CIWAMP makes Web app can be deployed quickly, increase stakeholder communication frequency, improve staff morale, and effectively reduce Web app maintenance quality and efficiency

Blended Scrum model for software development organizations

AbstractSoftware organizations have to develop software in a short time, and quickly respond to changing requirements. Recently, organizations have started to implement agile development models to reduce cost and increase productivity and quality. Scrum, one of the most widely used agile methodologies, is often implemented in various ways that depart in an uncontrolled fashion from the original model, resulting in development methods often called “ScrumBut.” Some argue that such incomplete implementations violate Scrum's core practices and philosophy, while others propose that all methodologies should be adapted to organization's unique culture and integrated with their best practices.In this research, a Blended Scrum model was proposed to overcome uncontrolled ScrumBut issues while transitioning to Scrum. The study was organized as a case study in which software professionals working in Scrum teams were interviewed. In addition, a questionnaire was conducted with other software professionals to determine how agile methods, specifically Scrum, were used. The interviews and questionnaire revealed various Scrum practical implementations. The Blended Scrum model was developed by integrating original Scrum with practices that were determined by interviews and questionnaire conducted with software professionals with real‐world Scrum experience. Finally, the Blended Scrum model was evaluated by Scrum professionals and received positive feedback.

Digital business model effectuation: An agile approach

The radical changes in today's competitive environment created a “big bang” effect: companies and industries are being disrupted in an unprecedented short time. The challenge has shifted from predicting the unknown or conventional method of venture creation to agile actions, which is to act rapidly before the competition catches up and eliminate any advantage one may have, especially for entrepreneurs and small businesses with significant resource constraints. The objective of this research is to investigate alternative approaches under a time-constrained setting. A recent national open innovation initiative of Finland challenged practitioners and researchers to transform technologies into commercializable innovations in under six months. A high-tech case within the challenge piloted the agile effectuation of a business model with three parallel approaches: effectuation, causation and lean startup method, thus providing antecedent on how effectuation theory can be integrated with agile development and business model theory.

A Survey on Software Estimation Techniques in Traditional and Agile Development Models

<p>Software projects mostly exceeds budget, delivered late and does not meet with the customer’s satisfaction for years. In the past, many traditional development models like waterfall, spiral, iterative, and prototyping methods are used to build the software systems. In recent years, agile models are widely used in developing the software products. The major reasons are – simplicity, incorporating the requirement changes at any time, light-weight approach and delivering the working product early and in short duration. Whatever the development model used, it still remains a challenge for software engineer’s to accurately estimate the size, effort and the time required for developing the software system. This survey focuses on the existing estimation models used in traditional as well in agile software development.</p>

Prospect: A Picture Exchange Communication System (PECS)-based Instant Messaging Application for Autism Spectrum Condition

Autism Spectrum Disorder (ASC) has widely gained the common attention from the public especially autistic communities. Individuals with ASC are said to have poor verbal skills and this affects them in carrying out their daily basis which they are afraid to expose themselves to the world due to their problems. ASC is diagnosed among children ranging from ages 5-12 years old and they suffer from the abnormal functioning of the brain which in turn causes lack of development activities. Thus, studies have shown that diagrammatic approaches help children with ASC to overcome their issues and improvise their visual and verbal skills. Picture Exchange Communication System or PECS consists of a series of illustrated cards and each cards has its own illustration with a caption on it. These children will understand the cards and they can compile several other cards to form sentences. This paper presents a mobile application called the Prospect, which has been developed using the agile development model for digital representation of PECS. The application is hoped to enhance the learning process and a better yielding results.

Client Communication: A Major Issue in Agile Development

Agile development model solved a lot of its predecessor the waterfall model problems like time, cost, resources and high risk of failure due to incomplete or inaccurate requirements. However, agile model introduced the client communication problem; due to the structure and nature of agile methodologies, it depends heavily on communicating with client. With four layers of communication that get repeated in almost every agile iteration, failing to handle client communication is one of the main reasons behind failure of agile based projects. In this paper, we survey the existing methods of communication which are classified into two main categories: physical meetings/workshops and software communication tools. Each category is assessed and compared based on certain attributes such as availability, productivity, cost, reliability, trust and project coverage. In addition, the available solutions to address the communication problem, which include enhanced physical meetings/workshops and software tools like requirement engineering tools, agile management tools and social media sites and applications, are analyzed and assessed based on attributes such as usability, formality and project coverage. The study revealed that the available solutions did not address all the aspects of the communication problem. Therefore, it is desirable to develop an integrated solution which utilized communication software tool using social media frameworks as its backbone and physical meetings to benefit from human interaction and relationships to solve the communication problem in agile environment.

Delineation and Elucidation of Security Activities in Agile Software Development

Agile programming advancement process is an arrangement of standards utilized for programming improvement. In Agile programming improvement the arrangements develop through coordinated effort between self-sorting out, cross-useful groups using the fitting practices for their unique situation. This paper suggests guidelines that may be followed in agile software development process. We have conducted a survey approximately 500 agile software developers, around the globe, have taken part in it. In survey a questionnaire related to the various security activities to be incorporated during every phase of agile software development were asked. Based on this survey we have accomplished the most compatible and beneficial security activity that can be incorporated during different phases of agile software development. 80% of agile developers voted for the initial education which is the important security activity to be incorporated during Prerequirement phase. Similarly 75% said that security requirements during requirement phase, 95% opted for risk analysis during design phase, 80% said coding rules during implementation phase, 62% said identify, perform and implement security tests in testing phase and 77% said final security review in release phase are to be incorporated during different phases of agile software development. The Proposed work overcomes the issues in agile model and security by giving a quick comprehension of the security activities incorporated during different phases of software development. We have bridge-in, the security gap between traditional waterfall model and in-practice agile development model.

Managing the transition to the new agile business and product development model: Lessons from Cisco Systems

Through an in-depth case study of Cisco Systems, this Executive Digest finds that companies face two broad challenges when transitioning to the agile product development model. The first is identifying and helping business units and engineering teams adopt this method; the second is developing new management practices that are compatible with and can sustain the agile development practices. Although extant literature has conducted many analyses on these two challenges, there still exist gaps in the research of the agile development method. Herein, we explore how Cisco Systems addressed these two challenges followed by a discussion of the broad implications of adopting the agile development method. This research deepens our understanding of how to adopt and lead the agile development process.

MADCE - TVD - Model Agile Development Educational Content for Digital Television

The software engineering discipline that allows to develop methods and processes that ensure success in building software products, consequently is relevant to instantiate these practices in the development of educational content for t-learning, enabling the development and supply of educational content for digital television. This article proposes a MADCE-TVD - Agile Development Model of Educational Content to Digital Television This is based on the methodologies, agile values and principles. This research is part of the model of good practice for the development of educational content for T-learning.

Agile Product Development Model Focused on the Telecommunication Service

The Telecommunications Industry has a highly competitive and constant technological innovation scenario. Therefore, its Product Development Process (PDP) must have adequate structure and agility. In this context, this article presents a structure of the PDP to providers of telecommunications services. This proposal was based on literature review and in two case studies in Brazil.

An Agile Development Bidirectional Iteration Model for Project Management Information System and its Application

With the rapid development of the IT, project management information was focused widely. In this paper, an agile development model based on bidirectional iteration for Project Management Information System (PMIS) was set up, in which the 9 modules of project management can be developed concurrently. Among the different development phases of the modules, the vertical iteration was used, and among the different functions in one module, the horizontal iteration was used. Finally, the model was applied to the PMIS of the Caozhuang pumping station project, which illustrated that with the model the constantly changing demands of the user can be satisfied and the high quality PMIS can be developed in time.

Systematic review of web application security development model

In recent years, web security has been viewed in the context of securing the web application layer from attacks by unauthorized users. The vulnerabilities existing in the web application layer have been attributed either to using an inappropriate software development model to guide the development process, or the use of a software development model that does not consider security as a key factor. Therefore, this systematic literature review is conducted to investigate the various security development models used to secure the web application layer, the security approaches or techniques used in the process, the stages in the development model in which the approaches or techniques are emphasized, and the tools and mechanism used to detect vulnerabilities. The study extracted 499 publications from respectable scientific sources, i.e. the IEEE Computer Society, ACM Digital Library, Google-Scholar, Science Direct, Scopus, Springer Link and ISI Web. After investigation, only 43 key primary studies were considered for this review based on defined inclusion and exclusion criteria. From the review, it appears that no one development model is referred to as a standard or preferred model for web application development. However, agile development models seem to have gained more attention, probably due to the multiple stakeholders that are involved in discussing security viewpoints, rather than a few members of the development team. It appears also that there is consistency in the use of the threat-modeling technique, probably due to its effectiveness in dealing with different kinds of vulnerabilities.

Designing an effective management system for enterprises: Concepts and verification

AbstractIn this article lean and agile manufacturing are considered as separate organizational strategies of enterprise management. Therefore, a model of these strategies for business situations as well as assigning modern concepts and methods of management to these strategies and business segments has been proposed. This model, called LABDM (lean agile business development model), has been provisionally verified in small‐ and medium‐sized enterprises from the gas engineering industry in the Wielkopolska province in Poland. In 17 enterprises of this industry the use of modern concepts and methods of management have been studied. With the help of the rough sets theory, a set of concepts and methods that are crucial for the effective enterprises has been identified. By comparing these concepts and methods to the LABDM, the model's rationality is proven. In conclusion, the LABDM can be used as a tool when considering a lean or agile strategy, and modern concepts and methods that are associated with these strategies. © 2008 Wiley Periodicals, Inc.

Affective assessment of team skills in agile CS1 labs

Team experiences can be important learning experiences, and industry highly values team skills in graduates. Low retention rates might also be improved with early team experiences because team experiences have been linked to increases in the sense of belonging, a key retention factor. Team experiences in upper-level courses could also benefit from earlier team experiences. The purpose of this paper is to describe and evaluate an early use of teams in the second semester of our CS1 sequence. The instructional methodology drew heavily upon the professional practices of an agile software development model, Extreme Programming. These professional practices fostered the development of team skills during a semester-long project in a closed lab. The evaluation of our experience revealed aspects of the good, the bad, and the ugly. Areas for improvement and future work are also explained.