Preferencje help
Widoczny [Schowaj] Abstrakt
Liczba wyników
Powiadomienia systemowe
  • Sesja wygasła!

Znaleziono wyników: 4

Liczba wyników na stronie
first rewind previous Strona / 1 next fast forward last
Wyniki wyszukiwania
Wyszukiwano:
w słowach kluczowych:  non-functional requirements
help Sortuj według:

help Ogranicz wyniki do:
first rewind previous Strona / 1 next fast forward last
EN
Background: Non-Functional Requirements (NFR) have a direct impact on the architecture of the system, thus it is essential to identify NFRs in the initial phases of software development. Aim: The work is based on extraction of relevant keywords from NFR descriptions by employing text mining steps and thereafter classifying these descriptions into one of the nine types of NFRs. Method: For each NFR type, keywords are extracted from a set of pre-categorized specifications using Information-Gain measure. Then models using 8 Machine Learning (ML) techniques are developed for classification of NFR descriptions. A set of 15 projects (containing 326 NFR descriptions) developed by MS students at DePaul University are used to evaluate the models. Results: The study analyzes the performance of ML models in terms of classification and misclassification rate to determine the best model for predicting each type NFR descriptions. The Naïve Bayes model has performed best in predicting “maintainability” and “availability” type of NFRs. Conclusion: The NFR descriptions should be analyzed and mapped into their corresponding NFR types during the initial phases. The authors conducted cost benefit analysis to appreciate the advantage of using the proposed models.
EN
Background: In practice, the developers focus is on early identification of the functional requirements (FR) allocated to software, while the system non-functional requirements (NFRs) are left to be specified and detailed much later in the development lifecycle. Aim: A standards-based model of system performance NFRs for early identification and measurement of FR-related performance of software functions. Method: 1) Analysis of performance NFR in IEEE and ECSS standards and the modeling of the identified system/software performance functions using Softgoal Interdependency Graphs. 2) Application of the COSMIC-FSM method (e.g., ISO 19761) to measure the functional size of the performance requirements allocated to software functions. 3) Use of the COSMIC-SOA guideline to tailor this framework to service-oriented architecture (SOA) for performance requirements specification and measurement. 4) Illustration of the applicability of the proposed approach for specification and measurement of system performance NFR allocated to the software for an automated teller machine (ATM) in an SOA context. Results: A standards-based framework for identifying, specifying and measuring NFR system performance of software functions. Conclusion: Such a standards-based system performance reference framework at the function and service levels can be used early in the lifecycle by software developers to identify, specify and measure performance NFR.
EN
Today, the list of telecom services, their functionality and requirements for Service Execution Environment (SEE) are changing extremely fast. Especially when it concerns requirements for charging as they have a high influence on business. This results in the need for constant adaptation and reconfiguration of Online Charging System (OCS) used in mobile operator networks. Moreover any new functionality requested from a service can have an impact on system behavior (performance, response time, delays) which are in general nonfunctional requirements. Currently, this influence and reconfiguration strategies are poorly formalized and validated. Current state-of-the-art approaches are considered methodologies that can model non-functional or functional requirements but these approaches don’t take into account interaction between functional and nonfunctional requirements and collaboration between services. All these result in time and money consuming service development and testing, and cause delays during service deployment. The balancing method proposed in this paper fills this gap. It employs a well-defined workflow with predefined stages for development and deployment process for OCS. The applicability of this novel approach is described in a separate section which contains an example of GPRS service charging. A tool, based on this method will be developed, providing automation of service functionality influence on non-functional requirements and allowing to provide a target deployment model for a particular customer. The reduction of development time and thus necessary financial input has been proved based on real-world experiments.
4
Content available remote Structured meetings for non-functional requirements elicitation
EN
The statement that requirements engineering process calls for special attention in every software development project is commonly known. So the question arises, how to begin this process to obtain results of good-enough quality? The paper focuses on one of the initial steps of requirements engineering process. It presents and evaluates a structural time-boxed computer-supported approach for non-functional requirements elicitation. A multiple case study experiment involving nine projects hosted at Poznan University of Technology was conducted. The obtained results of the evaluation are promising for future adaption of the method in industry environment.
first rewind previous Strona / 1 next fast forward last
JavaScript jest wyłączony w Twojej przeglądarce internetowej. Włącz go, a następnie odśwież stronę, aby móc w pełni z niej korzystać.