No-Frills Software Engineering for Business Information Systems Experience Report

Authors:
Volker Gruhn;Clemens Schäfer
Affiliations:
Applied Telematics / e-Business Group, University of Leipzig, Klostergasse 3, 04109 Leipzig, Germany;it factum GmbH, Lichtenbergstraße 8, 85748 Garching, Germany
Venue:
Proceedings of the 2009 conference on New Trends in Software Methodologies, Tools and Techniques: Proceedings of the Eighth SoMeT_09
Year:
2009

Citing 7
Cited 0

A field study of the software design process for large systems

Communications of the ACM
Uncertainty in computer application and its control through the engineering of software

Journal of Software Maintenance: Research and Practice
Peopleware (2nd ed.): productive projects and teams

Peopleware (2nd ed.): productive projects and teams
Extreme programming explained: embrace change

Extreme programming explained: embrace change
Software economics: a roadmap

Proceedings of the Conference on The Future of Software Engineering
Sysiphus: Enabling informal collaboration in global software development

ICGSE '06 Proceedings of the IEEE international conference on Global Software Engineering
Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation

IEEE Transactions on Software Engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

After years of heavyweight software process models there is a trend in industry towards agile methods for the development of business information systems. Experience shows that these approaches are promising, but there is still the demand for a lean and practicable, yet predictable approach for developing business information systems. With our approach we present the essence of experience in the area of business information systems development, which has been enriched with current scientific trends and findings to finally provide a practicable and useful approach. This approach, called No-Frills Software Engineering, is based on principles which address artifact quality and value orientation. These principles guide the socalled main activities during the actual software development. In this paper we motivate our approach and explain its core principles and main activities.