JAIST Repository
https://dspace.jaist.ac.jp/Title

Software Architecture with Accountability andEvolvability

Author(s)Ochimizu, Koichiro

CitationIssue Date

2005‑03‑11

TypePresentation

Text version

publisher

URL

http://hdl.handle.net/10119/8276

RightsDescription

JAIST 21世紀COEシンポジウム2005「検証進化可能電子社会」 = JAIST 21st Century COE Symposium 2005
Verifiable and Evolvable e‑Society , 開催：2005年3月10日〜11日, 開催場所：石川ハイテク交流センター, Technical session 4 <Modelling andEvolution>

Japan Advanced Institute of Science and Technology

Prof. Katayama’s Motivation
Software Architecture withAccountability and Evolvability• Can you dependably leave your life to infrastructure
information system ？
• Modeling and Implementing e-Society by applying advanced technologies
in Computer Science.

Koichiro Ochimizu
School of Information Science, JAISTOur Society

JAIST 21st Century COE Symposium 2005.
“Verifiable and Evolvable e-Society”
March 11th, 2005
Social Infrastructure Information System

Dependability Requirements ofe-Society( Prof. Katayama’s Definition)

Model Driven Approach to Realize
Dependable e-Society

1. Correctness
Are the functions correct? （”Is my tax correctly calculated?”）
Are they consistent with laws?

2. Accountability

Our Society（Society（Laws, Social system,…
system,…）Is the information system built to be able to answer questions about it?
“Why my tax is correct?”

3. Security

Verification of Dependability
Requirements

No illegal data access, Privacy protected…

4. Fault Tolerance

Formal Specification S, Model M of Society

Can to tolerate accidents?

5. Evolvability

Our Societ

Could e-society system be changed
according to the change of society?

Correct Implementation ofthe model M
Social Infrastructere Information System

Social Infrastructure Information System

Dependability Requirements(Range of Consideration)

Proof of some desirable properties

tradeoff study

AccountabilitySecurity

Currently
Out of scope

Correctness

Our Approach

Evolvability

Administration
or education
system (Rules orregulations）
of University andLocal
Government

on dependability requirements

Specificationin laws or regulations
Specification with provendependability requirements

Architecture DesignandModel

Implementationof accountable and evolvable system

Fault Tolerance
Evolvable System with dependability

1Topics of Today(Preliminary Consideration)

Goal and Scope of Our Team• Proving Dependability Requirements of e-Society using Heavy
weight Ontology– Prof. Ikeda– Dr.Hayashi• Definition• Designing Evolvable and Accountable System using
Advanced Object-Oriented Technologies including
Feature/Aspect Oriented approach– Accountability– Evolvability– Prof. Ochimizu– Associate Prof. Suzuki– Dr. Fujieda– Dr. Hattori– Dr. Amano– Mr. Hayasaka ( PhD. Student)• Expected Tools for Model Implementation– Variation Point modeling of PL• Target Domains– Administration of Local Government– Education System of University

What are the Origin of Accountability

Stakeholders of Information System• Officers of Civil Services
System– What should we do to improve the welfare of the aged ?
– What kinds of regulation should be enacted?
– What is a role of Information System ?

• CitizensRegulations

User2005– How can we reduce the tax payment?
– What are the related regulations.
– What should we do to use the system ?
– Semantics: understanding of the real world (origin)– Languages: to express ones needs
special thanks to Mr. Kumagai.
This definition was obtained– Concerns to the Systemfrom the discussion with him

Ontology-aware Course Consulting System （Prof. Ikeda)

Civil Service

Grade Maintenance

Ontology-aware Guidance Generation (Semantics&Language)

e-Learning

e-Learning

Plan Consultinggoal
goal

Curriculum

Regulation

Plan Consulting

Rationale

goal

Modeling a student
who takes the class.
Design the classbased on the model

Class Design Support

Grade Maintenance

What parts should I modify ?

System Developer

Course Management System (CMS)• Which class should I take to achieve
my goal ?
• Does my plan satisfy the course
regulation?
• How should we change my plan?

