LOGICAL DESIGN

Author: RIMAWI YASER.
Year: 2003.
University: CARLOS III DE MADRID [www.uc3m.es].
Place of defense: ESCUELA POLITECNICA SUPERIOR.
Place of preparation: UNIVERSIDAD CARLOS III DE MADRID.

Summary: The benchmarks software as CMM, CMM and ISO 15504 are difficult to implement in software organizations, especially at the stage of defining processes. Normally, software organizations are beginning to implement these benchmarks in the area of project management. In this area in particular, the Institute for Project Management (Project Management Institute, PMI) has developed standard project management Project Management Body of Knowledge (PMBOK), which provides organizations with a framework of processes that allow them to manage their projects of any kind. Despite that organizations have several software standards and benchmarks, they encounter difficulties in implementing them due to various reasons such as cost and complexity. For this reason we have developed the model Ramallah that is a model for improving the processes of project management software that helps organizations software to evaluate, define and continuously improve the processes of project management software. The following points summarize the Ramallah model: - The framework of PMBOK processes is the core model-Processes which are within the framework are detailed using the experience of experts and best practices of different benchmarks software for example, CMM, CMMI and ISO 15504. - The definitions of processes are enriched with active process of the most prominent methodologies in project management, such as PRINCE2, METRICA3, DOIT, etc. The result is a Knowledge Base which contains definitions goal of the project management process software. - The organizations use the software Knowledge Base to conduct reviews and develop their definitions of the process. - The evaluation method Ramallah that the model used is the method "Formal Approach to the improvement of software processes." Ph.D. Thesis, Carlos III University of Madrid. - Together with the outcome of the evaluation, the organization software will get the definition of the process of project management software. In addition, the organization will collect their own knowledge (of their assets process) and associated with the corresponding element in the process of defining the process. Since the definition of the process, the organization will be able to select processes and activities required for the implementation of individual projects of the organization. - The results of the projects (the behest of the assets of the organization process) are collected. In this case, Ramallah also serve as a historical database of projects. The organization software will be able to perform queries against the knowledge base to track compliance with the improvement implemented.

Author: ESCALONA CUARESMA MARÍA JOSÉ.
Year: 2004.
University: SEVILLA [www.us.es].
Place of defense: E.T.S. INGENIERÍA INFORMÁTICA.
Place of preparation: UNIVERSIDAD DE SEVILLA.

Summary: The Software Engineering, which is defined as the study of the principles and methodologies for the development and maintenance of software systems, leads dialing patterns of how they should work on the development of information systems within the computer engineering. However, the term of the Software Engineering is a broad term that covers a multitude of systems and which encompasses a large number of areas investigaicón. One of the most recent is what has been called Engineering Web. The Engineering Web is an area of the Software Engineering working in the environment of the Web systems. For years many groups investigaicón has its work aimed at development environments methodological oriented Web applications in general. Thus methodologies as HDM (Hypermedia Design Model), OOHDM (Objetct-Oriented Hypermedia Desgign Method), and other more current and WebML or UWE (UML Based Web Enginerring) working within the engineering Web proposing methods, techniques and models at the same suit. It is the field of engineering site which has assessed the need to consider how a particular feature of the software, which, in recent years, is defined as critical within the development process: Navigation [Cachero & Koch 2002b]. The work presented in this paper is motivated by the critical nature of navigation. It is based on a series of comparative studies, and a set of analytical and empirical experiments have shown that the need to deal with this issue in a series of little nuances developed in the literature. Although the main motivations that have begun carrying out this thesis are within the Engineering site, along the entire document states that the study of navigation is not only of interest in Web systems. It really is a software feature that although his study has been motivated in the environment of the Web, is present in any system where there is a need for a structure of interfaces advanced, complex and navigable by different user roles. Therefore, the work done in this thesis many reference works within the world of engineering Web but really, the proposals being made are applicable to any navigational system. This paper examines the current status in the treatment of navigation. Discusses the need to propose specific models for representation and validation techniques to facilitate their management within the life cycle of the project. This initial analysis leads to pose a comparative study to evaluate how it is addressing the issue of navigation at present: Mainly explores new methodological proposals including treatment of navigation in its life cycle. The comparative analysis that emerges from this assessment, allows the problems that have moved to the realization of this thesis. Navigation is emerging as a critical, complex and deal with what there is particular interest in the world of navigational systems. However, most environments methodological focus mainly processing stages in the design or implementation. This work provides the opportunity to elevate the treatment of navigation previous phases in the cycle of life. Indeed, the thesis moves into phases of engineering and requirements analysis. Its main objectives is to provide models for dealing with navigation in these phases and achieve systematic processes that support the development of such models to facilitate the work the development team. In addition to this, looking for all these models and techniques to describe above are close to the end users and customers with idea that can be included in the life cycle of development as both entities needed for the definition to the final validation of models. The cue 8 rpo l 6e9 a thesis therefore is based on a series of theoretical models and systematic derivation process between them. This theoretical structure finds its translation empirical NDAT (Navigational Development Techiniques) [Escalona et al. 2002] [Escalona et al. 2003] [Escalona et al.2004a]. NDT is a development methodology that takes and implements these models and processes within their life cycle, providing a practical path for application in real projects. The practical application reaches its greatest interest, with the presentation of NDT-Tool [Escalona et al 2003b]. NDET-Tool is a CASE tool that enables the application throughout the life cycle of NDT and get their results. With all this, the argument offered by the approach of a specific problem: the treatment of navigation in the early stages of the life cycle for systems development nevegacionales. This problem, based on a comparative study of current trends is resolved with a theoretical framework to be implemented later in the methodology and tools specific NDT and NDT-Tool.

Author: PEREZ PEREZ JUAN RAMON.
Year: 2005.
University: OVIEDO [www.uniovi.es].
Place of defense: ESC. UNIV. ING. TEC. INFORM. OVIEDO.
Place of preparation: DEPARTAMENTO DE INFORMATICA.

Summary: That argument carries out the definition of a model for a development environment software, which allows users to build applications with a better quality of the code that the current settings. The model is implemented in the system called SICODE, is based on techniques processors language allowing a static analysis of source code, to discover errors in the programming code. This model seeks to influence styles in the form of programming and not just occasional mistakes. It has set up what is called a history compilation, which generate metric evolution and frequency of errors over time. It uses a model active in preventing errors by sending messages. These notices associate semantic information to each error in a knowledge base. This knowledge base is dynamic and realimenta with the experience of all developers, allowing learn from the experience of others. This thesis has conducted a study that enables the classification of users based on the detection of errors in the code. SICODE has enabled us to analyze the mistakes of a large number of projects undertaken by developers. Thus, we have characterized different types of errors depending on the experience of the programmers. This study provides data that allow us to build the foundation for modeling the user and thus make the model is adaptable. The thesis offers new approaches to development systems presently available. The construction of history compilation allows for a deeper analysis than can perform a simple compiler, and this analysis is at the service of improving the code. In addition, the system is focused on the development environment and blends own software development learning to make a quality: the user simply program and SICODE gives you ways to improve the style of programming. Lastly, collaboration is used not only to facilitate the development, but also in building a knowledge base, which makes it possible to build a system that realimente the exchange of experiences among users.