Relevant bibliographies by topics / Survey of requirements

Contents

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

Academic literature on the topic 'Survey of requirements'

Author: Grafiati
Published: 4 June 2021
Last updated: 1 February 2022

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 'Survey of requirements.'

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 "Survey of requirements"

1

Sakthivel, Sachidanandam. "A Survey of Requirements Verification Techniques." Journal of Information Technology 6, no. 2 (June 1991): 68–79. http://dx.doi.org/10.1177/026839629100600203.

Full text
Abstract:
Requirements verification is a set of procedures used to detect errors in requirement specifications. This paper discusses various types of requirement errors and illustrates each error with an example. It also examines several techniques used for requirements verification and the capability of each technique to identify various requirement errors. In addition, it reviews the use of each technique in various requirements analysis approaches and indicates the drawbacks of these techniques. This paper can help systems analysts to be aware of possible errors in requirement specifications and the limitations in requirements verification while using a requirements analysis approach.
APA, Harvard, Vancouver, ISO, and other styles
2

Ivan, Jan. "Artillery Survey for Autonomous Weapon Systems and Basic Requirements on Survey Units." Vojenské rozhledy 28, no. 4 (November 25, 2019): 63–77. http://dx.doi.org/10.3849/2336-2995.28.2019.04.063-077.

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

Shukla, Vivek, Dhirendra Pandey, and Raj Shree. "Requirements Engineering: A Survey." Communications on Applied Electronics 3, no. 5 (November 25, 2015): 28–31. http://dx.doi.org/10.5120/cae2015651947.

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

Kaur, Harsimran, and Dr Ashish Sharma. "Non-Functional Requirements Research: Survey." International Journal of Science and Engineering Applications 3, no. 6 (December 20, 2014): 172–82. http://dx.doi.org/10.7753/ijsea0306.1003.

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

Palomares, Cristina, Carme Quer, and Xavier Franch. "Requirements reuse and requirement patterns: a state of the practice survey." Empirical Software Engineering 22, no. 6 (December 19, 2016): 2719–62. http://dx.doi.org/10.1007/s10664-016-9485-x.

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

Hedman, Lois Deming, David M. Morris, Cecilia L. Graham, Cynthia J. Brown, Matthew P. Ford, Debbie A. Ingram, Marjorie J. Hilliard, and Alice J. Salzman. "Locomotor Requirements for Bipedal Locomotion: A Delphi Survey." Physical Therapy 94, no. 1 (January 1, 2014): 52–67. http://dx.doi.org/10.2522/ptj.20120514.

Full text
Abstract:
BackgroundBipedal locomotor control requirements may be useful as classifications for walking dysfunction because they go beyond gait analysis to address all issues contributing to walking dysfunction.ObjectiveThe objective of this study was to determine whether locomotor experts could achieve consensus about the requirements for bipedal locomotion.Design and MethodsLocomotor experts from physical therapy and other related professions participated in an electronic mail Delphi survey. Experts recommended additions, deletions, rewording, and merges for 15 proposed locomotor requirements in round 1. In rounds 2 and 3, panelists commented on and rated the validity, mutual exclusiveness, and understandability of each requirement. Consensus was defined a priori as: (1) 75% or more panelists agree or strongly agree that a requirement is valid, mutually exclusive, and understandable in round 3; (2) no difference between round 2 and 3 ratings with kappa coefficients ≥.60; and (3) a reduction in panelists who commented and convergence of comments between rounds 1 and 3. Content analysis and nonparametric statistics were used.ResultsFifty-eight panelists reached full consensus on 5 locomotor requirements (Initiation, Termination, Anticipatory Dynamic Balance, Multi-Task Capacity, and Walking Confidence) and partial consensus for 7 other requirements. There were no significant differences in ratings between rounds 2 and 3, and there was a decrease in the percentage of panelists who commented between rounds 1 and 3.LimitationsThe study's 6-month time frame may have contributed to panelist attrition.ConclusionsLocomotor experts achieved consensus on several bipedal locomotor requirements. With validation, these requirements can provide the framework for a clinically feasible and systematic diagnostic tool for physical therapists to categorize locomotor problems and standardize intervention for walking dysfunction.
APA, Harvard, Vancouver, ISO, and other styles
7

Fussell, M., and Sarah A. Corbet. "BUMBLEBEE HABITAT REQUIREMENTS: A PUBLIC SURVEY." Acta Horticulturae, no. 288 (January 1991): 159–63. http://dx.doi.org/10.17660/actahortic.1991.288.21.

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

Sakthivel, Sachidanandam. "A survey of requirements verification techniques." Journal of Information Technology 6, no. 2 (June 1991): 68–79. http://dx.doi.org/10.1057/jit.1991.12.

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

Serban, Ioan, Sandra Cespedes, Corneliu Marinescu, Cesar A. Azurdia-Meza, Juan S. Gomez, and Doris Saez Hueichapan. "Communication Requirements in Microgrids: A Practical Survey." IEEE Access 8 (2020): 47694–712. http://dx.doi.org/10.1109/access.2020.2977928.

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

Harrison, PJ, PW Yu, PA Thompson, NM Price, and DJ Phillips. "Survey of selenium requirements in marine phytoplankton." Marine Ecology Progress Series 47 (1988): 89–96. http://dx.doi.org/10.3354/meps047089.

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

Dissertations / Theses on the topic "Survey of requirements"

1

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
2

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
3

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

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

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

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

Kollu, Ravichandra Kumar. "Requirements scoping outside product lines : Systematic Literature Review and Survey." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-11766.

Full text
Abstract:
Context: Scoping is admitted as a key activity in Market Driven Software Development for handling the constant inflow of requirements. It helps in identifying the features, domains and products which help for gaining economic benefits in Software Product Line (SPL) development. Beyond SPL, managing the scope of the project is a major risk for project management. Continuously changing scope creates a congestion state to handle the requirements inflow which causes negative consequences like scope scrap and scope creep. However, for managing negative consequences caused due to requirements volatility depicts a need for work on requirements scoping outside the product line.  Objectives: In this study, an exploratory work is carried to identify the literature and industrial perspectives on requirements scoping outside the product line. The main objectives are: Identifying the state of literature of requirements scoping outside product line and variability analysis. To explore the industrial practice on requirements scoping. Suggesting recommendations in improving the scoping process based on the literature and survey.  Methods: Systematic Literature Review (SLR) using snowballing procedure was conducted to identify the literature available on requirements scoping outside the product line. Quality assessment using rigor and relevance was performed to find the trustworthiness of the papers obtained through SLR. The data obtained through SLR was analyzed using narrative analysis. Furthermore, an industrial survey was performed using web questionnaire to identify the industrial perspective on requirements scoping. Statistical analysis was performed for analyzing the data obtained from survey.  Results: 23 relevant papers were identified through SLR. The results were categorized as definitions obtained, phenomena, challenges and methods/tools identified. From the finding of SLR, an industrial survey was conducted, which has obtained 93 responses. The challenges that were identified through literature were validated through survey and are prioritized. Moreover, the study identified additional challenges that are not discussed in the literature. Additionally, the approaches followed in organizations while scoping the requirements were identified through the survey. Conclusions: This study identified that scope creep is the most frequently occurring phenomenon that organizations are facing throughout the lifecycle of the project. In addition project delays, quality issues and project cost were identified as the most occurring scoping associated challenges. Moreover, scoping activity was identified as the continuous activity which changes significantly throughout the lifecycle. Finally, suggestions were given for improving the scoping process.
APA, Harvard, Vancouver, ISO, and other styles
6

Lin, Fangfei, and Hao Chen. "Comparative Study of Requirements Traceability in Facing Requirements Change: Systematic Literature Study and Survey." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-17841.

Full text
Abstract:
Context: Requirements change commonly occurs during the software development lifecycle. Requirements traceability is one of the important techniques to support requirement change management and analysis, ensure quality and keep requirements consistent during development. We find that existing research mentioned various issues and challenges during practicing requirements traceability, and the practitioners show certain obstacles on the subject. Major existing work of the area focuses on requirements traceability processes, frameworks, and techniques to address certain issues accordingly. And we want to focus on and investigate the existing challenges to practice requirements traceability systematically. Method: We investigate the requirements traceability and its challenges through a systematic literature review (SLR) of various concepts and existing challenges of requirements traceability, and a survey of 7 Chinese small-and-medium-sized enterprises (SMEs). With 7 interviews, we studied different traceability practices and situations with the surveyed companies under the possible impact of requirement change, development processes, tools, and other factors. And then we conducted conventional qualitative content analysis to identify and classify the challenges in practicing requirements traceability. Results: With the systematic literature review, we classified 14 categories of academic identified challenges. Through the collected data of the survey, we identified and discussed 6 categories of the requirement traceability challenges, involving costs, tools, awareness, documentation, etc. And we compared and discussed the connections and differences of the survey results with the literature for validation of our survey results and possible extension to the existing work. Through research, we may help the practitioners to deal with requirements change with traceability practice better by recognizing and preventing the obstacles. Our research may provide researchers with more information on practical situations. And in the future, researchers may study the traceability models more effectively aiming at addressing the existing problems.
APA, Harvard, Vancouver, ISO, and other styles
7

Mudduluru, Pavan. "Value Based Requirements Engineering : State-of-art and Survey." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-11814.

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

Sulehri, Latif. "Comparative Selection of Requirements Validation Techniques Based on Industrial Survey." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-1178.

Full text
Abstract:
In software engineering the requirements validation has very core importance. The requirements validation very helpful to judge that software requirements specification (SRS) is complete and free of bugs. The requirements validation is a assurance that the software requirements document is free of unwanted requirements and completely consistent. In order to remove inconsistency, detect defects and make the software requirements document fully functional the requirements validation is key factor. All possible requirements validation techniques available in academia such requirements reviews , requirements prototyping, requirements testing and viewpoint-oriented requirements validation are explained properly in this thesis report. In a very readable and understandable way the thesis presents all pros and cons of these requirements validation techniques practiced in different software companies in Sweden and available in academia. This report explains all possible advantages and issues related with these RVTs. In order to judge the best performance of these RVTs and to make their comparison I used a proper channel. I have designed a very effective survey questionnaire with the help of my colleges and literature review. To make creative comparison I conduct interviews and send survey questionnaire to different people working in requirements engineering departments in different software industries in Sweden. Finally the satisfaction levels of different software industries with these requirements validation techniques presents in this thesis report. These variables such as defect detection, time and cost are used to measure the satisfaction levels.
I Software Engineering kraven validering har en mycket central betydelse. Den kravvalidering very helpful att bedöma att Kravspecifikation (SRS) är klar och felfria. Kraven validering är en garanti för att programvaran kravdokument är fri från oönskade krav och helt konsekvent. För att undanröja inkonsekvens, upptäcka brister och göra programvaran kravdokument fullt funktionella kraven validering är viktig faktor. Alla möjliga kravvalidering tekniker inom den akademiska sådana krav recensioner, krav prototyper, provning och synpunkt-orienterade kravvalidering förklaras ordentligt i denna avhandling rapport. I ett mycket lättläst och begripligt sätt avhandling presenterar alla fördelar och nackdelar med dessa krav validera metoder praktiseras i olika mjukvaruföretag i Sverige och finns i den akademiska världen. Denna rapport förklarar alla möjliga fördelar och frågor kring dessa RVTs. För att bedöma de bästa resultaten i dessa RVTs och göra en jämförelse av dem använde jag en riktig kanal. Jag har skapat en mycket effektiv frågeformulär med hjälp av min högskolor och litteraturgenomgång. Skapa kreativa jämförelse jag intervjua och skicka frågeformuläret till olika personer som arbetar inom tekniska kraven för dessa avdelningar i olika programvaruföretag i Sverige. Slutligen tillfredsställande nivåer av olika programvaruföretag med dessa krav validering teknik presenteras i denna avhandling rapport. Dessa variabler såsom Upptäcka, tid och kostnader används för att mäta tillfredsställande nivåer.
Author: Latif Hussain Sulehri E-mail: latifsulehry@hotmail.com Phone: +46 704 917 140
APA, Harvard, Vancouver, ISO, and other styles
9

Ganna, Anil, and Sri Sai Ripughna Rishitosh Sonti. "Analysis of Requirements Volatility in Elicitation Process : A Systematic Literature Review & Survey." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-19339.

