BRIEFCASE | SEARCH | EMAIL THIS EVENT | LOGIN    
RSNA 2003 Scientific Papers > Use Of Forward Engineering (Automated Software Development) ...
 
  Scientific Papers
  SESSION: Radiology Informatics (PACS: Tools I)

Use Of Forward Engineering (Automated Software Development) in Healthcare Software Design and Implementation

  DATE: Tuesday, December 02 2003
  START TIME: 10:30 AM
  END TIME: 10:52 AM
  LOCATION: Room S404CD
  CODE: G21-717
TOOLS
 
ADD TO BRIEFCASE
  PRINT
  EMAIL

PARTICIPANTS
PRESENTER
Brian Rosenthal
 
CO-AUTHOR
Nogah Haramati MD
 

MOC
Management/Informatics/Health Policy
Keywords
Computers
Computers, educational aid
Computers, multimedia
Special
Virtual Presentation
 
Abstract:

HTML

Because the average programmer makes 1 mistake in every 7-10 lines of sourcecode, building reliable, large-scale systems poses a challenge for institutions that have specific needs. The maintenance of such systems in a cost-effective manner is challenging as maintenance represents 90% of software development costs, often far more than institutions anticipate. Forward Engineering is the process of automatically generating software from design specifications. Using forward-engineering techniques, software designers can design large software systems, and much of the software can be automatically generated, following established standards both technically, and also process-standards established within the industry / organization. Such techniques are attractive because (a) they streamline the prototyping process, (b) they allow for the software to evolve at the design level, and (c) they guarantee that standards / best practices are enforced as they evolve. Many developments in requirements analysis have allowed specification theory to elevate the comprehensiveness of software designs, such as the Zachman Framework. As purchasers, it is important to understand this thoroughly so that the expensive systems function properly in our organizations. One of us (BR) has built a forward-engineering engine. That engine subsequently built twelve different medical software products, based on recent developments in requirements analysis. This engine has produced twelve products, online in fifteen different hospitals, spanning five different languages, with 92% of the source code generated automatically from the design configurations. The implications of forward engineering to radiology software contracting will be discussed, along with the implications of requirements analysis to software purchasing.

 

 

1. Understand the concept of forward engineering 2. Assess the difference between forward engineered and traditionally coded software. 3. Understand the significance of forward engineered software to the costs and contractual issues related to software purchases 4. Understand the implication of requirements analysis in radiology software purchasing. (B.R. is a principle of MyBestHealth.)