Requirements Research Papers - Academia.edu (original) (raw)

As one of the two basic aims in the key fields of intervention in the National Program for Development of the Education in the Republic of Macedonia for 2005-2015, the issue of increasing the primary education, from 8 to 9 years, was... more

As one of the two basic aims in the key fields of intervention in the National Program for Development of the Education in the Republic of Macedonia for 2005-2015, the issue of increasing the primary education, from 8 to 9 years, was posed. The requirements in this period are mainly initiated by the developmental characteristics of the children. The need for more intensive application of play and the activities of play has been shown to be the most appropriate approach in the process of acquiring of knowledge, abilities, skills and habits, and as an educational reform it should be respected in school conditions.The subject of scientific research refers to the didactic-methodic components of the activity of play in the first educational cycle. The methodology, methods and techniques that were applied during the course of the research are: the method of analysis (analysis of content and structural analysis), the descriptive method and the method of comparison, as well as the technique...

This report documents the program and the outcomes of Dagstuhl Seminar 11481 “Models@run.time”. Research on models@run.time seeks to extend the applicability of models and abstractions to the runtime environment, with the goal of... more

This report documents the program and the outcomes of Dagstuhl Seminar 11481 “Models@run.time”. Research on models@run.time seeks to extend the applicability of models and abstractions to the runtime environment, with the goal of providing effective technologies for managing the complexity of evolving software behaviour while it is executing. The Dagstuhl Seminar “Models@run.time” brought together a diverse set of researchers and practitioners with a broad range of expertise, including MDE, software architectures, reflection, self-adaptive systems, validation and verification, middleware, robotics and requirements engineering. Seminar 27. November – 02. December, 2011 – www.dagstuhl.de/11481 1998 ACM Subject Classification D.2 Software Engineering, D.2.10 Design, H.1 Models and Principles

Requirements defects have a major impact throughout the whole software lifecycle. Having a specific defects classification for requirements is important to analyse the root causes of problems, build checklists that support requirements... more

Requirements defects have a major impact throughout the whole software lifecycle. Having a specific defects classification for requirements is important to analyse the root causes of problems, build checklists that support requirements reviews and to reduce risks associated with requirements problems. In our research we analyse several defects classifiers; select the ones applicable to requirements specifications, following rules to build defects taxonomies; and assess the classification validity in an experiment of requirements defects classification performed by graduate and undergraduate students. Not all subjects used the same type of defect to classify the same defect, which suggests that defects classification is not consensual. Considering our results we give recommendations to industry and other researchers on the design of classification schemes and treatment of classification results.

The advent of socio-technical, cyber-physical and artificial intelligence systems has broadened the scope of requirements engineering, which must now deal with new classes of requirements, concerning ethics, privacy and trust. This brings... more

The advent of socio-technical, cyber-physical and artificial intelligence systems has broadened the scope of requirements engineering, which must now deal with new classes of requirements, concerning ethics, privacy and trust. This brings new challenges to Requirements Engineering, in particular regarding the understanding of the non-functional requirements behind these new types of systems. To address this issue, we propose the Ontology-based Requirements Engineering (ObRE) method, which aims to systematize the elicitation and analysis of requirements, by using an ontology to conceptually clarify the meaning of a class of requirements, such as privacy, ethicality and trustworthiness. We illustrate the working of ObRE by applying it to a real case study concerning trustworthiness requirements.

: During the most recent rounds of Base Closure and Realignment Commission activities in 2005, a significant number of training bases were closed. In light of the introduction of new technologies and the great expansion of unmanned... more

: During the most recent rounds of Base Closure and Realignment Commission activities in 2005, a significant number of training bases were closed. In light of the introduction of new technologies and the great expansion of unmanned aircraft systems (UASs) in the force, Department of Defense planners and some in Congress have become concerned that the existing training infrastructure bases and their training support facilities may not be adequate to train UAS air and ground components and the ground forces that use such equipment to capitalize fully on their capabilities. Accordingly, the Deputy Director, Readiness and Training Policy and Programs in the Office of the Under Secretary of Defense for Personnel and Readiness (OUSD [P&R]) asked the RAND Corporation to assess the adequacy of UAS training to support current and future requirements. In addition, the House Armed Services Committee report accompanying the Fiscal Year 2013 National Defense Appropriations Act raised a number of...

Outsourcing decisions are not, technically, irreversible. But in practical terms the organizational disruption and financial costs of bringing services back in house (“backsourcing”) mean that few organizations revert, even when quite... more

Outsourcing decisions are not, technically, irreversible. But in practical terms the organizational disruption and financial costs of bringing services back in house (“backsourcing”) mean that few organizations revert, even when quite dissatisfied with an arrangement. Instead, organizations typically seek to move to another outsourcing arrangement, that is sometimes less attractive than the original in-house delivery. Preliminary evidence from studies of business process outsourcing (BPO) experiences, like those into IT outsourcing’s success, suggests that only a minority of organizations report their BPO arrangements as satisfactory, implying that many are caught in this “can’t go back” bind. In this paper the authors examine two organizations contemplating the adoption of BPO, and consider their expectations and experiences in light of existing empirical literature. The paper concludes with a set of principles to assist organizations to avoid BPO failure.

In light of high cost and higher rate of failure of Datawarehousing projects, it becomes imperative to study software processes being followed for Datawarehousing. In this paper we present a survey of literature for Datawarehousing... more