Full text
Abstract:
Context: In the requirements engineering phase, requirements elicitation is considered as the most important task as it is the initial phase in which the requirements are gathered and prioritised. Changes in requirements may lead to project failure or delay in project deliveries. So, it is essential to elicit the requirements at the early stage to avoid changes in requirements in the later stage of development. Therefore, there is a need to study the impact of volatility in elicitation techniques to gather requirements appropriately in the early stages. Objectives: In the present thesis, we focused on the analysis of the requirements volatility in the requirement elicitation phase. The main objectives we have formulated to achieve our goal are Objective 1: To identify and determine the various causes of requirement volatility. Objective 2: To examine the impact of requirement volatility in the requirement elicitation process. Objective 3: To examine whether the procedure of elicitation techniques differ if volatility occurs while eliciting the requirements. Methods: In this thesis, we have implemented a Systematic Literature Review(SLR) and Survey research methods in order to attain our aim and objectives. SLR is performed for objective 1, to receive the data about the causes of volatility in various development life cycle phases. A survey is conducted to identify the causes of volatility in all phases of development, in the elicitation phase, and check whether the process of elicitation techniques differ if volatility occurs while eliciting the requirements. Results: From the SLR and survey, numerous factors of causes of volatility on the software development lifecycle were identified. Several new factors were identified from both the research methods. The factors have its own interpretation for the cause of volatility. Moreover, from the survey results, we can determine that the volatility occurs in the elicitation phase and has a huge impact while eliciting the requirements. Most of the practitioners working with the agile development process and waterfall model have stated that the impact of volatility results in prolonging the elicitation phase, slowing down the project, etc. Conclusions: For this research, our contribution is to provide insights on the impact of volatility in the elicitation process and check whether the elicitation techniques and its process change due to volatility. Based on the results of the respondents, we can conclude that the elicitation techniques procedure change is not intentional and not only because of the volatility but also due to some external factors while eliciting the requirements.
APA, Harvard, Vancouver, ISO, and other styles
10

Abu, Daqqa Nizar, and Serkan Alan. "On the Requirements to Implement E-maintenance Cost effectively: Survey Study." Thesis, Linnéuniversitetet, Institutionen för maskinteknik (MT), 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-31681.

Full text
Abstract:
Nowadays, companies started to realize the impact of a good maintenance strategy on the production process. Quality, performance as well as availability are affected by maintenance; existing maintenance strategies help to optimize the production process to achieve high quality products with a low production cost. A new strategy of maintenance has immerged recently, e-maintenance provides an easy solution to follow up with maintenance, it provides condition monitoring, documentation, and it also gives you the best maintenance solution that fits your goals and vision. Articles related to e-maintenance was studied and analyzed to know the steps to implement a cost-effective e-maintenance. The authors came up with a model that describes the implementation process in three main steps.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Survey of requirements"

1

Consortium, Local Management in Schools Initiative IT User Requirements. IT User Requirements Consortium: Initial survey. London: Local Management in Schools Initiative, 1989.

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

France, Virginia Grace. The regulation of margin requirements: A survey. Urbana-Champaign, Ill: Bureau of Economic and Business Research, 1990.

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

Evans, R. W. Electrical bonding: A survey of requirements, methods, and specifications. MSFC, Ala: National Aeronautics and Space Administration, Marshall Space Flight Center, 1998.

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

FEDERAL AVIATION ADMINISTRATION. Requirements survey of aviation facilities, Greater Bangkok Area, Thailand. [Washington: U.S. Govt. Print. Off.], 1985.

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

Jobe, Jared B. Information requirements for battlefield management system: Survey and prototype evaluation. Alexandria, Va: U.S. Army Research Institute for the Behavioral and Social Sciences, 1986.

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

E, Allen James. Nursing home federal requirements, guidelines to surveyors, and survey protocols. 5th ed. New York: Springer Pub. Co., 2003.

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

1935-, Allen James E., ed. Nursing home federal requirements, guidelines to surveyors, and survey protocols. 4th ed. New York: Springer Pub. Co., 2000.

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

Emmel, Thomas C. Status survey and habitat requirements of Florida's endemic Schaus swallowtail butterfly. Tallahassee, FL: Nongame Wildlife Program, Florida Game and Fresh Water Fish Commission, 1995.

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

United Methodist Church (U.S.). General Council on Ministries. Survey of United Methodist opinion: The goal to increase membership, July 1986. Dayton, Ohio: General Council on Ministries, 1986.

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

McCracken, John R. A survey of public library certification requirements in the national library community. Carson City: The Library, 1991.

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

Book chapters on the topic "Survey of requirements"

1

Sita Devulapalli, Akhil Khare, and O. R. S. Rao. "Requirements Prioritization: Survey and Analysis." In Proceedings of the International Congress on Information and Communication Technology, 567–75. Singapore: Springer Singapore, 2016. http://dx.doi.org/10.1007/978-981-10-0755-2_60.

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

Palomares, Cristina, Xavier Franch, and Carme Quer. "Requirements Reuse and Patterns: A Survey." In Requirements Engineering: Foundation for Software Quality, 301–8. Cham: Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-05843-6_22.

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

Almaliki, Malik, Funmilade Faniyi, Rami Bahsoon, Keith Phalp, and Raian Ali. "Requirements-Driven Social Adaptation: Expert Survey." In Requirements Engineering: Foundation for Software Quality, 72–87. Cham: Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-05843-6_6.

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

Verner, June M., Steven J. Bleistein, Narciso Cerpa, and Karl A. Cox. "Requirements Practices: A Comparative Industrial Survey." In Advances in Information Systems Development, 719–30. Boston, MA: Springer US, 2006. http://dx.doi.org/10.1007/978-0-387-36402-5_62.

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

Rempel, Patrick, Patrick Mäder, Tobias Kuschke, and Ilka Philippow. "Requirements Traceability across Organizational Boundaries - A Survey and Taxonomy." In Requirements Engineering: Foundation for Software Quality, 125–40. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-37422-7_10.

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

Ameller, David, and Xavier Franch. "How Do Software Architects Consider Non-Functional Requirements: A Survey." In Requirements Engineering: Foundation for Software Quality, 276–77. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-14192-8_25.

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

Bouillon, Elke, Patrick Mäder, and Ilka Philippow. "A Survey on Usage Scenarios for Requirements Traceability in Practice." In Requirements Engineering: Foundation for Software Quality, 158–73. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-37422-7_12.

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

Väänänen, Olli, and Timo Hämäläinen. "Requirements for Energy Efficient Edge Computing: A Survey." In Lecture Notes in Computer Science, 3–15. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-030-01168-0_1.

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

Sun, Xiaoxun, Hua Wang, and Jiuyong Li. "Validating Privacy Requirements in Large Survey Rating Data." In Next Generation Data Technologies for Collective Computational Intelligence, 445–69. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-20344-2_17.

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

Regnell, Björn. "What Is Essential? – A Pilot Survey on Views About the Requirements Metamodel of reqT.org." In Requirements Engineering: Foundation for Software Quality, 232–39. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-30282-9_16.

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

Conference papers on the topic "Survey of requirements"

1

Idri, Ali, Sofia Ouhbi, Jose Luis Fernandez-Aleman, and Ambrosio Toval. "A survey of requirements engineering education." In 2012 IEEE Global Engineering Education Conference (EDUCON). IEEE, 2012. http://dx.doi.org/10.1109/educon.2012.6201142.

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

Bajpai, Vikas, and Ravi Prakash Gorthi. "On non-functional requirements: A survey." In 2012 IEEE Students' Conference on Electrical, Electronics and Computer Science (SCEECS). IEEE, 2012. http://dx.doi.org/10.1109/sceecs.2012.6184810.

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

Zwerneman, Farrel. "A Survey of CVN Toughness Requirements." In Structures Congress 2000. Reston, VA: American Society of Civil Engineers, 2000. http://dx.doi.org/10.1061/40492(2000)150.

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

Schobbens, P. Y., P. Heymans, and J. C. Trigaux. "Feature Diagrams: A Survey and a Formal Semantics." In 14th IEEE International Requirements Engineering Conference. IEEE, 2006. http://dx.doi.org/10.1109/re.2006.23.

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

Rebaudengo, Manuela. "ENVIRONMENTAL QUANTITY SURVEY FOR BUILDINGS GPP REQUIREMENTS." In 17th International Multidisciplinary Scientific GeoConference SGEM2017. Stef92 Technology, 2017. http://dx.doi.org/10.5593/sgem2017h/63/s27.106.

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

Rusinaite, Toma, Diana Kalibatiene, and Olegas Vasilecas. "Requirements of dynamic business processes - a survey." In 2015 IEEE 3rd Workshop on Advances in Information, Electronic and Electrical Engineering (AIEEE). IEEE, 2015. http://dx.doi.org/10.1109/aieee.2015.7367312.

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

Yousuf, Farzana, Zahid Zaman, and Naveed Ikram. "Requirements validation techniques in GSD: A survey." In IEEE INMIC 2008. 12th IEEE International Multitopic Conference. IEEE, 2008. http://dx.doi.org/10.1109/inmic.2008.4777800.

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

Kadebu, Prudence, Vikas Thada, and Panashe Chiurunge. "Security Requirements Extraction and Classification: A Survey." In 2018 3rd International Conference on Contemporary Computing and Informatics (IC3I). IEEE, 2018. http://dx.doi.org/10.1109/ic3i44769.2018.9007263.

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

Liu, Lin, Tong Li, and Fei Peng. "Why Requirements Engineering Fails: A Survey Report from China." In 2010 IEEE 18th International Conference on Requirements Engineering (RE). IEEE, 2010. http://dx.doi.org/10.1109/re.2010.45.

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

Kienle, Holger M., and Hausi A. Muller. "Requirements of Software Visualization Tools: A Literature Survey." In 2007 4th IEEE International Workshop on Visualizing Software for Understanding and Analysis. IEEE, 2007. http://dx.doi.org/10.1109/vissof.2007.4290693.

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

Reports on the topic "Survey of requirements"

1

Ellis, J. R. Minimum release survey requirements. Office of Scientific and Technical Information (OSTI), September 1994. http://dx.doi.org/10.2172/10194740.

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

Nieminen, Timo. Efficacy requirements for drinking water disinfectants - survey and proposal. Nordic Council of Ministers, May 2020. http://dx.doi.org/10.6027/na2020-904.

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

Aylor, James, Robert Klenke, Ron Waxman, Paul Menchini, Jack Stinson, and Bill Anderson. VHSIC Hardware Description Language (VHDL) 200X Requirements Report/Survey. Fort Belvoir, VA: Defense Technical Information Center, November 1999. http://dx.doi.org/10.21236/ada406178.

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

Gittleman, Maury, Kristen Monaco, and Nicole Nestoriak. The Requirements of Jobs: Evidence from a Nationally Representative Survey. Cambridge, MA: National Bureau of Economic Research, May 2016. http://dx.doi.org/10.3386/w22218.

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

Terlip, Danny, Chris Ainscough, William Buttner, and Scott McWhorter. H2FIRST Hydrogen Contaminant Detector Task: Requirements Document and Market Survey. Office of Scientific and Technical Information (OSTI), April 2015. http://dx.doi.org/10.2172/1215206.

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

Cirinna, Chiara, and William Kilbride. Report on Survey of Training Material/Assessment of Digital Curation Requirements. APA / DPC, December 2012. http://dx.doi.org/10.7207/op12-01.

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

Petty, Mikel D., Ryland C. Gaskins, and Frederic D. McKenzie. Crowd Modeling in Military Simulations: Requirements Analysis, Survey, and Design Study. Fort Belvoir, VA: Defense Technical Information Center, April 2003. http://dx.doi.org/10.21236/ada474641.

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

Dashiell, William H., L. Arnold Johnson, and Lynne S. Rosenthal. Criteria for United States Geological Survey (USGS) recognizing testing laboratoryies functions and requirements:. Gaithersburg, MD: National Institute of Standards and Technology, 1998. http://dx.doi.org/10.6028/nist.ir.6128.

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

SYNETICS CORP EL CAJON CA. Survey and Analysis of Environmental Requirements for Shipboard Electronic Equipment Applications. Volume 1. Fort Belvoir, VA: Defense Technical Information Center, July 1991. http://dx.doi.org/10.21236/ada240171.

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

Fuchs, Heidi, and Prakash Rao. Survey of Available Information on U.S. Manufacturing Wastewater and Energy Requirements for Reuse. Office of Scientific and Technical Information (OSTI), June 2021. http://dx.doi.org/10.2172/1821428.

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