An information system distinguishes itself from other software as it is developed to facilitate the operation of an organization, hence it reflects its strategies, plans, organizations, processes, marketing etc. We believe that the requirement in the form of domain knowledge acquired in the early stage of system development can be organized and modeled in Enterprise Architecture. However research in Enterprise Architecture focus on other issues rather than requirement engineering. Hence we propose several new ideas on the extension of Zachman Framework, one of the most widely used Enterprise Architectures. We first partition Zachman Framework from two different perspectives, domain engineering phases and requirement engineering techniques. Then we propose a meta-model for Zachman Framework which is adapted and integrated from the Bunge-Wand- Weber ontology and Enterprise Ontology.

Even if we have recognized many short-term benefits of agile methods, we still know very little about their long-term effects. In this panel, we discuss the long-term perspective of the agile methods. The panelists are either industrial or academic representatives. They will discuss problems and benefits related to the long-term lifecycle system management in agile projects. Ideally, the panel's outcome will provide ideas for future research.

Nowadays, the detection and correction of software defects has become a very hard task for software engineers. Most importantly, the lack of standard specifications of these software defects along with the lack of tools for their detection, correction and verification forces developers to perform manual modifications; resulting not only in mistakes, but also in costs of time and resources. The work presented here is a study of the specification and correction of a particular type of software defect: Object-Oriented anti-patterns. More specifically, we define a UML based specification of anti-patterns and establish design transformations for their correction. Through this work, we expect to open up the possibility to automate the detection and correction of these kinds of software defects.

This paper addresses the considerable interest there is in how to detect design patterns in existing designs and implementations. These approaches typically look for similarities between the diagrams used to describe the design and those which define the pattern. We look at several pattern detection techniques, before implementing and comparing two of the most successful. From this we conclude that both of these techniques have a certain ability to detect design patterns at the high levels of abstraction and programming language independence, needed at the design level. We then show that these approaches can work together to improve detection rates. Finally we propose how this work can be extended to detect more patterns and to include detection of anti-patterns.

The Reuse of code artefacts can make development quicker, cheaper and more robust, but is complex and has many pitfalls: Code artefacts must exist, be available, be found, be understood, be valid and finally be integrated. Many software developers try to ensure that artefacts meet these requirements through a process of making code "reusable." If the generation of reusable artefacts from developed code could be automated development time could be reduced. Code artefacts must be gathered and indexed automatically with no extra work. Our review of requirement management and version control tools identified a way to generate reuse artefacts through traceability, using information from the requirement management system and code stored in the version control system. A prototype to search these indexed artefacts showed that this tool could substantially reduce development time for simple tasks, by up to 63%.

In this short paper, we represent how user interaction could be integrated into an NLP-based system to support stakeholders' participation in terms of improving requirements elicitation. In contrast to commercial CASE tools that support user interface, the proposed iterative and incremental process allows the refinement of preliminary requirements extracted from domain-specific data, according to users' responses. Not only the quality of requirements could be improved, but also requirements engineers could gain the benefits in ambiguity detection, requirements interpretation and specification and modeling.

An important aspect of a pervasive environment is that it needs to support mobile users - i.e. users whose context changes frequently. In doing so it is important to take account of a user's context in adapting and personalizing services for the user. This paper describes a personalization mechanism that is exploited in the Daidalos project to provide users with value-added enhanced services. It personalizes services across layers including networking and service layers.

The reengineering of legacy systems --- by which we mean those that have value and yet "significantly resist modification and evolution to meet new and constantly changing business requirements" --- is widely recognised as one of the most significant challenges facing software engineers. The problem is widespread, affecting all kinds of organisations; serious, as failure to reengineer can hamper an organisation's attempts to remain competitive; and persistent, as there seems no reason to be confident that today's new systems are not also tomorrow's legacy systems.This paper argues1. that the main problem is not that the necessary expertise does not exist, but rather, that it is hard for software engineers to become expert;2. that the diversity of the problem domain poses problems for conventional methodological approaches;3. that an approach via systems reengineering patterns can help.We support our contention by means of some candidate patterns drawn from our own experience and published work on reengineering. We discuss the scope of the approach, how work in this area can proceed, and in particular how patterns may be identified and confirmed.

To resolve the inability to manage the software process, the Software Engineering Institute released the Capability Maturity Model for Software (SW-CMM) for producing software products effectively and efficiently. Meanwhile, the Booch, OMT, and OOSE methods have been unified into the Unified Modelling Language (UML). The UML focuses on the graphical modelling language and its semantics and far less so on the underlying process. To integrate all the software engineering technical activities, the authors use PASTA (Process and Artifact State Transition Abstraction), which is a bridge between guidance and automation of the software development process, to model the UML. Once a process-centred software environment has been created, it would provide a basis for cumulative benefits to the software organisation.