在軟體開發的過程中，有效的需求管理能促成高品質的軟體及管理。在CMMI中與需求管理有關的議題包括需求發展(Requirements Development)流程領域-屬於CMMI成熟度第三級，提供一些目標、執行方法(practices)和相關資訊作為指引，協助開發團隊發展顧客需求和產品需求。另一個相關議題-需求管理(Requirements Management) 流程領域，屬於CMMI成熟度第二級，可用於幫助需求管理的規劃與控制，建立追蹤機制，以及評估改變衝擊。 本篇論文以達成CMMI中需求發展和需求管理流程領域目標為前提，利用概念形成(Concept Formulation)和系統展示(System Representation)研究方法，並調適RUP中的需求工作流程(workflow)，最後發展出一個整合的需求管理架構-稱為IREQM(Integrated Requirements Management)，用於處理需求面的問題。本研究亦根據IREQM架構進行實作，發展出一套可協助軟體需求發展與管理的支援系統。最後，我們利用自我評鑑表，評估IREQM及依據IREQM實作的雛型系統與CMMI目標和執行方法相符的程度。 / Effective requirements management can help the software development process to ensure a high-quality software development and management process. In CMMI, the process area RD (Requirements Development) provides a set of goals, practices, and related features to develop customer and product requirements, and the process area REQM (Requirements Management) is to help establishing and appraising the quality of requirements management. Both issues are covered by the generic requirement management concerns. This study is conducted by the Concept Formulation and System Representation method to develop a systematic process to deal with the requirements issues in the software development process, in order to meet the RD and REQM goals in CMMI. The study proposes an integrated requirement management framework, called IREQM, tailored from the requirements workflow in RUP. A CMMI support system, to implement IREQM is established to facilitate the REQM and RD activities during the software development process. Finally, a self-appraisal checklist is used to evaluate the compliance of the IREQM framework and its implementation to the CMMI model.

Este trabalho de pesquisa propõe uma Estrutura para o Apoio a Detecção de Conflitos de Tráfego Aéreo em Rotas, com base no conceito CNS/ATM (Comunication, Navigation and Surveillance/Air Traffic Management), integrando o uso de técnicas, ferramentas e procedimentos de Engenharia de Software. Foram pesquisadas informações relacionadas ao sistema atual de controle de tráfego aéreo, com o objetivo de verificar quais eram as inovações propostas pelo CNS/ATM em relação ao sistema atual, auxiliando o autor na identificação das principais funcionalidades da estrutura proposta. Foi seguida uma metodologia de desenvolvimento baseada em técnicas de programação orientada a objetos denominada RUP (Rational Unified Process), composta pelas seguintes fases:Iniciação - responsável pela identificação inicial dos requisitos e funcionamento da estrutura;Elaboração - responsável pelo detalhamento das funcionalidades encontradas na fase de Iniciação;Construção - responsável pelo desenvolvimento da estrutura proposta;Transição - responsável pela entrega do produto final ao usuário.Testes, através de cenários, foram realizados com a estrutura desenvolvida, baseando-se nos modelos criados a partir dos requisitos, proporcionando a verificação e validação dos diversos conflitos detectados pela estrutura junto às funcionalidades e regras impostas por profissionais da área de controle de tráfego aéreo. Além desses testes envolvendo conflitos específicos, outros relacionados à quantidade de aeronaves suportadas pela estrutura, foram realizados. Dentre as principais contribuições deste trabalho de pesquisa, encontram-se a documentação, a modelagem, a prototipação, a simulação de conflitos de tráfego aéreo, a adaptação das funcionalidades de controle de tráfego aéreo atual ao CNS/ATM, a padronização de procedimentos para a detecção de conflitos em rota e o aumento da segurança em vôo proporcionada pela estrutura. Dentre as principais conclusões durante a pesquisa realizada encontram-se: a importância do FANS (Future Air Navigation System) no controle de fluxo de tráfego devido ao aumento previsto para os próximos anos, a importância no emprego de sistemas de posicionamento global, o compartilhamento de informações através da rede ATN (Aeronautical Telecommunications Network), a segurança proporcionada por simuladores na identificação antecipada de conflitos e o grande auxílio proporcionado por técnicas de orientação a objeto e pela metodologia RUP apoiada por ferramentas CASE (Computer Aided Software Engineering).

Choosing the Software Development Methodology is the very first step of any project; thus,has been a hot topic among, both, practitioners and academic people. After using plandrivensoftware development methodologies software development researchers came up withthe idea of agile software development methodologies as a masterpiece. Although, failurestories of some teams brought about fading the idea that agile methodologies are thebest recipe for any kind of development project. Considering the lack of studies in helpingpractitioners to select the most appropriate agile software methodology, this study aims atprovide the software development manager with a thorough knowledge of agile methodologiesand the criteria that should be considered, while selecting one of them. A case study is used asan empirical support. / Program: Magisterutbildning i informatik

