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...

quality of products and services is considered as a key factor for customer satisfaction. quality function deployment (qfd) is known as a critical tool for translating voice of customers to prioritize technical requirements of a production. the level of this satisfaction depends on the number of fulfilled requirements. it should be noted that this level varies according to the possible constrai...

Software architecture is the result of a design effort aimed at ensuring a certain set of quality attributes. As we show, quality requirements are commonly specified in practice but are rarely validated using automated techniques. In this paper we analyze and classify commonly specified quality requirements after interviewing professionals and running a survey. We report on tools used to valida...

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...

In designing product-line architecture (PLA), it is important to analyze common and variable requirements in a product family. These requirements must be analyzed not only from functional aspect but also from aspects relate to quality attributes such as performance aspect and reliability aspect. For example, if two products are required to attain different level of performance, architectures fo...

We present a design process for incorporating data quality requirements into database schemas that is rooted in goal-oriented requirements analysis techniques, developed in the Requirement Engineering community over last 15 years. Goal-oriented approaches (i) offer a body of notations, techniques and processes for modeling, analyzing and operationalizing quality requirements; (ii) support repre...