Dissertations / Theses: 'Requirements engineering'

1

Matulevičius, Raimundas. "Process Support for Requirements Engineering : A Requirements Engineering Tool Evaluation Approach." Doctoral thesis, Norwegian University of Science and Technology, Faculty of Information Technology, Mathematics and Electrical Engineering, 2005. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-576.

Full text

Abstract:

Requirements engineering (RE) tools are software tools which provide automated assistance during the RE process. However, the RE practice relies on office tools rather than RE-tools provided by various companies. Reasons for not using the RE-tools include financial causes. The part of the problem also lies in the difficulty to evaluate such tools before acquisition to support the RE process. Hence, to support the completeness and effectiveness of RE-tool evaluation, a sound framework providing methodological guidelines is needed.

This work proposes an RE-tool evaluation approach (R-TEA), which provides a systematic way of the RE-tool assessment using two evaluation frameworks. The framework for the functional RE-tool requirements consists of three dimensions: representation, agreement, and specification. The representation dimension deals with the degree of formality, where requirements are described using informal, semiformal and formal languages. The agreement dimension deals with the degree of agreement among project participants through communication means. The specification dimension deals with the degree of requirements understanding and completeness at a given time moment. The second framework categorises the non-functional RE-tool features to process, product, and external requirements. Process requirements characterise constraints placed upon the user’s work practice. Product requirements specify the desired qualitative characteristics of RE-tools. External requirements are derived from the user’s internal and external environment.

Both frameworks are applied to a specification exemplar which application initiates preparation of the requirements specification for the RE-tool selection. Assessment of the RE-tools’ compatibility to the specified RE-tool requirements is performed using different evaluation techniques. Decision about RE-tool selection is made after summarising all the assessment results.

A prototype tool is developed supporting the frameworks and R-TEA. The R-TEA method is tested in a number of case studies. The findings report on positive trends of the frameworks, prototype and the R-TEA method.

APA, Harvard, Vancouver, ISO, and other styles

2

Palomares, Bonache Cristina. "Definition and use of software requirement patterns in requirements engineering." Doctoral thesis, Universitat Politècnica de Catalunya, 2016. http://hdl.handle.net/10803/403992.

Full text

Abstract:

The final quality of software products and services depends on the requirements stated in the Software Requirements Specifications (SRSs). However, some problems like ambiguity, incompleteness and inconsistency have been reported in the writing of SRSs, especially when natural language is used. Requirements reuse has been proposed as a key asset for requirements engineers to efficiently elicit, validate and document software requirements and, as a consequence, obtain SRSs of better quality through more effective engineering processes. Among all the possible techniques to achieve reuse, patterns hold a prominent position. In their most classical form, patterns describe problems that occur over and over again, and then describe the core of the solution to these problems. Software engineering practitioners have adopted the notion of pattern in several contexts, remarkably related to software design (e.g., design patterns and software architectural patterns), but also in other software development phases, both earlier and later. Following this strategy, requirement patterns emerge as a natural way to reuse knowledge during the Requirements Engineering (RE) stage. Although there have been several techniques proposed to reuse requirements, it has been observed that no concrete proposal has achieved a wide acceptance, neither any covered all the necessary elements to encourage organizations to adopt requirements reuse. As a consequence, this thesis proposes the use of Software Requirement Patterns (SRPs) as a means to capture and reuse requirements knowledge in the context of information technology projects. Following the typical context-problem-solution structure of patterns, an SRP mainly consists of: a template (solution) that may generate one or more requirements when applied in a certain project, and some information (context-problem) to identify its applicability in that project. To facilitate their use, SRPs are encapsulated inside the PABRE (PAttern-Based Requirements Elicitation) framework. The framework covers all the elements that could be critical for the adoption of a requirements reuse technique. Specifically, the framework includes: - A metamodel that describes the structure and semantics of SRPs and their organization inside a catalogue. - An SRP catalogue composed by non-functional, non-technical and functional SRPs, the functional ones being specific for the content management system domain. - A method for guiding the use of an SRP catalogue during requirements elicitation and specification, as well as another one for constructing and updating it. - An economic model to perform cost-benefit analysis on the adoption of SRPs based on return-on-investment. - The PABRE system as technological support. In order to analyse the benefits and drawbacks of the SRPs proposed in this thesis, two empirical studies have been carried out to investigate the perception of participants about requirement patterns in general and SRPs in particular. The first one is an exploratory survey addressed to information technology people with industrial experience in RE, which analyses the current state of the practice of requirement patterns approaches. The second one corresponds to a set of semi-structured interviews, focussed on the SRP approach, conducted to requirements engineers of Swedish organizations. Moreover, as it has been discovered that there are few empirical studies showing the state of the practice of requirements reuse in industry, the first study also explores the current situation of requirements reuse practices in organizations.
La qualitat final dels productes i serveis de software depèn del requisits definits en l’especificació de Requisits Software (ERS). Tot i així, alguns problemes com la ambigüitat, incompletesa i inconsistència han sigut detectats en la escriptura dels ERS, especialment quan el llenguatge natural és usat per escriure’ls. La reutilització de requisits ha sigut proposada com un recurs clau pels enginyers de requisits per tal d’obtenir, validar i documentar requisits software i, com a conseqüència, obtenir ERS de millor qualitat usant processos d’enginyeria més efectius. Entre totes les tècniques possibles per aconseguir la reutilització, els patrons tenen una posició destacada. En la seva forma més clàssica, els patrons descriuen problemes que ocorren sovint, i després descriuen la part central de la solució a aquests problemes. Els professionals de la enginyeria del software han adoptat la noció de patró en diferents àmbits, especialment en els relacionats amb el disseny del software (per exemple, els patrons de disseny i els patrons d’arquitectura del software), però també en altres etapes del desenvolupament del software, tant abans com després del seu disseny. Seguint aquesta estratègia, els patrons de requisits emergeixen com una manera natural de reutilitzar coneixement durant l’etapa d’enginyeria de requisits. Tot i que hi ha hagut varies tècniques proposades per reutilitzar requisits, s’ha observat que no hi ha cap proposta concreta que hagi aconseguit una àmplia acceptació, ni cap proposta completa que cobreixi tots els elements necessaris per animar a les organitzacions a adoptar la reutilització de requisits. Com a conseqüència, aquesta tesis proposa l’ús de Patrons de Requisits Software (en anglès Software Requirement Patterns o SRPs) com un medi per capturar i reutilitzar coneixement de requisits en l’àmbit de projectes de tecnologia de la informació. Seguint la estructura típica dels patrons de context-problema-solució, un SRP consisteix en: una plantilla (solució) que pot generar un o més requisits quan és aplicat en un projecte específic, i informació relacionada (context-problema) per identificar la seva aplicabilitat en un projecte. Per facilitar el seu ús, els SRP han sigut encapsulats dintre del framework PABRE (de l’anglès PAttern-Based Requirements Elicitation). El framework cobreix tots els elements que podrien ser crítics per adoptar una tècnica de reutilització de requisits. Més detalladament, el framework inclou: - Un meta model que descriu la estructura i semàntica dels SRPs i la seva organització dintre d’un catàleg.

APA, Harvard, Vancouver, ISO, and other styles

3

Deifel, Bernhard. "Requirements Engineering komplexer Standardsoftware." [S.l.] : [s.n.], 2001. http://deposit.ddb.de/cgi-bin/dokserv?idn=962786500.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Gunda, Sai Ganesh. "Requirements engineering : elicitation techniques." Thesis, University West, Department of Economics and IT, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:hv:diva-596.

Full text

Abstract:

Requirement engineering is the first and crucial phase in the development of software. The main aim of the requirement engineering process is gathering of requirements. It involves set of activities like system feasibility study, elicitation analysis, validation and management of the requirements. There are many methods already exist to perform the requirement gathering process and the software developers apply them to gather the requirements but still they are facing so many problems in gathering the requirements due to the lack of knowledge on result of the methods and selection of appropriate method. This affects the quality of software and increases the production cost of software. this paper presents the literature study and the experimental case study on analyzing and compare different methods for requirement gathering process, this provides the flexibility to requirements engineers to know the characteristics and the effectiveness of every method, it is useful to select the particular elicitation method depends on the type of application and the situation. And this analysis may be useful for the future development of new methods for requirement elicitation.

APA, Harvard, Vancouver, ISO, and other styles

5

Thew, Sarah Louise. "Value based requirements engineering." Thesis, University of Manchester, 2014. https://www.research.manchester.ac.uk/portal/en/theses/value-based-requirements-engineering(bcb4e1c2-32a7-4d79-a3b5-b8a3a1e9b73e).html.

Full text

Abstract:

Whilst numerous studies have retrospectively reported the impact of negative user emotions, motivational problems or value clashes during software developments, few Requirements Engineering (RE) studies have considered the elicitation of users’ values, motivations or emotions (VM&Es) and there is little advice for practising analysts as to how to deal with these factors. This thesis explores the impact of users’ VM&Es within RE work. The starting point was a review of the current state of analyst practice. A literature survey considered the RE guidance available to analysts on the elicitation and understanding of ‘soft issues’ such as VM&Es. In parallel, a series of interviews with 12 industry analysts sought their views on the relevance of users’ VM&Es, the impact on requirements work, and approaches to identifying such information. This study identified behaviours adopted by experienced analysts that would be useful to promote to novice analysts, and documented the analysts’ own requirements for a method to support them in eliciting VM&Es. These findings informed the design of the Value Based Requirements Engineering (VBRE) method and website (www.vbre.org.uk), intended to support requirements analysts in identifying and considering the impact of such ‘soft factors’. Research into RE method adoption highlights the importance of industry input, so a Participatory Design (PD) approach was taken in developing VBRE, iteratively evaluating and refining the method with input from practising analysts. A series of complementary evaluations of the method are presented. An experimental study investigated the method’s utility and usability with computer science undergraduate students, whilst a set of four case studies explored adoption of the VBRE method with industry analysts. The analysts used the method during their RE work, adapting the approach according to their circumstances and levels of experience. The participants credited the method with a positive impact on their RE work and the novice analysts reported feeling more confident of their abilities to handle ‘soft issues’. The key contributions of this work are:1. An exploration of the views of practising analysts as to the relevance and impact of VM&Es within their RE work.2. Development of an analysis method and support materials to aid analysts in identifying users’ VM&Es.3. A demonstration of the utility of adopting a PD approach to the development of RE methods.4. An evaluation of the use of the method in industry, exploring the use of case studies to understand how novice and expert analysts adopt and adapt the VBRE approach. This thesis is unusual in taking a PD approach to developing a solution for a RE problem: that analysts need to understand users’ VM&Es and their impact on software projects. The VBRE method attempts to address this gap, and the positive reception given by the analysts involved in evaluation of the method indicates they see utility in the approach. Future work will focus on continuing to collaborate with industry analysts to understand their use of the VBRE method, identifying improvements to the method and website, and gathering examples of the method’s impact.

APA, Harvard, Vancouver, ISO, and other styles

6

Pakki, Neetika Roy, and Sritheja Kavuri. "Managing Quality Requirements in Requirements Engineering Process : A survey." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13546.

Full text

Abstract:

Context. Requirements play vital role in building the software application.These requirements are of two types: Functional requirements andNon-functional requirements (or quality requirements). Many of the organizationsconsider only functional requirements during the early stages ofdevelopment cycle. Poor management of the non-functional requirementsmay affect factors such as success rate, project cost and standards of thebuilding product. So it is important to manage the quality requirements inthe right phase at the right time. Our thesis mainly concentrates on fivequality aspects of Requirements Engineering Process. The quality aspectsElicitation, Quality Requirements Metrics, Dependencies, Cost Estimationand Prioritization.We have concentrated on whether there are any changesin the focus on the quality requirements depending on the quality aspectsof requirement engineering process and in identifying which quality requirementis analysed at each of the five quality aspects depending on the functionalrequirements. And we also tried to identify the challenges faced bythe organizations due to handling of quality requirements at each of the fivequality aspects of the requirement engineering process in order to provideuseful information to the further studies to this problem. Objectives. In this thesis, we investigated how the quality requirementsare handled and managed in the 5 quality aspects of requirements engineeringprocess. The main objectives in this thesis are: To identify if the focus on quality requirements change with respect to tothe quality aspects of RE process. To identify a correlation between focusing on certain functional requirementand the resulting type of quality requirement i.e.; impact onquality requirements based on selected functional requirement. To identify the challenges faced by the organizations when focusing onthe quality requirements in each of quality aspects mentioned earlier. Methods. In this thesis study we first conducted a Systematic LiteratureReview (SLR) through Snowballing process to identify available literatureabout functional and non-functional requirements. Later Narrative analysiswas used to analyse the SLR results. Further an industrial survey wasconducted. Statistical analysis was performed, chi-square test of significancewas used to analyse the results. Results. The results for the research questions of this thesis are observedentirely through survey results. Data that is collected through SLR is usedto validate the obtained results. From the survey responses, it is observedthat among the five quality aspects that are identified through SLR, qualitymetrics is given more importance by large number of organisations and isfollowed by cost estimation. It is observed that elicitation is identified byless number of respondents. It is also observed that more number of respondentssuggested that there will not be any change in the focus of qualityrequirements depending on the quality aspects of RE process. It is identifiedthat there is a high impact of the selection of functional requirementson the quality requirements as per the survey results and majority of therespondents stated that the selection of quality requirements is dependenton the functional requirements. It is interesting that from the survey results,it is identified that almost half of the respondents’ organisations aretreating functional requirements equally and half of them are treating separately.Several challenges that may arise while implementing the qualityrequirements are also identified through both SLR and survey. Conclusions. This thesis help the further researches to get a detailed ideaon quality requirements, their usage in the organisations and the challengesfaced by them while implementing quality requirements. As this study involvedseveral observations that are related to the influence of functionalrequirements on quality requirements and the relation between the managementof quality requirements and RE process, it serves as a reference forfurther studies on quality requirements and gives scope to derive many newideas related to the maintenance of quality requirements. This work can befurther improved by considering large population of survey.

APA, Harvard, Vancouver, ISO, and other styles

7

Kösters, Georg. "Requirements engineering für GIS-Applikationen /." Aachen : Shaker, 1997. http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&doc_number=007834320&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Krishna, Chaitanya Konduru. "Scalability Drivers in Requirements Engineering." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13480.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Adikari, Sisira, and n/a. "Usability Modelling For Requirements Engineering." University of Canberra. Information Sciences & Engineering, 2008. http://erl.canberra.edu.au./public/adt-AUC20081204.145827.

Full text

Abstract:

For over two decades user-centric methods and techniques have been proposed to assist the production of usable, useful, and desirable software products. Despite these approaches, usability problems are still identified in finished software products creating problems at systems acceptance, rework and impacting end user experience. Part of the reason for these continuing problems is that user-centric approaches are not part of the traditional software engineering process. The literature review shows that software engineering and human-computer interaction are largely different communities. The aim of this thesis is to investigate whether the incorporation of user modelling and usability modelling into software requirements specifications would improve design quality and usability of software products. This research study used a Design Science dominant mixed research methodology consisting of case study and action research for creating, analysing and evaluating artefacts for improving the effectiveness of user-centred design and usability of software artefacts. Using the functional specification of an existing system in a government agency, ten designers created screen and interaction designs. The specification was then enhanced with usability specifications and the designers redeveloped their designs in the light of the enhanced specification. Both designs were subject to pre-defined usability tests and designers described their design experience as they worked. The results of the research demonstrated that enhancing traditional software requirements specifications with additional specifications of user modelling and usability modelling made a positive difference to both designer perception as well as design quality of user interface artefacts. The theoretical and practical values of these findings are explored.

APA, Harvard, Vancouver, ISO, and other styles

10

Smith, Simon Robert. "Formal justification in requirements engineering." Thesis, University of York, 1996. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.319716.

Full text

APA, Harvard, Vancouver, ISO, and other styles

11

Deacon, M. "Distributed Collaboration: Engineering Practice Requirements." Thesis, Linkt to the online version, 2007. http://hdl.handle.net/10019/755.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

Adikari, Sisira. "Usability modelling for requirements engineering /." Canberra, 2008. http://erl.canberra.edu.au/public/adt-AUC20081204.145827/index.html.

Full text

APA, Harvard, Vancouver, ISO, and other styles

13

Vergne, Matthieu. "Expert Finding for Requirements Engineering." Doctoral thesis, Università degli studi di Trento, 2016. https://hdl.handle.net/11572/369206.

Full text

Abstract:

Requirements Engineering (RE) revolves around requirements, from their discovery to their satisfaction, passing through their formalisation, modification, and traceability with other project artefacts, like preliminary interviews or resulting source codes. Although it is clear for many that involving knowledgeable people is an important aspect of many RE tasks, no proper focus has been given to Expert Finding (EF) systems, leading to have only few related works in the field. Our work attempts to fill this gap by investigating several dimensions of EF: conceptual by analysing the literature about expertise and its evaluation, formal by revising the usual representation of expert rankings, and practical by designing an EF system. As a result, we provide (i) a metamodel grounded in literature from Psychology to identify requirements for EF systems, (ii) a novel formalisation of experts rankings which solves limitations observed in usual EF measures, (iii) two variants of an EF system which builds on usual RE indicators (accessible knowledge and social recognition), and (iv) an enriched evaluation process which investigates deeper the consistency and correctness of an EF system.

APA, Harvard, Vancouver, ISO, and other styles

14

Vergne, Matthieu. "Expert Finding for Requirements Engineering." Doctoral thesis, University of Trento, 2016. http://eprints-phd.biblio.unitn.it/1703/1/vergne_final_thesis.pdf.

Full text

Abstract:

Requirements Engineering (RE) revolves around requirements, from their discovery to their satisfaction, passing through their formalisation, modification, and traceability with other project artefacts, like preliminary interviews or resulting source codes. Although it is clear for many that involving knowledgeable people is an important aspect of many RE tasks, no proper focus has been given to Expert Finding (EF) systems, leading to have only few related works in the field. Our work attempts to fill this gap by investigating several dimensions of EF: conceptual by analysing the literature about expertise and its evaluation, formal by revising the usual representation of expert rankings, and practical by designing an EF system. As a result, we provide (i) a metamodel grounded in literature from Psychology to identify requirements for EF systems, (ii) a novel formalisation of experts rankings which solves limitations observed in usual EF measures, (iii) two variants of an EF system which builds on usual RE indicators (accessible knowledge and social recognition), and (iv) an enriched evaluation process which investigates deeper the consistency and correctness of an EF system.

APA, Harvard, Vancouver, ISO, and other styles

15

Aaramaa, S. (Sanja). "Developing a requirements architecting method for the requirement screening process in the Very Large-Scale Requirements Engineering Context." Doctoral thesis, Oulun yliopisto, 2017. http://urn.fi/urn:isbn:9789526217079.

Full text

Abstract:

Abstract Requirements engineering (RE) is an important process in systems development. This research was carried out in the context of Very Large-Scale Requirements Engineering (VLSRE) within the scope of a requirement screening (RS) process. The RS process is defined as a front-end process for screening incoming requests, which are received in a constant flow. The goal of the RS process is to efficiently identify the most promising requests for further analysis, development and implementation while filtering out non-valuable ones as early as possible. The objective of this study was to understand the challenges related to the RS process and develop solutions to address those challenges. A qualitative research approach was utilised to achieve the research goals. The overall research process follows an action research method, in which each action research cycle includes at least one individually defined and executed case study. Action research and case studies are research methods that are well suited to studying real-life phenomena in their natural settings. This research was carried out in two case companies in the information and communication technology domain. Data from 45 interviews were analysed for preparing publications I–V, which are included in this thesis. In addition, during the longitudinal action research study described in this thesis, data from 26 interviews and 132 workshops were utilised to develop solutions for the RS process, which is an industrial implementation of the VLSRE process. The conducted action research contributes to the field of software engineering, in which such research efforts are currently lacking. This research has identified a number of significant challenges that different stakeholders face related to requirements processing and decision making in the VLSRE context. Examples of these challenges are the great number of incoming requirements, the lack of information for decision making and the feasibility of utilised tools. To address the identified challenges, a requirements architecting method was developed. The method includes a dynamic requirement template, which gathers structured information content for eliciting requests, documenting and communicating requirements and forming features while considering the needs of different stakeholders. The method was piloted, validated and deployed in industry
Tiivistelmä Tutkimus toteutettiin laajamittaisen vaatimusmäärittelyprosessin kontekstissa keskittyen vaatimusten seulontaprosessiin. Vaatimusten seulontaprosessi määritellään tuotekehityksen alkuvaiheen prosessiksi, jossa käsitellään jatkuvana vuona tulevia kehityspyyntöjä. Vaatimusten seulontaprosessissa pyritään tunnistamaan tehokkaasti lupaavimmat pyynnöt jatkoanalyysiä, tuotekehitystä ja toteutusta ajatellen sekä suodattamaan pois niin aikaisessa vaiheessa, kun mahdollista ne pyynnöt, joilla ei ole arvontuotto-odotuksia. Tutkimuksen tavoite oli ymmärtää haasteita, jotka liittyvät vaatimusten seulontaprosessiin sekä kehittää ratkaisuja näihin haasteisiin. Tutkimuksessa käytettiin laadullisen tutkimuksen menetelmiä. Kokonaisuutena tutkimusprosessi noudattaa toimintatutkimuksen periaatteita siten, että jokainen sykli tai sen vaihe sisältää yhden tai useamman itsenäisesti määritellyn tapaustutkimuksen suunnittelun ja läpiviennin. Valitut tutkimusmenetelmät soveltuvat hyvin tilanteisiin, joissa tutkimuskohteina ovat reaalimaailman ilmiöt niiden luonnollisissa ympäristöissä havainnoituina. Tutkimusaineisto kerättiin kahdesta informaatio- ja kommunikaatioteknologia-alan kohdeorganisaatiosta. Väitöskirjaan sisällytettyihin julkaisuihin I-V on analysoitu 45 haastattelun aineisto. Näiden lisäksi väitöskirjassa kuvatun pitkäkestoisen toimintatutkimuksen aikana hyödynnettiin 26 haastattelun ja 132 työpajan aineistoa kehitettäessä ratkaisuja vaatimusten seulontaprosessin haasteisiin. Vaatimusten seulontaprosessi on laajamittaisen vaatimusmäärittelyprosessin teollinen toteutus. Tutkimuksessa tunnistettiin useita merkittäviä haasteta, joita eri sidosryhmillä on liittyen vaatimusten seulontaprosessiin ja päätöksentekoon laajamittaisessa vaatimusmäärittelyprosessissa. Vaatimusten suuri määrä, päätöksentekoon tarvittavan tiedon puute ja käytössä olevien työkalujen soveltumattomuus ovat esimerkkejä tunnistetuista haasteista. Ratkaisuna haasteisiin kehitettiin vaatimusten seulonta- ja analyysimenetelmä. Kehitetty menetelmä sisältää dynaamisen vaatimusdokumentin, jonka avulla voidaan kerätä kehityspyyntöjen tietosisältö jäsennellysti, dokumentoida ja kommunikoida vaatimukset sekä muodostaa niistä tuotteisiin toteutettavia ominaisuuksia ottaen huomioon eri sidosryhmien tarpeet. Kehitetty menetelmä on koestettu, validoitu ja soveltuvin osin otettu käyttöön teollisuudessa

APA, Harvard, Vancouver, ISO, and other styles

16

Ryndina, Ksenia. "Improving Requirements Engineering: An Enhanced Requirements Modelling and Analysis Method." Thesis, University of Cape Town, 2005. http://pubs.cs.uct.ac.za/archive/00000201/.

Full text

Abstract:

Inadequate requirements engineering is considered to be one of the top causes of software development project failure today. One of the major problems is the lack of processes, techniques and automated tool support available to developers for specification methodology by enhancing the approach that is most popular at the moment - use case modelling. Despite their popularity, use case models lack structure and precision, which makes formal analysis of such models impossible. In our proposal, we amend traditional use case models with formal structure and semantics to make them suitable for automayed analysis. The enhanced use case modelling method that we propose is called Susan ("S"ymbolic "us"e case "an"alysis), whcih facilitates anaysis of use case models using model checking. We also developed a software tool called SusanX to construct, manipulate and analyse Susan models. The analysis feature of the tool is implemented using publicly available NuSMV model checker, which allows verification of finite state systems for behavioural properties expressed in temporal logic. A number of generic properties that can be used for verification of any Susan model are built into the SusanX tool. Additionally, SusanX permits the user to define model-specific properties for verification. This is done through property specification patterns, which allow one to express logic properties without knowing the details of the underlying formalism. In order to evaluate how valuable Susan and the SusanX tool are in solving real world problems, we performed a case study of a Cash Management System (CMS). The case study was done in collaboration with an established South African software development company, which provided use with the requirements specifications for the system. We successfully used the Susan notation to model the CMS requirements and performed various analyses on the models with SusanX. The state of requirements specifications was considerably improved through this process and numerous errors were discovered during the SusanX analyses.

APA, Harvard, Vancouver, ISO, and other styles

17

Zahda, Showayb. "Obsolete Software Requirements." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2148.

Full text

Abstract:

Context. Requirements changes are unavoidable in any software project. Requirements change over time as software projects progress, and involved stakeholders (mainly customers) and developers gain better understanding of the final product. Additionally, time and budget constraints prevent implementing all candidate requirements and force project management to select a subset of requirements that are prioritized more important than the others so as to be implemented. As a result, some requirements become cancelled and deleted during the elicitation and specification phase while other requirements are considered not important during the prioritization phase. A common scenario in this situation is to leave the excluded requirements for being considered in the next release. The constant leaving of the excluded requirements for the next release may simply render them obsolete.

APA, Harvard, Vancouver, ISO, and other styles

18

Kola, Abhinav Ram. "Customer communication challenges in Agile Requirements Engineering." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-20645.

Full text

Abstract:

Context and background: Requirements engineering(RE) is a first and a very important phase in any software development which helps in building a suitable and customer satisfactory product. In the past few years, the use of Agile software development has become popular in the industry. Customer communication plays an important role in any software development life cycle. Customers state the requirements needed to develop a product in the Requirements Engineering phase. A project is likely to fail due to problems in customer communication during the RE phase. Objective: This thesis aims to study the Customer communication challenges in Agile requirements engineering, prioritize these challenges, and also find out the mitigation strategies to overcome these challenges. Research Method: A systematic mapping study is conducted to find out the customer communication challenges. Based on the data collected from the systematic mapping study, a survey is conducted to find out the mitigation strategies to overcome the customer communication challenges faced in the RE phase and also prioritize these challenges. Results: Based on the data collected from the systematic mapping study, a total of 18 customer communication challenges are identified. In the second step, a survey is conducted based on the identified challenges. The prioritization of these challenges is done by calculating the risk analysis of the challenges from the survey data. And finally, mitigation strategies are mentioned to overcome all the identified 18 challenges.

APA, Harvard, Vancouver, ISO, and other styles

19

Wang, Qianneng, and Yujie Huang. "Identification and Management of Requirements Debt : Systematic Mapping Study and Survey." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-20649.

Full text

Abstract:

Background: Technical debt(TD) is incurred when developers accept compromises in a system in one dimension to meet urgent demand in some other dimensions (e.g., a deadline). If technical debt is not managed correctly, it will cause hidden danger to software’s long term success. It does not get enough attention when TD applies to the requirements engineering. Objectives: In this study, we investigate the current state of requirements debt(ReD). We aim to give a precise definition of ReD. We also focus on the factors that can induce ReD in the requirement engineering and requirement management process. Moreover, we want to summarize the measurement tools to detect and locate the ReD. Finally, we try to find approaches and ideas to manage ReD. Methods: We conducted a systematic mapping study (SMS) and a survey for all of the objectives. When performing the systematic mapping study, we applied snow- balling method to ensure we find related and enough papers. Results: According to the analysis and results of SMS and the survey, we concluded the definition of requirements debt. We also presented and classified 54 ReD induced factors into 8 categories. 10 ReD measurement techniques searched from literatures were listed with a brief description for each one, suggestions from software practi- tioners on ReD detection also gathered and displayed. The management techniques and theoretical suggestions were presented based on related factors. Conclusions: From research result, we find academia and industry lay different emphasises on how to manage ReD. To stimulate Industry pay more attention on control and manage ReD effectively, this paper calls for the two sides to work on the same point.

APA, Harvard, Vancouver, ISO, and other styles

20

OLIVEIRA, ANTONIO DE PADUA ALBUQUERQUE. "INTENTIONAL REQUIREMENTS ENGINEERING: A METHOD FOR REQUIREMENTS ELICITATION, MODELING, AND ANALYSIS." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2008. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=13061@1.

Full text

Abstract:

Nos dias atuais, muito mais do que no passado, é sabido que o sucesso de projetos de software depende criticamente de requisitos. Um exemplo de GORE, que significa Engenharia de Requisitos Orientada a Metas, é o Framework i* (iestrela). Este afirma que os requisitos devem representar a intencionalidade do grande número de atores sociais, os quais são pessoas ou sistemas. Dentro desse contexto, existe ainda um vazio de métodos para cobrir o processo da elicitação de metas. Vários métodos para SMA (Sistemas Multi-Agentes) mencionam a elicitação das metas, mas eles não fornecem detalhes de como essa atividade é feita, eles tratam principalmente da modelagem de metas sem antes cuidar dos detalhes da elicitação. Em adição, modelos intencionais como exemplo o Framework i*, podem ser complexos e até mesmo incompreensíveis. Esta tese propõe um método chamado ERi*c – “Engenharia de Requisitos Intencional”, o qual primeiro provê um processo de elicitação que aplica uma abordagem “bottom-up” e simples, com perguntas que podem identificar metas concretas e metas flexíveis. Além disso, o método Eri*c propõe uma solução para reduzir o problema da “escalabilidade” de modelos i* que inclui heurísticas para a especificação desses modelos. O método contém também uma estratégia para fazer diagnósticos de modelos i* de maneira a cobrir o processo de análise de requisitos.
Nowadays, much more than in the past, it is known that the success of software projects depends critically on the requirements. Goal Oriented Requirements Engineering - GORE, for example i Framework, says that requirements must represent the intentionality of a large number of social actors, which can be people or systems. Several Multi-Agent Systems (MAS) methods mention goals elicitation but they do not provide details of how this is performed, they mainly focus on goals modeling. In this context, there is still a lack of methods to cover the goal elicitation process. Only after eliciting goals, requirements engineers will be able to deal properly with goal models. Typically, this is a difficult task to carry on since requirements engineers are not familiarized with the domain from the early stages of software development. And, intentionality models, for example i Framework, can be complex and incompreensible. This thesis proposes a method called ERi c - Engenharia de Requisitos Intencional which provides an inquire process that can identify goals and softgoals in a bottom-up and simple elicitation approach together with one solution to reduce the problem of scalability of i models. The method ERi c also includes heuristics for modeling specification and a diagnoses aproach in order to analyze i models.

APA, Harvard, Vancouver, ISO, and other styles

21

Wanganga, George. "Effective Requirements Management." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2004. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2369.

Full text

Abstract:

In many smaller companies, requirements management is a daunting challenge. Smaller groups mean fewer resources, and many organizations focus their efforts on design, development and testing not on managing requirements. Some small organizations may perceive requirements management as an activity only for large organizations that have complex products and large staffs to support the effort. Poor and uncontrolled requirement engineering processes yield low quality, highly expensive software products. Obviously, customers are highly dissatisfied with such systems. One of the most critical requirement engineering processes that grossly contribute to this misnomer is lack of “effective requirements management” Information Technology Associates (ITA) has had many challenges resulting from some poor and uncontrolled requirements engineering processes. Lack of effective requirements traceability has also had its share in plaguing ITA in software development activities. ITA started small and so it handled its requirements documentation manually as it only dealt with few customer requirements. Time has seen the company expand, and manual handling of customer requirement became difficult. This master thesis therefore aims to investigate: ♦ The state-of-practice, regarding requirements engineering and requirements management within a medium-sized software development company. ♦ How to successfully implement effective requirement management process within the ITA Company. ♦ How to successfully migrate ITA Company into this RE process while ensuring minimum hassles.

APA, Harvard, Vancouver, ISO, and other styles

22

Page, Christopher J. Reese Jean D. "Networking requirements analysis for Engineering 2000 /." Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 1996. http://handle.dtic.mil/100.2/ADA311386.

Full text

Abstract:

Thesis (M.S. in Information Technology Management) Naval Postgraduate School, March 1996.
Thesis advisor(s): Norman F. Schneidewind, Martin J. McCaffrey. "March 1996." Includes bibliographical references. Also available online.

APA, Harvard, Vancouver, ISO, and other styles

23

Swärd, Michael. "Konsultföretags metodanvändande under Requirements Engineering Processen." Thesis, University of Skövde, Department of Computer Science, 2001. http://urn.kb.se/resolve?urn=urn:nbn:se:his:diva-553.

Full text

Abstract:

Requirements Engineering processen, RE-processen, är den tidiga fasen i ett systemutvecklingsprojekt, där RE-processens syfte är att identifiera, verifiera, validera samt dokumentera en mängd krav som ett nytt eller utvidgat system skall konstrueras efter. RE-processen skall mynna ut i en kravspecifikation där de dokumenterade kraven finns samlade.

Detta examensarbete behandlar ämnet systemutveckling och fokuserar på konsultföretags metodanvändande under RE-processen. Att fokus ligger på RE-processen beror på att denna fas är den mest kritiska delen i ett systemutvecklingsprojekt.

För att få svar på vilka metoder som konsultföretag använder under RE-processen har en intervjundersökning gjorts.

Resultatet av undersökningen visar att konsultföretag använder olika metoder under RE-processen. Sättet att använda dem fungerar på ungefär samma sätt med ett aktivt deltagande från kundernas sida. Systemutvecklingsmetoderna är också uppbyggda på liknande sätt med samma synsätt att arbeta efter.

APA, Harvard, Vancouver, ISO, and other styles

24

Zhu, Yunyun. "Requirements Engineering in an Agile Environment." Thesis, Uppsala University, Department of Information Technology, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-108027.

Full text

Abstract:

The Requirements Engineering (RE) process often dominates the quality of a project.The requirement practices in a project team are supposed to be an important part ofthe whole software development process. Today lean and agile development isbecoming more and more popular in industry. Many project teams work in an agileenvironment in order to have rapid delivery of high-quality software. Usually the workof the teams adopting an agile methodology is flexible and changeable. This indicatesthat the requirements of the projects might also be frequently changed, which is avariation to the traditional RE that relies on long and detailed documentation.

This thesis investigates how to conduct a RE process under an agile environment – sothat there exist relatively formal but agile and changeable requirements within aproject. The methods planned to be used are literature study, a case study carriedout in two software development teams in the Test Tool & Support Section at SonyEricsson Mobile Communications AB, and one pilot in each team based on the casestudy. There were 11 employees interviewed, including eight developers, two productowners and one scrum master. The evaluation on the pilots was mainly based on thefeedback from the interviewees on the pilot.

The outcome of the evaluation was that one of the teams (BRAT team) should adoptuser stories for user-related requirements, “done criteria” and non-functionalrequirements, and have the product owner to do the demonstration during the sprintreview in the future. Also, when budget allows, they should have one or morefull-time testers in the team and formal documentation of the requirements. Besidesthe suggestion for the BRAT team, QC team was suggested to have a glossary,formalize the defect description and have the product owner to ask the customersfor the feedbacks on the developers’ thoughts about the uncertain requirements.

APA, Harvard, Vancouver, ISO, and other styles

25

Chiwenda, Madock. "Requirements Engineering Skills Development : A Survey." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2004. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5780.

Full text

Abstract:

Software projects are among the failure prone projects in engineering and software requirements problems have been attributed to be one of main reasons to software project failures. There are many techniques and methodology developed for practitioners to use in working with software requirements, which makes it impossible for one to master them during formal education. In addition, many of the practitioners are coming from different disciplines. Thus they are required to learn in practice. Previous studies have shown informal learning (i.e. not planned or run by institutions or organizations) to be more effective and more used in workplace learning situations. The study investigates how the requirements engineering skills are and can be learned in workplace especially informally. By comparing the results obtained by the literature study and empirical study the recommendations are given on how one can recognise, utilise, and encourage the informal learning activities to develop requirements engineering skills. The study does not rule out the need to have the formal education and training in requirements engineering but identify it as an important prerequisite and/or complement. It provides insight on how informal learning practices are utilised by practitioners who are rather experienced in requirements engineering and how they could try to recognise and/or utilise other learning opportunities presented by previous literature. It furthermore offers general recommendations of how to utilise the informal learning for developing requirements engineering skills and other related disciplines.

APA, Harvard, Vancouver, ISO, and other styles

26

Alalshuhai, Ahmed. "Requirements engineering of context-aware applications." Thesis, De Montfort University, 2015. http://hdl.handle.net/2086/12487.

Full text

Abstract:

Context-aware computing envisions a new generation of smart applications that have the ability to perpetually sense the user’s context and use these data to make adaptation decision in response to changes in the user’s context so as to provide timely and personalized services anytime and anywhere. Unlike the traditional distribution systems where the network topology is fixed and wired, context-aware computing systems are mostly based on wireless communication due to the mobility of the network nodes; hence the network topology is not fixed but changes dynamically in an unpredictable manner as nodes join and the leave network, in addition to the fact that wireless communication is unstable. These factors make the design and development of context-aware computing systems much more challenging, as the system requirements change depending on the context of use. The Unified Modelling Language (UML) is a graphical language commonly used to specify, visualize, construct, and document the artefacts of software-intensive systems. However, UML is an all-purpose modelling language and does not have notations to distinguish context-awareness requirements from other system requirements. This is critical for the specification, visualization, construction and documentation of context-aware computing systems because context-awareness requirements are highly important in these systems. This thesis proposes an extension of UML diagrams to cater for the specification, visualization, construction and documentation of context-aware computing systems where new notations are introduced to model context-awareness requirements distinctively from other system requirements. The contributions of this work can be summarized as follows: (i) A context-aware use case diagram is a new notion which merges into a single diagram the traditional use case diagram (that describes the functions of an application) and the use context diagram, which specifies the context information upon which the behaviours of these functions depend. (ii) A Novel notion known as a context-aware activity diagram is presented, which extends the traditional UML activity diagrams to enable the representation of context objects, context constraints and adaptation activities. Context constraints express conditions upon context object attributes that trigger adaptation activities; adaptation activities are activities that must be performed in response to specific changes in the system’s context. (iii) A novel notion known as the context-aware class diagram is presented, which extends the traditional UML class diagrams to enable the representation of context information that affect the behaviours of a class. A new relationship, called utilisation, between a UML class and a context class is used to model context objects; meaning that the behaviours of the UML class depend upon the context information represented by the context class. Hence a context-aware class diagram is a rich and expressive language that distinctively depicts both the structure of classes and that of the contexts upon which they depend. The pragmatics of the proposed approach are demonstrated using two real-world case studies.

APA, Harvard, Vancouver, ISO, and other styles

27

Gorschek, Tony. "Requirements engineering supporting technical product management /." Karlskrona : Blekinge Institute of Technology, 2006. http://www.bth.se/fou/Forskinfo.nsf/allfirst2/8b9d14ce365694b1c125714d0045ea0f?OpenDocument.

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

Nymark, Maria, and Joelle Zhang. "Balancing HMI Design and Requirements Engineering." Thesis, KTH, Maskinkonstruktion (Inst.), 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-49695.

Full text

Abstract:

