Spiral Model Of Software Development Research Articles

ОСОБЛИВОСТІ ЗАСТОСУВАННЯ СПІРАЛЬНОЇ МОДЕЛІ ДЛЯ ВИПРОБУВАНЬ ПРОГРАМНОГО ЗАБЕЗПЕЧЕННЯ ЗАСОБІВ ВИМІРЮВАЛЬНОЇ ТЕХНІКИ

The article presents a comparative analysis of different methods of designing, testing and testing of software for various purposes. For a more detailed analysis of the application for software design, a spiral model was selected and its advantages and disadvantages were analyzed. Although the spiral model has a complicated structure to compare it with other models, its use is appropriate for the development of software for measuring instruments (MI), which can be attributed to middle- and high-risk software. Proper use of the spiral model contributes to the avoidance of deliberate damage to the software, that is increases the level of software protection. The modified spiral model of software development that can be applied to software development of MI is presented. It is established that only the stages of conceptual definition of the software development project, conceptual prototype of the software and definition of general requirements for the software, as well as the stages of set for testing, module design, coding, module testing, acceptance and passing tests have their specific features for the MI software. When developing software for measuring instruments, you must take into account the testing features of the software modules, memory, storage devices and data transfer devices. The stage of the spiral model related to the software test is detailed, taking into account all the specific components of the software test, both built in MI and installed on universal computers. The necessity to set the level of division of software into legislatively significant and other parts is taken into account. For the testing tasks of the MI software, the sequence of verification of the software components is defined, such as the verification of the readability of the MI software, the verification of storage devices and the verification of data transfer devices, taking into account the requirements of documents and recommendations of international and regional metrology organizations. It has been established that acceptance tests of the MI software cannot be completed without eliminating the discrepancies found by the developer.

A Social Media mHealth Solution to Address the Needs of Dengue Prevention and Management in Sri Lanka.

BackgroundSri Lanka has witnessed a series of dengue epidemics over the past five years, with the western province, home to the political capital of Colombo, bearing more than half of the dengue burden. Existing dengue monitoring prevention programs are exhausted as public health inspectors (PHIs) cope with increasing workloads and paper-based modes of surveillance and education, characterizing a reactive system unable to cope with the enormity of the problem. On the other hand, the unprecedented proliferation and affordability of mobile phones since 2009 and a supportive political climate have thus far remained unexploited for the use of mobile-based interventions for dengue management.ObjectiveTo conduct a needs assessment of PHIs in Colombo with respect to their dengue-related tasks and develop a new mobile-based system to address these needs while strengthening existing systems.MethodsOne-on-one in-depth interviews were conducted with 29 PHIs to a) gain a nuanced, in-depth understanding of the current state of surveillance practices, b) understand the logistical, technological and social challenges they confront, and c) identify opportunities for mobile-based interventions. Quantitative analysis included simple descriptive statistics while qualitative analysis comprised textual analysis of 209 pages of transcripts (or nearly 600 minutes of conversations) using grounded theory approaches.ResultsCurrent paper-based data collection practices for dengue surveillance involved a circuitous, time consuming process that could take between 7-10 days to officially report and record a single case. PHIs confronted challenges in terms of unreliable, standalone GIS devices, delays in registering mosquito breeding sites and lack of engagement from communities while delivering dengue education. These findings, in concert with a high motivation to use mobile-based systems, informed the development of Mo-Buzz, a mobile-based system that integrates three components – digitized surveillance, dynamic disease mapping and digitized dengue education – on a common platform. The system was developed through an iterative, evolutionary, collaborative process, consistent with the Spiral model of software development and is currently being used by all 55 PHIs in the CMC system.ConclusionsGiven the entrenched nature of existing paper-based systems in PHIs’ work habits, we expect a gradual adoption curve for Mo-Buzz in the future. Equally, we expect variable adoption of the system with respect to its specific components, and specific PHI sub-groups (younger versus older). The Mo-Buzz intervention is a response to multiple calls by the global mHealth community for collaborations in the area of mobile interventions for global health. Our experience revealed that the benefits of this paradigm lies in alleviating country-specific public health challenges through a commonly shared understanding of cultural mores, and sharing of knowledge and technologies. We call upon future researchers to further dissect the applicability of the Spiral Model of software development to mHealth interventions and contribute to the mHealth evidence debate from theoretical and applied perspectives.

Implementing partnership-driven clinical federated electronic health record data sharing networks

