Este trabalho descreve a definição e institucionalização de um processo de engenharia de requisitos que está em conformidade com as áreas de processo do CMMI (Capability Maturity Model) de Gerência de Requisitos e Desenvolvimento de Requisitos e cujos componentes (atividades, papéis, produtos de trabalho) são baseados em RUP (Rational Unified Process). A principal contribuição deste estudo é a definição de um processo de engenharia de requisitos baseado em abordagens de desenvolvimento diferenciadas, que foi implantado em uma organização específica, com foco em praticidade, eficiência e retorno do investimento. A implantação do processo em projetos reais permitiu sua experimentação, avaliação e refinamento, validando as alternativas de integração utilizadas para empregar as abordagens de desenvolvimento escolhidas. Complementando o processo proposto, como decorrência do foco em eficiência, são consideradas possibilidades de emprego de práticas de métodos ágeis na execução do processo, com o intuito de aumentar a produtividade do mesmo, sustentando sua garantia de qualidade. O processo proposto é descrito, do método de concepção aos passos envolvidos e artefatos gerados em cada atividade. Também são comentadas as etapas e áreas de trabalho envolvidas na institucionalização do trabalho. / This research depicts the definition and institutionalization of a requirements engineering process which is in conformance to CMMI (Capability Maturity Model) Requirements Management and Requirements Development process areas. The proposed process components (activities, roles, work products) are based on Rational Unified Process (RUP) process framework. The proposed process main contribution is the definition of a requirements engineering process, leveraging such diverse development approaches, which was implemented in a specific organization, focusing on practicality, efficiency and return on investment. Implementing such process in real projects has promoted its experimentation, evaluation and refinement, validating the integration alternatives used to bring together the chosen development approaches. The possibility of employing agile methods practices through the process execution is discussed, aiming at increasing the process productivity, while assuring product quality. The proposed process details are described, from method conception to each activity steps and generated artifacts. The process institutionalization phases and work areas are also commented.

Este trabalho descreve a definição e institucionalização de um processo de engenharia de requisitos que está em conformidade com as áreas de processo do CMMI (Capability Maturity Model) de Gerência de Requisitos e Desenvolvimento de Requisitos e cujos componentes (atividades, papéis, produtos de trabalho) são baseados em RUP (Rational Unified Process). A principal contribuição deste estudo é a definição de um processo de engenharia de requisitos baseado em abordagens de desenvolvimento diferenciadas, que foi implantado em uma organização específica, com foco em praticidade, eficiência e retorno do investimento. A implantação do processo em projetos reais permitiu sua experimentação, avaliação e refinamento, validando as alternativas de integração utilizadas para empregar as abordagens de desenvolvimento escolhidas. Complementando o processo proposto, como decorrência do foco em eficiência, são consideradas possibilidades de emprego de práticas de métodos ágeis na execução do processo, com o intuito de aumentar a produtividade do mesmo, sustentando sua garantia de qualidade. O processo proposto é descrito, do método de concepção aos passos envolvidos e artefatos gerados em cada atividade. Também são comentadas as etapas e áreas de trabalho envolvidas na institucionalização do trabalho. / This research depicts the definition and institutionalization of a requirements engineering process which is in conformance to CMMI (Capability Maturity Model) Requirements Management and Requirements Development process areas. The proposed process components (activities, roles, work products) are based on Rational Unified Process (RUP) process framework. The proposed process main contribution is the definition of a requirements engineering process, leveraging such diverse development approaches, which was implemented in a specific organization, focusing on practicality, efficiency and return on investment. Implementing such process in real projects has promoted its experimentation, evaluation and refinement, validating the integration alternatives used to bring together the chosen development approaches. The possibility of employing agile methods practices through the process execution is discussed, aiming at increasing the process productivity, while assuring product quality. The proposed process details are described, from method conception to each activity steps and generated artifacts. The process institutionalization phases and work areas are also commented.

Este trabalho descreve a definição e institucionalização de um processo de engenharia de requisitos que está em conformidade com as áreas de processo do CMMI (Capability Maturity Model) de Gerência de Requisitos e Desenvolvimento de Requisitos e cujos componentes (atividades, papéis, produtos de trabalho) são baseados em RUP (Rational Unified Process). A principal contribuição deste estudo é a definição de um processo de engenharia de requisitos baseado em abordagens de desenvolvimento diferenciadas, que foi implantado em uma organização específica, com foco em praticidade, eficiência e retorno do investimento. A implantação do processo em projetos reais permitiu sua experimentação, avaliação e refinamento, validando as alternativas de integração utilizadas para empregar as abordagens de desenvolvimento escolhidas. Complementando o processo proposto, como decorrência do foco em eficiência, são consideradas possibilidades de emprego de práticas de métodos ágeis na execução do processo, com o intuito de aumentar a produtividade do mesmo, sustentando sua garantia de qualidade. O processo proposto é descrito, do método de concepção aos passos envolvidos e artefatos gerados em cada atividade. Também são comentadas as etapas e áreas de trabalho envolvidas na institucionalização do trabalho. / This research depicts the definition and institutionalization of a requirements engineering process which is in conformance to CMMI (Capability Maturity Model) Requirements Management and Requirements Development process areas. The proposed process components (activities, roles, work products) are based on Rational Unified Process (RUP) process framework. The proposed process main contribution is the definition of a requirements engineering process, leveraging such diverse development approaches, which was implemented in a specific organization, focusing on practicality, efficiency and return on investment. Implementing such process in real projects has promoted its experimentation, evaluation and refinement, validating the integration alternatives used to bring together the chosen development approaches. The possibility of employing agile methods practices through the process execution is discussed, aiming at increasing the process productivity, while assuring product quality. The proposed process details are described, from method conception to each activity steps and generated artifacts. The process institutionalization phases and work areas are also commented.

