Log in

Relevant bibliographies by topics / Software requirements specification (SRS)

Contents

Journal articles
Dissertations / Theses
Books
Book chapters
Conference papers
Reports

Academic literature on the topic 'Software requirements specification (SRS)'

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 'Software requirements specification (SRS).'

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 "Software requirements specification (SRS)"

1

Et.al, Osman, M. H. "Ambi Detect: An Ambiguous Software Requirements Specification Detection Tool." Turkish Journal of Computer and Mathematics Education (TURCOMAT) 12, no. 3 (2021): 2023–28. http://dx.doi.org/10.17762/turcomat.v12i3.1066.

Full text

Abstract:

Software Requirements Specification (SRS) is considered a highly critical artifact in the software development. All phases in software development are influenced by this artifact. Defects in software requirements may higher the risk of project overschedule that contributes to cost overrun of the project.Researchers have shown that finding defects in the initial software development phase is important becausethe cost of the bug is cheaper if it is fixed early. Hence, our main goal is to provide a platform for requirement engineers to produce better requirement specifications. We propose AmbiDet

APA, Harvard, Vancouver, ISO, and other styles

2

Et.al, Naveen N. Kulkarni. "Tailoring effective requirement's specification for ingenuity in Software Development Life Cycle." Turkish Journal of Computer and Mathematics Education (TURCOMAT) 12, no. 3 (2021): 3338–44. http://dx.doi.org/10.17762/turcomat.v12i3.1590.

Full text

Abstract:

Software Requirements Engineering (SRE) process define software manuscripts with sustaining Software Requirement Specification (SRS) and its activities. SRE comprises many tasks requirement analysis, elicitation, documentation, conciliation and validation. Natural language is most popular and commonly used to form the SRS document. However, natural language has its own limitations wrt quality approach for SRS. The constraints include incomplete, incorrect, ambiguous, and inconsistency. In software engineering, most applications are object-oriented. So requirements are unlike problem domain nee

APA, Harvard, Vancouver, ISO, and other styles

3

Mahalakshmi, K., Udayakumar Allimuthu, L. Jayakumar, and Ankur Dumka. "A Timeline Optimization Approach of Green Requirement Engineering Framework for Efficient Categorized Natural Language Documents in Non-Functional Requirements." International Journal of Business Analytics 8, no. 1 (2021): 21–37. http://dx.doi.org/10.4018/ijban.2021010102.

Full text

Abstract:

The system's functional requirements (FR) and non-functional requirements (NFR) are derived from the software requirements specification (SRS). The requirement specification is challenging in classification process of FR and NFR requirements. To overcome these issues, the work contains various significant contributions towards SRS, such as green requirements engineering (GRE), to achieve the natural language processing, requirement specification, extraction, classification, requirement specification, feature selection, and testing the quality attributes improvement of NFRs. In addition to this

APA, Harvard, Vancouver, ISO, and other styles

4

Hayman Oo, Khin, Azlin Nordin, Amelia Ritahani Ismail, and Suriani Sulaiman. "An Analysis of Ambiguity Detection Techniques for Software Requirements Specification (SRS)." International Journal of Engineering & Technology 7, no. 2.29 (2018): 501. http://dx.doi.org/10.14419/ijet.v7i2.29.13808.

Full text

Abstract:

Ambiguity is the major problem in Software Requirements Specification (SRS) documents because most of the SRS documents are written in natural language and natural language is generally ambiguous. There are various types of techniques that have been used to detect ambiguity in SRS documents. Based on an analysis of the existing work, the ambiguity detection techniques can be categorized into three approaches: (1) manual approach, (2) semi-automatic approach using natural language processing, (3) semi-automatic approach using machine learning. Among them, one of the semi-automatic approaches th

APA, Harvard, Vancouver, ISO, and other styles

5

Haris, M. Syauqi, Tri Astoto Kurniawan, and Fatwa Ramdani. "Automated Features Extraction from Software Requirements Specification (SRS) Documents as The Basis of Software Product Line (SPL) Engineering." Journal of Information Technology and Computer Science 5, no. 3 (2020): 279. http://dx.doi.org/10.25126/jitecs.202053219.

Full text

Abstract:

Extractive Software Product Line Engineering (SPLE) puts features on the foremost aspect in domain analysis that needs to be extracted from the existing system's artifact. Feature in SPLE, which is closely related to system functionality, has been previously studied to be extracted from source code, models, and various text documents that exist along the software development process. Source code, with its concise and normative standard, has become the most focus target for feature extraction source on many kinds of research. However, in the software engineering principle, the Software Requirem

APA, Harvard, Vancouver, ISO, and other styles

6