ObjectiveBuilding federated data sharing architectures requires supporting a range of data owners, effective and validated semantic alignment between data resources, and consistent focus on end-users. Establishing these resources requires development methodologies that support internal validation of data extraction and translation processes, sustaining meaningful partnerships, and delivering clear and measurable system utility. We describe findings from two federated data sharing case examples that detail critical factors, shared outcomes, and production environment results. MethodsTwo federated data sharing pilot architectures developed to support network-based research associated with the University of Washington’s Institute of Translational Health Sciences provided the basis for the findings. A spiral model for implementation and evaluation was used to structure iterations of development and support knowledge share between the two network development teams, which cross collaborated to support and manage common stages. ResultsWe found that using a spiral model of software development and multiple cycles of iteration was effective in achieving early network design goals. Both networks required time and resource intensive efforts to establish a trusted environment to create the data sharing architectures. Both networks were challenged by the need for adaptive use cases to define and test utility. ConclusionAn iterative cyclical model of development provided a process for developing trust with data partners and refining the design, and supported measureable success in the development of new federated data sharing architectures.

MODELI: An Emotion-Based Software Engineering Methodology for the Development of Digital Learning Objects for the Preservation of the Mixtec Language

In this paper, a methodology termed MODELI (methodology for the design of educational digital objects for indigenous languages) is presented for the development of digital learning objects (DLOs) for the Mixtec language, which is an indigenous Mexican language. MODELI is based on the spiral model of software development and integrates three important aspects for the analysis and design of DLOs: pedagogical, affective-emotional and technological-functional. The premise of MODELI is that the emotional aspect with the inclusion of cultural factors has an important effect on the learning motivation of indigenous users when interacting with the DLO. Principles of the visual, auditory (or aural), read/write, kinesthetic (VARK) model and Kansei engineering were considered for the inclusion of the pedagogical, emotional and technological-functional aspects within the spiral model for the development of MODELI. The methodology was validated with the development of a DLO for a previously unknown variant of the Mixtec language. Usability tests of the DLO built with MODELI evidenced an improvement on the learning motivation and the value of cultural identity of indigenous children. These results are important for the preservation of indigenous languages in Mexico, because most of them are partially documented, and there is social rejection of indigenous culture caused by discrimination of ethnic communities.

Reflections on Barry W. Boehm's “A spiral model of software development and enhancement”

PurposeThe purpose of this paper is to review the content, contributions and subsequent developments of the seminal paper by Barry Boehm, “A spiral model of software development and enhancement” written in 1988. The relationships of this paper to software development, agile projects, real options and present practice are put into perspective.Design/methodology/approachBasically an essayist approach is taken. First, the contents of Boehm's paper are reviewed and then associated with subsequent developments.FindingsReview of the paper as published represents a documentation of cutting‐edge software development as it existed at the time. Fundamentally it suggests the viability of a non‐linear, customer‐influenced, development approach.Practical implicationsThis basic approach illustrated in the spiral model of course has found its way into complex project approaches and management.Originality/valueThis paper follows the lines of increasing attention to classics, which is the purpose of this special issue of the journal. In particular, attention is called to the transition of thought on projects and project management from supplier‐oriented, linear processes to customer/client‐influenced, non‐linear ones.

NASA's TReK project: a case study in using the spiral model of software development

NASA's TReK project: a case study in using the spiral model of software development

Applying the spiral model: A case study in small project management

The need for new development processes becomes apparent as the complexity and cost of developing software systems increase. Many processes have evolved that attempt to improve upon the weaknesses of the traditional waterfall model. One such process is Barry Boehm's spiral model of software development. This risk-driven process uses prototyping and customer evaluation to address problems associated with defining system requirements and incorporating improved design alternatives. This paper describes an application of the spiral model used by a team of software engineering graduate students at Texas Christian University (TCU). The team used this process as part of a two semester software engineering course in which a communications simulator was built. As previous discussions of spiral model implementations have focused on large projects, this discussion will focus on applying the model in a small project setting and will offer refinements to the model at large. This paper discusses methods for handling product specifications and milestones in the spiral model and discusses why and how the model was used. Difficulties with applying the spiral model are presented along with conclusions drawn from the experience. © 1996 by John Wiley & Sons Ltd and Gauthier-Villars

A spiral model of software development and enhancement

A short description is given of software process models and the issues they address. An outline is given of the process steps involved in the spiral model, an evolving risk-driven approach that provides a framework for guiding the software process, and its application to a software project is shown. A summary is given of the primary advantages and implications involved in using the spiral model and the primary difficulties in using it at its current incomplete level of elaboration. >

A spiral model of software development and enhancement

Publisher Summary This chapter describes a spiral model of software development and enhancement. The spiral model of the software process has been evolving for several years, based on experience with various refinements of the waterfall model as applied to large government software projects. The spiral model can accommodate most previous models as special cases and further provides guidance as to which combination of previous models best fits a given software situation. Development of the TRW Software Productivity System (TRW-SPS) is its most complete application to date. The chapter illustrates the radial dimension that represents the cumulative cost incurred in accomplishing the steps to date and the angular dimension that represents the progress made in completing each cycle of the spiral.