O design de sistemas automatizados inteligentes é fortemente dependente da etapa inicial de análise de requisitos, que além de suprimir possíveis incongruências - próprias desta fase inicial - provê um modelo inicial e funcional do sistema a ser implementado, capaz de orientar a definição dos parâmetros (design parameters) e em seguida a própria implementação. Um grande esforço tem sido empregado na área de Inteligência Artificial para definir planejadores automáticos confiáveis que possam ser usados na solução de problemas reais, que geralmente possuem um número elevado de parâmetros. Isto leva a uma situação onde métodos formais, geralmente aplicados em abordagens independentes de domínio, precisam ser aliados a métodos mais pragmáticos para produzir bons resultados. Seguindo esse princípio,o presente trabalho propõe um método de projeto no qual o usuário podem fazer a aquisição de conhecimento, modelar o domínio (tanto o domínio de aplicação quanto o domínio do problema de planejamento), fazer uma análise dinâmica do modelo e eventualmente verificá-lo usando linguagens conhecidas como UML, as Redes de Petri, e HTN, mantendo as características hierárquicas do problema. Esta abordagem demanda novos planejadores automáticos que consideram a abstração do sistema hierárquico, que é derivado de um modelo hierárquico de requisitos e de uma análise unificada feita também em redes de Petri hierárquicas. / The design of intelligent systems is strongly dependent of the requirements analysis initial stage, wich can remove possible inconsistencies - own this early stage - providing a primary functional model of the system being implemented. Besides that, it can be able to guide the definition of the parameters (design parameters) and then the implementation itself. A lot of effort has been employed in Artificial Intelligence field to define reliable automated planning systems that can be used to solve real problems, which generally have a large number of parameters. This leads to a situation where formal methods, generally applied to solve domain-independent problems, need to be combined with more pragmatic methods to produce good results. Following this principle, this work proposes a design method in which the user can make the acquisition of knowledge, model the domain (both the work domain and the planning problem domain), make a dynamic analysis of the model and eventually simulate it using well-kown language as UML, Petri Nets, and HTN, maintaining the hierarchical characteristics of the problem. This approach demands new automated planners who consider the abstraction of hierarchical system, which is derived from a hierarchical model requirements and an unified analysis made in hierarchical Petri nets.

Requirements analysis is an essential part of the System Development Life Cycle (SDLC) in order to achieve success in a software development project. There are several methods, techniques and frameworks used when expressing, prioritizing and managing requirements in IT projects. It is widely established that it is difficult to determine requirements for traditional systems, so a question naturally arises on how the requirements analysis is executed as AI solutions (that even fewer individuals can grasp) are being developed. Little research has been made on how the vital requirements phase is executed during development of AI solutions. This research aims to investigate the requirements analysis phase during the development of AI solutions. To explore this topic, an extensive literature review was made, and in order to collect new information, a number of interviews were performed with five suitable organizations (i.e, organizations that develop AI solutions). The results from the research concludes that the requirements analysis does not differ between development of AI solutions in comparison to development of traditional systems. However, the research showed that there were some deviations that can be deemed to be particularly unique for the development of AI solutions that affects the requirements analysis. These are: (1) the need for an iterative and agile systems development process, with an associated iterative and agile requirements analysis, (2) the importance of having a large set of quality data, (3) the relative deprioritization of user involvement, and (4) the difficulty of establishing timeframe, results/feasibility and the behavior of the AI solution beforehand.

