Two paradigms characterize much of the research in the Information Systems discipline: behavioral science and design science The behavioral-science paradigm seeks to develop and verify theories that explain or predict human or organizational behavior The design-science paradigm seeks to extend the boundaries of human and organizational capabilities by creating new and innovative artifacts Both paradigms are foundational to the IS discipline, positioned as it is at the confluence of people, organizations, and technology Our objective is to describe the performance of design-science research in Information Systems via a concise conceptual framework and clear guidelines for understanding, executing, and evaluating the research In the design-science paradigm, knowledge and understanding of a problem domain and its solution are achieved in the building and application of the designed artifact Three recent exemplars in the research literature are used to demonstrate the application of these guidelines We conclude with an analysis of the challenges of performing high-quality design-science research in the context of the broader IS community

/pdf/design-science-in-information-systems-research-1f7l0yvs8e.pdf

Design science in information systems research

物件導向軟體之架構(Object-Oriented Software Construction)探討

Case study is a suitable research methodology for software engineering research since it studies contemporary phenomena in its natural context. However, the understanding of what constitutes a case study varies, and hence the quality of the resulting studies. This paper aims at providing an introduction to case study methodology and guidelines for researchers conducting case studies and readers studying reports of such studies. The content is based on the authors' own experience from conducting and reading case studies. The terminology and guidelines are compiled from different methodology handbooks in other research domains, in particular social science and information systems, and adapted to the needs in software engineering. We present recommended practices for software engineering case studies as well as empirically derived and evaluated checklists for researchers and readers of case study research.

/pdf/guidelines-for-conducting-and-reporting-case-study-research-q10xdzyou5.pdf

Guidelines for conducting and reporting case study research in software engineering

Background: In 2004 the concept of evidence-based software engineering (EBSE) was introduced at the ICSE04 conference. Aims: This study assesses the impact of systematic literature reviews (SLRs) which are the recommended EBSE method for aggregating evidence. Method: We used the standard systematic literature review method employing a manual search of 10 journals and 4 conference proceedings. Results: Of 20 relevant studies, eight addressed research trends rather than technique evaluation. Seven SLRs addressed cost estimation. The quality of SLRs was fair with only three scoring less than 2 out of 4. Conclusions: Currently, the topic areas covered by SLRs are limited. European researchers, particularly those at the Simula Laboratory appear to be the leading exponents of systematic literature reviews. The series of cost estimation SLRs demonstrate the potential value of EBSE for synthesising evidence and making it available to practitioners.

/pdf/systematic-literature-reviews-in-software-engineering-a-5ez032qyiz.pdf

Systematic literature reviews in software engineering - A systematic literature review

We survey the current techniques to cope with the problem of string matching that allows errors. This is becoming a more and more relevant issue for many fast growing areas such as information retrieval and computational biology. We focus on online searching and mostly on edit distance, explaining the problem and its relevance, its statistical behavior, its history and current developments, and the central ideas of the algorithms and their complexities. We present a number of experiments to compare the performance of the different algorithms and show which are the best choices. We conclude with some directions for future work and open problems.

/pdf/a-guided-tour-to-approximate-string-matching-22fowlmq5b.pdf

A guided tour to approximate string matching

An important problem in program development and maintenance is version con- trol, i.e., the task of keeping a software system consisting of many versions and configurations well organized. The Revision Control System (RCS) is a software tool that assists with that task. RCS manages revisions of text documents, in particular source programs, documentation, and test data. It automates the storing, retrieval, log- ging and identification of revisions, and it provides selection mechanisms for composing configurations. This paper introduces basic version control concepts and discusses the practice of version control using RCS. For conserving space, RCS stores deltas, i.e., differences between successive revisions. Several delta storage methods are discussed. Usage statistics show that RCS's delta storage method is space and time efficient. The paper concludes with a detailed survey of version control tools.

/pdf/rcs-a-system-for-version-control-2bikj68xze.pdf

RCS—a system for version control

Computer scientists and practitioners defend their lack of experimentation with a wide range of arguments. Some arguments suggest that experimentation is inappropriate, too difficult, useless, and even harmful. This article discusses several such arguments to illustrate the importance of experimentation for computer science. It considers how the software industry is beginning to value experiments, because results may give a company a three- to five-year lead over the competition.

/pdf/should-computer-scientists-experiment-more-upk848ppt8.pdf

Should computer scientists experiment more

Welcome to the silver anniversary of the International Conference on Software Engineering! Managing the complexity of modern software systems is without question a grand challenge. It is therefore fitting that, inspired by the view of Mount Hood in Portland, Oregon, the theme for this year's meeting is: Scaling New Heights.ICSE, the premier conference for software engineering, brings together world leaders in software engineering research, practice, and education to present and discuss the most recent advances, trends, and concerns in this ever expanding and critical field. This year's Software Engineering Week, May 3 to 10, 2003, consists of the main ICSE conference and an interesting array of tutorials, workshops, and related events associated or co-located with ICSE.

Proceedings of the 25th International Conference on Software Engineering

The Revision Control System (RCS) is a software tool that helps in managing multiple revisions of text. RCS automates the storing, retrieval, logging, identification, and merging of revisions, and provides access control. It is useful for text that is revised frequently, for example programs and documentation.This paper presents the design and implementation of RCS. Both design and implementation are evaluated by contrasting RCS with SCCS, a similar system. SCCS is implemented with forward, merged deltas, while RCS uses reverse, separate deltas. (Deltas are the differences between successive revisions.) It is shown that the latter technique improves run-time efficiency, while requiring almost no extra space.

https://docs.lib.purdue.edu/cgi/viewcontent.cgi?article=1322&context=cstech

Design, implementation, and evaluation of a Revision Control System

https://publikationen.bibliothek.kit.edu/39594/2047

Walter F. Tichy

Papers

RCS—a system for version control

Should computer scientists experiment more

Proceedings of the 25th International Conference on Software Engineering

Design, implementation, and evaluation of a Revision Control System

Experimental evaluation in computer science: a quantitative study