Non-functional requirements (NFRs) are rarely taken in account in most software development. There are some reasons that can help us to understand why these requirements are not explicitly dealt with: their complexity, NFRs are usually stated only informally, their high abstraction level and the rare support of languages, methodologies and tools. In this scenario, we concentrate on defining a l...

In the area of requirements engineering there are elicitation techniques that are based on business context to identify the software requirements. However, these techniques do not commonly use business processes models as a source of information relevant to the elicitation of requirements. Such techniques extract use cases from business processes models. However, before modeling use cases, it i...

A taxonomy is introduced and used as a backdrop against which current state-of-the-art in the requirements engineering field is reviewed. The emphasis is on identifying general trends and issues rather than offering the reader a literature survey. The contents of a requirements specification is presented in light of the consensus reached by both theoreticians and practitioners. The desirable pr...

According to the Singapore Framework, any development of a Dublin Core Application Profile (DCAP) has to include the creation of a domain model. DC Scholarly Works Application Profile (SWAP) was the first one explicitly using Functional Requirements for Bibliographic Records (FRBR) model in creating its domain model. FRBR has recently been extended with Functional Requirements for Authority Dat...

Software Requirements Specification (SRS) is the key documentation, defining the functional and non-functional system requirements. By revisiting a number of in the literature much discussed key aspects related to SRS and extracting essential views from the author’s daily work experience, this papers stresses the importance of the SRS and examines the process, which enables the emergence of a q...

Definitions of the concepts derived from the goal concept (including functional and nonfunctional goal, hardgoal, and softgoal) used in requirements engineering are discussed, and precise (and, when appropriate, mathematical) definitions are suggested. The concept of satisficing, associated to softgoals is revisited. A softgoal is satisficed when thresholds of some precise criteria are reached....

This paper presents the idea of Usage Oriented Requirements Engineering, an extension of Use Case Driven Analysis. The main objective is to achieve a requirements engineering process resulting in a model which captures both functional requirements and system usage aspects in a comprehensive manner. The paper presents the basic concepts and the process of Usage Oriented Requirements Engineering,...

: One of the tools for the architectural advent form is the structure, while architecture and structures, particularly in our sociable Iran, are separated from each other. Most successful buildings have dominating designers who are proficient in structural issues and have a comprehension of the structural system's behavior. The extent of attention to the structure of the building will inevitabl...

Non-functional requirements (NFRs) have been the focus of research in Requirements Engineering (RE) for more than 20 years. Despite this attention, their ontological nature is still an open question, thereby hampering efforts to develop concepts, tools and techniques for eliciting, modeling, and analyzing them, in order to produce a specification for a system-to-be. In this paper, we propose to...