1 / 10

SEMAT Language Track

This session invites participants to provide brief statements reflecting on the language aspects of software engineering, aligned with the SEMAT vision. Each participant will have one minute to express their views, potentially presenting keywords that capture their thoughts on technology maturation, language types, and the relationship between models and real-world applications. The discussions aim to highlight the evolving nature of software technology and explore diverse language representations that are essential in the field. Statements will be recorded and shared with participants.

makan
Download Presentation

SEMAT Language Track

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SEMAT LanguageTrack

  2. Languagetrackproposal • General introduction • Each participant mayprovide a short statement on the languageaspects of software enginering • 1 minute maximum • maybe one sentence • maybe five keywords • maybecontroversial • maybeconsensual • Of course, the statementswillberelated to the SEMAT vision paper • All statementswillberecorded and send back to participants (scriber JM Favre).

  3. Software technology changes rapidly

  4. 18 ± 3 Software Technology Maturation • « The magicnumberEighteen Plus or Minus Three », William E. Riddle, ACM Sigsoft, April 1984 • 15 to 20 years to mature a technology to the point thatitcanbepopularized and disseminated to the technicalcommunityat large

  5. Only 3 technology maturation cycles

  6. WhichLanguages for Software Engineering? • Procedural, functional, object-oriented, rule-based? • Formal (Z, B, VDM, Petri) or not (Basic) • General Purpose or Domain Specific (DSLs) • Executable or Non-Executable • For process or product • For business or IT (e.g. BPMN & UML) • For professional (Eiffel) or end-users (Excel) • For objects, rules, events, process, goals, etc. • For code or data • Normative or Proprietary • Textual, Visual, Tabular, Form-based, … • Grammar-based, metamodel-based, schema-based, … • etc.

  7. Variousrepresentations μ Metalanguages (EBNF, XML Schema, MOF, ECORE, …) μ M3 Link Node μ μ μ Language Libraries, Repositories M2 Cat Mat on μ μ on M1 aCat aMat Basic artifacts (programs, etc.) $ x,$ y :Cat (x)ÙMat (y)Ùon (x,y)

  8. Representation and Conformance Grammar Schema Metamodel An algebraic structure Basic SE artifacts conformsTo System Program Model representationOf

  9. Taking the representation relation seriously "What about the [relationship between model and real-world]? The answer, and one of the main points I hope you will take away from this discussion, is that, at this point in intellectual history, we have no theory of this [...] relationship". Brian Cantwell Smith The Limits of Correctness; a paper prepared for the Symposium on Unintentional Nuclear War, Fifth Congress of the International Physicians for the Prevention of Nuclear War, Budapest, Hungary, June 28  July 1, 1985. See also “On the origin of objects”

  10. Robin Milner’s Grand Challenge Languageis the rawmaterial of software engineering, rather as water is the rawmaterial for hydraulic engineering… A more thorough science-based approach to informatics and ubiquitous computing is both necessary and possible. We often think in terms of models, whether formal or not.  These models, each involving a subset of the immense range of concepts needed for ubiquitous computer systems, should form the structure of our science… Even more importantly, the relationships (either formal or informal) among them are the cement that will hold our towers of models together. For example, how do we derive a model for senior executives from one used by engineers in designing a platform for business processes, or by theoreticians in analyzing it?

More Related