Counter

COUNTER3505From 2012/10/25

Journal

2016/08/17

WOCS 2016 December 12, Call For Paper

Tweet ThisSend to Facebook | by kaizen
Call for Papers
JAXA/IPA 14th International Workshop on Critical Software Systems
(WOCS2 2016 December)  
Japanese version is here

Dates: Dec.  12(Mon.)*1 - Dec. 13 (Tue.), 2016
Place: Japan
Sponsored by JAXA and IPA

*1 These presentation sessions will open on the afternoon of Dec. 12(Mon), 2016.
Special lecture will open on the morning of Dec. 12(Tue.), 2016
Keynoteandinvited talks will open on the morning of Dec. 13(Tue.), 2016

Thema:  Look, Learn, Study and Think for the better future.

Increasingly large and complex critical systems provide unique
challenges to the researchers and practitioners in critical software
systems.
The goal of this international workshop is to provide a forum for
researchers and practitioners to discuss to not only the system which
fused for safety, but also all aspects of security, dependability,
reliability and quality for critical software systems.
All aspects of design, theory, product design/analysis,
process/practice, realization and experiences of the chritical software
system are of interest.

Topics of interest include, but are not limited to:

     Operational safety/ Function safety
     Maintenance safety and/or security system
     Model driven architecture
     Test driven design
     Quality in use/ Intended use
     Hazard analysis/ Design review
     Quantitative measure, predicting and management
     Mathematical/ Formal method
     Standardization for critical software system
     Training and Skill for engineer/operator
     Process/ Practice for critical software systems
     Case of Failure/ Success
     Tools and Methods for critical software systems

Submission Guidelines

To submit abstract, send the file (at most 8 pages long including
figures and references in the submission format below. describing
original research by August 2, 2016 in Text, PDF or MS Word 97/2003
format electronically via the mail address 14wocs2 at keiso-comm.com
(please change “at” to “@”)

All papers will be reviewed.
Notification of authors: August 31, 2016
Camera-ready presentation: November 1, 2016.
The proceedings for workshops will be published web only.
After workshops, IPA/SEC journal will be published as regular papers or
short reports according to submission papers.

Best presentation will be awarded at the end of sessions.

Submission Format
Author
     Name:
     Organization:
     Section:
     Address:
     TEL:
        FAX:
     E-Mail:
        twitter:

Co-author (if any)

Name:          organization:
Name:          organization:
Name:          organization:
Name:          organization:

Abstract

     Title:
     Keywords; (3 to 5)
     Key point
     Audience
     Abstract: (Over 200 words, please include figure or table, and references and )

(1) back grounds
(2) issue
(3) proposal ( idea or direction)
(4) result
(5) references (more than 1)
(6) Spelled out abbreviations (if any)

---
Partners       
INCOSE Japan Chapter
Software Engineering Method and Theory(SMAT), Japan
NPO Association of Software Test Engineering (ASTER)
NPO Society of Embedded Software Skill Acquisition for Managers and Engineers(SESSAME)
NPO TOPPERS Project
Connected Consumer Device Security Council(CCDS)
Dependability Engineering for Open Systems(DEOS)
Embedded Systems Innovation Council(ESIC)
Japan Automobile Research Institute (JARI)
Japan Embedded System Technology (JASA)
Union of Japanese Scientists and Engineers (JUSE)
System Assuarance Association
System Engineering Research Association(SERA)
Skills Management Association (SMA)
Smart System Verification and Validation Technology Association (SVA)
Control System Security Center
Automotive Embedded System Industry Forum (ASIF)
Association of System Documentation Quality(ASDoQ)
Japan SPI Consortium (JASPIC)
Nippon SPICE Network (NSPICE)
Software Engineers Association (SEA)
Yokohama Research Park(YRP)


Committee     
◆Chairpersons
Dr. Kiichiro Tamaru, SEC/IPA
Mr. Naoki Ishihama, JEDI/JAXA
◆Program Chair
Dr. Kiyoshi Ogawa(Nagoya Municipal Industrial Research Institute)
◆Program Committee
Dr. Daichi Mizuguchi(Atelier)
Dr. Hideto Ogasawara(Toshiba)
Dr. Hironori Washizaki(Waseda Univ.)
Dr. Seiichi Shin(Univ. ofElectro-Communications)
Dr. Seikou Shirasaka(Keio Univ.)
Dr. Taro Kurita(Sony)
Dr. Yasuharu Nishi(Univ. of Electro-Communications)
Dr. Yutaka Matsubara(Nagoya Univ.)
Mr. Fumiaki Kono(Advics)
Mr. Haruhiko Urokohara(U'eyes Design)
Mr. Hiroaki Sakai(Fujitsu)
Mr. Hiroshi Monden(JASA)
Mr. Hisayoshi Adachi(Denso)
Mr. Katsutoshi Shintani(IPA)
Mr. Kazunari Tabuchi(Biz3)
Mr. Nobuyasu Suzumura(Aishin Comcruise)
Mr. Osamu Inagaki(Tokai Rika)
Mr. Ryo Sano(Nissan)
Mr. Satoshi Fushimi(JISA)
Mr. Susumu Sasabe(JUSE)
Mr. Tsutomu Kojima(DNV)
Mr. Yasutaka Michiura(JAMMS)
Mr. Yoshikazu Hayashi(SRA)
Mr. Yukihiko Akasaka(NTTData)
17:31 | Impressed! | Voted(0) | Comment(0)
2012/10/25

Rewriting a Book Review

Tweet ThisSend to Facebook | by kaizen
I am writing some book reviews at amazon.com.
Now I am rewriting some book review, because any sentences are not good.

Eiffel


The review of the Eiffel Book was,   
"Eiffel is known the tower in Paris, France.
This Eiffel is a Language born in France that can support .NET framework.
Eiffel can express specifications and constraints.
I first read the book by Japanese translation."

The last sentence rewrite like this,
"I first read the book in Japanese translation."

Non native writer may not choice a correct preposition or an correct adverb. 

Any other questions and opinions, please comment this article.

<I spent writing this article. I will gradually improve this.>

BTW, 5 years ago, I decided to post 100 book review.
Now it is cleared. The quantity is full but quality is little poor.
So I rewrite some articles using translate.google.com, machine translation.

1. I input English article to translate to Japanese.
1.1 If Japanese translation is good, then I input the japanese translated article to translate to English.
2. If English translation is good, then I finish the check.
1.2 If Japanese translation is not good, then I rewrite a Japanese article and input it to translate to English.
1.2.1 If English translation is good, then I rewire the article.
1.2.2 If English Translation is not good, I rewire a Japanese article and input it to translate to English.

and so on.

10:14 | Impressed! | Voted(0) | Comment(0)