Software Engineering verteilter Systeme. Hauptseminar im WS 2011 / 2012

Transkript

1 Software Engineering verteilter Systeme Hauptseminar im WS 2011 / 2012

2 Model-based Testing(MBT) Christian Saad (1-2 students) Context Models (e.g. State Machines) are used to define a system s behavior Test cases can be generated by following different paths in the model Not all possible tests should be executed, only*good* ones Part 1: Theory Short introduction to Model-based Testing Discussion of relevant metrics for evaluating a given set of tests For example: % of states covered, distinctiveness of elements, Part2: Implementation

3 Requirements Engineering Christian Saad Context Requirement Management is an important part of modern Software Engineering processes Requirements that are only written down in text form are difficult to manage Theory Short introduction to Requirements Engineering in SE processes Survey of current tools and technologies in this area Description of model-based RE using the ReqIF modeling standard Techniques/Tools Eclipse Requirements Modeling Framework ( OMG ReqIF Specification ( IBM Rational Doors (

4 TextualDSL Editors withxtextvs. MPS Raphael Romeikat Context of domain-specific languages(dsls) What are DSLs Abstract syntax: defines the structure of the models(metamodel) Concrete syntax: defines how the models look like(notation) Frameworks for textual DSL editors Xtext( MPS ( Comparison Implementation One example with both frameworks Personal experience

5 Textual DSL Editors with TEF vs. Monticore Raphael Romeikat Context of domain-specific languages(dsls) What are DSLs Abstract syntax: defines the structure of the models(metamodel) Concrete syntax: defines how the models look like(notation) Frameworks for textual DSL editors TEF ( Monticore( Comparison Implementation One example with both frameworks Personal experience

6 Collaborative Ontology Design Wolf Fischer Overview Ontology Shared Conceptualization Endless discussions for creating an ontology Tool support could facilitate ontology design process Tasks Become familiar with Ontologies, Ontology Design, etc. Create prototype

7 Controlled Natural Language for Software Requirements Wolf Fischer Overview ControlledNatural Language isa simplificationofnormal Natural Language (Simplified Syntax, Controlled Vocabulary, etc.) Easier for computers to parse, relatively easy for humans to use Good for mapping syntax to semantic Ideal for Software Requirements Tasks Become familiar with CNLs Create a CNL for Software Requirements Realize within BRM-S

8 OWL 2 BRM-S Transformation Wolf Fischer Overview OWL: De-facto ontology standard BRM-S: Bridging natural language and ontologies Transforming OWL information within an BRM-S model Tasks Become familiar with OWL, BRM-S, GMF, Eclipse Create a prototypical transformation from OWL to BRM-S

9 Safety& Security Analysis Techniques Benjamin Honke Focus Techniques to analyze Safety& Security properties» FMEA, FMECA, FTA, (A)SIL Relevant Norms& Standards» (ISO 26262, IEC 61508, DO 178 B/C, ARP 4754) State oftheart analysis Software System Safety Handbook NASA Software Safety Guidebook Showcase Evaluation

10 Process Coordination Paradigms Benjamin Honke Context Process models are more than paperware Processmodelcanbeusedfor Tasks» Enactment project setup» Execution project coordination(activity-centric vs. artifact-centric) Literature research State of the Art Analysis Comparison of different approaches

11 Organisatorisches Bewerbung an Betreuer ( Name, Matrikelnummer, Studiengang, Semester Bereits gehörte Vorlesungen und Seminare im Hauptstudium Gegebenenfalls weitere qualifizierende Vorkenntnisse Drei priorisierte Themenwünsche STUDIS Zusätzliche Anmeldung in STUDIS ist zwingend erforderlich Seminararbeit Formatvorlage auf der PvS-Website (Springer LNCS, LaTeX) Umfang: Seiten (exkl. Anhang) Abgabe aller für die Kompilierung notwendigen Ressourcen + Arbeit im PDF-Format Seminarvortrag Formatvorlage auf der PvS-Website (PowerPoint, andere Programme erlaubt) Dauer: ca. 45 min / Person (35-40 min Vortrag, 5-10 min Diskussion) Anrechung des Seminars Alle Themen können in den Bereich Software Engineering eingebracht werden

12 Termine Kickoff-Meeting: Bewerbungsschluss: Verteilung der Themen: Versandvon Literaturhinweisen Anmeldung in STUDIS: 1. Besprechung: Literaturüberblickabgeschlossen Grobgliederungerstellt 2. Besprechung: Feingliederungerstellt Seminararbeit~90% geschrieben Abgabe der Seminararbeiten: Abgabe der Foliensätze: offizieller Zeitraum (spätestens) (spätestens) (spätestens) (spätestens) Seminarvorträge: