<br><font size=2 face="sans-serif"><b>Hello, "Sorry for Multiple
Copies" "PLEASE DISRIBUTE To Your Mailing Lists" Thank
you. Cheers, M. Fayad</b></font>
<br><font size=2 face="sans-serif">________________________________</font>
<br>
<br><font size=2 face="sans-serif">The First International Workshop on
Patterns Languages: </font>
<br><font size=2 face="sans-serif">Addressing Challenges</font>
<br>
<br>
<br><font size=2 face="sans-serif">PLAC 2007</font>
<br>
<br><font size=2 face="sans-serif">Call for Papers</font>
<br>
<br><font size=2 face="sans-serif">Montréal, Canada, October 21,
2007</font>
<br><font size=2 face="sans-serif"> (in conjunction with OOPSLA 2007)</font>
<br>
<br><font size=2 face="sans-serif">http://www.oopsla.org/oopsla2007 (OOPSLA
2007 Link) </font>
<br><font size=2 face="sans-serif">http://www.oopsla.org/oopsla2007/index.php?page=sub/&id=150
(Workshop Link 1)</font>
<br><font size=2 face="sans-serif">http://www.engr.sjsu.edu/~fayad/workshops/PLAC07
(Workshop Link 2)</font>
<br><font size=2 face="sans-serif">http://www.vrlsoft.com/workshops/PLAC07
(Workshop Link 3)</font>
<br>
<br><font size=2 face="sans-serif">INTRODUCTION</font>
<br>
<br><font size=2 face="sans-serif">A pattern language consists of a cascade
or hierarchy of parts, linked closely together by patterns, which solve
generically recurring problems that are associated with the parts. Each
pattern has a title, and collectively the titles form a language for design
[1]. Pattern Languages are simply a collection of interrelated patterns
[2]. These interrelated patterns are combined in any way and combination
to create new environments, where practitioners can solve context-specific
problems. Precisely, the concept of pattern languages has invaded
over into the software engineering field, to describe prior experiences
and the processes that stem from them, in a very simple language, where
patterns are tactfully woven as a whole, and can be combined in any manner
to solve a particular and complex problem. Yet, this process is still
done in an ad-hoc manner and is not straightforward enough, to ease and
speed up the software development process. </font>
<br>
<br><font size=2 face="sans-serif">Thus, this workshop is driven forward
by three main questions. First, how can we classify, develop, and utilize
analysis and design patterns together towards the path of a problem resolution?
Second, what is the “behind-the-“ language that guides the sewing of
patterns together as a whole? And third, how can we overcome and face challenges,
other than patterns composition problems (patterns traceability, etc.)
that can hinder the development of a system of patterns? The inherent inability
to answer these questions detrimentally impacts the understanding of how
to put patterns in real practice, and will therefore make software
patterns’ use more complex than it should.</font>
<br>
<br>
<br><font size=2 face="sans-serif">OBJECTIVE AND MOTIVATION</font>
<br>
<br><font size=2 face="sans-serif">Building high quality systems is not
an easy exercise, specifically when several factors can undermine their
quality success, such as cost, time, and lack of systematic approaches.
The potential promise of using software patterns in software development
to deal with these aforementioned obstacles, has led software practitioners
to steadfastly believe in the power of pattern languages, as the means
for constructing complex systems in a constrained environment. </font>
<br><font size=2 face="sans-serif"> </font>
<br><font size=2 face="sans-serif">Software Patterns, along with Pattern
Languages, have recently attracted software practitioners for more than
a decade. They have seen software patterns and pattern languages as really
promising techniques that ease and speed up their software development
[2, 3, 4, and 5]. However, developing robust software patterns and pattern
languages has not reached the expected ease and flexibility it should have
been, when dealing with determined problems; instead, they construct models
that specifically lack some essential qualities that diminish the overall
quality of the system rather than improving it [6]. </font>
<br><font size=2 face="sans-serif"> </font>
<br><font size=2 face="sans-serif">The concept of Pattern Languages [3,
7, 8, and 9] is spilling over into the software engineering field, to highlight
software development’s prior experiences or best practices, using a coherent
language that can be used for both discussing about a particular problem
and also in creating new environments from the patterns it conveys.
This language works by connecting a collection of patterns, as if they
were in a detailed, narrated story. Each of the patterns in the collection
is an insightful and a novel way to manage or solve a set of recurrent
problems in a particular context [2, 3, and 5]. As a whole, they make clearly
visible both the knowledge that is pertinent to a particular domain, and
the solutions for a set of recurrent problems. </font>
<br>
<br><font size=2 face="sans-serif">Pattern languages have emerged as a
promising classification technique and in providing ways to build frameworks.
However, there area number of problems [10], such as:</font>
<br>
<br><font size=2 face="sans-serif">1. Context’s
missing indicators/guidelines for in-context patterns selection within
the pattern language.</font>
<br><font size=2 face="sans-serif">2. Classifications
of patterns’ rationale within the pattern language structure is also missing.</font>
<br><font size=2 face="sans-serif">3. Traceability
is lost, especially when dealing with deeper levels of pattern language
implementation.</font>
<br><font size=2 face="sans-serif">4. No
systematic way for compositing these patterns, similar or different, to
build software architectures</font>
<br><font size=2 face="sans-serif">5. There
is a loss of generality in traditional pattern languages.</font>
<br><font size=2 face="sans-serif">6. Pattern
languages struggles and conflicts in providing full software maintainability
and stability.</font>
<br><font size=2 face="sans-serif">7. How
pattern languages deal with the problem they address is neither straightforward
nor easy.</font>
<br><font size=2 face="sans-serif">8. There
is no set classification in pattern languages.</font>
<br><font size=2 face="sans-serif">9. Pattern
languages don’t distinguish between associate and remote knowledge.</font>
<br>
<br><font size=2 face="sans-serif">WORKSHOP CHALLENGES</font>
<br>
<br><font size=2 face="sans-serif">The workshop will address pattern languages’
challenges and debate several issues related to the following questions.
We want researchers, framework developers, and application developers
to discuss and debate the following questions related to: </font>
<br>
<br><font size=2 face="sans-serif">I. Pattern
Languages Creation and Development</font>
<br><font size=2 face="sans-serif">a. Leaving
career experience claim on the side, can you show how to create and develop
pattern languages?</font>
<br><font size=2 face="sans-serif">b. What
are the bases of creating pattern Languages? </font>
<br><font size=2 face="sans-serif">c. Are
there guidelines, methodologies, and/or processes for pattern language
creations and developments?</font>
<br><font size=2 face="sans-serif">d. Would
you show an example or two of systematic and non-systematic pattern languages?</font>
<br><font size=2 face="sans-serif">e. What
is the starting point of any pattern language?</font>
<br><font size=2 face="sans-serif">f. What
are the components of any pattern language?</font>
<br><font size=2 face="sans-serif">g. What
kind of patterns that appear in pattern languages?</font>
<br>
<br><font size=2 face="sans-serif">II. Pattern
Languages Selection Process: </font>
<br><font size=2 face="sans-serif">a. How
does one select analysis and design patterns to create a pattern language?</font>
<br><font size=2 face="sans-serif">b. What
is the basis for selecting these patterns into the pattern language? </font>
<br><font size=2 face="sans-serif">c. If
someone would like to build a system from patterns, how does he/she select
patterns from the pattern language?</font>
<br><font size=2 face="sans-serif">d. What
kind of patterns should one select to build a system from patterns?</font>
<br><font size=2 face="sans-serif">e. Is
there a guideline for the selection process from a pattern language?</font>
<br>
<br><font size=2 face="sans-serif">III. Patterns
Languages Composition</font>
<br><font size=2 face="sans-serif">a. How
does one integrate the selected pattern languages to build any given system?
Or how does one compose any system from one or more pattern languages?
</font>
<br><font size=2 face="sans-serif">b. What
are the various claims related to pattern languages composition? Are they
really true?</font>
<br><font size=2 face="sans-serif">c. Are
there any guidelines or techniques for pattern languages composition? Would
you illustrate how to use them?</font>
<br>
<br><font size=2 face="sans-serif">IV. System
of Patterns and General Reuse</font>
<br><font size=2 face="sans-serif">a. What
do we mean, when we say “systems of patterns”?</font>
<br><font size=2 face="sans-serif">b. Are
the various claims related to building any system from pattern languages
reasonable?</font>
<br><font size=2 face="sans-serif">c. How
to develop pattern repositories and catalogs, from which pattern languages
can be retrieved and reused?</font>
<br><font size=2 face="sans-serif">d. Are
there any automated approaches for patterns using languages mining and
integration?</font>
<br><font size=2 face="sans-serif">e. What
other concepts will help assist build any system from pattern languages?</font>
<br><font size=2 face="sans-serif">f. Can
patterns within a given pattern language appear in other remote pattern
languages?</font>
<br><font size=2 face="sans-serif">g. Is
it possible to create many architectures from a given pattern languages?
How many architectures?</font>
<br><font size=2 face="sans-serif">h. Can
we measure the ROI from the pattern language of a given domain?</font>
<br><font size=2 face="sans-serif">i. Is
it possible to measure or perform cost estimation using pattern languages?</font>
<br><font size=2 face="sans-serif">j. It
is possible to insert the quality factors with the pattern languages? How?
</font>
<br>
<br><font size=2 face="sans-serif">V. Impacts</font>
<br><font size=2 face="sans-serif">a. What
is the impact of software stability on the above mentioned challenges and
software quality factors?</font>
<br>
<br><font size=2 face="sans-serif">More information will be available at:</font>
<br><font size=2 face="sans-serif">http://www.oopsla.org/oopsla2007 (OOPSLA
2007 Link) </font>
<br><font size=2 face="sans-serif">http://www.oopsla.org/oopsla2007/index.php?page=sub/&id=150
(Workshop Link 1)</font>
<br><font size=2 face="sans-serif">http://www.engr.sjsu.edu/~fayad/workshops/PLAC07
(Workshop Link 2)</font>
<br><font size=2 face="sans-serif">http://www.vrlsoft.com/workshops/PLAC07
(Workshop Link 3)</font>
<br>
<br>
<br><font size=2 face="sans-serif">PAPER FORMAT AND SUBMISSIONS</font>
<br>
<br><font size=2 face="sans-serif">Developers and programmers who are interested
in participating in the workshop, are requested to submit a short position
paper (3-5 pages), or regular workshop paper (limited to 6-15 pages, double
spaced, including figures) representing views and experiences relevant
to the given discussion topic. The title page must include a maximum 150-word
abstract, five keywords, full mailing address, e-mail address, phone number,
fax number, and a designated contact author. Workshop papers will be selected
depending on their originality, quality and relevance to the workshop.
All submitted papers will also be evaluated according to its originality,
significance, correctness, presentation and relevance. Papers should be
submitted electronically at:</font>
<br><font size=2 face="sans-serif"> http://www.oopsla.org/oopsla2007/index.php?page=sub/&id=150.
Please follow the instructions given on the web page. Camera Ready
manuscripts must be submitted following ACM SIGPLAN conference proceedings
style and guidelines. We also encourage authors to present novel and fresh
ideas, critiques of existing work, and practical studies. </font>
<br>
<br><font size=2 face="sans-serif">Each accepted workshop paper must be
presented in the person, either by the author or one of the co-authors.
To foster and promote lively discussions, authors are encouraged
to present open questions and one or two main statements for discussion
at the workshop. Submissions must be made either in MS-Word or RTF
formats (please, DO NOT compress files).</font>
<br>
<br><font size=2 face="sans-serif">Depending on the total number and spread
of contributions, the scope may be narrowed down to ensure an effective
communication and information sharing session. Accepted position papers
will be distributed to the participants, before the workshop and made generally
available through the WWW and FTP. Accepted papers will be published
in the Workshop Proceedings. At least one of the authors of each accepted
paper must register as a full delegate in the workshop. Selected
papers will be published in the online Journal of International Journal
Of Patterns (IJOP) www.ijop.org. </font>
<br>
<br><font size=2 face="sans-serif">WORKSHOP PARTICIPATION</font>
<br>
<br><font size=2 face="sans-serif">People who are interested in participating
in the workshop, without making any submissions are requested to fill out
the participation form and e-mail to any of the workshop chairs. </font>
<br><font size=2 face="sans-serif">-------------------------------------------------</font>
<br><font size=2 face="sans-serif">PARTICIPATION FORM:</font>
<br><font size=2 face="sans-serif">Name and Affiliation:</font>
<br><font size=2 face="sans-serif">Position: </font>
<br><font size=2 face="sans-serif">Address: </font>
<br><font size=2 face="sans-serif">E-mail:</font>
<br><font size=2 face="sans-serif">URL:</font>
<br><font size=2 face="sans-serif">Areas of interest:</font>
<br><font size=2 face="sans-serif">Reasons for Participating?</font>
<br><font size=2 face="sans-serif">-------------------------------------------------</font>
<br><font size=2 face="sans-serif">Please note that registration is mandatory,
in order to participate in the workshop. An early registration discount
is available for all desired participants. An overhead projector
and a flipchart will be available to all participants. </font>
<br>
<br><font size=2 face="sans-serif">For more information please visit any
of the following websites:</font>
<br>
<br><font size=2 face="sans-serif">http://www.oopsla.org/oopsla2007 (OOPSLA
2007 Link) </font>
<br><font size=2 face="sans-serif">http://www.oopsla.org/oopsla2007/index.php?page=sub/&id=150
(Workshop Link 1)</font>
<br><font size=2 face="sans-serif">http://www.engr.sjsu.edu/~fayad/workshops/PLAC07
(Workshop Link 2)</font>
<br><font size=2 face="sans-serif">http://www.vrlsoft.com/workshops/PLAC07
(Workshop Link 3)</font>
<br>
<br><font size=2 face="sans-serif">You may also contact the organizers,
either by e mail or by phone.</font>
<br>
<br><font size=2 face="sans-serif">PROPOSED AGENDA</font>
<br>
<br><font size=2 face="sans-serif">1. Welcome and introduction of participants.
The organizers will first provide a short overview of all open issues
and also of the main arguments arising out of the position papers. (Estimated
time: 20-30 minutes)</font>
<br>
<br><font size=2 face="sans-serif">2. Selected authors (who’ll be representing
the main trends) will be allotted 20 minutes to explain how their
position relates to other positions, and what each one of them sees as
the three major issues. We expect about 5-10 position papers in this session.
(Estimated time: 120-130 minutes) </font>
<br>
<br><font size=2 face="sans-serif">3. The organizers will propose an identification
process of the major issues, and the participants will then discuss, choose
and select what they perceive are the hottest issues to be examined. (Estimated
time: 10-15 minutes)</font>
<br>
<br><font size=2 face="sans-serif">4. The participants will work for 70-95
minutes in small groups, with a designated moderator assigned for each
group. The groups will individually deal with two different, identified
hot issues and will produce a summary note in the form of points and counterpoints,
showing either how several views are irreducibly opposed or how they are
complementary. The total number of groups will depend mainly on the
number of participants and issues selected; ideally there should be 3-5
p people in each group. (Estimated time: 60-70 minutes) </font>
<br>
<br><font size=2 face="sans-serif">5. Each group will be given 10-15 minutes
to present its findings and inferences to the workshop. A closing
discussion will soon follow. The workshop report will be composed on the
basis of these findings, and will include a clear cut agenda for future
exploration and cooperation; this will be made available through the WWW
and FTP. (Estimated time: 50-60 minutes for five teams) </font>
<br>
<br><font size=2 face="sans-serif">(Total estimated time: 285-315 minutes,
i.e. about five hours +/- 15 minutes; lunch and breaks are not included.)
</font>
<br>
<br><font size=2 face="sans-serif">IMPORTANT DATES</font>
<br>
<br><font size=2 face="sans-serif">Submission deadline
September 14, 2007</font>
<br><font size=2 face="sans-serif">Acceptance notification
September 30,
2007</font>
<br><font size=2 face="sans-serif">Camera-ready paper due
October 10, 2007</font>
<br><font size=2 face="sans-serif">Workshop date:
October 21, 2007</font>
<br><font size=2 face="sans-serif">Conference begins:
October 21, 2007</font>
<br>
<br><font size=2 face="sans-serif">ORGANIZERS</font>
<br>
<br>
<br><font size=2 face="sans-serif">DR. M.E. FAYAD (CHAIR)</font>
<br><font size=2 face="sans-serif">Professor of Computer Engineering</font>
<br><font size=2 face="sans-serif">Computer Engineering Dept., College
of Engineering</font>
<br><font size=2 face="sans-serif">San José State University</font>
<br><font size=2 face="sans-serif">One Washington Square, San José, CA
95192-0180</font>
<br><font size=2 face="sans-serif">Ph: (408) 924-7364, Fax: (408) 924-4153</font>
<br><font size=2 face="sans-serif">E-mail: m.fayad@sjsu.edu, mefayad@gmail.com</font>
<br><font size=2 face="sans-serif">URL: http://www.engr.sjsu.edu/fayad</font>
<br>
<br><font size=2 face="sans-serif">DR. CHIA-CHU CHIANG (CO-CHAIR)</font>
<br><font size=2 face="sans-serif">University of Arkansas at Little Rock</font>
<br><font size=2 face="sans-serif">Department of Computer Science, 2801
South University Ave.,</font>
<br><font size=2 face="sans-serif">Little Rock, Arkansas 72204-1099, USA</font>
<br><font size=2 face="sans-serif">Ph: (501) 569-8142</font>
<br><font size=2 face="sans-serif">E-mail: cxchiang@ualr.edu</font>
<br><font size=2 face="sans-serif">URL: http://pandora.compsci.ualr.edu/cxchiang/index.html</font>
<br>
<br><font size=2 face="sans-serif">HUÁSCAR A. SÁNCHEZ (CO-CHAIR) </font>
<br><font size=2 face="sans-serif">Independent Consultant</font>
<br><font size=2 face="sans-serif">22 Marcin Hill, Burnsville MN 55337</font>
<br><font size=2 face="sans-serif">Ph: 952-223-4060</font>
<br><font size=2 face="sans-serif">E-Mail: huascar.sanchez@hsanchez.net</font>
<br><font size=2 face="sans-serif">URL: www.hsanchez.net</font>
<br>
<br><font size=2 face="sans-serif">DR. PABLO CHACIN (CO-CHAIR) </font>
<br><font size=2 face="sans-serif">Technical University of Catalonya</font>
<br><font size=2 face="sans-serif">Departamento de Arquitectura de Computadores</font>
<br><font size=2 face="sans-serif">UPC Campus Nord, C6-002</font>
<br><font size=2 face="sans-serif">Jordi Girona 1-3</font>
<br><font size=2 face="sans-serif">Barcelona 08034, Spain</font>
<br><font size=2 face="sans-serif">Ph: +34 93 401 10 55</font>
<br><font size=2 face="sans-serif">E-mail: pchacin@ac.upc.edu</font>
<br><font size=2 face="sans-serif">URL: http://personals.ac.upc.edu/pchacin</font>
<br>
<br><font size=2 face="sans-serif">DR. SRINI RAMASWAMY (CO-CHAIR)</font>
<br><font size=2 face="sans-serif">Department of Computer Science</font>
<br><font size=2 face="sans-serif">Dickinson Hall Suite 515</font>
<br><font size=2 face="sans-serif">University of Arkansas at Little Rock</font>
<br><font size=2 face="sans-serif">2801 S. University Avenue, Little Rock,
AR 72204 </font>
<br><font size=2 face="sans-serif">Ph: (501)-569-8134</font>
<br><font size=2 face="sans-serif">Fax: (501)-569-8144</font>
<br><font size=2 face="sans-serif">E-mail: sxramaswamy@ualr.edu</font>
<br><font size=2 face="sans-serif">URL: http://pandora.compsci.ualr.edu/srini/
</font>
<br>
<br><font size=2 face="sans-serif">DR. ARTURO SÁNCHEZ-RUÍZ, (CO-CHAIR)
</font>
<br><font size=2 face="sans-serif">University of North Florida, USA</font>
<br><font size=2 face="sans-serif">School of Computing</font>
<br><font size=2 face="sans-serif">University of North Florida</font>
<br><font size=2 face="sans-serif">4567 St Johns Bluff Rd. S.</font>
<br><font size=2 face="sans-serif">Jacksonville, FL 32224-2669</font>
<br><font size=2 face="sans-serif">Ph: 904-620-1314</font>
<br><font size=2 face="sans-serif">Fax: 904-620-2988</font>
<br><font size=2 face="sans-serif">E-mail: asanchez@unf.edu, Arturo@acm.org</font>
<br><font size=2 face="sans-serif">URL: http://www.unf.edu/~asanchez</font>
<br>
<br><font size=2 face="sans-serif">DR. SELMIN NURCAN (CO-CHAIR) </font>
<br><font size=2 face="sans-serif">Maître de Conférences</font>
<br><font size=2 face="sans-serif">Centre de Recherche en Informatique,
France </font>
<br><font size=2 face="sans-serif">Université Paris 1 - Panthéon - Sorbonne</font>
<br><font size=2 face="sans-serif">Centre de Recherche en Informatique</font>
<br><font size=2 face="sans-serif">90, rue de Tolbiac 75634 Paris cedex
13 FRANCE</font>
<br><font size=2 face="sans-serif">Ph: 33 - 1 44 07 86 34
</font>
<br><font size=2 face="sans-serif">Fax : 33 - 1 44 07 89 54</font>
<br><font size=2 face="sans-serif">E-mail: nurcan@univ-paris1.fr</font>
<br><font size=2 face="sans-serif">URL: http://crinfo.univ-paris1.fr/users/nurcan</font>
<br>
<br><font size=2 face="sans-serif">DR. A. KANNAMMAL SAMPATHKUMAR (CO-CHAIR)
</font>
<br><font size=2 face="sans-serif">Coimbatore Institute of Technology,
TamilNadu, India</font>
<br><font size=2 face="sans-serif">34/43, 14th Cross, </font>
<br><font size=2 face="sans-serif">Thirumagal Nagar, Peelamedu Pudur, </font>
<br><font size=2 face="sans-serif">Coimbatore 641 004, TN, INDIA.</font>
<br><font size=2 face="sans-serif">Ph: 00 91 422 2574071</font>
<br><font size=2 face="sans-serif">E-mail: kannaphd@yahoo.co.in</font>
<br><font size=2 face="sans-serif">URL: http://www.citindia.com/Computer_Kannammal.htm</font>
<br>
<br><font size=2 face="sans-serif">PROGRAM COMMITTEE</font>
<br>
<br><font size=2 face="sans-serif">Rami Bahsoon, Aston University in Birmingham,
Birmingham, United Kingdom</font>
<br><font size=2 face="sans-serif">Javier Bilbao, University of the Basque
Country, Spain</font>
<br><font size=2 face="sans-serif">Rafael Capilla, Universidad Rey Juan
Carlos, Madrid, Spain</font>
<br><font size=2 face="sans-serif">Rogerio Atem de Carvalho, Federal
Center for Technological Education of Campos, Brazil</font>
<br><font size=2 face="sans-serif">Pablo Chacin, Technical University
of Catalonya, Barcelona, Spain</font>
<br><font size=2 face="sans-serif">Chia-Chu Chiang, University of Arkansas,
Little Rock, USA</font>
<br><font size=2 face="sans-serif">Bernard Coulette, University of
Toulouse II, France</font>
<br><font size=2 face="sans-serif">Sergiu Dascalu, University of Nevada,
Reno, USA</font>
<br><font size=2 face="sans-serif">Sergio de Cesare, Brunel University,
West London, United Kingdom</font>
<br><font size=2 face="sans-serif">Jurgen Dix, Clausthal University of
Technology, Germany</font>
<br><font size=2 face="sans-serif">M.E. Fayad, San Jose State University
& vrlSoft, Inc., Silicon Valley, USA </font>
<br><font size=2 face="sans-serif">Giancarlo Fortino, University of Calabria,
Italy </font>
<br><font size=2 face="sans-serif">João Miguel Fernandes, Universidade
do Minho, Braga, Portugal</font>
<br><font size=2 face="sans-serif">Maria Joao Ferreira, Universidade Portucalense,
PORTO, Portugal</font>
<br><font size=2 face="sans-serif">Rosario Girardi, Federal University
of Maranhão, São Luís, Brasil</font>
<br><font size=2 face="sans-serif">Yann-Gaël Guéhéneuc, Université de Montréal,
Canada</font>
<br><font size=2 face="sans-serif">Pilar Herrero, Universidad Politécnica
de Madrid, Spain</font>
<br><font size=2 face="sans-serif">Hoda Hosny, The American University
in Cairo, Egypt</font>
<br><font size=2 face="sans-serif">Lise Hvatum, Schulmberger, Taxes, USA</font>
<br><font size=2 face="sans-serif">Dong, Jing, University of Texas at Dallas,
USA</font>
<br><font size=2 face="sans-serif">A. Kannammal, Coimbatore Institute of
Technology, TamilNadu, India</font>
<br><font size=2 face="sans-serif">Mohamed-Khireddine Kholladi, University
of Constantine, France</font>
<br><font size=2 face="sans-serif">Dae-Kyoo Kim, Oakland University, USA</font>
<br><font size=2 face="sans-serif">Jianzhi Li, De Montfort University,
United Kingdom</font>
<br><font size=2 face="sans-serif">Jing Liu, East China Normal University,
Shanghai, China</font>
<br><font size=2 face="sans-serif">Ricardo J. Machado, Universidade do
Minho, Guimaraes, Portugal</font>
<br><font size=2 face="sans-serif">Aime Mokhoo Mbobi, Ecole Supérieure
d'Electricité, France</font>
<br><font size=2 face="sans-serif">Supratik Mukhopadhyay, Utah State University,
USA </font>
<br><font size=2 face="sans-serif">Selmin Nurcan, Université Paris 1, France</font>
<br><font size=2 face="sans-serif">Flavio Oquendo, University of South
Brittany, France</font>
<br><font size=2 face="sans-serif">Toacy Cavalcante de Oliveira, Pontifical
Catholic University of Rio Grande do Sul, Brazil</font>
<br><font size=2 face="sans-serif">Michael Oudshoorn, Montana State
University, USA</font>
<br><font size=2 face="sans-serif">Shushma Patel, London South Bank University,
United Kingdom</font>
<br><font size=2 face="sans-serif">Loris Penserini, ITC-IRST, Automated
Reasoning Systems, Italy</font>
<br><font size=2 face="sans-serif">Agostino Poggi, University of
Parma, Italy</font>
<br><font size=2 face="sans-serif">Srini Ramaswamy, University of Arkansas
at Little Rock, USA </font>
<br><font size=2 face="sans-serif">Philippe Roose, Laboratoire d'Informatique
de l'Université de Pau et des Pays de l'Adour, France</font>
<br><font size=3 color=#006000 face="Book Antiqua">Ahmed Salem, </font><font size=3 face="Book Antiqua">California
State University , Sacramento (CSUS), USA </font>
<br><font size=2 face="sans-serif">Huascar A. Sanchez, Independent Consultant,
Minnesota, USA </font>
<br><font size=2 face="sans-serif">Arturo Sánchez-Ruíz, University of North
Florida, USA</font>
<br><font size=2 face="sans-serif">Christian Schlegel, University of Applied
Sciences Ulm, Germany</font>
<br><font size=2 face="sans-serif">Alberto Rodrigues da Silva, Technical
University of Lisbon,, PORTUGAL </font>
<br><font size=2 face="sans-serif">Marjan Sirjani, University of Tehran,
Iran</font>
<br><font size=2 face="sans-serif">Yasemin Topaloglu, Ege University, Izmir,
Turkey</font>
<br><font size=2 face="sans-serif">Manolis Tzagarakis, University of Patras
Campus, Greece</font>
<br><font size=2 face="sans-serif">Hironori Washizaki, National Institute
of Informatics, Japan </font>
<br><font size=2 face="sans-serif">Levent Yilmaz, Auburn University,
USA</font>
<br><font size=2 face="sans-serif">Wolfgang Zuser, OBJENTIS Software
Integration GmbH, Austria</font>