Engineering secure software remains a significant challenge for today's software organizations as they struggle to understand the implications of security on their systems and develop systems that guarantee specified software security properties. The use of formal methods that are based on mathematical models has long been advocated in the development of secure systems, yet the promise of formal methods has not been realized. This is due to the additional discipline needed to formulate precisely the requirements and due complexities that often confront engineers. Further, the cost of development and the requisite learning curve of formal methods are quite high making them cost prohibitive to apply, especially for large software. The transition from requirements to design has been one of the most difficult steps in software development. Moreover, effective methods for deriving design from requirements that guarantee retention of the intended security properties remain largely unrealized on a repeatable and consistent basis. If security requirements are formalized and transformed into design using formal methods, the potential for security vulnerabilities would be diminished through better clarity, completeness, and consistency. Therefore, a requirements specification must be systematically transformable to a formal representation, and through effective formal methods the design can be derived such that the security properties are preserved and conveyed. This dissertation presents the FADES (Formal Analysis and Design for Engineering Security) approach that couples goal-oriented requirements specification with formal design specification to develop secure software in a constructive, provable and cost-effective way. To the best of our knowledge, FADES is the first security engineering approach that provides a systematic and automated bridge between semi-formal security requirements and formal design and implementation. FADES maintains the completeness and consistency of the security requirements specified with KAOS (Knowledge Acquisition for autOmated Specifications) when transformed to B formal specifications. Relaxing formality during requirements analysis enables security requirements to be better organized for producing more complete, consistent and clear requirements. The KAOS requirements model is then transformed to B, a popular formal representation used to derive and refine software systems. Security design specifications and implementation are produced using the B formal method which preserves the requisite security requirement properties. FADES treats security-specific elements in a systematic and constructive way while considering security early in the development lifecycle. Moreover, employing FADES provides better confidence for security evaluators in the evaluation of trusted software. A side effect of employing formal methods in development is the availability of sufficient traceability information at the various phases of development and maintenance allowing for more accurate impact analysis of security changes. FADES has been examined empirically both by security engineering experts and practitioners. Results obtained from the controlled experiments compare FADES to other formal methods, and show that FADES preserves security properties while maintaining better consistency, quality, and completeness. This is accomplished at a lower cost and with better results. These results have been evaluated by academic and industry experts working in the area of security and formal methods. / Ph. D.

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.

The goal of Master's thesis is analysis of suitability of Unicorn Universe service, which is operated by Unicorn Company, for implementation of PRINCE2 project management methodology. Theoretical and Methodological part of Master's thesis includes description of PRINCE2 methodology and description of methods, which are used for requirements analysis and analysis of Unicorn Universe service. The analysis of Unicorn Universe service confirmed that this service is suitable for implementation of PRINCE2 methodology. This suitability is also proven by implementation of chosen part of PRINCE2 methodology. The Master's thesis recommends the implementation of PRINCE2 methodology to Unicorn Universe service. There are estimated economical and non-economical benefits, which are brought by this implementation to Unicorn and Unicorn its clients.

This diploma thesis deals with the requirements engineering as one of the key areas of development of software applications. By requirements prospective users express their needs and goals which shall be achieved using the developed application. The correctness and completeness of the requirements is thus critical for the success of any software project. The main objective of this dissertation is determination of steps which must be made to improve quality of requirements on real software project in Czech financial institution. This is achieved by analysis of current requirements development process as well as by analysis of the sample of specific requirements. One part of the carried out analysis focuses also on the revision of actual settings of Atlassian JIRA application which is used for requirements management. Based on the analysis some crucial shortcomings are identified and steps for their elimination are introduced. This includes, inter alia, manual of how to specify correct requirements and checklists for different actors who work with requirements. The theoretical part gives a comprehensive overview of selected techniques and practices which are applicable for requirements gathering and analysis. Every mentioned technique is then evaluated from the perspective of its usability in the environment of large Czech bank. This overview can be useful both for junior analytics as a collection of best practices and for senior analytics as an overview of possible areas for their professional development.

In der vorliegenden Arbeit wird eine emirische Untersuchung vorgestellt, in der mittels eines multimethodalen Zuganges eine Anforderungsanalyse für intermediäre Tätigkeiten umgesetzt wurde. Genutzt wurden zur Anforderungsanalyse Experteniterviews, eine Anwendung der Grid-Technik, sowie die Critical-Incidence-Technique.

Covid-Pandemin i början av 2020 har på ett eller annat sätt påverkat och begränsat hur anställda arbetar. Flera förändringar har skett som att företag med förutsättningarna förlagt arbetet till de anställdas hem. Detta har bidragit till att spontana interaktioner minskat, nya arbetsmetoder har formats och nya verktyg lanserats. Denna nya situation har medfört en rad utmaningar och möjligheter kring hur anställda samarbetar och delar kunskap kring kundbehov. Syftet med uppsatsen har varit att undersöka hur mjukvaruföretag har anpassat metoder, aktiviteter och arbetsprocesser vid utvecklingsarbetet av mjukvara. Syftet besvaras genom att utreda processerna vid krav och behovsanalys samt till att kartlägga samarbetsverktyg, arbetssituationen hemifrån, interaktioner inom projektgruppen samt vilka möjligheter och hinder som finns vid kontakt med kunder. En kvalitativ intervjustudie genomfördes på två mjukvaruföretag med sex informanter inom olika roller i en projektgrupp med tre krav: att de arbetat på distans under pandemin, att de har kundkontakt samt är involverade i utveckling av mjukvara.  Resultatet visar att distansen leder till möjligheter i kombinationen arbets- och privatliv exempelvis ingen restid, lättare att planera in aktiviteter som barnlämning och hämtning. Vidare pekar resultatet på utmaningar och svårigheter i digitala interaktioner mellan arbetskollegor och kunder som att det exempelvis är svårt att tolka kroppsspråk, ansiktsuttryck och tystnad samt att spontana interaktioner minskat. Utmaningarna leder till att det kan bli svårt att uppfatta tyst kunskap vilket kan påverka arbetet med kravanalys och i sin tur slutprodukten.  Resultatet analyserades genom att betrakta hur kunskap kring kundbehov skapas exempelvis vilka metoder som används samt vilka förutsättningar som projektgruppen lever upp till för framgångsrik kunskapsdelning på distans. Analysen visar att den ökade användningen av digitala verktyg har skapat en social acceptans för digitala möten vilket resulterat i frekvent kontakt med kund samt skapande av mer underlag som exempelvis inspelade möten. När arbetet sker uteslutande via digitala verktyg kan fler roller involveras tidigare i utvecklingsprocessen. Då kommunikationen sker digitalt kan en minskning i förståelse för kundens behov upplevas då exempelvis informella möten inte längre sker samt att metoder som observationer inte längre används. Projektgrupper bör anpassa sig för att möta utmaningarna som distansen medför genom att exempelvis minst en gång om dagen träffa kollegorna i digitala träffar i syfte att ingen ska känna sig ensam och för att stärka samhörigheten. Digitala intervjuer och återkoppling med kund sker oftare och leder till ökad mängd lagrad data som exempelvis inspelningar och mötesanteckningar. Ökningen behöver hanteras i syfte att den blir lättillgänglig för projektmedlemmar. Vidare försöker projektgrupper anpassa sig till minskningen av fysiska interaktioner genom att aktiviteter som observationer och workshops inte längre används. / The Covid-Pandemic at the beginning of 2020 has in one way or another affected and limited how employees work. Changes such as companies with the possibility relocating the work to the employees' homes, changes in spontaneous interactions, new working methods have been formed and new tools have been launched. This new situation has led to several challenges and opportunities regarding how employees collaborate and share knowledge about customer needs. The purpose of the thesis has been to investigate how software companies have adapted methods, activities and work processes. The purpose is answered by investigating the processes for requirements and needs analysis and for mapping collaboration tools, the work situation from home, interactions within the project group and the opportunities and obstacles that exist in contact with customers. A qualitative interview study was conducted at two software companies with six informants in different roles with three requirements: that they worked remotely during the pandemic, that they have customer contact and are involved in software development. The results show that distance work leads to opportunities in the combination of work and private life, for example no travel time and easier planning of picking up children from school. Furthermore, the results point to challenges and difficulties in digital interactions between work colleagues and customers in that, for example, it is difficult to interpret body language, facial expressions and silence and that spontaneous interactions have decreased. The challenges lead to becoming difficult to perceive tacit knowledge, which can affect the work with requirements analysis and in turn the product.  The results were analysed by considering how knowledge about customer needs is created, for example which methods are used and which conditions the project group lives up to for successful knowledge sharing at a distance. The analysis shows that the increased use of digital tools has created a social acceptance for digital meetings, which has resulted in frequent contact with customers and the creation of more data in the form of, for example, recorded meetings. When the work is done exclusively with digital tools, more roles can be involved earlier in the development process. When communication takes place digitally, a reduction in understanding of the customer's needs can be experienced when, for example, informal meetings no longer take place and methods such as observations are no longer used. Project groups should adapt to meet the challenges posed by the distance by, for example, meeting colleagues in digital meetings at least once a day for no one to feel alone and to strengthen cohesion. Digital interviews and customer feedback take place more often and lead to an increased amount of stored data in the form of, for example, recordings and meeting notes. The increase in data needs to be managed for it to be easily accessible to project members. Furthermore, project groups try to adapt to the reduction in understanding and perception of tacit knowledge by no longer using activities such as observations and workshops.

