The confluence of component based development, model driven development and software product lines forms an approach to application development based on the concept of software factories. This approach promises greater gains in productivity and predictability than those produced by incremental improvements to the current paradigm of object orientation, which have not kept pace with innovation in platform technology. Software factories promise to make application assembly more cost effective through systematic reuse, enabling the formation of supply chains and opening the door to mass customization. Categories and Subject Descriptors D.2.2 [Design Tools and Techniques], D.2.11 [Software

Use cases have proven helpful for eliciting, communicating and documenting requirements. But whereas functional requirements are well supported, use cases provide less support for working with extra-functional requirements, such as security requirements. With the advent of e-commerce applications, security and other extra-functional requirements are growing in importance. In an earlier paper, the authors have introduced the concept of misuse cases -- inverted use cases to denote functions that should not be possible to perform in a system. In this paper, security related misuse cases are elaborated in further detail through a discussion of templates for their textual description.

Abstract. The work presented in this paper is related to the area of Situational Method Engineering (SME) which focuses on project-specific method construction. We propose a generic process model supporting the integration of different existing SME approaches. This model shall help the method engineer either selecting one SME approach or combining several approaches that best fit the situation of the method engineering project at hand. The generic model presented in this paper already contains three SME techniques: (1) to assemble method chunks (2) to extend an existing method and (3) to generate a method by abstraction/instantiation of a model/meta-model. The paper presents and illustrates these three techniques and show how other SME techniques could be integrated in the model. 1.

Use Cases are an effective technique to express Functional Requirements of a system in a very simple and easy-to-learn way. Use Cases are mainly composed of Natural Language (NL) sentences and the use of NL to describe the behavior of a system is always a critical point, due to the inherent ambiguities originating from the different possible interpretations of NL sentences. We discuss in this paper the application of analysis techniques based on a linguistic approach to detect, within requirements documents, defects related to such inherent ambiguity. Starting from the proposed analysis techniques we will define some metrics that will be used to perform a quality evaluation of requirements documents. Some available automatic tools supporting the linguistic analysis of NL requirements have been used to evaluate an industrial Use Cases document according to the defined metrics. A discussion on the application of linguistic analysis techniques to support semantic analysis of Use Cases is also reported. 1.

ABSTRACT The purpose of this paper is to first showcase the concept of an operation schema---a precise form of system-level operation specification---and secondly show how operation schemas enhance development when they are used as a supplement to use case descriptions. An operation schema declaratively describes the effects of a system operation by pre- and post conditions using the Object Constraint Language (OCL), as defined by the Unified Modeling Language (UML). In particular, the paper highlights techniques to map use cases to operation schemas and discusses the advantages of doing so in terms of clarifying the granularity and purpose of use cases and providing a precise specification of system behavior.

{hoecht} @ rhrk.uni-kl.de Abstract. Self-organized reuse of artifacts from software and system development, using the lightweight Wiki-Technology, promises a sustainable preservation and availability of business-critical information. However, due to the organic, sometimes chaotic growth of content inside a Wiki, additional support for structuring the knowledge and finding interrelated useful content is needed. The enhancement of Wiki content with ontologies – named semantic Wikis- can solve these problems. The application of such semantic Wikis and the development of reasoning mechanisms for software engineering is subject of the project RISE (Reuse in Software Engineering).

The paper proposes a reuse-based approach to determining security requirements. Development for reuse involves identifying security threats and associated security generic threats --- expressed as misue cases --- and requirements --- expressed as security use cases. Development with reuse involves identifying security assets, setting security goals for requirements, based on reuse of generic threats and requirements from the repository.

The provision of lifelong learning facilities is considered to be a major new direction for higher and distance teaching educational institutes catering for the demands of industry and society. ICT networks will in future support seamless, ubiquitous access to lifelong learning facilities at home, at work, in schools and universities. This implies the development of new ways of organizing learning delivery that goes beyond course and programme-centric models. It envisions a learner-centred, learner-controlled model of distributed lifelong learning. We present a conceptual model for the support of lifelong learning which is based on notions from self-organization theory, learning communities, agent technologies and learning technology specifications such as IMS Learning Design. An exploratory implementation has been developed and used in practice. We reflect on the findings and future directions. Lifelong Learning Networks Both higher and distance education are currently exploring the new possibilities offered by eLearning. Today we find new, collaborative initiatives such as virtual universities, consortia and digital universities, which aspire to share learning resources, increase the quantity and quality of educational services, and explore

Capturing the variations characterizing the set of products belonging to a product line is a key issue for the requirements engineering of this development philosophy. This paper describes ways to extend the well-known Use Case formalism in order to make possible the representation of these variations, in the perspective to make them suitable for an automatic analysis. 1.

In this paper we discuss several features of XP we have used in developing curricula and courses at Duke University and the University of Northern Iowa. We also discuss those practices of XP that we teach as part of the design and implementation process we want students to practice as they develop programming expertise and experience. In theory the academic study of programming and software development should be able to embrace all of XP. In practice, however, we find the demands of students and professors to be different from professional and industrial software developers so that while we embrace the philosophy and change of XP we have not (yet) adopted its principles completely.