The Impact of Software Process Maturity and Software Development Risk on the Performance of Software Development Projects

Despite the increasing efforts of organizations to improve the development processes of their software projects, there remain few empirical and generalizable findings when it comes to key questions regarding software process improvement initiatives. Rarely there was any empirical examination in an integrative model on how process improvement efforts affect key organizational concerns such as software project performance and the threat of risks in today’s dynamic and complex business environment. In addressing this knowledge gap, we propose and test a research model that allows for an empirical examination of the relationships between software process maturity and the performance of software development projects while assessing the impact of risk on software project performance. Data were collected from officially CMM-appraised organizations to test developed hypotheses using proven metrics identified in the literature. Our findings support our theoretical framework in providing evidence of the positive impact of software development process maturity on the performance of software projects while underscoring the negative effect of risk on software project performance. Key results and a discussion of the findings are also provided

Towards developing a software process improvement strategy through the application of ethical concepts

Aligning Software Process Improvement with the business and strategic goals of an enterprise is a core factor for process improvement. Achieving success in Software Process Improvement (SPI) has shown to be a problematic challenge for countless organisations. SPI, as a discipline, can be described as a set of use cases, each use case describing the logically related activities that must be undertaken. In addition, each use case is a description of the interactions between itself and the participants, i.e. the Actors. The nature of these interactions more often than not may demand, from the participant, the recognition, and fulfilment, of ethical duties. In this paper we customise a theoretical framework developed by the US Content Subcommittee of the Impact CS Steering Committee that specifies traditional moral and ethical concepts, which can be used to identify the moral issues concerning the Software Process Improvement field. An application of these conventional and generic ethical concepts is made to use cases such as: Determining Business Needs; Conducting Process Improvement Assessment; the Tailoring and Creation of Processes; and Deployment. In doing so a number of ethical issues are highlighted. In the application and utilisation of SPI: business process engineers, software engineering teams, process improvement managers, and so on must be aware of these ethical duties, which have been identified by the application of the moral and ethical concepts, as presented in this paper, in order to become more responsible professionals in general. We propose a set of heuristics for ethical engagement with the SPI discipline proposing that an effective SPI strategy must be underpinned with ethical consideration

The proposal of adding a society value to the software process improvement manifesto

The use of computers has become ubiquitous and spread out to every part of our personal lives and businesses. Computer Ethics focuses on the questions of right and wrong that arise from the development and deployment of computers. Thus, it urges that the social impact of computers must be analysed. In software engineering, the Software Process Improvement (SPI) Manifesto was developed by groups of experts in the field and aimed to improve the software produced, by improving the process, the attitudes of software engineers, and the organisational culture and practices. The manifesto is centred on three basic values: people, business focus and organisational change, underpinning the philosophy of software process improvement; and ten corresponding principles, which serve as foundations for action. In this paper, we argue that SPI professionals, need to, in addition to fulfilling duties to the Organisation, the Business, the Employees who participate in SPI, and the People who will be most affected, broaden their obligations to include wider society. The impact of developed and deployed software systems is often beyond the organisation and affects the daily lives and activities of citizens in society. This paper argues for the inclusion, in the SPI Manifesto, of a fourth value titled Society, along with six corresponding principles. These half-dozen principles are based on traditional moral and ethical concepts, sourced from the field of Computer Ethics. This proposed revision to the SPI manifesto would explicitly espouse the notion of serving the public interest. It will likely help SPI professionals to remember that working in the public interest is also important in Software Process Improvement, thus, making the duty to society clear and obvious or evident

Контролінг як інструмент ефективного управління підприємством

У статті визначена необхідність здійснення постійного процесу контролю використання внутрішніх чинників через розробку та послідовну реалізацію власної програми підвищення ефективності діяльності, а також врахування впливу на неї зовнішніх чинників. Підвищення ефективності діяльності суб’єктів господарювання залежить від удосконалення інформаційного забезпечення управлінських функцій на базі використання сучасних програмних продуктів. Дослідження автоматизації управління значно полегшує процес впровадження і підвищує ефективність подальшого використання цієї системиThe article identified the need to implement the continuous process of monitoring internal factors through development and consistent implementation of an own program to improve business efficiency, and taking into account the impact of external factors on it. Improving the efficiency of business entities depends on the improvement of informational support of management functions based on the use of modern software. The study on management automation greatly simplifies the process of implementation and improves the efficiency of the further use of the above-mentioned syste

How to develop financial applications with game features in e-banking?

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.info:eu-repo/semantics/acceptedVersio

Improving the Modifiability of the Architecture of Business Applications

