Information Technology systems are in today's digitalized society taken for granted. Within the public sector there are, as in the private sector, a lot of digital systems that unfortunately are not entirely integrated into the municipality businesses. The systems are not coordinated with other systems that the workers interact with in their day-to-day activities. This has several effects such as unnecessary costs of licenses or support, not to mention wasted working hours. The purpose of digitalization to optimize businesses fails due to lack of control and structure in the systems used, what systems are acquired and for what purpose, and whether the systems are followed up and further worked on. To secure the integration of systems, requirement specifications and procurement processes need to be reviewed. There is also a need for investment to make sure the follow-up is done properly. Coordination, structure, and control is the answer to effectivizing and optimizing municipal activities using the possibilities enabled by digitalization. / Informationsteknologiska verksamhetssystem tas i dagens digitaliserade samhälle för givet. Inom den offentliga sektorn finns det, precis som i den privata, en hel del digitala system, som dessvärre inte är helt integrerade i verksamheterna. Systemen samspelar inte med andra system som medarbetare möter i vardagen. Detta följs av olika konsekvenser i form av onödiga kostnader av licenser eller support, för att inte tala om nedlagd arbetstid. Digitaliseringens syfte att optimera verksamheter fallerar på grund av att det finns en bristande kontroll och struktur på de system som finns i verksamheten, vilka system som köps in och till vad, samt huruvida systemen följs upp och arbetas vidare på. För att säkra systemintegrationen bör kravspecifikationer och upphandlingsprocessen ses över, samt lägga investeringsmedel på att uppföljningen blir gjord ordentligt. Samordning, struktur och kontroll är svaret för att effektivisera och optimera kommunala verksamheter med hjälp av digitaliseringens alla möjligheter.

No description available.

The Kano method1 was used in order to determine the benchmark requirements of an educational web portal. A comprehensive list of possible specifications for an educational portal was constructed by examining the characteristics of educational portals globally. This information was used to develop a questionnaire in accordance with the Kano method. A number of hand-picked expert users were asked to answer the questionnaire. The results obtained from these questionnaires were used to categorize the importance of each component of a web portal as a “one-dimensional”2 , “must-be”3 or “attractive”4 requirement. The components categorized as “must-be” requirements were used to generate the benchmark of the minimum specifications of an educational web portal. Copyright / Dissertation (MEd)--University of Pretoria, 2008. / Curriculum Studies / MEd / Unrestricted

Les outils d’aide à la preuve basés sur la théorie des types permettent à l’utilisateur d’adopter soit un style fonctionnel, soit un style relationnel (c’est-à-dire en utilisant des types inductifs). Chacun des deux styles a des avantages et des inconvénients. Le style relationnel peut être préféré parce qu’il permet à l’utilisateur de décrire seulement ce qui est vrai, de s’abstraire temporairement de la question de la terminaison, et de s’en tenir à une description utilisant des règles. Cependant, une spécification relationnelle n’est pas exécutable.Nous proposons un cadre général pour transformer une spécification inductive en une spécification fonctionnelle, en extrayant à partir de la première une fonction et en produisant éventuellement la preuve de correction de la fonction extraite par rapport à sa spécification inductive. De plus, à partir de modes définis par l’utilisateur, qui permettent de considérer les arguments de la relation comme des entrées ou des sorties (de fonction), nous pouvons extraire plusieurs comportements calculatoires à partir d’un seul type inductif.Nous fournissons également deux implantations de notre approche, l’une dans l’outil d’aide à la preuve Coq et l’autre dans l’environnement Focalize. Les deux sont actuellement distribuées avec leurs outils respectifs. / Proof assistants based on type theory allow the user to adopt either a functional style, or a relational style (e.g., by using inductive types). Both styles have advantages and drawbacks. Relational style may be preferred because it allows the user to describe only what is true, discard momentarily the termination question, and stick to a rule-based description. However, a relational specification is usually not executable.We propose a general framework to turn an inductive specification into a functional one, by extracting a function from the former and eventually produce the proof of soundness of the extracted function w.r.t. its inductive specification. In addition, using user-defined modes which label inputs and outputs, we are able to extract several computational contents from a single inductive type.We also provide two implementations of our approach, one in the Coq proof assistant and the other in the Focalize environnement. Both are currently distributed with the respective tools.

The aim of this work is to study methods for requirement determination and specification methods to create information system on the .NET platform which will be specialized for restaurant and bar establishments. The information system will be therefore process and archive informations about condition of goods, employee's schedule of working shifts, summary of incomes and expenses and book of norms.