goal

Does this system satisfy
dependability requirement ?

I want to know
the reasoningof the decision

Ontology-aware Course Consulting System (Prof. Ikeda)

Feature:Plan2004

Civil Service• Each stakeholder has own:

STUDENT

Evaluation of theclass based on thestudent model.

Knowledge•How the change of
regulation effects onthe students' plan
•How the course
design matches withstudents' needs•How well the course
works?

Curriculum

Regulation

Rationale

Knowledge

Curriculum Ontology

Class Design Support

FUCULTY
DESIGNER

Course Design Support

Curriculum Ontology

Check the Consistency
Provide GuidanceInfo.
fbased on ontology.

LECTURER•What should we teachto the students?
•How well the students
learned ?
•How the knowledge isuseful for students'
carrier?

SWANTypes of thestudents

LECTURER

Redesign support

Course Management System (CMS)

goalgoal

Are these laws
consistent ?

Grade Information+Semantic Interpretation ofthe grade information
based on the student
model and ontology.

•What should we teachto the students?
•How well the students
learned ?
•How the knowledge isuseful for students'
Rcarrier?
E

What types of students
have we succeeded infostering ?

2

Our Definition of Accountability

Software Engineering Approach• Various kinds of stakeholders can access the systembefore/after system development using their own
semantics and languages

Translation and loss of accessiblenesssoftwarerequirement

different semantics and languages
semantics
andconcerns

Civil Service

Civil Service
semantics
andconcerns

semantics
andconcerns

Citizensemantics
andconcerns

System Developer

Our Definition of Accountability• Various kinds of stakeholders can access the systembefore/after system development using their own
semantics and languages
different semantics and languages
semantics
andconcerns

Citizen

System Analyst

System Developer

semantics
andconcerns

semantics
andconcerns

Accountability• The system can answer the question from the stakeholder basedon their semantics using their languages
Accountability
Semantics

Civil Service

Languagesemantics
andconcerns

Concerns to the System

Citizen

SystemAnalyst/Developersemantics
andconcerns

Concerns of
Stakeholder type 1

Then We Can Define Evolvability• Maintaining the correspondence between stakeholders’concerns and components of the systemdifferent semantics and languages
semantics
andconcerns

Civil Service
semantics
andconcerns

Usersemantics
andconcerns

Concerns of…

Stakeholder type 2

Candidates for the Implementation• Evolution related issues– Applying Product Line Technology followingGomaa’s PLUS method– Variation points modeling on version ofregulations• Accountability related issues– Component Design based on accountability– Framework Design based on execution order ofcomponents

SystemAnalyst/Developer3

Variation Points Modeling

Structure and Type of Regulations• Regulations are managed by Change History

rule 32005– Like SCCS Delta
rule 2• Type of Regulations

2004
2003

rule 1– Rules– Workflows– Calculation

2005

2004 2003
Usecase Name: Explain Something

Name: check something

Reuse Category: Kernel

Type of functionality: mandatory
alternativeDescription
2005•

Input necessary data2004•

Check something

2003•Output it

Line numbers: 2
Description of functionality:
Apply rule1 in 2003, rule2 in 2004,
rule3 in 2005

clauseComponent Design(under consideration)

Conclusion (Research Plan)

Check something

2003

2004

2005

check something

check something

check something• Method and Language for Describing
Stakeholders’ Semantics and Concerns• Component Specification Language related toAccountability• Language for Variation Points Modeling• Framework Development• Dynamic Binding to the corresponding component• Component specification considering the proper units for accounting

Light Weight Ontology and Heavy Weight Ontology
for describing Semantics and Concerns• to remove GAPs

Component Specifications• For Accountability and Evolvability

different semantics and languages

different semantics and languages

semantics
andconcerns

semantics
andconcerns

Civil Service

Civil Service
semantics
andconcerns

semantics
andconcerns

User

Citizensemantics
andconcerns

SystemAnalyst/Developer

The necessary information
to make an answer may
not exist in the same world.

semantics
andconcerns

SystemAnalyst/Developer4