Abstract We live at an exciting time where software has become a dominant aspect of our everyday life. Although software provides opportunities for improving various aspects of our society, it also presents many challenges. One of them is development, deployment, and sustaining of high quality software on a broad scale. While agile methods (Scrum being one of the most prominent examples) ease the process, their popularity deteriorates the clarity and simplicity they were once meant to bring into software development. This article explores the synergy of Scrum and Essence, a domain model of software engineering processes, intending to become a common ground for software development methods, bringing clarity into the composition of methods from individual practices. This short communication motivates the interplay of Scrum and Essence, being accompanied with a set of videotutorials and 21 Scrum Essential cards to further guide more effective team's way of working.

General theories explain the fundamental phenomena that constitute a research domain. They apply across a domain and often integrate many theories and concepts into a single cohesive view. While general theories are extremely important for education and research coordination, and common in many disciplines (e.g. sociology, criminology, electrical engineering, biology, physics), software engineering lacks a well-accepted general theory. The General Theory of Software Engineering workshop seeks to rectify this situation by promoting theory development in software engineering. The fourth workshop in this series, held in conjunction with the International Conference on Software Engineering, displayed a promising trend toward more theory development papers.

Most academic disciplines emphasize the importance of their general theories. Examples of well-known general theories include the Big Bang theory, Maxwell's equations, the theory of the cell, the theory of evolution, and the theory of demand and supply. Less known to the wider audience, but established within their respective fields, are theories with names such as the general theory of crime and the theory of marriage. Few general theories of software engineering have, however, been proposed, and none have achieved significant recognition. This workshop, organized by the SEMAT initiative, aims to provide a forum for discussing the concept of a general theory of software engineering. The topics considered include the benefits, the desired qualities, the core components and the form of a such a theory.

The new software engineering initiative, Semat, is in the process of developing a kernel for software engineering that stands on a solid theoretical basis. So far, it has suggested a set of kernel elements for software engineering and basic language constructs for defining the elements and their usage. This paper describes a session during which Semat results and status will be presented. The presentation will be followed by a discussion panel.

Software engineering is gravely hampered by immature practices. Specific problems include: The prevalence of fads more typical of the fashion industry than an engineering discipline; a huge number of methods and method variants, with differences little understood and artificially magnified; the lack of credible experimental evaluation and validation; and the split between industry practice and academic research.

Summary form only given. One of the most popular buzzwords in software development is agile. Today everyone wants to be agile. That is good! However, being agile is not enough. For several years Dr. Ivar Jacobson has expressed that the most important character you need to have to be a great software developer is to be smart. What does that mean? Most people know intuitively what does it mean for software. In this session, Dr. Ivar Jacobson will describe what it means to be smart when it comes to developing software from requirements through to deployment.

Article Free Access Share on Patterns: cult to culture? Authors: Steven Fraser BNR/Nortel (Moderator) BNR/Nortel (Moderator)View Profile , Grady Booch Rational RationalView Profile , Frank Buschmann Siemens SiemensView Profile , Jim Coplien AT&T AT&TView Profile , Norm Kerth Elite Systems Elite SystemsView Profile , Ivar Jacobson Objectory ObjectoryView Profile , Mary Beth Rosson Virginia Polytechnic Institute and State University Virginia Polytechnic Institute and State UniversityView Profile Authors Info & Claims OOPSLA '95: Proceedings of the tenth annual conference on Object-oriented programming systems, languages, and applicationsOctober 1995 Pages 231–234https://doi.org/10.1145/217838.217863Online:17 October 1995Publication History 3citation600DownloadsMetricsTotal Citations3Total Downloads600Last 12 Months19Last 6 weeks0 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF

No abstract available.

article Free Access Share on Methodology standards: help or hindrance? Authors: Grady Booch Rational Software Corporation Rational Software CorporationView Profile , Brian Henderson-Sellers University of Technology, Sydney University of Technology, SydneyView Profile , Ivar Jacobson Objective Systems AB Objective Systems ABView Profile , Steve Mellor Project Technology, Inc. Project Technology, Inc.View Profile , James Rumbaugh GE GEView Profile , Rebecca Wirfs-Brock Digitalk DigitalkView Profile , Chairman: David Monarchi University of Colorado, Boulder University of Colorado, BoulderView Profile Authors Info & Claims ACM SIGPLAN NoticesVolume 29Issue 10Oct. 1994 pp 223–228https://doi.org/10.1145/191081.191115Online:01 October 1994Publication History 5citation0DownloadsMetricsTotal Citations5Total Downloads0Last 12 Months0Last 6 weeks0 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF

Article Free Access Share on The OO software development process (panel) Authors: Dennis de Champeaux View Profile , Bob Balzer View Profile , Dave Bulman View Profile , Kathleen Culver-Lozo View Profile , Ivar Jacobson View Profile , Stephen J. Mellor View Profile Authors Info & Claims OOPSLA '92: Conference proceedings on Object-oriented programming systems, languages, and applicationsOctober 1992Pages 484–489https://doi.org/10.1145/141936.141974Published:31 October 1992Publication History 0citation383DownloadsMetricsTotal Citations0Total Downloads383Last 12 Months9Last 6 weeks0 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF

Object-oriented programming is a promising approach to the industrialization of the software development process. However, it has not yet been incorporated in a development method for large systems. The approaches taken are merely extensions of well-known techniques when 'programming in the small' and do not stand on the firm experience of existing developments methods for large systems. One such technique called block design has been used within the telecommunication industry and relies on a similar paradigm as object-oriented programming. The two techniques together with a third technique, conceptual modeling used for requirement modeling of information systems, have been unified into a method for the development of large systems.

A set of concepts for modeling large real time systems is discussed informally. The concepts support the design of centralized as well as distributed systems. They are object oriented in that they correspond to entities of the 'real world', and they are 'change oriented' in that they support not only the first development stage of a system but also its continuous change and evolution. In particularly, the concepts give a promising solution to 'on the fly' changes of existing, active entities.