Få studier har undersökt hur mobila arbetsprocesser kan integreras i verksamheter ur ett verksamhetsorienterat perspektiv, och bland organisationer råder brist på förståelse för, och långsiktiga strategier inom, företagsintern mobilitet. Denna studie undersöker hur en organisation kan förbereda sig inför förändring mot ett mobilare arbetsliv. För att besvara detta utfördes en litteraturstudie och en fallstudie bestående av dokumentstudier och intervjuer hos en organisation med särskilt utformad metodik inom området. Mognadsgraden kan utifrån resultaten anses relativt låg, och arbetet behöver lägga vikt på skapandet av förståelse för mobilitet och dess innebörd, där utmaningarna återfinns i hantering av förhållningssätt, organisationskultur, och ledarskap. Mobilitetsrelaterade behov var av både uppgiftsorienterad och social art, där olika tekniska lösningar föreslogs kunna bevara band mellan individer och organisation.  Det finns behov av mer longitudinella studier eftersom de signifikanta förändringarna antyddes ske över längre tid. En viktig del av kunskapsutvecklingen inom området handlar också om att lära från andras exempel, där denna studie utgör ett bidrag. / Few studies have examined how mobile work processes can be integrated into organizations from a business-oriented perspective, and among organizations there’s a lack of long-term strategies, and understanding, for internal business mobility. This study examines how an organization can prepare itself for change towards a mobile work life. In order to do this a literature review and case study involving document studies and interviews at an organization with specifically developed methodologies were conducted. The results showed that the state of maturity is still relatively low, and there is a need to focus on developing a more thorough understanding of mobility, where challenges involve handling attitudes, organizational culture and leadership. Mobility-related needs involve task-oriented and social aspects, where different technological solutions were suggested to maintain the connections between individuals and the organization. There is also a need for more longitudinal studies due to the results showing how the significant changes occur over a longer period of time. An important part of the development of knowledge concerning mobility also involves learning from others’ examples, where this study is a contribution.

Multimodale Anwendungen bieten den blinden Benutzern neue Möglichkeiten und Chancen, die durch Verlust des Sehsinnes entstandenen Defizite über andere Sinneskanäle auszugleichen. Die benutzerorientierte Gestaltung ist der sicherste Weg, um interaktive Systeme gebrauchstauglich zu gestalten. Dabei sind die Benutzer hauptsächlich an zwei Aktivitäten beteiligt. Dies sind die Nutzungsanforderungsanalyse und die Evaluation. Hinsichtlich dieser zwei Aktivitäten wurden in der vorliegenden Arbeit Usability-Methoden untersucht bzw. neu entwickelt, um die nutzerzentrierte Gestaltung multimodaler Anwendungen für blinde Benutzer zu unterstützen. Bezogen auf die Aktivität Nutzungsanforderungsanalyse wurde ein Verfahren entwickelt, welches speziell die Besonderheiten blinder Benutzer und multimodaler Anwendungen bei der Nutzungsanforderungsanalyse berücksichtigt. Zusätzlich wurden zwei Schritte des Verfahrens, die Erstellung mentaler Modelle und die Modalitätsauswahl, die speziell auf den Kontext multimodaler Anwendungen für blinde Benutzer ausgerichtet sind, weiter vertiefend untersucht. Für den Schritt Erstellung mentaler Modelle wurden zwei Erstellungsmethoden, Teaching-Back und Retrospective Think-Aloud, mit blinden Benutzern untersucht. Dabei sind sowohl die Gestaltung vom Teaching-Back als auch der Vergleich beider Methoden von Interesse. Für den Schritt Modalitätsauswahl stand die Analyse des multimodalen Nutzerverhaltens blinder Benutzer im Mittelpunkt. Vier Eingabemodalitäten, Sprache, Touchscreen-Gesten, Touchscreen-Tastatur und Touchscreen-Braille bzw. deren Kombinationen wurden unter Einfluss von acht Aufgabentypen bei der Bedienung einer mobilen multimodalen Navigationsanwendung untersucht. In Hinblick auf die Usability-Evaluationsmethoden wurde zuerst das Augenmerk auf die Auswertung und die Erhebung mentaler Karten von blinden Benutzern gerichtet, da sie eine wichtige Rolle bei der Entwicklung von Navigationssystemen spielen. Zwei Auswertungsmethoden für mentale Karten hinsichtlich des Überblicks- und Routenwissens wurden entwickelt. Beide Methoden ermöglichen es, die mentalen Karten anhand speziell entwickelter Bewertungskriterien, wie Anzahl der Elemente und Eigenschaften der Straßen, quantitativ zu bewerten. Bezüglich der Erhebung mentaler Karten wurden zwei Erhebungsmethoden – Rekonstruktion mit Magnetstreifen und verbale Beschreibung – mit blinden Probanden hinsichtlich unterschiedlicher Aspekten untersucht. In zwei weiteren Untersuchungen wurden taktiles Paper-Prototyping und computerbasiertes Prototyping für die frühen Entwicklungsphasen bzw. Labor- und synchroner Remote-Test für die späteren Entwicklungsphasen mit blinden Benutzern verglichen. Dabei wurden die Effektivität der Evaluation, die Erkenntnisse und Erfahrungen der Probanden sowie des Testleiters als Vergleichskriterien in beiden Untersuchungen eingesetzt.

