<p>The world of systems engineering methods is changing as rigorous ‘off-the-shelf’ systems engineering methods become more popular. One example of such a systems engineering method is Rational Unified Process. In order to cover all phases in a software development process, and a wide range of project-types, such methods need to be of an impressive size. Thus, the need for configuring such methods in a structured way is increasing accordingly. In this thesis, method configuration is considered as a particular kind of method engineering that focuses on tailoring a standard systems engineering method. We propose a meta-method for method configuration based on two fundamental values: standard systems engineering method’s rationality and reuse. A conceptual framework is designed, introducing the concepts Configuration Package and Configuration Template. A Configuration Package is a pre-made ideal method configuration suitable for a delimited characteristic of a (type of) software artifact, or a (type of) software development project, or a combination thereof. Configuration Templates with different characteristics are built combining a selection of Configuration Packages and used as a base for a situational method. The aim of the proposed meta-method is to ease the burden of configuring the standard systems engineering method in order to reach an appropriate situational method.</p>

<p>Att designa en generell och utbyggbar mjukvara är inte enkelt, då det krävs en bred kompetens inom många olika områden. Vi belyser i detta arbete en del av problematiken kring design. Utgångspunkten är ett praktikfall vars målmiljö rör processer och integrationer. Huvudfokus ligger på designmönster, men även en bredare genomgång av ämnen så som utvecklingsmetodik, Service Oriented Architecture (SOA), Web Services (WS) och utvecklingsmiljöer presenteras. Arbetet bedrivs i enlighet med riktlinjer från Rational Unified Process (RUP) och slutprodukten är en checklista på tre punkter. De tre punkterna speglar de lärdomar vi dragit av arbetet genom saker vi gjort och saker vi borde ha gjort. God design kan uppnås genom att förstå den uppgift man åtagit sig, utvärdera sitt resultat och delresultat samt genom användandet av rätt verktyg. Framtida forskningsområden med anknytning till vårt rör förslagsvis metoders betydelse för mjukvarudesign, dynamiska perspektiv hos utvecklare och mer enhetlighet kring begreppet SOA.</p>

Reports of software a development projects that miss schedule, exceeds budget and deliver products with poor quality are abundant in the literature. Both researchers and the industry are seeking methods to counter these trends and improve software quality. Software Process Improvement is a systematic approach to improve the capabilities and performance of software organizations. One basic idea is to assess the organizations’ current practice and improve their software process on the basis of the competencies and experiences of the practitioners working in the organization. A major challenge is to create strategies and mechanisms for managing relevant and updated knowledge about software development and maintenance. Insights from the field of knowledge management are therefore potentially useful in software process improvement efforts to facilitate the creation, modification, and sharing of software processes in any organization. In the work presented in this thesis, we have made an overview of empirical studies on the effect of knowledge management in software engineering. We have categorized these studies according to a framework and we report findings on the major concepts that have been investigated empirically, as well as the research methods applied within the field. We have also investigated two main strategies for knowledge management, codification and personalization, through the application of four concrete methods in a software process improvement setting: Mentoring, Rational Unified Process, Process Workshops and Post Mortem Analysis. We have classified the work in this thesis within three main themes: RT1: Previous research on knowledge management in software engineering. RT2: Application of knowledge management to improve the software process through codification of knowledge. RT3: Application of knowledge management to improve the software process through personalization of knowledge. The main contributions are: C1: An overview of the research literature on empirical studies of knowledge management in software engineering. C2: A method for tailoring the Rational Unified Process to the development process of a software consulting company. C3: Improvements of the Process Workshops method by contextualization. C4: Improvement of the root-cause analysis phase of the lightweight Post Mortem Analysis for more effective project retrospectives. C5: Proposed methods to increase the learning effect of mentor programs in software engineering.

Werden Softwaresysteme auf Basis eines komponentenorientierten Architekturparadigmas entwickelt, stellt sich die Frage, welches Vorgehensmodell zur Projektabwicklung herangezogen werden kann. In der Literatur werden unterschiedliche Vorgehensmodelle zur komponentenorientierten Softwareentwicklung vorgeschlagen. Aus diesen werden in der vorliegenden Untersuchung vier Modelle ausgewählt: Catalysis, Perspective, Rational Unified Process 2002 und V-Modell ’97. Die ausgewählten Vorgehensmodelle werden auf Basis eines allgemeinen Rahmens beschrieben und verglichen. Dabei werden die Aspekte Terminologie, Klassifizierung, Komponentenbegriff, Abdeckung des Lebenszyklus einer Komponente, Abdeckung der Tätigkeitsbereiche, Prozessarchitektur, Prozesssteuerung, Rollenabdeckung und Adaption untersucht. Komponentenorientierte Vorgehensmodelle sind sowohl Weiterentwicklungen bekannter konventioneller Vorgehensmodelle als auch ausschließlich auf die komponentenorientierte Entwicklung ausgerichtet. Obwohl die ausgewählten Vorgehensmodelle speziell auf eine komponentenorientierte Entwicklung ausgerichtet sind, zeigt sich, dass wesentliche Lebenszyklen einer Komponente nur rudimentär behandelt werden. Eine Ausnahme bildet hier Catalysis.