Introduction to problem: Many software development projects today have a tendency to fail on some level. Even though they may not fail entirely, they might be completed with schedule delays, budget overrun or with poor quality that do not meet the customer?s requirements. When a project fails in some way, it is because one or many project risks have occurred. Our own opinion in this matter is that if the project team members are more aware of the project?s risks, it might increase the probability of project success. Therefore, we wanted to explore the area of risk awareness. We contacted Volvo Information Technology AB and through discussions we decided to investigate risk awareness when using one of their software project methods. That method was the Rational Unified Process. This report has not been conducted because Volvo IT considers this to be a problem that they wanted to investigate. Instead, we wanted to investigate this since we find the area of risk awareness among project team members interesting and we were able to do this with help from Volvo IT. Even though we mention the term ?project success? in this report, we will not investigate this in the report. Hypothesis: ?By using the Rational Unified Process, a higher awareness of the risks can be achieved by all team members of the project? Aim: The aim of this report is to investigate if risk awareness among project team members increases when software development projects make use of the Rational Unified Process. Method: We have used a web-based questionnaire to gather information. Four projects at Volvo Information Technology AB were contacted and asked to participate in the questionnaire. Two of these were using RUP and two did not use RUP. Personal e-mails were later sent out to each of the project managers with a description of the aim of our research and the way it would be carried out. The participants had a total of seven workdays to fill out the questionnaire. After seven days the site of the questionnaire were closed down. Conclusion: The differences in answers to certain questions have been rather significant between the two project methods. On the whole though, the answers have been positive for both project methods from a risk awareness point of view. Therefore, it seems to us that risk awareness is not dependent on the project method that is being used. We feel that we have not received enough convincing proof that members of RUP projects possess a higher awareness of project risks than non-RUP project members. Therefore we are of the opinion that we cannot verify our hypothesis. / Introduktion till problem: Många av dagens mjukvaru-projekt har en tendens till att misslyckas på ett eller annat sätt. Även om de inte misslyckas helt, kan det hända att de slutförs med förseningar, stora kostnader utanför budgetens ramar eller med otillräcklig kvalitet som inte motsvarar kundernas krav. Anledningen till att ett projekt misslyckas på något sätt är att en eller flera projekt-risker har inträffat. Vår åsikt i detta ämne är att om projekt-medlemmarna har högre medvetenhet om sitt projekts risker kan detta leda till en ökad sannolikhet att projektet "lyckas". Vi ville därför undersöka området risk-medvetenhet närmare. Vi kontaktade Volvo Information Technology AB och genom diskussioner bestämde vi oss för att undersöka risk-medvetenhet vid användandet av en av deras mjukvaru-projekts metoder. Denna metod var The Rational Unified Process. Denna rapport har inte genomförts på grund av att Volvo IT anser detta vara ett problem som de ville ha undersökt. Istället ville vi själva undersöka detta eftersom vi tycker att risk-medvetenhet bland projektets medlemmar är ett intressant område som borde undersökas. Vi kunde genomföra detta tack vare hjälp från Volvo IT. Även om vi nämner begreppet "lyckade projekt" i rapporten, kommer vi i rapporten inte att undersöka detta. Hypotes: "Genom att använda sig av the Rational Unified Process, kan man uppnå en högre risk-medvetenhet bland projektets samtliga medlemmar" Syfte: Syftet med denna rapport är att undersöka om risk-medvetenheten bland projektets medlemmar ökar när mjukvaru-projekt använder sig av the Rational Unified Process. Metod: Vi har använt en web-baserad enkät för att samla information. Vi kontaktade fyra projekt på Volvo Information Technology AB och frågade om de ville medverka i vår enkät. Två av dessa projekt använde the Rational Unified Process och två gjorde det inte. Personliga e-mail skickades senare ut till varje projektledare med förklaring till syftet med undersökningen samt sättet den skulle genomföras på. Deltagarna hade totalt sju arbetsdagar att fylla i enkäten. Efter dessa sju dagar stängdes sidan med undersökningen. Slutsats: Skillnaden i svar på vissa av frågorna var ganska markanta mellan de två projekt metoderna. Dock, från ett risk-medvetenhets perspektiv, var svaren på det hela taget positiva för båda projekt metoderna. Därför verkar det som att risk-medvetenhet inte är beroende av vilken projekt-metod som används. Vi anser oss inte ha tillräckliga belägg för att medlemmar av projekt som använder the Rational Unified Process besitter en högre risk-medvetenhet än projekt som inte använder sig av denna metod. Vi anser därför att vi inte kan verifiera vår hypotes. / Sophie Eklund 0739-078698 Daniel Gunnarsson 0737-344243

The goal of this thesis is to create a proposal of framework which can be used to support software quality management in a small development company. Framework is composed of processes, methodologies and tools which together should improve the quality of software products of a company. Concrete implementation of the framework is shown as a case study. Data for the case study were collected in the company Cleverbee, where the author worked during the case study's creation. Personal contribution of the author of the thesis is firstly the creation of the framework concept based on author's experiences and commented list of concrete results of framework's implementation. The detailed goal setting for this thesis and the definition of the target reader can be found in the chapter 1. Introduction. The definition of main terms, which will appear in the rest of the thesis, is contained in the chapter 2. Terms. Chapter 3. Software quality and its definition is explains the term "software quality" and the nature of the small companies. Chapter 4. Software quality management forms the theoretical foundation of the thesis. In this chapter you find how the methodologies RUP and CMMI view the software quality. Chapter 5. Framework concept contains the concept of the software quality management framework. Framework is based upon relevant sources and also author's personal experience. The chapter 6. Case study describes the concrete example of the implementation of the proposed framework. The case study also contains descriptions of the used software tools. The chapter 7. Conclusion contains the brief resume of the findings of the thesis.