Dieser Beitrag beschreibt das technologische Konzept und die praktische Realisierung einer universellen Telearbeitsumgebung. Dabei wird neben der Definition und Anforderungsanalyse von Telearbeit ein Architekturmodell für eine integrierte Arbeitsumgebung und die geplante prototypische Umsetzung auf der Basis von Web Services vorgestellt. Abschließend werden weitere Entwicklungs- und Ausbaumöglichkeiten des Konzeptes vorgestellt.

This work presents problems of software products field failure analysis and introduces terms a field failure and a system for field failures analysis. Rest of this work contains requirements analy­sis and design of one part of the system for field failures analysis a central. A part of the central is then implemented and design correctness and practical usability of the central is evaluated.

As part of a project within Saab Aeronautics, a Swedish Fighter Aircraft industry, this study was conducted. The fighter pilot is under immense pressure as he/she ventures into the complex environment that is airspace and air combat in a hostile area. The HMI (Human Machine Interface) is the pilot and aircrafts common denominator that leads to mission success but has its limitations. An Adaptive Human-Machine Interface (AHMI) is an HMI that is modified to help the pilot despite the situation he/she finds themselves in. The AHMI has many tasks but what gives it its edge is the adaptivity to different situations and to assist the pilot’s well-being. This can be done via proper visualization of information but also automation of lesser tasks. Mission success depends on physiological parameters such as mental workload and situational awareness to attain optimized operative performance. In this thesis we delve into the depths of what is important in AHMI and the requirements that are needed to produce and demonstrate the AHMI. The mapping of requirements onto simulators is an important aspect to move forward with the development of AHMI. Literature reviews and interviews were conducted in order to learn more about the domain and answer the research questions. The interviewees concur that the proper way of mapping requirements is dependent on what is supposed to be investigated. Is it a graphical component, principle, function or scenario? Through the comparison between the literature and thematic analysis through the interviews it was found that the mapping of requirements is dependent on what is to be investigated. Further, AHMI is deemed an effective support system for the pilot and that autonomy is effective to a certain extent. But when autonomy takes too much control the pilot loses situational awareness and therefore performs worse. Within the project, there is a common consensus between the interviewed subjects that AHMI is the way to move forward with fighter aircraft cockpit development.

[pt] No processo de desenvolvimento do software, atividades relacionadas ao Processo de Requisitos envolvem elicitação, modelagem, verificação e validação dos requisitos. O uso da linguagem natural no registro dos requisitos facilita a comunicação entre os participantes do processo, além de possibilitar que clientes e usuários validem requisitos sem necessitar de conhecimento extra. Por outro lado, na economia globalizada atual, o desenvolvimento de software por equipes geograficamente distribuídas está se tornando uma norma. Nesse cenário, atividades de verificação e validação de requisitos para um software de média ou alta complexidade podem envolver o tratamento de centenas ou milhares de requisitos. Com essa ordem de complexidade é importante que o engenheiro de software tenha apoio computacional para o desempenho adequado das atividades de aferição de qualidade. Neste trabalho estamos propondo uma estratégia que combina técnicas de processamento da linguagem natural (PLN) e agentes de software para apoiar as atividades de análise dos requisitos. Geramos visões textuais ou gráficas de grupos de requisitos relacionados; visões apóiam a análise de completude, a identificação de duplicidades e de dependências entre requisitos. Utilizamos técnicas de análise de conteúdo para apoiar a identificação de omissões em requisitos não funcionais. Também propomos uma estratégia para a construção ou atualização do léxico da aplicação, utilizando técnicas de PLN. Utilizamos agentes de software para implementar serviços que incorporam as estratégias referidas, e também para atuar como representantes dos participantes do projeto em desenvolvimento. / [en] In software development process, initial activities can involve requirements elicitation, modeling and analysis (verification and validation). The use of natural language in the register of the requirements facilitates the communication among stakeholders, besides offering possibilities to customers and users to validate requirements without extra knowledge. On the other hand, in the current global economy, software development for teams geographically distributed is becoming a rule. In this scenario, requirements verification and validation for medium or high complexity software can involve the treatment of hundreds or even thousand requirements. With this complexity order it is important to provide computational support for the software engineer execute quality activities. In this work we propose a strategy which combines natural language processing (NLP) techniques and software agents to support analysis activities. We have generated textual or graphical visions from groups of related requirements; visions help completeness analysis, identification of duplicities and dependences among requirements. We use content analysis techniques to support the identification of omissions in nonfunctional requirements. Also, we propose a strategy to construct the lexicon, using NLP techniques. We use software agents to implement web services that incorporate the related strategies, and also agents to act as personal assistants for stakeholders of the software project.