No description available.

Försvarets materielverk (FMV), som förser Svenska försvaret med materiel, har en del av sin organisation belägen i Karlsborg nämligen test och evaluering av markstridssystem. Fotogruppen på test och evaluering önskar realtidsstyra en robotiserad kameraplattform av märket Vinten med hjälp av diverse olika positionsgivande system i form av joystick, Doppler-positionsradar, deras självutvecklade system UNIPOS samt en predikterad bana för avlossade projektiler. Projektets huvudsakliga mål blev därför att skapa ett styrsystem för att kontrollera kameraplattformen med hjälp av nämnda indatakällor. Den teoretiska referensramen samt litteraturstudien gav projektets deltagare den kunskapsbas, inom seriell kommunikation och dataprotokoll, som krävdes för att genomföra projektet. De gav även förståelse för hur tidigare liknande arbeten sett ut och valde utifrån detta att följa systemutvecklingsmodellen Rational Unified process (RUP). FMV uttryckte önskemål om att den huvudsakliga styrenheten skulle vara en PC för att möjliggöra fjärrstyrning samt enkel vidareutveckling av systemet. RUP användes för att strukturera upp arbetet samt säkerställa kvalitén på slutprodukten. Utvecklingsprocessen består, enligt RUP’s struktur, av ett antal iterationer som alla tillför någon funktion till systemet. I samråd och nära samarbete med personal på FMV utvecklades systemet och testades succesivt för att säkerställa kvalitén. En enkel manual togs även fram för att förenkla användandet av systemet. Samtliga önskade indatakällor behandlades på något sätt i projektet och resultatet blev ett portabelt system som kan köras på vilken PC som helst. Tester med drönare, granatkastare samt ett stegsvar har utförts för att verifiera att systemets funktion uppfyller de krav som satts upp samt utvärdera systemets möjligheter och begränsningar. Testen visade att realtidsstyrning är möjlig till viss grad med samtliga system och att systemets begränsningar ligger i fördröjningarna som finns både i signalöverföring samt kameraplattformens inbyggda filter för mjuka rörelser. / The Swedish Defence Material Administration (FMV) that supplies materials to the Swedish military, has a part of its organization located in Karlsborg called test and evaluation of land combat systems. The photogroup of test and evaluation wishes to control a robotized camera platform, of the brand Vinten, in real time using a number of different positioning systems like joystick, Doppler-position radar, their self-constructed system UNIPOS and using a predicted trajectory of a launched projectile. The main goal of the project is therefore to create a control system to maneuver the camera platform with the assistance of mentioned data sources. The theoretical framework and literature review gave the members of the project the knowledge base, in serial communication and data protocols, needed to complete the project and gave understanding about earlier similar projects and choose to follow the structure of the systems development model Rational Unified Process (RUP). FMV wanted the main control unit to be a PC to be able to remotely control the system and to be able to make further developments. RUP was used to give the work structure and to make sure the quality of the end product was satisfactory. The development process consists, in accordance with the RUP structure, of a number of iterations that all add some function to the system. In close cooperation with the staff at FMV the system is developed and continuously tested to ensure the quality. A simple manual has been developed to make usage of the system easier. Every data source wanted by FMV has been handled in some way throughout the project and the result was a portable system that can be ran on any PC. Tests using drones, grenade launchers and a response-test was performed to verify that the functions of the system lives up to the goals that were set up and to evaluate the systems possibilities and limitations. The tests showed that real time control is possible to some extent with all systems and that the limitations lies in the delays that exists both in signal transfers and in the camera platforms built in filters for soft movements.

Everyone is talking about the software development methods but these methods are categorised into the different parts and the most important are two categories, one is agile software development methods and second is using the traditional software development methods. Agile software methods are relatively considered to be quick and for the small teams. Our main mission is to check which method is better from each other, so for that purpose we go out in the software development market to meet the professional to ask about their satisfaction on these software development methods. Our research is based on to see the suitable method for the professionals; see the challenges on the adoptability of methods and which method is quicker. To perform this study we have gone through a survey questionnaire, and results are analysed by using mixed method approach. Results shows that professionals from both types of methods are satisfied but professionals with traditional methods are more satisfy with their methods with respect to development of quality software, whereas agile professionals are more satisfied with their methods with respect of better communication with their customers. With agility point of view, our study says that both methods have characteristics which support agility but not fully support, so in such case we need to customize features from both types of methodologies.

