An introduction to the DUB framework in information system development: a data centric approach

2014 ◽  
Author(s):  
M. Gu ◽  
R. Gu ◽  
B. Xu
Keyword(s):  
Information System ◽  
System Development ◽  
Information System Development

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

Geographic information system development in the CARETS project

1977 ◽  
Author(s):  
William B. Mitchell ◽  
Robin G. Fegeas ◽  
Katherine A. Fitzpatrick ◽  
Cheryl A. Hallam
Keyword(s):  
Information System ◽  
Geographic Information System ◽  
System Development ◽  
Geographic Information ◽  
Information System Development

A Kernel System for information system development, evolution, and operation

1973 ◽  
Vol 8 (9) ◽  
pp. 117-119 ◽  
Author(s):  
Harlan D. Mills ◽  
Max L. Wilson
Keyword(s):  
Information System ◽  
System Development ◽  
Information System Development

Design for Maintenance: How Kms Document Linking Decisions Affect Maintenance Effort and Use

2014 ◽  
Vol 29 (4) ◽  
pp. 312-326 ◽  
Author(s):  
Alan R Dennis ◽  
Binny M Samuel ◽  
Kelly McNamara
Keyword(s):  
Information System ◽  
System Development ◽  
Management Systems ◽  
Information System Development ◽  
Web Based ◽  
Useful Knowledge ◽  
Design Considerations ◽  
Dynamic Content ◽  
System Maintenance ◽  
The Cost

Information system maintenance is an important aspect of information system development, especially in systems that provide dynamic content, such as Web-based systems and Knowledge Management Systems (KMS). Design for Maintenance (DFM) is an approach that argues that maintenance effort should be considered during the design of information systems in addition to the usual system design considerations. This research examines how the design of links among knowledge documents in a KMS affects both their maintenance and use. We argue that providing links among knowledge documents increases the cost of maintenance because when a document changes, the documents that link to and from that document are more likely to need changes. At the same, linking knowledge documents makes it easier to locate useful knowledge and thus increases use. We examine this tension between use and maintenance using 10 years of data from a well-established KMS. Our results indicate that as the number of links among documents increases, both maintenance effort and use for these documents increase. Our analyses suggest two DFM principles for dynamic content in practice. First, knowledge coupling (i.e., linking) to documents internal to the KMS rather than sources external to the KMS better balances maintenance effort and use. Second, designing small, knowledge cohesive documents (e.g., 250-350 words) leads to the best balance between maintenance effort and use.

Sign in / Sign up

Export Citation Format

Share Document