Iterative Development Methods Research Articles

Research on software reliability enhancement methods based on iterative development

Iterative development is an agile software development methodology that speeds up the development process and increases the flexibility of software delivery. However, the current software requirements change extremely fast, which leads to its increasing uncertainty, and iterative development also faces the challenge of software reliability. The software reliability enhancement method based on iterative development is researched and discussed for the current situation of insufficient reliability in the traditional software development process. In traditional software development, one-time delivery pressure and overall design complexity often lead to software functional defects and instability, affecting software reliability. The iterative development method, on the other hand, improves software reliability by decomposing the software development process into multiple iterative cycles, each of which contains requirements analysis, design, coding, and testing, updating the software functionality in smaller increments, and gradually improving the software product. This study proposes a software reliability improvement methodology by exploring and analyzing the key factors related to reliability in the iterative development process. This dissertation can establish a reliable and high-quality software development process through the steps of meticulous requirements planning and management, iterative development and testing, automated testing and continuous integration, code quality control, defect management and continuous improvement, user feedback and user engagement, and continuous learning and technology enhancement.

An Architectural View Model for Designing and Implementing Microservices-based Systems: Use Case in FinTech

Describing the architecture of microservices systems allows for the illustration of various aspects of design and implementation with information tailored to different stakeholders. On the one hand, the microservices architecture provides flexibility, scalability, faster deployment times, and the potential to design solutions incorporating multiple technologies. An architecture-centered, scenario-driven, iterative development method, on the other hand, is used to explain the system from the perspective of many stakeholders, such as project managers, system architects, developers, and end users. To complement this point of view, this paper proposes an architectural view model that highlights numerous viewpoints and disciplines in microservices-based software development. Such methods are typically well suited for developing and implementing microservices-based software processes to satisfy stakeholders' demands and expectations.

SaaS Service Combinatorial Trustworthiness Measurement Method Based on Markov Theory and Cosine Similarity

With the rapid progress of information technology, cloud computing and cloud services are widely accepted and applied to all aspects of social life. In the cloud computing environment, SaaS (Software-as-a-Service) services have become the main form of software services. For SaaS services, evolutionary and iterative development methods have become the main methods of software system construction. For systems with high trustworthiness, the independent trustworthiness of each SaaS service has a great impact on the overall status. However, SaaS services with high independent trustworthiness do not always build highly trusted software systems. The combinatorial trustworthiness between SaaS services is as important as the independent trustworthiness of each SaaS service. This paper takes combinatorial trustworthiness between SaaS services as the research object. Combinatorial trustworthiness measurement method based on Markov and cosine similarity theory is proposed. The feasibility and effectiveness of the proposed method are verified through simulation experiments. Applicable scenarios, advantages, and disadvantages of the proposed method are shown through the comparison of different measurement methods. The proposed method provides theoretical and technical support for users to select SaaS services suitable for their application scenarios, build cloud service systems, and monitor the operation status of cloud service systems.

How leading companies practice software development and delivery to achieve a competitive edge

Purpose – Increasingly companies recognize that effective and rapid software development – from ideation to delivery – is crucial to achieving competitiveness. This article looks at how leading companies are establishing an enterprise capability for accelerated software delivery to differentiate themselves in the market. Design/methodology/approach – This research looks at how leading software organizations focus on software investments that efficiently and speedily deliver marketplace results. Findings – Successful companies build comprehensive skills in Agile and lean software development methods and for fostering extensive collaboration among business users, IT professionals and customers throughout the software development and delivery lifecycle. Practical implications – Advanced organizations are more likely to apply more mature development practices, such as service-oriented architecture (SOA) and Agile iterative development methods. Originality/value – Advanced organizations collaborate much more with customers and business partners to improve software development outcomes.

Development of a Transcatheter Tricuspid Valve Prosthesis Through Steps of Iterative Optimization and Finite Element Analysis.

The development of a transcatheter tricuspid valve prosthesis for the treatment of tricuspid regurgitation (TR) is presented. The design process involves an iterative development method based on computed tomography data and different steps of finite element analysis (FEA). The enhanced design consists of two self-expandable stents, one is placed inside the superior vena cava (SVC) for primary device anchoring, the second lies inside the tricuspid valve annulus (TVA). Both stents are connected by flexible connecting struts (CS) to anchor the TVA-stent in the orthotopic position. The iterative development method includes the expansion and crimping of the stents and CS with FEA. Leaflet performance and leaflet-stent interaction were studied by applying the physiologic pressure cycle of the right heart onto the leaflet surfaces. A previously implemented nitinol material model and a new porcine pericardium material model derived from uniaxial tensile tests were used. Maximum strains/stresses were approx. 6.8% for the nitinol parts and 2.9 MPa for the leaflets. Stent displacement because of leaflet movement was ≤1.8 mm at the commissures and the coaptation height was 1.6-3 mm. This led to an overall good performance of the prosthesis. An anatomic study showed a good anatomic fit of the device inside the human right heart.

