Search

Software Engineering is a branch of Computer Science that evolved as a result of urgent need to deal with decades of software crisis, characterized by low theoretical knowledge and practice of the construction of error-free and efficient software. The introduction of well-organized scientific, engineering and management strategies in the process of software development no doubt led to major breakthroughs, and solutions to software failures. One of the obvious game-changer in this regard is the evolution of Software Development Life Cycle, also known as Software Process Model for driving the different phases of software construction. A sound understanding of the process model is therefore inevitable, not just for software developers, but also to users and researchers. Such a theoretical cum practical understanding will enhance decisions on which process model is best for a particular job or perspective. This invariably, contributes immensely to the probability of success or failure of the project in question. Thus, the necessity for this research. This work presents an unambiguous expository of selected software development model variants. A total of four process model variants were studied, in a theoretical, visual and analytical manner. The variants were analyzed using strength versus weakness (SVW) tabular scenario. This work was concluded by presenting guides towards choice of these models. This research is expected to be a useful reference to software practitioners and researchers.

This paper presents a new method of engaging older participants in the process of application and IT solutions development for older adults for emerging IT and tech startups. A new method called SPIRAL (Support for Participant Involvement in Rapid and Agile software development Labs) is proposed which adds both sustainability and flexibility to the development process with older adults. This method is based on the participatory approach and user empowerment of older adults with the aid of a bootstrapped Living Lab concept and it goes beyond well established user-centered and empathic design. SPIRAL provides strategies for direct involvement of older participants in the software development processes from the very early stage to support the agile approach with rapid prototyping, in particular in new and emerging startup environments with limited capabilities, including time, team and resources.

The purpose of this writing is to design and to develop an application that is able to present data in Sumbawa Language (Basa Samawa) Dictionary which is still in book outline into digital form. Spiral method is used in this research for software development process and its data collection method applies literature study with data source from "Dictionary of Sumbawa-Indonesia" by Department of Education National Language Center Office Province of West Nusa Tenggara, moreover its test method pertains black box method that is a software experiment in terms of its functionality. The results of research that has been built with Android Studio 1.5 and SQLite database with target android version 6.0 (Marshmallow) has been accessible through Play Store, in which this application has been equipped with vocabulary search including sentence examples, introduction to dictionary usage, dictionary procedure information and application to contribute to the indigenous communities of Sumbawa as well as exterior societies of Sumbawa in studying Sumbawa language and preserving the Sumbawa cultural heritage.

Successful engineering and evaluation of complex software depends on successfully completing all the stages of the Software Development Life Cycle. There have been many models which illustrate the stages Software Engineers have to go through to produce software. This paper investigates one of these—The Spiral Model (Sommerville 1997) with particular reference to recent enhancements to it, examines the interaction of COCOMO II (19xx) within the WinWin framework, and reports on a case study using the WinWin Spiral Model (Boehm et al. 1998) to develop software.

International audience; The main development models from Software Engineering are too general and largely insufficient in term of interactive systems development. One solution to this problem is the proposal to use so-called HCI-enriched models. Such a model, called  (pronounced "nabla"), is presented in this paper. During a questionnaire-based evaluation, this model has been compared with four classical models (Waterfall, V, Spiral and Incremental models) and five other HCI-enriched models. The first results of this evaluation, led with 43 subjects are discussed in the paper.

As for Gamification, it is about business software with game characteristics, understanding the software development process will improve the practices, and will more than likely, improve the business itself (make it more efficient, effective, and less costly and mainly collect a positive influence from the customers). This study aims to develop a framework that provides the mechanisms to ensure that the software will have game characteristic and that clients will recognize it as Gamification. Our results show that the five-step framework proposal applied to the Gamification project management on this study, the Spiral development model, and the group discussion results into a positive effect on customers and e-business. The spiral development methodology used for the development of this application showed to be the appropriated for this type of project. The tests with discussion-groups proved to be a key "tool" to identify and adapt the game characteristics that has led to the improvement of customer perception of socialness, usefulness ease of use, enjoyment and ease of use that probed to have a strong positive impact on the intention to use the game.

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