In light of high cost and higher rate of failure of Datawarehousing projects, it becomes imperative to study software processes being followed for Datawarehousing. In this paper we present a survey of literature for Datawarehousing requirement gathering and testing. This paper has analyzed drawbacks of traditional techniques for requirement gathering and testing of Datawarehouse. We have reported areas where more research needs to be focused. Using text analytics technique called “word cloud”, we have analyzed main areas being researched and shown areas that need more focus. This paper can give a direction to future research in the areas of Datawarehouse requirement gathering and testing.

The relationships between the work products of a security engineering process can be hard to understand, even for persons with a strong technical background but little knowledge of security engineering. Market forces are driving software... more

The relationships between the work products of a security engineering process can be hard to understand, even for persons with a strong technical background but little knowledge of security engineering. Market forces are driving software practitioners who are not security specialists to develop software that requires security features. When these practitioners develop software solutions without appropriate security-specific processes and models, they sometimes fail to produce effective solutions. We have adapted a proven object oriented modeling technique, use cases, to capture and analyze security requirements in a simple way. We call the adaptation an abuse case model. Its relationship to other security engineering work products is relatively simple, from a user perspective

: This paper is an academic examination of the need for the formation of a multinational Regional Security System (RSS) Coast Guard Unit. It concludes that among RSS operational-level maritime forces leaders, there is a common perception... more

: This paper is an academic examination of the need for the formation of a multinational Regional Security System (RSS) Coast Guard Unit. It concludes that among RSS operational-level maritime forces leaders, there is a common perception that the formation of a multinational RSS Coast Guard is a necessity and that such an entity would enhance the security of the sub-region. Though over time the nomenclature of the security challenges to the RSS sub-region has not changed, the complexity of those challenges has. This complexity is the result of the sub-region's existence in an inescapable and uncontrollable world risk society that forces the sub-region to create new, or modify existing security risk mitigation systems to preserve itself. The proposed multinational RSS Coast Guard is an example of this. However, this effort at risk mitigation will not succeed if there is no commonality of perception among policy makers in the RSS that the proposed multinational RSS Coast Guard wou...

An abstraction level hierarchy models abstraction-concretization relationships between different types of specifications. The proposed model combines into a single, continuous partially ordered set, all types of specifications, such as... more

An abstraction level hierarchy models abstraction-concretization relationships between different types of specifications. The proposed model combines into a single, continuous partially ordered set, all types of specifications, such as requirement specifications, design specifications and even the program code. Information theoretic definitions were developed for the concepts of abstraction, concretization and abstraction level. The paper demonstrates how the model can be used to reason about software engineering issues. The purpose of this conceptual paper is to propose an underlying model for software engineering research.

Requirements Engineering is the set of activities involved in creation, managing, documenting, and maintaining a requirements' set for a product. Engineering involves the use of systematic repeatability techniques to ensure that the... more

Requirements Engineering is the set of activities involved in creation, managing, documenting, and maintaining a requirements' set for a product. Engineering involves the use of systematic repeatability techniques to ensure that the Software Requirements are complete, consistent, valid, and verifiable. Software Requirements Specification is an organized process oriented toward defining, documenting and maintaining requirements throughout the development life cycle. Many authors suggest that requirements should always focus their claims on what the software product needs to address, without specifying how to implement them. However, the detail of Software Requirements is influenced by several factors such as: organizational thinking; existing specification standards; and regulatory needs. This work fits exactly with regulatory needs, where the characteristics of Software Requirements Specification in Regulated Environments such as aeronautics, railways and medical are presented and explored. This paper presents and analysis of software requirements specification characteristics in regulated environments. The four characteristics identified are: consistency (internal and external), unambiguity, verifiability, and traceability. The paper also describes the three standards used in these regulated environments (RTCA DO-178C, IEC 62279 and IEC 62304) and examines their similarities and differences from a Requirements Specification standpoint. The similarities and differences will be used to address a future requirements framework universal process that can be configured to address each standard by the usage of Software Process Lines.

The fast-paced, dynamic environment within which information and communication technology (ICT) projects are run as well as ICT professionals’ constant changing requirements present a challenge for project managers in terms of aligning... more

The fast-paced, dynamic environment within which information and communication technology (ICT) projects are run as well as ICT professionals’ constant changing requirements present a challenge for project managers in terms of aligning projects’ requirements with project team members’ requirements. This research paper purports that if projects’ requirements are properly aligned with team members’ requirements, then this will result in a balanced decision approach. Moreover, such an alignment will result in the realization of employee’s needs as well as meeting project’s needs. This paper presents a Project’s requirements and project Team members’ requirements (PrTr) alignment model and argues that a balanced decision which meets both software project’s requirements and team members’ requirements can be achieved through the application of the PrTr alignment model.

All automated information systems (AIS) used on Department of Defense (DoD) data networks must register the data communication modes identifying the ports, protocols, and application services (PPS) used, and the network boundaries... more

All automated information systems (AIS) used on Department of Defense (DoD) data networks must register the data communication modes identifying the ports, protocols, and application services (PPS) used, and the network boundaries crossed. Compliance with the PPS requirements will reduce development time and cost, increase security, speed ecrtification and accreditation steps, enhance AIS interoperability across the department, and speed operational deployment of all new and updated AIS in DoD. This article introduces the PPS basic concepts, and demonstrates how developers and program anagers can comply with the PPS requirements, leverage the security analysis provided by the management office, and obtain the benefits listed.