Mapping General System Characteristics to Non- Functional Requirements

The Function point analysis (FPA) method is the preferred scheme of estimation for project managers to determine the size, effort, schedule, resource loading and other such parameters. The FPA method by International Function Point Users Group (IFPUG) has captured the critical implementation features of an application through fourteen general system characteristics. However, Non- functional requirements (NFRs) such as functionality, reliability, efficiency, usability, maintainability, portability, etc. have not been included in the FPA estimation method. This paper discusses some of the NFRs and tries to determine a degree of influence for each of them. An attempt to factor the NFRs into estimation has been made. This approach needs to be validated with data collection and analysis.Comment: 5 page

Spacelab system analysis: A study of the Marshall Avionics System Testbed (MAST)

An analysis of the Marshall Avionics Systems Testbed (MAST) communications requirements is presented. The average offered load for typical nodes is estimated. Suitable local area networks are determined

Spacelab system analysis: A study of communications systems for advanced launch systems

An analysis of the required performance of internal avionics data bases for future launch vehicles is presented. Suitable local area networks that can service these requirements are determined

Study of microcomputer applications in police services

Issued as Final report, Project no. A-364

Multiple Access Protocols for Data Communications via VSAT Networks

One of the most significant advantages of VSAT Networks is the ability to link together many terminals at remote sites under a single manageable network and to adapt the performance characteristics of the network to the requirements of the type of data traffic presented to the network

Layered-MAC: An Energy-Protected and Efficient Protocol for Wireless Sensor Networks

In wireless sensor networks, the radio of the wireless sensor node happens to be the highest source of energy consumption. Hence, there is a need to focus on the MAC layer, as it controls access to the radio. While there are several existing techniques to make sensors more energy-efficient, not many of them consider the security aspects of energy efficiency. By this we mean, protecting energy from external attacks. The existing protocols focus mainly on either duty-cycling (Sensor-MAC, Time-out MAC) or clustering (Gateway MAC), as a way of conserving energy. One of such attacks to energy is the denial-of-sleep (DoSL) attack which is a specific kind of denial-of-service attacks designed to drain the energy of battery-powered sensors in a Wireless Sensor Network. This paper explains the development of a new MAC-layer protocol called Layered-MAC aimed at not just energy efficiency but energy protection against DoSL attacks. The protocol is implemented on the OMNET++ and Castalia simulator. The results from the simulation are then compared with two representative existing duty-cycled protocols (Time-out MAC and Sensor-MAC) and significant improvements are present. One of the benefits of the developed protocol is that, not only does it attempt to save energy, but it protects energy from DoSL attacks. There are two main contributions from this research – the first is the additional layer of network metrics (RSSI and LQI) consideration, based on the premise that protection/security is not possible without some form of measurement of assets, and the cluster head rotation which adds an extra layer of energy protection while considering energy efficiency

Software security requirements management as an emerging cloud computing service

© 2016 Elsevier Ltd. All rights reserved.Emerging cloud applications are growing rapidly and the need for identifying and managing service requirements is also highly important and critical at present. Software Engineering and Information Systems has established techniques, methods and technology over two decades to help achieve cloud service requirements, design, development, and testing. However, due to the lack of understanding of software security vulnerabilities that should have been identified and managed during the requirements engineering phase, we have not been so successful in applying software engineering, information management, and requirements management principles that have been established for the past at least 25 years, when developing secure software systems. Therefore, software security cannot just be added after a system has been built and delivered to customers as seen in today's software applications. This paper provides concise methods, techniques, and best practice requirements engineering and management as an emerging cloud service (SSREMaaES) and also provides guidelines on software security as a service. This paper also discusses an Integrated-Secure SDLC model (IS-SDLC), which will benefit practitioners, researchers, learners, and educators. This paper illustrates our approach for a large cloud system Amazon EC2 service