Most of today's products and services are software-based. Organizations that develop software want to maintain and improve their competitiveness by controlling software-related risks. To do this, they need to align their business goals with software development strategies and translate them into quantitative project management. There is also an increasing need to justify cost and resources for software and system development and other IT services by demonstrating their impact on an organization's higher-level goals. For both, linking business goals and software-related efforts in an organization is necessary. However, this is a challenging task, and there is a lack of methods addressing this gap. The GQM + Strategies ® approach effectively links goals and strategies on all levels of an organization by means of goal-oriented measurement. The approach is based on rationales for deciding about options when operationalizing goals and for evaluating the success of strategies with respect to goals. Keywords Need for Business AlignmentAlong with the growth in society's dependence on software and other forms of information technology (IT), the size and complexity of software systems have also grown. This has only magni-fied the cost, schedule, and quality concerns that have always plagued software development efforts. For decades, software engineering researchers and practitioners have attempted to control and reduce the costs of building software, to produce working software within shorter periods of time, and to increase the quality of the software produced. While great strides have been made in all three areas, the growth of software, along all dimensions (size, complexity, pervasiveness, criticality, etc.), has outpaced our ability to control all the factors related to its development.What has become clear, however, is that the issues related to software cost, schedule, and quality are inextricably linked with larger issues facing the businesses that develop the software. Such businesses come in a variety of flavors. Some are in the business of selling the software they develop to customers, either as custom-built software on contract or shrink-wrapped applications for some segment of the population. Others are in the business of selling some product or service, of which software is a significant component. Still others may only develop software to support their internal IT infrastructure, and do not sell software-related products. Some software organizations are not in business at all, but are non-profit organizations, government entities, or educational institutions. While all these organizational configurations provide quite different challenges to their development projects, the key here is that all software is developed within a larger business context, encompassing larger business goals, strategies, and measures of success.While all businesses employ various strategies to achieve their objectives, these objectives are not always stated explicitly or clearly enough to allow one to check whether or not ...
No abstract
Cost estimation is a very crucial field for software developing companies. The acceptance of an estimation technique is highly dependent on estimation accuracy. Often, this accuracy is only determined after an initial application. Possible further steps for improving the underlying estimation model typically do not influence the decision on whether to discard the technique or deploy it. In addition, most estimation techniques do not explicitly support the evolution of the underlying estimation model in an iterative manner. This increases the risk of overlooking some important cost drivers or data inconsistencies. This paper presents an enhanced process for developing a CoBRA® cost estimation model by systematically including iterative analysis and feedback cycles, and its evaluation in a software development unit of Oki Electric Industry Co., Ltd., Japan. During the model improvement cycles, estimation accuracy was improved from an initial 120% down to 14%. In addition, lessons learned with the iterative development approach are described
Despite overwhelming evidence of the benefits of risk-adjusted oral anticoagulation on stroke reduction in patients with atrial fibrillation (AF), there is still considerable undertreatment. A multidisciplinary expert group was formed to discuss issues surrounding anticoagulant treatment of patients with AF to try and achieve consensus on various aspects of the implementation of guidelines on oral anticoagulation therapy in AF. Panel members were cardiologists, hematologists, and laboratory and primary care physicians with specific expertise from Europe and the United States. One of the most important conclusions of the meeting was to enhance guideline adherence by better communication of the data showing that the benefits of stroke reduction outweigh the risk of bleeding associated with treatment with vitamin K antagonists. Management of oral anticoagulation therapy by dedicated centers, such as anticoagulation clinics, or by patient self-management may improve the quality of anticoagulation and facilitate the management of these patients and thereby further facilitate optimal antithrombotic management in patients with AF.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.
hi@scite.ai
10624 S. Eastern Ave., Ste. A-614
Henderson, NV 89052, USA
Copyright © 2024 scite LLC. All rights reserved.
Made with 💙 for researchers
Part of the Research Solutions Family.