LSR ASE 2005 Panel on Education in Automated Software Engineering Yves Ledru LSR/IMAG, University of Grenoble-1, (France) Long Beach, CA,Nov. 11th 2005.

Slides:



Advertisements
Similar presentations
Practical Database Design Methodology and Use of UML Diagrams
Advertisements

CASE tools Upper CASE tools: support for the analysis and design Lower CASE tools: support for construction and maintenance 1980s… Nowadays… Integrated.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 1: Introduction.
Budapest University of Technology and EconomicsDagstuhl 2004 Department of Measurement and Information Systems 1 Towards Automated Formal Verification.
S Y S T E M S E N G I N E E R I N G.
Free Mini Course: Applying UML 2.0 with MagicDraw.
Unified Modeling Language
Formal Methods in Software Engineering Credit Hours: 3+0 By: Qaisar Javaid Assistant Professor Formal Methods in Software Engineering1.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
Jan 2005 Ron McFadyen1 Contracts Used to help understand requirements more completely (and so may not always be necessary) based on assertions;
Rainbow: XML and Relational Database Design, Implementation, Test, and Evaluation Project Members: Tien Vu, Mirek Cymer, John Lee Advisor:
LSR TOBIAS and some ASE challenges Y. Ledru P. Bontron, O. Maury, L. du Bousquet, M.L. Potet, C. Oriat, S. Beghdadi, H. Bouldjedri LSR/IMAG – Grenoble.
September 2002 R McFadyen1 Domain Model Use Case Model text diagram SSD System operation contracts Design Model Figure 13.3.
1 Info 1409 Systems Analysis & Design Module Lecture 8 – Modelling tools and techniques HND Year /9 De Montfort University.
LSR 1 Jartege : a Tool for Random Generation of Unit Tests for Java Classes Catherine Oriat LSR/IMAG, Grenoble, France (presented by Yves Ledru) SOQUA’05,
1 Scenario-based Analysis of UML Design Class Models Lijun Yu October 4th, 2010 Oslo, Norway.
Software Engineering Education Andy Gravell, Feb 2007.
Compiler Design Nai-Wei Lin Department of Computer Science National Chung Cheng University.
Object Oriented Analysis By: Don Villanueva CS 524 Software Engineering I Fall I 2007 – Sheldon X. Liang, Ph. D.
1.1 © 2007 by Prentice Hall 11 Chapter Building Information Systems.
Project CC4U2 Setting an Efficient Partnership for Allowing International Student Exchanges: a Difficult Issue Philippe Lahire University of Nice Sophia.
MDE Model Driven Engineering Xavier Blanc Université Pierre et Marie Curie
Adaptive Processes © Adaptive Processes Simpler, Faster, Better Software Requirements.
February 24th 2000Peter Demeester - Philippe De Pauw 1 ObjeCt oriented Agents for distributed PlannIng systems OCAPI-COALA team.
Requirements Engineering Requirements Elicitation Process Lecture-8.
Overview of Formal Methods. Topics Introduction and terminology FM and Software Engineering Applications of FM Propositional and Predicate Logic Program.
Information System Development Courses Figure: ISD Course Structure.
Generic API Test tool By Moshe Sapir Almog Masika.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Future Media  BBC MMXI TDD at the BBC David Craddock, Jack Palfrey and Tom Canter.
1 Department of Electrical, Computer, and Software Engineering Faculty of Engineering and Applied Science UOIT
Improving Code Generation for Associations: Enforcing Multiplicity Constraints and Ensuring Referential Integrity SERA 2013SERA 2013 (August 7, 2013 in.
Requirements Specification. Welcome to Software Engineering: “Requirements Specification” “Requirements Specification”  Verb?  Noun?  “Specification”
Simulating Real-Life IT Project Environments Nicholas Harkiolakis, PhD Hellenic American University Athens - Greece.
Software Production ( ) First Semester 2011/2012 Dr. Samer Odeh Hanna (PhD)
Sheet 1 DocEng’03, Grenoble, November 2003 Model Driven Architecture based XML Processing Ivan Kurtev, Klaas van den Berg University of Twente, the Netherlands.
A DESIGN AND IMPLEMENTATION COURSE FRAMEWORK: A CURRICULUM PROPOSAL FOR AN EXPERIENTIAL APPROACH TO THE SYSTEMS ANALYSIS AND DESIGN AND THE PROJECTS IN.
Rainbow: XML and Relational Database Design, Implementation, Test, and Evaluation Project Members: Tien Vu, Mirek Cymer, John Lee Advisor:
Applying a Research Prototype Tool in Industrial Practice Ottawa Carleton Institute for Computer Science Umple: a Model Oriented Programming Language University.
Software Engineering Emphasis for Engineering Computing Courses William Hankley Computing & Information Sciences Kansas State University.
CIM LAB MEETING Presentation on UML Rakesh Mopidevi Kwangyeol Ryu.
Source Mastering UML with Rational Rose 2002 Information System Engineering Introduction to UML.
UML Diagrams for Caradon developers Daniel DG Moth Core Development Group, Research Student University of Brighton, MSc Object Oriented Software Technology.
Software Design. A well-known phenomenon You will learn…. –Thinking "object oriented“ –Define requirements and analyze the problem domain. –Design of.
LSR Test purposes: adapting the notion of specification to testing Yves Ledru, L. du Bousquet, P. Bontron, O. Maury, C. Oriat, M.-L. Potet LSR/IMAG Grenoble,
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 14.
UniTesK Test Suite Architecture Igor Bourdonov Alexander Kossatchev Victor Kuliamin Alexander Petrenko.
Object Oriented Analysis and Design 1 Chapter 9 From Design to Implementation  Implementation Model  Forward, Reverse, and Round-Trip Engineering  Mapping.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
Source Mastering UML with Rational Rose 2002 Information System Engineering Introduction to UML.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
UniTesK Test Suite Architecture Igor Bourdonov Alexander Kossatchev Victor Kuliamin Alexander Petrenko.
Abstract BPEL Candidate Use Case: Modeling for Business Understanding Wednesday, May 23, 2004 Disclaimer: These are the views of Phil Rossomando and not.
Formal Methods: for All or for Chosen? Victor Kuliamin 1 Vitaliy Omelchenko 1 Olga Petrenko 2 1 Institute for System Programming 2 Institute of Open Education.
TCCICOMPUTERCOACH ING.COM.  TCCI-Tririd Computer Coaching Institute provides best teaching in basic computer programming language at tcci-ahmedabad.
CompSci 280 S Introduction to Software Development
5/11/2018.
An Overview of Requirements Engineering Tools and Methodologies*
What is Wrong with Models?
Used to help understand requirements more completely
Object-Oriented Software Engineering Using UML, Patterns, and Java,
Applying a Research Prototype Tool in Industrial Practice
Conceptual data modeling
CSE432: Object-Oriented Software Engineering
University of Nice Sophia Antipolis
Object-Oriented and Classical Software Engineering Sixth Edition, WCB/McGraw-Hill, 2005 Stephen R. Schach
Software Requirements
Software Requirements
UML Design for an Automated Registration System
Software Architecture & Design
Presentation transcript:

LSR ASE 2005 Panel on Education in Automated Software Engineering Yves Ledru LSR/IMAG, University of Grenoble-1, (France) Long Beach, CA,Nov. 11th 2005

LSR The french educational system Master 1st year Master 2 Research Master 2 Pro Software Engineers (practitioners of ASE) Ph D Researchers (designers of ASE) Should we teach the same ASE courses to both kinds of students?

LSR Automatic generation of applications from a UML diagram PERSON Lastname Firstname Cardnb Tel [*] * GROUP Groupcode Groupname 1 GroupofpersonMembers Delphia Object Modeler Level: Master 1 Context: UML+Z course Objectives: –Show that the concepts learned in the course are at the basis of such tools –Experimentation with such tools –Limits of such tools : show that the specification of constraints on the database schema is shorter than their actual implementation with deamons

LSR What should software engineers learn? Master 1st year Master 2 Pro Software Engineers (practitioners of ASE) Concepts The magic of ASE tools The limits of ASE tools Practice the tools in order to see: My experience in this curriculum: Master 1: DOM Master 2: DbC executable specifications (VDM, JML)

LSR Research : KIDS/VDM Theme: prototyping VDM specifications using KIDS Underlying concepts: –Design by contract (VDM) –Program synthesis (KIDS) Underlying technologies: –Theorem Proving (KIDS) –The Refine language: Functional, Declarative, imperative, Object- oriented + Input/output grammars! Too many things to learn for a master 2 project!

LSR What should PhD students learn? Master 1st year Master 2 Research Ph D Researchers (designers of ASE) Concepts Underlying Techniques! Bad news: Underlying techniques are very dependent on the kind of tool you are trying to build! Evaluation techniques!

LSR What should they learn? (Merging) Master 1st year Master 2 Research Ph D Researchers (designers of ASE) Concepts Underlying Techniques! Master 2 Pro Software Engineers (practitioners of ASE) The magic of ASE tools The limits of ASE tools Practice the tools in order to see: Underlying Techniques! Evaluation techniques!

LSR Use your own medecine! Tool: TOBIAS Combinatorial testing of Java programs Tool developed by 2 PhD students + 2 Master students Tool written in Java Succesfully used outside of our team But… today never used to test TOBIAS itself!

LSR What should they learn? (Merging) Master 1st year Master 2 Research Ph D Researchers (designers of ASE) Concepts Underlying Techniques! Master 2 Pro Software Engineers (practitioners of ASE) The magic of ASE tools The limits of ASE tools Practice the tools in order to see: Underlying Techniques! Evaluation techniques! Researchers should be the first actors to bridge the gap between research and practice!

LSR