The diploma thesis focuses on project management – managing of software development activities. It explains a basic terms of given issue and it also deals with advantages and disadvantages of some known practices and methods which are often followed when developing software. The practical part includes an analysis and evaluation of concrete project. This project is then the base for designing an optimization of software development methodology. Designed optimization will be able to help manage similar projects in future.

How can you do a right measurement of culture as well as with other social sectors and with what can culture contribute when it comes to a town´s development? We found out that in Linköping the regional federation Ostsam recently (2005) started mapping the region's creative centers in order to look into the spreading of the culture in the county, and then use the uniqueness of the culture as an advantage in society- planning contexts. The reason was that both municipal - and State directions detected that the culture has a broader importance when it comes to building up society and infrastructure than earlier considered. This is called Cultural planning and is the foundation- method that Östsam used when working with their new projekt The creative sector. The outcome of the Östsam study resulted in an exciting study basis to work further on with and to examine through own demarcations and directions. This research manages the matter of the creative sector as an extension to the cultural sector. Our aim with this report is to find out the concept of the creative sector, what it stands for, and also to look into how the creative sector runs in practice.

<p>How can you do a right measurement of culture as well as with other social sectors and with what can culture contribute when it comes to a town´s development? We found out that in Linköping the regional federation Ostsam recently (2005) started mapping the region's creative centers in order to look into the spreading of the culture in the county, and then use the uniqueness of the culture as an advantage in society- planning contexts. The reason was that both municipal - and State directions detected that the culture has a broader importance when it comes to building up society and infrastructure than earlier considered. This is called Cultural planning and is the foundation- method that Östsam used when working with their new projekt The creative sector. The outcome of the Östsam study resulted in an exciting study basis to work further on with and to examine through own demarcations and directions.</p><p>This research manages the matter of the creative sector as an extension to the cultural sector. Our aim with this report is to find out the concept of the creative sector, what it stands for, and also to look into how the creative sector runs in practice.</p>

Modeliais grįsta sistemų architektūra (MDA) yra „Object Management Group“ (OMG) konsorciumo iniciatyva apibrėžti naują požiūrį į programų sistemų kūrimą remiantis modeliais ir automatizuota jų transformacija į programinį kodą. Siekdama standartizuoti šį požiūrį, OMG patvirtino visą eilę standartų, bet esminiai MDA principai ir praktikos glūdi modeliais grįstame sistemų kūrimo stiliuje, kuris yra fundamentalus programų sistemų inžinerijoje. MDA idėjos, pradžioje sukėlusios didelį entuziazmą IT bendruomenėje, ilgainiui peraugo į skepticizmą ir kai kurie autoriai atvirai pradėjo abejoti modeliais grįsto sistemų kūrimo perspektyva. Šiame darbe analizuojamos praktinio MDA taikymo programų sistemų kūrimo procese aspektai ir galimybės, analizuojami galimi sprendimai ir kliūtys, dėl kurių MDA požiūris gali būti sunkiai pritaikomas. Įvairių autorių įvardijami praktiniai MDA taikymo programų sistemų kūrimo procese sunkumai, didelės tam reikalingos investicijos, pastangos ir resursai, tinkamų instrumentų trūkumas, didelė standartų įvairovė ir sudėtingos technologijos iš dalies lėmė išaugusį skepticizmą MDA paradigmai. MDA apibrėžia naujus sistemų kūrimo principus ir standartais apibrėžia technologijas, kurios pagrindžia šiuos principus. Tai neišvengiamai įtakoja patį programų sistemų kūrimo procesą, kuris turi pasipildyti naujomis veiklomis, praktikomis ir technologijomis, kaip kurti sistemas taikant MDA požiūrį. Šiame kontekste būtinas tam tikras pragmatinis požiūris į MDA ir su juo... [toliau žr. visą tekstą] / Model Driven Architecture (MDA) is an approach to using models in software development, which states that models and model-based transformations are a key part of effective automated software development. The Object Management Group (OMG) has defined standards for representing MDA models, but the principles and practice of MDA are rooted in model-based styles of development that have been fundamental to software engineering from its earliest days. Unfortunately, early enthusiasm for Model Driven Architecture (MDA) has dissipated to the point that many people are openly skeptical of the value of any model-driven approach. This paper examines the practical realities of MDA, difficulties and challenges in adopting an MDA approach to software engineering process. While MDA requires additional efforts and high investment to be adopted in software engineering process, it doesn’t provide any means or guidelines for this. This paper argues that to be successful, a pragmatic MDA approach must be executed in context of a sound Enterprise Architecture providing an integrated business architecture and governance structure that enables an organization to respond to business requirements quickly and appropriately.