 Introduction  Methodology  Case Study 1 : Event-B and RODN  Case Study 2 : B-Method and Atelier B  Observations and Analysis  Conclusion.

Slides:



Advertisements
Similar presentations
DEVELOPING A METHODOLOGY FOR MS3305 CW2 Some guidance.
Advertisements

Requirements gathering
Rigorous Software Development CSCI-GA Instructor: Thomas Wies Spring 2012 Lecture 11.
LIFE CYCLE MODELS FORMAL TRANSFORMATION
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 9 Duplication.
CS 355 – Programming Languages
Spoken Language Support for Software Development Andrew Begel University of California, Berkeley Advisor: Prof. Susan L. Graham.
Ch 11 Cognitive Walkthroughs and Heuristic Evaluation Yonglei Tao School of Computing and Info Systems GVSU.
Part 4: Evaluation Days 25, 27, 29, 31 Chapter 20: Why evaluate? Chapter 21: Deciding on what to evaluate: the strategy Chapter 22: Planning who, what,
1 / 31 CS 425/625 Software Engineering User Interface Design Based on Chapter 15 of the textbook [SE-6] Ian Sommerville, Software Engineering, 6 th Ed.,
Today’s class Group Presentation More about principles, guidelines, style guides and standards In-class exercises More about usability Norman’s model of.
Design and Evaluation of Iterative Systems n For most interactive systems, the ‘design it right first’ approach is not useful. n The 3 basic steps in the.
Project Life Cycle Jon Ivins DMU. Introduction n Projects consist of many separate components n Constraints include: time, costs, staff, equipment n Assets.
User interface design Designing effective interfaces for software systems Objectives To suggest some general design principles for user interface design.
CS 330 Programming Languages 09 / 16 / 2008 Instructor: Michael Eckmann.
Lecture 7 Evaluation. Purpose Assessment of the result Against requirements Qualitative Quantitative User trials Etc Assessment of and Reflection on process.
Specifying Languages CS 480/680 – Comparative Languages.
Requirements Gathering and Task analysis. Requirements gathering and task analysis 4 Requirements gathering is a central part of systems development understanding.
1. Learning Outcomes At the end of this lecture, you should be able to: –Define the term “Usability Engineering” –Describe the various steps involved.
PROGRAMMING LANGUAGES The Study of Programming Languages.
CC0002NI – Computer Programming Computer Programming Er. Saroj Sharan Regmi Week 7.
Compositional IS Development Framework Application Domain Application Domain Pre-existing components, legacy systems Extended for CD (ontologies) OAD Methods.
WRITTEN ABILITY TEST(WAT) GUIDE An initiative of MPRC, IIM Kashipur.
1 ICAS’2008 – Gosier, March 16-21, 2008 A Transformational Approach for Pattern-based Design of User Interfaces Costin Pribeanu Jean Vanderdonckt National.
Invariant Based Programming in Education Tutorial, FM’08 Linda Mannila
Key Challenges for Modeling Language Creation by Demonstration Hyun Cho, Jeff Gray Department of Computer Science University of Alabama Jules White Bradley.
TMF1013 : Introduction To Computing Lecture 1 : Fundamental of Computer ComputerFoudamentals.
Nielsen’s Ten Usability Heuristics
Multimedia Specification Design and Production 2012 / Semester 1 / week 5 Lecturer: Dr. Nikos Gazepidis
© 2006 Pearson Education 1 Obj: cont 1.3 and 1.4, to become familiar with identifiers and to understand how programming languages work HW: p.51 #1.8 –
ISBN Chapter 3 Describing Semantics -Attribute Grammars -Dynamic Semantics.
Design 2 (Chapter 5) Conceptual Design Physical Design Evaluation
Software Architecture
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 10.
Chapter 6: Thinking about requirements and describing them.
Developed by Tim Bell Department of Computer Science and Software Engineering University of Canterbury Human Computer Interaction.
Usability Engineering Dr. Dania Bilal IS 582 Spring 2006.
3.2 Semantics. 2 Semantics Attribute Grammars The Meanings of Programs: Semantics Sebesta Chapter 3.
ISBN Chapter 3 Describing Semantics.
Survey Methodology Survey Instruments (1) EPID 626 Lecture 7.
Cognitive Dimensions  Developed by Thomas Green, Univ. of Leeds  Used to analyze the usability of information artifacts  Applied to discover useful.
OVERVIEW Framework Overview – From Programming to Music Dimensions in Detail – Visibility, Progressive Evaluation, Consistency, Viscosity, Abstraction.
Usability Engineering Dr. Dania Bilal IS 592 Spring 2005.
Heuristic Evaluation Short tutorial to heuristic evaluation
Chapter 5:User Interface Design Concepts Of UI Interface Model Internal an External Design Evaluation Interaction Information Display Software.
Formal Specification: a Roadmap Axel van Lamsweerde published on ICSE (International Conference on Software Engineering) Jing Ai 10/28/2003.
Concepts and Realization of a Diagram Editor Generator Based on Hypergraph Transformation Author: Mark Minas Presenter: Song Gu.
The Semantic Web. What is the Semantic Web? The Semantic Web is an extension of the current Web in which information is given well-defined meaning, enabling.
Programming Language Design Issues Programming Languages – Principles and Practice by Kenneth C Louden.
The Design Process A bluffer’s guide to interface design A ‘proper’ Design process.
Examining issues with advanced authoring Chris Roast Andrew Dearden Babak Khazaei Sheffield Hallam University.
INTRODUCTION TO COGNITIVE SCIENCE NURSING INFORMATICS CHAPTER 3 1.
Usability Engineering Dr. Dania Bilal IS 582 Spring 2007.
CSC141 Introduction to Computer Programming Programming Language.
Introduction to Computer Programming Concepts M. Uyguroğlu R. Uyguroğlu.
Cognitive Dimensions  Developed by Thomas Green and Alan Blackwell  Enhanced by Marian Petre Marian PetreMarian Petre  Descriptions of aspects, attributes,
Review of Usability Testing
Lexical and Syntax Analysis
Sparkle a functional theorem prover
Algorithm and Ambiguity
HCI in the software process
TRANSLATORS AND IDEs Key Revision Points.
Informatics 121 Software Design I
Ada – 1983 History’s largest design effort
Heuristic Evaluation Jon Kolko Professor, Austin Center for Design.
Krug Chapter 6 B: Flow in UIs
HCI in the software process
HCI in the software process
Boolean Expressions to Make Comparisons
Nilesen 10 hueristics.
Presentation transcript:

 Introduction  Methodology  Case Study 1 : Event-B and RODN  Case Study 2 : B-Method and Atelier B  Observations and Analysis  Conclusion

To evaluate the usability of Event-B and Rodin compared to B-Method and Atelier B Demonstrate how easy it is to learn Event-B with Rodin Focus on novice users – context of education

B-Method - method of software development based on B - programming language code is developed from specifications. - relates to the B language, refinement, proof and its related tools. - Supporting tool : Atelier B Event-B - Evolution of B - Supporting tool : Rodin

 Case Study Demonstration  Case Study 1 : Event-B and Rodin  Case Study 2 : B-Method and Atelier B  Usability Evaluation  Cognitive Dimensions Framework  ISO Usability criteria  Generic case study evaluation criteria suggested by Rodin

 Case Study Demonstration  Case Study 1 : Event-B and Rodin - Simple Railway System  Case Study 2 : B-Method and Atelier B - Simple Jukebox System

 Usability Evaluation  Cognitive Dimensions Framework - CD questionnaire ; 14 CDs  ISO Usability criteria - Learnability and Understandability  Generic case study evaluation criteria suggested by Rodin - 6 criteria

types and availability of abstraction mechanisms. -high level of abstraction for both notations Relates to learnability and understandability

how closely related is the notation to the end result

Are similar semantics expressed in similar syntactic forms. - High level of consistency for both notations Relates to learnability and understandability

Verbosity of a language High level for novice users of both notations Mathematical symbols - short and have 1 interpretation Expressions long-winded and complicated- difficult for novice users compared to experts Relates to learnability and understandability

Does the notation invite mistakes High level for novice users of both notations Relates to learnability and understandability

Did tasks require a high demand of mental effort. High level for novice users of both notations Need to understand set theory and 1 st order logic Need to get familiar with mathematical symbols Need to get familiar with ASCII symbols Relates to learnability and understandability

Does the notation invite mistakes

whether the work-to-date can be checked at any time Dependent on the tool Both tools have option to save work till-date Shows error for dependencies Related to learnability and understandability

the ability to provide any extra information in means other than a formal syntax. Use English for comments Use ‘Pretty Print’ for indentation ASCII symbols to represent mathematical symbols

resistance to change High level of repetition viscosity Have to manually change name of variable No auto-update available in both tools Related to learnability and understandability

ability to view components easily/ ability to place components side by side

The Rodin tool is much more user-friendly, attractive and easy to use. Easier to learn the Event-B notation with Rodin Rodin provides good user manual Existing B tools are tedious

Thank You Q&A