The development of cyber-physical system (CPS) is a big challenge because of its complexity and its complex requirements. Especially in Requirements Engineering (RE), there exist many redundant and conflict requirements. Eliminating conflict requirements and merged redundant/common requirements lead a challenging task at the elicitation phase in the requirements engineering process for CPS. Col...

Multi-dimensional data (i.e., data referenced in one, two, three, and four dimensions) are often managed by transportation agencies with databases and technologies that cannot be integrated due in part to the lack of a comprehensive model for location referencing of the data. This lack of a comprehensive location referencing system data model limits organizations in implementing improved soluti...

Software is becoming critical to more and more sectors of the economy. Time-to-market, robustness, and quality of software is now more important than ever before, due to new competitive environments, and the resulting need to evolve rapidly with changing business requirements. Thus the difficulty in understanding and modifying evolving software systems remains a serious obstacle to innovation a...

1. INTRODUCTION Software developers are constantly under pressure to deliver code on time and on budget. As a result, many projects focus on delivering functionalities at the expense of meeting non-functional requirements such as reliability, security, maintainability, portability, accuracy, among others. As software complexity grows and clients demand higher and higher quality software, non-fu...

Goal-Oriented Requirements Engineering (GORE) is founded on the premise that functional and non-functional requirements (NFRs) are stakeholder goals to be fulfilled by the system-to-be. Moreover, functional requirements are “hard” goals with clear-cut criteria for fulfillment, while traditionally NFRs are usually “soft” goals (aka softgoals) lacking a clear-cut criterion for success. We argue a...

The support for traceability between requirement specifications has been recognised as an important task in the development life-cycle of software systems. In this paper we present an approach for automatic generation and maintenance of bi-directional traceability relations between commercial and functional requirements expressed in natural language, and requirement object models. The generatio...

All readers of this paper most likely have knowledge of the software requirements discipline and of the use case notation, however not everyone is aware that with the progress of the development process, requirement models evolve in different ways. In particular, some artefacts (such as the glossary, for example) are simply enhanced, while others (functional requirements, object model, etc), in...

There are three basic reasons why you might need to model a business: to re-engineer a business, to improve a business process and to automate a business process. Nevertheless, another reason may be very useful for analyst of software systems and their customers – to understand and automatically generate functional requirements to the system. The present paper describes the process of redefinit...