Asif, Muhammad, Ishfaq Ali, Muhamad Sheraz Arshed Malik, Muhammad Hasanain Chaudary, Shahzadi Tayyaba, and Muhammad Tariq Mahmood. "Annotation of Software Requirements Specification (SRS), Extractions of Nonfunctional Requirements, and Measurement of Their Tradeoff." IEEE Access 7 (2019): 36164–76. http://dx.doi.org/10.1109/access.2019.2903133.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Sharma, Ashish, Manu Vardhan, and Dharmender Singh Kushwaha. "A Versatile Approach for the Estimation of Software Development Effort Based on SRS Document." International Journal of Software Engineering and Knowledge Engineering 24, no. 01 (2014): 1–42. http://dx.doi.org/10.1142/s0218194014500016.

Full text

Abstract:

Requirement engineering is a disciplined application of proven principles, methods, tools and notations to describe the behavior of a system. Generally a project suffers because of improper determination and documentation of software requirements. The intricacies in software development processes are often not understood by the client. Hence, requirements submitted by client need a careful examination. In order to produce proper artifact, it is necessary that the software requirements should be documented into the software requirement specification (SRS) on the basis of the recommendations of

APA, Harvard, Vancouver, ISO, and other styles

8

Mohanan, Murali, and Imran Sarwar Bajwa. "Requirements to Class Model via SBVR." International Journal of Open Source Software and Processes 10, no. 2 (2019): 70–87. http://dx.doi.org/10.4018/ijossp.2019040104.

Full text

Abstract:

A user's software requirements are represented in natural language or a speech such as English. Translating these requirements into the object-oriented models is a tough process for designers. This article proposes a neoteric approach to generate Unified Modeling Language (UML) class models instantly from software requirement specifications (SRS). Here the authors make use of the Open Natural language processing tool (OpenNLP) for lexical analysis and to generate the necessary parts of speech (POS) tags from these requirement specifications. Then, the Semantics of Business Vocabulary and Rules

APA, Harvard, Vancouver, ISO, and other styles

9

Ashfaq, Fariha, Imran Sarwar Bajwa, Rafaqut Kazmi, Akmal Khan, and Muhammad Ilyas. "An Intelligent Analytics Approach to Minimize Complexity in Ambiguous Software Requirements." Scientific Programming 2021 (March 22, 2021): 1–20. http://dx.doi.org/10.1155/2021/6616564.

Full text

Abstract:

An inconsistent and ambiguous Software Requirement Specification (SRS) document results in an erroneous/failed software project. Hence, it is a serious challenge to handle and process complex and ambiguous requirements. Most of the literature work focuses on detection and resolution of ambiguity in software requirements. Also, there is no standardized way to write unambiguous and consistent requirements. The goal of this research was to generate an ambiguity-less SRS document. This paper presents a new approach to write ambiguity-less requirements. Furthermore, we design a framework for Natura

APA, Harvard, Vancouver, ISO, and other styles

10

Dinata, Surya, and Martinus Raditia Sigit Surendra. "Penyusunan Kebutuhan Perangkat E-Banking dengan Pendekatan UI Analysis." Jurnal ULTIMA InfoSys 5, no. 2 (2014): 75–82. http://dx.doi.org/10.31937/si.v5i2.268.

Full text

Abstract:

This paper propose a method to collect software requirement (Software Requirement Specification – SRS) using user interface analysis on several running and stable system. In this paper we analyzed user interfaces of five internet banking system in Indonesia. The result are list of internet banking features. Then the features are categorized into three category, which are most important, important, and addiontal. Index Terms: Software Requirement Specification (SRS), Use case (UC), Internet banking, Reverse Engineering

APA, Harvard, Vancouver, ISO, and other styles

Dissertations / Theses on the topic "Software requirements specification (SRS)"

1

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 , r

APA, Harvard, Vancouver, ISO, and other styles

2

Chidambaram, Jeyashree. "Software reuse using formal specification of requirements." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1997. http://www.collectionscanada.ca/obj/s4/f2/dsk3/ftp04/mq23250.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Schneider, Gary David. "A requirements specification software cost estimation tool." Thesis, Kansas State University, 1986. http://hdl.handle.net/2097/9952.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Levin, Lukas, and Christoffer Stjernlöf. "Automated Testing Toolkit Service : Software Requirements Specification." Thesis, KTH, Skolan för informations- och kommunikationsteknik (ICT), 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-227859.

Full text

Abstract:

Frequent automated testing of software services is vital to speed up the development cycle and ensure upgrades do not break existing features. With a centralised testing service, it is also possible to catch errors at customer sites before they become severe enough that the customers (or in the end – regular people) start suffering from them. It also gives the customers an insight into how well their services are working at a predictable cost. When developing a larger software system such as an automated testing service toolkit, a requirements specification can drastically cut development cost

APA, Harvard, Vancouver, ISO, and other styles

5

Thongglin, Kanjana. "Controlled language for Thai software requirements specification." Thesis, Besançon, 2014. http://www.theses.fr/2014BESA1003.

Full text

Abstract:

Cette thèse porte sur l’utilisation d’une langue contrôlée pour les spécifications des besoins du logiciel en thaï. L’étudedécrit les ambiguïtés syntaxiques et sémantiques ainsi que les problèmes rencontrés dans les spécifications des besoins dulogiciel en thaï. Ce travail explique également la nature de la langue thaïe. Le modèle de la langue contrôlée pour lesspécifications des besoins du logiciel en thaï, proposé dans cette étude, comprend trois composantes: l’analyse lexicale,l’analyse syntaxique et l’analyse sémantique. Pour l’analyse syntaxique, une syntaxe contrôlée est conçue en utilis

APA, Harvard, Vancouver, ISO, and other styles

6

Au, Oliver T. S. "Requirements specification using concrete scenarios." Thesis, Loughborough University, 2009. https://dspace.lboro.ac.uk/2134/6642.

Full text

Abstract:

The precision of formal specifications allows us to prove program correctness. Even if formal methods are not used throughout the software project, formalisation improves our understanding of the problem. Formal specifications are amenable to automated analysis and consistency checking. However using them is challenging. Customers do not understand formal notations. Specifiers have difficulty tackling large problems. Once systems are built, formal specifications quickly become outdated during software maintenance. A method of developing formal specifications using concrete scenarios is propose

APA, Harvard, Vancouver, ISO, and other styles

7

Alderman, Robert Bruce. "Software requirements specification for an ammunition management system." Thesis, Monterey, California: U.S. Naval Postgraduate School, 1986. http://hdl.handle.net/10945/22109.

Full text

Abstract:

Approved for public release; distribution is unlimited.<br>This thesis concerns the software requirements necessary to automate the present manual effort associated with ammunition inventory management and reporting at the afloat end-user level. Functional characteristics for the application software are developed, program and data structures are proposed and possible sources of data are identified. The end-product of this research is the software requirements specification. This document supports further design development of the application software and is independent of programming language

APA, Harvard, Vancouver, ISO, and other styles

8

Knapp, James Robert. "Specification for Visual Requirements of Work-Centered Software Systems." Wright State University / OhioLINK, 2006. http://rave.ohiolink.edu/etdc/view?acc_num=wright1165518140.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

MEDEIROS, Juliana Dantas Ribeiro Viana de. "An approach to support the requirements specification in agile software development." Universidade Federal de Pernambuco, 2017. https://repositorio.ufpe.br/handle/123456789/25327.

Full text

Abstract:

SCHUENEMANN, Carla Taciana Lima Lourenco Silva, também é conhecida em citações bibliográficas por: SILVA, Carla<br>Submitted by Fernanda Rodrigues de Lima (fernanda.rlima@ufpe.br) on 2018-07-31T22:18:30Z No. of bitstreams: 2 license_rdf: 811 bytes, checksum: e39d27027a6cc9cb039ad269a5db8e34 (MD5) TESE Juliana Dantas Ribeiro Viana de Medeiros.pdf: 2161644 bytes, checksum: e9d1db641ca49230902d1d8963b8bb68 (MD5)<br>Approved for entry into archive by Alice Araujo (alice.caraujo@ufpe.br) on 2018-08-01T22:34:12Z (GMT) No. of bitstreams: 2 license_rdf: 811 bytes, checksum: e39d27027a6cc9cb039ad269a5d

APA, Harvard, Vancouver, ISO, and other styles

10

Silva, Araujo Joao Baptista da. "Metamorphosis : an integrated object oriented requirements analysis and specification method." Thesis, Lancaster University, 1996. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.337663.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Books on the topic "Software requirements specification (SRS)"

1

CSR Workshop (1984 University of East Anglia). Software: Requirements, specification and testing. Blackwell Scientific, 1985.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

2

Davis, Alan M. Software requirements: Analysis and specification. Prentice-Hall International, 1990.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

3

Software requirements: Analysis and specification. Prentice Hall, 1990.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

4

Requirements modelling and specification for service oriented architecture. Wiley, 2008.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

5

Butler, Ricky W. An introduction to requirements capture using PVS: Specification of a simple autopilot. National Aeronautics and Space Administration, Langley Research Center, 1996.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

6

O, Salas A., and Langley Research Center, eds. HSCT4.0 application: Software requirements specification. National Aeronautics and Space Administration, Langley Research Center, 2001.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

7

O, Salas A., and Langley Research Center, eds. HSCT4.0 application: Software requirements specification. National Aeronautics and Space Administration, Langley Research Center, 2001.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

8

Davis, Alan M. Software Requirements Analysis and Specification. Prentice Hall (Higher Education Division, Pearson Education), 1991.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

9

HSCT4.0 application: Software requirements specification. National Aeronautics and Space Administration, Langley Research Center, 2001.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

10

O, Salas A., and Langley Research Center, eds. HSCT4.0 application: Software requirements specification. National Aeronautics and Space Administration, Langley Research Center, 2001.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

Book chapters on the topic "Software requirements specification (SRS)"

1

Ismail, Muhammad. "Ontology Learning from Software Requirements Specification (SRS)." In Lecture Notes in Computer Science. Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-58694-6_39.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Foster, Elvis C. "The Requirements Specification." In Software Engineering. Apress, 2014. http://dx.doi.org/10.1007/978-1-4842-0847-2_4.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Foster, Elvis C. "The Requirements Specification." In Software Engineering, 2nd ed. Auerbach Publications, 2021. http://dx.doi.org/10.1201/9780367746025-8.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Jalote, Pankaj. "Software Requirements Specification." In Springer Compass International. Springer New York, 1991. http://dx.doi.org/10.1007/978-1-4757-3857-5_2.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

Wieringa, Roel J. "Requirements Specification." In Design Science Methodology for Information Systems and Software Engineering. Springer Berlin Heidelberg, 2014. http://dx.doi.org/10.1007/978-3-662-43839-8_6.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Berry, Daniel M., and Erik Kamsties. "Ambiguity in Requirements Specification." In Perspectives on Software Requirements. Springer US, 2004. http://dx.doi.org/10.1007/978-1-4615-0465-8_2.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Jalote, Pankaj. "Software Requirements Analysis and Specification." In An Integrated Approach to Software Engineering. Springer New York, 1997. http://dx.doi.org/10.1007/978-1-4684-9312-2_3.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Jalote, Pankaj. "Software Requirements Analysis and Specification." In A Concise Introduction to Software Engineering. Springer London, 2008. http://dx.doi.org/10.1007/978-1-84800-302-6_3.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Foster, Elvis C. "Requirements Specification for a Generic Inventory Management System." In Software Engineering. Apress, 2014. http://dx.doi.org/10.1007/978-1-4842-0847-2_29.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Cooling, J. E. "First steps — requirements analysis and specification." In Software Design for Real-time Systems. Springer US, 1991. http://dx.doi.org/10.1007/978-1-4899-2957-0_3.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software requirements specification (SRS)"

1

Aman, Hannani, and Rosziati Ibrahim. "XML_DocTracker: Generating Software Requirements Specification (SRS) from XML Schema." In 2016 International Conference on Information Science and Security (ICISS). IEEE, 2016. http://dx.doi.org/10.1109/icissec.2016.7885872.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Georgiades, Marinos G., and Andreas S. Andreou. "Automatic generation of a Software Requirements Specification (SRS) document." In 2010 10th International Conference on Intelligent Systems Design and Applications (ISDA). IEEE, 2010. http://dx.doi.org/10.1109/isda.2010.5687039.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

"A SOFTWARE TOOL FOR REQUIREMENTS SPECIFICATION - On using the STORM Environment to Create SRS Documents." In 2nd International Conference on Software and Data Technologies. SciTePress - Science and and Technology Publications, 2007. http://dx.doi.org/10.5220/0001345303190326.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Nur Fathin Najwa Binti Mustaffa, Siti, Jamaludin Bin Sallim, and Rozlina Binti Mohamed. "Semi – Automated Software Requirement Specification (SRS) Document Generator: The Guideline to Novice System Analyst." In 2021 International Conference on Software Engineering & Computer Systems and 4th International Conference on Computational Science and Information Management (ICSECS-ICOCSIM). IEEE, 2021. http://dx.doi.org/10.1109/icsecs52883.2021.00022.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

Rocha, Fabiana Ferreira, Elisa Cerri E Cerri, Ricardo Melo Bastos, and Marcelo Hideki Yamaguti. "Uma Proposta de Modelo para Avaliação da Qualidade da Tradução de Requisitos para Casos de Uso." In III Simpósio Brasileiro de Sistemas de Informação. Sociedade Brasileira de Computação, 2006. http://dx.doi.org/10.5753/sbsi.2006.14721.

Full text

Abstract:

