Information Systems and Design of Communication (ISDOC2012)

At workshop Information Systems and Design of Communication (ISDOC2012), researchers and practitioners will exchange information in areas relevant to the design of communication, processes, methods, and technologies for communicating and designing communication artifacts such as printed documents, online text, and hypermedia applications. The workshop will emphasize the following subjects (but not exclusively):
  • design of communication and Multimedia
  • design of communication and Editing tools
  • design of communication and Games
  • design of communication and HCI
  • design of communication and ERPdesign of communication and organizational systems

Important Dates:

  • Paper submission: 29th February, 2012
  • Author notification: 9th April, 2012
  • Camera ready: 21th April, 2012
  • Workshop Date: 11th June,2012

ISDOC 2012 will include technical papers, experience reports and posters. Authors should submit complete drafts of all type of submissions for review by the program committee.

The ACM paper format (http://www.acm.org/sigs/publications/pubform.doc) must be followed. Additional information in ACM SIG Proceedings Templates (http://www.acm.org/sigs/publications/proceedings-templates)To submit a paper, experience report or poster proposal for review, use the submission platform or carlos.costa@acm.org mail, with the following subject:”ISDOC2012 – Paper”. If you have any question e-mail Carlos Costa (carlos.costa@acm.org).

Acceptance for publication is contingent on registration for the workshop. (In the case of multiple authors, at least one must register to full workshop.) If you cannot attend the workshop, a publication fee equivalent to the event registration will be charged.

Guidelines for Research Papers – Papers should not exceed 5,000 words, approximately 8 pages in ACM conference format (available at the site), including figures and references. The results described must not be under consideration for publication elsewhere.

Guidelines for Short Papers – Papers should not exceed 6 pages in ACM conference format.

Guidelines for Experience Reports – Experience reports should not exceed 3,500 words. The experience report is a standalone, six-page extended abstract that describes a design experience and its lessons for other designers of communication. The experience report must include the title, names and affiliations of the authors, an abstract of up to 150 words, and keywords.

Guidelines for posters – Accepted poster submissions will receive a two pages description in the conference proceedings. The submission should be formatted according to the ACM guidelines for paper submissions, but the length must be only two pages.

Acceptance for publication is contingent on registration for the workshop. In the case of multiple authors, at least one must register to full workshop. If you cannot attend the workshop, a publication fee equivalent to the event registration will be charged. If an author presents more than one paper, an additional fee is charged for publishing each additional paper.

Sponsored Post Learn from the experts: Create a successful blog with our brand new courseThe WordPress.com Blog

WordPress.com is excited to announce our newest offering: a course just for beginning bloggers where you’ll learn everything you need to know about blogging from the most trusted experts in the industry. We have helped millions of blogs get up and running, we know what works, and we want you to to know everything we know. This course provides all the fundamental skills and inspiration you need to get your blog started, an interactive community forum, and content updated annually.

ERP and Assistance Systems

Paper Title: ERP and Assistance Systems

Abstarct: User assistance systems are especially important in complex information systems. ERP (Enterprise Resource Planning) is an example of a complex system. On the other hand, users of those systems want a quick and precise answer to their problems in order to perform specific tasks. In this paper, we analyze the adoption of user assistance systems. In order to analyze, we use as theoretical framework the technology Acceptance Model (TAM). We also proposed some characteristics related to the perception of ERP use that may influence the acceptance and adoption of user assistance systems.

http://www.wseas.us/e-library/conferences/2011/Florence/AIASABEBI/AIASABEBI-33.pdf

Testing usability of ERP open source systems

Title: Testing usability of ERP open source systems

Abstract: In this paper we estimated three models that may be used to identify performance of a ERP system. As dependent variables, generic performance variables were used (effectiveness, efficiency and satisfaction). As independent variables we used usability criteria. Those were derived from literature and but their inclusion in the models was estimated. In what concerns independent variables several criteria were identified like existence of online support, easiness of interpretation of output, support to navigation, help and documentation or minimize of memory load.

http://dl.acm.org/citation.cfm?id=1936755.1936763

Organizational Tools in the Web: ERP Open Source

Title: Organizational Tools in the Web: ERP Open Source

Abstract: ERP (Enterprise Resource Planning) open source systems appeared as opportunities. For example, to organizations that cannot support the cost of large ERP systems, open source may be a possible solution. Nevertheless, those systems have limitations. Those systems may not be as free as their developers claim. Furthermore, as developers do not receive a fee for the production of the software, those solutions are not so well built. In this paper, we intend to answer three questions.
First, we want to know the main needs in terms of software systems in organizations. We also want to know in what extent open source ERP may become one competitive solution for IT Consultant, Software Distributor, software producer or information systems clients’. Finally, what extend current solutions presented by the market fulfils client’s needs.

http://www.slideshare.net/Agcristi/organizational-tools-in-the-web-erp-open-source

Supporting ERP open source customization with UML

Title: Supporting ERP open source customization with UML

Abstract: ERP are complex systems. One of the consequences is the need to support customizations, maintenance and help users. An adequate documentation may be the solution to this problem. In the documentation ERP features, UML may play an important role. Consequently, here we propose an approach supported in the use o UML. This approach was used in a limited context.

http://dl.acm.org/citation.cfm?id=1936764

innovating organizational systems