Made available in DSpace on 2014-06-12T16:00:36Z (GMT). No. of bitstreams: 2 arquivo6793_1.pdf: 1868835 bytes, checksum: 71b2827ff6e54be17b026ed94a084b69 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2009 / Uma das tendências da pesquisa em gerenciamento de projetos para os próximos anos é o estudo da ênfase na criação de valor pelos projetos. Este tema envolve uma maior preocupação com o alinhamento dos projetos aos objetivos estratégicos das organizações. No contexto dos projetos de desenvolvimento de software, tal preocupação passa pela revisão das metodologias de desenvolvimento de software que os suportam. A Engenharia de Software Baseada em Valor (VBSE) é uma abordagem que adiciona considerações de valor aos aspectos técnicos da Engenharia de Software, estabelecendo um conjunto de elementos-chave necessários à evolução das técnicas e práticas atuais para que enfatizem a criação de valor. Este trabalho faz uma análise do Rational Unified Process, um framework de processos de software, quanto à ênfase em criação de valor que ele possibilita, usando os elementos-chave da VBSE como diretriz para a análise. Pontos de convergência entre o RUP e os elementoschave são identificados, e uma extensão do processo é proposta para suprir as lacunas encontradas. Uma avaliação do novo processo é feita e oportunidades para trabalhos futuros apresentadas

Att designa en generell och utbyggbar mjukvara är inte enkelt, då det krävs en bred kompetens inom många olika områden. Vi belyser i detta arbete en del av problematiken kring design. Utgångspunkten är ett praktikfall vars målmiljö rör processer och integrationer. Huvudfokus ligger på designmönster, men även en bredare genomgång av ämnen så som utvecklingsmetodik, Service Oriented Architecture (SOA), Web Services (WS) och utvecklingsmiljöer presenteras. Arbetet bedrivs i enlighet med riktlinjer från Rational Unified Process (RUP) och slutprodukten är en checklista på tre punkter. De tre punkterna speglar de lärdomar vi dragit av arbetet genom saker vi gjort och saker vi borde ha gjort. God design kan uppnås genom att förstå den uppgift man åtagit sig, utvärdera sitt resultat och delresultat samt genom användandet av rätt verktyg. Framtida forskningsområden med anknytning till vårt rör förslagsvis metoders betydelse för mjukvarudesign, dynamiska perspektiv hos utvecklare och mer enhetlighet kring begreppet SOA.

Agile methods change the software processes. Agile processes such as Scrum, ExtremeProgramming (XP), Open Unified Process (OpenUP) etc. have techniques that improve softwarequality. No doubt that the purpose of these techniques is to inject quality assurance into theproject under development. This thesis presents quality assurance techniques in Open UnifiedProcess (OpenUP) along with comparative study to extreme programming (XP) for agilesoftware development. OpenUP is an agile and unified process that contains the minimal set ofpractices that help teams to be more effective in developing software. It assists to achieve qualityby an iterative and incremental approach with artifacts, checklists, guidelines, disciplines androles. On the other side XP emphasizes on values such as communication, feedback, respect,and courage. In addition, XP prescribes a collection of techniques, which aim to improvesoftware quality. Both these processes have the same purpose, to develop software that meets the stakeholder’sneeds and expectations, however they uses different approaches to achieve their goals. Thisthesis compares both processes in four different points of view, by comparing their qualitytechniques, focus in time, and cost of usage and social perspective. We have proposed an extrarole of the quality coordinator (QC) in OpenUP/XP. QC can support and coordinate project inall quality assurance activities. The objective of an extra role is to use the knowledge of QC toachieve highest possible product quality in software development process.Keywords: Agile Development, Quality assurance (QA), Open unified process (OpenUP),extreme programming (XP), Quality coordinator (QC)

The content of this thesis is analysis and design Planning software using agile software development methodology for small and middle size projects. I focused primary on specific work products of roles Analytic and Project manager laid down by selected methodology. Created solution can be used as project documentation for the subsequent development of application itself. The result of this thesis allow the reuse of this principles and practices to future projects of similar scope.

