Relevant bibliographies by topics / Requirements engineering

Contents

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

Academic literature on the topic 'Requirements engineering'

Author: Grafiati
Published: 4 June 2021
Last updated: 5 October 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 'Requirements 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 "Requirements engineering"

1

Firesmith, Donald. "Requirements Engineering." Journal of Object Technology 1, no. 4 (2002): 93. http://dx.doi.org/10.5381/jot.2002.1.4.c7.

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

Firesmith, Donald. "Requirements Engineering." Journal of Object Technology 1, no. 5 (2002): 83. http://dx.doi.org/10.5381/jot.2002.1.5.c7.

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

Winbladh, Kristina. "Requirements engineering." XRDS: Crossroads, The ACM Magazine for Students 10, no. 4 (August 31, 2004): 4. http://dx.doi.org/10.1145/1027313.1027317.

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

Finkelsteiin, Anthony. "Requirements engineering." ACM SIGSOFT Software Engineering Notes 17, no. 1 (January 1992): 45–47. http://dx.doi.org/10.1145/134292.134297.

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

Berry, D. M., and B. Lawrence. "Requirements Engineering." IEEE Software 15, no. 2 (March 1998): 26–29. http://dx.doi.org/10.1109/ms.1998.663780.

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

Egesoy, Ahmet, and Aylin Güzel. "Fuzzy Logic Support for Requirements Engineering." International Journal of Innovative Research in Computer Science & Technology 9, no. 2 (March 2021): 14–21. http://dx.doi.org/10.21276/ijircst.2021.9.2.3.

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

Hasan, M. Mahmudul. "Regulatory Requirements Compliance in Requirements Engineering." International Journal of Systems and Service-Oriented Engineering 6, no. 4 (October 2016): 22–35. http://dx.doi.org/10.4018/ijssoe.2016100102.

Full text
Abstract:
Regulations and policies contain a rich source of requirements and failure to address these authoritative requirements in software system development can impose costly penalties for regulatory noncompliance. Despite the advancement of information system research, regulatory requirements compliance remains one of the primary challenges still to be efficiently dealt in system development because of the scarce information, complexity, and understanding of available approaches in requirements engineering process of a system development. This paper reports a systematic literature review of the documented approaches of regulatory requirements compliance, classifies these approaches according to different criteria and provides a qualitative analysis of their operational characteristics. The results of this analysis can serve system developers as the means of deriving appropriate methods and tools for regulatory requirements compliance in the software system development.
APA, Harvard, Vancouver, ISO, and other styles
8

Firesmith, Donald. "Engineering Security Requirements." Journal of Object Technology 2, no. 1 (2003): 53. http://dx.doi.org/10.5381/jot.2003.2.1.c6.

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

Firesmith, Donald. "Requirements Engineering Tasks." Journal of Object Technology 5, no. 8 (2006): 21. http://dx.doi.org/10.5381/jot.2006.5.8.c3.

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

Carrillo de Gea, Juan M., Joaquín Nicolás, José L. Fernández Alemán, Ambrosio Toval, Christof Ebert, and Aurora Vizcaíno. "Requirements Engineering Tools." IEEE Software 28, no. 4 (July 2011): 86–91. http://dx.doi.org/10.1109/ms.2011.81.

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

Dissertations / Theses on the topic "Requirements engineering"

1

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

Full text
Abstract:

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

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

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

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

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

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

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

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

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

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

Full text
Abstract:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Books on the topic "Requirements engineering"

1

Hofmann, Hubert F. Requirements Engineering. Wiesbaden: Deutscher Universitätsverlag, 2000. http://dx.doi.org/10.1007/978-3-663-07965-1.

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

Hull, Elizabeth, Ken Jackson, and Jeremy Dick. Requirements Engineering. London: Springer London, 2002. http://dx.doi.org/10.1007/978-1-4471-3730-6.

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

Hull, Elizabeth, Ken Jackson, and Jeremy Dick. Requirements Engineering. London: Springer London, 2011. http://dx.doi.org/10.1007/978-1-84996-405-0.

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

Dick, Jeremy, Elizabeth Hull, and Ken Jackson. Requirements Engineering. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-61073-3.

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

Zowghi, Didar, and Zhi Jin, eds. Requirements Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2014. http://dx.doi.org/10.1007/978-3-662-43610-3.

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

Macaulay, Linda A. Requirements Engineering. London: Springer London, 1996. http://dx.doi.org/10.1007/978-1-4471-1005-7.

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

Pohl, Klaus. Requirements Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-12578-2.

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

1942-, Jackson Ken, and Dick Jeremy 1955-, eds. Requirements engineering. 3rd ed. London: Springer, 2011.

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

Timm, Michael, ed. Requirements Engineering ’91. Berlin, Heidelberg: Springer Berlin Heidelberg, 1991. http://dx.doi.org/10.1007/978-3-642-76622-0.

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

Partsch, Helmuth. Requirements-Engineering systematisch. Berlin, Heidelberg: Springer Berlin Heidelberg, 1998. http://dx.doi.org/10.1007/978-3-662-09758-8.

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

Book chapters on the topic "Requirements engineering"

1

Pohl, Klaus. "Continuous Requirements Engineering." In Requirements Engineering, 29–40. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-12578-2_3.

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

Dick, Jeremy, Elizabeth Hull, and Ken Jackson. "Erratum to: Requirements Engineering." In Requirements Engineering, E1. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-61073-3_10.

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

Hofmann, Hubert F. "Situatedness in Requirements Engineering." In Requirements Engineering, 189–229. Wiesbaden: Deutscher Universitätsverlag, 2000. http://dx.doi.org/10.1007/978-3-663-07965-1_5.

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

Pohl, Klaus. "The Requirements Engineering Framework." In Requirements Engineering, 41–57. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-12578-2_4.

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

Wiesner, Stefan, Margherita Peruzzini, Jannicke Baalsrud Hauge, and Klaus-Dieter Thoben. "Requirements Engineering." In Concurrent Engineering in the 21st Century, 103–32. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-13776-6_5.

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

Partsch, Helmut A. "Requirements Engineering." In Specification and Transformation of Programs, 19–55. Berlin, Heidelberg: Springer Berlin Heidelberg, 1990. http://dx.doi.org/10.1007/978-3-642-61512-2_2.

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

Ortel, Markus, Marc Malot, Andreas Baumgart, Jan Steffen Becker, Ralf Bogusch, Stefan Farfeleder, Nora Gerber, et al. "Requirements Engineering." In CESAR - Cost-efficient Methods and Processes for Safety-relevant Embedded Systems, 69–143. Vienna: Springer Vienna, 2012. http://dx.doi.org/10.1007/978-3-7091-1387-5_3.

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

Loucopoulos, Pericles. "Requirements engineering." In Design process improvement, 116–39. London: Springer London, 2005. http://dx.doi.org/10.1007/978-1-84628-061-0_5.

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

O’Regan, Gerard. "Requirements Engineering." In Undergraduate Topics in Computer Science, 85–99. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-031-07816-3_5.

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

Hruschka, Peter. "Requirements Engineering." In Handbuch IT-Projektmanagement, 421–52. München: Carl Hanser Verlag GmbH & Co. KG, 2014. http://dx.doi.org/10.3139/9783446441217.013.

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

Conference papers on the topic "Requirements engineering"

1

Pelletier, Brad. "Systems Engineering - Requirements Development." In Vertical Flight Society 80th Annual Forum & Technology Display, 1–4. The Vertical Flight Society, 2024. http://dx.doi.org/10.4050/f-0080-2024-1100.

Full text
Abstract:
Today's world of engineering is moving faster with a goal of producing more, in less time. This leads to the question that every engineer faces, "do I take the time to develop requirements or jump straight into the design effort?" This question is easily answered when the engineer understands the role of requirements and how they fit into the product life cycle. Once the role of requirements is understood the next step is to understand what requirements are and how they work. The goal is to produce efficient, precise, and professional requirements that describe one system or a system of multiple systems for the project that is in work. When requirements are done right, the project will be completed on time, on budget, with a happy customer that is receiving the product they paid for. This paper is intended to train engineers to understand what requirements are and how to develop them. The paper will cover the basic reasoning for requirements, where requirements fit into the product design lifecycle, and rules for writing good requirements.
APA, Harvard, Vancouver, ISO, and other styles
2

Bencharqui, Hatime, and Adil Anwar. "Ontology Design for Requirements Engineering." In 2024 International Conference on Intelligent Systems and Computer Vision (ISCV), 1–6. IEEE, 2024. http://dx.doi.org/10.1109/iscv60512.2024.10620132.

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

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
4

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
5

Pols, Andy. "Requirements engineering." In Addendum to the 1997 ACM SIGPLAN conference. New York, New York, USA: ACM Press, 1997. http://dx.doi.org/10.1145/274567.274583.

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

Nuseibeh, Bashar, and Steve Easterbrook. "Requirements engineering." In the conference. New York, New York, USA: ACM Press, 2000. http://dx.doi.org/10.1145/336512.336523.

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

van Lamsweerde, Axel. "Requirements engineering." In the 16th ACM SIGSOFT International Symposium. New York, New York, USA: ACM Press, 2008. http://dx.doi.org/10.1145/1453101.1453133.

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

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
9

Otto, Paul N., and Annie I. Anton. "Addressing Legal Requirements in Requirements Engineering." In 15th IEEE International Requirements Engineering Conference (RE 2007). IEEE, 2007. http://dx.doi.org/10.1109/re.2007.65.

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

Vassev, Emil, and Mike Hinchey. "Autonomy requirements engineering." In 2013 IEEE 14th International Conference on Information Reuse & Integration (IRI). IEEE, 2013. http://dx.doi.org/10.1109/iri.2013.6642470.

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

Reports on the topic "Requirements 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

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
3

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
4

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
5

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
6

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
7

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
8

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
9

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
10

CORPS OF ENGINEERS WASHINGTON DC. Engineering and Design. Hydrologic Engineering Requirements for Flood Damage Reduction Studies. Fort Belvoir, VA: Defense Technical Information Center, January 1995. http://dx.doi.org/10.21236/ada402463.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Requirements 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