摘要：It is widely acknowledged that requirements Engineering (RE) has an important implication for the overall success of software or system development projects. As more and more organizations consider RE as the principal problem areas in the projects, improving RE process therefore appears critical for future business success. Moreover, nowadays there are evidences that support improving RE process maturity can contributes to improved business performance. There exist generic Software Process Improvement (SPI) standards, specialised RE process improvement models as well as guidance and advices on RE. However, they suffer from various issues that limit their adoption by organizations that are interested to assess and improve their RE process capability. Therefore, the research presented in this paper proposes a new RE process improvement model. The model is built by adapting and expanding the structure of the continuous representation of the formal maturity framework Capability Maturity Model Integration for Development (CMMI-DEV) developed by the Software Engineering Institute (SEI) through three rounds of development and validation stages, which involved RE and CMMI expert panel in the software industry. This paper aims to provide an overview on what, why and how we build the maturity model for RE. The intention is to provide a foundation for future development in the area of RE process improvement.

摘要：Value delivery is becoming an important asset for an organization due to increasing competition in industry. Therefore, companies apply Agile Software Development (ASD) to be more competitive and reduce time to market. Using ASD for the development of systems implies that established approaches of requirements Engineering (RE) undergo some changes in order to be more flexible to changing requirements. To this end, the field of agile RE is emergent and different process models for agile RE have arisen. The aim of this paper is to build an abstract layer about the variety of existing process models by means of a metamodel for agile RE. It has been created in several iterations and relies on the evaluation of related process models. Furthermore, we have derived process models for agile RE in industry by presenting instances of the metamodel in two different cases: one is based on Scrum whereas the other is based on Kanban. This paper contributes to the software development body of knowledge by delivering a metamodel for agile RE that supports researchers and practitioners modeling and improving their own process models. We can conclude that the agile RE metamodel is highly relevant for the industry as well as for the research community, since we have derived it following empirical research in the field of ASD.

摘要：In recent years, the process orientation requirements engineering field has received significant interest. However, dealing with ordinary users within an enterprise for developing as-is business process is very complex because this requires skills, responsibility, knowledge, and expertise of business processes. This research answers the following questions: 1) how to systematically gather information regarding as-is business process requirements in an informal environment and by non-expert users? and 2) how can an enterprise refine the identified business process with a semantic process model? The primary purpose of this research is to develop a supporting framework that is suitable for the definition of an as-is business process to be deployed within the enterprise environment. Hence, the focus is on gathering requirements to define the as-is business process. This framework concentrates on three significant aspects of this process: development, refinement, and serialization the semantics of the process model. To accomplish this objective, the LORS framework has been proposed, which consists of four phases (List, Order, Refinement, and Serialization). The framework presents a new unique technique to identify the business process, refine the process, and generate the model semantics. This study assumes that a simple and complete framework will help non-expert users define a high-quality as-is process, such that enhance and facilitate the matching process with existing reference models. We present a case study, evaluate the case study relative to specified criteria, and research the limitations and implications discovered from our research. This research concludes that the LORS framework is simple, flexible, visible, interactive, dynamic, and effective.

摘要：Our dependability on software in every aspect of our lives has exceeded the level that was expected in the past. We have now reached a point where we are currently stuck with technology, and it made life much easier than before. The rapid increase of technology adoption in the different aspects of life has made technology affordable and has led to an even stronger adoption in the society. As technology advances, almost every kind of technology is now connected to the network like infrastructure, automobiles, airplanes, chemical factories, power stations, and many other systems that are business and mission critical. Because of our high dependency on technology in most, if not all, aspects of life, a system failure is considered to be very critical and might result in harming the surrounding environment or put human life at risk. We apply our conceptual framework to integration between security and safety by creating a SaS (Safety and Security) domain model. Furthermore, it demonstrates that it is possible to use goal-oriented KAOS (Knowledge Acquisition in automated Specification) language in threat and hazard analysis to cover both safety and security domains making their outputs, or artifacts, well-structured and comprehensive, which results in dependability due to the comprehensiveness of the analysis. The conceptual framework can thereby act as an interface for active interactions in risk and hazard management in terms of universal coverage, finding solutions for differences and contradictions which can be overcome by integrating the safety and security domains and using a unified system analysis technique (KAOS) that will result in analysis centrality. For validation we chose the Systems-Theoretic Accident Model and Processes (STAMP) approach and its modelling language, namely System-Theoretic Process Analysis for safety (STPA), on the safety side and System-Theoretic Process Analysis for Security (STPA-sec) on the security side in order to be the base of the e

