Constructing a software development system Jimconrad with MOF 2004-10-17 Although the MOF model is a powerful modeling language, many types of information models can be expressed, but it does not attempt to end modeling languages. Instead, we want to use MOF to design and achieve more complex modeling systems. The following example will surround a hypothetical UDL modeling language, explaining how to build a software development system with MOF.
There are many similar places between the UML recommendations of the UDL and OA & DF, where UML is a universal modeling language as visual design and development component software. UDL can be treated as an extension of many concepts in UML, or a language of improvement. This extension is mainly manifested in more detail to complete a variety of implementation of the framework techniques and define additional meta-layer models, where the meta-layer model involves various technical fields such as database management, transaction processing, and more.
Developers based on UDL-based software development system will first use MOF MODEL's symbols to define UDL meta-model. For convenience, the UDL meta model reuses some or all MOF Model. I don't know if this is a good idea (the MOF meta model has some non-map special needs, for example: simplifying and supporting the model to generate the IDL Wait. Therefore, it is not reasonable to use the MOF meta model to do all types of object modeling.). The developer then uses a simple MOF-based development system (described in line to describe) to convert the UDL meta model to CORBA IDL, and provides the corresponding handwritten or generated software to implement UDL warehouse and appropriate UDL model input tool. (UDL warehouse includes UDL meta model, UDL model warehouse and UDL warehouse interface)
This hypothesis UDL development system does not consider the following: Provide certain levels of support for the process of creating the work code described by the system described in the UDL model. Depending on the nature of UDL, this process may include several steps, in which the concept design is converted to more specific design, and finally become a program source code. A UDL development system may provide designers and programmers for a series of tool auxiliary target systems. These tools need to be supported by the warehouse function (function, operation) to store special design and implementation information, along with version history information, project timetable information, etc., which constitutes a development process of mature software.
In practice, software development systems that implement the above lines may be difficult to encounter market needs. A typical software engineering "store" may have demand in both software engineering techniques and processes, but there is no "all-in-seas" development system. The current trend of the software development system is to tend to be universal warehouse systems; that is, a highly flexible system that can be quickly cut and expanded.
MOF-based universal warehouse systems will work based on MOF MODEL, and a tool for developing target meta (such as UDL) and their support tools. Many tools in a generic warehouse can be supported; that is, these tools may use higher levels of meta-level information to enable them to perform operations across mode categories. It features, such as persistence, replication, version control, and access control will need to be unified on different entity warehouse frameworks.
English text (from MOF specification): While the MOF model is a powerful modeling language for expressing a range ofinformation models, it is not intended to be the ultimate modeling language Instead, one intended use of the MOF is as a tool for designing and. implementing moresophisticated modeling systems. The following example illustrates how the MOF mightbe used to construct a software development system centered around a hypothetical "Universal Design Language" (UDL) .Many parallels can be drawn between the hypothetical UDL discussed below and thedraft OA & DF UML proposal in that UML is designed to be a general purposemodeling language for visualizing, designing, and developing component software.The UDL can be thought of as an extension, as well as a refinement, of many of theconcepts in the UML. The extensions are mainly in the Area of providing sufficientdetail to Complete the Implementation Framework Technologies and Defining Additionalmeta Models That Address Various Technology Domains Such As Database Ma Nagement, Transaction Processing, ETC.
The developer of a software development system based on UDL might start by using aMOF Model notation to define a meta-model for UDL. Conceivably, the UDLmetamodel could reuse part or all of the MOF Model, though this is not necessarily agood idea (The MOF metamodel has specific requirements (eg, model simplicity and support forautomatic IDL generation) that are not generally applicable. As a consequence, it is unreasonableto expect the MOF metamodel design to be suitable for all kinds of object modeling.). The developer could then use a simple MOF-based development system (along the lines described above) to translate the UDL metamodel into CORBA IDLfor a UDL repository, and to provide hand-written or generated software thatimplements the UDL repository and suitable UDL model input tools.The hypothetical UDL Development System Cannot Be ConsideRed Complete WITHOUTSOTING WORKING CODE THATEMENTSSYSSYSDRIBEDYD by The Udl Models. Dependin g on the nature of the UDL, thisprocess might involve a number of steps in which the conceptual design is transformedinto more concrete designs and, finally, into program source code. A UDLdevelopment system might provide a range of tools to assist the target system designeror programmer . These tools would need to be supported by repository functions tostore extra design and implementation information, along with information such asversion histories, project schedules, and so on, that form the basis of a mature softwaredevelopment process.
In practice, a software development system implemented along these lines would havedifficulty meeting the needs of the marketplace. A typical software engineering "shop" will have requirements on both the technical and the process aspects of softwareengineering that can not be met by a "one-size . -fits-all "development system thecurrent trend in software development systems is for Universal Repository systems; that is, for highly flexible systems that can be tailored and extended on the fly.A MOF-based universal repository system would be based around the core . of the MOFModel, and a suite of tools for developing target metamodels (for example, the UDL) and their supporting tools Many of the tools in the universal repository could bereflective; that is, the tools could make use of information from higher meta- Levels toallow the Operate Across A Range of Model Types. FunctionALITY, SUCH AS Asstence, Replication, Version Control, And Access Control Would Need To Be Supported Uniformlyac Ross the entire repository framework.