O documento de especificação de requisitos de software (Software Requirements Specification - SRS) é decisivo para o desenvolvimento de um bom produto final. As métricas desempenham um papel essencial na detecção de defeitos dos requisitos, fornecendo meios para a visualização de discrepâncias e identificação de pontos fora de uma situação projetada. Assim, o objetivo deste trabalho é propor um modelo com a finalidade de avaliar a qualidade da tradução de requisitos para casos de uso.

APA, Harvard, Vancouver, ISO, and other styles

6

Vilela, Jéssyka. "An Empirical Evaluation about Using Models to Improve Preliminary Safety Analysis." In Workshop em Modelagem e Simulação de Sistemas Intensivos em Software. Sociedade Brasileira de Computação - SBC, 2020. http://dx.doi.org/10.5753/mssis.2020.12496.

Full text

Abstract:

Context: Safety analysis is an activity of fundamental importance in the development of safety-critical systems (SCS) to ensure that hazardous situations are properly found and mitigated. Such analysis is usually performed after a system requirements specification is available. Therefore, it is then worthwhile to investigate specification techniques to detect their strengths and weaknesses with respect to finding and documenting hazards early in the development process. Objective: In this paper, we investigate similarities and differences in the results of a preliminary safety analysis from re

APA, Harvard, Vancouver, ISO, and other styles

7

Awan, Misbah Mehboob, Farooque Azam, Muhammad Waseem Anwar, and Yawar Rasheed. "Formal Requirements Specification." In ICSIE 2020: 2020 9th International Conference on Software and Information Engineering. ACM, 2020. http://dx.doi.org/10.1145/3436829.3436845.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Thongglin, Kanjana, Sylviane Cardey, and Peter Greenfield. "Thai software requirements specification pattern." In 2013 IEEE 12th International Conference on Intelligent Software Methodologies, Tools and Techniques (SoMeT). IEEE, 2013. http://dx.doi.org/10.1109/somet.2013.6645650.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Šenkýř, David, and Petr Kroha. "Patterns in Textual Requirements Specification." In 13th International Conference on Software Technologies. SCITEPRESS - Science and Technology Publications, 2018. http://dx.doi.org/10.5220/0006827301970204.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Šenkýř, David, and Petr Kroha. "Patterns in Textual Requirements Specification." In 13th International Conference on Software Technologies. SCITEPRESS - Science and Technology Publications, 2018. http://dx.doi.org/10.5220/0006827302310238.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Software requirements specification (SRS)"

1

Glasscock, J. A., and M. J. Flanagan. Surveillance Analysis Computer System (SACS) software requirements specification (SRS). Office of Scientific and Technical Information (OSTI), 1995. http://dx.doi.org/10.2172/436527.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Glasscock, J. A. Surveillance Analysis Computer System (SACS): Software requirements specification (SRS). Revision 2. Office of Scientific and Technical Information (OSTI), 1995. http://dx.doi.org/10.2172/33085.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Clark, R. E. Solid Waste Information Tracking System (SWITS), Backlog Waste Modifications, Software Requirements Specification (SRS). Office of Scientific and Technical Information (OSTI), 1995. http://dx.doi.org/10.2172/67204.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Gneiting, B. C. RMACS software requirements specification. Office of Scientific and Technical Information (OSTI), 1996. http://dx.doi.org/10.2172/331653.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

Frank, D. D. Requirements management system browser software requirements specification. Office of Scientific and Technical Information (OSTI), 1996. http://dx.doi.org/10.2172/331654.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Zhang, Hongbin, David Andrs, Richard Martineau, Nancy Kyle, Hollis Henry, and Stella McKirdy. Software Requirements Specification for RELAP-7. Office of Scientific and Technical Information (OSTI), 2017. http://dx.doi.org/10.2172/1374509.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Grush, W. H., and E. S. Marwil. In Situ Vitrification software requirements specification. Office of Scientific and Technical Information (OSTI), 1990. http://dx.doi.org/10.2172/6496101.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Vargo, G. F., and M. Gimera. Software requirements specification of low moisture monitor. Office of Scientific and Technical Information (OSTI), 1995. http://dx.doi.org/10.2172/442532.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Gimera, M. Software requirements specification for surface moisture monitor. Office of Scientific and Technical Information (OSTI), 1995. http://dx.doi.org/10.2172/443105.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Sisk, Daniel R., Michael R. Brambley, Teresa A. Carlon, and Robert S. Briggs. Automated Diagnostics Software Requirements Specification, Version 1.1. Office of Scientific and Technical Information (OSTI), 2003. http://dx.doi.org/10.2172/15010305.

Full text

APA, Harvard, Vancouver, ISO, and other styles

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!