No full-text available
To read the full-text of this research,
you can request a copy directly from the authors.
A NEW LOOK AT DOCUMENTATION AND TRAINING
Abstract
Users need quality documentation and training. A technical communicator can be an indispensable communications analyst and problem solver for an organization, helping to analyze user requirements, clarify the documentation process, develop information products, and provide computer training. By assisting IS management in solving increasingly complex communication problems, this person can also shed the one-dimensional image of the technical writer who works solely as a software documenter at the end of the development process.
... It is often difficult to control the type of materials accessed by students – for example, students may access unwarranted or unauthorized materials. For Indigenous students, the availability of resources to access the Internet and the use of such resources, associated with technical knowledge has been a source of concern working against the claim that the Internet is beneficial education (Craig & Beck, 1993). Aboriginal children who experience the breakup in families, the loss of Indigenous culture, the demise of many Indigenous languages, racism, violence, poverty, lack of facilities, and poor health have very little incentive to finish their schooling and possibly look forward to higher education. ...
In 2000 the Australian government, recognising the need for educational equality for Australian Indigenous people has commissioned a taskforce to identify various factors affecting Indigenous Education. One of the factors identified by the task force included the need for strategies to deliver quality education to various Indigenous communities. Research studies conducted on the delivery of education highlight the importance of the Internet for the flexible delivery of education. However, government reports indicate that Australian Indigenous communities have problems in utilising this technology for reasons such as access, infrastructure, training, etc. Therefore a new model based on the recently introduced digital technology may be tested for delivering quality education to Indigenous communities. This paper provides a discussion of the impact and influence of digital transmission in facilitating the delivery of quality educational resources for Indigenous Australians. For the purposes of discussion, a model architecture is formed and a number of issues based on this architecture are considered. These issues include data transmission, delivery mechanisms, regulations and the pricing of realising such services. The focus of the paper is to provide discussion of quality educational services to a wide range of Indigenous audiences.
Implementing enterprise resource planning (ERP) systems remains challenging and requires organizational changes. Given the scale and complexity of ERP projects, documentation plays a crucial role in coordinating operational details. However, the emergence of the agile approach raises the question of how adequate lightweight documentation is in agile ERP implementation. Unfortunately, both academia and industry often overlook the natural evolution of documentation practices. This study examines current documentation practices through interviews with 23 field experts to address this oversight. The findings indicate a shift in documentation practices from retrospective approaches to dialogue-based, agile throwaway documents, including audiovisual recordings and informal emails. Project managers who extensively engage with throwaway documents demonstrate higher situational awareness and greater effectiveness in managing ERP projects than those who do not. The findings show an organic transformation of ERP documentation practices. We redefine documentation to include unstructured, relevant information across different media, emphasizing searchability. Additionally, the study offers two vignettes for diverse organizational contexts to illustrate the best practices of agile ERP projects.
This paper describes our long journey from the first standardization projects to support a fully automated work flow to three complex automation hardware projects, including learnings about change management within a running fab for all departments. The general principles used to automate a mature fab were motivated by a clear economical approach-cost reduction in manufacturing by automation of simple and recurring logistic steps. This can only be successfully completed by an interdisciplinary team work. But there is no ONE recipe for all mature fabs-the older the fab, the more flexible and cost effective the automation concepts must be. Collaboration between human and machine become a key element in this context. One topic in this field is the development of smarter and cost efficient mobile robotic systems (AGV). Smarter means more intelligent, less cost and more stability in process execution. Since we manufacture IoT elements like Time of Flight and Radar sensor in our fabs-we also developed a new integrated sensor fusion concept combined with artificial intelligence (AI) and machine Learning (ML) methods.
A case study was performed examining the electronic data interchange (EDI) implementation projects of four divisions of an aerospace company. By interviewing both partners in the relationship, a business-to-business (B2B) electronic commerce (e-commerce) implementation framework was developed. The framework provides guidelines for the type of e-business partnership to be pursued based on the volume of transactions (low vs. high) and complexity of transactions (simple vs. complex). Machine-to-machine B2B solutions should be pursued when the there is a high transaction volume of simple transactions. In other situations, potential B2B solutions include: e-business pull, partner access-extranet/push, or manual e-transmission.
This paper deals with errors by novices and experts when interacting with the computer in normal office work. Three criteria are discussed to determine the level of expertise: a) total length of time that the user has worked computers, b) number of programs known, and c) length of daily work-time with the computer. In contrast to widespread assumptions, experts did not make less errors than novices (except knowledge errors). On the other hand, experts spent less time handling the errors than novices. A cluster analysis produced groups of Occasional-, Frequent-, Beginning- and General Users in the work force.
Although many variables can contribute to the failure of a systems development project, the use of the traditional f one-dimensional systems development life cycle approach is often a major factor in the failure of such an effort This article describes an alternative method— the two-dimensional approach to systems development— and discusses why IS managers should consider adopting this new development approach.
The use of appropriate documentation standards is particularly important in database environments due to the size and complexity of the problems usually involved. An approach to the use of standards in such environments is described that uses documentation standards described for traditional data processing to preserve the similarities of descriptions usually required by the users and help solve some of the problems currently encountered.
It is noted that user interface professionals contribute to a
project by making sure that the design of both the input and output of
any system takes users' needs into consideration. These professionals
perform varied tasks. They analyze the job tasks of users, design and
administer questionnaires, conduct user studies, make user interface
design recommendations, design prototypes, perform statistical analysis,
and interpret the results. In some projects, they are assisted in these
tasks by software tools that generate interface code which can be reused
by programmers, thus saving significant development time and enhancing
the quality of the product. It is recommended that project managers
assign user interface professionals to work on large projects throughout
their life cycle
A study of communication in graduate management programs sponsored
by IEEE/PCS and Fairleigh Dickinson University is described. The
findings indicate a clear need for more emphasis on oral and written
communication and suggest that one solution to the problem is a course
requirement in written and oral communication in conjunction with one or
two full-time faculty dedicated to the subject. The findings also
indicate that full-time faculty who teach communication courses at the
graduate level have extensive business and academic experience, and
their compensation is well within national guidelines. The study
indicates clearly that exit requirements, when they exist, lack both an
oral and written communication component, although a written term
project for course work is almost universally employed. Other surveys
and publications provide background information;
You know one when you see one, even though they come in all shapes and sizes. The titles of these small, hand-held publications usually contain the word guide, summary, or reference. Many of us in the documentation business have coined the terms job aid or quick reference to identify these small packages of information that readers can refer to at a moment's notice. Quick references are small, portable packages of information that can be seen in the pockets of programmers, high-tech equipment operators, and even shoppers at the grocery store. But where did they come from? What strange breed of documentation is this? Is there rhyme or reason in the design of quick reference documentation? This paper presents a description of various quick references and discusses their design.