The world of systems engineering methods is changing as rigorous ‘off-the-shelf’ systems engineering methods become more popular. One example of such a systems engineering method is Rational Unified Process. In order to cover all phases in a software development process, and a wide range of project-types, such methods need to be of an impressive size. Thus, the need for configuring such methods in a structured way is increasing accordingly. In this thesis, method configuration is considered as a particular kind of method engineering that focuses on tailoring a standard systems engineering method. We propose a meta-method for method configuration based on two fundamental values: standard systems engineering method’s rationality and reuse. A conceptual framework is designed, introducing the concepts Configuration Package and Configuration Template. A Configuration Package is a pre-made ideal method configuration suitable for a delimited characteristic of a (type of) software artifact, or a (type of) software development project, or a combination thereof. Configuration Templates with different characteristics are built combining a selection of Configuration Packages and used as a base for a situational method. The aim of the proposed meta-method is to ease the burden of configuring the standard systems engineering method in order to reach an appropriate situational method.

Made available in DSpace on 2014-12-17T15:48:07Z (GMT). No. of bitstreams: 1 IvanoMS.pdf: 3097163 bytes, checksum: bd3961677e236c9bf0982f3d9ccf0f64 (MD5) Previous issue date: 2004-04-30 / The way to deal with information assets means nowadays the main factor not only for the success but also for keeping the companies in the global world. The number of information security incidents has grown for the last years. The establishment of information security policies that search to keep the security requirements of assets in the desired degrees is the major priority for the companies. This dissertation suggests a unified process for elaboration, maintenance and development of information security policies, the Processo Unificado para Pol?ticas de Seguran?a da Informa??o - PUPSI. The elaboration of this proposal started with the construction of a structure of knowledge based on documents and official rules, published in the last two decades, about security policies and information security. It's a model based on the examined documents which defines the needed security policies to be established in the organization, its work flow and identifies the sequence of hierarchy among them. It's also made a model of the entities participating in the process. Being the problem treated by the model so complex, which involves all security policies that the company must have. PUPSI has an interative and developing approach. This approach was obtained from the instantiation of the RUP - Rational Unified Process model. RUP is a platform for software development object oriented, of Rational Software (IBM group). Which uses the best practice known by the market. PUPSI got from RUP a structure of process that offers functionality, diffusion capacity and comprehension, performance and agility for the process adjustment, offering yet capacity of adjustment to technological and structural charges of the market and the company / () trato com os ativos de informa??o representa hoje principal fator deteminante para o sucesso e, at? mesmo, perman?ncia das organiza??es no mundo globalizado. () n?mero de incidentes de seguran?a da informa??o est? crescendo nos ?ltimos anos. A implanta??o de pol?ticas de seguran?a da informa??o que busquem manter os requisitos de seguran?a dos ativos nos n?veis desejados, caracteriza-se como prioridade maior para as organiza??es. Esta disserta??o prop?e um processo unificado para elabora??o, manuten??o e desenvolvimento de pol?ticas de seguran?a da informa??o, o Processo Unificado para Pol?ticas de Seguran?a da informa??o PUPSI. A elabora??o dessa proposta foi iniciada com a constru??o de uma base de conhecimento fundamentada em documentos e normas oficiais, publicados nas ?ltimas duas d?cadas, que tratam sobre o tema seguran?a da informa??o e pol?ticas de seguran?a. Trata-se de um modelo elaborado a luz dos documentos pesquisados, que define as pol?ticas de seguran?a necess?rias a serem implantadas em uma organiza??o, seus fluxos de trabalho e identifica uma sequ?ncia e hierarquia entre elas, bem como ? feito uma modelagem das entidades participantes do processo. Diante da dimens?o e complexidade do problema que o modelo trata, o qual envolve todas as pol?ticas ele seguran?a que uma organiza??o deve possuir, o PUPSI possui uma abordagem interativa e incremental. Esta abordagem foi adquirida com a instancia??o do modelo ao RUP - Rational Unified Process. O RUP ? uma plataforma para desenvolvimento de software orientado a objeto, da Rational Software (grupo IBM) que utiliza as melhores pr?ticas reconhecidas pelo mercado. O PUPSI herdou do RUP uma estrutura de processo que oferece funcionalidade, capacidade de difus?o e compreens?o, desempenho e agilidade na readequa??o do processo, possuindo capacidade de se adequar as mudan?as tecnol?gicas e estruturais do mercado e da organiza??o