摘要：Vee-tail configuration is an unconventional tail configuration for commercial transport aviation, the use of which could suppose reductions on CO2 emissions. The conceptual design criteria have been selected inspired on the certification requirements established by the aviation regulation in force. They are static stability in cruise, control after Critical Engine Failure(CEF),control in crosswind landing, and trim in these three conditions. The study is carried out through a combination of semi-empirical techniques and Vortex-Lattice Methods(VLM) and thus this analyses the consequences of applying these criteria to a reference aeroplane substituting its conventional tail by a parametrised Vee-tail configuration. The Vee-tail is defined by four parameters:span, root chord, taper ratio and dihedral angle. The results of the study establish a relation between the parameters in order to accomplish the proposed conceptual design criteria. To sum up, minimum and maximum limits are obtained for dihedral angle depending on the combination of the rest of parameters. In addition, a design restriction to the yawing trailing-edge tail control is reached when the results are analysed, demonstrating that its minimum size must be between 60%and 80% of the half-span of the tail, depending on the Vee-tail geometry.

摘要：Design Patterns, which give abstract solutions to commonly recurring design problems, have been widely used in the software and hardware domain. As non-functional requirements are an important aspect in the design of safety-critical embedded systems, this work focuses on the integration of non-functional implications in an existing design pattern concept. We propose a pattern representation for safety-critical embedded application design methods by including fields for the implications and side effects of the represented design pattern on the non-functional requirements of the overall systems. The considered requirements include safety, reliability, modifiability, cost, and execution time.

摘要：With continuous evolution in software industry, security is becoming very important in software projects. However, in many development methodologies, security is thought to be added in the project at later stages of the development lifecycle. There are also many proposed methodologies where the security measures are considered at requirement engineering stage of the development lifecycle, but many of them still do not seem adequate for applicability due to the reason that these approaches do not provide sufficient support for mapping the security requirements to the later stages of development. So, we are in need of a software requirement engineering approach, which is not only helpful in security requirement specification at requirement engineering stage but also provides support for using the specified security requirements at later stages of development. To meet this requirement, we introduce a new method Secure and Traceable Requirement Engineering Process (STREP). This method also helps the non-security-expert requirement engineers to specify requirements in such a way that the specified requirements can be used to derive security related test cases. STREP method not only deals with security issues of the system at requirement engineering stage, but also makes the security requirements more traceable to be used at later stages of development lifecycle, and as a result, secure systems are produced that are also usable as the customer wishes.

摘要：New methodology of designing the differential pressure flow meters for fluid energy carriers is developed in order to provide minimum uncertainty of results of flow rate measurement. This methodology is implemented in “Raskhod-RU” CAD system for computer aided design and calculation of differential pressure flow meters. “Raskhod-RU” CAD meets the requirements of new Standards implemented in CIS countries (GOST 8.586.1,2,3,4,5-2005) and provides accomplishment of the following tasks: verification of conditions (constraints) for application of the differential pressure method according to the requirements of new Standards;calculation of parameters of primary device, pipe straight lengths and flow meter in general according to the requirements of new Standards;calculation of uncertainty of results of fluid flow rate and volume measurement.

摘要：Automatically mapping a requirement specification to design model in Software Engineering is an open complex problem. Existing methods use a complex manual process that use the knowledge from the requirement specification/modeling and the design, and try to find a good match between them. The key task done by designers is to convert a natural language based requirement specification (or corresponding UML based representation) into a predominantly computer language based design model—thus the process is very complex as there is a very large gap between our natural language and computer language. Moreover, this is not just a simple language conversion, but rather a complex knowledge conversion that can lead to meaningful design implementation. In this paper, we describe an automated method to map Requirement Model to Design Model and thus automate/partially automate the Structured Design (SD) process. We believe, this is the first logical step in mapping a more complex requirement specification to design model. We call it IRTDM (Intelligent Agent based requirement model to design model mapping). The main theme of IRTDM is to use some AI (Artificial Intelligence) based algorithms, semantic representation using Ontology or Predicate Logic, design structures using some well known design framework and Machine Learning algorithms for learning over time. Semantics help convert natural language based requirement specification (and associated UML representation) into high level design model followed by mapping to design structures. AI method can also be used to convert high level design structures into lower level design which then can be refined further by some manual and/or semi automated process. We emphasize that automation is one of the key ways to minimize the software cost, and is very important for all, especially, for the “Design for the Bottom 90% People” or BOP (Base of the Pyramid People).