A hierarchy of SPI activities for software SMEs: results from ISO/IEC 12207-based SPI assessments

In an assessment of software process improvement (SPI) in 15 software small- and –medium-sized enterprises (software SMEs), we applied the broad spectrum of software specific and system context processes in ISO/IEC 12207 to the task of examining SPI in practice. Using the data collected in the study, we developed a four-tiered pyramidal hierarchy of SPI for software SMEs, with processes in the higher tiers undergoing SPI in more companies than processes on lower level tiers. The development of the hierarchy of SPI activities for software SMEs can facilitate future evolutions of process maturity reference frameworks, such as ISO/IEC 15504, in better supporting software development in software SMEs. Furthermore, the findings extend our body of knowledge concerning the practice of SPI in software SMEs, a large and vital sector of the software development community that has largely avoided the implementation of established process maturity and software quality management standards

Modeling the object-oriented software process: OPEN and the unified process

A short introduction to software process modeling is presented, particularly object-oriented modeling. Two major industrial process models are discussed: the OPEN model and the Unified Process model. In more detail, the quality assurance in the Unified Process tool (formally called Objectory) is reviewed

The Impact of Regulatory Changes on the Development of Mobile Medical Apps

Mobile applications are being used to perform a wide variety of tasks in day-to-day life ranging from checking email, to controlling your home heating. Application developers have recognized the potential to transform a smart device into a medical device, by using a mobile medical application i.e. a mobile phone or a tablet. When initially conceived these mobile medical applications performed basic functions e.g. BMI calculator, accessing reference material etc.; however, increasing complexity offers clinicians and patients a range of functionality. As this complexity and functionality increases, so too does the potential risk associated with using such an application. Examples include any applications that provide the ability to inflate and deflate blood pressure cuffs, as well as applications that use patient-specific parameters and calculate dosage or create a dosage, plan for radiation therapy. If an unapproved mobile medical application is marketed by a medical device organization, then they face significant penalties such as receiving an FDA warning letter to cease the prohibited activity, fines and possibly face criminal conviction. Regulatory bodies have finalized guidance intended for mobile application developers to establish if their applications are subject to regulatory scrutiny. However, regulatory controls appear contradictory with the approaches taken by mobile application developers who generally work with short development cycles and very little documentation and as such, there is the potential to stifle further improvements due to these regulations. The research presented as part of this paper details how by adopting development techniques such as agile software development, mobile medical application developers can meet regulatory requirements whilst still fostering innovation

A conceptual descriptive-comparative study of models and standards of processes in SE, SwE, and IT disciplines using the theory of systems

e increasing design, manufacturing, and provision complexity of high-quality, cost-efficient and trustworthy products and services has demanded the exchange of best organizational practices in worldwide organizations. While that such a realization has been available to organizations via models and standards of processes, the myriad of them and their heavy conceptual density has obscured their comprehension and practitioners are confused in their correct organizational selection, evaluation, and deployment tasks. Thus, with the ultimate aim to improve the task understanding of such schemes by reducing its business process understanding complexity, in this article we use a conceptual systemic odel of a generic business organization derived from the theory of systems to describe and compare two main models (CMMI/SE/SwE, 2002; ITIL V.3, 2007) and four main standards (ISO/IEC 15288, 2002; ISO/IEC 12207, 1995; ISO/IEC 15504, 2005; ISO/IEC 20000, 2006) of processes. Description and comparison are realized through a mapping of them onto the systemic model

A lightweight assessment method for medical device software processes

This paper outlines the MDevSPICE-Adept process assessment method. MDevSPICE-Adept is a lightweight process assessment method that has been created for the MDevSPICE software process assessment model which is currently being developed for the medical device industry. MDevSPICE is a fully validated release of a medical device software process assessment model (formerly known as Medi SPICE), which was developed by the authors. While the MDevSPICE process assessment model is detailed and comprehensive, there is industry demand for a lightweight medical device software process assessment method. To address this requirement the MDevSPICE-Adept method has been developed. Details on how this has taken place and the procedures for implementing an MDevSPICE-Adept process assessment are presented. Information is also provided regarding how an MDevSPICE process assessment was undertaken in an Irish based medical device company. A summary of the issues identified from this process assessment and the actions taken to facilitate process improvement is also presented. Finally, plans for future work are discussed

Standardization of information systems development processes and banking industry adaptations

This paper examines the current system development processes of three major Turkish banks in terms of compliance to internationally accepted system development and software engineering standards to determine the common process problems of banks. After an in-depth investigation into system development and software engineering standards, related process-based standards were selected. Questions were then prepared covering the whole system development process by applying the classical Waterfall life cycle model. Each question is made up of guidance and suggestions from the international system development standards. To collect data, people from the information technology departments of three major banks in Turkey were interviewed. Results have been aggregated by examining the current process status of the three banks together. Problematic issues were identified using the international system development standards.Comment: 12 pages; International Journal of Software Engineering & Applications (IJSEA), Vol.2, No.2, April 201