Roles in the MDA Process: MDA will make developers more productive, not redundant

Uptake of the Object Management group's Model-Driven Architecture (MDA) initiative is dependent not only on its technical capabilities, but also the acceptance of the approach in the developer community. This paper examines the roles in today's software development processes and show how those roles change and improve as MDA is applied.

By Stephen J. Mellor
stephen_mellor@mentor.com, or www.mentor.com/embedded
and Andrew Watson
andrew@omg, or www.omg.org

Register to Download the Presentation:

NOTE: REQUIRED FIELDS ARE MARKED WITH *

	Salutation:* Ms. Mrs. Mr. Dr. Prof.
	Primary Business:* Advertising Aerospace & Defense Agribusiness Airlines Alcoholic Beverages & Tobacco Apparel & Footwear Broadcasting & Cable Business Process Management Chemicals Computers Consulting Educational Services Environmental & Waste Management Financial Services Government Healthcare Homebuilding Information Technology Insurance Networking Pharmaceuticals Retailing Software System Design Telecommunications Transportation Travel & Tourism Wholesaling
	Areas of Interest:* Blockchain Business Architecture BPM - Business Process Management CORBA - Common Object Request Broker Architecture Data Governance DDS - Data Distribution Service Finance Government/Military Healthcare IIoT - Industrial Internet Standards Manufacturing MDA - Model Driven Architecture Ontologies Retail Robotics Software Quality Space SysML - OMG Systems Modeling Language System Assurance UAF - Unified Architecture Framework UML - Unified Modeling Language

To prevent automated posts, Please type this code 3TMw8 into the field below.

 

The information you submit with this form is subject to OMG's Privacy Policy.

Whitepapers produced by third parties do not express the opinions of OMG or its other members, and OMG does not endorse any products mentioned or claims made therein.