Today there are no requirements on burglary protection in the building regulation “Boverketsbyggregler”. Instead SSF Stöldskyddsföreningen has developed norms for physical security.SSF 200:5 is a norm that treats burglary protection in buildings and business premises, and isused as a basis for the insurance companies own description of security classification.The main purpose of the report is to get an increased understanding of what requirementsregarding burglary protection there are, and who is demanding them. The report also aims toexplore how people in the industry deal with security related work in the design stage.The questions at issue are all related to burglary protection. To answer these questions threemethods have been used. Interviews/surveys, physical tests, and a comparison between SSF200:5 and the insurance companies description of security classification.The interviews show that the burglary protection can vary depending on who the claimant is.It shines a light on a problem that occurs in the construction process, that is, discussingsecurity related questions too late. This can lead to compromised burglar security andincreased construction costs.The comparison shows that SSF 200:5 is not fully comparable with the insurance companiesdescription of security classification. Easy measures like door and window locks can beequated, meanwhile more complicated measures like wall constructions, can not.Using the test results, alternative wall constructions that satisfy the norm have been presented.Also improvements of SSF 200:5 have been discussed in favor of the whole industry.

The main part in the testing of the software is in the generation of test cases suitable for software system testing. The quality of the test cases plays a major role in reducing the time of software system testing and subsequently reduces the cost. The test cases, in model de- sign stages, are used to detect the faults before implementing it. This early detection offers more flexibility to correct the faults in early stages rather than latter ones. The best of these tests, that covers both static and dynamic software system model specifications, is one of the chal- lenges in the software testing. The static and dynamic specifications could be represented efficiently by Unified Modelling Language (UML) class diagram and sequence diagram. The work in this thesis shows that High Level Petri Nets (HLPN) can represent both of them in one model. Using a proper model in the representation of the software specifications is essential to generate proper test cases. The research presented in this thesis introduces novel and automated test cases generation techniques that can be used within a software sys- tem design testing. Furthermore, this research introduces e cient au- tomated technique to generate a formal software system model (HLPN) from semi-formal models (UML diagrams). The work in this thesis con- sists of four stages: (1) generating test cases from class diagram and Object Constraint Language (OCL) that can be used for testing the software system static specifications (the structure) (2) combining class diagram, sequence diagram and OCL to generate test cases able to cover both static and dynamic specifications (3) generating HLPN automat- ically from single or multi sequence diagrams (4) generating test cases from HLPN. The test cases that are generated in this work covered the structural and behavioural of the software system model. In first two phases of this work, the class diagram and sequence diagram are decomposed to nodes (edges) which are linked by Classes Hierarchy Table (CHu) and Edges Relationships Table (ERT) as well. The linking process based on the classes and edges relationships. The relationships of the software system components have been controlled by consistency checking technique, and the detection of these relationships has been automated. The test cases were generated based on these interrelationships. These test cases have been reduced to a minimum number and the best test case has been selected in every stage. The degree of similarity between test cases is used to ignore the similar test cases in order to avoid the redundancy. The transformation from UML sequence diagram (s) to HLPN facilitates the simpli cation of software system model and introduces formal model rather than semi-formal one. After decomposing the sequence diagram to Combined Fragments, the proposed technique converts each Combined Fragment to the corresponding block in HLPN. These blocks are con- nected together in Combined Fragments Net (CFN) to construct the the HLPN model. The experimentations with the proposed techniques show the effectiveness of these techniques in covering most of the software system specifications.

The work investigates the cognitive styles of students who are learning in order to be a translator. It compares students from two universities, their cognitive styles and motivation to learn. / Работа посвящена исследованию когнитивных стилей студентов, которые учатся, чтобы стать переводчиком. В ней сравниваются студенты двух университетов, их когнитивные стили и мотивация обучения.

Software testing plays a fundamental role in software engineering as it ensures the quality of a software system. However, one of the major challenges of software testing is its costs since it is a time and resource-consuming process which according to academia and industry can take up to 50% of the total development cost. Today, one of the most common ways of generating testcases is through manual labor by analyzing specification documents to produce test scripts, which tends to be an expensive and error prone process. Therefore, optimizing software testing by automating the test case generation process can result in time and cost reductions and also lead to better quality of the end product. Currently, most of the state-of-the-art solutions for automatic test case generation require the usage of formal specifications. Such formal specifications are not always available during the testing process and if available, they require expert knowledge for writing and understanding them. One artifact that is often available in the testing domain is test case specifications written in natural language. In this thesis, an approach for generating integration test cases from natural language test case specifications is designed, applied and, evaluated. Machine learning and natural language processing techniques are used to implement the approach. The proposed approach is conducted and evaluated on an industrial testing project at Ericsson AB in Sweden. Additionally, the approach has been implemented as a tool with a graphical user interface for aiding testers in the process of test case generation. The approach involves performing natural language processing techniques for parsing and analyzing the test case specifications to generate feature vectors that are later mapped to label vectors containing existing C# test scripts filenames. The feature and label vectors are used as input and output, respectively, in a multi-label text classification process. The approach managed to produce test scripts for all test case specifications and obtained a best F1 score of 89% when using LinearSVC as the classifier and performing data augmentation on the training set. / Programvarutestning spelar en grundläggande roll i programvaruutveckling då den säkerställer kvaliteten på ett programvarusystem. En av de största utmaningarna med programvarutestning är dess kostnader eftersom den är en tids och resurskrävande process som enligt akademin och industrin kan ta upp till 50% av den totala utvecklingskostnaden. Ett av de vanligaste sätten att generera testfall idag är med manuellt arbete genom analys av testfallsspecifikationer, vilket tenderar att vara en dyr och felbenägen process. Därför kan optimering av programvarutestning genom automatisering av testfallsgenereringsprocessen resultera i tids- och kostnadsminimeringar och även leda till bättre kvalitet på slutprodukten. Nuförtiden kräver de flesta toppmoderna lösningarna för automatisk testfallsgenerering användning av formella specifikationer. Sådana specifikationer är inte alltid tillgängliga under testprocessen och om de är tillgängliga, så krävs det expertkunskap för att skriva och förstå dem. En artefakt som ofta finns i testdomänen är testfallspecifikationer skrivna på naturligt språk. I denna rapport utformas, tillämpas och utvärderas en metod för generering av integrationstestfall från testfallsspecifikationer skrivna på naturligt språk. Maskininlärnings- och naturlig språkbehandlingstekniker används för implementationen av metoden. Den föreslagna metoden genomförs och utvärderas vid ett industriellt testprojekt hos Ericsson AB i Sverige. Dessutom har metoden implementerats som ett verktyg med ett grafiskt användargränssnitt för att hjälpa testare i testfallsgenereringsprocessen. Metoden fungerar genom att utföra naturlig språkbehandlingstekniker på testfallsspecifikationer för att generera egenskapsvektorer som senare mappas till etikettsvektorer som innehåller befintliga C# testskriptfilnamn. Engenskaps och etikettsvektorerna används sedan som indata och utdata, respektive, för textklassificeringsprocessen. Metoden lyckades producera testskript för allatestfallsspecifikationer och fick en bästa F1 poäng på 89% när LinearSVC användes för klassificeringen och datautökning var utförd på träningsdatat.

Formal specification of software systems has been very promising. Critics against the end results of formal methods, that is, producing quality software products, is certainly rare. Instead, reasons have been formulated to justify why the adoption of the technique in industry remains limited. Some of the reasons are: • Steap learning curve; formal techniques are said to be hard to use. • Lack of a step-by-step construction mechanism and poor guidance. • Difficulty to integrate the technique into the existing software processes. Z is, arguably, one of the successful formal specification techniques that was extended to Object-Z to accommodate object-orientation. The Z notation is based on first-order logic and a strongly typed fragment of Zermelo-Fraenkel set theory. Some attempts have been made to couple Z with semi-formal notations such as UML. However, the case of coupling Object-Z (and also Z) and the Use Case Maps (UCMs) notation is still to be explored. A Use Case Map (UCM) is a scenario-based visual notation facilitating the requirements definition of complex systems. A UCM may be generated either from a set of informal requirements, or from use cases normally expressed in natural language. UCMs have the potential to bring more clarity into the functional description of a system. It may furthermore eliminate possible errors in the user requirements. But UCMs are not suitable to reason formally about system behaviour. In this dissertation, we aim to demonstrate that a UCM can be transformed into Z and Object-Z, by providing a transformation framework. Through a case study, the impact of using UCM as an intermediate step in the process of producing a Z and Object-Z specification is explored. The aim is to improve on the constructivity of Z and Object-Z, provide more guidance, and address the issue of integrating them into the existing Software Requirements engineering process. / Computer Science / M. Sc. (Computer Science)