Un développement d'un système débute par la constitution, dans la phase de spécification des besoins, d'un cahier des charges dans lequel un ensemble de scénarios d'utilisation du système est défini avec les contraintes auxquelles il doit obéir, dans lequel chaque scénario est un simple exemple d'exécution du système à concevoir. Une fois que tous les scénarios sont précisés, on obtient une description complète des interactions entre les composants. Toutefois, cette spécification n'est pas directement implémentable, car il est difficile, surtout pour les systèmes les plus complexes, d'apercevoir le comportement d'un système dans sa globalité directement à partir des scénarios. C'est pour cela que ces derniers sont souvent intégrés à d'autres modèles, utilisés dans la conception détaillée, qu'on appelle "les modèles de comportement", en particulier les machines à états [Harel 87] qui permettent de passer de la vue partielle à la vue globale du système afin de répondre à différents problèmes comme la validation du comportement ou la détection des inconsistances au sein du système. Notre thèse a pour but, d'une part, de recenser et étudier différents langages de scénarios, particulièrement les diagrammes de séquences UML et les diagrammes MSC's, et d'autre part de proposer une méthode se synthèse automatique permettant de générer des modèles exécutables à évènements discrets DEVS [Zeigler 76] à partir d'une base de scénarios décrivant le comportement fonctionnel du système. Les modèles obtenus sont déterministes et avec une sémantique formelle qui garantit une interprétation unique de chaque élément des modèles. / A development of a system begins with the constitution, in the phase of requirements analysis, a specification in which a set of scenarios describing the behavior of the system is defined with the constraints that it must obey, where each scenario is a partial representation of the system behavior. However, this specification is not directly implementable, because it is difficult, especially for more complex systems, to observe the global behavior of a system directly from scenario. That is why they are often integrated with other models used in the detailed design, called "behavioral models", in particular State Machines [Harel 87], who allow to move from partial to global view of the system in order to answer different problems such as validation of the behavior or the detection of system inconsistencies. Our thesis aims, firstly, to study different languages of scenarios, especially UML sequence diagrams, and MSC's (Message Sequence Charts), and secondly to propose an automatic synthesis method who generate executable discrete event DEVS models [Zeigler 76] from scenarios describing the desired behavior of a system. The resulting models are executable and deterministic with a formal semantics that ensures a unique interpretation of each element of models. The use of final models simulation traces, taking into account the coverage of the simulation compared to the number of states and transitions visited, allow validating the behavior.

This dissertation titled Content management systems and their implementation focuses in its theoretical part on the terms content and content management. Then it defines particular types of content management systems and their functions, both the general ones and the specific ones for particular types of systems. It also focuses on the using of particular terms in the field of content management systems and it defines some differences in their interpretation. In the theoretical part it also describes how the organization applying the project approach to implementing of content management systems as from requirements setting through the selection criteria for comparing and selecting the appropriate system. The output of the practical part is the selection of suitable web content management system for Vyšší odborná škola a Obchodní akademie Chotěboř. The practical part is an analysis of requirements, determination of appropriate criteria for the selection system, a comparison of systems based on these criteria, cost-benefit analysis and feasibility study.

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.

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.