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.
The DICOM standard, as all standards, specifies in generic way the management in network and storage media environments of digital medical images and their related information. However, understanding the specifications for particular implementation is not a trivial work. Thus, this work is about understanding and modelling parts of the DICOM standard using Object Oriented methodologies, as part of software development processes. This has offered different static and dynamic views, according with the standard specifications, and the resultant models have been represented through the Unified Modelling Language (UML). The modelled parts are related to network conformance claim: Network Communication Support for Message Exchange, Message Exchange, Information Object Definitions, Service Class Specifications, Data Structures and Encoding, and Data Dictionary. The resultant models have given a better understanding about DICOM parts and have opened the possibility of create a software library to develop DICOM conformable PACS applications.
Access to the requested content is limited to institutions that have purchased or subscribe to SPIE eBooks.
You are receiving this notice because your organization may not have SPIE eBooks access.*
*Shibboleth/Open Athens users─please
sign in
to access your institution's subscriptions.
To obtain this item, you may purchase the complete book in print or electronic format on
SPIE.org.
INSTITUTIONAL Select your institution to access the SPIE Digital Library.
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.