The Proceedings of the Information Systems Education Conference 2005: §2534    Home    Papers/Indices    prev (§2533)    Next (§2535)
Fri, Oct 7, 3:30 - 3:55, Governors E     Paper (refereed)
Recommended Citation: Conn, S S and L Forrester.  Model Driven Architecture: A Research Review for Information Systems Educators Teaching Software Development.  In The Proceedings of the Information Systems Education Conference 2005, v 22 (Columbus OH): §2534. ISSN: 1542-7382. (A later version appears in Information Systems Education Journal 4(43). ISSN: 1545-679X.)

Model Driven Architecture: A Research Review for Information Systems Educators Teaching Software Development

Refereed10 pages
Samuel S. Conn    [a1] [a2]
Graduate School of Computer and Information Sciences
Nova Southeastern University    [u1] [u2]
Fort Lauderdale, Florida, USA    [c1] [c2]

Lynne Forrester    [a1] [a2]
University of Denver    [u1] [u2]
Denver, Colorado, USA    [c1] [c2]

The increasing complexity of business systems, the accelerating pace of technological change, and the highly competitive business environment are overwhelming software development methodologies that have stayed essentially the same for the last fifty years. Model Driven Architecture (MDA) is a current initiative by the Object Management Group that represents a major evolution in the way software is developed. There is growing consensus by the information systems community on the fundamental principals of MDA, but some critical elements are missing in the areas of transformation and system-behavior modeling. Agreement on standards and approaches in these areas will take some time, and substantial work remains before MDA can replace traditional, long-practiced methods and be considered a routine approach to software development. When this happens it has the potential to significantly improve the integration of customers into the software development lifecycle. Traditional development methodologies and the newer agile methods strive to overcome quality and delivery problems by emphasizing customer involvement and by attempting to move system validation activities (e.g. those concerned with confirming that the system will meet the customerís needs) earlier in the development lifecycle. The adoption of an MDA approach will not change the role of customers in the development process or the nature of their activities; it will not change what customers do. However, it can significantly change when customers validate a systemís functionality. This paper will investigate these issues through a qualitative study using an interpretivist epistemology, and will form generalized conclusions about MDA.

Keywords: model driven architecture, MDA, customer integration, PIM, PSM, life cycle development

Read this refereed paper in Adobe Portable Document (PDF) format. (10 pages, 501 K bytes)
Preview this refereed paper in Plain Text (TXT) format. (34 K bytes)

Comments and corrections to