To see the other types of publications on this topic, follow the link: Requirement engineering.
Dissertations / Theses on the topic 'Requirement engineering'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 dissertations / theses for your research on the topic 'Requirement engineering.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.
1
Louis, Harriet. "Towards agile requirement engineering." Thesis, Stellenbosch : Stellenbosch University, 2015. http://hdl.handle.net/10019.1/97337.
Full textAbstract:
Thesis (MBA)--Stellenbosch University, 2015.ENGLISH ABSTRACT: Software development is a relatively young science and involves certain tools, techniques, documentation aids and processes that are applied to deliver a software project. As hardware, software and business needs advanced, so did the processes used in managing software development. It is a dynamic and complex process and each development environment or project has its own unique characteristics. For this reason the methodologies followed during the development process is very often debated. Software development teams have a wide array of methodologies to choose from. The development team usually decides what the key success factors are to deliver a software product, and then examines each one within the framework of a list of potential methodologies. This way the team can compare which methodology would best suit their needs. Factors used to evaluate which methodology to follow, includes the size of the project team, rate of expected changes, the primary goal of the project, how requirements will be managed, communication structures that will be followed, the nature of the relationship with the customer, and the organisational culture in the customer organisation. This research report takes a comparative look at Waterfall methods versus Agile methods.
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 textAbstract:
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.
3
Urwin, Esmond. "Knowledge supported requirement engineering framework." Thesis, University of Nottingham, 2003. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.408633.
Full text
4
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 textAbstract:
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.
5
Darlington, Mansur. "Cognition and the engineering design requirement." Thesis, University of Bath, 2002. https://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.250822.
Full textAbstract:
This thesis is concerned with the engineering design requirement and the process by which it is elicited, evolved and recorded. The purpose of the research reported in the work is to achieve a more complete understanding of the engineering design requirement, and to apply that understanding to the better support of designers during the design requirement capture phases of the design process. Two perspectives dominate the approach to the research. The first concerns the relation between the design process and human cognition. The research subject is seen as being fundamentally a product of the human mind and that such things as knowledge, language and meaning – the things commonly associated with cognition – are crucial to its proper understanding. The second perspective is informed by the view that the development of the design requirement can be seen as a knowledge-intensive process of communication. Thus, understanding communication between humans and some aspects of communication failure can assist in understanding and remedying failure in design requirement capture.
6
Hussain, Dostdar, and Muhammad Ismail. "Requirement Engineering : A comparision between Traditional requirement elicitation techniqes with user story." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-70174.
Full textAbstract:
Requirements are features or attributes which we discover at the initial stage of building a product. Requirements describe the system functionality that satisfies customer needs. An incomplete and inconsistent requirement of the project leads to exceeding cost or devastating the project. So there should be a process for obtaining sufficient, accurate and refining requirements such a process is known as requirement elicitation. Software requirement elicitation process is regarded as one of the most important parts of software development. During this stage it is decided precisely what should be built. There are many requirements elicitation techniques however selecting the appropriate technique according to the nature of the project is important for the successful development of the project. Traditional software development and agile approaches to requirements elicitation are suitable in their own context. With agile approaches a high-level, low formal form of requirement specification is produced and the team is fully prepared to respond unavoidable changes in these requirements. On the other hand in traditional approach project could be done more satisfactory with a plan driven well documented specification. Agile processes introduced their most broadly applicable technique with user stories to express the requirements of the project. A user story is a simple and short written description of desired functionality from the perspective of user or owner. User stories play an effective role on all time constrained projects and a good way to introducing a bit of agility to the projects. Personas can be used to fill the gap of user stories.
7
Grahn, Andreas. "Requirement engineering in programs that generates applications." Thesis, University West, Department of Informatics and Mathematics, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:hv:diva-587.
Full text
8
Roy, Jean-Francois. "Requirement engineering with URN: Integrating goals and scenarios." Thesis, University of Ottawa (Canada), 2007. http://hdl.handle.net/10393/27912.
Full textAbstract:
The User Requirements Notation (URN) is an emerging standard that combines two views: the Goal-oriented Requirement Language (GRL) and the Use Case Map (UCM) notation. This standard intends to combine goals and scenarios for expressing and reasoning about functional and non-functional requirements. Although tools exist in isolation for both views, they are currently not meant to work together, hence hindering the development and adoption of URN. This thesis presents Eclipse-based tool support for integrated goal and scenario modelling based on URN. A metamodel that integrates GRL with an existing UCM metamodel is given, together with a detailed description of the tool capabilities. New and automated analysis approaches are also introduced, which exploit integrated URN models. The approaches that are described include quantitative goal evaluations, stakeholder evaluations, novel GRL strategies, and links between the URN views. In addition, this thesis presents an approach to link GRL models to external requirements, also supported by our tool. Finally, the integrated URN approach is illustrated and validated using case studies.
9
Zhu, Anlin. "Railway Infrastructure Management - System Engineering and Requirement Management." Thesis, KTH, Spårfordon, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-228192.
Full textAbstract:
Rail Control Solutions (RCS) is one division of Bombardier Transportation, aimed at optimising flow of trains. OPTIFLO is a new solution package within RCS, providing services and solutions to address challenges in modern railway infrastructures worldwide. Infrastructure Management (IM) Service is a significant sub-module under OPTIFLO, performing monitoring and diagnostic functionalities for each impacted system or component in railway signalling systems to continuously improve safety, reliability and availability. Requirement management is a significant stage while dealing with engineering problems. In this master thesis project, three modules in railway signalling scope are focused, including system level Infrastructure Management, sub-system level Maintenance and Diagnostic Centre (MDC) and sub-system level Remote Sensor Unit (RSU). For each part, requirement managements have been implemented, referring to CENELEC standards where necessary. The work starts with the draft Requirement Specification for IM and then identify the requirements related to diagnostics and performance in each sub-system. Both links between the requirements in different modules and links between the requirements and their test cases are built from the requirement management tool DOORS to realize verification and validation following the system engineering process. Finally, the standard documentations "System Requirement Specification" for each impacted module that are mostly concerned in the thesis have been released.Rail Control Solutions (RCS) är en del av Bombardier Transportation, som syftar till att optimera flödet av tåg. OPTIFLO är ett nytt programspaket inom RCS, som erbjuder tjänster och lösningar för att hantera utmaningar inom modern järnvägsinfrastruktur världen över. Infrastrucutre Management (IM) Service är en viktig delmodul under OPTIFLO, som utför övervakning och diagnostiska funktioner för varje påverkat system eller komponent i järnvägssignalsystem för att kontinuerligt förbättra säkerhet, tillförlitlighet och tillgänglighet. Kravhantering är ett viktigt steg när man arbetar med tekniska problem. Det här mastersprojektet är inriktat på tre moduler inom järnvägssignalområdet: systemnivå Infrastructure Management, underhållssystem för Maintenance and Diagnostic Centre (MDC) och delsystemnivå Remote Sensor Unit (RSU). För varje del har kravhantering implementerats, med hänvisning till CENELEC-standarder vid behov. Arbetet har utgått från utkast till kravspecifikation för IM och identifierat kraven för diagnostik och prestanda i varje delsystem. Både kopplingar mellan kraven i olika moduler och kopplingar mellan kraven och deras testfall är byggda i systemet DOORS för att realisera verifiering och validering i en systemteknisk process. Slutligen släpps standarddokumentationen "Systemkrav Specifikation" för de moduler som behandlar i detta arbete.
10
Mahmood, Farrukh, and Waqas Rasheed. "Quality Requirement Abstraction Model (QRAM)." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3397.
Full textAbstract:
Requirement engineering (RE) is an important phase in any project. Both functional and non-functional requirements are required to be elicited. Quality requirements (QRs) are usually catered at the end of software development process. Along with functional requirements, non-functional (QRs) also need to be handled and implemented through a structural way. It is observed that most organizations do not have proper management for quality requirements in their project life cycles. Especially if we consider the case of market driven requirement engineering (MDRE), it is a dire need to handle those QRs along with the functional requirement using a structural way. In this study we investigate Requirements Abstraction Model (RAM), which is basically designed for MDRE and is the case of continuous RE. The purpose was to analyze RAM specifications, which could be able to provide an effective way of manage QRs. RAM also deals with the specification of QRs, so it was required to investigate that how effective RAM can handle the creation of QRs.
11
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 textAbstract:
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 industryTiivistelmä 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
12
Rashdan, Adam. "Requirement prioritization in Software Engineering : A Systematic Literature Review on Techniques and Methods." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-105747.
Full textAbstract:
The present study provides a systematic overview of the most important software requirement prioritization techniques. Software requirement prioritization is a process in software engineering that precludes the actual development of software application programs and deals with assigning priorities to single requirements to define the order of their implementation. The study aims to help researchers and practitioners in deciding about the right technique since each has its advantages and limitations. Compared to the existing reviews, the current one not only captures the most promising techniques but the more general trends behind them. The study utilizes the review protocol method that aims to answer four research questions about the most popular techniques, their taxonomy, their limitations, and involved processes. The empirical data was collected from six databases for scientific manuscripts and put under scrutiny to identify the most relevant and elaborated papers. The results from 53 selected manuscripts and 106 discovered techniques demonstrate that there is evidence of a gradual shift from purely manual elicitation methods to computed-assisted and/or algorithmic ones.
13
Dreger, Sally Anne. "Matrix remodelling : a requirement for heart valve tissue engineering." Thesis, Imperial College London, 2008. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.510735.
Full text
14
Liskowsky, R., R. Pjater, and H. Steifer. "Gruppenorientiertes Requirement Engineering auf der Basis von Lotus Notes." Josef Eul Verlag GmbH, 1999. https://tud.qucosa.de/id/qucosa%3A29756.
Full textAbstract:
Aus der Zusammenfassung:
'Alle Projektarbeit insbesondere zur Schaffung verteilter Gemeinschaften, die mit neuen multimedialen Informationen arbeiten, beginnt mit einer tiefgründigen Anforderungsanalyse. Wenn diese frühe Phase der Softwareentwicklung ebenso von einem verteilt arbeitendem Team, bestehend aus Auftraggebern, Auftragnehmern, Systemanalytikern, Endnutzern u.a., durchgeführt wird, sprechen wir von einem gruppenorientierten Requirement Engineering. Gegenwärtig liegen für dessen rechentechnische Unterstützung noch keine befriedigenden Lösungen vor.
15
Liskowsky, R., R. Pjater, and H. Steifer. "Gruppenorientiertes Requirement Engineering auf der Basis von Lotus Notes." Saechsische Landesbibliothek- Staats- und Universitaetsbibliothek Dresden, 2016. http://nbn-resolving.de/urn:nbn:de:bsz:14-qucosa-209286.
Full textAbstract:
Aus der Zusammenfassung:
"Alle Projektarbeit insbesondere zur Schaffung verteilter Gemeinschaften, die mit neuen multimedialen Informationen arbeiten, beginnt mit einer tiefgründigen Anforderungsanalyse. Wenn diese frühe Phase der Softwareentwicklung ebenso von einem verteilt arbeitendem Team, bestehend aus Auftraggebern, Auftragnehmern, Systemanalytikern, Endnutzern u.a., durchgeführt wird, sprechen wir von einem gruppenorientierten Requirement Engineering. Gegenwärtig liegen für dessen rechentechnische Unterstützung noch keine befriedigenden Lösungen vor."
16
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 textAbstract:
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.
17
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 textAbstract:
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.
18
Liu, Xia. "A requirement engineering framework for assessing health care information systems." Thesis, University of Ottawa (Canada), 2010. http://hdl.handle.net/10393/28534.
Full textAbstract:
Health care is increasingly being provided by collaborative teams that involve multiple health care providers at multiple locations. To date, most of that collaboration is on an ad-hoc basis via phone calls, faxes, and paper based documentation. However, Internet and wireless technologies provide an opportunity to improve this situation via electronic data sharing. These new technologies make possible new ways of working and collaboration but it can be difficult for health care organizations to understand how to adopt new technologies while still ensuring that their policies and objectives are being met. It is also important to have a systematic approach to validate that e-health processes deliver the performance improvements that are expected. Using a case study of a palliative care patient receiving home care from a team of collaborating healthcare providers and organizations, we introduce a framework for assessing health care information systems based on requirements engineering. Key concerns and objectives were identified and modeled. Business processes which will use the new health care information system are modeled in terms of these concerns and objectives to assess their impact and ensure that electronic data sharing is well regulated and effective. The work in the thesis is design-oriented research to show the utility of our proposed requirement engineering framework compared to existing evaluation approaches for healthcare IT. The approach is evaluated based on a set of criteria drawn from our literature review and a gap analysis of our case study for palliative care.
19
Liaw, Judy-Audrey-Chui-Yik. "DEFINITION AND REPRESENTATION OF REQUIREMENT ENGINEERING / MANAGEMENT: A PROCESS-ORIENTED APPROACH." MSSTATE, 2002. http://sun.library.msstate.edu/ETD-db/theses/available/etd-04092002-095054/.
Full textAbstract:
Requirements are important in software development, product development, projects, processes, and systems. However, a review of the requirements literature indicates several problems. First, there is confusion between the terms ?requirements engineering? and ?requirements management.? Similarities and/or differences between the two terms are resolved through a literature review; resulting in comprehensive definitions of each term. Second, current literature recognizes the importance of requirements but offers few methodologies or solutions for defining and managing requirements. Hence, a flexible methodology or framework is provided for defining and managing requirements. Third, requirements methodologies are represented in various ways, each with their respective strengths and weaknesses. A tabular view and hybrid graphical view for representing the requirements process are provided.
20
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 textAbstract:
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.
21
Ng, Yu Lung Alan 1976. "Requirement analysis for distributed software development." Thesis, Massachusetts Institute of Technology, 2000. http://hdl.handle.net/1721.1/80957.
Full text
22
Hameed, Faysal, and Mohammad Ejaz. "Model for conflict resolution in aspects within Aspect Oriented Requirement engineering." Thesis, Blekinge Tekniska Högskola, Avdelningen för för interaktion och systemdesign, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5292.
Full textAbstract:
Requirement engineering is the most important phase within the software development phases since it is used to extract requirements from the customers which are used by the next phases for designing and implementation of the system. Because of its importance, this thesis focuses on the term aspect oriented requirement engineering, which is the first phase in aspect oriented software development used for the identification and representation of requirements gathered in the form of concerns. Besides the overall explanation of aspect oriented requirement engineering phase, detail attention is given to a specific activity within AORE phase called conflict resolution. Several techniques proposed for conflict resolution between aspects is discussed along with an attempt to give a new idea in the form of an extension of the already proposed model for conflict resolution. The need for extension to the already proposed model is justified by the use of a case study which is applied on both the models i.e. on the original model and on the extended model to compare the results.Krav engineering är den viktigaste fasen inom mjukvaruutveckling faser eftersom det är användas för utvinning av krav från kunder som används av de följande faserna för utformning och genomförandet av systemet. På grund av dess betydelse, denna avhandling fokuserar på sikt aspekt orienterade krav på teknik, som är den första fasen i aspekt Orienten mjukvaran utveckling används för identifiering och representation krav som samlats in i form av oro. Förutom det övergripande förklaring av aspekt oriented Kravet tekniska fasen, detalj uppmärksamhet ges till en specifik verksamhet inom AORE fasen kallas konfliktlösning. Flera metoder som föreslås för konfliktlösning mellan aspekter diskuteras tillsammans med ett försök att ge en ny idé i form av en utvidgning av redan föreslagna modellen för konflikt resolution. Behovet av förlängning av redan föreslagna modellen är motiverad av att använda en fallstudie som appliceras på båda modellerna dvs i den ursprungliga modellen och om den utvidgade modell för att jämföra resultat.
faysal_hameed@hotmail.com, ijazbutt1@hotmail.com
23
ENGIEL, PRISCILA. "EUNOMIA (ΕΥΝΟΜIΑ): A REQUIREMENT ENGINEERING BASED COMPLIANCE FRAMEWORK FOR SOFTWARE SYSTEMS." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2018. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=35871@1.
Full textAbstract:
PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIROCOORDENAÇÃO DE APERFEIÇOAMENTO DO PESSOAL DE ENSINO SUPERIOR
CONSELHO NACIONAL DE DESENVOLVIMENTO CIENTÍFICO E TECNOLÓGICO
PROGRAMA DE EXCELENCIA ACADEMICA
Leis e regulamentos afetam o desenvolvimento de software, já que freqüentemente exigem mudanças nos requisitos de software para proteger indivíduos e empresas em relação à segurança, privacidade, governança, sustentabilidade e muito mais. Requisitos legais podem ditar novos requisitos ou restringir os existentes. O problema da conformidade de software é como garantir que o software esteja em conformidade com as normas impostas pela legislação. O problema é particularmente desafiador porque combina etapas difíceis: 1) analisar documentos legais, 2) extrair requisitos desses documentos, 3) identificar requisitos conflitantes com aqueles já implementados em software e 4) garantir que o software permaneça compatível mesmo com as alterações. A conformidade é um processo contínuo: as leis, o software e o contexto no qual o sistema de software opera mudam continuamente. Os trabalhos que lidam com o problema de conformidade concentram-se apenas em um ou dois assuntos: analisar documentos legais ou extrair requisitos ou identificar conflitos ou mudanças. Esta tese trata de todos os problemas ao mesmo tempo; a ideia é extrair requisitos do texto legal, compará-los com o requisito de software, resolver os possíveis conflitos que possam surgir, lidando continuamente as mudanças no ambiente, leis e requisitos. Para tanto, este trabalho propõe um framework que é composto por um processo de compliance e monitoramento contínuo das mudanças ambientais. O processo de conformidade suporta a identificação, extração, comparação e resolução de conflitos para ajudar na conformidade do software, produzindo um conjunto conforme de requisitos. O processo de conformidade é baseado na anotação semântica e no modelo de meta. A anotação semântica ajuda a extrair requisitos do arquivo, usando padrões. O modelo de meta é usado para ajudar na comparação entre requisitos e representar requisitos em uma especificação de requisitos formal e consistente. O processo é suportado por ferramentas; sendo algumas reutilizadas (Desiree e NomosT) para avançar cada etapa. Foi necessário adaptar as ferramentas para o contexto do processo de conformidade, criando diretrizes, padrões e heurísticas. O monitoramento contínuo está preocupado com as mudanças que afetam a conformidade do software e tem o mecanismo para garantir que, mesmo com essas mudanças, o software recupere a conformidade. O monitoramento da conformidade é baseado em agentes e requisitos não funcionais. Os agentes são representados usando em i, a idéia é mostrar a colaboração entre os agentes para garantir a conformidade contínua. A especificação de requisitos de como cada agente deve se comportar também foi gerada usando a linguagem Desiree e BPMN. O catálogo de Requisitos Não Funcionais é usado para ajudar a definir as operações para o reconhecimento de software. A validação do framework foi feita em duas partes: primeiro, o processo de compliance e após todo o framework proposto. Para o processo de conformidade, o esforço e a exatidão foram medidos comparando o uso do processo proposto e um método ad-hoc. Para todo o framework, foi usado o exemplo de monitoramento das mudanças no ambiente quando um carro automatizado cruza a fronteira entre Washington e o Canadá. A contribuição deste trabalho é a estrutura da Eunomia, que tem uma perspectiva de processo e modelo de metas, com ênfase no monitoramento que ajuda a lidar com o desafio da conformidade. O framework equipa a equipe de engenharia de requisitos com um método sistemático e suportado por ferramentas que pode ser reutilizado para reduzir o esforço de tempo e melhorar a qualidade da especificação de requisitos.
Laws and regulation affect software development, as they frequently demand changes in software requirements to protect individuals and businesses regarding security, privacy, governance, sustainability and more. Legal requirements can dictate new requirements or constrain existing ones. The problem of software compliance is how to ensure that the software complies with the norms that the legislation imposes. The problem is particularly challenging because it combines difficultsteps: 1)analyze legal documents, 2) extract requirements from those documents, 3) identify conflictingrequirements with those already implemented in software and 4) ensure that software remains compliant even with the changes. Compliance is a continuous process: laws, software and the context within which software system operates changes continuously. The works dealing with the compliance problem focus only on one or two subjects: analyze legal documents or extract requirements or identify conflicts or changes. This thesis deals with all the problems at the same time; the idea is to extract requirements from legal text, compare them with the software requirement, resolve the possible conflicts that may arise, continuously leading with the changes on environment, laws and requirements. For this, this work proposes a framework that is composed of a compliance process and continuous monitoring of environmental changes. The framework deals with different types of laws (security, privacy, transparency, health care) that are represented in explicit norms. The compliance process supports the identification, extraction, comparison and conflict resolution to help software compliance, by producing a compliant set of requirements. The compliance process is based on the semantic annotation and goal model. The semantic annotation helps to extract requirements from thelaw, using patterns. The goal model is used to help the comparison between requirement and to represent requirements in a formal and consistent requirement specification. The process is tool supported; some tools were reused (Desiree and NomosT) to further each step. It was necessary to adapt the tools for the context of the compliance process, creating a guideline, patterns, and heuristics. The continuous monitoring is concerned about the changes that affect the software compliance and has presented using in i, the idea is to showthe collaboration between the agents to ensure the continuous compliance. The requirement specification of how each agent should behave was also generated using Business Process Modeling Notation and Desiree language. The Non Functional Requirements catalogue is used to help to define operalizations for the software awareness. The framework validation was made in two parts: first, the compliance process and after all the framework proposed. For the compliance process, the effort and correctness were measured comparing the use of the proposed process andan ad-hoc method. For the entire framework, the example of monitoring the changes in the environment when an automated car is crossing the border between Washington and Canada was used. The study shows that context has a strong influence on the software requirements, and nonconformity problems may incur penalties. The contribution of this work is the Eunomia framework that has a process and goal model perspective with emphasis on monitoring that helps to deal with the compliance challenge. The framework equips the requirements engineering team with a systematic method. Eunomia framework is a tool-supported and systematic process which can be reused to reduce the time effort and to improve the quality of the requirement specification that helps to create a compliant software requirement specification that is compliant over the time.
24
Engiel, Priscila. "Eunomia (Εὐνομία): A Requirement Engineering based Compliance Framework for Software Systems." Doctoral thesis, Università degli studi di Trento, 2018. http://hdl.handle.net/11572/283380.
Full textAbstract:
Laws and regulation affect software development, as they frequently demand changes in software’ requirements to protect individuals and businesses regarding security, privacy, governance, sustainability and more. Legal requirements can dictate new requirements or constrain existing ones. The problem of software compliance is howto ensure that the software complies with the norms that the legislation imposes. The problem is particularly challenging because it combines difficultsteps: 1)analyze legal documents, 2) extract requirements from those documents, 3) identify conflicting requirements with those already implemented in software and 4) ensure that software remains compliant even with the changes. Compliance is a continuous process: laws, software and the context within which software system operates changes
continuously. The works dealing with the compliance problem focus only on one or two subjects: analyze legal documents or extract requirements or identify conflicts or changes. This thesis deals with all the problems at the same time; the idea is to extract requirements
from legal text, compare them with the software requirement, resolve the possible conflicts that may arise, continuously leading with the changes on environment, laws and requirements. For this, this work proposes a framework that is composed of a compliance process and continuous monitoring of environmental changes. The framework deals with different types of laws (security, privacy, transparency, health care) that are represented in explicit norms. The compliance process supports the identification, extraction, comparison and conflict resolution to help software compliance, by producing a compliant set of requirements. The compliance process is based on the semantic annotation and goal model. The semantic annotation helps to extract requirements from thelaw, using patterns. The goal model is used to help the comparison between requirement and to represent requirements in a formal and consistent requirement specification. The process is tool supported; some tools were reused (Desiree and NomosT) to further each step. It was necessary to adapt the tools for the context of the
compliance process, creating a guideline, patterns, and heuristics. The continuous monitoring is concerned about the changes that affect the software compliance and has 7 the mechanism to ensure that even with those changes the software will regain compliance. The compliance monitor is basedon agents and Non Functional Requirements. The agents are represented using in i*, the idea is to showthe collaboration
between the agents to ensure the continuous compliance. The requirement specification of how each agent should behave was also generated using Business Process Modeling Notation and Desiree language. The Non Functional Requirements catalogue is used to
help to define operalizations for the software awareness. The framework validation was made in two parts: first, the compliance process and after all the framework proposed. For the compliance process, the effort and correctness were measured comparing the use of the proposed process andan ad-hoc method. For the entire framework, the example of monitoring the changes in the environment when an automated car is crossing the border between Washington and Canada was used. The study shows that context has a strong influence on the software requirements, and nonconformity problems may incur penalties. The contribution of this work is the Eunomia framework that has a process and goal model perspective with emphasis on monitoring that helps to deal with the compliance challenge. The framework equips the requirements engineering team with a systematic method. Eunomia framework is a tool-supported and systematic process which can be reused to reduce the time effort and to improve the quality of the requirement specification that helps to create a compliant software requirement specification that is compliant over the time.
25
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 textAbstract:
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.
26
Hamilton, Jakob, and Mahmoud Jeresi. "Geometry-Based Requirements : Support requirement owners in connecting and mediating requirements from SystemWeaver to CATIA V5." Thesis, Linköpings universitet, Maskinkonstruktion, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-149901.
Full textAbstract:
Requirements of a Volvo car are stored in a requirements management system at Volvo Car Group (VCG). VCG recently implemented a new requirements management system, a system called SystemWeaver. Many different types of requirements are stored in the SystemWeaver software, where the requirements can only be described in text and pictures. However, some requirements are geometry-based, describing some type of shape or measurement in space that the car should fulfil. Geometry-based requirements are stored in Teamcenter and have two components, the requirement text and requirement geometry in the form of CAD-models. The models are used to illustrate the requirement in space. This master thesis examines the possibilities of connecting text-based requirements in SystemWeaver to requirement geometries. The technical aspects are studied as well as the organizational mechanisms of creating and changing a geometry-based requirement. To find a working solution, research relating to the issue gave input to the project. Furthermore, interviews were conducted at different departments at VCG to get insight in the working tasks of requirement management at the company. The project resulted in a concept of a new process, describing the actions of geometry-based requirement management and how requirement geometries should be connected to SystemWeaver. The new concept outlined the logical steps that are required to work with SystemWeaver and geometry-based requirements. The work has laid a foundation on which future studies can be conducted to further streamline management of geometry-based requirements at VCG.
27
Penmetsa, Sneha, and Navya Lingampalli. "An Empirical Analysis of the Usageand Impact of RequirementsAttributes on RequirementsEngineering Research and Practice : A mixed method approach." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13352.
Full textAbstract:
Context: Requirement Engineering (RE) is one of the important phases inthe development of any software. Hence, there is a need to take much careon the elicitation and management of these requirements. Attributes playan important role in order to store and manage the important informationabout the requirements. There has been a lot of research performed inthe literature regarding the attributes of requirements engineering, but stillthere is a gap in the research that is concerned to requirement attributesin particular. Hence we focused more on identification and management ofthese requirement attributes. Objectives: In the current thesis, we focused mainly on the requirementattributes used in the companies and how they are managed. The majorobjectives we have framed in order to achieve our aim are: 1. To identify the publication trends in the literature of requirementsengineering that mainly focus on requirement attributes. 2. To identify the requirement attributes that are used by the softwarecompanies which includes both global attributes and project specificattributes. 3. To investigate how the requirement engineering models impact theselection of requirement attributes in companies. 4. To identify the phase and sequence of the requirement attributesbased on the four phases (elicitation, analysis, documentation and validation)of requirements engineering. 5. To investigate how the requirement attributes help in documentingand managing the continuous changes to requirements. Methods: In this thesis, we have performed Systematic Mapping Study(SMS),Systematic Literature Review (SLR) and Survey methods in order to achieveour aim and objectives. SLR is performed through the snowballing procedurebased on the guidelines of Wohlin[1].SMS is performed based on theguidelines of petersen et al.[2]. The main aim of the SMS is to identifythe publication trends in the literature on requirements engineering. Themain aim of SLR is to extract important information about the RE modelsand changes in requirements engineering. The main aim of the Survey is tovalidate the information retrieved from the SLR. Results: 83 requirement attributes were identified through the SLR outof which 15 attributes are in common. These 15 attributes are includedin the survey questionnaire. From these attributes, ID and description areidentified as most commonly used attributes from the survey. Publication trends related to requirement attributes are observed from the past 25 yearsrequirement attributes. From the survey, it is observed that there is a highimpact of RE models on requirement attributes. It is also observed thatmaximum number of attributes is stored in the form of documents and indatabases by the companies and the attributes are generally documented inanalysis phase and in specification phase. Results from the survey indicatedthat there is no particular sequence to document the attributes and theyare identified and documented based on the needs. Conclusions: This thesis lists different attributes that are used by thecompanies and also gives important information about the requirement attributesin detail that is close to the practical scenarios. It also gives scopefor further researches related to requirement attributes. This thesis helpthe practitioners to know the importance of consideration of requirementattributes in developing a project and its advantages. This work can beextended further by considering large number of attributes and retrievingresponses and opinions by large population.
28
Trijonis, Vidas. "Vartotojo įvedamos ir išvedamos informacijos specifikavimo konceptualizavimas." Master's thesis, Lithuanian Academic Libraries Network (LABT), 2005. http://vddb.library.lt/obj/LT-eLABa-0001:E.02~2005~D_20050115_134953-14112.
Full textAbstract:
The specification of requirements is one of the most important stages in the development of information system. The correct description is one of the principle goals in preparation of specification of requirements. Well-done specification of information system is a significant support to create software with high functionality, low maintenance and adaptation costs. Filled in document forms play an important role in the analysis of user requirements. This analysis helps to reduce the gap between the user and the system analyst. The methods of form analysis are oriented in creation of an entity relationship scheme. Information system department offering user requirements specification process of functional requirements specification method is similar to natural requirements analysis proceeding. This process begins from specification of users' requirements to incoming and out coming information. This work presents the model and prototype for specification of users' requirements to incoming and out coming information. The model is based on analysis of documents forms given by user. Method is divided into three phases: 1) user incoming and out coming information, 2) data structure analysis, 3) conceptual schema generation. The meta-model repository of requirements specification is presented. The specification process and prototype of specification of incoming and out coming information of user’s requirements are described.
29
Sheikh, Bilal Tahir. "Interdisciplinary Requirement Engineering for Hardware and Software Development - A Software Development Perspective." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-147886.
Full textAbstract:
The software and hardware industries are growing day by day, which makes their development environments more complex. This situation has a huge impact on the companies which have interdisciplinary development environments. To handle this situation, a common platform is required which can be acted as a bridge between hardware and software development to ease their tasks in an organized way. The research questions of the thesis aim to get information about differences and similarities in requirements handling, and their integration in current and future prospectives. The future prospect of integration is considered as a focused area. Interviews were conducted to get feedback from four different companies having complex development environments.
30
Hadi, Ahsanuzzaman. "Requirements Engineering for an Online Asset Mapping Tool for Disaster Preparedness." Thesis, Université d'Ottawa / University of Ottawa, 2017. http://hdl.handle.net/10393/35724.
Full textAbstract:
With increasing incidence of severe disasters, global policies and frameworks have been shifting towards an emphasis on collaboration and community resilience. The greater use of information systems to assist with disasters has prompted a need to examine how technology can support collaboration and resilience. Hence, this thesis aims to identify a set of requirements for a collaborative online asset mapping tool through a requirement engineering process. A multiple case study design was used with the objective of answering: (1) what are the functional, non-functional, and general system requirements of an online asset mapping tool for disaster preparedness; (2) is a standard “off-the-shelf” asset-mapping application feasible for community development and adaptive capacity building for disaster management; and (3) what are the potential designs that can address the requirements?
The specific cases examined were The Region of Waterloo, Ontario and Truro, Nova Scotia. The data from the cases was used to perform qualitative content analysis combined with activity diagrams, to determine and analyze the requirements for an online asset mapping tool to aid in disaster preparedness. The findings of the research included shared requirements between the two communities that encompassed: system purpose, system functionalities, user characteristics, and system requirements. Furthermore, prototype user interface (UI) wireframes were developed using the requirements results to show a potential design of an online asset mapping application. This thesis research addressed the need to design a tool that facilitates all aspects of the asset mapping process. Ultimately, this research builds the foundation to which future research can examine the requirements to design and develop a citizen-oriented tool to enhance community disaster resilience.
31
Frazier, David E. "Requirement elicitation of large web projects." [Johnson City, Tenn. : East Tennessee State University], 2004. http://etd-submit.etsu.edu/etd/theses/available/etd-1109104-113450/unrestricted/FrazierD112304f.pdf.
Full textAbstract:
Thesis (M.S.)--East Tennessee State University, 2004.Title from electronic submission form. ETSU ETD database URN: etd-1109104-113450 Includes bibliographical references. Also available via Internet at the UMI web site.
32
Johansson, Hanna. "Interdisciplinary Requirement Engineering for Hardware and Software Development : from a Hardware Development Perspective." Thesis, Linköpings universitet, Industriell miljöteknik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-139097.
Full textAbstract:
Complexity in products is increasing, and still there is lack of a shared design language ininterdisciplinary development projects. The research questions of the thesis concern differencesand similarities in requirement handling, and integration, current and future. Futureintegration is given more focus with a pair of research questions highlighting obstacles andenablers for increased integration. Interviews were performed at four different companieswith complex development environments whose products originated from different fields;hardware, software, and service. Main conclusions of the thesis are: Time-frames in different development processes are very different and hard to unite. Internal standards exist for overall processes, documentation, and modification handling. Traceability is poorly covered in theory whilst being a big issue in companies. Companies understand that balancing and compromising of requirements is critical fora successful final product. The view on future increased interdisciplinary development is that there are more obstaclesto overcome than enablers supporting it. Dependency is seen as an obstacle inthis regard and certain companies strive to decrease it.The thesis has resulted in general conclusions and further studies is suggested into morespecific areas such as requirement handling tools, requirement types, and traceability.
33
Islam, Gibrail, and Murtaza Ali Qureshi. "A Framework for Security Requirements Elicitation." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3448.
Full textAbstract:
Context: Security considerations are typically incorporated in the later stages of development as an afterthought. Security in software system is put under the category of non-functional requirements by the researchers. Understanding the security needs of a system requires considerable knowledge of assets, data security, integrity, confidentiality and availability of services. Counter measures against software attacks are also a security need of a software system. To incorporate security in the earliest stages, i.e. requirement gathering, helps building secure software systems from the start. For that purpose researchers have proposed different requirements elicitation techniques. These techniques are categorized into formal and informal techniques on the basis of finiteness and clarity in activities of the techniques. Objectives: Limitations of formal methods and lack of systematic approaches in informal elicitation techniques make it difficult to rely on a single technique for security requirements elicitation. Therefore we decided to utilize the strengths of formal and informal technique to mitigate their weaknesses by combining widely used formal and informal security requirements elicitation techniques. The basic idea of our research was to integrate an informal technique with a formal technique and propose a flexible framework with some level of formality in the steps. Methods: We conducted a systematic literature review to see “which are the widely used security requirement elicitation techniques?” as a pre-study for our thesis? We searched online databases i.e. ISI, IEEE Xplore, ACM, Springer, Inspec and compendeX. We also conducted a literature review for different frameworks that are used in industry, for security requirement elicitation. We conducted an experiment after proposing a security requirements elicitation Framework and compared the result from the Framework with that of CLASP and Misuse cases. Results:Two types of analysis were conducted on results from the experiment: Vulnerability analysis and Requirements analysis with respect to a security baseline. Vulnerability analysis shows that the proposed framework mitigates more vulnerabilities than CLASP and Misuse Cases. Requirements analysis with respect to the security baseline shows that the proposed framework, unlike CLASP and Misuse cases, covers all the security baseline features. Conclusions:The framework we have proposed by combining CLASP, Misuse cases and Secure TROPOS contains the strengths of three security requirements elicitation techniques. To make the proposed framework even more effective, we also included the security requirements categorization by Bogale and Ahmed [11]. The framework is flexible and contains fifteen steps to elicit security requirements. In addition it also allows iterations to improve security in a system
34
Sajjad, Umar, and Muhammad Qaisar Hanif. "Issues and Challenges of Requirement Elicitation in Large Web Projects." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3216.
Full textAbstract:
Requirement elicitation is a critical activity in the requirement development process and it explores the requirements of stakeholders. The success or failure of this process is based on identifying the relevant stakeholders and discovering their needs as well as the quality of requirements. The quality of the requirements is greatly influenced by methods applied during requirements elicitation process. Only complete and structured requirements make these projects more reliable. The common challenges that analysts face during elicitation process are to ensure effective communication between stakeholders as well as the acquisition of tacit knowledge. Mostly errors in the systems are due to poor communication between user and analyst, and these errors require more resources (time and money) to correct them. The understandability problems during elicitation process of large web projects can lead to requirements ambiguous, inconsistent, incorrect and unusable. Different methods (Conversational, Observational, Analytical and Synthetic) are available to deal with the problems during requirement elicitation process. The challenge for analysts is to select an appropriate method or set of methods and apply them for the clear, consistent and correct requirement gathering. This study based on the results of interviews conducted to the professionals, who have industrial experience in development of web systems. The elicitation problems that are identified in literature and interview along with applicability of elicitation methods for requirement gathering in large web projects development are documented in this report.Umar Sajjad Charhoi, Kotli, Azad Kashmir, Pakistan Muhammad Qaisar Hanif Bhimber, Azad Kashmir, Pakistan
35
Arab, Yar Mohammadi Mahshid, and Yar Mohammadi Mahshid Arab. "Personalized Requirements Elicitation Using a Domain Model." Thesis, University of Oregon, 2012. http://hdl.handle.net/1794/12349.
Full textAbstract:
My interest is in applying a domain model to help elicit personal requirements for the problem of community travel for people with cognitive impairments. The domain model I took advantage of is the ACT model, which is embedded in the tool I designed for defining required prompts for travel. I set up a study to look at the use of the domain model to help travel-planners generate personalized prompts for a traveler. My goal is to better understand the mechanisms of running a human-performance study and to get a first look at how the domain model can be understood by travel-planners. The study shows that most participants prefer the ACT-based tool to free-thinking and writing down prompts. I found out that the tool helps participants define more organized and concise prompts, but not necessarily a higher number of prompts, compared to the free-think approach. The tool captures prompts for some steps that are neglected while free-thinking. However, some steps of the ACT model need to be disambiguated or presented more effectively in the tool.
36
Soufi, Alan. "What Is the Structure of a Security Requirement?" Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-54618.
Full textAbstract:
Well-defined and unambiguous security requirements are essential for developing secure software systems. Misinterpretation of security terms and insufficient knowledge about security terminology can lead to inappropriate security requirements which, in turn, leave the system vulnerable to attacks. There exist many methods for eliciting and specifying security requirements. Among the possible methods, ontologies and templates can be used in order to elicit and/or specify security requirements. The objective of this study is to identify some common security concepts as well as some generic properties that characterize a security requirement, by comparing how ontologies and templates methods define and use security requirements. A comparison framework is therefore built in this thesis and applied to compare three ontology methods and three template methods in order to identify the generic properties and the security concepts that are related to security requirements. The properties and security concepts are analysed based on how they relate to the security requirements. The results of the study show that the security concepts that are mostly addressed by ontology and template methods considered in this work are: threat, asset, countermeasure and security objectives. It is also found that security requirements can be specified in different ways depending on which security concepts they concern.
37
Hassan, Syed Karimuddin and Syed Muhammad. "Defect Detection in SRS using Requirement Defect Taxonomy." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5253.
Full textAbstract:
Context: Defects occurred in the SRS may cause problems in project due to implementation of poor requirements which require extra time, effort, resources and budget to complete it. Reading techniques i.e., checklist based reading (CBR) helps to guide reviewers in identifying defects in software requirement specification (SRS) during individual requirement inspections. Checklists contain potential defects/problems to look for, but often lack clear definitions with examples of the problem, and also their abstractions are different. Therefore, there is a need for identifying existing defects and classifiers and to create a consolidated version of taxonomy. Objectives: We developed taxonomy for requirement defects that are in requirement specifications and compared it with the checklist based approach. The main objective was to investigate and compare the effectiveness and efficiency of inspection techniques (checklist and taxonomy) with M.Sc. software engineering students and industry practitioners by performing a both controlled student and industry experiment. Methods: Literature review, controlled student experiment and controlled industry experiment were the research methods utilized to fulfill the objectives of this study. INSPEC and Google scholar database was used to find the articles from the literature. Controlled student experiment was conducted with the M.Sc. software engineering students and controlled industry experiment was performed with the industry practitioners to evaluate the effectiveness and efficiency of the two treatments that are checklist and taxonomy. Results: An extensive literature review helped us to identify several types of defects with their definitions and examples. In this study, we studied various defect classifiers, checklists, requirement defects and inspection techniques and then built taxonomy for requirement defects. We evaluated whether the taxonomy performed better with respect to checklist using controlled experiments with students and practitioners. Moreover, the results of student experiment (p= 0.90 for effectiveness and p=0.10 for efficiency) and practitioner experiment (p=1.0 for effectiveness and p=0.70 for efficiency) did not show significant values with respect to effectiveness and efficiency. But because of less number of practitioners it is not possible to apply a statistical test since we also have used standard formulas to calculate effectiveness and efficiency. 2 out of the 3 reviewers using taxonomy found more defect types compared to 3 reviewers using checklist. 10-15% more defects have been found by reviewers using taxonomy. 2 out of the 3 reviewers using taxonomy are more productive (measuring in hours) compared to reviewers of checklist. Although the results are quite better than the student experiment but it is hard to claim that reviewers using taxonomy are more effective and efficient than the reviewers using checklist because of less subjects in number. The results of the post experiment questionnaire revealed that the taxonomy is easy to use and easy to understand but hard to remember while inspecting SRS than the checklist technique. Conclusions: Previously researchers created taxonomies for their own purpose or on industry demand. These taxonomies lack clear and understandable definitions. To overcome this problem, we built taxonomy with requirement defects which consists of definitions and examples. No claims are made based on student experiment because of insignificant values with respect to effectiveness and efficiency. Although the controlled industry experiment results showed that taxonomy performed slightly better than the checklist in efficiency i.e., in defect detection rate and effectiveness i.e., number of defect found. From this we can conclude that taxonomy helps guiding the reviewers to indentify defects from SRS but not quite much so it is recommended to perform a further study with practitioners in a large scale for effective results.skarimuddin@yahoo.com, hassanshah357@gmail.com
38
Pukėnas, Vilius. "Reikalavimų specifikacijos analizės priemonių tyrimas ir kūrimas." Master's thesis, Lithuanian Academic Libraries Network (LABT), 2007. http://vddb.library.lt/obj/LT-eLABa-0001:E.02~2007~D_20070121_185849-75644.
Full textAbstract:
In the early stage of building a new informational system requirement engineering involves all the processes related to the requirement system and research of problems emerged during this process. In this stage the requirements specification of corresponding information system are built. Many different notations serve for this purpose, selection of which is dependant on available resources and project goals. Requirements specification must be of good quality. It is evaluated by characteristics of quality. Specifications could be analyzed and improved by using various tools including CASE tools. The specification is developed and its quality is improved by making analysis of requirements. Well done specification is basis for creating high leveled functionality system.
39
Chen, Mingda, and Yao He. "Exploration on Automated Software Requirement Document Readability Approaches." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-14816.
Full textAbstract:
Context. The requirements analysis phase, as the very beginning of software development process, has been identified as a quite important phase in the software development lifecycle. Software Requirement Specification (SRS) is the output of requirements analysis phase, whose quality factors play an important role in the evaluation work. Readability is a quite important SRS quality factor, but there are few available automated approaches for readability measurement, because of the tight dependency on readers' perceptions. Low readability of SRS documents has a serious impact on the whole process of software development. Therefore, it's extremely urgent to propose effective automated approaches for SRS documents readability measurement. Using traditional readability indexes to analyze readability of SRS documents automatically is a potentially feasible approach. However, the effectiveness of this approach is not systematically evaluated before. Objectives. In this study, firstly, we aim to understand the readability of texts and investigate approaches to score texts readability manually. Then investigate existing automated readability approaches for texts with their working theories. Next, evaluate the effectiveness of measuring the readability of SRS documents by using these automated readability approaches. Finally, rank these automated approaches by their effectiveness. Methods. In order to find out the way how human score the readability of texts manually and investigate existing automated readability approaches for texts, systematic literature review is chosen as the research methodology. Experiment is chosen to explore the effectiveness of automated readability approaches. Results. We find 67 articles after performing systematic literature review. According to systematic literature review, human judging the readability of texts through reading is the most common way of scoring texts readability manually. Additionally, we find four available automated readability assessments tools and seven available automated readability assessments formulas. After executing the experiment, we find the actual value of effectiveness of all selected approaches are not high and Coh-Metrix presents the highest actual value of effectiveness of automated readability approach among the selected approaches. Conclusions. Coh-Metrix is the most effective automated readability approach, but the feasibility in directly applying Coh-Metrix in SRS documents readability assessments cannot be permitted. Since the actual value of evaluated effectiveness is not high enough. In addition, all selected approaches are based on metrics of readability measures, but no semantic factors are blended in readability assessments. Hence studying more on human perception quantifying and adding semantic analysis in SRS documents readability assessment could be two research directions in future.
40
Liang, Feng. "Modeling in Modelica and SysML of System Engineering at Scania Applied to Fuel Level Display." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-84829.
Full textAbstract:
The main objective of this thesis is to introduce a four perspectives structure in order to provide one solution for traceability and dependability in the system design phase. The traceability between different perspectives help engineers have a clear picture of the whole system before goes to the real implementation. Fuel Level Display system from Scania Truck is used to undertake as a case study to offer insights of the approach. A four perspectives structure is made in the first place in order to analysis traceability between different viewpoints. After implementing the Fuel Level Display system in Modelica, a verification scenario is specified to perform a complete requirement verification process for system design against requirements.
41
Nusom, F. Allen. "Application of the systems engineering process to the explosive ordnance disposal requirement for an underwater system." Master's thesis, This resource online, 1990. http://scholar.lib.vt.edu/theses/available/etd-12232009-020010/.
Full text
42
Su, Mehmet Onur. "Business Process Moedlling Based Computer-aided Software Functional Requirements Generation." Master's thesis, METU, 2004. http://etd.lib.metu.edu.tr/upload/3/12604698/index.pdf.
Full textAbstract:
Problems of requirements which are identified in the earlier phase of a software development project can deeply affect the success of the project. Thus studies which aim to decrease these problems are crucial. Automation is foreseen
to be one of the possible solutions for decreasing or removing some of the problems originating from requirements.
This study focuses on the development and implementation of an automated tool that will generate requirements in natural language from business process models. In this study, The benefits of the tool are discussed, and the tool is compared with other software requirement s related tools with respect to their functionality. The developed tool has been tested within a large military project and the results of using the tool are presented.
43
Ahmad, Jamil. "Octane requirement increase arising from the use of lead free fuel." Thesis, Aston University, 1989. http://publications.aston.ac.uk/9796/.
Full textAbstract:
Lead in petrol has been identified as a health hazard and attempts are being made to create a lead-free atmosphere. Through an intensive study a review is made of the various options available to the automobile and petroleum industry. The economic and atmospheric penalties coupled with automobile fuel consumption trends are calculated and presented in both graphical and tabulated form. Experimental measurements of carbon monoxide and hydrocarbon emissions are also presented for certain selected fuels. Reduction in CO and HC's with the employment of a three-way catalyst is also discussed. All tests were carried out on a Fiat 127A engine at wide open throttle and standard timing setting. A Froude dynamometer was used to vary engine speed. With the introduction of lead-free petrol, interest in combustion chamber deposits in spark ignition engines has ben renewed. These deposits cause octane requirement increase or rise in engine knock and decreased volumetric efficiency. The detrimental effect of the deposits has been attributed to the physical volume of the deposit and to changes in heat transfer. This study attempts to assess why leaded deposits, though often greater in mass and volume, yield relatively lower ORI when compared to lead-free deposits under identical operating conditions. This has been carried out by identifying the differences in the physical nature of the deposit and then through measurement of the thermal conductivity and permeability of the deposits. The measured thermal conductivity results are later used in a mathematical model to determine heat transfer rates and temperature variation across the engine wall and deposit. For the model, the walls of the combustion cylinder and top are assumed to be free of engine deposit, the major deposit being on the piston head. Seven different heat transfer equations are formulated describing heat flow at each part of the four stroke cycle, and the variation of cylinder wall area exposed to gas mixture is accounted for. The heat transfer equations are solved using numerical methods and temperature variations across the wall identified. Though the calculations have been carried out for one particular moment in the cycle, similar calculations are possible for every degree of the crank angle, and thus further information regarding location of maximum temperatures at every degree of the crank angle may also be determined. In conclusion, thermal conductivity values of leaded and lead-free deposits have been found. The fundamental concepts of a mathematical model with great potential have been formulated and it is hoped that with future work it may be used in a simulation for different engine construction materials and motor fuels, leading to better design of future prototype engines.
44
Hardy, AliciA Jillian Jackson 1978. "Vehicle fuel economy benefit and aftertreatment requirement of an HCCI-SI engine system." Thesis, Massachusetts Institute of Technology, 2007. http://hdl.handle.net/1721.1/42986.
Full textAbstract:
Thesis (Ph. D.)--Massachusetts Institute of Technology, Dept. of Mechanical Engineering, 2007.Includes bibliographical references (v. 2, p. 821-823).
This body of work dimensions the HCCI fuel economy benefits and required aftertreatment performance for compliance with emissions regulations in North America and Europe. The following parameters were identified as key factors influencing the benefit of implementing HCCI over driving cycle: * Power-to-weight ratio * Operation range of HCCI * Conditions of the driving cycle * Application of constraints that cause "un-natural" mode transitions * Application of transition penalties * Available after-treatment performance * Constraints imposed by emissions regulations This study shows that development priorities for attaining maximal fuel economy benefit during urban driving cycles differ greatly in North America and in Europe due to differences in emissions regulations. The combined effect of increasing power-to-weight ratio, increasing the operation range of HCCI, removing operational constraints on HCCI implementation, and reducing fuel penalties associated with transitions into and out of HCCI mode is shown to double the emissions-constrained fuel economy benefit of HCCI during the new European driving cycle. These factors are shown to have modest impact on fuel economy benefit of HCCI during the North American city driving cycle when compliance with the more stringent emissions regulations is required. In order to attain maximal fuel economy benefit and comply with emissions regulations in California, improving conversion efficiencies in the aftertreatment of lean engine exhaust must be a primary focus. Fuel economy benefit of HCCI during the highway driving cycles is shown to be most responsive to the amount of time the engine spends in the speed and load range of HCCI operation. Time spent in HCCI mode during these driving cycles is most heavily influenced by changes in power-to-weight ratio and upper load limit for HCCI.
by AliciA Jillian J Hardy.
Ph.D.
45
Baranski, Jacob A. "Experimental Investigation of Octane Requirement Relaxation in a Turbocharged Spark-Ignition Engine." University of Dayton / OhioLINK, 2013. http://rave.ohiolink.edu/etdc/view?acc_num=dayton1375262182.
Full text
46
Suo, Dajiang. "Tool-assisted hazard analysis and requirement generation based on STPA." Thesis, Massachusetts Institute of Technology, 2016. http://hdl.handle.net/1721.1/105628.
Full textAbstract:
Thesis: S.M. in Engineering Systems, Massachusetts Institute of Technology, School of Engineering, Institute for Data, Systems, and Society, 2016.Cataloged from PDF version of thesis.
Includes bibliographical references (pages 79-82).
The automotive industry has been observing a trend of integrating new features into old vehicle designs to provide more convenience and flexibility to customers. However, it can be challenging to ensure safety without the support of appropriate techniques and tools for hazard analysis and requirement engineering. Systems Theoretic Process Analysis (STPA) is a hazard analysis technique that has been developed at MIT. It is based on systems and control theory and aims at capturing more causal factors leading to accidents, including component interactions. So far, STPA has been successfully applied to various industries. While there are tools that allow engineers to document the results of hazard analysis based on STPA, there are no tools that provide guidance during the analysis. Also, although a method is proposed to generate requirements from an STPA analysis, no tools have been developed to support that process. This thesis illustrates how tools can provide support for hazard analysis and requirement generation based on STPA, based on the proof of concept of a software tool that was developed at MIT. This STPA tool assists STPA Step I analysis by applying logical simplification to the original Step I results and automatically generating the simplified requirement in formal and executable forms. The simplified requirements are easily understandable and address all of the unsafe control actions identified in the original STPA analysis. The use of the STPA tool is illustrated through a case study of automotive systems that include multiple features. The STPA tool generates simplified and formal requirements for each individual feature based on STPA Step I results. In addition, it is also used to check whether conflicts between features have been resolved and to identify exactly what decisions should be made jointly between multiple design teams.
by Dajiang Suo.
S.M. in Engineering Systems
47
Hallgren, Ellen. "A Problem Analysis at Tieto Leading to the Development of a Test-Data-Handler Application." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-81171.
Full textAbstract:
The purpose of this thesis is to provide the Maftaki team at Tieto a proposal of a tool or improve one of the current tools that will support their processes. In order to find a suitable tool a problem analysis model, as described by Goldkuhl and Rostlinger (1988), was used. To find out what kind of problem existed, members from the Maftaki team were interviewed. Out of the problems that were brought up during the interviews, difficulties with finding telephone numbers that can be used in the testing environment at testing was chosen. In order to solve the problem, a tool that handles test data was to be developed. Firstly, a requirement elicitation was performed by interviewing potential users of the system. In this way, use cases and functional requirements were elicited. A framework called Struts2, an Object-relational Mapping framework, Hibernate and an Inversion of Control container, Spring was used during the development. Maven was used for building the application. During the development demos were performed in order to elicit more requirements from the users and to clarify some requirements. Also refactoring was done continuously during the development. When the development of the application was done a couple of test cases were written and some basic testing of the application were performed .Syftet med examensarbetet är att ge Maftaki teamet vid Tieto ett förslag på ett verktyg eller förbättra ett av de nuvarande verktygen för att ge support till deras processer. För att hitta ett lämpligt verktyg gjordes först en problemanalys, den problemanalysmodell som beskrivs i Goldkuhl och Röstlinger, (1988), bok användes. För att ta reda på vilka problem som kunde finnas genomförde ett antal intervjuer med medlemmar i Maftaki. Ur de problem som hade kommit fram under intervjuerna valdes svårigheten att hitta telefonnummer som kan användas i testmiljön vid testning ut. För att lösa problemet beslutades att ett verktyg som hanterar testdata skulle utvecklas. Först genomfördes en kravfångst genom att intervjua potentiella användare och på så sätt togs användningsfall och funktionella krav fram. För att bygga applikationen användes ett ramverk som heter Struts2, ett Object/Relational Mapping ramverk, Hibernate, och en Inversion of Control container, Spring. För att bygga applikationen användes Maven. Under utvecklingens gång genomfördes demos för att få fler krav ifrån användare och för att få en klarare bild av betydelsen av vissa krav. Också omstrukturering av kod genomfördes kontinuerligt under utvecklingens gång. Sist av allt genomfördes ett antal test på applikationen.
48
Montrimaitė, Donata. "Reikalavimų specifikacijos pilnumo įvertinimo galimybių tyrimas." Master's thesis, Lithuanian Academic Libraries Network (LABT), 2007. http://vddb.library.lt/obj/LT-eLABa-0001:E.02~2007~D_20070117_090618-79309.
Full textAbstract:
ODRES (output driven requirements engineering)method, which is being developed in the department of information systems comprises the following stages: separating out the context, specification of function results, specification of data sources, specification of data source processing, modelling, automatic projectionof interface of information system and prototype. While creating requirement specification, there arises a need to evaluate the quality of it. In every stage of creating requirement specification an analyst does not know if he or she has got enough information in order to do produce a working prototype of the system. Therefore, in this study the problem of information system is analysed, namely, the problem of how to hallmark the quality of ISRS? How to measure this quality? What must the IS be, so that it is of good quality? While seeking to evaluate the quality of RS, it is necessary to understant and analyse what is quality on the whole, how it is defined, how it is measured and if it is possible to measure it at all. In this study methods which are used to measure the quality and the possibilities of CASE tools to evaluate specification quality are analyzed. In the research requirements to evaluate the RS quality have also been established and the experiment that realizes the RS quality evaluation has been done.
49
Duffus, LuAnn McClernan. "Exoskeleton Requirements for Firefighters." Ohio University / OhioLINK, 2019. http://rave.ohiolink.edu/etdc/view?acc_num=ohiou1574688158168652.
Full text
50
AMIRTHALINGAM, ILAKIA, and NADJA ZAHIRALDINNI. "Requirement Management in Product Development in B2B : A Study on the Process of Capturing Customer Requirements." Thesis, KTH, Skolan för industriell teknik och management (ITM), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-279771.
Full textAbstract:
Our world is ever-changing hence the surroundings ought to develop accordingly. This applies particularly to the product development process and therefore, it is of high priority to adapt to the changes. This can be achieved by observing the market and especially the customers. It is believed that customers possess certain knowledge that can be crucial pieces of information when developing products. According to the literature, involving customer will result in the increased diversity of information and as a result, this may enhance the quality as well as the development process. Nevertheless, integrating customers may prove to be a tedious task as well as a costly one especially if the customers are of a complex nature. Due to this, it may be appropriate to apply various methods to map customer’s needs and requirements to further develop them in a systematic manner. The purpose of this study is to gain greater knowledge about customer involvement, mainly focusing on international as well as complex customers. The essence of the study is to obtain information about how an organisation navigates around customers along with what roles and responsibilities there are within the organisations. The study was conducted at Xolaris, a smallmedium size (SME) company within software development, hence the collected data stems from that organisation. Initially, a comparative literature study was executed to obtain a broader spectrum of knowledge. This was complemented by interviews with respondents who held relevant positions within the organisation. The interviews were conducted in a semi-structured manner for the sole purpose of optimizing the information flow. From the data that was collected, several categories were derived that contributed to the study in a suitable manner. The results of the study proved that there are obstacles when involving customers. Yet, there are methods and tools to overcome these obstacles, conversely, they may not always prove to be efficient and one must adapt oneself according to the situation. Furthermore, this study confirmed that it is of great importance to maintain stable customer relationships, hence there cannot be a fixed method to process the customer's requirements. Moreover, the study also proves there ought to be a limit to the degree of customer involvement.Världen står konstant inför för nya utmaningar samt förändringar och därav bör omgivningen utvecklas i enlighet med detta. Inte minst gäller det för produktutvecklingsprocessen som har eftersträvat att anpassa sig till diverse utvecklingar. Detta kan bland annat uppnås genom att observera marknaden och särskilt kunderna. Kunderna kan besitta kunskap som kan vara avgörande information när man utvecklar produkter. Enligt litteraturstudien kan involvering av kunder resulterat i ökad mångfald av information och på så vis kan det bidra till att produktkvalitet förbättras såväl som utvecklingsprocessen. Integrering av kunder kan emellertid visa sig vara en ledsam handling såväl som en kostsam sådan, särskilt om kunderna är av en komplex karaktär. Därför kan det vara lämpligt att använda olika metoder för att kartlägga kundernas behov samt krav för att vidareutveckla dem på ett systematiskt vis. Syftet med denna studie är att erhålla bredare kunskap om kundinvolvering med fokus på internationella såväl som komplexa kunder. Vidare kommer studien inrikta sig mot att studera hur en organisation navigerar runt kunder samt vilka roller och ansvarsområden som finns inom organisationerna. Studien genomfördes på Xolaris, ett mindre företag (SME) som specialiserar sig i mjukvaruutveckling, därav härstammar all erhållen data från denna organisation. För att besvara på samtliga frågeställningar genomfördes en litteraturstudie för få en djupare förståelse om kundinvolvering . Detta kompletterades med intervjuer från respondenter som besatt relevanta positioner inom organisationen. Intervjuerna genomfördes på ett semistrukturerat viss i syfte att optimera informationsflödet. Data som samlades in kodades samt delades in i lämpliga kategorier. Resultaten av studien visade att det finns hinder när kunderna involveras. Trots det, finns det metoder samt verktyg för att hantera dessa hinder, å andra sidan är de inte effektiva i alla situationer utan man böra anpassa efter förhållandet. Vidare bekräftade denna studie att det är av stor vikt att upprätthålla en god kundrelation. Däremot visade studien på att det bör finnas en sund gräns för graden av kundinvolvering då för mycket involvering inte alltid gynnar projektet.