En lyckad kravhanteringsprocess är A och O för en lyckad produktutveckling. Kravhantering består av aktiviteter som ska se till att det som utvecklas verkligen stämmer överrens med kunders krav och förväntningar. Kravhanteringsprocessen behöver ständigt ses över, för knappt en sjättedel av alla innovationer erbjudna av biltillverkare och leverantörer köps av kunder, och hela 40 procent av bilindustrins R&D utgifter går till projekt som misslyckas att uppfylla kunders önskemål (Oliver Wyman, 2007).Syftet med detta examensarbete är att analysera hur kravhantering balanserar utvecklingsprocessen för Human-Machine Interface (HMI) design på ett företag aktivt i transportindustrin. I denna rapport ska resultat, slutsatser och förslag på hur förbättringar skulle kunna ske presenteras.Vår analys baseras på litteraturforskning, externa intervjuer samt interna intervjuer med utvecklare och direktörer på studerat företag.Som resultatet av detta arbete presenteras iakttagelser på studerat företag och relevant forskning skriven i litteratur. Analysen från intervjuerna avslöjade tre utmaningar för företaget: (1) otillräcklig kvalitet på krav, (2) svårigheter i att finna alla dokumenterade krav som rör HMI design, och (3) indata i lösningar missas. Om detta inte tas itu med kan det resultera i ökade utvecklingskostnader för företaget och att slutgiltig HMI design innehåller brister. Som ytterligare resultat presenterar vi även två lösningsförslag. Det första är en kartläggningsansats för att förbättra samarbetet mellan utvecklingsteam för HMI design. Den andra syftar till att skapa en mekanism så att information sprids inom företaget.Vi anser att resultatet av detta examensarbete är en bra grund för framtida arbete. Syftet med de två lösningsförslagen är att skapa ett mer dynamiskt och balanserat samarbete mellan utvecklingsteam. Med effektiv kommunikation i detta tvärvetenskapliga utvecklande så finns stor potential för att skapa en lyckad och kunduppskattad HMI produkt.
Practising Requirements Engineering is vital for R&D companies since it addresses activities needed to create the right customer- and organization oriented requirements and the follow up of these requirements. Constant improvement of Requirements Engineering is important as barely one sixth of all innovations offered by auto manufacturers are actually bought by the customers and close to 40 percent of R&D expenses in the automotive industry go to projects that fail because of weak customer acceptance (Oliver Wyman, 2007).Therefore, the purpose of this thesis is to analyse how Requirements Engineering is balancing the Human Machine Interface design process. The objective is to present findings, conclusions and improvement proposals.The analysis is based on literature research, external interviews, and interviews and workshops with design teams and managers at studied company.As a result of this master thesis we present findings from studied company and from literature. Our interview analysis revealed three challenges that the studied company are facing; (1) inadequate quality of requirements, (2) difficulty to find all documented requirements regarding HMI, (3) missing input. Not addressing these challenges can result in increased development costs for the company, and inadequate HMI design solutions and HMI product. Furthermore, we present two improvement proposals that address presented challenges and their root causes. The first proposal is a mapping approach to create effective collaboration between development teams for HMI design, and the second proposal is to create a mechanism for information communication.We believe that the results presented in this master thesis report are a good foundation for future work. The purposes of the two presented improvement proposals are to create a more dynamic and balanced collaboration between teams. With effective communication for interdisciplinary development, the HMI product will achieve a high customer value and customer satisfaction.

APA, Harvard, Vancouver, ISO, and other styles

29

Ketabchi, Shokoofeh. "Patterns of semiosis in requirements engineering." Thesis, University of Reading, 2011. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.558764.

Full text

Abstract:

Requirements engineering (RE) is a process of eliciting, analysing, specifying and validating requirements. It is carried out early in the development lifecycle and acts as the basis for other phases in the software development lifecycle. Therefore, proper requirements engineering improves the quality of the development cycle and, thus, the final product. Many methods and frameworks have been developed for RE. They introduce step-by-step guidelines and methods that need prior knowledge and experience to be applied properly; these are not suitable for novice analysts. Applying requirements patterns is a technique to overcome this problem. A pattern is a regularity that repeats again and again. Requirements may repeat in projects; thus, they can be defined as patterns and reused whenever needed instead of developing them from scratch. Several methods have been introduced for developing and reusing patterns; however, they are mainly concerned with technology and implementation aspects, and usually ignore users' high-level informal requirements. This research aims to develop the theory of semiosis patterns and to introduce a requirements engineering patterns method that solves mentioned problems. The proposed theory and method are mainly inspired by the semiosis process from semiotics theory. The semiosis process helps to make a connection from signs to their objects through an interpretant. The semiosis pattern theory introduces new concepts and principles for patterns in requirements engineering. The semiosis patterns method helps to create, reuse, and customise pattern for requirements engineering. To develop the semiosis patterns, a problem domain is decomposed into smaller sections (sub- domains) called problem patterns for which related requirements patterns are created, or reused, if currently exist in the repository, when the semiosis process is used to match problem patterns (regarded as signs) with requirements patterns (regarded as objects). To validate the proposed method, the information management area is chosen to carry out an extensive study and develop its patterns accordingly. Then, two case studies from the Oil and Gas industry are selected and their information management (IM) function is studied, and the developed patterns are reused and customised. Finally, the whole research including the theoretical foundation, methodology, SPM and the result of the application of SPM are critically evaluated.

APA, Harvard, Vancouver, ISO, and other styles

30

Page, Christopher J., and Jean D. Reese. "Networking requirements analysis for Engineering 2000." Thesis, Monterey, California. Naval Postgraduate School, 1996. http://hdl.handle.net/10945/8731.

Full text

Abstract:

Approved for public release; distribution is unlimited
The Cruise Weapons community wants to evaluate its baseline network and define the characteristics of its Engineering 2000 target network. In this thesis, we develop and execute a methodology for completing these actions. By following this methodology, we compare the community's current requirements with its current capabilities to produce our baseline evaluation. Then, we predict the future requirements and capabilities. From this, we produce our target definition. In our baseline evaluation, we find that the current network does not provide sufficient reach, range, responsiveness, user support, or workgroup support. In addition, we find that it is too complex to maintain or manage effectively. In our target definition, we determine that the future network should be a simple, centrally managed and maintained system that supports all users, including afloat customers and mobile employees. Furthermore, we determine that the network should handle simple messages, multi-version documents, and engineering drawings. In order to provide these capabilities, we recommend that the community streamline its applications suite, discard unnecessary computing assets, produce formal maintenance and management policies, and establish a network operations center. In addition, we recommend that the community implement peer-to-peer networking systems within workgroups, take advantage upgrading LAN technology at the local level, and continue working with DoD service providers for wide area communications

APA, Harvard, Vancouver, ISO, and other styles

31

Siegemund, Katja. "Contributions To Ontology-Driven Requirements Engineering." Doctoral thesis, Saechsische Landesbibliothek- Staats- und Universitaetsbibliothek Dresden, 2015. http://nbn-resolving.de/urn:nbn:de:bsz:14-qucosa-162704.

Full text

Abstract:

Today, it is well known that missing, incomplete or inconsistent requirements lead to faulty software designs, implementations and tests resulting in software of improper quality or safety risks. Thus, an improved Requirements Engineering contributes to safer and better-quality software, reduces the risk of overrun time and budgets and, most of all, decreases or even eliminates the risk for project failures. One significant problem requirements engineers have to cope with, are inconsistencies in the Software Requirements Specification. Such inconsistencies result from the acquisition, specification, and evolution of goals and requirements from multiple stakeholders and sources. In order to regain consistency, requirements information are removed from the specification which often leads to incompleteness. Due to this causal relationship between consistency, completeness and correctness, we can formally improve the correctness of requirements knowledge by increasing its completeness and consistency. Furthermore, the poor quality of individual requirements is a primary reason why so many projects continue to fail and needs to be considered in order to improve the Software Requirements Specification. These flaws in the Software Requirements Specification are hard to identify by current methods and thus, usually remain unrecognised. While the validation of requirements ensures that they are correct, complete, consistent and meet the customer and user intents, the requirements engineer is hardly supported by automated validation methods. In this thesis, a novel approach to automated validation and measurement of requirements knowledge is presented, which automatically identifies incomplete or inconsistent requirements and quality flaws. Furthermore, the requirements engineer is guided by providing knowledge specific suggestions on how to resolve them. For this purpose, a requirements metamodel, the Requirements Ontology, has been developed that provides the basis for the validation and measurement support. This requirements ontology is suited for Goal-oriented Requirements Engineering and allows for the conceptualisation of requirements knowledge, facilitated by ontologies. It provides a huge set of predefined requirements metadata, requirements artefacts and various relations among them. Thus, the Requirements Ontology enables the documentation of structured, reusable, unambiguous, traceable, complete and consistent requirements as demanded by the IEEE specification for Software Requirement Specifications. We demonstrate our approach with a prototypic implementation called OntoReq. OntoReq allows for the specification of requirements knowledge while keeping the ontology invisible to the requirements engineer and enables the validation of the knowledge captured within. The validation approach presented in this thesis is capable of being applied to any domain ontology. Therefore, we formulate various guidelines and use a continuous example to demonstrate the transfer to the domain of medical drugs. The Requirements Ontology as well as OntoReq have been evaluated by different methods. The Requirements Ontology has been shown to be capable for capturing requirements knowledge of a real Software Requirements Specification and OntoReq feasible to be used by a requirements engineering tool to highlight inconsistencies, incompleteness and quality flaws during real time requirements modelling.

APA, Harvard, Vancouver, ISO, and other styles

32

Unterkalmsteiner, Michael. "Coordinating requirements engineering and software testing." Doctoral thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-663.

Full text

Abstract:

The development of large, software-intensive systems is a complex undertaking that is generally tackled by a divide and conquer strategy. Organizations face thereby the challenge of coordinating the resources which enable the individual aspects of software development, commonly solved by adopting a particular process model. The alignment between requirements engineering (RE) and software testing (ST) activities is of particular interest as those two aspects are intrinsically connected: requirements are an expression of user/customer needs while testing increases the likelihood that those needs are actually satisfied. The work in this thesis is driven by empirical problem identification, analysis and solution development towards two main objectives. The first is to develop an understanding of RE and ST alignment challenges and characteristics. Building this foundation is a necessary step that facilitates the second objective, the development of solutions relevant and scalable to industry practice that improve REST alignment. The research methods employed to work towards these objectives are primarily empirical. Case study research is used to elicit data from practitioners while technical action research and field experiments are conducted to validate the developed solutions in practice. This thesis contains four main contributions: (1) An in-depth study on REST alignment challenges and practices encountered in industry. (2) A conceptual framework in the form of a taxonomy providing constructs that further our understanding of REST alignment. The taxonomy is operationalized in an assessment framework, REST-bench (3), that was designed to be lightweight and can be applied as a postmortem in closing development projects. (4) An extensive investigation into the potential of information retrieval techniques to improve test coverage, a common REST alignment challenge, resulting in a solution prototype, risk-based testing supported by topic models (RiTTM). REST-bench has been validated in five cases and has shown to be efficient and effective in identifying improvement opportunities in the coordination of RE and ST. Most of the concepts operationalized from the REST taxonomy were found to be useful, validating the conceptual framework. RiTTM, on the other hand, was validated in a single case experiment where it has shown great potential, in particular by identifying test cases that were originally overlooked by expert test engineers, improving effectively test coverage.

APA, Harvard, Vancouver, ISO, and other styles

33

Grützner, Ines, Patrick Waterson, Carsten Vollmers, Sonja Trapp, and Thomas Olsson. "Requirements Engineering für Communities of Practice." Saechsische Landesbibliothek- Staats- und Universitaetsbibliothek Dresden, 2014. http://nbn-resolving.de/urn:nbn:de:bsz:14-qucosa-155494.

Full text

Abstract:

Eine der Herausforderungen des Requirements Engineering (RE) ist, dass bei der Entwicklung eines Software-Systems sowohl die technischen Einzelheiten als auch der Kontext des Einsatzes berücksichtigt werden müssen. Wie schon andere Autoren bemerkt haben, ist RE ein sozio-technisches Unterfangen. Bei der Entwicklung von Desktop-Software zum Beispiel ist zu berücksichtigen, wie der einzelne Benutzer die Anwendung einsetzen wird. Im Bereich Computer Supported Cooperative Work (CSCW) ist der Einsatzkontext komplizierter, da Kommunikation und Interaktion zwischen Benutzern ebenfalls berücksichtigt werden müssen. Bei der Entwicklung einer Community of Practice (CoP) muss der Kontext noch weiter ausgedehnt werden, da Dinge wie Kooperation, Gruppenbildung bzw. Bildung von Netzwerken, Lernen etc. auch in die Anforderungen einfließen.

APA, Harvard, Vancouver, ISO, and other styles

34

Matei, Alexandru. "Requirements engineering for electronic healthcare records." Thesis, University College London (University of London), 2018. http://discovery.ucl.ac.uk/10058555/.

Full text

Abstract:

This thesis investigates requirements engineering methods based on process modelling for Electronic Healthcare Record (EHR) systems. The relation between software requirements and user workflows is essential in healthcare settings: EHRs are expected to improve clinical and administrative workflows. In turn, the new workflows are expected to satisfy a number of business goals. If a new software system does not support the desired clinical workflows or patient journeys, then its value and benefits are often disputed by stakeholders. Our hypothesis is that requirements engineering methods based on process models will contribute to the overall success of EHR projects in the industry. By success, we mean software systems that are in use and meet the business benefits expected of them. The experiments presented in this thesis are aimed to develop and evaluate a method that allows business analysts to make use of process models during requirements engineering for EHRs. The goal of the method is to ensure the software specification is aligned to and supports the user workflows. Each of the four experiments addresses a specific research objective, and thus the findings from each experiment constitute the basis for one of our four contributions to science. / Experiment 1: Relating Goal Oriented Requirements Engineering and Process Modelling: This experiment investigates the design of a common framework for describing process models and software requirements. It relates the KAOS framework for goal oriented requirements engineering and the Business Process Modelling Notation (BPMN). Our goal is to facilitate requirements elicitation. Specifically, business analysts using our framework should be able to reason about the alignment of the software specification to the business processes, and identify specific changes that improve this alignment (either changes in the design of the system, or changes in the business processes). This first experiment was conducted as part of the WellbeingUCL project, supported by Boots. / Experiment 2: Inferring Goal Models from Process Models: The second experiment investigates a method for business analysts to derive software requirements from process models. The purpose for defining such a method is to provide sufficient guidance to business analysts, during requirements elicitation. Our aim is to help business analysts elicit meaningful goal models and shape the design of the system-to-be, in light of these goals. A number of heuristics to facilitate requirements elicitation are proposed and evaluated, considering the trade-offs between a fully automated and a human driven process. / Experiment 3: Electronic Healthcare Record for Bupa: The third experiment evaluates the requirements engineering method during an EHR implementation for a chronic condition management service delivered by Bupa nurses in South West England. Action research is used to assess the impact and fit of the requirements elicitation process, in relation to the current work practices of business analysts in the industry. The extended KAOS framework and goal inference heuristics have been used to inform the final software specification, guide the workflow redesign and clarify the business benefits. From a project management perspective, this experiment evaluates how the KAOS method aligns with the Agile and Lean methodologies used in Bupa. The project has delivered an EHR system actively used to support the care of 2,600 patients. / Experiment 4: Personal Health Record for Nuffield Health: The fourth experiment evaluates the extended KAOS framework when developing a new digital customer proposition with an underlying EHR system. It investigates how consumer journeys can be modelled as KAOS process models. Of specific interest is the ability of the framework to clarify the responsibility assignments among the different agents (i.e. system components) that need to collaborate to deliver the end to end customer journey. The experiment was run as an action research project, in partnership with Nuffield Health. The results have informed the architecture of an open source personal health record for lifestyle data. / Contributions to science: This thesis advances the field of requirements engineering by introducing and evaluating a requirements elicitation method based on business process models. It also presents new evidence into the use of goal oriented requirements engineering for the design and implementation of EHR systems in the industry. Our four contributions to science directly follow from the results of the four experiments conducted as part of this research. Our first two contributions cover the conceptual framework and our proposed method for requirement elicitation based on process models. Our last two contributions present evidence for the practical use and benefits of our goal oriented requirements engineering method in industry based projects. First, we present an extension of the KAOS requirements engineering framework which includes a business process view with clearly defined syntax and execution semantic. This approach ensures process models and goal models have a shared semantic. A new concept, that of Intentional Fragment, captures the explicit relation between fragments of a process model and a specific goal. We also define additional consistency rules, to clarify how the process view relates with other KAOS models: object, agent and operation model. Secondly, we present a set of goal inference techniques to help analysts build goal models starting from process models. In effect, analysts can start from the artefacts that are most familiar to them (i.e. the workflow models) and gradually derive a goal model for the system-to-be. A set of 12 heuristics have been fully defined and integrated into a semi-structured method for goal elicitation. Our third contribution is an evaluation of how the goal oriented requirements engineering method (incorporating workflow analysis) supports the design and deployment of a EHR system in a clinical setting. The project was representative for the challenges faced by healthcare organisations wishing to deploy EHRs: quality of care standards that impose constraints on process redesign; legacy systems that have shaped the workflow; organisational complexity and competing stakeholder interests. We show that by methodically applying our goal inference techniques we were able to produce a valid goal model starting from models of the nurses workflows. The resulting goal model was used to reason about alternative design options in the system-to-be, and to clarify the benefit case in deploying the EHR system. Fourth, we examine the requirements engineering process for an EHR system meant to support a new customer proposition. This project was representative for the challenges faced in the digital health industry: a target consumer journey driven by user experience research; many different systems required to collaborate; focus on the architectural design of the system. We show that we can apply our goal inference techniques to customer journey maps and produce a meaningful goal model. This has been used to shape the architecture of the EHR system and reason about integration requirements. We also argue that our goal inference techniques complement agile development practices used within the organisation.

APA, Harvard, Vancouver, ISO, and other styles

35

Yassipour, Tehrani Sobhan. "Requirements engineering for model transformation development." Thesis, King's College London (University of London), 2018. https://kclpure.kcl.ac.uk/portal/en/theses/requirements-engineering-for-model-transformation-development(259ad351-0771-415d-8969-af6a805050b5).html.

Full text

Abstract:

Model transformation (MT) is central to model driven engineering. It can be used for a range of purposes, including to improve the quality of models, to refactor models, to migrate or translate models from one representation to another, and to generate code or other artifacts from models. At present, the development of MT is mainly focused on the specication and implementation phases, whereas there is a lack of support in other phases including requirements, analysis, design and testing. In this thesis, we are only interested in the requirements phase of MT development, namely the initial phase of software development life-cycle where the software's specifications are determined, for which at present there is no systematic requirement engineering (RE) process. In this research study, we aim to systematically find out how MT is being developed. We are particularly interested in understanding how requirements for MT are being identified. A comprehensive systematic literature review together with an interview-based study have been applied in order to address these shortcomings. Moreover, this thesis addresses the lack of a guideline for a systematic RE process in MT by defining a systematic procedural RE process framework for MT development and it identifies criteria for selecting the most appropriate RE techniques. This framework is evaluated and validated through its application on two substantial industrial cases. The first case is an example of model driven development applied to MT development. The second is a financial application involving risk evaluation of multiple financial investments.

APA, Harvard, Vancouver, ISO, and other styles

36

Rantanen, E. (Eetu). "Requirements engineering in agile software projects." Bachelor's thesis, University of Oulu, 2017. http://urn.fi/URN:NBN:fi:oulu-201705091721.

Full text

Abstract:

Many software projects are failed due to the delivery decisions that were made without adequate requirements information. In addition, the project management process including agile-oriented requirement management process has been identified as one of the four success factors in the agile software projects. Having the clear rules for requirements engineering is, therefore, an important thing for agile software projects from their success point of view. In this study, the objective is to analyze agile requirements engineering and to find out practices that are used in it. The goal is to define a continuous process to identify customer needs and translate them into software requirements in the agile software development. This goal is going to be achieved by a systematic literature review on the agile requirements engineering. For the agile software development and the traditional requirements engineering, the theory has been gathered from some basic books of the theme. The primary research question for this study is: How the customer needs will be translated into requirements in the agile software project as a continuous process? There are also two secondary research questions: 1. What are the customer needs and how can they be identified? 2. What kind of practices are used in the agile requirements engineering? Generally, the requirements engineering process includes four separate steps. First, the business usefulness of the system should be evaluated (feasibility study). After that, the requirements are discovered (elicitation and analysis)and converted into some standard form (specification). Last phase includes checking that the requirements define the system as customer wants (validation). Agile requirements engineering includes four major practices. The high-level interaction between the development team and the customer, iterative approach for the requirements engineering, prioritizing the requirements based on their business value for the customer, and eliciting also the non-functional requirements. In addition, the documentation of requirements is minimalistic in agile approaches. Results of this study can generally be applied and the model created can be utilized as a guideline when doing requirements engineering in the agile software projects
Monet ohjelmistoprojektit epäonnistuvat, koska tieto vaatimuksista on riittämätöntä toimituspäätöksiä tehdessä. Lisäksi projektinhallinnan prosessi, johon sisältyy ketterä vaatimustenhallinnan prosessi, on tunnistettu yhdeksi neljästä ketterien ohjelmistoprojektien menestystekijästä. Tämän takia ketterien ohjelmistoprojektien onnistumiseksi on tärkeää, että vaatimusmäärittelylle on selkeät ohjeet. Tämän tutkimuksen tarkoituksena on analysoida ketterää vaatimusmäärittelyä ja löytää siinä yleisesti käytettyjä tapoja. Tavoitteena on määrittää jatkuva prosessi, jossa asiakkaan tarpeet tunnistetaan ja käännetään ohjelmiston vaatimuksiksi ketterässä ohjelmistokehityksessä. Tavoitteeseen pyritään tekemällä systemaattinen kirjallisuuskatsaus ketterään vaatimusmäärittelyyn. Ketterää ohjelmistokehitystä sekä perinteistä vaatimusmäärittelyä käsitellään muutaman perusteoksen pohjalta. Tutkimuksen ylätason tutkimuskysymys on: Kuinka asiakkaan tarpeet käännetään vaatimuksiksi jatkuvana prosessina ketterissä ohjelmistoprojekteissa? Lisäksi tutkimuksella on kaksi alatason tutkimuskysymystä: 1. Mitä asiakkaan tarpeet ovat ja kuinka ne tunnistetaan? 2. Minkälaisia tapoja ketterässä vaatimusmäärittelyssä käytetään? Yleinen vaatimusmäärittelyprosessi sisältää neljä vaihetta. Ensin arvioidaan järjestelmän liiketoiminnallinen tarpeellisuus (kannattavuusselvitys). Tämän jälkeen etsitään vaatimuksia (selvitys ja analyysi) ja käännetään ne johonkin standardimuotoon (spesifikaatio). Viimeisessä vaiheessa tarkistetaan, että vaatimukset määrittävät järjestelmän juuri asiakkaan haluamalla tavalla (validointi). Ketterässä vaatimusmäärittelyssä on neljä yleistä käytäntöä. Korkean tason kanssakäyminen asiakkaan ja kehitystiimin välillä, iteratiivinen eli toistava lähestymistapa vaatimusmäärittelyyn, vaatimusten priorisointi perustuen asiakkaalle syntyvään arvoon ja myös ei-funktionaalisten vaatimusten tunnistus. Lisäksi voidaan sanoa, että vaatimusten dokumentointi ketterissä menetelmissä on vähäistä. Tämän tutkimuksen tuloksia voidaan yleisesti ottaen hyödyntää ja kehitettyä mallia voidaan käyttää vaatimusmäärittelyn ohjenuorana ketterissä ohjelmistoprojekteissa

APA, Harvard, Vancouver, ISO, and other styles

37

Ahmed, Kushal. "iRE: An Interactive Requirements Engineering Framework." Thesis, Griffith University, 2016. http://hdl.handle.net/10072/368167.

Full text

Abstract:

Requirements Engineering (RE) involves processing informal natural language de-scriptions of the system requirements into an integrated and structured formal specification. Current and future software intensive systems must accommodate increasingly larger sets of requirements. Therefore, in large-scale new systems engi- neering projects, the requirements analyst (RA) may end up with many thousands, sometimes tens or even hundreds of thousands, of requirements. Dealing with these large volume of requirements is extremely challenging for several reasons: 1. The system requirements may be unstructured and loosely distributed. 2. They may be ill-defined, incomplete, or redundantly specified. 3. They may change at any time, having ripple effects on others. As a result, the RE process becomes very difficult to manage for a large-scale software intensive system, even if it is somewhat manageable for a small-scale one. In order to streamline the RE process, we present an interactive requirements engineering (iRE) framework. The iRE framework provides automated supports for (1) defects detection and resolution, (2) change management and (3) derivation of integrated and structured system model. Since domain knowledge is necessary in different scenarios, the framework involves the RA in an interactive fashion.
Thesis (PhD Doctorate)
Doctor of Philosophy (PhD)
Institute for Integrated and Intelligent Systems
Science, Environment, Engineering and Technology
Full Text

APA, Harvard, Vancouver, ISO, and other styles

38

Bhoomgoud, Uday, and Kiran P. "An Empirical Study On Requirements Engineering Core Practices." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2005. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3461.

Full text

Abstract:

Requirements engineering (RE) is the primary task (process) that is done when agreed upon to develop a software product. The success of the software product is gauged on its ability to meet the intended needs of the stakeholders. There is abundant literature emphasizing the significance of RE and its influence on the entire software project, apart from its importance as the first step for a successful development endeavor. There are several established methodologies that are acknowledged to support the RE process and assist in creating a reliable structure of creating software. Despite the availability of such techniques and solutions, it was observed that umpteen number of software product failures are attributed to unsatisfactory RE practices. In this thesis, we have conducted a study with six organizations to emphasize the gap between the state of the art and the state of the practice, and consequently identify the factors that hinder the industrial community to implement state of the art RE. As a result of this empirical research we have found that to a great extent, state of the art practices are unpopular, more specifically in small organizations. Interestingly the majority of the problems associated with RE are associated to non technical issues.

APA, Harvard, Vancouver, ISO, and other styles

39

Soundararajan, Shvetha. "Agile Requirements Generation Model: A Soft-structured Approach to Agile Requirements Engineering." Thesis, Virginia Tech, 2008. http://hdl.handle.net/10919/34511.

Full text

Abstract:

The agile principles applied to software engineering include iterative and incremental development, frequent releases of software, direct stakeholder involvement, minimal documentation and welcome changing requirements even late in the development cycle. The Agile Requirements Engineering applies the above mentioned principles to the Requirements Engineering process. Agile Requirements Engineering welcomes changing requirements even late in the development cycle. This is achieved by using the agile practice of evolutionary requirements which suggests that requirements should evolve over the course of many iterations rather than being gathered and specified upfront. Hence, changes to requirements even late in the development cycle can be accommodated easily. There is however, no real process to the agile approach to Requirements Engineering. In order to overcome this disadvantage, we propose to adapt the Requirements Generation Model (a plan-driven Requirements Engineering model) to an agile environment in order to structure the Agile Requirements Engineering process. The hybrid model named the Agile Requirements Generation Model is a soft-structured process that supports the intents of the agile approach. This model combines the best features of the Requirements Generation Model and Agile Software Development.
Master of Science

APA, Harvard, Vancouver, ISO, and other styles

40

Ponugubati, Dhana Lakshmi, and Vineesha Vallem. "Requirements Engineering For Distraction-Free Software : Systematic Literature Review and Survey." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-20643.

Full text

Abstract:

Context and Motivation: Technology play a vital role in the people’s present life. These technology has different types of softwares and devices. Now a days people mostly live around the digital devices and involve with them. These softwares when using causes digital distraction. Mostly digital distraction occurs only when using digital devices. For the development of software and devices requirements play a major role in the development in an organization. Question/Problem: The requirements are developed into the features of software. These features when using can cause distraction. So to manage these digital distraction causing by the software, we considered requirements engineering, by introducing the requirements engineering process at the beginning of the development of software, so to develop a distraction-free software. This can be helpful for the developers to develop the distraction-free software from early stages for the user. Principal Ideas/Objectives: Our thesis mainly focus on the identification of quality factors requirements contributing to the digital distraction and analyse them and we also tried to identify feature usage and user experience of software to identify distraction of software and a mind-map is designed for the study of digital distraction. So that these can provide useful information for future studies. Methods/Contributions: In our thesis study, we conducted Systematic Literature Review using snowballing process for the identification of the literature about the digital distraction and analysed the SLR. Further an online survey is conducted on Instagram users to extract distraction features and reasons for distraction and then we used this data to plan a mind-map of different categories contributing to digital distraction. Results: The main findings and observations in our research are observed through SLR and survey results. For research question 1, the data that is extracted through SLR gives quality factor requirements that contribute to the digital distraction. An understanding of digital distraction among software and feature and also the causes are observed. For the research question 2, the data from the survey is collected from the users of Instagram are observed. The results from the survey are extracted to know about the distraction of software using the feature usage which is extracted from the survey and also the user experience. From these results of SLR and survey data, a mind map is designed to know about the study of the digital distraction. Conclusions: Finally, we come up with a idea by planning mind-map that helps the software developers and requirement engineers to build a distraction-free software. The results of this study can be helpful to all the software developers and also to the ones who want to carry our the research on requirements connection with digital distraction, this can be a start point for them.

APA, Harvard, Vancouver, ISO, and other styles

41

Harron, Thomas W. "Requirements compiler /." Connect to unofficial online version of: Requirements compiler, 2006. http://minds.wisconsin.edu/bitstream/1793/18753/1/HarronTom.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Dahlberg, Kristian. "Marknadsinriktad Requirements Engineering : kännetecken och centrala aktiviteter." Thesis, University of Skövde, Department of Computer Science, 2001. http://urn.kb.se/resolve?urn=urn:nbn:se:his:diva-522.

Full text

Abstract:

Denna rapport behandlar den marknadsinriktade Requirements Engineering (RE) processen. Allt fler företag väljer idag att implementera standardsystem i sina verksamheter. Den situation som ett standardsystem utvecklas i är annorlunda jämfört med den som ett kundspecifikt system utvecklas i. Detta innebär att den traditionella RE-processen inte är anpassad till dessa nya förhållanden.

Syftet med denna rapport är därför att utreda vad som kännetecknar en marknadsinriktad RE-process som stödjer kravhanteringsarbetet vid utvecklingen av ett standardsystem. Rapporten avser även att undersöka hur RE tillämpas av marknadsinriktade systemtillverkare i praktiken. Detta har gjorts genom en litteraturstudie och intervjuer med tre marknadsinriktade systemtillverkare.

Rapporten resulterar i en beskrivning av den marknadsinriktade RE-processens kännetecken och centrala aktiviteter samt en översiktlig sammanställning över hur marknadsinriktade systemtillverkare tillämpar RE i praktiken. Resultatet belyser att de teorier och aktiviteter som betraktas som centrala i den marknadsinriktade RE-processen även tillämpas i praktiken.

APA, Harvard, Vancouver, ISO, and other styles

43

Gomes, Andrigo, and Andreas Pettersson. "Market-Driven Requirements Engineering Process Model – MDREPM." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2007. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3533.

Full text

Abstract:

Research findings in requirements engineering (RE) report that software organizations still struggle in establishing processes that lead to proper requirements handling. This leads to the acknowledgement that the adoption of good requirements engineering practices by industry is still not common. Although some initiatives have been made to spread the use of good practices of bespoke RE, the area of market-driven requirements engineering (MDRE) still lacks a contribution in that direction. MDRE is characterized by strong market and strategic orientation, which contrasts with the customer/development organization relationship of bespoke RE. This poses several challenges to software product organizations, such as the need for aligning development activities with organizational and product strategies. In an attempt to help these organizations to realize the benefits of MDRE, this Master Thesis presents the Market-Driven Requirements Engineering Process Model (MDREPM). MDREPM is both a collection of good practices in MDRE, and an assessment tool for organizations to get a snapshot of the current state of their MDRE practices. The assessment intends to reveal problem areas of organization’s requirements process, which can then be worked upon by introducing good practices described in the model. The thesis describes the motivation for creating MDREPM, both from an academia and industry perspectives. In addition, it describes the process of developing the model, from its creation through to its validation within academia and industry. As the series of three case studies conducted indicate, the MDREPM has been shown to be useful for industry practitioners. A unanimous opinion has been found as to the good coverage it provides of issues related to MDRE, and as to its usefulness for driving improvement efforts in requirements engineering.

APA, Harvard, Vancouver, ISO, and other styles

44

Korziuk, Kamil, and Tomasz Podbielski. "Engineering Requirements for platform, integrating health data." Thesis, Blekinge Tekniska Högskola, Institutionen för tillämpad signalbehandling, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-16089.

Full text

Abstract:

In the world that we already live people are more and more on the run and population ageing significantly raise, new technologies are trying to bring best they can to meet humans’ expectations. Survey’s results, that was done during technology conference with elderly on Blekinge Institute of Technology showed, that no one of them has any kind of help in their home but they would need it. This Master thesis present human health state monitoring to focus on fall detection. Health care systems will not completely stop cases when humans are falling down, but further studying causes can prevent them.In this thesis, integration of sensors for vital parameters measurements, human position and measured data evaluation are presented. This thesis is based on specific technologies compatible with Arduino Uno and Arduino Mega microcontrollers, measure sensors and data exchange between data base, MATLAB/Simulink and web page. Sensors integrated in one common system bring possibility to examine the patient health state and call aid assistance in case of health decline or serious injury risk.System efficiency was based on many series of measurement. First phase a comparison between different filter was carried out to choose one with best performance. Kalman filtering and trim parameter for accelerometer was used to gain satisfying results and the final human fall detection algorithm. Acquired measurement and data evaluation showed that Kalmar filtering allow to reach high performance and give the most reliable results. In the second phase sensor placement was tested. Collected data showed that human fall detection is correctly recognized by system with high accuracy. Designed system as a result allow to measure human health and vital state like: temperature, heartbeat, position and activity. Additionally, system gives online overview possibility with actual health state, historical data and IP camera preview when alarm was raised after bad health condition.

APA, Harvard, Vancouver, ISO, and other styles

45

BLEISTEIN, Steven, Karl COX, Haruhiko KAIYA, and Shuichiro YAMAMOTO. "Goal Oriented Requirements Engineering: Trends and Issues." Institute of Electronics, Information and Communication Engineers, 2006. http://hdl.handle.net/2237/15023.

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

Djouab, Rachida. "Software product quality requirements engineering method : SOQUAREM." Mémoire, École de technologie supérieure, 2012. http://espace.etsmtl.ca/1092/1/DJOUAB_Rachida.pdf.

Full text

Abstract:

L'industrie des TI a besoin de données fiables sur les exigences de qualité pour évaluer adéquatement les systèmes et leur architecture. La gestion des exigences de qualité du produit logiciel est une discipline qui vient d’émerger pour améliorer la qualité du produit en adressant ses exigences de qualité. Cette tâche n’est pas facile et exige de grands efforts des praticiens, une meilleure implication des parties prenantes ainsi qu’une solide connaissance des techniques de gestion des exigences de qualité. De plus ce type d’exigences est difficile à définir et de nature conflictuelle. De nouvelles approches de gestion de qualité ont été développées pour palier aux limitations des approches traditionnelles d’ingénierie des exigences comme : a) l’absence de conseils systématiques sur la façon de définir les exigences de qualité; b) la difficulté d’identifier les exigences de qualité et de les représenter dans des modèles et processus et c) l’absence de techniques de gestion des exigences de qualité. Cette thèse définit une nouvelle méthode d’ingénierie des exigences de qualité nommée SOQUAREM, basée sur le standard de qualité ISO/IEC SQuaRE 25030. La méthode propose un processus structuré, supporté par des techniques et concepts de traitement de ces exigences. Le processus de SOQUAREM couvre 2 niveaux d'abstraction (Affaires et système) et six étapes conceptuelles telles que: l'identification et spécification des objectifs d’affaire, la dérivation des attributs de qualité, leur analyse et consolidation et finalement leur intégration dans le processus fonctionnel. Le processus SOQUAREM propose la combinaison de plusieurs concepts de différents niveaux organisationnels pour identifier, représenter et retracer les attributs de qualité. Ce document est divisé en 6 chapitres. Le premier chapitre présente l’état de l’art sur les « Exigences de qualité » en général et sur les différentes approches de leur traitement telles que “MOQARE” (Misuse-Oriented QuAlity Requirements Engineering), “IESE NFR" (Institute for Experimental Software Engineering Non Functional Requirements), "Soft Goal Notation" (Chung Framework), "FDAF” (Formal Design and Analysis Framework) et "ATAM" (Architecture Tradeoff Analysis Method). Le deuxième chapitre introduit la problématique de la recherche, ses objectifs, limites et sa méthodologie. Le troisième chapitre décrit le déroulement de la recherche pour justifier la solution de recherche proposée. Il commence par une analyse de la situation actuelle des exigences de qualité dans les milieux académiques et industriels pour en ressortir les principaux indicateurs. Il termine par une description des aspects innovateurs de la nouvelle méthode proposée concrétisés en ses caractéristiques spécifiques, méta modèle, processus de sa conception et la structure de son processus. Le quatrième chapitre décrit la nouvelle méthode d’ingénierie des exigences de qualité (SOQUAREM) incluant ses fondements, concepts clés et son modèle de processus. Le cinquième chapitre présente un exemple détaillé appliqué à un système automatisé de contrôle des bâtiments appelé MSLite. L’applicabilité de SOQUAREM est illustrée dans cet exemple et ensuite analysée. Le dernier chapitre présente une conclusion sur le travail de recherche et son éventuelle évolution.

APA, Harvard, Vancouver, ISO, and other styles

47

Champion, R. E. M. "Modelling for requirements engineering using conceptual structures." Thesis, University of Manchester, 1991. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.334615.

Full text

APA, Harvard, Vancouver, ISO, and other styles

48

Piveropoulos, Marios. "Requirements engineering for hard real-time systems." Thesis, University of York, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.310980.

Full text

APA, Harvard, Vancouver, ISO, and other styles

49

Shahri, Alimohammad. "Engineering motivation requirements in business information systems." Thesis, Bournemouth University, 2017. http://eprints.bournemouth.ac.uk/29960/.

Full text

Abstract:

Digital Motivation refers to the use of software-based solutions to change, boost or maintain people’s attitude and behaviour towards certain tasks, policies and regulations. Gamification, persuasive technology, and entertainment computing are example strands of such paradigm. Digital Motivation exhibits unique properties which necessitate reconsidering its design methods. This stems from the intense human factor which may make it destructive, pressuring, and a reason for negative work ethics. The emerging literature on the topic includes engineering approaches for Digital Motivation. However, their main focus is on specifying its operation, e.g., the design of rewards and levels. This thesis conducts a series of empirical studies and proposes a novel modelling framework which enables capturing Digital Motivation as an integral part of the organisational and social structure of a business. This modelling framework provides a tool which utilises the generated models to perform analysis that informs the design, introduction, and management of Digital Motivation. The modelling and analysis framework is evaluated via case studies involving novice software system analysts, expert software system analysts, and managers of a business information system. The results of the evaluation illustrate that the modelling language has a good capability to elicit and analyse motivation requirements of stakeholders of a business information system.

APA, Harvard, Vancouver, ISO, and other styles

50

Hansen, Sean William. "A Socio-Technical Perspective on Requirements Engineering." Case Western Reserve University School of Graduate Studies / OhioLINK, 2010. http://rave.ohiolink.edu/etdc/view?acc_num=case1291749802.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Dissertations / Theses on the topic 'Requirements engineering'

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