Abstract-In the current rapidly changing business environment, organizations must keep on changing their business applications to maintain their competitive edges. Therefore, the modifiability of a business application is critical to the success of organizations. Software architecture plays an important role in ensuring a desired modifiability of business applications. However, few approaches exist to automatically assess and improve the modifiability of software architectures. Generally speaking, existing approaches rely on software architects to design software architecture based on their experience and knowledge. In this paper, we build on our prior work on automatic generation of software architectures from business processes and propose a collection of model transformation rules to automatically improve the modifiability of software architectures. We extend a set of existing product metrics to assess the modifiability impact of the proposed model transformation rules and guide the quality improvement process. Eventually, we can generate software architecture with desired modifiability from business processes. We conduct a case study to illustrate the effectiveness of our transformation rules

Information Technology: DOD Needs to Strengthen Management of Its Statutorily Mandated Software and System Process Improvement Efforts

A letter report issued by the Government Accountability Office with an abstract that begins "The Department of Defense's (DOD) acquisition of weapon systems and modernization of business systems have both been on GAO's list of high-risk areas since 1995. To assist DOD in managing software-intensive systems, Section 804 of the Bob Stump National Defense Authorization Act for Fiscal Year 2003 required the Office of the Secretary of Defense (OSD) and DOD component organizations, including the military departments, to undertake certain software and systems process improvement (SSPI) actions. As requested, GAO assessed (1) the extent to which DOD has implemented the process improvement provisions of the act, and (2) the impact of DOD's process improvement efforts. To do so, GAO analyzed relevant plans, policies, guidance, performance measures, and reports against statutory requirements and relevant guidance, and interviewed DOD officials.

The Impact of Process Visibility on Process Performance - A Multiple Case Study of Operations Control Centers in ITSM

Successful monitoring is essential for managing security-critical or business-critical processes. The paper seeks to understand and empirically evaluate benefits of the BPM use case “monitor” in the context of Operations Control Centers (OCCs). OCCs create visibility about critical events and statuses in very sensitive processes. In IT Service Management (ITSM) they support the event management process with real-time monitoring and event analysis of critical systems in complex system landscapes. This special focus of OCCs on visibility is a promising context to study fundamentals of process visibility. The paper develops a Process Monitoring Benefits Framework that draws on the Situation Awareness Theory and the Theory of Constraints. The authors conceptualize process visibility and suggest that it is positively related to process performance. A multiple case study in seven organizations is carried out to examine the framework and its propositions. The case study indicates that the impact of process visibility on process performance is mediated by the situation awareness of the process participants as well as the identification of bottlenecks in processes. Moreover, factors are identified that potentially influence process visibility outcome – namely continuous improvement culture, outsourcing quality, and maturity of the software tool used for monitoring

Information technology service management: an experimental approach towards IT service prediction

Dissertation presented to obtain a Masters degree in Computer ScienceSoftware development and software quality improvement have been strong topics for discussion in the last decades. Software Engineering has always been concerned with theories and best practices to develop software for large-scale usage. However, most times those theories are not validated in real live environments. Therefore, the need for experiments is immense. The incidents database can be an important asset for software engineering teams. If they learn from past experience in service management, then they will be able to shift from a reactive approach to a more proactive one. The main goal of this dissertation is shedding some light on the influential factors that affect incidents lifecycle, from creation to its closure, and also to investigate to what accuracy the ARIMA models are a valid approach to model and predict not only the ITIL incident management process, but also other ITIL processes and services in general. The dissertation presented herein is on the crossroads of Empirical Software Engineering and of the emerging area of Services Science. It describes an experiment conducted upon a sample of incident reports, recorded during the operation of several hundred commercial software products, over a period of three years (2005-2007), on six countries in Europe and Latin America. The incidents were reported by customers of a large independent software vendor. The primary goal of an Incident Management process is to restore normal service operation as quickly as possible and minimize the adverse impact on business operations, thus ensuring that the best possible levels of service quality and availability are maintained. As a result of this, a software company can make use of a good incident management process to improve several areas of their business, particularly product development, product support, the relation with its customers and their positioning in the marketplace. The underlying research questions refer to the validation of which are the influencing factors affecting the incidents management lifecycle, and also aims at finding the existence of patterns and/or trends in incident creation and resolution based on a time series approach. Additionally, it presents the estimation, evaluation and validation of several ARIMA models created with the purpose of forecasting upon incident resolution based on incident creation historic data. Understanding causal-relationships and patterns on incident management can help software development organizations on optimizing their support processes and in allocating the adequate resources; people and budget