| Popis: |
Healthcare diagnostic applications demand state-of-art technology in order to assist the doctor to do accurate and efficient diagnoses. In order to keep pace with the latest technologies Philips Medical Systems has a competency development group which executes projects that examine the feasibility of adapting an existing product to a new technology/platform. The outcome of these projects is to evolve a set of new features in its existing applications/products which can leverage the new technology. The requirements collected at the end of this project typically drive a technology migration project.The stake holders in a competency development project typically represent different medical imaging groups unlike normal product engineering where stakeholders are the end-users. The outcome of this project in most cases may not directly result in a newly marketable product, but a product which is technologically superior, competitive and essentially one which can improve diagnostics or treatment of patient health care. As in the case of R&D projects these projects are also characterized by unclear/shifting goals. Established techniques of planning tracking and management which are applicable to most mainstream software engineering projects aren't applicable to competency development projects. In this paper we outline a well defined and managed approach to requirements engineering using competency development projects, which in effect are prototyping projects. We substantiate our arguments with some case studies carried out at Philips Medical Systems. |
