Defining the Roles and Responsibilities of the Systems Engineering Organization/Team

1997 ◽  
Vol 7 (1) ◽  
pp. 626-633 ◽  
Author(s):  
Jack Fisher
2018 ◽  
Vol 36 (7_suppl) ◽  
pp. 57-57
Author(s):  
Mandy Swiecichowski ◽  
Amye Tevaarwerk ◽  
Mark Juckett ◽  
James Edward Haine ◽  
Kirsten Norslien ◽  
...  

57 Background: BMT survivors are underrepresented in survivorship research, yet are at high risk for complications. Practice guidelines are vague, non-BMT clinicians are inadequately informed, and communication between BMT and non-BMT clinicians is inconsistent. Our objective is to develop EHR-integrated survivorship care planning that is user-centered, supports non-BMT clinician and survivor needs, but does not adversely impact clinical workflow. Methods: A multidisciplinary team of clinicians (primary care, oncology, BMT), engineers, and EHR analysts used a systems engineering approach to identify barriers and facilitators to BMT survivorship care planning. The team identified patient data categories to include in BMT survivorship care plan (SCP) templates, as well as examined tasks, technology, workflows and individual roles and responsibilities necessary to support care planning. Results: Facilitators include: potential for EHR to discretely capture individual diagnosis and treatment data to create accurate SCPs addressing survivor and primary care information needs. Barriers are: lack of EHR inter-operability which prevents sharing of patient data outside the BMT center’s EHR system, reliance on manual entry of critical data elements into the SCP (i.e. majority of the 88 patient data categories, identified by the team, are non-discrete in the EHR), inefficient or absent survivorship workflows, lack of resources (including time, dedicated clinical staff, space, SCP content), poorly defined roles and responsibilities for survivorship care provision, and lack of evidence-based BMT survivorship guidelines. Conclusions: Work system barriers impede use of the EHR to support survivorship care planning. Steps to overcome barriers: design discrete fields in the EHR to support patient-level data capture, re-engineer existing workflows to support survivorship care planning, obtain BMT program consensus on SCP content, and evaluate user-centeredness of SCPs. This research has the potential to improve feasibility and sustainability of survivorship care planning activities, resulting in improved communication and care coordination for BMT survivors.


2019 ◽  
Vol 29 (1) ◽  
pp. 1158-1173
Author(s):  
Barclay R. Brown ◽  
Bradford Leigh ◽  
Bruce Douglass ◽  
Larry Kennedy

Having a well-defined control of the change processes in the configuration management in the software development life cycle, before and after being put into production environment, implies an effort of development personnel and an additional cost in the maintenance system. The objective of this paper is to establish the guidelines to regulate the activities and tasks during the process of development and maintenance of software-based systems in order to control the changes, integrity and traceability of its configuration, for this purpose it is taken as a reference the peruvian technical standards NTP-ISO/IEC 12207: 2016 for Software and systems engineering, NTPISO/IEC 27001: 2014 for Information security management systems and the methodology MÉTRICA version 3 for the systematization of life cycle of the software activities. The proposal defines the roles and responsibilities, the activities of each thread and the use of control templates, the validation of the was achieved through the analysis of three software systems with results that show that there is a better organization in the development, maintenance, control of the versions of the elements and the percentage of error in the configuration.


2016 ◽  
Vol 19 (5) ◽  
pp. 422-435 ◽  
Author(s):  
Dawn Gilbert ◽  
Mike Yearworth

Having a well-defined control of the change processes in the configuration management in the software development life cycle, before and after being put into production environment, implies an effort of development personnel and an additional cost in the maintenance system. The objective of this paper is to establish the guidelines to regulate the activities and tasks during the process of development and maintenance of software-based systems in order to control the changes, integrity and traceability of its configuration, for this purpose it is taken as a reference the peruvian technical standards NTP-ISO/IEC 12207: 2016 for Software and systems engineering, NTPISO/IEC 27001: 2014 for Information security management systems and the methodology MÉTRICA version 3 for the systematization of life cycle of the software activities. The proposal defines the roles and responsibilities, the activities of each thread and the use of control templates, the validation of the was achieved through the analysis of three software systems with results that show that there is a better organization in the development, maintenance, control of the versions of the elements and the percentage of error in the configuration.


Sign in / Sign up

Export Citation Format

Share Document