Study on Risk-Driven Iterative Development Method of Geophysical Information Management System Based on RUP

It is the function of Geophysical Information Management System to manage these data and provide database for the project decision-making. This paper uses Unified Modeling Language to describe and construct the system model by means of iterative and incremental development method under the guidance of mature Rational Unified Process. The analysis and design of Geophysical Information Management System can not only reduce the risk of failure, but also meet all the users’ requirements.

Research on the Developmental Situation to Software Development Method

Developmental situation of the software development method in the past was studied. In the past developmental form main contain these: from only considering programming to fully considering total developing process; from the linear development method to iterative development method; from rough qualitative analysis to tight and precise quantitative analysis; from developmental mode of lower efficiency to developmental mode of high efficiency; from the developmental process of walking the chalk to flexible developmental process. Some regularity in the development of software development method are pointed out: new way of thinking can propel the development of software development methods; the change of condition of the goal software can propel the development of software development methods; new developmental tools can propel the development of software development methods; new developmental field can propel the development of software development methods. The efficient path to propel the development of software development method is presented: the development of software development methods is propelled by inheritance the past knowledge of software development, the development of software development methods is propelled by learning and absorbing knowledge of other domain, the development of software development methods is propelled by innovating.

Assessing the state of software in a large enterprise

To be relevant to the goals of an enterprise, an industrial software engineering research organization must identify problems of interest to, and find solutions that have an impact on, the software development organizations within the company. Using a systematic measurement program both to identify the problems and assess the impact of solutions is key to satisfying this need. Avaya has had such a program in place for about seven years. Every year we produce an annual report known as the State of Software in Avaya that describes software development trends throughout the company and that contains prioritized recommendations for improving Avaya's software development capabilities. We start by identifying the goals of the enterprise and use the goal-question-metric approach to identify the measures to compute. The result is insight into the enterprise's problems in software development, recommendations for improving the development process, and problems that require research to solve. We will illustrate the process with examples from the Software Technology Research Department in Avaya Labs whose purpose is to improve the state of software development and know it. "Know it" means that improvement should be subjectively evident and objectively quantifiable. "Know it" also means that one must be skilled at identifying the data sources, performing the appropriate analyses to answer the questions of interest, and validating that the data are accurate and appropriate for the purpose. Examples will include how and why we developed a measure of software quality that appeals to customers, how and why we are studying the effectiveness of distributed software development, and how and why we are helping development organizations to adopt iterative development methods. We will also discuss how we keep the company and the department apprised of the current strengths and weaknesses of software development in Avaya through the publication of the annual State of Software in Avaya Report. Our purpose is both to provide a model for assessment that others may emulate, based on seven years of experience, and to spotlight analyses and conclusions that we feel are common to software development today.

Measuring ERP success: The key-users’ viewpoint of the ERP to produce a viable IS in the organization

Enterprise resource planning (ERP) systems are becoming mature technologies to support inter- and intra-company business processes even in small and medium enterprises. However, ERP systems are complex and expensive, and the decision to install an ERP system necessitates a choice of mechanisms for determining whether the ERP is needed, and once implemented, whether it is successful. User satisfaction is one evaluation mechanism for determining system success. This study looked at key-user satisfaction as a means of determining system success. Initial analyses of ERP system characteristics important for the environment were explored, and some previously validated user satisfaction instruments were selected for examination, using rigorous and systematic interview techniques and iterative development methods. A questionnaire was developed and then tested to prove its reliability and validity. Finally, a relationship was shown to exist between key-user satisfaction and perceived system success.

Heuristics for iterative software development

The author discusses the foundation principles of iterative software development. He goes on to examine a set of heuristics that he has found useful when applying iterative development methods to define the contents of subsequent increments. Understanding the heuristics helps provide vision and focus, which is essential when building complex systems. All the examples share the same domain, that of an advanced air traffic control (ATC) system, admittedly simplified to illustrate the points for an audience that might not be familiar with the ATC domain. The choice is not accidental. Designers successfully used incremental development, and the heuristics described, to build the Canadian Automated Air Traffic System, probably the most advanced system of its kind.

Iterative development of information systems: A case study

AbstractThis paper makes some observations about the applicability of iterative development for system implementation. After a general discussion of the software process, the types of projects suitable for this approach are identified. A system designed to support the iterative development method is then briefly examined, and a case study of its use is presented. Conclusions about the process are drawn, and some research issues regarding productivity are defined.