Designing a quality assurance information system for a process firm — A case study

1985 ◽  
Vol 9 (1-3) ◽  
pp. 169-176
Author(s):  
Charles A. Snyder ◽  
James F. Cox ◽  
George Griesinger
Keyword(s):  
Information System ◽  
Quality Assurance

scholarly journals A Contemporary Case Study Illustrating the Integration of Health Information Technologies into the Organisation and Clinical Practice of Radiation Oncology

2005 ◽  
Vol 34 (4) ◽  
pp. 136-145 ◽  
Author(s):  
Andrew A Miller ◽  
Aaron K Phillips
Keyword(s):  
Information System ◽  
Quality Assurance ◽  
Radiation Oncology ◽  
Information Technologies ◽  
Data Use ◽  
Design Management ◽  
Implementation Cost ◽  
Health Information Technologies ◽  
Local Solutions

The development of software in radiation oncology departments has seen the increase in capability from the Record and Verify software focused on patient safety to a fully-fledged Oncology Information System (OIS). This paper reports on the medical aspects of the implementation of a modern Oncology Information System (IMPAC MultiAccess®, also known as the Siemens LANTIS®) in a New Zealand hospital oncology department. The department was successful in translating paper procedures into electronic procedures, and the report focuses on the changes in approach to organisation and data use that occurred. The difficulties that were faced, which included procedural re-design, management of change, removal of paper, implementation cost, integration with the HIS, quality assurance and datasets, are highlighted along with the local solutions developed to overcome these problems.

Implementation of Booking Performance Application Using Bootstrap Case Study in PT XYZ

2019 ◽  
Vol 4 (1) ◽  
pp. 10
Author(s):  
Arfan Sansprayada ◽  
Kartika Mariskhana
Keyword(s):  
Information System ◽  
Business Processes ◽  
System Development ◽  
Basic Requirement ◽  
Application Development ◽  
Information System Development ◽  
Special Expertise ◽  
A Company ◽  
Need For Information

Abstract—The need for information system development in a company is a basic requirement that must be met by each company in order to run its business processes properly. This is the basic key in a company in order to provide maximum results to find as many profits or profits. Application development or requirements in the application also provide speed for employees to carry out their activities to work properly and optimally. The development of the era requires that companies must be productive and have innovations so that the business wheel of the company can run well. This is based on the development of technology that is so fast that it requires special expertise in its application. This research is expected to be able to help some problems that exist in a company. Where its application can make it easier for employees to carry out their respective duties and roles in order to maximize their potential. For companies, the application of this application can accommodate the company's business wheels so that they can be properly and correctly documented .   Keywords : Systems, Information, Applications

Community of inquiry

2018 ◽  
Author(s):  
Philippe Lorino
Keyword(s):  
Information System ◽  
Communities Of Practice ◽  
Management Information System ◽  
Public Management ◽  
Community Of Inquiry ◽  
Integrated Management ◽  
Management Information ◽  
Democratic Life ◽  
General Concern

Pragmatist inquiry involves a group of inquirers who face a break in their experience and pursue existential motives. They must continuously build reciprocal intelligibility. The felicitous outcome requires reciprocal trust, transforming the group of inquirers into a temporary community. The community dimension of inquiry is illustrated through a case study: the implementation of an integrated management information system in an electricity company. It identifies the roles of two types of communities: communities of practice, characterized by common practice, and communities of inquiry, characterized by the diversity of practices but an agreed general concern. The concept of community of inquiry was initially sketched by classic pragmatist authors and later developed by organization scholars, particularly in the field of public management. It is related to Follett’s view of “group organization” as the basis of democratic life and Latour’s concept of “matter of concern.”

scholarly journals On systematically building a controlled natural language for functional requirements

2021 ◽  
Vol 26 (4) ◽  
Author(s):  
Alvaro Veizaga ◽  
Mauricio Alferez ◽  
Damiano Torre ◽  
Mehrdad Sabetzadeh ◽  
Lionel Briand
Keyword(s):  
Information System ◽  
Natural Language ◽  
Qualitative Methodology ◽  
Case Study Research ◽  
Empirical Evaluation ◽  
Functional Requirements ◽  
Industrial Case Study ◽  
Requirements Specifications ◽  
Financial Domain

AbstractNatural language (NL) is pervasive in software requirements specifications (SRSs). However, despite its popularity and widespread use, NL is highly prone to quality issues such as vagueness, ambiguity, and incompleteness. Controlled natural languages (CNLs) have been proposed as a way to prevent quality problems in requirements documents, while maintaining the flexibility to write and communicate requirements in an intuitive and universally understood manner. In collaboration with an industrial partner from the financial domain, we systematically develop and evaluate a CNL, named Rimay, intended at helping analysts write functional requirements. We rely on Grounded Theory for building Rimay and follow well-known guidelines for conducting and reporting industrial case study research. Our main contributions are: (1) a qualitative methodology to systematically define a CNL for functional requirements; this methodology is intended to be general for use across information-system domains, (2) a CNL grammar to represent functional requirements; this grammar is derived from our experience in the financial domain, but should be applicable, possibly with adaptations, to other information-system domains, and (3) an empirical evaluation of our CNL (Rimay) through an industrial case study. Our contributions draw on 15 representative SRSs, collectively containing 3215 NL requirements statements from the financial domain. Our evaluation shows that Rimay is expressive enough to capture, on average, 88% (405 out of 460) of the NL requirements statements in four previously unseen SRSs from the financial domain.

Sign in / Sign up

Export Citation Format

Share Document