Why and What on This Blog

The goal is to share author’s thoughts and communicate with everyone who interested in, and finally to promote the valuable one–if any. There is a theme here: all topics are relevant to models and modeling, which are mainly appeared in a few aspects.

  • Computer application. There are two keywords: architecture and enterprises. The main subject is application architecture; the enterprise applications are the origin and source, and also the main goal of the author in computing.
  • The right-side approaches. Mainly, in enterprise (business) engineering, including architecture (EA), modeling (EM), and so on. The meaning of right-side, see the Situation for Discussions about MDApps.
  • The fundamentals. The basic notions, principles, and perhaps some theories, for example, general modeling theory, to the above aspects.

There is another relevant term,  namely Information Systems; the word “enterprise” sometimes to be referred to some meanings a bit ambiguous and uninviting, someone may prefer to use “business” or “organization” to replace it in some case.

What the author talk about here is come from longtime practice and seeking, the tracks gone through is shown in the early post A Roadmap of Research for Enterprise Applications. One of the central topics here is the model-driven applications (abbreviated as MDApp(s) ), which is a concept proposed by the author, it is defined in three aspects: principles, type of a system, and the architecture. So far, this phrase is rarely appeared in English; it is not a widely recognized, well-defined concept yet. The idea is proposed originally as enterprise-model-driven application (EMDA), and then generalized as a concept for general computer application. Note that, it’s quite different with the well know concepts such as MDE / MDSD and MDA (see Model-Driven Applications vs. Model-Driven Engineering).

There is indeed an important basis for many of the topics on the blog, that is, general modeling theory (GMT; though it is perhaps not yet the time to propose the concept again), in which the term “modeling” is referred to two of meanings: to obtain and formulated a model, and to serve as a model. It is still a quite open issue so far but whatever, a GMT should be required to answer two fundamental questions

  • The first, what are models? An initial answer is shown in Model as Use.
  • The second, how models work? It can be due to the basic subject namely model-working mechanisms (MWM), and there is also a primary answer by the author: model-driven mechanism (MDM).

The author is committed to explore in such regards more than dozen years. All the efforts so far are done by himself and have no any relevant “background”. For a long time, the goal was focused on the development of specific software product but it had been unsuccessful, because never gotten enough resources to complete a preliminary development planning. That is perhaps must be due to the lack of personal capacities and some necessary “background”–it does not imply that it is doubtful to the feasibility; there are at least one company, faithfully followed the earliest account to develop their business application platform (an enterprise / business model-driven solution), and have been successful in market from ten yeas ago.

The author believes such the innovative ideas are very significant and valuable to industry, for both IT providers and the end users,  it should not be ignored. That is why he has been reluctant to give up though paid a heavy price and never gotten anything in return. Writhing hard on the blog is also an attempt to promote the ideas for the world.

By the way, the contents will be appeared in two sites: one is https://thinkinmodels.wordpress.com/ (the blog platform is blocked by the Fire Wall in the country); one is http://EE-Forum.org in which has the same contents in English and more in Chinese.

The author’s English is not well yet so reading and writing very slowly, among others, maybe make some critical mistakes in expressions but is not sensed by himself. Please remind if you have any questions, thanks! (25 March, 2013)

Author Biography

余彤鹰 (Yu, Tong-Ying; also signed as TY or Mountriver TY Yu on Internet) is an independent consultant from China, in the fields of enterprise application, business process improvement and transition, management; has a wealth of experiences from industrial and the experiences on each main phase in the lifecycle of enterprise applications. He is committed to the innovative development and research of the application for enterprises and information systems for a long term. The research interests include model-driven applications and model working mechanisms, architectures, enterprise modeling, enterprise engineering, and general modeling theory. Since 1998, he has published many influential articles through EE-Forum.org and so on; in 2001, launched the first enterprise engineering seminar in china.


Created: 26 March, 2011. Last updated: 26 March, 2013.



6 thoughts on “About

  1. Note for re-starting of this blog

    Because of certain reasons which I don’t want to mention, some resources on internet will suddenly not be able to access from our home such as the BSP WordPress in past a few months and modeldrivensoftware.net lately, thereby we must “cross the wall” if we still need to visit them. This is why I created a blog at wordpress.com but had stopped, started a new blog but now go back again…and why I hold the same entries in more the one place.

    Now, I restarted this blog and suspended the blog at http://modeldrivensoftware.net

    I wish it does not ZHE-TENG again.

    Mar 27, 2011

    Changed the default license from Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License to Attribution-NonCommercial-ShareAlike 3.0. (Nov 24, 2011)

    Posted by TY | March 27, 2011, 23:11
  2. TY, very interesting Blog ! Maybe you could be interested into our ”Model Interpretation” on wich we worked for the last 25 years. It’s actually working in large Information System in Canada. Look at http://www.consyst-sql.com Thx, Pierre Fournier

    Posted by Pierre Fournier | April 11, 2012, 23:35
  3. Hi Pierre, you are welcome!

    Thanks for your attention. Just looked at some information on the site. I think it’s a great effort. It reminds me of another solution to metadata management and your solution looks more sophisticated… :)

    It seems, IMHO, your solution are now being a development and integrating platform/environment and it provide a runtime environment (with the metadata) to the end applications too. It seems it’s based on the model of application systems but not of the enterprise/business (isn’t it?) – this may be a huge space to development. And, in addition to the reflection mechanism, the model driven mechanism is also (should be) the core principle to make such the system/solution.

    Just a very preliminary view. We would do some more discussion if you like.


    Posted by TY | April 12, 2012, 23:09
  4. Thx TY,

    As our metamodel is alive when applications are running (as an extension of the DBMS catalog if you want), 90% of our model is based on declarative but relevent executable metadata. All metadata are stoked and managed through a RDBMS, as any other information system. It can be enrich, enlarge, even hooked through a broader Enterprise / business model…

    When you talk about Business / enterprise model, opposed to Application Model, I suppose that you are talking about information who are not mandotory in the Application Execution ?

    I will be pleased to continu the discussion with you ! Best regards,

    Pierre Fournier

    Posted by Pierre Fournier | April 12, 2012, 23:59
    • Yes, I see – “All metadata are stoked and managed through a RDBMS” (didn’t say, languages) – that is a point I am attracted with and interested in. Since this is indeed somewhat an inevitable choice (onto “my” road). Thus it could be said that such the solution is firstly an extended RDB platform (if the stoked metamodel isn’t stored as some scripts but as relational data;-) ), in fact, it is necessary to redesign or reconstruct the current RDBMSs / apps (its ecosystem and/or the division among the relevant products, platforms, modules, etc.). This will take us go back on the E.F. Codd’s course, the data BANK based on the relational model and some lost essences hidden in such the Codd’s 12 rules (e.g. the necessity for a pure relational database) for many years.

      About the enterprise / business model and the distinction from the model of an application system, would you like have a look at this post, see “A model driven enterprise application framework based on MDM” with the Fig. 4, and some of my discussion on block/white-box model, and also my first essays on this blog, A Roadmap of Research for Enterprise Applications and Model-Driven: An Essential Requirement Come from Customers (the “customers” are not the IT managers / architects / developers but the end users of IT).

      I think, roughly, a metamodel repository based development / integration platform not yet a model driven application system for enterprises (the end use of IT in business) but the basis.

      Posted by TY | April 13, 2012, 10:16
  5. Change the license of the site from CC-BY-NC-SA to CC-BY-NC

    Posted by TY | February 23, 2013, 15:14

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s



Subscribe notifications of new posts by email.

Join 62 other followers

%d bloggers like this: