Global ETD Search

Search theses and dissertations gathered from participating repositories worldwide. Every result links back to the library that holds it. No account is needed.

Results

Showing 1 to 20 of 732 for “"functional requirements"”.

  1. Functional requirements and non-functional requirements : a survey

    … for software modeling and associated artifacts. Requirements are basis of software systems. As the first phase of the software development process, requirements set reasonable targets to be achieved. The purpose of this report is to study the role of requirements in software development process, …

    concordia Download PDF for Functional requirements and non-functional requirements : a survey (opens in a new tab)

  2. Extracting Non-Functional Requirements from Unstructured Text

    Non-functional requirements (NFRs) of a software system describe desired quality attributes rather than specific user-visible features; NFRs model stakeholder expectations about pervasive system properties such as performance, security, reliability, and usability. Failing to meet these expectations …

    waterloo Repository record for Extracting Non-Functional Requirements from Unstructured Text (opens in a new tab)

  3. Semantic Component Selection Based on Non-Functional Requirements

    … reuse, we need a good understanding of both the functional and non-functional requirements of the component needed, and the components available. Functional requirements specify what a software component does and non-functional requirements specify how a software component achieves its goals. …

    adelaide Repository record for Semantic Component Selection Based on Non-Functional Requirements (opens in a new tab)

  4. Non-functional requirements testing in the Medtech industry

    … identification, separation, and testing of functional and non-functional requirements within the development cycle. The objective of this thesis was to implement a taxonomy for non-functional requirements within the Medtech industry, and to build an automated test framework including tests …

    chalmers Repository record for Non-functional requirements testing in the Medtech industry (opens in a new tab)

  5. Perspectives in hospital pharmacy design based on functional requirements

    It is significant that the separation of pharmacy from medicine occurred for the first time in institutions under ecclesiastic authority which were devoted to the care of the sick. In this period of history, there was little division between the church and state; therefore, business did not play …

    u-pacific Repository record for Perspectives in hospital pharmacy design based on functional requirements (opens in a new tab)

  6. Categorizing Non-Functional Requirements Using a Hierarchy in UML.

    Non-functional requirements (NFRs) are a subset of requirements, the means by which software system developers and clients communicate about the functionality of the system to be built. This paper has three main parts: first, an overview of how non-functional requirements relate to software …

    etsu Repository record for Categorizing Non-Functional Requirements Using a Hierarchy in UML. (opens in a new tab) Download PDF for Categorizing Non-Functional Requirements Using a Hierarchy in UML. (opens in a new tab)

  7. Optimisation and Characterisation of Lattice Structures for Functional Requirements

    … lattice structures that met the mechanical requirements of the applications and that had an optimal balance between the objectives. The results of this study can be used to design and optimize lattice structures for a variety of applications.

    unsw Repository record for Optimisation and Characterisation of Lattice Structures for Functional Requirements (opens in a new tab)

  8. Automated Quality Assurance of Non-Functional Requirements for Testability

    A Software Requirements Specification (SRS) document contains all the requirements to describe a software system to be developed. These requirements are typically separated into Functional Requirements (FRs), which describe the features of the system under development and Non-Functional …

    concordia Download PDF for Automated Quality Assurance of Non-Functional Requirements for Testability (opens in a new tab)

  9. Non-functional requirements and their impact on AGV based systems

    … facilities are impacted by the choice of nonfunctional requirements (NFRs). This study is based on a mixed-method approach to assess the impact that these NFRs have on system throughput, and whether the results differentiate based on the layout and the fleet size of the system. An interview …

    chalmers Repository record for Non-functional requirements and their impact on AGV based systems (opens in a new tab)

  10. Automated testing of non-functional requirements based on behavioural scripts

    … high quality software, it is crucial that non‐functional requirements (NFRs) are well specified and thoroughly tested in parallel with functional requirements (FRs). Nevertheless, in requirement specification the focus is mainly on FRs, even though NFRs have a critical role in the success of …

    chalmers Repository record for Automated testing of non-functional requirements based on behavioural scripts (opens in a new tab)

  11. Towards an Ontology-Based Approach for Reusing Non-Functional Requirements Knowledge

    Requirements Engineering play a crucial role during the software development process. Many works have pointed out that Non-Functional Requirements (NFR) are currently more important than Functional Requirements. NFRs can be very complicated to understand due to its diversity and subjective nature. …

    york Repository record for Towards an Ontology-Based Approach for Reusing Non-Functional Requirements Knowledge (opens in a new tab)

  12. The Use Of Modeling Tools In The Analysis Of Functional Requirements

    … analysis methodology to investigate the functional requirements of software systems with modeling technologies, such as Unified Modeling Language (UML) and Systems Modeling Language (SysML). The main focus of the analysis is to discover objects and describe them in the problem domain. The …

    uab Repository record for The Use Of Modeling Tools In The Analysis Of Functional Requirements (opens in a new tab)

  13. An Examination of Standards of Functional Requirements, Performance and Finish in Housing

    … standard of building may be judged, statutory requirements and recommended standards covering all facets of the construction of housing are reviewed. Grades of finish of external and internal surfaces are defined by detailed specifications. Previous research relevant to building standards in …

    aston Download PDF for An Examination of Standards of Functional Requirements, Performance and Finish in Housing (opens in a new tab)

  14. Quantifiable non-functional requirements modeling and static verification for web service compositions

    … services from different vendors. Although the functionalities of the composite web services are ensured during the composition process, the non-functional requirements (NFRs) are often ignored in this process. Since quality of services plays a more and more important role in modern …

    iastate Repository record for Quantifiable non-functional requirements modeling and static verification for web service compositions (opens in a new tab)

  15. Improving Priority-Awareness Of Non-Functional Requirements During Decision-Making In Self-Adaptive Systems

    … problem with SASs is to ensure that their requirements remain satisfied as they adapt. Trade-off analysis of the non-functional re-quirements (NFRs), based on their satisfaction priorities, is a key to establishing a balance among them. Such trade-off analysis is often based on optimization …

    aston Download PDF for Improving Priority-Awareness Of Non-Functional Requirements During Decision-Making In Self-Adaptive Systems (opens in a new tab)

  16. A multi-layered desires based framework to detect evolving non-functional requirements of users

    Non-Functional Requirements (NFRs) have a great impact on all the downstream activities in a software's entire life-cycle. It is important to capture newly emerged NFRs for system evolution. NFRs are treated as quality goals in Goal Oriented Requirements Engineering. Under the concept of the goal, …

    iastate Repository record for A multi-layered desires based framework to detect evolving non-functional requirements of users (opens in a new tab)

Page 1 of 37