Relevant bibliographies by topics / Requirement engineering

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Requirement engineering'

Author: Grafiati
Published: 4 June 2021
Last updated: 8 June 2024

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

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources 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.

Journal articles on the topic "Requirement engineering"

1

Pavanasam, Velayutham, and Chandrasekaran Subramaniam. "Understanding Security Requirement Engineering." Indian Journal of Applied Research 1, no. 6 (October 1, 2011): 111–12. http://dx.doi.org/10.15373/2249555x/mar2012/38.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Pavanasam, Velayutham, and Chandrasekaran Subramaniam. "Metabolic Algorithm for Software Requirement Engineering." Advanced Materials Research 267 (June 2011): 639–44. http://dx.doi.org/10.4028/www.scientific.net/amr.267.639.

Full text
Abstract:
The objective of this work is to apply metabolic algorithm to the various items involved during the software development process. The metabolic algorithm is introduced in the rewriting mechanism of membrane or P system considering many time varying functions. Rules for requirement evolution, reaction between items in the membrane, communications between data items, process speed-up and abort rule are being proposed. The metabolic algorithm is applied for the transformation of user requirements into system requirements which can be further segregated into functional as well as non-functional requirements. The requirement elicitation is illustrated and verified to obtain the most expected requirement objects using C# programming language.
APA, Harvard, Vancouver, ISO, and other styles
3

Abdulaziz Abdullah, Alsahli, and Hameed Ullah Khan. "FreGsd: A Framework for Global Software Requirement Engineering." Journal of Software 10, no. 10 (October 2015): 1189–98. http://dx.doi.org/10.17706//jsw.10.10.1189-1198.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Hameed, Isma. "Title: Security in Requirement Engineering for Qualitative Products." International Journal of Engineering and Technology 4, no. 6 (2012): 747–49. http://dx.doi.org/10.7763/ijet.2012.v4.476.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Li, Yan. "CMM Based Requirement Engineering Model in Software Development." Applied Mechanics and Materials 385-386 (August 2013): 1701–4. http://dx.doi.org/10.4028/www.scientific.net/amm.385-386.1701.

Full text
Abstract:
Requirement engineering is the basis of software development, and it is a key factor determines whether a software development can be successful or not. This article first presents the requirement engineering at capability maturity model (CMM). Then the problem in demand development and demand management are discussed in the second section. Finally, a CMM based requirement engineering model is presented. This model provides a more efficient and effective method in requirement engineering. As the most important parts of this model, requirements analysis, form requirement document, review requirement and change control are described in detail.
APA, Harvard, Vancouver, ISO, and other styles
6

Aballa, A. N., D. U. Ebem, P. C. Ezeagwu, and A. N. Ohadoma. "Significance of Requirement Engineering In Educational Technology Development." Advances in Multidisciplinary and scientific Research Journal Publication 1 (July 30, 2022): 61–66. http://dx.doi.org/10.22624/aims/rebk2022-p6.

Full text
Abstract:
ABSTRACT To effectively actualize the advantages of educational technology in the educational sector, the requirements of the learners, the teachers and all the stakeholders must be thoroughly captured by requirement engineering. This chapter shows the different ways in which requirement engineering has managed the requirements to produce software and other educational technology tools and platforms to make teaching and learning more effective. Keywords: Requirement Engineering, Educational Technology, Teaching, learning, Institutions.
APA, Harvard, Vancouver, ISO, and other styles
7

Laborde, Romain, Sravani Teja Bulusu, Ahmad Samer Wazan, Arnaud Oglaza, and Abdelmalek Benzekri. "A Methodological Approach to Evaluate Security Requirements Engineering Methodologies: Application to the IREHDO2 Project Context." Journal of Cybersecurity and Privacy 1, no. 3 (July 13, 2021): 422–52. http://dx.doi.org/10.3390/jcp1030022.

Full text
Abstract:
An effective network security requirement engineering is needed to help organizations in capturing cost-effective security solutions that protect networks against malicious attacks while meeting the business requirements. The diversity of currently available security requirement engineering methodologies leads security requirements engineers to an open question: How to choose one? We present a global evaluation methodology that we applied during the IREHDO2 project to find a requirement engineering method that could improve network security. Our evaluation methodology includes a process to determine pertinent evaluation criteria and a process to evaluate the requirement engineering methodologies. Our main contribution is to involve stakeholders (i.e., security requirements engineers) in the evaluation process by following a requirement engineering approach. We describe our experiments conducted during the project with security experts and the feedback we obtained. Although we applied it to evaluate three requirements engineering methods (KAOS, STS and SEPP) in the context of network security, our evaluation methodology can be instantiated in other contexts and other methods.
APA, Harvard, Vancouver, ISO, and other styles
8

Nour, Tarek, and Noura Albaladi. "Software Requirement Engineering: Traceability Techniques and Tools." International Journal of Computers and Informatics 2, no. 4 (August 28, 2023): 8–23. http://dx.doi.org/10.59992/ijci.2023.v2n4p1.

Full text
Abstract:
Requirement Traceability is one of the activities in managing requirements. It is important for software projects and is affecting the quality of software products. Requirement Traceability is a method to analyze the effect of changes among various software development lifecycle parts. Agile methodologies have been presented as an alternative to traditional software engineering methodologies. The transformation between traditional and agile methodologies is a hard task so the need for traceability grows. This paper introduces traceability research at the requirement engineering on the traceability literature published during the last years. It also investigates and discusses the requirements for traceability issues. It finally presents several requirement traceability techniques and tools to support traceability.
APA, Harvard, Vancouver, ISO, and other styles
9

Ghanyani, Ume-Sauda, Maham Murad, and Waqas Mahmood. "Crowd-based Requirement Engineering." International Journal of Education and Management Engineering 8, no. 3 (May 8, 2018): 43–53. http://dx.doi.org/10.5815/ijeme.2018.03.05.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Fatima, Tazeen, and Waqas Mahmood. "Requirement Engineering in Agile." International Journal of Education and Management Engineering 9, no. 4 (July 8, 2019): 20–33. http://dx.doi.org/10.5815/ijeme.2019.04.03.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Requirement engineering"

1

Louis, Harriet. "Towards agile requirement engineering." Thesis, Stellenbosch : Stellenbosch University, 2015. http://hdl.handle.net/10019.1/97337.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
2

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

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

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
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
Background: Technical debt(TD) is incurred when developers accept compromises in a system in one dimension to meet urgent demand in some other dimensions (e.g., a deadline). If technical debt is not managed correctly, it will cause hidden danger to software’s long term success. It does not get enough attention when TD applies to the requirements engineering. Objectives: In this study, we investigate the current state of requirements debt(ReD). We aim to give a precise definition of ReD. We also focus on the factors that can induce ReD in the requirement engineering and requirement management process. Moreover, we want to summarize the measurement tools to detect and locate the ReD. Finally, we try to find approaches and ideas to manage ReD. Methods: We conducted a systematic mapping study (SMS) and a survey for all of the objectives. When performing the systematic mapping study, we applied snow- balling method to ensure we find related and enough papers. Results: According to the analysis and results of SMS and the survey, we concluded the definition of requirements debt. We also presented and classified 54 ReD induced factors into 8 categories. 10 ReD measurement techniques searched from literatures were listed with a brief description for each one, suggestions from software practi- tioners on ReD detection also gathered and displayed. The management techniques and theoretical suggestions were presented based on related factors. Conclusions: From research result, we find academia and industry lay different emphasises on how to manage ReD. To stimulate Industry pay more attention on control and manage ReD effectively, this paper calls for the two sides to work on the same point.
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
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
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
Requirement engineering (RE) is an important phase in any project. Both functional and non-functional requirements are required to be elicited. Quality requirements (QRs) are usually catered at the end of software development process. Along with functional requirements, non-functional (QRs) also need to be handled and implemented through a structural way. It is observed that most organizations do not have proper management for quality requirements in their project life cycles. Especially if we consider the case of market driven requirement engineering (MDRE), it is a dire need to handle those QRs along with the functional requirement using a structural way. In this study we investigate Requirements Abstraction Model (RAM), which is basically designed for MDRE and is the case of continuous RE. The purpose was to analyze RAM specifications, which could be able to provide an effective way of manage QRs. RAM also deals with the specification of QRs, so it was required to investigate that how effective RAM can handle the creation of QRs.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Requirement engineering"

1

Grady, Jeffrey O. Systems requirement analysis. Boston, MA: Academic Press, 2006.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Systems requirement analysis. Boston: Elsevier Academic Press, 2005.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Wundenberg, Sven-Michael. Requirement Engineering for Knowledge-Intensive Processes. Wiesbaden: Springer Fachmedien Wiesbaden, 2015. http://dx.doi.org/10.1007/978-3-658-08832-3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Alexander, Michael G. Requirement assurance: A verification process. Hampton,Va: National Aeronautics and Space Administration, Langley Research Center, 2011.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Klion, Jerome. Practical Electronic Reliability Engineering: Getting the Job Done from Requirement through Acceptance. Dordrecht: Springer Netherlands, 1992.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Rama, Mimoza. Requirement engineering for Lotus Notes: A case study in Price Waterhouse. London: University of East London, 1996.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Klion, J. Practical electronic reliability engineering: Getting thejob done from requirement through acceptance. New York: Van Nostrand Reinhold, 1992.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Practical electronic reliability engineering: Getting the job done from requirement through acceptance. New York: Van Nostrand Reinhold, 1992.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Law, Freddy Chi-tak. Computer aided software engineering (CASE) requirement for object-oriented programming systems (OOPS) development. [s.l: The Author], 1992.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Soni, N. K. Investment and output coefficient for engineers and engineering technicians and methodology for estimation of requirement of engineering degree and diploma holders. New Delhi: Institute of Applied Manpower Research, 1987.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Requirement engineering"

1

Mettler, Cory J. "Requirement Documents." In Engineering Design, 119–43. Cham: Springer International Publishing, 2023. http://dx.doi.org/10.1007/978-3-031-23309-8_7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Lee, Jonathan, Jong-Yih Kuo, Nien-Lin Hsueh, and Yong-Yi Fanjiang. "Trade-off Requirement Engineering." In Software Engineering with Computational Intelligence, 51–72. Berlin, Heidelberg: Springer Berlin Heidelberg, 2003. http://dx.doi.org/10.1007/978-3-540-36423-8_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Lutters, Eric. "Requirement Specification." In CIRP Encyclopedia of Production Engineering, 1–4. Berlin, Heidelberg: Springer Berlin Heidelberg, 2018. http://dx.doi.org/10.1007/978-3-642-35950-7_6466-4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Lutters, Eric. "Requirement Specification." In CIRP Encyclopedia of Production Engineering, 1431–33. Berlin, Heidelberg: Springer Berlin Heidelberg, 2019. http://dx.doi.org/10.1007/978-3-662-53120-4_6466.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Lutters, Eric. "Requirement Specification." In CIRP Encyclopedia of Production Engineering, 1047–50. Berlin, Heidelberg: Springer Berlin Heidelberg, 2014. http://dx.doi.org/10.1007/978-3-642-20617-7_6466.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Oulehlová, Alena, Jiří Barta, Hana Malachová, and Jiří F. Urbánek. "Requirement Engineering for Emergency Simulations." In IFIP Advances in Information and Communication Technology, 388–96. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-15994-2_39.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Liong, Shie-Yui, Ongko Sutjahyo, and Bernard Rasli. "Irrigation Water Requirement Model." In Engineering Software IV, 755–65. Berlin, Heidelberg: Springer Berlin Heidelberg, 1985. http://dx.doi.org/10.1007/978-3-662-21877-8_61.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Crowder, James A., and Curtis W. Hoff. "Introduction to Multidisciplinary Requirement Engineering (MDRE)." In Requirements Engineering: Laying a Firm Foundation, 1–9. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-030-91077-8_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Lu, Ruqian, and Zhi Jin. "Automating the Requirement Analysis." In Domain Modeling-Based Software Engineering, 123–66. Boston, MA: Springer US, 2000. http://dx.doi.org/10.1007/978-1-4615-4487-6_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Ukarande, S. K. "Water Requirement of Crops." In Irrigation Engineering and Hydraulic Structures, 5–25. Cham: Springer Nature Switzerland, 2023. http://dx.doi.org/10.1007/978-3-031-33552-5_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Requirement engineering"

1

Gaspard-Boulinc, Hélène, and Stéphane Conversy. "Usability requirements for requirement engineering tools." In the 26th Conference. New York, New York, USA: ACM Press, 2014. http://dx.doi.org/10.1145/2670444.2670458.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Smoots, Gregory C., Andreas Garstenauer, and Timothy Blackburn. "Measuring System Usability during Requirement Engineering: Requirements Engineering." In 2016 International Conference on Information Systems Engineering (ICISE). IEEE, 2016. http://dx.doi.org/10.1109/icise.2016.20.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Faisal, Muhammad, Ghassan F. Issa, Iqra Ayub, Muhammad Asadullah, Uzma Nazar Joiya, and Muhammad Iqbal. "How Automate Requirements Engineering System Effects and Support Requirement Engineering." In 2022 International Conference on Business Analytics for Technology and Security (ICBATS). IEEE, 2022. http://dx.doi.org/10.1109/icbats54253.2022.9758997.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Mishra, Deepti, Alok Mishra, and Ali Yazici. "Successful requirement elicitation by combining requirement engineering techniques." In 2008 First International Conference on the Applications of Digital Information and Web Technologies (ICADIWT). IEEE, 2008. http://dx.doi.org/10.1109/icadiwt.2008.4664355.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Yang, Yanwu, Fen Xia, Wensheng Zhang, Xian Xiao, Yiqun Li, and Xuhui Li. "Towards Semantic Requirement Engineering." In 2008 IEEE International Workshop on Semantic Computing and Systems (WSCS). IEEE, 2008. http://dx.doi.org/10.1109/wscs.2008.21.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Shikta, Shatadru, Sowvik Das, Somania Mahal, H. Shahriyar, Kazi Al Jannat, and Mahady Hasan. "Requirement Engineering in Startups." In 16th International Conference on Software Technologies. SCITEPRESS - Science and Technology Publications, 2021. http://dx.doi.org/10.5220/0010561002070214.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Shikta, Shatadru, Sowvik Das, Somania Mahal, H. Shahriyar, Kazi Al Jannat, and Mahady Hasan. "Requirement Engineering in Startups." In 16th International Conference on Software Technologies. SCITEPRESS - Science and Technology Publications, 2021. http://dx.doi.org/10.5220/0010561000002992.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Lu, Chih-Wei, Chih-Hung Chang, William C. Chu, Ya-Wen Cheng, and Hsin-Chien Chang. "A Requirement Tool to Support Model-Based Requirement Engineering." In 2008 32nd Annual IEEE International Computer Software and Applications Conference. IEEE, 2008. http://dx.doi.org/10.1109/compsac.2008.232.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Souza, Vitor E. Silva, Alexei Lapouchnian, and John Mylopoulos. "(Requirement) evolution requirements for adaptive systems." In 2012 7th International Symposium on Software Engineering for Adaptive and Self-Managing Systems (SEAMS). IEEE, 2012. http://dx.doi.org/10.1109/seams.2012.6224402.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Bulusu, Sravani Teja, Romain Laborde, Ahmad Samer Wazan, Francois Barrere, and Abdelmalek Benzekri. "Applying a requirement engineering based approach to evaluate the security requirements engineering methodologies." In SAC 2018: Symposium on Applied Computing. New York, NY, USA: ACM, 2018. http://dx.doi.org/10.1145/3167132.3167417.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Requirement engineering"

