<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Design of Usable Interface for a Mobile e-Commerce System</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Paulius Pasˇkevicˇius</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Robertas Damasˇevicˇius</string-name>
          <email>robertas.damasevicius@ktu.lt</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Software Engineering Kaunas University of Technology Kaunas</institution>
          ,
          <country country="LT">Lithuania</country>
        </aff>
      </contrib-group>
      <fpage>31</fpage>
      <lpage>35</lpage>
      <abstract>
        <p>-The development of user interfaces for mobile devices is a challenging research topic as it addresses specific usage of mobile devices-users want rapid responses to their actions while minimizing the amount of information entered. Because of its nature mobile devices face many constraints such as limited size of display and motoric limitations on information input. Good usability is a primary requirement for interface design and is critical to attracting and retaining users, especially in business applications such as mobile e-commerce systems. In this paper, we analyze design principles of user interfaces for mobile devices, formulate requirements for a usable interface of a mobile application, describe model and architecture for interface of a developed PDN (Product Distribution Network) mobile ecommerce system and present its evaluation based on principles of controllability, predictability, unobtrusiveness, privacy and breadth of experience.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>I. INTRODUCTION</title>
      <p>
        Mobile devices impose great challenges on developing
userfriendly interfaces for effective browsing of web content.
Designing a usable user interface (UI) that is also effective
within the constraints of mobile devices and the applied
development technology is becoming a hot research topic.
Good usability is the primary requirement for interface design
[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] that is critical to attracting and retaining users, especially
in business applications such as mobile e-commerce systems.
      </p>
      <p>As the user base of mobile devices grows faster than that
of desktop computers it is essential to constantly research best
principles of effective user interface usable UI and to
evaluate their implementations by designing mobile applications
according to these principles.</p>
      <p>In this paper, we analyze the design principles of user
interfaces for mobile devices, formulate the requirements for
a usable interface of a mobile application, describe the model
and architecture of an interface of a developed mobile
ecommerce system and present its evaluation based on a set
of functional and non-functional criteria.</p>
      <p>II. REQUIREMENTS FOR USABLE INTERFACES IN</p>
      <p>MOBILE DEVICES</p>
      <p>The ISO 9241-11 standard defines usability as a high level
quality objective, i.e., “the extent to which, a product can be
Copyright c 2016 held by the authors.
used by specified users to achieve specified goals with
effectiveness, efficiency and satisfaction in a specified context of
use”. According to the ISO 9241 standard, usability has three
dimensions: efficiency, effectiveness and user satisfaction.</p>
      <p>
        Usability of interface can be evaluated based on the UI
usability challenges formulated in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]:
      </p>
      <p>Predictability and transparency: users must be capable of
predicting the repercussion of their actions.</p>
      <p>Controllability: user must have control over his actions.
Unobtrusiveness: messages must not cause confusion and
distract the user from current activities.</p>
      <p>Privacy: information that is collected about users
implicitly.</p>
      <p>Breadth of experience: learning curve needed to start
using an interface fully and effectively.</p>
      <p>
        Differences in user needs require that an interface will be
effectively used by novice and as expert users. A set of criteria
for evaluating UIs based on user needs was formulated in [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]:
Efficiency: ability to complete transactions quickly in a
minimal number of steps or amount of time, while clarity
implies immediate learnability of efficient user usage of
UI.
      </p>
      <p>Simplicity: avoiding presentation of UI elements
unnecessary for performing the required tasks (minimalistic
design).</p>
      <p>Symbiosis: seamless and ergonomic use of UI.</p>
      <p>Cognitive and motor limits: interface should not overload
the user’s cognitive, visual, auditory, tactile, or motor
limits.</p>
      <p>
        Gong and Tarasewich [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] formulated interface design
guidelines for mobile devices as follows:
      </p>
      <p>Consistency: elements of mobile interfaces such as
names, colour schemes, and dialog appearances should
be device independent;
Reversal of actions: mobile applications should rely
network connectivity as little as possible;
Design for multiple and dynamic contexts: allow users to
configure output to their needs and preferences (e.g., text
size, brightness);
Design for small devices: provide word selection instead
of requiring text input;
Design for speed and recovery: allow applications to be
stopped, started, and resumed with little or no effort;
Design for top-down interaction: present high levels of
information and let users decide whether or not to retrieve
details;
Allow for personalization: provide users the ability to
change settings to their needs or liking;
Design for enjoyment: applications should be visually
pleasing and fun as well as usable.</p>
      <p>
        General design principles or guidelines for mobile interface
include (according to [
        <xref ref-type="bibr" rid="ref5 ref6">5, 6</xref>
        ]):
      </p>
      <p>Learnability: an interface should be easy to use from
the first time the user interacts with it. Amount of
functionality presented to the user should be limited to
exactly what the user requires to get to their goal.
Efficiency: number of steps it takes for a user to complete
a task. Key tasks should be made as efficient as possible.
Memorability: interface should be easier to use each time
the user interacts with it.</p>
      <p>Error recovery: users should not be allowed to make a
mistake.</p>
      <p>Simplicity: avoid unnecessary functionality and keep the
visual design and layout uncluttered.</p>
      <p>Mapping: users get exactly what they expect to happen
when they interact with the interface.</p>
      <p>Visibility: important information should be more visible
than less important information.</p>
      <p>Feedback: user should always be in control of the UI.
Satisfaction: user should enjoy of using the UI.</p>
      <p>Consistency: UI elements should always be displayed and
act the same way across the application.</p>
      <p>
        Of these design principles learnability [
        <xref ref-type="bibr" rid="ref10 ref9">9, 10</xref>
        ] can be
considered as the most important one that facilitates user engagement
and rapid adoption of the product.
      </p>
      <p>III. ARCHITECTURE OF A MOBILE E-COMMERCE</p>
      <p>SYSTEM</p>
      <p>PDN mobile e-commerce platform is an electronic shopping
network for mobile devices that we developed for the
evaluation and implementation of UI design principles for mobile
devices. We think it is essential to line up functional and
nonfunctional requirements for user interface to reach high user
satisfaction.</p>
      <p>PDN platform has a goal—to sell products and services on
mobile devices and save time for buyer and seller.</p>
      <p>
        PDN is software-as-a-service [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] solution that runs on
number of servers and mobile user interface to deliver shopping
experience to mobile devices. System architecture is presented
in Fig. 1.
      </p>
      <p>
        We use a taxonomy of Rich-User-Interface Components [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]
to model the interface and implemented it with
Model-ViewController architectural pattern (Fig. 2).
      </p>
      <p>
        MVC (Model-View-Controller) enables clear separation of
data, logic and user interface. By using this software design
pattern we can inject any user interface as a new view
independently from any component in the system. We are also
able to create any number of views. This design pattern is
widely used, and alongside it other modularity issues can be
tackled according to recent advances [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
      </p>
      <p>
        To reach mobile users we developed front-end application
for mobile devices (PDN Store) that addresses major UI
usability challenges formulated in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]:
      </p>
      <p>
        Predictability: minimal number of UI elements; fast to
read UI elements (ex. images vs. text) [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ];
Controllability: consistent and always available
navigation; consistent colour schemes for key actions;
Unobtrusiveness: avoid entering duplicate information; do
not limit user input format; (e.g., use special controls for
sophisticated input);
Privacy: do not collect unnecessary private information
in advance (e.g., phone number, address, etc.) [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ];
Breadth of experience: use well known symbols for
representing user actions.
      </p>
      <p>
        The UI is also build on set of criteria for evaluating
interfaces based on user needs formulated in [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]: efficiency,
simplicity, symbiosis and motor limits.
      </p>
      <p>IV. IMPLEMENTATION OF USABLE INTERFACE</p>
      <p>FOR E-COMMERCE SYSTEM</p>
      <p>A typical workflow for the PDN Store mobile application
user is to browse goods catalog and to buy items. It is clear that
by helping customer to reach a goal of buying faster and easier,
platform achieves higher customer satisfaction. First mobile
application screen displays product categories and product lists
(Fig. 3). Application views are divided into areas for user
navigation, category (product) information (picture, title, etc.),
user action and user view.</p>
      <p>Selecting product in the product list triggers product
description and media gallery interface. The product description
follows the same pattern of representation giving the user the
feel of familiarity and the ease of use, while avoiding the need
to learn another interface (Fig. 4).</p>
    </sec>
    <sec id="sec-2">
      <title>V. EVALUATION OF DEVELOPED USER</title>
      <p>INTERFACE</p>
      <p>
        To evaluate the design principles formulated by [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] we
compare our developed PDN Store mobile web application
with another popular mobile native application Magento
Mobile. Both applications are recent implementations mobile
applications for e-commerce and suggest resourceful examples
of good principles in mobile user interfaces.
      </p>
      <p>Controllability. It is essential to assure that user always
have control over his actions. One way to ensure it is
to use bidirectional navigation. In PDN Store mobile
application where user moves through number of steps to
reach the goal of buying the product or service it enables
user to switch from one view to another (Fig. 5 shows
ability to go back from product gallery to product details,
product list or category list).</p>
      <p>Magento Mobile uses controllability principle to switch
between different mobile application areas (home, store,
search, cart, profile).</p>
      <p>Magento Mobile also uses controllability for “sort by”
functionality to allow user to sort products in ascending
or descending order. See Fig. 6:
The other important controllability aspect is to persist
input values and do not ask user to re-enter data in case of
information reload (ex. required field empty or incorrect
data).</p>
      <p>Predictability. User must be capable of predicting the
repercussion of interface actions. The main factor
disrupting it is complex interface with many active UI
components (buttons, text boxes, etc.). First and most
important option to avoid this complexity is to use less
UI controls as possible. This reduces functionality but
increases user predictability.</p>
      <p>Using images instead of text can be a key to more
predictable interface worldwide by removing a need for
translation addressing multi-language problems and will
help to recognize interface faster. It is easier to interpret
one symbol (image) than a group of two or more symbols
(text). The PDN Store uses image controls extensively to
simplify navigation interface (Fig. 7).</p>
      <p>Implementation of predictability principle by using
images instead of text is well recognizable on Magento
Mobile as well. To reach high predictability Magento</p>
    </sec>
    <sec id="sec-3">
      <title>Mobile use combinations of images and text.</title>
      <p>Despite being predictable text makes UI more obtrusive.
Unobtrusiveness. To ensure unobtrusiveness it is
important to highlight most desired user actions and ensure
minimal number of clicks to achieve expected result.
PDN Store requires 1 (or 2 steps) to buy preferable
product (select the category and select the product), while
Magento Mobile requires at least 2 or 3 steps. Another
way towards unobtrusiveness on the mobile application
is to allow the user enter his personal data (ex. name,
phone, password) without any unnecessary constrains
(e.g., no special requirements for length, format, quality)
as well as no artificial barriers that stop user from
achieving the goal in timely manner (e.g., too sensitive
limitations for login attempts or delays that block user
in case of unsuccessful login). PDN Store is optimized
to use mobile interface to enter products and most of its
configuration. It makes information more compact and
unobtrusive. Magento Mobile focuses on desktop version
to enter product information. It results in more obtrusive
information entry, validation and display in Magento
Mobile.</p>
      <p>Privacy. People usually do not like to provide personal
information especially if system is not well known yet. To
not respect user privacy we ask only information which
is needed to make the contract (Fig. 9 shows require
recipient address and name only if user chooses shipment
instead of collect at sales point). Leave the responsibility
to the user about his personal data (e.g., if a user prefers
not to enter a phone number we do not require it there
is always an opportunity for email communication).
Breadth of experience. People use symbols to
commubidirectional navigation
images instead of text
optimized for mobile
respected</p>
      <p>Magento Mobile</p>
      <p>navigation
images instead of text
focused on desktop
respected
Breadth of experience
small set of symbols
small set of symbols
nicate in extremely concise form. Symbols are equally
good understandable among many languages and easy
to remember. The PDN Store relies on a small set
of symbols to make the interface equally simple for
any consumer. Fig. 7 displays navigation steps—arrow
suggests direction to reach user goal to buy a product or
service and well known symbols (home, shopping cart,
box, money) indicate progress towards it.</p>
      <p>Both PDN Store and Magento Mobile use small set of
symbols, well defined styles and standard modern UI elements
for most of user actions.</p>
      <p>The other important controllability aspect is to persist input
values and do not ask user to re-enter data in case of failure
(ex. required field empty or incorrect data). This behaviour is
recognizable in Magento Mobile as well.</p>
      <p>In Table I provided are the results of PDN Store and
Magento Mobile evaluation.</p>
    </sec>
    <sec id="sec-4">
      <title>VI. CONCLUSION</title>
      <p>
        In this paper, we have described the development of a
user interface (UI) for a mobile e-commerce system based on
the principles of controllability, predictability, unobtrusiveness,
privacy and breadth of experience. The development of UIs for
a mobile device is especially challenging because of mobile
device constraints such as limited size of display and motoric
limitations on information input as well as the mode of usage
of a mobile device (the user wants rapid response to his actions
while minimizing the amount of entered information as much
as possible). As concluded from evolution of usable UI in
PDN Store and Magento Mobile both mobile e-commerce
applications are aware and use the design principles formulated
by [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>Our future work will focus on the evolution of a usable user
interface for a PDN (Product Distribution Network) mobile
ecommerce system as well as mobile collaboration platform
CDB (Community Driven Business).</p>
      <p>Further research efforts will be made to make the usable
UI adoptable and customizable to the user and we will further
research the ides of UI evolution, where the usable UI design
is based on the evolution through user feedback, user profiling
and the community voting mechanism.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Qiu</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhang</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Huang</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <article-title>Usability in mobile interface browsing</article-title>
          .
          <source>Web Intelligence and Web Agent Systems</source>
          ,
          <volume>4</volume>
          (
          <issue>1</issue>
          ),
          <fpage>43</fpage>
          -
          <lpage>59</lpage>
          . IOS Press,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Jameson</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <article-title>Adaptive Interfaces and Agents</article-title>
          .
          <source>In J. Jacko and A. Sears (Eds.)</source>
          ,
          <article-title>The human-computer interaction handbook: Fundamentals, evolving technologies and emerging applications, 305330</article-title>
          . Erlbaum,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Padilla</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Strike</surname>
          </string-name>
          <article-title>a balance: Users' expertise on interface design</article-title>
          .
          <source>[online] IBM DeveloperWorks</source>
          ,
          <year>2003</year>
          . Available at: http://www.ibm.com/developerworks/webservices/library/wssoamethod3/index.html
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Gong</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tarasewich</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <article-title>Guidelines for Handheld Mobile Device Interface Design</article-title>
          .
          <source>Proc. of the 2004 Decision Sciences Institute Annual Meeting</source>
          , Boston, Massachusetts, USA,
          <fpage>3751</fpage>
          -
          <lpage>3756</lpage>
          .
          <source>Decision Sciences Institute</source>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Masterton</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mauney</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <article-title>Small Screen Interfaces</article-title>
          . In Kortum, P. (Ed.),
          <source>HCI Beyond The GUI: Design for Haptic</source>
          , Speech, Olfactory, and
          <source>Other Nontraditional Interfaces</source>
          ,
          <fpage>307</fpage>
          -
          <lpage>358</lpage>
          . Morgan Kaufmann,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Mayhew</surname>
            ,
            <given-names>D.J.</given-names>
          </string-name>
          <article-title>The Usability Engineering Lifecycle: A Practitioner's Handbook for User Interface Design</article-title>
          . Morgan Kaufmann,
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Senga</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <article-title>A Service-Oriented Approach to Implementing an Adaptive User Interface</article-title>
          ./ Masters Thesis. Nelson Mandela Metropolitan University, Port Elizabeth, South Africa.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Gomez</surname>
            ,
            <given-names>R.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cebollero</surname>
            ,
            <given-names>D.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Moreno</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Diaz-Perez</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aedo</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          <article-title>Taxonomy for Rich-User-Interface Components: Towards a Systematic Development of RIAs</article-title>
          .
          <source>Proc. of 11th Int. Conf. on Web Engineering, ICWE</source>
          <year>2011</year>
          , Paphos, Cyprus. Springer 2011. LNCS Vol.
          <volume>6757</volume>
          ,
          <fpage>411</fpage>
          -
          <lpage>414</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Damasevicius</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tankeleviciene</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <article-title>Learning Object Reengineering Based On Principles for Usable User Interface Design</article-title>
          .
          <source>Proc. of 10th Int. Conf. on Enterprise Information Systems, ICEIS</source>
          <year>2008</year>
          , Barcelona, Spain, Vol.
          <volume>HCI</volume>
          ,
          <fpage>124</fpage>
          -
          <lpage>129</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Damasevicius</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tankeleviciene</surname>
            ,
            <given-names>L. Merging</given-names>
          </string-name>
          <article-title>HCI and e-Learning Domain Oriented Design Principles for Developing User Interfaces for Mobile Devices</article-title>
          .
          <source>Proc. of 2nd Int. Conf. On Innovations for the Future</source>
          <year>2008</year>
          e-Learning, Istanbul, Turkey,
          <fpage>155</fpage>
          -
          <lpage>166</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Wozniak</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Napoli</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tramontana</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Capizzi</surname>
            <given-names>G.</given-names>
          </string-name>
          <article-title>A multiscale image compressor with rbfnn and discrete wavelet decomposition</article-title>
          .
          <source>In Proc. of International Joint Conference on Neural Networks (IJCNN)</source>
          . IEEE,
          <year>2015</year>
          , pp.
          <fpage>12191225</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Wozniak</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Polap</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nowicki</surname>
            ,
            <given-names>R.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Napoli</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pappalardo</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tramontana</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <article-title>Novel approach toward medical signals classifier</article-title>
          .
          <source>In Proceedings of IEEE International Joint Conference on Neural Networks (IJCNN)</source>
          .
          <volume>12</volume>
          -
          <issue>17</issue>
          <year>July</year>
          , Killarney, Ireland: IEEE,
          <year>2015</year>
          , pp.
          <fpage>19241930</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>Calvagna</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Tramontana</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <article-title>Delivering dependable reusable components by expressing and enforcing designdecisions</article-title>
          .
          <source>In Proceedings of IEEE Computer Software and Applications Conference Workshops (COMPSACW)</source>
          ,
          <source>Kyoto, Japan, 2226 July</source>
          <year>2013</year>
          ; pp.
          <fpage>493498</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>Giunta</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ; Pappalardo,
          <string-name>
            <given-names>G.</given-names>
            ;
            <surname>Tramontana</surname>
          </string-name>
          ,
          <string-name>
            <surname>E.</surname>
          </string-name>
          <article-title>Superimposing roles for design patterns into application classes by means of aspects</article-title>
          .
          <source>In Proceedings of the ACM Symposium on Applied Computing (SAC)</source>
          ,
          <source>Trento, Italy, 2630 March</source>
          <year>2012</year>
          ; pp.
          <fpage>18661868</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <surname>Napoli</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Pappalardo</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ; Tina,
          <string-name>
            <given-names>G.M.</given-names>
            ;
            <surname>Tramontana</surname>
          </string-name>
          ,
          <string-name>
            <surname>E.</surname>
          </string-name>
          <article-title>Cooperative Strategy for Optimal Management of Smart Grids by Wavelet RNNs and Cloud Computing</article-title>
          .
          <source>IEEE Transactions on Neural Networks and Learning Systems</source>
          , vol.
          <volume>27</volume>
          , no.
          <issue>8</issue>
          , pp.
          <fpage>16721685</fpage>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>