No description available.

This thesis investigates information systems development with special regard to the area of Geographical Information Systems. It addresses the area through the investigation of the software life-cycle development model and its augmentation by the use of prototyping. Observations are made on empirical experiments conducted to assess the usefulness of the new techniques of hypertext and hypermedia and their suitability within this field of study. This investigation is complemented by a case study, the Norfolk and Suffolk Broads Authority. The Norfolk and Suffolk Broads are designated by statute with similar status to the National Parks of Great Britain, and are managed by the Norfolk and Suffolk Broads Authority. Through cooperation with the Norfolk and Suffolk Broads Authority, a prototype information system was created. This system makes use of geographical data from the Broads Authority. The development stages of this system were used to conduct experiments for this thesis. The tools and techniques used for the development of this system are described. These include a hypertext tool called FIELD (Fully Integrated Environment for Layered Development) which has been especially designed for the complete storage of all information for each stage throughout this development. The use of this tool and hypertext for the development of the geographically based information system for the Norfolk and Suffolk Broads Authority are discussed.

The popularity of smart phones has risen throughout the years since first introduced. With the popularity of the devices growing so too has the number of malicious applications flooding the devices’ marketplaces. With more usage there becomes a larger target for malware and exploitation creation. As threats to these devices continue to grow there is a constant need for security to safeguard against these threats. Some attempts to protect smart phones involve building software to analyze applications running on the devices. This attempt has cut back on the amount of malicious software on the marketplace. These attempts however only catch malicious applications after they have been running. This dissertation presents the Secure Android Development Model. The goal of this model is to contribute to security of these devices by having a development model that implicitly builds security into applications. The model ensures a minimal amount of open permissions thus limiting the number of attack vectors that malicious software can make on the devices. By following the model, developers will have all information available during development to make appropriate security decisions in their applications.

<p>Currently, security is frequently considered late in software life cycle. It is often bolted on late in development, or even during deployment or maintenance, through activities such as add-on security software and penetration-and-patch maintenance. Even if software developers aim to incorporate security into their products from the beginning of the software life cycle, they face an exhaustive amount of ad hoc unstructured information without any practical guidance on how and why this information should be used and what the costs and benefits of using it are. This is due to a lack of structured methods.</p><p>In this thesis we present a model for secure software development and implementation of a security plug-in that deploys this model in software life cycle. The model is a structured unified process, named S3P (Sustainable Software Security Process) and is designed to be easily adaptable to any software development process. S3P provides the formalism required to identify the causes of vulnerabilities and the mitigation techniques that address these causes to prevent vulnerabilities. We present a prototype of the security plug-in implemented for the OpenUP/Basic development process in Eclipse Process Framework. We also present the results of the evaluation of this plug-in. The work in this thesis is a first step towards a general framework for introducing security into the software life cycle and to support software process improvements to prevent recurrence of software vulnerabilities.</p> / Report code: LiU-Tek-Lic-2008:11.

This master thesis deals with the design of extending UIS module for mobile devices. First part of this thesis is dedicated to the analysis and justification to the benefit of mobile devices with focus on available mobile platforms. Subsequently, this thesis describes theoretical backgrounds upon which is based my own solution in perspective of software life cycle and SCRUM project management.

Currently, security is frequently considered late in software life cycle. It is often bolted on late in development, or even during deployment or maintenance, through activities such as add-on security software and penetration-and-patch maintenance. Even if software developers aim to incorporate security into their products from the beginning of the software life cycle, they face an exhaustive amount of ad hoc unstructured information without any practical guidance on how and why this information should be used and what the costs and benefits of using it are. This is due to a lack of structured methods. In this thesis we present a model for secure software development and implementation of a security plug-in that deploys this model in software life cycle. The model is a structured unified process, named S3P (Sustainable Software Security Process) and is designed to be easily adaptable to any software development process. S3P provides the formalism required to identify the causes of vulnerabilities and the mitigation techniques that address these causes to prevent vulnerabilities. We present a prototype of the security plug-in implemented for the OpenUP/Basic development process in Eclipse Process Framework. We also present the results of the evaluation of this plug-in. The work in this thesis is a first step towards a general framework for introducing security into the software life cycle and to support software process improvements to prevent recurrence of software vulnerabilities. / <p>Report code: LiU-Tek-Lic-2008:11.</p>

<p>Software engineering tools are being used in the industry in order to improve the productivity and the quality of the software development process. The properties of those tools are being perceived to be unsatisfactory. For example, researchers have found that some problems are due to deficient integration among the tools. Furthermore, a continuing problem is that there is a gap between the IT education and real demand of tool-skills form IT industry. Consequently, knowledge is needed of the properties of software development tools as well an understanding of demanded tool-skill from the industry. </p><p>The purpose of this study is to survey commercial software development environment (SDEs) that are used today in professional software engineering and discuss their advantages adn disadvantages. A secondary goal of the study is to identify the actual requirements from the industry on the IT-education. </p><p>A questionnaire was sent out to 90 software developers and IT managers of 30 IT companies in Sweden. The results of the survey show that IT companies, for most part, use SDEs from commercial software vendors. Respondents report that common problems of the SDEs are the following: bad integration among the tools, problems to trace software artifacts in the different phases of the programming cycle, and deficient support for version control and system configuration. Furthermore, some tools are difficult to use which results in a time-consuming development process. </p><p>We conclude that future software development environments need to provide better support for integration, automation, and configuration management. Regarding the required tool-skills, we believe that the IT education would gain from including commercial tools that cover the whole software product lifecycle in the curriculum.</p>

Abstract - Mobile devices in the near future will need to collaborate to fulfill their function. Collaboration will be done by communication. We use a real world example of robotic soccer to come up with the necessary structures required for robotic communication. A review of related work is done and it is found no examples come close to providing a RANET. The robotic ad hoc network (RANET) we suggest uses existing structures pulled from the areas of wireless networks, peer to peer and software life-cycle management. Gaps are found in the existing structures so we describe how to extend some structures to satisfy the design. The RANET design supports robot cooperation by exchanging messages, discovering needed skills that other robots on the network may possess and the transfer of these skills. The network is built on top of a Bluetooth wireless network and uses JXTA to communicate and transfer skills. OSGi bundles form the skills that can be transferred. To test the nal design a reference implementation is done. Deficiencies in some third party software is found, specifically JXTA and JamVM and GNU Classpath. Lastly we look at how to fix the deciencies by porting the JXTA C implementation to the target robotic platform and potentially eliminating the TCP/IP layer, using UDP instead of TCP or using an adaptive TCP/IP stack. We also propose a future areas of investigation; how to seed the configuration for the Personal area network (PAN) Bluetooth protocol extension so a Bluetooth TCP/IP link is more quickly formed and using the STP to allow multi-hop messaging and transfer of skills.

Software engineering tools are being used in the industry in order to improve the productivity and the quality of the software development process. The properties of those tools are being perceived to be unsatisfactory. For example, researchers have found that some problems are due to deficient integration among the tools. Furthermore, a continuing problem is that there is a gap between the IT education and real demand of tool-skills form IT industry. Consequently, knowledge is needed of the properties of software development tools as well an understanding of demanded tool-skill from the industry. The purpose of this study is to survey commercial software development environment (SDEs) that are used today in professional software engineering and discuss their advantages adn disadvantages. A secondary goal of the study is to identify the actual requirements from the industry on the IT-education. A questionnaire was sent out to 90 software developers and IT managers of 30 IT companies in Sweden. The results of the survey show that IT companies, for most part, use SDEs from commercial software vendors. Respondents report that common problems of the SDEs are the following: bad integration among the tools, problems to trace software artifacts in the different phases of the programming cycle, and deficient support for version control and system configuration. Furthermore, some tools are difficult to use which results in a time-consuming development process. We conclude that future software development environments need to provide better support for integration, automation, and configuration management. Regarding the required tool-skills, we believe that the IT education would gain from including commercial tools that cover the whole software product lifecycle in the curriculum.

The Recursive Multi-Threaded (RMT) software process management tool gives software developers the following capabilities: break a large project into a sequence of prototypes (or threads) track these threads individually, and estimate the progress and completion date of the project from these individual threads. The goal of this project is to provide the RMT Tool with an ability to support multi-database for collaborative software development. As a demonstration, actual data is used from several previous algorithma projects.