1

Striuk, Andrii M., Сергій Олексійович Семеріков, Hanna M. Shalatska, Vladyslav P. Holiver, Андрій Миколайович Стрюк, Ганна Миколаївна Шалацька, and Владислав Павлович Голівер. Software requirements engineering training: problematic questions. Криворізький державний педагогічний університет, January 2022. http://dx.doi.org/10.31812/123456789/6980.

Full text
Abstract:
The key problems of training Requirement Engineering and the following ways to overcome the contradiction between the crucial role of Requirement Engineering in industrial software development and insufficient motivation to master it in the process of Software Engineering specialists professional training were identified based on a systematic research analysis on the formation of the ability of future software engineers to identify, classify and formulate software requirements: use of activity and constructivist approaches, game teaching methods in the process of modeling requirements; active involvement of stakeholders in identifying, formulating and verifying requirements at the beginning of the project and evaluating its results at the end; application of mobile technologies for training of geographically distributed work with requirements; implementation of interdisciplinary cross-cutting Software Engineering projects; involvement of students in real projects; stimulating the creation of interdisciplinary and age-old student project teams.
APA, Harvard, Vancouver, ISO, and other styles
2

Mullen, O. D. Function and requirement for a waste disloging and conveyance system for the Idaho National Engineering Laboratory high level liquid waste tanks. Office of Scientific and Technical Information (OSTI), September 1996. http://dx.doi.org/10.2172/658959.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

SOFTWARE PRODUCTIVITY CONSORTIUM HERNDON VA. Consortium Requirements Engineering Guidebook. Fort Belvoir, VA: Defense Technical Information Center, December 1993. http://dx.doi.org/10.21236/ada274691.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Williams, Otis. Engineering and Design. Hydrologic Engineering Requirements for Reservoirs. Fort Belvoir, VA: Defense Technical Information Center, October 1997. http://dx.doi.org/10.21236/ada402460.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Siranosian, Antranik Antonio. Engineering Analysis Baseline Model Requirements. Office of Scientific and Technical Information (OSTI), January 2019. http://dx.doi.org/10.2172/1492682.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Bort, Joshua. Engineering Disciplines, Requirements, and Opportunities. Office of Scientific and Technical Information (OSTI), August 2020. http://dx.doi.org/10.2172/1647198.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Mead, Nancy R., Eric D. Hough, II Stehney, and Theodore R. Security Quality Requirements Engineering (SQUARE) Methodology. Fort Belvoir, VA: Defense Technical Information Center, November 2005. http://dx.doi.org/10.21236/ada443493.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Schembri, Philip Edward. Weapon Systems Engineering Material Database Requirements. Office of Scientific and Technical Information (OSTI), April 2015. http://dx.doi.org/10.2172/1178718.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Awduche, D., J. Malcolm, J. Agogbua, M. O'Dell, and J. McManus. Requirements for Traffic Engineering Over MPLS. RFC Editor, September 1999. http://dx.doi.org/10.17487/rfc2702.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Ganska, Ralph, John Grotzky, Jack Rubinstein, Jim Van Buren, and Gary Petersen. Requirements Engineering and Design Technology Report,. Fort Belvoir, VA: Defense Technical Information Center, October 1995. http://dx.doi.org/10.21236/ada325333.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Requirement engineering' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography