IWSFT2005 1 2005/11/08 - 10 A Layered Formal Specification of Contactless IC Card "FeliCa" Kyushu University (JAPAN) Xiaojing ZHANG, Yoichi OMORI and Keijiro.

Slides:



Advertisements
Similar presentations
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Advertisements

Ch 3: Unified Process CSCI 4320: Software Engineering.
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Revision Session 1.UML Overview 2.Detailed software design : operation specification, designing for re-use.
1 Introduction to Software Engineering Lecture 42 – Communication Skills.
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
Developed by Reneta Barneva, SUNY Fredonia Component Level Design.
1 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2002] January 26, 2006.
Software Product Line Architectures (SPLA) Nipun Shah
The Re-engineering and Reuse of Software
Software Development Concepts ITEC Software Development Software Development refers to all that is involved between the conception of the desired.
What is UML? What is UP? [Arlow and Neustadt, 2005] January 23, 2014
Systems Analysis and Design in a Changing World, Fifth Edition
Component Software: A New Software Engineering Course H. Conrad Cunningham, Yi Liu, Pallavi Tadepalli, and Mingxian Fu Software Architecture Research Group.
An Introduction to Software Architecture
OHTO -99 SOFTWARE ENGINEERING LECTURE 5 Today: - An overview to OO Analysis and OO Design - Introduction of Assignment 2.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 07. Review Architectural Representation – Using UML – Using ADL.
An Introduction to Design Patterns. Introduction Promote reuse. Use the experiences of software developers. A shared library/lingo used by developers.
4/2/03I-1 © 2001 T. Horton CS 494 Object-Oriented Analysis & Design Software Architecture and Design Readings: Ambler, Chap. 7 (Sections to start.
Ch:10 Component Level Design Unit 4. What is Component? A component is a modular building block for computer software Because components reside within.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Object Management Group (OMG) Specifies open standards for every aspect of distributed computing Multiplatform Model Driven Architecture (MDA)
Selected Topics in Software Engineering - Distributed Software Development.
L10 - April 12, 2006copyright Thomas Pole , all rights reserved 1 Lecture 10: Software Assets and Text: Ch. 8: Language Anatomy and Ch 9: Families.
UML Use Case Diagramming Guidelines. What is UML? The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
Modeling system requirements. Purpose of Models Models help an analyst clarify and refine a design. Models help simplify the complexity of information.
Designing Classes Prelude © 2015 Pearson Education, Inc., Upper Saddle River, NJ. All rights reserved. Data Structures and Abstractions with Java, 4e Frank.
Unit 2 Architectural Styles and Case Studies | Website for Students | VTU NOTES | QUESTION PAPERS | NEWS | RESULTS 1.
Gaudi software process Ralph Back CREST CREST: Center for Reliable Software Technology Åbo Akademi.
Operating Systems Structure what is the organizational principle?
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 11a: Component-Level Design Software Engineering: A Practitioner’s Approach, 6/e Chapter.
Dr D. Greer, Queens University Belfast )Chapter Six 1 Software Engineering Chapter Six Software Design Quality Learning Outcomes.
Software Engineering Zhang Shuang
UML Diagrams for Caradon developers Daniel DG Moth Core Development Group, Research Student University of Brighton, MSc Object Oriented Software Technology.
Software Engineering and Object-Oriented Design Topics: Solutions Modules Key Programming Issues Development Methods Object-Oriented Principles.
1 Software Design Lecture What’s Design It’s a representation of something that is to be built. i.e. design  implementation.
Exam 2 Review Software Engineering CS 561. Outline Requirements Development UML Class Diagrams Design Patterns Users, Usability, and User Interfaces Software.
RE-ENGINEERING AND DOMAIN ANALYSIS BY- NISHANTH TIRUVAIPATI.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
Architecture Analysis and Design Language: An Overview Drew Gardner.
CHAPTER 3 MODELING COMPONENT-LEVEL DESIGN.
November 7-11, 2005IWFST20051 A formal specification of entrance system using contactless IC card Tatsuo SUMIDA, Yoichi OMORI, and Keijiro ARAKI Graduate.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Presentation Layer (Graphical User Interface) AppGUI Logic Layer (Business Logic and data access) Network Discovery Device Information Extraction Network.
04 - OOD Intro.CSC4071 Software Design ‘Requirements’ defines –The goals the system needs to satisfy. ‘Specification’ defines –The externally-observable.
2000 Research Overview Dr. Kim Mens Programming Technology Lab Vrije Universiteit Brussel.
Copyright © 2010 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Starting Out with Programming Logic & Design Second Edition by Tony Gaddis.
Toward product architecture oriented requirements analysis for product line development in systems engineering Kei Kurakawa Nara Institute of Science and.
Software Design and Architecture Muhammad Nasir Software Architecture Documentation
Computer Systems Architecture Edited by Original lecture by Ian Sunley Areas: Computer users Basic topics What is a computer?
11 Systems Analysis and Design in a Changing World, Fifth Edition.
The PLA Model: On the Combination of Product-Line Analyses 강태준.
Topic 4: Distributed Objects Dr. Ayman Srour Faculty of Applied Engineering and Urban Planning University of Palestine.
Elaboration popo.
CS 325: Software Engineering
What is UML? What is UP? [Arlow and Neustadt, 2005] October 5, 2017
Software Engineering: A Practitioner’s Approach, 6/e Chapter 11 Component-Level Design copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
final registration seminar presentation
Object-Orientated Programming
Protocols and Layering
The Object Oriented Approach to Design
INFS 6225 – Object-Oriented Systems Analysis & Design
NTNU Dept of Telematics and SINTEF Telecom and Informatics, Norway
Analysis models and design models
Software Design Lecture : 14.
An Introduction to Software Architecture
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Chapter 10 – Component-Level Design
Presentation transcript:

IWSFT /11/ A Layered Formal Specification of Contactless IC Card "FeliCa" Kyushu University (JAPAN) Xiaojing ZHANG, Yoichi OMORI and Keijiro ARAKI Background  Consumer embedded systems Product family development Short interval between releases Similar service with variable platform  Software productline Extracts commonalities of a series of products Manage and improve core asset Application Engineering Domain Engineering Management Core Asset

IWSFT /11/ Feedback process from product to core asset is complicate  Product is complicatedly mixed  Which part should we feedback to the core asset? Formal specifications help clarifying commonalities and differences Purpose  Propose a layered architecture of specification To improve efficiency of the feedback process Approach  Separate descriptions between logical and physical level by hardware dependency  Apply to Contactless IC card "FeliCa“

IWSFT /11/ Core Asset Software Product feedback specification in natural language Physical Layer (variable components) Logical Layer (common components) + reuse Layered Architecture Figure1: Concept Of Research separation

IWSFT /11/ Method  Layered architecture Logical layer  preserved data with logical meaning  Operations derived from design purpose Physical layer  Physical structure of data  Algorithms or procedure of operations 1. Divide natural language specification into several modules 2. separate each module into Logical Layer and Physical Layer by principles above 3. Draw class diagrams in UML, and then materialize them to VDM++ 4. Inheritance are used temporarily Gathering only physical descriptions can’t make the layer complete To make up shortage; To indicate correspondency

IWSFT /11/ Case Study: FeliCa Card  Divide card into file system and commands File System – data structure on card memory  Data hold on the memory area Operations access the data  Type of the data Operations about types Commands – protocol between card and R/W  Command/Response packet Command purpose  Structure of packet Procedure of command’s operation Future Works  Improve and formalize the method How to express both independency and correspondency? Logical Layer Class Physical Layer Class Logical Layer Class Physical Layer Class

IWSFT /11/ Class of Logical Layer File System inheritance Figure2: Class Diagram Of Commands (partial) Class of Physical Layer Module: Command Polling