Context. With the entry of smart-phones on the market in the beginningof 2007, the integration of an mp3 player, camera and gps into an all in onedevice. As the integration was realized, creating and storing own contentbecame easier. Therefore the need of more storage became a problem as thesmart-phones were limited in capacity. The 3G network was on the rise andthe cloud solutions could help to contribute to the storage problems usersstarted to have. Objectives. In this study we will evaluate what can be done with use casesin terms of quality attributes, seeing it from a users perspective by havingusers rank use cases for cloud services. With further investigation we willmake a contribution of what the differences between public and personalclouds are. Methods. Use-cases were found by the conducted empirical study andwere based on a Systematic mapping review. In this review, a number ofarticle sources are used, including Google search, Bth summon and Googlescholar. Studies were selected after reading the articles and checked if thepapers matched our defined inclusion criteria. We also designed a surveywith variable amount of questions depending on what the participant wouldanswer. The questions were featured in terms of functionality interpretedfrom the use-cases found in the SLM. Results. Through our SLM we found six different use-cases which were Recovery, Collaborative working, Password protection, Backup, Version tracking and Media streaming. The identified quality attributes gave two or moremappings to their corresponding use-case. As for the comparison betweendifferent clouds, only two out of six use-cases where implemented for the Personal cloud. Conclusions. This gave us the conclusion that the vendors have beenmostly focusing on the storage part of the Personal cloud, but there are solutions in order to increase the functionalities. Those solutions will probably not fit everyone as it includes open source software, with skills of handling installation and other procedures by the user.

Multimedia och informationssystem integreras allt mer. I detta arbete beskrivs informationssystem med multimedialt gränssnitt som multimediasystem. Likväl integreras utvecklingsarbetet och utvecklare från skilda discipliner arbetar med utveckling av en gemensam produkt. Innehållsproducenter och tekniker, med skilda fokus och skilda referensramar, arbetar gemensamt. På grund av skilda referensramar uppstår frekventa kommunikationsproblem. I detta arbete undersöks huruvida Use Case som beskrivningsteknik kan användas för att reducera kommunikationsproblem mellan innehållsproducenter och tekniker i utveckling av webbaserade multimediasystem. I detta arbete har en intervjustudie genomförts med utvecklare av webbaserade multimediasystem samt en literaturstudie genomförts. Resultatet av undersökningen visar att det är möjligt att använda Use Case som beskrivningsteknik i utveckling av webbaserade multimediasystem. Undersökningen visar även att Use Case som beskrivningsteknik kan användas i ett kommunikativt syfte mellan innehållsproducenter och tekniker i utveckling av webbaserade multimediasystem.

Dlouhodobě trvající projekty patří do kategorie projektů majících zvláštní charakteristiky. Tato diplomová práce obsahuje mimo jiné studii situace příkladu existujícího dlouhodobě trvajícího projektu a poukazuje na důležité okolnosti, které ovlivňují práci role business analyst (byznys analytika). Na základě studia konkrétního případu je prezentován koncept nové metodologie pro roli byznys analytika, jehož cílem je práci této role zpřehlednit a zefektivnit. Byznys analytik jako role je zkoumán z hlediska postupu jeho činností, vztahu k ostatním projektovým rolím a také k zákazníkovi a ostatním rolím zainteresovaným na projektu. Nový návrh metodiky je zaměřen na minimalizaci problémů a rizik identifikovaných v rámci studia případového projektu. Definuje rozsah činností byznys analytika a techniky, jakými jsou tyto činnosti vykonávány. Celá metodika je podpořena specifikací dokumentů relevantních pro práci byznys analytika, což představuje zejména dokumenty pro samotnou správu požadavků, řízení toku nových požadavků, specifikaci řešení pokrývajících požadavky a hodnocení naplnění zákazníkových očekávání. Všechny části práce jsou zpracovány s ohledem na specifika prostředí dlouhodobě trvajících projektů, kde je zvýšená míra fluktuace členů projektového týmu a nemožnost dlouhodobě alokovat zkušené profesionály.

yes / This paper presents a structured approach for systems requirements analysis that integrates use case modelling with a coherent flows based approach for describing interface exchanges based on the Interface Analysis Template. The approach is discussed in the context of current frameworks for requirements elicitation from the engineering design and systems engineering domains, and it is illustrated with an automotive case study. This illustrates the strength of the framework to support structured multi-domain and multi-disciplinary analysis of requirements for complex systems.

