Displaying discussions with Hans here February
2010-02-12
1. Philosophy: Lead, not follow. Solve hard problem and build an illustrative prototype, industrial standards are hard to follow because we are small research groups. Not too much coding. If our work solves problems of their concern, the industrial will come to us for the prototype and commercialize it. 2. Research Route: Build a Mindmap, Problem breakdown. Publish papers or write a technique report about each sub-problem. 3. Exhaustive analysis about problem and sub-problems: What’s been done by others? What do I do in the topic? What I (others) will do in the future? 4. Case study of my research: A suitable relatively complex system to study. We need to know the coding (when my research is absent), then we do modeling and transformation applying our research fruits on. 5. Restrict the research domain: around SMP2 and in a specific problem domain to illustrate a MDA application. (MDA is a abstract concept, we will give a illustration and develop it) 6. AToMPM, improved version of AToM3, neutral action language. MOF-based.
1.Modeling the joint training
a)Topic: what you want to study;
b)Scope: what you want to study here, considering Hans’ interests and the topic;
c)Expected fruits: papers, prototypes, tools
2.Modeling the paper(part I):Where to publish?
a)Literature review to find the research community;
b)Relevant journals and conferences;
c)Relevant researchers and organizations--Where they publish, what’s their favoritesd)On the internet (personal website, mainly via technique report)
3.Modeling the paper(part II):Why technique report?—record your experience and work in detail via written form.
a)Detailed literature review (maybe for your PhD thesis);
b)Detailed description of work;
c)Record the work not published in journal nor conference;
d)For time-step to publish your work earlier; e)Source for related work of a paper.
4.Modeling the paper(part III);Organization of a paper (thesis, or problem, we can break it down, also apply to sub problems):
a)Literature review (related work);
b)Foundation (theory);
c)Prototype (implementation);
d)Case study (validation);
5.Theoretical academic research versus commercialized application research:
a)Elegant foundation;
b)Prototype adopting commercial standard
1.About Case study in Antwerp:
a) Find a collaborator (Hopefully In UA, or Ghent, Brussels, Hasselt) in Belgium
b) Domain: Urban Planning, M&S of Transportation.
2.Two application directions of M&S:
a) Science: Biology, Medicine, Chemistry (for the sake of understanding)(difficult but prospective)
b) Engineering: M&S based design(design space exploration, performance analysis and simulation)
3.How to use model?
a) Understanding (simulation)
b) Answer questions(model checking)
c)Performance analysis(simulation)
d)Realize (synthesize of simulation, model checking and formal verification)
4. Where to publish
a)Journals: SoSyM, SIMULATION, JDMS, SimPaT
b)Conferences: MODELS;SummerSim, WSC, SimuTools
March
2010-03-02
1.UML a)UML : a series of diagram supporting the requirements, designing and deployment of software.
b)Ways to use UML: Profile, Metamodeling, SysML
c)UML needs precise definition of Semantics
d)Publications for UML : MODELS,SoSyM
2.UML(to describe software) and M&S
a)M&S systems contain software
b)M&S needs software (simulator)
c)UML was not designed for M&S purpose, but can support M&S
3.Road to New Scientific contributions
a)Using MDE Techniques in M&S:need true contributions in M&S (To be recognized) and Vice versa.
b)Combining MDE and M&S: more feasible (because both are evolving) but be careful
4.Potential Contributions for PhD Study
a)Large Scale Model Transformation for M&S(Work together with Eugene in Aug and Sep)
b)DSM (visual) Language for M&S (in the browser)
c)Multi-formalism, multi-view modeling
d)An Advanced M&S framework
5.MPM Philosophy:
a)Model everything explicitly and Minimize accidental complexity. b)Model on the right abstraction level, using the right formalism c)How to implement : Modeling Language Engineering d)How to implement MLE: MM, MT
6.Modeling Language Engineering:
a)Abstract syntax, concrete syntax, semantics, syntactic mapping and semantic mapping
b)Render VS. Parsing
c)Semantics of metamodel(e.g. Class diagram)
About Modeling Language Engineering a)Basics of modeling Languages: Model, metamodel, syntax and semantics.
b)Hans’s picture about Modeling Language
c)ML is the core Technology of Generative M&S
d)Semantic Anchoring
1.Atom3 Demo
a)Modeling in Atom3
b)Model transformation in Atom3
c)Atom3 future: Industrial-strength complex modular transformation
2. (Concrete) Modeling language, formalism(operational and denotational), MoC(operational)
April
2010-04-01
1.Modeling Language Engineering Proposal
a)A common scientific foundation for DSM
b)Multi-Dimensional Separation of Concerns
c)Atom3 future: Industrial-strength complex modular transformation
2. AtoM3 Demo:Model Transformation, PacMan M&S
|
Maintained by Xiaobo Li. | Last Modified: 2010/04/20 16:33:15. |