Dissertations / Theses: 'Functional and non-functional requirements'

1

Cherukuri, Vijaya Krishna, and Piyush Gupta. "Model Based Testing for Non-Functional Requirements." Thesis, Mälardalen University, School of Innovation, Design and Engineering, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-9851.

Full text

Abstract:

Model Based Testing (MBT) is a new-age test automation technique traditionally used for Functional Black-Box Testing. Its capability of generating test cases by using model developed from the analysis of the abstract behavior of the System under Test is gaining popularity. Many commercial and open source MBT tools are available currently in market. But each one has its own specific way of modeling and test case generation mechanism that is suitable for varied types of systems. Ericsson, a telecommunication equipment provider company, is currently adapting Model Based Testing in some of its divisions for functional testing. Those divisions haven’t yet attempted adapting Model Based Testing for non-functional testing in a full-pledged manner. A comparative study between various MBT tools will help one of the Ericsson’s testing divisions to select the best tool for adapting to its existing test environment. This also helps in improving the quality of testing while reducing cost, time and effort. This thesis work helps Ericsson testing division to select such an effective MBT tool. Based on aspects such as functionality, flexibility, adaptability, performance etc., a comparative study is carried out on various available MBT tools and a few were selected among them: Qtronic, ModelJUnit and Elvior Motes.This thesis also helps to understand the usability of the selected tools for modeling of non-functional requirements using a new method. A brief idea of modeling the non-functional requirements is suggested in this thesis. A System under Test was identified and its functional behavior was modeled along with the non functional requirements in Qtronic and ModelJUnit. An experimental analysis, backed by observations of using the new proposed method indicates that the method is efficient enough to carry out modeling non-functional requirements along with modeling of functional requirements by identifying the appropriate approach.Model Based Testing (MBT) is a new-age test automation technique traditionally used for Functional Black-Box Testing. Its capability of generating test cases by using model developed from the analysis of the abstract behavior of the System under Test is gaining popularity. Many commercial and open source MBT tools are available currently in market. But each one has its own specific way of modeling and test case generation mechanism that is suitable for varied types of systems. Ericsson, a telecommunication equipment provider company, is currently adapting Model Based Testing in some of its divisions for functional testing. Those divisions haven’t yet attempted adapting Model Based Testing for non-functional testing in a full-pledged manner. A comparative study between various MBT tools will help one of the Ericsson’s testing divisions to select the best tool for adapting to its existing test environment. This also helps in improving the quality of testing while reducing cost, time and effort. This thesis work helps Ericsson testing division to select such an effective MBT tool. Based on aspects such as functionality, flexibility, adaptability, performance etc., a comparative study is carried out on various available MBT tools and a few were selected among them: Qtronic, ModelJUnit and Elvior Motes.

This thesis also helps to understand the usability of the selected tools for modeling of non-functional requirements using a new method. A brief idea of modeling the non-functional requirements is suggested in this thesis. A System under Test was identified and its functional behavior was modeled along with the non functional requirements in Qtronic and ModelJUnit. An experimental analysis, backed by observations of using the new proposed method indicates that the method is efficient enough to carry out modeling non-functional requirements along with modeling of functional requirements by identifying the appropriate approach.

APA, Harvard, Vancouver, ISO, and other styles

2

Al-kfairy, Mousa. "Toward Agile development methods & Non-functional requirements." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-54656.

Full text

Abstract:

In this thesis, we tried to solve those problems by adapting agile development methods with Non-functional requirements-framework (NFR-Framework). In this thesis, we have inspected many research papers, and we have met industrial experts for feedback regarding our theoretical results. As a result of the inspection, we have been able to adapt agile development methods (extreme programming (XP)) with NFR-framework. We use XP since it is more practically oriented process than other agile development methods. In the first try for this process model, we got three alternatives for applying it. The first one is based on collecting all NFRs from the beginning of the development process. The second one is based on updating the SIG (software interdependency graph) every time we have new functional requirements (FR) and the third one is based on the incremental nature of agile development methods. Each one of these alternatives has it is own advantages and disadvantages. We tried to extract those advantages and disadvantages by brainstorming and reading research papers. The most important issue in all of the three alternatives is the applicability. Finally we got industrial feedback regarding all of them. As a result of the industrial feedback, we were able to find another alternative of how to apply the process model which is presented in 7.2.

APA, Harvard, Vancouver, ISO, and other styles

3

Ahmad, Manzoor. "Modeling and verification of functional and non functional requirements of ambient, self adaptative systems." Phd thesis, Université Toulouse le Mirail - Toulouse II, 2013. http://tel.archives-ouvertes.fr/tel-00965934.

Full text

Abstract:

The overall contribution of this thesis is to propose an integrated approach for modeling and verifying the requirements of Self Adaptive Systems using Model Driven Engineering techniques. Model Driven Engineering is primarily concerned with reducing the gap between problem and software implementation domains through the use of technologies that support systematic transformation of problem level abstractions to software implementations. By using these techniques, we have bridged this gap through the use of models that describe complex systems at multiple levels of abstraction and through automated support for transforming and analyzing these models. We take requirements as input and divide it into Functional and Non Functional Requirements. We then use a process to identify those requirements that are adaptable and those that cannot be changed. We then introduce the concepts of Goal Oriented Requirements Engineering for modeling the requirements of Self Adaptive Systems, where Non Functional Requirements are expressed in the form of goals which is much more rich and complete in defining relations between requirements. We have identified some problems in the conventional methods of requirements modeling and properties verification using existing techniques, which do not take into account the adaptability features associated with Self Adaptive Systems. Our proposed approach takes into account these adaptable requirements and we provide various tools and processes that we developed for the requirements modeling and verification of Self Adaptive Systems. We validate our proposed approach by applying it on two different case studies in the domain of Self Adaptive Systems.

APA, Harvard, Vancouver, ISO, and other styles

4

Ameller, David. "Non-functional requirements as drivers of software architecture design." Doctoral thesis, Universitat Politècnica de Catalunya, 2014. http://hdl.handle.net/10803/144942.

Full text

Abstract:

In the last decades, software engineering has become an important area of research. As researchers, we try to identify a problem, a need, or a hole in some research topic, once identified we make an effort to produce new techniques, methods, and tools that hopefully will help to improve the detected issue. In the present thesis the identified issue was the need of supporting non-functional requirements in the software architecture design where these requirements are the drivers of the architectural decision-making. This thesis started with the idea that a relatively new software engineering discipline, model-driven development, was a good place to propose a solution for the detected issue. We envisioned how non-functional requirements can be integrated in model-driven development and how this integration will impact in the architectural design activities. When we started to produce our techniques, methods, and tools for model-driven development we found out that there was a bigger hole in the web of knowledge than what we had initially foreseen. Much of the evidence of how non-functional requirements affect the software architecture design is hidden. This situation caused a turn in this thesis: we needed to understand architects, how they think and how they make the architectural decisions, what is the role of non-functional requirements in the architectural decision-making process, and to what extent are the non-functional requirements important in this process. All these questions needed an answer, an answer that only architects could provide. In consequence we opted to drove several empirical studies to answer these questions. In parallel, we started to work in a way of representing this knowledge, an ontology for software architecture that integrates non-functional requirements. Using this ontology as basis, we designed a method to assist architects in the architectural decision-making process and a tool that acted as a proof of concept of both, the ontology and the method. In summary, this thesis explores how non-functional requirements are currently integrated in the software architecture design practices, and proposes ways to improve this integration and facilitate the work of architects by providing means to assist them in the architectural decision-making process.

APA, Harvard, Vancouver, ISO, and other styles

5

Moody, James D. "Categorizing non-functional requirements using a hierarchy in UML." [Johnson City, Tenn. : East Tennessee State University], 2003. http://etd-submit.etsu.edu/etd/theses/available/etd-0330103-170022/unrestricted/MoodyJ04292003b.pdf.

Full text

Abstract:

Thesis (M.S.)--East Tennessee State University, 2003.
Title from electronic submission form. ETSU ETD database URN: etd-0330103-170022. Includes bibliographical references. Also available via Internet at the UMI web site.

APA, Harvard, Vancouver, ISO, and other styles

6

Moody, James David. "Categorizing Non-Functional Requirements Using a Hierarchy in UML." Digital Commons @ East Tennessee State University, 2003. https://dc.etsu.edu/etd/763.

Full text

Abstract:

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 engineering is given, along with a survey of NFRs in the software engineering literature. Second, a collection of 161 NFRs is diagrammed using the Unified Modelling Language, forming a tool with which developers may more easily identify and write additional NFRs. Third, a lesson plan is presented, a learning module intended for an undergraduate software engineering curriculum. The results of presenting this learning module to a class in Spring, 2003 is presented.

APA, Harvard, Vancouver, ISO, and other styles

7

Farid, Weam Mohamed. "The NORMAP Methodology: Non-functional Requirements Modeling for Agile Processes." NSUWorks, 2011. http://nsuworks.nova.edu/gscis_etd/147.

Full text

Abstract:

Agile software development methodologies, such as Scrum, have gained tremendous popularity and proven successful in quickly delivering quality Functional Requirements (FRs). However, agile methodologies have not adequately identified, modeled, and linked Non-Functional Requirements (NFRs) with FRs in early development phases. Researchers agree that NFRs have been generally ignored in conventional methodologies, especially ignored in agile environments. This dissertation develops a conceptual framework for NFR modeling in agile processes. The proposed Non-functional Requirements Modeling for Agile Processes (NORMAP) Methodology investigated the feasibility of identifying, linking, and modeling Agile Loose Cases (ALCs) with Agile Use Cases (AUCs) and Agile Choose Cases (ACCs). AUCs are newly proposed hybrid of use cases and agile user stories. ALCs are proposed—loosely—defined agile NFRs. ACCs are proposed potential solutions (operationalizations) for ALCs. A lightweight adapted version of the NFR Framework was developed including 25 important NFRs selected out of 161 for this study. Further, an enhanced risk-driven agile requirements implementation sequence (NORPLAN) was developed and visualized as a tree-like view (NORVIEW). The NORMAP Methodology was validated through developing NORMATIC--a Java-based agile visual modeling simulation tool and two case studies. NORMATIC utilized Natural Language Processing (NLP) tools to parse requirement sentences and identify potential ALCs. The first case study utilized the Predictor Models in Software Engineering (PROMISE) dataset used in NFRs classification. NORMAP successfully parsed and classified ALCs for 529 out of 607 (87.15%) independent user requirements. The second case study utilized the European Union eProcurement System’s 26 functional requirements. NORMAP successfully parsed and classified ALCs for 50 out of 57 sentences that included possible ALCs (87.71%). Furthermore, requirements quality and project management metrics were used to calculate a risk-driven requirements implementation sequence using three priority schemes. Results showed that Riskiest-Requirements-First priority scheme planned requirements in 17 sprints--two months earlier than the Highest-Business-Value-First scheme (21 sprints) and one month earlier than the Riskiest-Requirements-Last scheme (19 sprints). Agile communities can potentially benefit from the NORMAP Methodology by utilizing a systematic and risk-driven lightweight engineering process to visually model and plan NFRs as first-class artifacts in agile environments.

APA, Harvard, Vancouver, ISO, and other styles

8

Sadiq, Mazhar. "Modeling the Non-functional Requirements in the Context of Usability, Performance, Safety and Security." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2007. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3246.

Full text

Abstract:

Requirement engineering is the most significant part of the software development life cycle. Until now great emphasis has been put on the maturity of the functional requirements. But with the passage of time it reveals that the success of software development does not only pertain to the functional requirements rather non-functional requirements should also be taken into consideration. Among the non-functional requirements usability, performance, safety and security are considered important. Further it reveals that there exist so many modeling and testing techniques for functional requirements but the area of non-functional requirements is still deprived off. This is mainly due to difficulty, diversity in nature and hard to express for being domain-specific. Hence emphasis is put to the development of these models or testing techniques. While developing these models or testing techniques it is found that all the four areas of usability, performance, safety and security are not only closely related but rather depend on one another up to some extent. This meant that they all should be tackled while keeping into consideration of the related from among them. For the purpose it seemed necessary to collect in one artefact all the available modeling and testing techniques related to the four core areas of non-functional requirements may be collected and compared. This work at first provides an understanding of the problem domain while describing aspects of the non-functional requirements. Then possibly the available related models or testing techniques are collected and discussed. Finally in the last they are compared with respect to diversified aspects.

APA, Harvard, Vancouver, ISO, and other styles

9

Gokyer, Gokhan. "Identifying Architectural Concerns From Non-functional Requirements Using Support Vector Machine." Master's thesis, METU, 2008. http://etd.lib.metu.edu.tr/upload/12609964/index.pdf.

Full text

Abstract:

There has been no commonsense on how to identify problem domain concerns in architectural modeling of software systems. Even, there is no commonly accepted method for modeling the Non-Functional Requirements (NFRs) effectively associated with the architectural aspects in the solution domain. This thesis introduces the use of a Machine Learning (ML) method based on Support Vector Machines to relate NFRs to classified "
architectural concerns"
in an automated way. This method uses Natural Language Processing techniques to fragment the plain NFR texts under the supervision of domain experts. The contribution of this approach lies in continuously applying ML techniques against previously discovered &ldquo
NFR - architectural concerns&rdquo
associations to improve the intelligence of repositories for requirements engineering. The study illustrates a charted roadmap and demonstrates the automated requirements engineering toolset for this roadmap. It also validates the approach and effectiveness of the toolset on the snapshot of a real-life project.

APA, Harvard, Vancouver, ISO, and other styles

10

Wen, Zhenyu. "Partitioning workflow applications over federated clouds to meet non-functional requirements." Thesis, University of Newcastle upon Tyne, 2016. http://hdl.handle.net/10443/3343.

Full text

Abstract:

With cloud computing, users can acquire computer resources when they need them on a pay-as-you-go business model. Because of this, many applications are now being deployed in the cloud, and there are many di erent cloud providers worldwide. Importantly, all these various infrastructure providers o er services with di erent levels of quality. For example, cloud data centres are governed by the privacy and security policies of the country where the centre is located, while many organisations have created their own internal \private cloud" to meet security needs. With all this varieties and uncertainties, application developers who decide to host their system in the cloud face the issue of which cloud to choose to get the best operational conditions in terms of price, reliability and security. And the decision becomes even more complicated if their application consists of a number of distributed components, each with slightly di erent requirements. Rather than trying to identify the single best cloud for an application, this thesis considers an alternative approach, that is, combining di erent clouds to meet users' non-functional requirements. Cloud federation o ers the ability to distribute a single application across two or more clouds, so that the application can bene t from the advantages of each one of them. The key challenge for this approach is how to nd the distribution (or deployment) of application components, which can yield the greatest bene ts. In this thesis, we tackle this problem and propose a set of algorithms, and a framework, to partition a work ow-based application over federated clouds in order to exploit the strengths of each cloud. The speci c goal is to split a distributed application structured as a work ow such that the security and reliability requirements of each component are met, whilst the overall cost of execution is minimised. To achieve this, we propose and evaluate a cloud broker for partitioning a work ow application over federated clouds. The broker integrates with the e-Science Central cloud platform to automatically deploy a work ow over public and private clouds. We developed a deployment planning algorithm to partition a large work ow appli- - i - cation across federated clouds so as to meet security requirements and minimise the monetary cost. A more generic framework is then proposed to model, quantify and guide the partitioning and deployment of work ows over federated clouds. This framework considers the situation where changes in cloud availability (including cloud failure) arise during work ow execution.

APA, Harvard, Vancouver, ISO, and other styles

11

Cooke, Alan. "X-Tools: A Case Study in Building World Class Software." International Foundation for Telemetering, 2010. http://hdl.handle.net/10150/605982.

Full text

Abstract:

ITC/USA 2010 Conference Proceedings / The Forty-Sixth Annual International Telemetering Conference and Technical Exhibition / October 25-28, 2010 / Town and Country Resort & Convention Center, San Diego, California
X-Tools is a collection of utilities for validation, translation, editing and report generation designed to enable the Flight Test Instrumentation (FTI) community to quickly adopt the XidML 3.0 meta-data standard. This paper discusses the challenges of developing such software that meets the current and future needs of the FTI community, and meets the increasingly high quality standards expected of modern software. The paper first starts by discussing the needs of the FTI community and the specific functional requirements of software. These include the ability to fit in with legacy systems, the ability to handle many tens of thousands of parameters, support for new networked-based technologies and support for hardware from any vendor. The non-functional requirements of FTI orientated software are also described and it is suggested that the key non-functional requirements include testability, modifiability, extensibility and maintainability. Finally, as a case study, the X-Tools from ACRA CONTROL are presented. The paper discusses their design, and the tactics used to meet the functional and non-functional requirements of the FTI industry. The paper then outlines how the rigorous quality standards were met and describes the specific mechanisms used to verify the quality of the software.

APA, Harvard, Vancouver, ISO, and other styles

12

Kolla, Madhuri, and Mounika Banka. "Merging Functional Requirements with Test Cases." Thesis, Malmö högskola, Fakulteten för teknik och samhälle (TS), 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:mau:diva-20363.

Full text

Abstract:

A lot of research is done in requirements engineering and testing but often the extensive literature is missing on defining good methods for linking functional requirements with test cases. Most of the delays occurring in the software development projects are because of incomplete or inaccurate functional requirements. The two main goals of our project are to achieve a successful software project by First, to design a template, which will merge functional requirements with test cases and second is to find the benefits of the aligning requirements to test cases. Changing, updating and tracing the requirements during the development of the project is not an easy task. The main reason for project failure is due to possibility of not fulfilling specified project requirements, so one way to solve this problem is to merge functional requirements with test cases. Thus removes the need of creating a separate requirements document, which will improve the traceability process between requirements and testing, thus leads to high quality and efficient development. The template helps us to drive a successful project by identifying the issues at an earlier stage of the development cycle.

APA, Harvard, Vancouver, ISO, and other styles

13

Tariq, Muhammad Adnan [Verfasser], and Kurt [Akademischer Betreuer] Rothermel. "Non-functional requirements in publish, subscribe systems / Muhammad Adnan Tariq. Betreuer: Kurt Rothermel." Stuttgart : Universitätsbibliothek der Universität Stuttgart, 2013. http://d-nb.info/1037955978/34.

Full text

APA, Harvard, Vancouver, ISO, and other styles

14

Heit, Jürgen. "Impact of methods and mechanisms for improving software dependability on non-functional requirements." [S.l. : s.n.], 2007. http://nbn-resolving.de/urn:nbn:de:bsz:93-opus-32394.

Full text

APA, Harvard, Vancouver, ISO, and other styles

15

Saadatmand, Mehrdad. "Satisfying Non-Functional Requirements in Model-Driven Development of Real-Time Embedded Systems." Licentiate thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-14533.

Full text

Abstract:

Design of real-time embedded systems is a complex and challenging task. Part of this complexity originates from their limited resources which incurs handling a big range of Non-Functional Requirements (NFRs). Therefore, satisfaction of NFRs plays an important role in the correctness of the design of these systems. Model-driven development has the potential to reduce the design complexity of real-time embedded systems by increasing the abstraction level, enabling analysis at earlier phases of development and code generation. In this thesis, we identify some of the challenges that exist in model-driven development of real-time embedded systems with respect to NFRs, and provide techniques and solutions that aim to help with the satisfaction of NFRs. Our end goal is to ensure that the set of NFRs defined for a system is not violated at runtime. First, we identify and highlight the challenges of modeling NFRs in telecommunication systems and discuss the application of a UML-based approach for modeling them. Since NFRs have dependencies, and the design decisions to satisfy them cannot be considered in isolation, we propose a model-based approach for trade-off analysis of NFRs to help with the comparison of different design models with respect to the satisfaction level of their NFRs. Following the issue of evaluating the interdependencies of NFRs, we also propose solutions for establishing and maintaining balance between different NFRs. In this regard, we categorize our suggested solutions into static and dynamic. The former refers to a static design and set of features which ensures and guarantees the balance of NFRs, while the latter means establishing balance at runtime by reconfiguring the system and runtime adaptation. Finally, we discuss the role of the execution platform in preservation and monitoring of timing properties in real-time embedded systems and propose an approach to enrich the platform with necessary mechanisms for monitoring them.
CHESS

APA, Harvard, Vancouver, ISO, and other styles

16

Domah, Darshan. "The NERV Methodology: Non-Functional Requirements Elicitation, Reasoning, and Validation in Agile Processes." NSUWorks, 2013. http://nsuworks.nova.edu/gscis_etd/137.

Full text

Abstract:

Agile software development has become very popular around the world in recent years, with methods such as Scrum and Extreme Programming (XP). Literature suggests that functionality is the primary focus in Agile processes while non-functional requirements (NFR) are either ignored or ill-defined. However, for software to be of good quality both functional requirements (FR) and NFR need to be taken into consideration; lack of attention to NFR has been documented to be the cause of failure for many software projects. Hence special attention needs to be focused on NFR in Agile software development. By its very nature Agile processes require frequent changes but these changes are often not well documented. This is especially true of NFR in Agile processes. While functional requirements are carefully identified, NFR are often not properly elicited. Once NFR are identified they become the basis for reasoning and facilitation of design and development decisions. NFR also need to be validated through proper testing to ensure their quality attributes have been met in the final software product. This dissertation aimed at developing a methodology for addressing NFR in Agile processes. As such, the "NERV Methodology: Non-Functional Requirements Elicitation, Reasoning, and Validation in Agile Processes" was proposed. Several artifacts were created as part of this methodology and included: the NFR Elicitation Taxonomy, the NFR Reasoning Taxonomy, the NFR Quantification Taxonomy, and the Non-Functional Requirements User Story Companion (NFRusCOM) Card. Additionally the NERV Agility Index (NAI) was developed using the Agile Manifesto and its twelve principles. The NERV Methodology was validated using the 26 requirements of the European Union (EU) eProcurement Online System. Additionally the results obtained by the NORMAP Methodology in previous research, were used as baseline. Results show that the NERV Methodology was successful in identifying NFR, for 55 out of 57 requirements sentences that contained implicit NFR, compared to 50 for the baseline. This represented a 96.49% success rate compared to 87.71% for the baseline; an improvement of 8.78%. Furthermore the NERV Methodology was successful in eliciting 82 out of 88 NFR compared to 75 for the baseline. The elicitation success rate was 93.18% compared to 85.24% for the baseline; an improvement of 7.94%. Agility was validated using the same data set as above. Two experiments investigated project durations measured in 2-week sprint iterations, commonly used in Scrum. Results show that the first experiment, using the "FR and NFR Simultaneous Scheme" completed all FR and NFR scope in 24 sprints. The second experiment, using the "FR First Then NFR Scheme" consumed 26 sprints. The first agile scheduling scheme delivered all scope two sprints earlier than the second scheme; representing a saving of almost one month. Validation results showed that the NERV Methodology and its artifacts can potentially be beneficial for software development organizations for eliciting, reasoning about, and validating NFR in Agile processes.

APA, Harvard, Vancouver, ISO, and other styles

17

Mahmood, Farrukh, and Waqas Rasheed. "Quality Requirement Abstraction Model (QRAM)." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3397.

Full text

Abstract:

Requirement engineering (RE) is an important phase in any project. Both functional and non-functional requirements are required to be elicited. Quality requirements (QRs) are usually catered at the end of software development process. Along with functional requirements, non-functional (QRs) also need to be handled and implemented through a structural way. It is observed that most organizations do not have proper management for quality requirements in their project life cycles. Especially if we consider the case of market driven requirement engineering (MDRE), it is a dire need to handle those QRs along with the functional requirement using a structural way. In this study we investigate Requirements Abstraction Model (RAM), which is basically designed for MDRE and is the case of continuous RE. The purpose was to analyze RAM specifications, which could be able to provide an effective way of manage QRs. RAM also deals with the specification of QRs, so it was required to investigate that how effective RAM can handle the creation of QRs.

APA, Harvard, Vancouver, ISO, and other styles

18

Chung, Jinpyung 1967. "Functional requirements to shape generation in CAD." Thesis, Massachusetts Institute of Technology, 2002. http://hdl.handle.net/1721.1/29628.

Full text

Abstract:

Thesis (Ph. D.)--Massachusetts Institute of Technology, Dept. of Mechanical Engineering, June 2003.
Includes bibliographical references (p. 119-121).
An outstanding issue in computer-aided design (CAD) is the creation of geometric shapes from the description of functional requirements (FRs). This thesis presents a method that can generate assembled shapes from the given FRs without human intervention. To achieve this goal, the design process follows a V-model of decomposition and integration based on axiomatic design. The V-model consists of three main sub-processes; (1) a top-down decomposition of FRs and design parameters (DPs), (2) mapping of DPs into geometric entities, and (3) a bottom-up integration of the geometric entities. A shape decomposition technique is used in the V-model to generate solid cells from the geometric entities in the CAD models based on FRs. These cells are stored and reused during the integration process. A set of cells mapped to an FR is called a functional geometric feature (FGF) to differentiate it from geometric features defined by only geometric characteristics. Each FGF has mating faces as its pre-defined interfaces. Links of FR-DP-FGF-INTERFACES and their hierarchies are made and stored in the database as fundamental units for automatic assembled shape generation. The retrieval of proper FGF from the database is performed by matching a query FR with stored FRs by a lexical search based on the frequency of words and the sequence of the words in the FR statements using a synonym checking system. The language-matching rate is calculated as a value of FRmetric between 0 and 1. A computer algorithm automatically combines and assembles the retrieved FGFs. Genetic algorithm (GA) searches for the best combination for matching interface types and generates assembly sequences.
(cont.) From the highest-valued chromosome, the computer algorithm automatically assembles FGFs by coordinating, orienting, and positioning with reference to the given mating conditions and calculates geometric interface-ability to a value of INTERFACEmetric between 0 and 1. The higher the values of FRmetric and INTERFACEmetric, the better the generated design solution for the given FRs that must be satisfied. The process of top-down decomposition and bottom-up integration reduces the number of possible combinations of interfacing FGFs. Design matrix visually relates FRs to FGFs. The method presented in this thesis has demonstrated that a "functional CAD" can aid designers in generating conceptual design solutions from functional descriptions, in reusing existing CAD models, and in creating new designs.
by Jinpyung Chung.
Ph.D.

APA, Harvard, Vancouver, ISO, and other styles

19

Chen, Baosheng. "Characterization and representation of functional requirements and functional tolerancing for concurrent design and manufacturing /." The Ohio State University, 1994. http://rave.ohiolink.edu/etdc/view?acc_num=osu1487856906256501.

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

Hussein, Nesrin. "Enhancing Software Security through Modeling Attacker Profiles." University of Cincinnati / OhioLINK, 2018. http://rave.ohiolink.edu/etdc/view?acc_num=ucin1523635219435409.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

Adamsson, Niklas. "Mechatronics engineering : New requirements on cross-functional integration." Licentiate thesis, Stockholm, 2005. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-152.

Full text

APA, Harvard, Vancouver, ISO, and other styles

22

Graham, James T. "Development of Functional Requirements for Cognitive Motivated Machines." Ohio University / OhioLINK, 2016. http://rave.ohiolink.edu/etdc/view?acc_num=ohiou1455711952.

Full text

APA, Harvard, Vancouver, ISO, and other styles

23

Čekanauskaitė, Jūratė, and Jolanta Čekanauskaitė. "Reikalavimų specifikacijos integralumo užtikrinimo metodas." Master's thesis, Lithuanian Academic Libraries Network (LABT), 2011. http://vddb.laba.lt/obj/LT-eLABa-0001:E.02~2011~D_20110831_145319-12912.

Full text

Abstract:

Darbo tikslas yra sukurti reikalavimų specifikavimo integralumą užtikrinantį metodą. Šiam tikslui įgyvendinti sukurtas procesų modelis, kurį sudaro trys pagrindiniai uždaviniai: reikalavimų identifikavimas, specifikavimas ir komponavimas. Pirmi du uždaviniai padeda identifikuoti besikertančius reikalavimus taip sumažinamas reikalavimų išsibarstymas specifikacijoje, nustatomos priklausomybės ir būtini reikalavimai. Komponavimo etapo tikslas yra sukomponuoti reikalavimus ir suteikti kūrėjams visą sistemos vaizdą bei nustatyti ir valdyti konfliktus tarp reikalavimų. Reikalavimų integralumas užtikrinamas visus reikalavimus, laikant vienoje formoje. Darbe išnagrinėti reikalavimų specifikavimo šablonai, klasifikavimo standartų bei reikalavimų valdymo įrankiai. Analizuojami besikertančių reikalavimų identifikavimo ir išgavimo strategijos. Atlikta funkcinių ir nefunkcinių reikalavimų integralumo metodų ir būdų analizė. Sukurtas šablonas reikalavimams specifikuoti, kuris apima funkcinius ir nefunkcinius reikalavimus, funkcinius ir nefunkcinius besikertančius reikalavimus. Reikalavimų valdymui sudarytas šablonas RequisitePro aplinkoje. Sukurtas MagicDraw paketo profilis, siekiant pateikti kūrėjams pilną sistemos vaizdą, atvaizduojant reikalavimų rinkinius panaudos atvejų diagramomis. Metodas patikrintas sudarant ATM sistemos reikalavimų specifikaciją, reikalavimai specifikuojami apimant funkcinius ir nefunkcinius reikalavimus, būtinus reikalavimus, funkcinius ir... [toliau žr. visą tekstą]
The aim of this work is to create A method for integrity support of requirements specification. For this purpose a process model is developed, which consists of three main tasks: the identification of requirements, specification and composition. The first two tasks helps to identify the crosscutting requirements of the following reduction the requirements dispersal in requirements specification, also identify responsibilities of requirements and identify required requirements. The goal of composition task is to compose the requirements to give the developer a view of the whole system and to identify and manage conflicts between requirements. Integrity of requirements are ensured keeping all requirements in a unique form. The paper analyzes the identification of crosscutting requirements and gathering strategies. The templates of requirements specification, standards of requirements classification and requirements management tools were analyzed. The methods and techniques of functional and non-functional requirements for the integrity were analyzed. The unique template for requirements specification was created, which includes functional and non-functional requirements, functional and non-functional crosscutting requirements. The template for requirements management was consisted in RequisitePro environment. The MagicDraw profile package was created, which provide the developer a view of the whole system, representing set of requirements for use case diagrams. The method... [to full text]

APA, Harvard, Vancouver, ISO, and other styles

24

Saadatmand, Mehrdad. "Preservation of Extra-Functional Properties in Embedded Systems Development." Doctoral thesis, Mälardalens högskola, Inbyggda system, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-27300.

Full text

Abstract:

The interaction of embedded systems with their environments and their resource limitations make it important to take into account properties such as timing, security, and resource consumption in designing such systems. These so-called Extra-Functional Properties (EFPs) capture and describe the quality and characteristics of a system, and they need to be taken into account from early phases of development and throughout the system's lifecycle. An important challenge in this context is to ensure that the EFPs that are defined at early design phases are actually preserved throughout detailed design phases as well as during the execution of the system on its platform. In this thesis, we provide solutions to help with the preservation of EFPs; targeting both system design phases and system execution on the platform. Starting from requirements, which form the constraints of EFPs, we propose an approach for modeling Non-Functional Requirements (NFRs) and evaluating different design alternatives with respect to the satisfaction of the NFRs. Considering the relationship and trade-off among EFPs, an approach for balancing timing versus security properties is introduced. Our approach enables balancing in two ways: in a static way resulting in a fixed set of components in the design model that are analyzed and thus verified to be balanced with respect to the timing and security properties, and also in a dynamic way during the execution of the system through runtime adaptation. Considering the role of the platform in preservation of EFPs and mitigating possible violations of them, an approach is suggested to enrich the platform with necessary mechanisms to enable monitoring and enforcement of timing properties. In the thesis, we also identify and demonstrate the issues related to accuracy in monitoring EFPs, how accuracy can affect the decisions that are made based on the collected information, and propose a technique to tackle this problem. As another contribution, we also show how runtime monitoring information collected about EFPs can be used to fine-tune design models until a desired set of EFPs are achieved. We have also developed a testing framework which enables automatic generation of test cases in order verify the actual behavior of a system against its desired behavior. On a high level, the contributions of the thesis are thus twofold: proposing methods and techniques to 1) improve maintenance of EFPs within their correct range of values during system design, 2) identify and mitigate possible violations of EFPs at runtime.
CHESS
MBAT
ITS-EASY

APA, Harvard, Vancouver, ISO, and other styles

25

Gurses, Ozgur. "Non-functional Variability Management By Complementary Quality Modeling In A Software Product Line." Master's thesis, METU, 2010. http://etd.lib.metu.edu.tr/upload/12612571/index.pdf.

Full text

Abstract:

Software product lines provide the opportunity to improve productivity, quality and time-to-market of software-based systems by means of systematic reuse. So as to accomplish systematic software reuse, elicitation of commonality knowledge is to be upheld by the analysis and management of variability knowledge inherent in domain requirements. Considerable effort is devoted to the management of functional variability, often neglecting the impact of quality concerns originating from non-functional requirements. In this thesis, a hybrid approach concentrating on the modeling of quantitative as well as qualitative concerns on quality has been proposed. This approach basically aims to support the domain design process by modeling non-functional variability. It further aims to support application design process by providing trade-off selection ability among quality concerns to control functional features that belong to the same domain. This approach is implemented and evaluated on an example domain to reveal its benefits on non-functional variability.

APA, Harvard, Vancouver, ISO, and other styles

26

Lidström, Christian. "Verification of Functional Requirements of Embedded Automotive C Code." Thesis, KTH, Skolan för datavetenskap och kommunikation (CSC), 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-191566.

Full text

Abstract:

Today's vehicles are increasingly controlled by embedded computer systems. Such systems are of safety-critical nature, where an error in the computation could have dire consequences. A common way to ensure that software works is testing, but as the complexity of these systems grows larger it gets harder to ensure enough coverage in the tests. Another way to ensure that software fulfills its requirements is formal verification, where properties of the code are proven mathematically to hold under certain conditions. Formal verification gives a higher level of confidence in the correctness of code than testing alone, but it is not as widely used within the industry. This project has examined whether current state-of-the-art tools for formal verification are ready to be used to verify real-life safety-critical code. To answer this, a case study on a module running in Scania's vehicles was performed. Several of the requirements were successfully verified. The thesis also identifies for what type of code and requirements this is possible, and describes a process for how it can be done.
Idag kontrolleras fordon allt mer av inbyggda datorsystem. Sådana system är säkerhetskritiska, där ett fel kan ha ödesdigra konsekvenser. Ett vanligt sätt att försäkra sig om att mjukvaran fungerar är testning, men när komplexiteten av dessa system växer blir det allt svårare att försäkra sig om att testen har tillräcklig täckning. Ett annat sätt att försäkra sig om att mjukvaran uppfyller dess krav är formell verifiering, där egenskaper hos koden bevisas matematiskt att hålla under vissa villkor. Formell verifiering ger ett högre förtroende för kods korrekthet än vad enbart testning skulle göra, men används ännu inte i lika stor utsträckning inom industrin. Detta projekt har undersökt huruvida moderna verktyg för formell verifiering är mogna att användas för att verifiera riktig säkerhetskritisk kod. För att svara på detta har en fallstudie av en modul i Scanias fordon genomförts. Flera av dess krav lyckades verifieras. Rapporten identifierar också för vilka typer av kod och krav detta är möjligt, och beskriver en process för hur det kan utföras.

APA, Harvard, Vancouver, ISO, and other styles

27

Maiti, Richard Rabin. "Capturing, Eliciting, and Prioritizing (CEP) Non-Functional Requirements Metadata during the Early Stages of Agile Software Development." NSUWorks, 2016. http://nsuworks.nova.edu/gscis_etd/968.

Full text

Abstract:

Agile software engineering has been a popular methodology to develop software rapidly and efficiently. However, the Agile methodology often favors Functional Requirements (FRs) due to the nature of agile software development, and strongly neglects Non-Functional Requirements (NFRs). Neglecting NFRs has negative impacts on software products that have resulted in poor quality and higher cost to fix problems in later stages of software development. This research developed the CEP “Capture Elicit Prioritize” methodology to effectively gather NFRs metadata from software requirement artifacts such as documents and images. Artifact included the Optical Character Recognition (OCR) artifact which gathered metadata from images. The other artifacts included: Database Artifact, NFR Locator Plus, NFR Priority Artifact, and Visualization Artifact. The NFRs metadata gathered reduced false positives to include NFRs in the early stages of software requirements gathering along with FRs. Furthermore, NFRs were prioritized using existing FRs methodologies which are important to stakeholders as well as software engineers in delivering quality software. This research built on prior studies by specifically focusing on NFRs during the early stages of agile software development. Validation of the CEP methodology was accomplished by using the 26 requirements of the European Union (EU) eProcurement System. The NORMAP methodology was used as a baseline. In addition, the NERV methodology baseline results were used for comparison. The research results show that the CEP methodology successfully identified NFRs in 56 out of 57 requirement sentences that contained NFRs compared to 50 of the baseline and 55 of the NERV methodology. The results showed that the CEP methodology was successful in eliciting 98.24% of the baseline compared to the NORMAP methodology of 87.71%. This represents an improvement of 10.53% compared to the baseline results. of The NERV methodology result was 96.49% which represents an improvement of 1.75% for CEP. The CEP methodology successfully elicited 86 out of 88 NFR compared to the baseline NORMAP methodology of 75 and NERV methodology of 82. The NFR count elicitation success for the CEP methodology was 97.73 % compared to NORMAP methodology of 85.24 %which is an improvement of 12.49%. Comparison to the NERV methodology of 93.18%, CEP has an improvement of 4.55%. CEP methodology utilized the associated NFR Metadata (NFRM)/Figures/images and linked them to the related requirements to improve over the NORMAP and NERV methodologies. There were 29 baseline NFRs that were found in the associated Figures/images (NFRM) and 129 NFRs were both in the requirement sentence and the associated Figure/images (NFRM). Another goal of this study was to improve the prioritization of NFRs compared to prior studies. This research provided effective techniques to prioritize NFRs during the early stages of agile software development and the impacts that NFRs have on the software development process. The CEP methodology effectively prioritized NFRs by utilizing the αβγ-framework in a similarly way to FRs. The sub-process of the αβγ-framework was modified in a way that provided a very attractive feature to agile team members. Modification allowed the replacement of parts of the αβγ-framework to suit the team’s specific needs in prioritizing NFRs. The top five requirements based on NFR prioritization were the following: 12.3, 24.5, 15.3, 7.5, and 7.1. The prioritization of NFRs fit the agile software development cycle and allows agile developers and members to plan accordingly to accommodate time and budget constraints.

APA, Harvard, Vancouver, ISO, and other styles

28

Nanduru, Pavan Kumar. "Non-Functional Requirement Modeling in the Early-Phase Software Product Life Cycle : A Systematic Literature Review and a Meta Model." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13986.

Full text

Abstract:

Context. Non-functional requirements (NFRs) are important aspects which directly or indirectly determine whether a product is a success or a failure. It becomes essential to incorporate and understand them, before the software product enters the development phase. Despite the increasing emphasis put into NFR studies (namely; models and frameworks etc.) over the past few years, most industries prefer not use these techniques or to deal with NFRs later, in simpler manners. This could limit the efficiency of the development process. Integration of the existing NFR models/frameworks into the earlier phases of the product life cycle can provide a systematic approach to plan and anticipate NFRs for any software product. Objectives. This study aims to provide a generic meta model which acts as a compilation of the best NFR models/frameworks integrated into the early phases of the software product life cycle. This study also provides a real-world example which applies the conceptual meta model. Lastly, the meta model undergoes some limited validation to determine its relevance to what is being used and the extent of its practical use. Methods. Initially, a systematic literature review (snowballing) was conducted, to identify the different types of NFR models/frameworks. A comparative pro-con analysis was performed on the results of the SLR, which was the basis of the inclusion criteria for the meta model. The conceptual meta model was developed based on the International Software Product Management Association’s (ISPMA) definition of a product life cycle. Each phase of this meta model was imbedded with an NFR model/framework associated to the purpose of that phase and the results from the SLR. The application of the meta model was then demonstrated using a mobile phone example. Finally, the meta model was validated limitedly via an exploratory survey and the results were analyzed. Results. The meta model introduced can be used for the constructive inclusion of NFRs from product inception to product development. All phases required for the fulfillment of an NFR, are included. The overall positive feedback of the meta model is at 67%. Validations and assessments by practitioners helped determine to some extent that some industries are open to using the approach. Keeping in mind most of the available models on NFRs have not been validated, the NFR works used in this research have gone through some preliminary validation in this study. Conclusions. The study promotes the use of NFR models in the early phases of the software product life cycle. Some of the best modeling techniques were included based on results of literature analysis and their capability to fit into each phase. This study also analyzed the various insights of practitioners and researchers, justifying the significance of modeling, and the proposed technique. Possible extensions to this research were also mentioned.

APA, Harvard, Vancouver, ISO, and other styles

29

Su, Mehmet Onur. "Business Process Moedlling Based Computer-aided Software Functional Requirements Generation." Master's thesis, METU, 2004. http://etd.lib.metu.edu.tr/upload/3/12604698/index.pdf.

Full text

Abstract:

Problems of requirements which are identified in the earlier phase of a software development project can deeply affect the success of the project. Thus studies which aim to decrease these problems are crucial. Automation is foreseen to be one of the possible solutions for decreasing or removing some of the problems originating from requirements. This study focuses on the development and implementation of an automated tool that will generate requirements in natural language from business process models. In this study, The benefits of the tool are discussed, and the tool is compared with other software requirement s related tools with respect to their functionality. The developed tool has been tested within a large military project and the results of using the tool are presented.

APA, Harvard, Vancouver, ISO, and other styles

30

Al-Sarayreh, Khalid. "Identification, specification and measurement, using international standards, of the system non functional requirements allocated to realtime embedded software." Mémoire, École de technologie supérieure, 2011. http://espace.etsmtl.ca/923/1/AL%2DSARAYREH_Khalid.pdf.

Full text

Abstract:

Au cours de la phase de l’analyse des besoins pour le développement d’un système, l’accent est souvent porté sur les besoins fonctionnels, tandis que les besoins non fonctionnels (Non Functional Requirements - NFR) sont capturés par les analystes systèmes seulement à un niveau très global : au cours de cette phase, les NFR sont décrits typiquement au niveau du système et non au niveau du logiciel. Le détail de ces besoins non fonctionnels est souvent précisé (c'est à dire défini au niveau de détail nécessaire) par les concepteurs du système à la phase de l’architecture et à la phase de conception du système. Pour le moment, il n’y a pas de consensus sur la manière de décrire et de mesurer les besoins non fonctionnels des systèmes (system-NFR) : c’est donc un défi de les prendre en compte dans l’estimation des efforts pour le développement des logiciels qui feront partie de ces systèmes et dans l’évaluation de la productivité des projets de développement de ces logiciels. Durant la phase de l’analyse des besoins pour les logiciel, les besoins non fonctionnels des systèmes peuvent être décrits et spécifiés comme étant les besoins fonctionnels alloués au logiciel : ceci permet alors aux ingénieurs logiciels de développer, tester et configurer les livrables finaux aux utilisateurs du système. La motivation de cette recherche est de contribuer à l’effort d’amélioration des modèles d’estimation des projets de développement logiciel en introduisant les exigences non fonctionnelles des systèmes au sein du processus d’estimation du projet logiciel et ce au travers d’une vue quantitative. Le but de cette recherche est d’aider les chefs de projets, les organisations ainsi que les chercheurs, à prendre des décisions éclairées sur les plannings des projets et sur le développement des logiciels et ce pendant la phase initiale d’identification des besoins, des spécifications et d’estimation des besoins non fonctionnels d’un système incluant du logiciel embarqué. Plus précisément, cette étude a comme but de contribuer à une meilleure définition, description et estimation de certains entrants, qui sont les besoins non fonctionnels du système, nécessaire pour réaliser une estimation préalable des couts. Dans les standards internationaux, un certain nombre de concepts sont utilisés afin de décrire différents types de besoins non fonctionnels des systèmes, que ces besoins soient au niveau du système, du logiciel ou du matériel. L’objectif de cette recherche est d’effectuer, le plus en amont possible, les spécifications et la quantification des besoins fonctionnel pour le logiciel, dérivés des besoins non fonctionnels au niveau système, en utilisant comme base les standards de l’ingénierie du logiciel. Pour atteindre cet objectif de recherche les deux sous-objectifs de recherche spécifiques suivants doivent être atteints: • Conceptions de modèles standards pour l’identification et la spécification des besoins fonctionnels de l'utilisateur (FUR) alloués au logiciel pour répondre aux besoins non fonctionnels du système (system-NFR). • Mesure de la taille fonctionnelle, en utilisant le standard COSMIC ISO 19761. des besoins fonctionnels alloués au logiciel pour répondre aux besoins non fonctionnels du système les résultats de cette recherche sont à un ensemble de quatorze (14) modèles de spécifications et de mesure, basés sur des standards, pour les besoins non-fonctionnels du système qui peuvent être alloués à du logiciel embarqué temps réel. La contribution principale de cette recherche est cet ensemble de quatorze modèles des besoins fonctionnels des utilisateurs du logiciel basés sur des standards pour l’identification, la spécification et la mesure des besoins non fonctionnels du système.

APA, Harvard, Vancouver, ISO, and other styles

31

Ives, Nadine E. (Nadine Elizabeth). "Functional ecology of hardwood trees under chronic drought." Thesis, McGill University, 1994. http://digitool.Library.McGill.CA:80/R/?func=dbin-jump-full&object_id=28786.

Full text

Abstract:

I compared the interrelationships among traits affecting interspecific variation in the growth of seedlings of 22 hardwood tree species subjected to chronic intermittent drought. Leaf traits were the most responsive to contrasting water regimes; canopy architecture, hydraulic conductivity and leaf phenology were less affected. Relative growth rate (RGR) under drought, however, was most closely related to variation in canopy duration: species in leaf longer had greater RGR. Secondarily, maintaining higher stomatal conductance (g) under drought further enhanced RGR. Higher g is associated with a higher photosynthetic rate (A), but the relationship between A and g varied with internal CO$ sb2$ concentration (c$ sb{ rm i}$), foliar nitrogen and specific leaf mass. Species with weaker homeostatic control over c$ rm sb{i}$ had higher water use efficiency. While photosynthetic characteristics were related primarily to species' shade tolerance, water use efficiency was most closely related to habitat moisture preference.

APA, Harvard, Vancouver, ISO, and other styles

32

Al-Ahmad, Bilal Ibrahim. "Domain Ontology Based Detection Approach to Identify Effect Types of Security Requirements upon Functional Requirements." Diss., North Dakota State University, 2015. https://hdl.handle.net/10365/27632.

Full text

Abstract:

Requirements engineering is a subfield of software engineering that is concerned with analyzing software requirements specifications. An important process of requirement engineering is tracing requirements to investigate relationships between requirements and other software artifacts (i.e., source code, test cases, etc.). Requirements traceability is mostly manual because of difficulties automating the process. A specific mode of tracing is inter-requirements traceability, which focuses on tracing requirements with other requirements. Investigating inter-requirements traceability is very important because it has significant influence on many activities of software engineering such as requirements implementation, consistency checking, and requirements impact change management. Several studies used different approaches to identify three types of relationships: cooperative, conflicting, and irrelevant. However, the current solutions have several shortcomings: (1) only applicable to fuzzy requirements, user requirements, and technical requirements, (2) ignoring the syntactic and semantic aspects of software requirements, and (3) little attention was given to show the influence of security requirements on functional requirements. Furthermore, several traceability tools have a lack of using predefined rules to identify relationships.

APA, Harvard, Vancouver, ISO, and other styles

33

Lundberg, Dan. "Functional Requirements for Bibliographic Records : Viktiga frågeställningar och områden för FRBR." Thesis, Linnéuniversitetet, Institutionen för kulturvetenskaper, KV, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-14178.

Full text

Abstract:

In this Bachelor's thesis the result from a Delphi study regarding FRBR, performed by Yin Zhang and Athena Salaba in 2007 and published in 2009 – What is next for Functional Requirements for Bibliographic Records? A Delphi study – is analyzed by qualitatively interviewing professionals active within the library and information science field in Sweden. The results are compared and possible deviations and adjustments are illuminated and discussed. The purpose of the thesis is to determine the topicality of the Delphi study in 2011 from a Swedish perspective. Conclusions made from the thesis shows that the main areas are still the same, but adjustments regarding the relative order of issues might be needed; primarily a shift of focus from theoretical to practical issues. More specifically, a focus on user aspects, user studies and authority work is needed.

APA, Harvard, Vancouver, ISO, and other styles

34

Sternudd, Patrik. "Unambiguous Requirements in Functional Safety and ISO 26262: Dream or Reality?" Thesis, Uppsala universitet, Institutionen för informationsteknologi, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-164883.

Full text

APA, Harvard, Vancouver, ISO, and other styles

35

Kamadia, Gopi. "The use of modeling tools in the analysis of functional requirements." Birmingham, Ala. : University of Alabama at Birmingham, 2008. https://www.mhsl.uab.edu/dt/2008m/kamadia.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Ellul, Claire Denise. "Querying topology in a 3D spatial database - functional requirements and performance optimisation." Thesis, University College London (University of London), 2008. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.500047.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

Wnukiewicz, Karol Kazimierz. "The role of quality requirements in software architecture design." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2253.

Full text

Abstract:

An important issue during architectural design is that besides functional requirements, software architecture is influenced greatly by quality requirements [9][2][7], which often are neglected. The earlier quality requirements are considered, the less effort is needed later in the software lifecycle to ensure a sufficient software quality levels. Errors due to lack of their fulfilment are the most expensive and difficult to correct. Therefore, attention to quality requirements is crucial during an architectural design. The problem is not only to gather the system’s quality requirements, but to establish a methodology that helps to deal with them during the software development. Literature has paid some attention to software architecture in the context of quality requirements, but there is still lack of effective solutions in this area. To alleviate the problem, this paper lays out important concepts and notions of quality requirements in a way they can be used to drive design decisions and evaluate the architecture to estimate whether these requirements are fulfilled. Important concepts of software architecture area are presented to indicate how important quality requirements are during the design and what are the consequences of their lack in a software system. Moreover, a quality requirement-oriented design method is proposed as an outcome of the literature survey. This method is a model taking quality requirements into account at first, before the core functionality is placed. Besides the conceptual solution to the identified problems, this paper also suggests a practical method of handling quality requirements during a design. A recommendation framework for choosing the most suitable architectural pattern from a set of quality attributes is also proposed. Since the literature provides insufficient qualitative information about quality requirement issues in terms of software architectures, an empirical research is conducted as means for gathering the required data. Therefore, a systematic approach to support and analyze architectural designs in terms of quality requirements is prepared. Finally, quality requirement-oriented and pattern-based design method is further proposed as a result of investigating patterns as a tool for addressing quality requirements at different abstraction levels of a design. The research is concerned with the analysis of software architectures against one or more desired software qualities that ought to be achieved at the architectural level.
http://wnukiewicz.pl kareel@gmail.com

APA, Harvard, Vancouver, ISO, and other styles

38

Yildiz, Okan. "An Approach For Eliciting Functional Requirements Of The Software Intensive Systems Based On Business Process Modeling." Master's thesis, METU, 2003. http://etd.lib.metu.edu.tr/upload/4/1260300/index.pdf.

Full text

Abstract:

In this thesis, eliciting system functional requirements based on business requirements during software intensive systems acquisition or development process is investigated and an approach is proposed for this purpose. Concepts and current problems within the framework of business requirements are investigated with a general literature review of requirements engineering and technology acquisition. Determination of requirements of IT system to be acquired according to the business objectives and base lining business processes is dealt with business process modeling. ARIS providing integrated and complete information system architecture along with modeling techniques and modeling tool is also investigated. Proposed approach recommends EEPC as process modeling technique and ARIS software as supporting toolset, and explains how to conduct application of automatic requirements eliciting from business process models, by extending a reporting script provided by ARIS software. Proposed approach was partially applied to the real project and the obtained results were presented in this thesis.

APA, Harvard, Vancouver, ISO, and other styles

39

Moradi, koutchi Behrang. "Contribution à la formalisation et à l'évaluation de propriétés non-fonctionnelles pour l’ingénierie de système complexe : application à la résilience." Thesis, IMT Mines Alès, 2019. http://www.theses.fr/2019EMAL0009.

Full text

Abstract:

Pour remplir la mission qui lui est assignée et atteindre les objectifs fixés, un système complexe doit satisfaire un ensemble d’exigences fonctionnelles et non fonctionnelles identifiées et formalisées. Parmi les exigences non fonctionnelles certaines sont identifiées comme mettant à disposition du système un ensemble de capacités lui permettant de satisfaire aux objectifs de sa mission. Ce référentiel intégré les exigences connues sous le nom d’ « -ilities » telles que la résilience, l’interopérabilité (De Weck , 2012). La résilience apparait comme une exigence importante et devant être maitrisée et maximisée par un système qui souhaite faire face à des perturbations et maintenir des niveaux de services et de performances acceptables. En effet, elle se définie comme « la capacité à résister, absorber, se rétablir ou s’adapter à une épreuve ou des changements » (Hollnagel, 2011). Dans ce contexte, une évaluation de la résilience peut permettre à des opérateurs humains d’identifier plus facilement les éléments (activités, techniques, humains…) qui pourraient tendre à améliorer le niveau de résilience. Les travaux présentés dans ce manuscrit portent sur la définition, la spécification et le développement d’une méthode pour l’évaluation de la résilience des systèmes. Si le concept de résilience n’est pas nouveau, les études existantes se limitent majoritairement au développement de méthodes d’évaluation basée sur la performance et la qualité de service d’un système. De plus ces méthodes se concentre souvent sur l’évaluation d’une seule des phases du cycle de vie de la résilience : anticipation ou réponse ou rétablissement. En ce sens ces méthodes n’intègrent pas les interactions existantes entre la résilience et les autres exigences. Dans cette thèse, nous nous intéressons à l’étude des interactions entre les exigences et la résilience afin de fournir une évaluation globale de la résilience du système et, ceci, dans chacune des phases du cycle de vie de la résilience. En conséquence, la méthode développée pour évaluer la résilience s’appuie sur l’analyse du réseau d’« -ilities » et à la caractérisation de la nature des relations qui existent entre la résilience et ces « -ilities ». La méthode proposée s’appuie sur deux contributions : la réalisation d’une cartographie de la résilience et la formalisation d’un indicateur de résilience nommé « opérabilité ». La cartographie permet d’identifier l’ensemble des « -ilities » qui sont en relation avec la résilience et, de les positionner relativement à leur implication dans le cycle de vie de la résilience (anticipation, réponse, rétablissement). Cette cartographie est réalisée à partir de l’analyse des travaux existants sur les « -ilities » et de son réseau (De Weck, 2012). C’est sur la base de ses relations et de la définition de leur nature l’indicateur de résilience est développé. L’évaluation fourni par notre indicateur (« opérabilité ») est qualitative. Elle s’appuie sur la définition d’un ensemble de paramètres (valeur courante, impact, priorité et existence) décrivant les interactions des autres « -ilities » sur la résilience. L’indicateur construit permet d’agréger tous ces paramètres afin de donner une évaluation de la résilience pour chaque phase de son cycle de vie. L’interprétation résultante est alors facilement exploitable par des opérateurs humains afin de leur de vérifier l’état courant de résilience voire de l’améliorer
To fulfill its mission and achieve its objectives, a complex system must satisfy a set of identified and formalized functional and non-functional requirements. Some non-functional requirements are identified as providing a set of capabilities allowing a system to reach its objectives. This repository includes the requirements known as « -ilities » such as the resilience or the interoperability (De Weck, 2012). The resilience is an important requirement that must be managed and maximized by a system that aims to face up to disruptions and maintain acceptable levels of service and performance. It is defined as "the ability to resist, absorb, recover or adapt to a test or change" (Hollnagel, 2011). In this context, the assessment of resilience enables human operators to easily identify the elements (activities, techniques, humans ...) that can improve the level of resilience. The here presented research work focuses on the definition, the specification and the development of a method to evaluate the resilience. Although the concept of resilience is not new, existing studies are mainly limited to the development of evaluation methods based on the performance and quality of service of a system. In addition, these methods often focus only on one phase of the resilience lifecycle: anticipation or response or recovery. In this sense, these methods do not integrate existing interactions between resilience and other requirements. In this research work, we focus on the study of the interactions between requirements and resilience to provide an overall assessment of the resilience in each of its lifecycle phases. As a result, the method developed to assess resilience is based on the analysis of the network of "-ilities" and the characterization of the nature of the relationships that exist between resilience and these « -ilities ». The proposed method is based on two contributions: the mapping of the resilience and the formalization of a resilience metric called "operability". Mapping allows to identify all « -ilities » linked to resilience and to position them according to their involvement in the life cycle of the resilience (anticipation, response, recovery). This mapping is based on the analysis of existing work on « -ilities » and its network (De Weck, 2012). According to its relationships and the definition of their nature the indicator of resilience is developed. The evaluation provided by the metric ("operability") is qualitative. It relies on the definition of a set of parameters (current value, impact, priority and existence) describing the interactions of other « -ilities » on resilience. The developed metric allows to aggregate all these parameters to give an evaluation of the resilience for each phase of its life cycle. The resulting interpretation is then easily exploitable by human operators in order to check the current state of resilience or improve it

APA, Harvard, Vancouver, ISO, and other styles

40

Sulyman, Muhammad, and Shahid Ali. "Applying Model Checking for Verifying the Functional Requirements of a Scania’s Vehicle Control System." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-15447.

Full text

Abstract:

Model-based development is one of the most significant areas in recent research and development activities in the field of automotive industry. As the field of software engineering is evolving, model based development is gaining more and more importance in academia and industry. Therefore, it is desirable to have techniques that are able to identify anomalies in system models during the analysis and design phase instead of identifying them in development phase where it is difficult to detect them and a lot of time, effort and resources are required to fix them. Model checking is a formal verification technique that facilitates the identification of defects in system models during early stages of system development. There are a lot of tools in academia and industry that provide the automated support for model checking. In this master thesis a vehicle control system of Scania the Fuel Level Display System is modeled in two different model checking tools; Simulink Design Verifier and UPPAAL. The requirements that are to be satisfied by the system model are verified by both tools. After verifying the requirements against the system model and checking the model against general design errors, it is established that the model checking can be effectively used for detecting the design errors in early development phases and can help developing better systems. Both the tools are analyzed depending upon the features supported. Moreover, relevance of model checking is studied with respect to ISO 26262 standard.

APA, Harvard, Vancouver, ISO, and other styles

41

Schneider, Marc. "Investigations on structural and functional requirements of the formation of human pre-catalytic spliceosomes." Berlin mbv, Mensch-und-Buch-Verl, 2009. http://d-nb.info/1000286517/04.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Lundius, Amelie. "Initial Assessment ofManufacturing ExecutionSystems : Development of a methodology to definebusiness needs and functional requirements." Thesis, KTH, Skolan för industriell teknik och management (ITM), 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-264568.

Full text

Abstract:

A key component of the smart factories that industry 4.0 introduce is the MES (manufacturing executionsystem). The MES lies above the actual shop floor in the enterprise system hierarchy and is not in directcontact with the actual production, in the way PLC (programmable logic control) or SCADA (supervisorycontrol and data acquisition) systems are. MES guide, initiate, respond to and reports on the productionactivities as well as distribute information to other company IT systems, bridging the gap between thecontrol systems of the shop floor and the information systems on an enterprise level. MES is a class ofinformation systems built to support shop floor processes and improve the integration to other departmentsof the enterprise by incorporating these systems into the overall IT-architecture. The main goal of an MESis to improve and optimize the production management functions and increase visibility into themanufacturing process. The role of the MES is defined by industry standards that identify what functionalities and dataflows anMES should include, and how it is intended to be integrated with other information systems. However, littleresearch has been focused on adopting these standards in actual MES implementation projects. The MESA(manufacturing executions system association) is presenting a standardized definition of MES as well as 2models of the, according to the standard, 11 key MES functionalities. The ISA-95 (IEC/ISO 62264)standard identifies sub-systems of an MES and defines the boundaries between the ERP, MES and otherautomation and IT systems. Company parameters such as manufacturing environment, production modeland plant type all affect the business needs and what MES functionalities are of priority. Hence, for an MESimplementation project, a business-specific evaluation must be performed. Prior research in the area is presenting a high-level workflow and best-practices of an MES implementationproject. By combining this workflow with the general software implementation standard ISO/IEC 12588(ISO/IEC 15288: System engineering – System lifecycle process), a methodology for performing the initialassessment of a company’s MES needs and business requirements is built. In the methodology models fromMESA and ISA-95 are applied to ensure an industry-accepted terminology and process. The objective ofthe methodology is to provide a standardized way to make an initial assessment of a company’s MES needsand specify system requirements. The methodology is validated through a study performed at discretemanufacturing line. The overall needs and specific functional requirements are identified through the methodology and arepresented according to a URS (user requirements specification) for an MES. The requirements areprioritizing according to MoSCoW analysis. Additional validation of the methodology must be performedto further evaluate the suitability of using the methodology for initial assessments of businesses’ MES needs.
En an nyckelkomponenterna för de smarta fabriker som industri 4.0 introducerar är MES (manufacturingexecution system). Dessa system verkar för tillverkande företag ovanför produktions golvet i en klassiskhierarkisk företagsstruktur och är inte i direkt kontakt med produktionen, till skillnad från exempelvis PLC-(programmable logic control) eller SCADA- (supervisory control and data acquisition) system. Trots detguidar, initierar, svara på och rapporterar MES systemet kring produktionsaktiviteter samt distribuerarinformation till företagets övriga IT-system, vilket överbryggar luckan mellan produktionsgolvetskontrollsystem och övriga informationssystem på företagsnivå. Ett MES är en grupp av informationssystembyggda för att stötta processerna på produktionsgolvet och dess integration med övriga delar av företaget. Genom att koppla samman det till företagets totala IT-arkitektur. Det huvudsakligamålet med ett MES äratt förbättra och optimera produktionsstyrnings funktioner samt öka insynen i tillverkningsprocesserna. Det existerar flertalet industristandarder som definierar vilken roll ett MES bör ha samt identifierar essfunktionaliteter samt relaterade data flöden och integrationer med övriga informations system. Å andra sidanär området kring hur dessa standarder bör tolkas och användas vid MES implementerings projekt. MESA(manufacturing execution system association) presenterar en standardiserad definition av vad MES är samttvå modeller över de 11 huvud funktionaliteter som systemet enligt standarden bör innefatta. ISA-95(IEC/ISO 62264) standarden identifierar del-system av ett MES samt definierar avgränsningen mellan ettföretags ERP (enterprise resource planning) system, MES system och övriga automations ochinformationssystem. Företags parametrar, som tillverknings system, produktions modell samt fabriks typ,påverkar alla systembehovet samt vilka funktionaliteter som är prioriterade hos ett MES. Därav krävs detatt företags specifika utvärdering utförs vid en MES implementering. Tidigare forsning inom området presenterar ett överblicks aktivitetsflöde och bästa praxis när det kommertill MES implementeringsprojekt. Genom att kombinera dessa med den generella mjukvaruimplementeringsstandarden ISO/IEC 15288 (ISO/IEC 15288: System engineering – System lifecycle process), byggs enmetodik för att utföra en initial bedömning av ett företags behov av ett MES system, där modellernapresenterade i MESA och ISA-95 är applicerade. Målet med metodiken är att före en standardiserad metodför att göre en initial bedömning av ett företags MES behov samt specificera systemkrav. Metodiken ärvaliderad genom en studie på en produktionslina. Genom att följa metodiken kan ett företags generella behov samt specifika funktionalitets krav specificerasi korrelation med generella användar-kravställningar för MES. För att validera metodikens lämplighet i detaktuella avseendet att göra en initial bedömning av ett företags MES behov krävs ytterligare utvärderingaroch validerings studier.

APA, Harvard, Vancouver, ISO, and other styles

43

Lautner, Erik, and Daniel Körner. "An integrated System Development Approach for Mobile Machinery in consistence with Functional Safety Requirements." Saechsische Landesbibliothek- Staats- und Universitaetsbibliothek Dresden, 2016. http://nbn-resolving.de/urn:nbn:de:bsz:14-qucosa-200666.

Full text

Abstract:

The article identifies the challenges during the system and specifically the software development process for safety critical electro-hydraulic control systems by using the example of the hydrostatic driveline with a four speed transmission of a feeder mixer. An optimized development approach for mobile machinery has to fulfill all the requirements according to the Machinery Directive 2006/42/EC, considering functional safety, documentation and testing requirements from the beginning and throughout the entire machine life cycle. The functionality of the drive line control could be verified in advance of the availability of a prototype by using a “software-in-the-loop” development approach, based on a MATLAB/SIMULINK model of the drive line in connection with the embedded software.

APA, Harvard, Vancouver, ISO, and other styles

44

Vieira, Andrws Aires. "Uma abordagem para estimação prévia dos requisitos não funcionais em sistemas embarcados utilizando métricas de software." reponame:Biblioteca Digital de Teses e Dissertações da UFRGS, 2015. http://hdl.handle.net/10183/117766.

Full text

Abstract:

O crescente aumento da complexidade dos sistemas embarcados demanda consigo a necessidade do uso de novas abordagens que acelerem o seu desenvolvimento, como por exemplo, o desenvolvimento baseado em modelos. Essas novas abordagens buscam aumentar o nível de abstração, utilizando conceitos de orientação a objetos e UML para modelar um software embarcado. Porém, com o aumento do nível de abstração, o projetista de software embarcado não possui a ideia exata do impacto de suas decisões de modelagem em questões importantes, como desempenho, consumo de energia, entre tantas outras que são de suma importância em um projeto embarcado. Dessa forma, se fazem necessárias técnicas de análise e/ou estimação de projeto que, em um ambiente de desenvolvimento mais abstrato, possam auxiliar o projetista a tomar melhores decisões nas etapas inicias de projeto, garantindo assim, as funcionalidades (requisitos funcionais) e os requisitos não funcionais do sistema embarcado. Neste trabalho, propõe-se estimar os requisitos não funcionais de um sistema embarcado a partir de informações (métricas) extraídas das etapas iniciais do projeto. Pretende-se com isso auxiliar o projetista na exploração do espaço de projeto já nos estágios iniciais do processo de desenvolvimento, através de uma rápida realimentação sobre o impacto de uma decisão de projeto no desempenho da aplicação em uma dada plataforma de execução. Os resultados experimentais mostram a aplicabilidade da abordagem, principalmente para um ambiente de evolução e manutenção de projetos de software, onde se tem um histórico de métricas de aplicações semelhantes para serem usadas como dados de treinamento. Neste cenário, a abordagem proposta possui acurácia de pelo menos 98% para as estimativas apresentadas ao projetista. Em um cenário heterogêneo, assumindo o uso da metodologia em um sistema diferente daquele usado para treinamento, a acurácia do método de estimação cai para pelo menos 80%.
The increasing complexity of embedded systems demands the use of new approaches to accelerate their development, such as model-driven engineering. Such approaches aim at increasing the level of abstraction using concepts such as object-orientation and UML for modeling the embedded software. However, with the increase of the abstraction level, the embedded software developer looses controllability and predictability over important issues such as performance, power dissipation and memory usage for a specific embedded platform. Thus, new design estimation techniques that can be used in the early development stages become necessary. Such a strategy may help the designer to make better decisions in the early stages of the project, thus ensuring the final system meets both functional and non-functional requirements. In this work, we propose an estimation technique of non-functional requirements for embedded systems, based on data (metrics) extracted from early stages of the project. The proposed methodology allows to better explore different design options in the early steps of software development process and can therefore provide a fast and yet accurate feedback to the developer. Experimental results show the applicability of the approach, particularly for software evolution and maintenance, which has a history of similar applications metrics to be used as training data. In this scenario, the accuracy of the estimation is at least of 98%. In a heterogeneous scenario, where the estimation is performed for a system that is different from the one used during training, the accuracy drops to 80%.

APA, Harvard, Vancouver, ISO, and other styles

45

Trudel, Sylvie. "Using the COSMIC functional size measurement method (ISO 19761) as a software requirements improvement mechanism." Mémoire, École de technologie supérieure, 2012. http://espace.etsmtl.ca/1003/1/TRUDEL_Sylvie.pdf.

Full text

Abstract:

Ce projet de recherche porte sur la contribution de l’utilisation de la méthode COSMIC (ISO 19761) de mesure de la taille fonctionnelle du logiciel à l’identification des défauts dans les spécifications fonctionnelles. Le mesureur de la taille fonctionnelle doit comprendre et interpréter les exigences fonctionnelles servant d’intrant à un mesurage. Dans l’industrie ces exigences sont typiquement écrites en langage naturel et sont propices aux ambigüités: des erreurs d’interprétation peuvent donc en découler. Les erreurs dans les spécifications fonctionnelles affectent le coût des étapes subséquentes du cycle de développement et d’évolution du logiciel: du travail additionnel est requis lorsque ces erreurs sont détectées et doivent être corrigées. Les organisations appliquent alors des techniques de revue et d’inspection permettant de détecter les erreurs dans les spécifications. Toutefois, ces techniques ne permettent pas de détecter l’ensemble des défauts dans un seul cycle de revue ou d’inspection, laissant ainsi un certain nombre de défauts résiduels dans le document de spécifications. Nonobstant l’application de telles techniques, un mesureur appliquant la méthode COSMIC peut identifier des défauts dans les spécifications fonctionnelles lorsque celles-ci ne définissent pas lairement les éléments attendus en intrant au mesurage. Les objectifs de ce projet de recherche sont de quantifier l’efficience et l’efficacité (coût unitaire) de l’utilisation de la méthode COSMIC en tant que mécanisme d’identification des défauts dans ces spécifications fonctionnelles, en comparant les résultats avec une approche d’inspection. L’efficacité et le coût unitaire sont établis à partir du nombre de défauts identifiés et de l’effort pour y parvenir. Les résultats démontrent que, en moyenne, les mesureurs participant à une inspection trouvent un nombre de défauts similaire à celui obtenu par l’ajout d’un inspecteur, ce qui maintient l’efficacité. En moyenne, le coût unitaire augmente légèrement puisque l’effort est légèrement supérieur, sauf qu’en plus, à ce coût, le projet obtient une mesure de la taille fonctionnelle utilisable à des fins d’estimation, d’étalonnage et de supervision des améliorations de processus. Sans l’apport d’identification des défauts, le mesurage de la taille fonctionnelle est considéré comme un coût de gestion. Avec l’identification des défauts de façon similaire à un inspecteur, le mesurage de la taille fonctionnelle peut alors être considéré comme un bénéfice qui crée de la valeur liée à l’économie de travail à refaire, puisque les défauts identifiés par un mesureur peuvent être corrigés relativement tôt dans le cycle de développement. À partir des expérimentations avec des experts et des praticiens dont l’expérience était limitée, il a été de plus observé que les praticiens nouvellement formés à la mesure de la taille fonctionnelle rencontraient plusieurs défis liés à la qualité de leurs résultats de mesure. Ce projet de recherche a donc contribué aussi à définir des exigences liées à la formation des mesureurs.

APA, Harvard, Vancouver, ISO, and other styles

46

Koene, Randal A. "Functional requirements determine relevant ingredients to model for on-line acquisition of context dependent memory." Thesis, McGill University, 2005. http://digitool.Library.McGill.CA:80/R/?func=dbin-jump-full&object_id=85561.

Full text

Abstract:

Biophysical simulations of memory must choose which aspects of known neurophysiology and neuroanatomy to model. Relevant aspects were constrained by functional requirements determined for on-line acquisition in context dependent memory, memory that is retrieved by contextual cues. In an on-line task, the protocol of data presentation and the tunes at which encoding or retrieval in memory is needed are not predetermined. A sequence of neuronal spike patterns representing items may be presented only once. Yet, episodic memory of the sequence immediately encodes the temporal context of familiar items, a process known to depend on hippocampal function. For this, interference caused by overlapping spike patterns must be avoided, a requirement that suggested the relevance of coincidental spiking. Overlap in the input to the hippocampus was reduced by recruiting such spikes in a model of encoding in dentate gyrus. Durable encoding is required in the hippocampus, since hippocampal damage can cause retrograde amnesia in context dependent memory that spans years. Long-lasting synaptic changes involved modeling relevant neurophysiology concerning protein production elicited by the spaced reactivation of spike patterns. The likelihood of reactivation was increased by the well-known process of long-term potentiation of synaptic transmission. Such potentiation is elicited when a presynaptic spike precedes a postsynaptic spike within a specific time window repeatedly. The intervals in a sequence of spike patterns must be compressed and the sequence repeated, requirements that were achieved with a model of short-term memory based on persistent spiking. Retrieval may be concurrent with these encoding processes due to effects of different phases of a brain rhythm at theta frequency (3-12 Hz) that modulate transmission and plasticity. A model of short-term memory by Lisman and Idiart (Science 267:1512-15), extended by Jensen et al. (Learning and Memory 3:243

APA, Harvard, Vancouver, ISO, and other styles

47

Nelson, Paul M. "A requirements specification of modifications to the Functional Description of the Mission Space Resource Center." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2001. http://handle.dtic.mil/100.2/ADA393372.

Full text

APA, Harvard, Vancouver, ISO, and other styles

48

Hedberg, Mikael. "Competences in Agile Development : Exploring the social, functional and cognitive requirements of a systems developer." Thesis, Umeå universitet, Institutionen för informatik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-101220.

Full text

Abstract:

Agile methodologies are becoming increasingly more popular among developers. However, there is little known research regarding the competences of working in development projects. This led me to my research question, what competences are considered important for working in agile projects? I narrowed down my research to three categories of competence; social, functional and cognitive. In order to gather the information needed for the study, I interviewed developers with and extensive knowledge and experience from working in agile development projects. The results from the study revealed that there is a need for a broad set of competences for working in agile development projects. This study is intended to contribute to the literature on competences is systems development by exploring the competence requirements for systems developers working in agile methods.

APA, Harvard, Vancouver, ISO, and other styles

49

Reilly, Dennis J. "Unitary Joint Standoff Captive Air Training Missile avionics design through operational concepts and functional requirements analysis /." Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 1996. http://handle.dtic.mil/100.2/ADA309753.

Full text

APA, Harvard, Vancouver, ISO, and other styles

50

Reilly, Dennis J. III. "Unitary Joint Standoff Captive Air Training Missile avionics design through operational concepts and functional requirements analysis." Thesis, Monterey, California. Naval Postgraduate School, 1996. http://hdl.handle.net/10945/9103.

Full text

Abstract:

Approved for public release; distribution is unlimited.
To accurately simulate the Unitary Joint Standoff (JSOW) weapon functions and provide pilots with the most realistic training, the captive air training missile (CATM) avionics design will fully implement well defined operational concepts and functional requirements in terms of flight simulation characteristics, operational functions, pilot feedback, and electronic interfaces. This would provide the Navy, Marines, and Air Force with a single, multi-capable, light weight CATM that consolidates CATM procurement, decreases aircraft turnaround time and increases aircrew training per flight hour.

APA, Harvard, Vancouver, ISO, and other styles

Dissertations / Theses on the topic 'Functional and non-functional requirements'

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles