Function point analysis (FPA) is a standardized method to systematically measure the functional size of software. This method is proposed by an international organization and it is currently recommended by governments and organizations as a standard method to be adopted for this type of measurement. This paper presents a compilation of improvements, focused on increasing the accuracy of the FPA method, which have been proposed over the past 13 years. The methodology used was a systematic literature review (SLR), which was conducted with four research questions aligned with the objectives of this study. As a result of the SLR, of the 1600 results returned by the search engines, 454 primary studies were preselected according to the criteria established for the SLR. Among these studies, only 18 specifically referred to accuracy improvements for FPA, which was the goal of this study. The low number of studies that propose FPA improvements might demonstrate the maturity of the method in the current scenario of software metrics. Specifically in terms of found issues, it was found that the step for calculating the functional size exhibited the highest number of problems, indicating the need to revise FPA in order to encompass the possible improvements suggested by the researchers.
Governments around the globe are paving the way for healthcare services that can have a profound impact on the overall well-being and development of their nations. However, government programs to implement health information technologies on a large-scale are challenging, especially in developing countries. In this article, the process and outcomes of the large-scale implementation of a hospital information system for the management of Brazilian university hospitals are analyzed. Based on a qualitative approach, this research involved 21 hospitals and comprised a documentary search, interviews with 24 hospital managers and two system user focus groups, and a questionnaire of 736 respondents. Generally, we observed that aspects relating to the wider context of system implementation (macro level), the managerial structure, cultural nuances, and political dynamics within each hospital (meso level), as well as the technology, work activities, and individuals themselves (micro level) acted as facilitators and/or obstacles to the implementation process. The dynamics and complex interactions established between these aspects had repercussions on the process, including the extended time necessary to implement the national program and the somewhat mixed outcomes obtained by hospitals in the national network. Mostly positive, these outcomes were linked to the eight emerging dimensions of practices and work processes; planning, control, and decision making; transparency and accountability; optimization in the use of resources; productivity of professionals; patient information security; safety and quality of care; and improvement in teaching and research. We argued here that to maximize the potential of information technology in healthcare on a large-scale, an integrative and cooperative vision is required, along with a high capacity for change management, considering the different regional, local, and institutional contexts.
3 April 2017 in Business Process Management Journal
Purpose: The purpose of this paper is to present business process point analysis (BPPA), a technique to measure business functional process size, based on function point analysis (FPA), and using business process model and notation (BPMN). This paper also discusses the assessment results of BPPA compared with FPA. Design/methodology/approach: Two experimental studies with participants from academia and industry were conducted. The following aspects in the experimental studies were focused: similarity, application easiness, feasibility, and application benefits. The purpose of the experiment was to assess BPPA comparing with FPA as the BPPA design followed the FPA pattern. Findings: Experimental results showed that both academia and industry groups highly rated similarity and application benefits for BPPA compared with FPA. However, only participants from industry highly rated BPPA for application easiness and feasibility. The results also showed that participants’ previous experiences did not influence their ratings on BPPA. Originality/value: BPPA helps project managers to measure functional process size of business process management projects. As BPPA is derived from FPA, its mechanism is easily recognizable by project managers who are used to FPA. These results also show that both techniques are in most cases considered rather similar.
Currently, organizations that are seeking to achieve a strategic alignment between business areas and Information Technology (IT) have been increasingly using Business Process Management (BPM) and Service-oriented Architecture (SOA). BPM and SOA, when used together, can help to achieve this goal. In this context, a Service Level Agreement (SLA) is commonly used to define and monitor the establishment of the relationship between business and IT, including the technical level of this relationship. However, a previous agreement, in a higher and wider level of this relationship, is necessary so that this desired strategic alignment can be achieved in the way that was expected, and this can take the form of a Business Level Agreement (BLA). This paper proposes the integrated use of BLAs and SLAs, together with a business processes modelling language (in this case, BPMN -- Business Process Modeling and Notation) and a business process execution languages (in this case, WS-BPEL -- Web Services Business Process Execution Language), in a search for a strategic alignment. An overall description of the proposed approach is presented, including a simple illustrative example, in order to foster the conduction of more research works in this area.