Results 241 to 250 of about 5,663,412 (281)
Some of the next articles are maybe not open access.
Components for Non-Functional Requirements
1998Building distributed applications is very hard as we not only have to take care of the application semantics, but of non-functional requirements such as distributed execution, security and reliability as well. A component-oriented approach can be a powerful technique to master this complexity, and to manage the development of such applications. In such
Bert Robben +4 more
openaire +2 more sources
2012
Software Requirements Specifications (SRS) documents are important artifacts in the software industry. A SRS contains all the requirements specifications for a software system, either as functional requirements (FR) or non-functional requirements (NFR). FRs are the features of the system-to-be, whereas NFRs define its quality attributes.
openaire +1 more source
Software Requirements Specifications (SRS) documents are important artifacts in the software industry. A SRS contains all the requirements specifications for a software system, either as functional requirements (FR) or non-functional requirements (NFR). FRs are the features of the system-to-be, whereas NFRs define its quality attributes.
openaire +1 more source
Metabolic Requirements for Renal Function
Hospital Practice, 1979Renal mass accounts for only 0.5% of body weight, yet the kidney consumes 7% of the body's total oxygen uptake. Most is used for tubular transport, but a significant portion contributes to less well-recognized aspects of renal function. Cortical gluconeogenesis capacity, for example, exceeds that of the liver per gram of tissue.
openaire +2 more sources
Towards Functional Requirements Analytics
2016In the Era of sharing, several efforts have been launched to construct repositories (referential/warehouses) storing entities used in projects for enterprises (e.g., data, processes, models, APIs, etc.). These repositories augment the business value of the enterprises in terms of reuse, sharing, traceability and analysis.
Djilani, Zouhir +2 more
openaire +3 more sources
Task descriptions as functional requirements
IEEE Software, 2003The tasks and support approach uses task descriptions that specify what the user and computer shall accomplish together without being explicit about who performs which parts of a task. The requirement is simply to support the identified tasks. Stakeholders can easily validate and later verify such requirements.
openaire +2 more sources
Hardware Requirements For Functional MRI
Proceedings of the Annual International Conference of the IEEE Engineering in Medicine and Biology Society Volume 13: 1991, 2005To perform functional MRI requires faster gradient switching and larger gradients than are usually available. The reasons for this are described. and feasible hardware specifications are given. Some comments are made on very fast digitization, and examples of functional imaging are presented.
openaire +2 more sources
Functional and user requirements for IMACS
Computer Methods and Programs in Biomedicine, 1991An Image Management, Archiving and Communication System (IMACS) should integrate all imaging modalities in a diagnostic radiology department. In order to obtain this integration, manufacturers of diagnostic imaging modalities must follow the established standards for communication protocols and image formats.
openaire +2 more sources
Compensation functions and requirements
Proceedings of the 4th workshop on ACM SIGOPS European workshop, 1990David Scholefield, Hussein S. M. Zedan
openaire +2 more sources
The functional requirements of proteins for foods
Journal of the American Oil Chemists' Society, 1971AbstractAs a growing amount of research attention has been diverted, for a number of reasons, from the traditional protein foods to the so‐called unconventional food proteins, an awareness has increased of the need to understand the functional properties of these proteins.
openaire +2 more sources
The functional requirements for community information
Journal of Documentation, 2016Purpose – The purpose of this paper is to consider the nature of community information (CI) and proposes a data model, based on the entity-relationship approach adopted in the Functional Requirements for Bibliographic Records (FRBR), which may assist with the development of future metadata standards for CI systems.
openaire +2 more sources