A strategy for PACS development using introductory team software process

A. Martinez-Martinez; M. A. Nunyez-Gaona; J. R. Jimenez-Alaniz; J. E. Munyoz de Cote; N. Chavez-Avelar; R. E. Delgado-Esquerra; J. Gutierrez-Martinez

doi:10.1117/12.596088

15 April 2005 A strategy for PACS development using introductory team software process

A. Martinez-Martinez, M. A. Nunyez-Gaona, J. R. Jimenez-Alaniz, J. E. Munyoz de Cote, N. Chavez-Avelar, R. E. Delgado-Esquerra, J. Gutierrez-Martinez

Author Affiliations +

Proceedings Volume 5748, Medical Imaging 2005: PACS and Imaging Informatics; (2005) https://doi.org/10.1117/12.596088
Event: Medical Imaging, 2005, San Diego, California, United States

Abstract

A PACS development requires to fill the needs of a specific imagenology area in a hospital and, as consequence, the amount of requirements associated to a PACS implicate a great complexity. This can be observed through methods that allow the size and complexity of a PACS software system to be quantified and measured, by analyzing the user requirements and interactions with other systems to be realized. When a PACS development is proposed, it can be difficult to actually launch the development project since a lot of time may be invested in defining the initial activities to be performed. In this work a model to address the complexity of a PACS development is proposed, and a strategy to divide the different tasks involved is defined. The model can offer an estimation about the effort to be spent. To face the problem, a correct planning and schedule can be defined. The model was obtained applying the first steps of the introductory Team Software Process (TSPi) methodology, and was represented using Unified Modelling Language activity diagrams. The model shows the different activities that have to be realized during the PACS development, and also the products that are generated once activities are accomplished. Another main aspect is a dependence view which shows the synchronization and dependence between tasks. This allows the possible sequences of activities to be visualized, and to be planned across different cycles. According to the TSPi, in each planned cycle a testable version of a PACS specific application should to be produced and the combination of the products, obtained through the different cycles should produce a final software system. With the model presented in this work, PACS developers can have a clear idea about the involved tasks and can schedule the work to accomplish specific PACS applications. A case study was conducted at the "Centro Nacional de Rehabilitacion" (National Rehabilitation Center)in Mexico City, using the proposed model.

Citation Download Citation

A. Martinez-Martinez, M. A. Nunyez-Gaona, J. R. Jimenez-Alaniz, J. E. Munyoz de Cote, N. Chavez-Avelar, R. E. Delgado-Esquerra, and J. Gutierrez-Martinez "A strategy for PACS development using introductory team software process", Proc. SPIE 5748, Medical Imaging 2005: PACS and Imaging Informatics, (15 April 2005); https://doi.org/10.1117/12.596088

ACCESS THE FULL ARTICLE

INSTITUTIONAL
Select your institution to access the SPIE Digital Library.

SELECT YOUR INSTITUTION

PERSONAL
Sign in with your SPIE account to access your personal subscriptions or to use specific features such as save to my library, sign up for alerts, save searches, etc.

PERSONAL SIGN IN

No SPIE Account? Create one

PURCHASE THIS CONTENT

SUBSCRIBE TO DIGITAL LIBRARY

50 downloads per 1-year subscription

Members: $195

Non-members: $335 ADD TO CART

25 downloads per 1 - year subscription

Members: $145

Non-members: $250 ADD TO CART

PURCHASE SINGLE ARTICLE

Includes PDF, HTML & Video, when available