Popular Object Oriented size metrics and estimation methods are examined. A case study is conducted. Five of the methods (&ldquo / LOC&rdquo / , &ldquo / OOPS&rdquo / , &ldquo / Use Case Points Method&rdquo / , &ldquo / J.Kammelar&rsquo / s Sizing Approach&rdquo / and &ldquo / Mark II FP&rdquo / ) are applied to a project whose requirements are defined by means of use cases. Size and effort estimations are made and compared with the actual results of the project.

A preocupação da engenharia de software esteve por muito tempo relacionada a aspectos da funcionalidade do sistema, ou seja, com \"o que\" e \"como\" fazer e não com o \"por que\" fazer. Tais aspectos, envolvidos nos processos existentes, buscam a definição das propriedades desejadas, em lugar de observarem a informação de uma forma mais ampla, começando com as necessidades do próprio negócio, ou dos objetivos dos sistemas nele embutidos. As técnicas de análise estruturadas, diagrama de fluxo de dados e modelagem entidade e relacionamento modelam importantes conceitos para o desenvolvimento de sistemas, mas não buscam por soluções alternativas inovadoras aos problemas da organização. É comum encontrar situações onde o sistema não satisfaz às reais necessidades do negócio, embora esteja tecnicamente correto. O entendimento dos aspectos sociais, organizacionais, técnicos, jurídicos e econômicos é essencial para a realização de um bom trabalho de engenharia de requisitos. Nesse sentido, a modelagem organizacional facilita a compreensão do ambiente empresarial e é reconhecida como uma atividade valiosa pela engenharia de requisitos. O modelo organizacional representa o \"mundo\" onde se aplicam as regras do negócio. O entendimento das regras do negócio é muito importante para a organização ser flexível em um ambiente de crescente competitividade. Com a necessidade de se ter a modelagem dos aspectos relativos à organização para que o sistema atenda as suas reais necessidades, o presente trabalho tem como objetivo investigar o processo de desenvolvimento de software buscando conhecer técnicas ou métodos que atendem aos requisitos organizacionais, enfatizando o uso de regras do negócio com a finalidade de obter a especificação de requisitos. / The software engineering\'s focus were for a long time related to system\'s functionality aspects, or with \"what\" and \"how\" to do, and not with \"why\" to do. Those aspects in the existents process are looking for the definition of the desired proprieties instead observe the information in a more large aspect, beginning with the business needs itself or the systems goals inserted in it. The structure analysis techniques, flux data diagram, and relationship and entity modeling form important concepts for systems development but do not search for innovating alternatives solutions for organization\'s problems. It is very common to find situations were the system does not satisfy the real business needs, thought it is technically correct. The comprehension of social, organizational, technical, juridical and economics aspects are essential for a good realization of requirements in engineering work. In that way the enterprise modeling makes the business environment comprehension easier and is recognized as a value activity by the requirements engineering. The enterprise model represents the \"world\" where the business rules are applied. The comprehension of the business rules is very important so the organization can be flexible in a growing competitive environment. With the necessity to have a modeling of the relative aspects to the organization so the system can accomplish the real needs, this present research has the objective to investigate a software development process trying to find techniques or methods that answer the enterprise\'s requirement, emphasizing the use of business rules to obtain the specifics requirements.

A preocupação da engenharia de software esteve por muito tempo relacionada a aspectos da funcionalidade do sistema, ou seja, com \"o que\" e \"como\" fazer e não com o \"por que\" fazer. Tais aspectos, envolvidos nos processos existentes, buscam a definição das propriedades desejadas, em lugar de observarem a informação de uma forma mais ampla, começando com as necessidades do próprio negócio, ou dos objetivos dos sistemas nele embutidos. As técnicas de análise estruturadas, diagrama de fluxo de dados e modelagem entidade e relacionamento modelam importantes conceitos para o desenvolvimento de sistemas, mas não buscam por soluções alternativas inovadoras aos problemas da organização. É comum encontrar situações onde o sistema não satisfaz às reais necessidades do negócio, embora esteja tecnicamente correto. O entendimento dos aspectos sociais, organizacionais, técnicos, jurídicos e econômicos é essencial para a realização de um bom trabalho de engenharia de requisitos. Nesse sentido, a modelagem organizacional facilita a compreensão do ambiente empresarial e é reconhecida como uma atividade valiosa pela engenharia de requisitos. O modelo organizacional representa o \"mundo\" onde se aplicam as regras do negócio. O entendimento das regras do negócio é muito importante para a organização ser flexível em um ambiente de crescente competitividade. Com a necessidade de se ter a modelagem dos aspectos relativos à organização para que o sistema atenda as suas reais necessidades, o presente trabalho tem como objetivo investigar o processo de desenvolvimento de software buscando conhecer técnicas ou métodos que atendem aos requisitos organizacionais, enfatizando o uso de regras do negócio com a finalidade de obter a especificação de requisitos. / The software engineering\'s focus were for a long time related to system\'s functionality aspects, or with \"what\" and \"how\" to do, and not with \"why\" to do. Those aspects in the existents process are looking for the definition of the desired proprieties instead observe the information in a more large aspect, beginning with the business needs itself or the systems goals inserted in it. The structure analysis techniques, flux data diagram, and relationship and entity modeling form important concepts for systems development but do not search for innovating alternatives solutions for organization\'s problems. It is very common to find situations were the system does not satisfy the real business needs, thought it is technically correct. The comprehension of social, organizational, technical, juridical and economics aspects are essential for a good realization of requirements in engineering work. In that way the enterprise modeling makes the business environment comprehension easier and is recognized as a value activity by the requirements engineering. The enterprise model represents the \"world\" where the business rules are applied. The comprehension of the business rules is very important so the organization can be flexible in a growing competitive environment. With the necessity to have a modeling of the relative aspects to the organization so the system can accomplish the real needs, this present research has the objective to investigate a software development process trying to find techniques or methods that answer the enterprise\'s requirement, emphasizing the use of business rules to obtain the specifics requirements.

Use cases are textual artifacts used to define the expected behavior of a system. However, use cases become more complicated when applied in a product line context since they need to define the behavior of several systems. Product line use cases require knowledge of commonality and variability concepts, which all involved stakeholders do not necessarily possess. Product-specific use cases are more understandable since they do not include variability information. Therefore, it would be beneficial to derive product-specific use cases from the product line use cases once the variability has been bound. This derivation could alleviate communication and help create a shared understanding of the product's expected behavior amongst diverse stakeholders.  In this thesis work, we have implemented a tool that can perform this type of derivation. The tool is divided into two collaborating parts. The first part is an extension to DOORS, which is responsible for creating and maintaining product line use cases. The second part is a third-party application responsible for binding the variability and deriving product-specific use cases. This tool was evaluated using a questionnaire with participants from Alstom, a company within the railway transportation domain. The evaluation showed that the tool has potential as a vehicle for communication amongst diverse stakeholders. / Use cases är textuella artefakter vilka används för att definiera det förväntade beteendet hos system. Dock så blir use cases mer komplicerade när de appliceras inom en produktionslinje-kontext, eftersom de då behöver definiera beteendet av flera olika system. Användandet av produktionslinje use cases kräver kännedom av kommonalitet och variabilitet koncept, vilket alla inblandade delägare inte nödvändigtvis behärskar. Därför skulle det vara gynnsamt om man kunde derivera produktspecifika use cases från produktionslinje use cases när dess variabilitet har bundits. Denna derivation skulle kunna underlätta kommunikation och skapa en gemensam förståelse av produktens förväntande beteende bland delägare med olika bakgrunder.    I detta avhandlingsarbete har vi implementerat ett verktyg som kan utföra denna typ av derivation. Verktyget är uppdelat i två samarbetande delar. Den första delen är ett tilläggsprogram till DOORS, vilken är ansvarigt för att skapa och underhålla produktionslinje use cases. Den andra delen är en tredjeparts applikation vilken är ansvarig för att binda variabiliteten och derivera fram produktspecifika use cases. Verktyget evaluerades med ett frågeformulär med tio deltagare från Alstom, ett företag inom järnvägstransport området. Denna evaluering visade att verktyget har potential att användas som ett fordon för kommunikation mellan delägare med olika bakgrunder.

Leaves 112 and 136 folded. / Digitized by Kansas State University Libraries

ITC/USA 2007 Conference Proceedings / The Forty-Third Annual International Telemetering Conference and Technical Exhibition / October 22-25, 2007 / Riviera Hotel & Convention Center, Las Vegas, Nevada / CTEIP has launched the integrated Network Enhanced Telemetry (iNET) project to foster advances in networking and telemetry technology to meet emerging needs of major test programs. In the past these programs have been constrained by vendor proprietary equipment configuration utilities that force a significant learning curve on the part of instrumentation personnel to understand hardware idiosyncrasies and require significant human interaction and manipulation of data to be exchanged between different components of the end-to-end test system. This paper describes an ongoing effort to develop a measurement-centric data model of airborne data acquisition systems. The motivation for developing such a model is to facilitate hardware and software interoperability and to alleviate the need for vendor-specific knowledge on the part of the instrumentation engineer. This goal is driven by requirements derived from scenarios collected by the iNET program. This approach also holds the promise of decreased human interaction with and manipulation of data to be exchanged between system components.