The software part of embedded real-time systems is constantly increasing in size and complexity. Therefore, for a company to stay competitive in a strong market, techniques for management of such risks as misunderstanding of customer needs, schedule or budget overrun, quality pitfalls, or in the worst case cancelled projects, are required. The spiral model guides a developer to postpone detailed elaboration of low-risk software elements until the essential high-risk elements of the design are stabilised. The spiral model incorporates prototyping as a risk reduction option at any stage of development. This means supporting executable system models where different parts are represented at different levels of abstractions called (distributed) heterogeneous prototypes. Source code is integrated into the system models through a run-time adaptation technology which is explained in this paper.

This chapter contains sections titled: Prototyping Versus Specifying: A Multiproject Experiment A Spiral Model of Software Development and Enhancement Anchoring the Software Process

Conventional software development such as structured programming based on the waterfall model has been used for the telecommunication field; however, the conventional process has had some problems. Various new techniques have been practically introduced into other fields such as computer software development. We have discussed the object oriented approach based on spiral modeling and its application to telecommunication software development. Spiral modeling is a type of prototyping.

A primary difficulty in applying the spiral model has been the lack of explicit process guidance in determining the prospective system's objectives, constraints, and alternatives that get elaborated in each cycle. This paper presents an extension of the spiral model, called the Next Generation Process Model (NGPM), which uses the Theory W(win-win) approach (Boehm-Ross, 1989) to converge on a system's next-level objectives, constraints, and alternatives. The refined Spiral Model explicitly addresses the need for concurrent analysis, risk resolution definition, and elaboration of both the software product and the software process in a collaborative manner. This paper also describes some of the key elements of the support system developed based on the model and refined through experiments with it. It reports on experiences in applying NGPM to a large Department of Defense program. >

Rather than having software tool assessment and selection be performed separately from the software development process, Boehm's (1988) spiral model of software development can be used to provide a framework within which tool assessment and selection can be systematically integrated into the software development process. The result is an incremental decision making/integration process which results in conservative (minimal, best-for-now) decisions which come under review each cycle through the spiral. This paper first describes the decision making/integration process. It then shows how the decision making/integration process has been used in the VETRONICS Simulation Facility project. The first three cycles through the spiral are described for the selection of a CASE tool, a prototyping tool, and an interprocess communication (IPC) tool. >

IDERS is a new generation environment for developing real time critical systems. It integrates specification, design and code within a single framework, provides support for incremental prototyping and allows early validation through testing and animation. The system is based on a kernel that eliminates ambiguities and supplies dynamic semantic checks. Customization facilities allow one to tailor the environment to specific notations, preserving the benefits of the formal kernel. The software process is modeled by a process centered software engineering environment that guarantees the complete visibility of both the development process and the evolving products. The IDERS project supplies a specific process model inspired by B. Boehm's spiral life cycle model (1988).

Spiral development is a family of software development processes characterized by repeatedly iterating a set of elemental development processes and managing risk so it is actively being reduced. This paper characterizes spiral development by enumerating a few "invariant" properties that any such process must exhibit. For each, a set of "variants" is also presented, demonstrating a range of process definitions in the spiral development family. Each invariant excludes one or more "hazardous spiral look-alike" models, which are also outlined. This report also shows how the spiral model can be used for a more cost-effective incremental commitment of funds, via an analogy of the spiral model to stud poker. An important and relatively recent innovation to the spiral model has been the introduction of anchor point milestones. The latter part of the paper describes and discusses these.

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.

Barry B. Boehm suggested an interesting spiral model for the software development process in the International Workshop on the Software Process and Software Environments last Year (Boe86). The model is particularly interesting to me, since it seems to be highly consistent with some of the basic ideas of the PIOCO model for the information systems (IS) design process (Iiv82, Iiv83a, IiKo86) and also with its application to the development of embedded software (IiKT86). For instance, he characterizes the spiral model as a risk-driven approach. In the PIOCO model we have chosen to use the term uncertainty instead of risk emphasiznig that the IS/SW process, particularly in its earlier phases, is information production for the steering committee deciding about the IS/SW product and process (Iiv83a, Iiv86). In Iiv83a and b we have also formalized this idea in terms of Information Economics (Mar74) leading to the conclusion that IS/SW elaboration should be directed to those aspects of the IS/SW process in which the uncertainty, and therefore the potential value of the new information, is greatest (cf. Boe86).