La industria del calzado en el Perú es un sector relevante en la economía por su participación y la generación de puestos de trabajo. Se considera como unas de las actividades minoristas más importantes del país. El mercado de calzados en el Perú se caracteriza por ser bastante competitivo, con colaboración de variadas marcas tanto nacionales como internacionales. Por otro lado, es un producto que ha dado espacio para la diferenciación y que cambia temporada tras temporada siguiendo las últimas tendencias de moda. La empresa es una fábrica de calzados el cual comercializa calzados a través de sus asesores de venta. Estos asesores presentan diversos problemas, entre ellos los más importantes: la información con la que cuenta de sus clientes, productos, pedidos, etc., es escaza o desactualizada; la entrega de pedidos se ha realiza a destiempo o con retrasos; el crédito de los clientes no está controlado; el pago de moras o cuotas no se realiza adecuadamente; en la venta por consignación, frecuentemente se cometen errores en la generación de cuotas. Antes la situación problemática existente se plantea el desarrollo de un sistema móvil con el objetivo de mejorar la productividad de los asesores de venta en sus actividades diarias, lograr un mejor manejo de la información en la empresa e incrementar la rentabilidad por medio de la venta de calzados. El desarrollo de la solución comprende las siguientes fases: modelado del negocio, modelado del sistema, arquitectura del software, construcción, calidad, pruebas de software y la gestión del proyecto. / The footwear industry in Peru is a relevant sector in the economy for its participation and the generation of jobs. It is considerate as one of the most important retail activities in the country. The footwear sector in Peru is characterized by being quite competitive with the collaboration of several national and international brands. In addition, it is a product that provides space for differentiation and that changes seasons continuously following the latest fashion trends. The company is a shoe factory that sells shoes through sales consultants. These consultants present various problems, some of the most important: the information of its customers, products, orders, etc., is scarce or out of date; the delivery of orders is done out of time or with delays; customer credit is not controlled; the payment of arrears or quota is not made properly; in consignment sales, mistakes are often made in the generation of quota. Given the problematic situation, it is proposed to develop a mobile system that aims to improve the productivity of sales consultants in their daily activities, achieve better management of information in the company and increase profitability through the sale of footwear. The development of the solution contains the phases:business modeling, system modeling, software architecture, building, software quality, testing and the project management. / Tesis

This master's thesis deals with the analysis of the requirements placed on the technical support information system which should be used in the software developing company. The basic functions of this system are the collecting of information about all kinds of work which the company employees concentrate on and the possibility of statistics generating. Moreover, it is also possible to implement further extensions to the system which will not only enable other functions, that are not related to the primary goal of the system, to be integrated; but also to define new user roles, for which various limited parts of the system will be accessible.

Goal of this thesis is to describe the warehouse management systems with focus on the engineering solution, software development and innovation. The evolution of warehouse management systems is very similar to that of many other software solutions. Initially a system to control movement and storage of materials within a warehouse, the role of WMS is expanding to including light manufacturing, transportation management, order management, and complete accounting systems. General point of view of this thesis is suggest the method how to implement modular (standard) solution on the premises. Project is specialized on PDA terminals and wireless access points settings. Introductory chapter of thesis offer extensive background, which reach out reader with system SAP and logistics processes. Practical part of project can divided to two parts. First one analyze software and develop system in cooperation with supplier and ITC department of ABB corporation. Follow part describe reports and dynamic programmes in programming language ABAP with a view to adoption architecture of system SAP. In fine author intend about future development of modern technology in ABB corporation and potential development of object identification method.

The thesis deals with a problem of the design of information system. The design of system is provided with Rational Unifeid Process methodology. This thesis creates a list of requests to system. It makes an analysis and a design of current information system. It useses a RUP methodology to realize two first phases, inception phase and elaboration phase. Created elaboration phase of document is a base for creating programming prototype in Ruby on Rails environment using Ruby language with combination of HTML code.

Goal of my work is to introduce software development process metods specialized to Rational Unified Process metod from IBM. I aplicate inception and elaboration phases of RUP on practical example.