Applying Software Engineering Methodology for Designing Biomedical Software Devoted To Electronic Instrumentation

Problem statement: Significant effort goes into the development of bio medical software, which is integrated with computers/processors, sens ors and electronic instrumentation devoted to a specific application. However, the scientific work on electronic instrumentation controlled by biomedical software has not emphasized software development, instead focusing mainly on electronics engineering. The development team is rarely composed of Software Engineering (SE) experts. Usually, a commercial automated tools environment is not used due to its high cost and complexity for researchers from other areas to understand. Approach: This present study reports how the SE approach was applied to design and develop biomedical software, which is part of a Computerized Electronic Instrumentation (CEI). This CEI comprise s software and an electronic instrumentation based on a force sensor and electrogoniometer to mo nitor the hand exertion of computer user during typing task. The aim is to serve as a guideline for academic researchers who are not expert in softwar e engineering methodology but usually develop their o wn software to run with their CEI. The specification of the requirements, presented as use case, includes the context diagram, the data flow diagram, the entity relationship diagram and test p rocedure. The Unified Modelling Language from the Enterprise Architect tool was used. The developed s oftware and the electronic instrumentation were tested together. Results: A sample of the interface screen shows how the out comes could be plotted in an integrated manner. By comparing the values with other values obtained by manual calculations and with those provided by sensor manufacturer, the rep eatability of test procedure validated the results. Reliable electronic instrumentation when working with unreliable software can become unreliable. Conclusion: Applying software engineering methodology principles provided a simple and clear documentation that was helpful to establish the tes t procedures and the re-work.

[1]  Elena Troubitsyna,et al.  Developing Fault Tolerant Distributed Systems by Refinement , 2010, 2010 Fifth International Conference on Software Engineering Advances.

[2]  R. M. Suresh,et al.  Software Architecture Evaluation Methods - A survey , 2012 .

[3]  Akira Fukuda,et al.  Structured analysis for software product lines , 2009, 2009 IEEE 13th International Symposium on Consumer Electronics.

[4]  Gilles Soulez,et al.  Clinical validation of a software for quantitative follow-up of abdominal aortic aneurysm maximal diameter and growth by CT angiography. , 2011, European journal of radiology.

[5]  Alok Mishra,et al.  Simplified software inspection process in compliance with international standards , 2009, Comput. Stand. Interfaces.

[6]  T. S. E. Maibaum,et al.  A Product-Focused Approach to Software Certification , 2008, Computer.

[7]  Gilsa A. L. Machado,et al.  Design of an electronic instrumentation for measuring repetitive hand movements during computer use to help prevent work related upper extremity disorder , 2011 .

[8]  Hesham A. Ali,et al.  Database Security Protection based on a New Mechanism , 2012 .

[9]  Enrique J. Gómez,et al.  Architecture of a wireless Personal Assistant for telemedical diabetes care , 2009, Int. J. Medical Informatics.

[10]  G. D'Addio,et al.  In-Time Prognosis Based on Swarm Intelligence for Home-Care Monitoring: A Case Study on Pulmonary Disease , 2012, IEEE Sensors Journal.

[11]  Larry Constantine,et al.  Structure and style in use cases for user interface design , 2001 .

[12]  Mario Cannataro,et al.  Early detection of voice diseases via a web-based system , 2007, MAVEBA.

[13]  Jauhar Ali,et al.  An Industrial Case Study for Scrum Adoption , 2012, J. Softw..