Security is today considered as a basic foundation in software development and therefore, the modelling and implementation of security requirements is an essential part of the production of secure software systems. Information technology organisations are moving towards agile development methods in order to satisfy customers' changing requirements in light of accelerated evolution and time restrictions with their competitors in software production. Security engineering is considered difficult in these incremental and iterative methods due to the frequency of change, integration and refactoring. The objective of this work is to identify and implement practices to extend and improve agile methods to better address challenges presented by security requirements consideration and management. A major practices is security requirements capture mechanisms such as UMLsec for agile development processes. This thesis proposes an extension to the popular Scrum framework by adopting UMLsec security requirements modelling techniques with the introduction of a Security Owner role in the Scrum framework to facilitate such modelling and security requirements considerations generally. The methodology involved experimentation of the inclusion of UMLsec and the Security Owner role to determine their impact on security considerations in the software development process. The results showed that overall security requirements consideration improved and that there was a need for an additional role that has the skills and knowledge to facilitate and realise the benefits of the addition of UMLsec.

This thesis investigates the building of a textual tracing language that operates at the model level to allow trace specification of textually modeled UML constructs. Current tracing approaches focus on manually injecting tracepoints into targeted systems at the source code level. Such approaches are useful in code-centric development styles where the majority of the code is handwritten. However, in the case of Model Driven Development (MDD), where models are utilized to generate some or all of the code, current tracing technology results in low level trace specification and generation of execution traces that are not aware of or linked to the originating model-level constructs. Dynamic analysis hence becomes harder for a modeler adopting an MDD approach. This field, which we call model-oriented tracing, is currently immature, with little pre-existing research. In this thesis, we present a textual model-level tracing language, implemented as part of Umple, that overcomes some of the limitations of existing tracing methods. The language facilitates model-level tracing, in a fashion very similar to code tracing. The language, which we call MOTL (Model-Oriented Tracing Language) allows tracing of UML associations, attributes and state machines. Constraints can be imposed to limit the scope of tracing. As a result of this work, modelers will gain the ability to specify traces of UML constructs at the model level without the need to modify the generated code, and then generate execution traces when the generated system is run. The resulting trace links back to the model constructs. Modelers can choose from among several tracing technologies including basic file or console output, Java logging framework, Log4J and LTTng. This thesis defines the language syntactically and semantically. Model-Driven Development (MDD) and Test-Driven Development (TDD) were followed to implement the language architecture to ensure high quality code generation. MOTL was used in the development in two of Umple subprojects. An empirical evaluation was conducted to evaluate the language’s usability.

Orientador : Manuel de Jesus Mendes / Tese (doutorado) - Universidade Estadual de Campinas, Faculdade de Engenharia Eletrica / Made available in DSpace on 2018-08-03T14:47:14Z (GMT). No. of bitstreams: 1 Silva_ClaudioRodriguesMunizda_D.pdf: 2971745 bytes, checksum: a6299b56a201bbcfbfd4061c1b532313 (MD5) Previous issue date: 2003 / Doutorado

This diploma thesis deals with the design of an information system for sharing documents and bibliographical citations with the main emphasis put on using a cloud solution. The theoretical part explains the terms related to cloud computing and its application, the importance of citation and methods for the evaluation of information systems. Subsequent chapters of the theoretical part explain why citation is important and what methods are used for the assessment of an information system. The practical part provides an overview of the currently available solutions for developing an implemented information system. Moreover, an outline of the system illustrated via UML diagrams is included.

Diploma thesis deals with business processes in the Service department of the company Schneider Electric Slovakia, spol. s .r. o. The main objective is optimization of processes. To reach this purpose, the SWOT analysis of the department and modeling of current state of selected processes are carried out, and subsequently appropriately chosen process analyses are applied. Source information were gained mainly by observing of process flow and communication with employees and management of the company.

Diploma thesis is focused on the process modelling and innovation of the information system. At the beginning of the thesis, there is modeled project management pro-cesses using BPMN notation. In next part of the thesis is analysed current state of the information system with UML notation. Finally, inovation of the information system are proposed and implemented using Nette Framework.

This work deals with creation of database information system for employee training and bonus calculation with direct connection on existing personal systems in Honeywell production company. The project makes provision for solution on dynamic database server and maximal usage of its potentiality for application development. The system dispose of access privileges containing several user roles and role of administrator. The system concept is realized in UML modeling language. The implementation is realized on Microsoft technologies. The system is generally implmented in 3 tiers: user interface, database component, data base model. The user interface is implemented in ASP.NET 2.0 with utilization of ASP.NET AJAX 1.0 technology. The database component is implemented using object oriented language Visual .NET C# and ADO.NET classes. Data base is relized on SQL Server 2000 in Transact-SQL language. The integral part of the project is also testing on sample data and application in live business on Honeywells company intranet.

Sketching software design models is a common and intuitive practice amongsoftware engineers. These informal sketches are transient in nature unlesstransformed into a formal model that can be reused and shared. Manualtransformation, however, is time-consuming and redundant, and a method toautomatically transform these sketches into a permanent and formal softwaremodel is lacking. This study addresses this gap by creating and testingSketchToPlantUML, a sketchrecognition and transformation tool that reduces theeffort of manually transforming static, sketched UML Class Diagrams (CDs) intoformal models. The artefact uses the OpenCV library to preprocess images,segment UML elements, identify geometric features, classify relationships andtransform the output into the equivalent, formal PlantUML model. Tested againsta dataset of 70 sketched CDs, the artefact achieved overall Precision and Recallvalues of 88% and 86% respectively, scoring highest on classes (0.92 / 0.96) andlowest on association relationships (0.76 / 0.76). While the approach providesinsight into image processing and object recognition using OpenCV, a morerobust and generalised solution for automating the transformation of UMLsketches into formal models is needed.

Non-functional requirements (NFRs) are a subset of requirements, the means by which software system developers and clients communicate about the functionality of the system to be built. This paper has three main parts: first, an overview of how non-functional requirements relate to software engineering is given, along with a survey of NFRs in the software engineering literature. Second, a collection of 161 NFRs is diagrammed using the Unified Modelling Language, forming a tool with which developers may more easily identify and write additional NFRs. Third, a lesson plan is presented, a learning module intended for an undergraduate software engineering curriculum. The results of presenting this learning module to a class in Spring, 2003 is presented.

No description available.