This diploma thesis describes both the theoretical and practical part of the process of design and implementation of interactive computer software for the~management of~the~quality control of the~devices, assigned by SIGMA GROUP a.s., more precisely its Energo division, which is engaged in the maintenance and repair of pumping equipment. The theoretical part explains the concept of user experience, its acquisition methods, specification of~requirements and interface design methods. The next part is focused on the description of the~formats used by common text editors. Within the theoretical part is described the design of the interactive application itself. In the practical part there is a description of the main parts of the system and the conclusions from the system testing.

[pt] A análise de requisitos desempenha um papel fundamental no processo de desenvolvimento de software. Neste sentido, representações de cenários baseados em linguagem natural são muitas vezes utilizados para descrever especificações de requisitos de software (SRS). Cenários descritos usando linguagem natural podem ser ambíguos e, às vezes, imprecisos. Este problema é parcialmente devido ao fato de que os relacionamentos entre os cenários são raramente representados explicitamente. Como os cenários são utilizados como entrada para as actividades subsequentes do processo de desenvolvimento de software (SD), é muito importante facilitar a sua análise; especialmente para detectar defeitos devido a informações erradas ou falta de informação. Este trabalho propõe uma abordagem baseada em Redes de Petri e técnicas de Processamento de Linguagem Natural como uma forma eficaz para analisar os cenários adquiridos, e que toma descrições textuais de cenários (em conformidade com um metamodelo definido neste trabalho) como entrada e gera um relatório de análise como saída. Para facilitar a análise automática, os cenários são transformados em Redes de Petri (Lugar/Transição) equivalentes. Os cenários e suas Redes de Petri resultantes podem ser analisados automaticamente para avaliar algumas propriedades relacionadas à desambiguidade, completeza, consistência e corretude. Os defeitos identificados podem ser rastreados até os cenários, permitindo a sua revisão. Nós também discutimos como desambiguidade, completeza, consistência e corretude das SRSs baseadas em cenários podem ser decompostas em propriedades relacionadas, e definimos heurísticas para encontrar indicadores de defeitos que prejudicam estas propriedades. Avaliamos nosso trabalho, aplicando a nossa abordagem de análise em quatro estudos de caso. Essa avaliação compara os resultados obtidos pela nossa abordagem automatizada contra os resultados obtidos por um processo de inspeção e com trabalhos relacionados. / [en] Requirements analysis plays a key role in the software development process. Natural language-based scenario representations are often used for writing software requirements specifications (SRS). Scenarios written using natural language may be ambiguous, and, sometimes, inaccurate. This problem is partially due to the fact that relationships among scenarios are rarely represented explicitly. As scenarios are used as input to subsequent activities of the software development process (SD), it is very important to enable their analysis; especially to detect defects due to wrong information or missing information. This work proposes a Petri-Net and Natural Language Processing (NLP) based approach as an effective way to analyze the acquired scenarios, which takes textual description of scenarios (conform to a metamodel defined in this work) as input and generates an analysis report as output. To enable the automated analysis, scenarios are translated into equivalent Place/Transition Petri-Nets. Scenarios and their resulting Petri-Nets can be automatically analyzed to evaluate some properties related to unambiguity, completeness, consistency and correctness. The identified defects can be traced back to the scenarios, allowing their revision. We also discuss how unambiguity, completeness, consistency and correctness of scenario-based SRSs can be decomposed in related properties, and define heuristics for searching defect indicators that hurt these properties. We evaluate our work by applying our analysis approach to four case studies. The evaluation compares the results achieved by our tool-supported approach, with an inspection based approach and with related work.