2,320 research outputs found

    Reconciling agility and discipline in COTS selection processes

    Get PDF
    Currently, information systems are mainly built by integrating or customizing commercial off-the-shelf (COTS) components acquired or licensed from the marketplace. The processes necessary to steer a suitable acquisition are different from traditional software development processes. Among them, we are interested in the process of selection of COTS components. COTS selection requires discipline to coordinate the selection team and the set of new activities that are necessary to support a successful selection. The Capability Maturity Model (CMM) contains important guidelines for process improvement, and specifiesPeer ReviewedPostprint (published version

    Coordination in Distributed Agile Software Development: Insights from a COTS-based Case Study

    Get PDF
    This study investigates the practices of a development team that uses an Agile system of working where some team members and stakeholders were distributed geographically and temporally. The focus of the investigation was to study the dependencies and related coordination activities as the team collaborated on their work, which was the installation and customization of a complex Commercial Off-The-Shelf (COTS) software system in this case. We collected data by interviewing eight key team members and observing three team meetings over a 2-month period. We made detailed field notes and used thematic analysis to identify the key globally distributed dependencies in the development process. We identify and discuss the coordination mechanisms and tools that address these dependencies, along with the main coordination challenges. We conclude by discussing some ideas and lessons learned by the participants which we expect to be useful for other teams in a similar context

    Roadblocks to Software Modernization

    Get PDF
    Failed or troubled modernization efforts, such as the multi-million dollar 1997-2000 ROCC/SOCC failure, are a serious acquisition problem for the Air Force. Using both historical data and a survey of current Air Force software acquisition program key staff, this research examined the Air Forces ability to modernize legacy software systems. The search of historical program data, to identify trends or similarities between known failed software modernization efforts, failed to uncover sufficient data for analysis. This lack of project data indicates a knowledge management issue (i.e. lessons learned are not recorded and stored so that they can be accessed by other programs) in the acquisition community. The Phase II survey gathered data on current software programs and addressed the recommendations of the 2000 Defense Science Board (DSB) Study on Software. The goal was to determine first, had the recommendations been implemented, second, did program characteristics effect implementation, and third, did implementing the recommendations lead to program success. The survey results indicate that most of the recommendations of the DSB are not in practice in the acquisition community. They also indicate that support programs are more likely to have implemented the recommendations than are weapons systems

    Software Evolution for Industrial Automation Systems. Literature Overview

    Get PDF

    USING HYBRID SCRUM TO MEET WATERFALL PROCESS DELIVERABLES

    Get PDF
    System Development Life Cycles (SDLCs) for organizations are often based upon traditional software development models such as the waterfall model. These processes are complex, heavy in documentation deliverables, and are rigid and less flexible than other methods being used in modern software development. Consider by contrast, agile methods for software development. In essence, agile methods recommend lightweight documentation and simplified process. The focus shifts to completed software as the "measure of success" for delivery of product in software projects, versus accurate and comprehensive documentation, and the accomplishment of static milestones in a work breakdown structure. This thesis implements, explores, and recommends a hybrid agile approach to Scrum in order to satisfy the rigid, document-laden deliverables of a waterfall-based SDLC process. This hybrid Scrum is a balance of having enough documentation and process - but not too much - to meet SDLC deliverables, while at the same time focusing on timely product delivery and customer interactions that come from an agile approach to software development.M.S

    A discovery and analysis of influencing factors of pair programming

    Get PDF
    The exploration into the underlying psychosocial links of pair programming. a new and unorthodox programming paradigm in which two programmers share one keyboard and monitor during real-time programming sessions, is undertaken. These complex psychosocial relationships, along with cognitive process exchanges, ultimately mold the programming output as well as determine the level of communication, satisfaction. confidence and compatibility. Laying the framework for this research, a through review of traditional and contemporary paradigms with a special focus on their limitations and a list of current software development problems are presented. Next, a detailed summary of pair programming and related agile software paradigms, such as extreme programming, which lists pair programming as one of its twelve principles, is given. From earlier pair programming studies, a number of programming benefits have been unveiled and these are listed and discussed. However, a lack of formal studies pertaining to the psychosocial aspects of pair programming exists. Given this void, a field survey is administered to a group of professional programmers and a resulting list of influencing factors on pair programming emerges. From the list, the most popular factor, personality, and two other factors, communication and gender, have been selected in order to study their impact on pair programming product outcome and the level of communication, satisfaction, confidence and compatibility. An experiment focusing on these factors is designed and implemented. From the experimental findings, the personality of the two partners in pair programming is found to have a significant impact on the pair programming output. Also, it is discovered that same gender pairs exhibited an unusually high level of communication, satisfaction and compatibility between each other, especially among female-female pairs. A detailed statistical experiment result based on research hypotheses is reported

    Roles and responsibilities for COTS components selection processes

    Get PDF
    Information systems tend nowadays to be designed by integrating or customizing Commercial Off-The-Shelf (COTS) components acquired or licensed from the marketplace. There are currently many methods that contribute to select these components. The application of COTS selection methods result in processes that are different from usual development processes, yielding to new activities and responsibilities that should be covered by interactions of specialized roles. However it may be observed that these methods do not put emphasis neither on the identification of these roles, nor on their subsequent interactions, nor on their combination to form a selection team. The contribution of this work is based on identifying and defining the roles that take place in COTS selection processes, their interactions and their responsibilities. We use a goal-oriented approach, the i* notation, and a framework to model the engineering process, the OPEN Process Framework (OPF), with the purpose of issuing a well-defined work team that can adapt itself to the internal processes of a particular organization. We apply our generic proposal to a particular case, a COTS-based development life-cycle based on the agile principles and individuals interactions as defined in eXtreme Programming (XP).Postprint (published version

    Software Engineering Laboratory Series: Proceedings of the Twenty-Second Annual Software Engineering Workshop

    Get PDF
    The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of application software. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that includes this document

    SSV Launch Monitoring Strategies: HGDS Design Implementation Through System Maturity

    Get PDF
    With over 500,000 gallons of liquid hydrogen and liquid oxygen, it is of vital importance to monitor the space shuttle vehicle (SSV) from external tank (ET) load through launch. The Hazardous Gas Detection System (HGDS) was installed as the primary system responsible for monitoring fuel leaks within the orbiter and ET. The HGDS was designed to obtain the lowest possible detection limits with the best resolution while monitoring the SSV for any hydrogen, helium, oxygen, or argon as the main requirement. The HGDS is a redundant mass spectrometer used for real-time monitoring during Power Reactant Storage and Distribution (PRSD) load and ET load through launch or scrub. This system also performs SSV processing leak checks of the Tail Service Mast (TSM) umbilical quick disconnects (QD's), Ground Umbilical Carrier Plate (GUCP) QD's and supports auxiliary power unit (APU) system tests. From design to initial implementation and operations, the HGDS has evolved into a mature and reliable launch support system. This paper will discuss the operational challenges and lessons learned from facing design deficiencies, validation and maintenance efforts, life cycle issues, and evolving requirement

    Reef research volume 04: no 4

    Get PDF
    • …
    corecore