Context: The main part of software engineering methods, tools and technologies has developed around projects as the central organisational form of software development. A project organization depends on clear bounds regarding scope, participants, development effort and lead-time. What happens when these conditions are not given? The article claims that this is the case for software product spec...

In this column, I use a common situation facing many requirements engineers to illustrate that " one size does not fit all " when it comes to selecting a project-specific requirements engineering process. I then recommend a metaprocess for constructing such a process based on the use of a preexisting process framework and its associated repository of reusable process components. I conclude the ...

Usually, the development of an information system (or some part of it) starts with an requirements elicitation, collection and analysis phase that results in a set of natural language requirements specifications. These then serve as a source for the phase of conceptual design where a semantic model of the given universe of discourse is established using modeling and representation concepts like...

Question: Difference between Verification and Validation? Answer: Verification ensures the product is designed to deliver all functionality to the customer; it typically involves reviews and meetings to evaluate documents, plans, code, requirements and specifications; this can be done with checklists, issues lists, walkthroughs and inspection meetings. You CAN learn to do verification, with lit...

In a project like MUMPS, software engineering aspects are critical to ensure the stability of the software and improve the users’ experience. In this talk, we present some of the software engineering aspects tackled since the last users meeting. We present a new functionality allowing users to dump all MUMPS internal data to disk and then restart a previous MUMPS instance from a different proce...

In this paper we present an approach for developers to benefit from multi-project software knowledge. As we show in this paper, this can be achieved by gathering information about how numerous software projects are being built, and about the interrelation of the modules within the projects. Compared to approaches that only monitor a single project, the contribution of our approach is that it no...

This thesis investigates the application of Search Based Software Engineering (SBSE) approach in the field of Software Project Management (SPM). With SBSE approaches, a pool of candidate solutions to an SPM problem is automatically generated and gradually evolved to be increasingly more desirable. The thesis is motivated by the observation from industrial practice that it is much more helpful t...

Context: Software project cancellations are often caused by mistakes made during the project, and such cancellations make a strong economic impact. We analyzed five cancelled software engineering projects. One case was an internal product development project of a company that sells products to its customers. The other four cases were different software engineering projects, and outcomes of thes...