Relevant bibliographies by topics / Formal requirements

Contents

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

Academic literature on the topic 'Formal requirements'

Author: Grafiati
Published: 4 June 2021
Last updated: 25 April 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 'Formal 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 "Formal requirements"

1

Gebreyohannes, Solomon, William Edmonson, and Albert Esterline. "Formal Behavioral Requirements Management." IEEE Systems Journal 12, no. 3 (September 2018): 3006–17. http://dx.doi.org/10.1109/jsyst.2017.2775740.

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

Defossez, Francois. "A Formal Model of Requirements." Open Transportation Journal 5, no. 1 (October 6, 2011): 60–70. http://dx.doi.org/10.2174/1874447801105010060.

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

Paech, Barbara. "Formal user-centered requirements engineering." ACM SIGCHI Bulletin 29, no. 1 (January 1997): 54–55. http://dx.doi.org/10.1145/251761.248502.

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

Hussak, Walter, and John A. Keane. "Formal Analysis of Memory Requirements." Requirements Engineering 4, no. 4 (December 1, 1999): 188–97. http://dx.doi.org/10.1007/s007660050019.

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

Yen, John, and W. Amos Tiao. "A Formal Methodology for Analyzing Tradeoffs of Imprecise Requirements." International Journal of Software Engineering and Knowledge Engineering 08, no. 02 (June 1998): 283–311. http://dx.doi.org/10.1142/s0218194098000157.

Full text
Abstract:
Conflict identification and resolution are inevitable parts of the requirement analysis process. Over the past few years, the need to deal with conflicting system requirements has become increasingly important. These requirements are often elastic in that they can be satisfied to a degree. The overall goal of this research is to develop a formal methodology that facilitates the identification and tradeoff analysis of conflicting requirements by explicitly capturing their elasticity. In order to capture the elasticity of imprecise requirements, we represent imprecise requirements using fuzzy logic. Based on the representation, we build a formal foundation to facilitate the identification of conflicting requirements. Once the conflicting requirements are identified, we describe a systematic approach for analyzing the tradeoff between conflicting requirements using the techniques in decision science. The systematic tradeoff analyses are used for three important tasks in the requirement engineering process: (1) for validating the structure used in aggregating prioritized requirements, (2) for assisting requirement engineers in identifying the structures and the parameters of the underlying representation of imprecise requirements and in eliciting them from the customer, and (3) for assessing the priorities of conflicting requirements. We illustrate the usage of these techniques using the requirements of a conference room scheduling system.
APA, Harvard, Vancouver, ISO, and other styles
6

Amoroso, Edward G. "Creating formal specifications from requirements documents." ACM SIGSOFT Software Engineering Notes 20, no. 1 (January 1995): 67–70. http://dx.doi.org/10.1145/225907.225915.

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

Johnson, W. L., K. M. Benner, and D. R. Harris. "Developing formal specifications from informal requirements." IEEE Expert 8, no. 4 (August 1993): 82–90. http://dx.doi.org/10.1109/64.223994.

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

Lawrence, B., and D. Jackson. "Do you really need formal requirements?" IEEE Software 13, no. 2 (March 1996): 20. http://dx.doi.org/10.1109/52.506459.

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

Kampfner, Roberto R. "Formal specification of information systems requirements." Information Processing & Management 21, no. 5 (1985): 401–14. http://dx.doi.org/10.1016/0306-4573(85)90086-x.

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

Liu, Xiao Jian, Zhi Xue Wang, Xu Qin Yan, Yang Li, and Jian Xin Li. "Formal Modeling of Automotive Software Requirements by Correctness." Applied Mechanics and Materials 40-41 (November 2010): 961–67. http://dx.doi.org/10.4028/www.scientific.net/amm.40-41.961.

Full text
Abstract:
Correctly modeling software requirements is one of the grand challenges of current ECU (Electronic control Unit) development. To ensure the correctness of the requirements, formal modeling techniques are usually used because they allow analyzers to simulate, verify and even conduct performance analysis in the requirement level. In this paper, we propose a requirements modeling framework, based on the philosophy of separation of concerns and the formal modeling techniques. The main contributions of this paper are two-fold: (1) We divide a complicated automotive software as several concerns, each of which is modeled by different formal techniques, thus the descriptive complexity of the requirements is decreased, and accordingly the models’ understandability is enhanced; (2) The adoption of formal techniques allows us to simulate the execution of the software and calculate the performance in the early stage of development, therefore the correctness of requirements can be improved.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Formal requirements"

1

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
2

Fuxman, Ariel Damián. "Formal analysis of early requirements specifications." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 2001. http://www.collectionscanada.ca/obj/s4/f2/dsk3/ftp05/MQ62963.pdf.

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

Olthuis, Jorrit. "Verification of Formal Requirements through Tracing." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-289947.

Full text
Abstract:
Software development in the railway application is governed by strict standards which aim to ensure safety. It is for example highly recommended to use formal methods when specifying requirements. Moreover, it is mandatory to have certain roles be fulfilled by different people. A common technique is developing software tests for the requirements. Making sure that software requirements are properly described, interpreted and implemented by different people is a major challenge. Tests fully depend on the tester to cover all scenarios. Having more methods that simplify requirement tracing and that depends less on thoroughness of the tester would provide many benefits. This thesis investigates whether and how software tracing can be used to validate formal requirements of software. The goal is to perform trace validation such that it can be used to complement more traditional verification techniques. By verifying formal requirements on traces, the detection of errors depends on the events in the traces. As a consequence, more traces provide a higher chance of detecting errors. Thereby eliminating risk of the tester missing important cases. The presented verification approach firstly specifies requirements in linear temporal logic and converts this specification to a non-deterministic Büchi automaton, or a finite state machine which is also evaluated. Secondly, the approach describes several alternatives for collecting traces and how to link those to the formal specification. Lastly, the verification approach proposes an algorithm which takes the Büchi automaton and a trace to detect violations of the requirement. The validation approach is implemented in form of multiple tools and its operation shown by means of a toy example. This example models a railway application such that its requirements can be verified using the tools. The results are then used to show how these tools can be used in an actual railway application. Using these research outcomes, and the stand-alone tool, an implementation in Trace Compass is created. This can, just like the stand-alone tool, decide for each pair of trace and requirement whether the trace violates the requirement.
Programvaruutveckling i järnvägsapplikationen styrs av strikta standarder som syftar till att säkerställa säkerheten. Det rekommenderas till exempel starkt att använda formella metoder när krav anges. Dessutom är det obligatoriskt att vissa roller uppfylls av olika ingenjörer. En vanlig teknik är att utveckla programvarutest för kraven. Det är en stor utmaning att se till att programvarukrav beskrivs, tolkas och implementeras på rätt sätt av olika ingenjörer. Tester beror helt på testaren för att täcka alla scenarier. Att ha fler metoder som förenklar spårning av krav och som beror mindre på testarens noggrannhet skulle ge många fördelar. Denna avhandling undersöker om och hur spårning av programvara (software tracing) kan användas för att värdera formella krav på programvara. Målet är att utföra spårningsvalidering så att den kan användas för att komplettera mer traditionella verifieringstekniker. Genom att verifiera formella krav på spår (trace) beror upptäckten av fel på händelserna i spåren. Som en konsekvens ger fler spår större möjlighet för att detektera fel. Därmed elimineras risken för att testaren missar viktiga fall. Den presenterade verifieringsmetoden specificerar först kraven i linear temporal logic och omvandlar denna specifikation till en icke-deterministisk Büchi-automat, eller en ändlig tillståndsautomat som också utvärderas. För det andra beskriver tillvägagångssättet flera alternativ för att samla in spår och hur man länkar dem till den formella specifikationen. Slutligen föreslår verifieringsmetoden en algoritm som tar Büchi-automaten och ett spår för att upptäcka överträdelser av kravet. Valideringsmetoden implementeras i form av flera verktyg och dess funktion visas med hjälp av ett leksaksexempel. Detta exempel modellerar en järnvägsapplikation så att dess krav kan verifieras med verktygen. Resultaten används sedan för att visa hur dessa verktyg kan användas i en verklig järnvägsapplikation. Med hjälp av dessa forskningsresultat och det fristående verktyget skapas en implementering i Trace Compass. Detta kan, precis som det fristående verktyget, avgöra för varje par av spår och krav om spårningen bryter mot kravet.
APA, Harvard, Vancouver, ISO, and other styles
4

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
5

Subramanian, Senthil K. "Object-oriented program testing using formal requirements specification." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1997. http://www.collectionscanada.ca/obj/s4/f2/dsk2/ftp04/mq23517.pdf.

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

Tilley, Thomas. "Formal concept analysis applications to requirements engineering and design /." [St. Lucia, Qld.], 2003. http://adt.library.uq.edu.au/public/adt-QU20050223.204947/index.html.

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

Piveropoulos, Marios. "Requirements engineering for hard real-time systems." Thesis, University of York, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.310980.

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

Lai, Danny Cho-Liang 1978. "Extending a formal specification & requirements language : a case study." Thesis, Massachusetts Institute of Technology, 2001. http://hdl.handle.net/1721.1/86814.

Full text
Abstract:
Thesis (M.Eng.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2001.
Includes bibliographical references (leaves 92-93).
by Danny Cho-Liang Lai.
M.Eng.
APA, Harvard, Vancouver, ISO, and other styles
9

Pino, Lou. "A formal method for modeling and analysis of requirements for software /." Thesis, McGill University, 1993. http://digitool.Library.McGill.CA:80/R/?func=dbin-jump-full&object_id=69740.

Full text
Abstract:
Requirements that are well understood by a client and a provider are a major contributor to developing and supporting reliable, quality software on time and within budget. This thesis has two thrusts to facilitate improved interpretation of requirements: (1) a requirements model and (2) a new formalism called LaP, with automated tools, to express and analyze requirements. The new formalism is based on the integration of an algebraic based language, Larch, and an extended finite state machine based language, Promela. Larch comes with a theorem prover (Larch Prover) and Promela comes with a tool (SPIN) to aid in the validation of dynamic properties. It is the objective of LaP to express the control and data intensive aspects of requirements. The two thrusts are demonstrated by building a requirements model for real telecommunications requirements that ask for a system that can manage the access configurations of user's accounts in telecommunications equipment.
APA, Harvard, Vancouver, ISO, and other styles
10

Bittner, Margot. "Enhancing the fusion method to fusionB requirements engineering and formal specification /." [S.l.] : [s.n.], 2005. http://deposit.ddb.de/cgi-bin/dokserv?idn=980229839.

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

Books on the topic "Formal requirements"

1

Fuxman, Ariel Damian. Formal analysis of early requirements specifications. Ottawa: National Library of Canada, 2001.

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

Systems engineering and architecting: Creating formal requirements. boca Raton, FL: CRC Press, 2012.

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

Owens, Dermot. A comparison of formal and informal requirements specification methods. [s.l: The Author], 1993.

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

Shaikh, Shazib E. E-business process negotiation: Formal requirements for strategy support. Lahore: Centre for Management and Economic Research, Lahore University of Management Sciences, 2007.

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

Thomas, Alan M. The utilization of prior learning assessment as a basis for admission and the establishment of advanced standing in education in Canada. [Toronto: Ontario Institute for Studies in Education?], 1989.

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

Vito, Ben L. Di. Using formal methods to assist in the requirements analysis of the space shuttle GPS change request. Hampton, Va: National Aeronautics and Space Administration, Langley Research Center, 1996.

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

Barbara, Paech, and Martell Craig, eds. Innovations for requirements analysis: From stakeholders' needs to formal designs : 14th Monterey Workshop 2007, Monterey, CA, USA, September 10-13, 2007 : revised selected papers. Berlin: Springer, 2008.

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

Monterey Workshop (14th 2007 Monterey, Calif.). Innovations for requirements analysis: From stakeholders' needs to formal designs : 14th Monterey Workshop 2007, Monterey, CA, USA, September 10-13, 2007 : revised selected papers. Berlin: Springer, 2008.

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

Monterey Workshop (14th 2007 Monterey, Calif.). Innovations for requirements analysis: From stakeholders' needs to formal designs : 14th Monterey Workshop 2007, Monterey, CA, USA, September 10-13, 2007 : revised selected papers. Berlin: Springer, 2008.

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

Monterey Workshop (14th 2007 Monterey, Calif.). Innovations for requirements analysis: From stakeholders' needs to formal designs : 14th Monterey Workshop 2007, Monterey, CA, USA, September 10-13, 2007 : revised selected papers. Berlin: Springer, 2008.

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

Book chapters on the topic "Formal requirements"

1

Laplante, Phillip A., and Mohamad H. Kassab. "Formal Methods." In Requirements Engineering for Software and Systems, 167–94. 4th ed. New York: Auerbach Publications, 2022. http://dx.doi.org/10.1201/9781003129509-7.

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

Wieringa, Roel, Eric Dubois, and Sander Huyts. "Integrating semi-formal and formal requirements." In Notes on Numerical Fluid Mechanics and Multidisciplinary Design, 19–32. Cham: Springer International Publishing, 1997. http://dx.doi.org/10.1007/3-540-63107-0_2.

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

Hagelstein, J., D. Roelants, and P. Wodon. "Formal requirements made practical." In Lecture Notes in Computer Science, 127–44. Berlin, Heidelberg: Springer Berlin Heidelberg, 1993. http://dx.doi.org/10.1007/3-540-57209-0_10.

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

Smith, David J. "Formal methods in requirements." In Achieving Quality Software, 90–102. Dordrecht: Springer Netherlands, 1995. http://dx.doi.org/10.1007/978-94-011-0549-1_8.

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

Jureta, Ivan. "Links to Formal Logic." In The Design of Requirements Modelling Languages, 267–74. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-18821-8_15.

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

Luqi. "Formal Models and Prototyping." In Requirements Targeting Software and Systems Engineering, 257–72. Berlin, Heidelberg: Springer Berlin Heidelberg, 1998. http://dx.doi.org/10.1007/10692867_12.

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

Hagelstein, J., and F. Ponsaert. "Introducing formal requirements into industry." In Algebraic Methods II: Theory, Tools and Applications, 125–41. Berlin, Heidelberg: Springer Berlin Heidelberg, 1991. http://dx.doi.org/10.1007/3-540-53912-3_21.

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

Somenzi, Fabio, and Ashutosh Trivedi. "Reinforcement Learning and Formal Requirements." In Numerical Software Verification, 26–41. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-28423-7_2.

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

Muñoz, César, Anthony Narkawicz, and Aaron Dutle. "From Formal Requirements to Highly Assured Software for Unmanned Aircraft Systems." In Formal Methods, 647–52. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-95582-7_38.

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

Berger, Philipp, Johanna Nellen, Joost-Pieter Katoen, Erika Ábrahám, Md Tawhid Bin Waez, and Thomas Rambow. "Multiple Analyses, Requirements Once:." In Formal Methods for Industrial Critical Systems, 59–75. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-27008-7_4.

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

Conference papers on the topic "Formal requirements"

1

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. New York, NY, USA: ACM, 2020. http://dx.doi.org/10.1145/3436829.3436845.

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

Pill, I., S. Semprini, R. Cavada, M. Roveri, R. Bloem, and A. Cimatti. "Formal analysis of hardware requirements." In the 43rd annual conference. New York, New York, USA: ACM Press, 2006. http://dx.doi.org/10.1145/1146909.1147119.

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

Pill, I., S. Semprini, R. Cavada, M. Rovers, R. Bloem, and A. Cimatti. "Formal analysis of hardware requirements." In 2006 Design Automation Conference. IEEE, 2006. http://dx.doi.org/10.1109/dac.2006.229231.

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

Dietsch, Daniel, Vincent Langenfeld, and Bernd Westphal. "Formal Requirements in an Informal World." In 2020 IEEE Workshop on Formal Requirements (FORMREQ). IEEE, 2020. http://dx.doi.org/10.1109/formreq51202.2020.00010.

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

Schopp, Ulrich, Andreas Schweiger, Marina Reich, Tatiana Chuprina, Levi Lucio, and Hartmut Bruning. "Requirements-based Code Model Checking." In 2020 IEEE Workshop on Formal Requirements (FORMREQ). IEEE, 2020. http://dx.doi.org/10.1109/formreq51202.2020.00011.

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

Sayar, Imen, and Jeanine Souquieres. "Formalization of Requirements for Correct Systems." In 2020 IEEE Workshop on Formal Requirements (FORMREQ). IEEE, 2020. http://dx.doi.org/10.1109/formreq51202.2020.00012.

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

Ilic, Duvravka. "Deriving Formal Specifications from Informal Requirements." In 31st Annual International Computer Software and Applications Conference - Vol. 1- (COMPSAC 2007). IEEE, 2007. http://dx.doi.org/10.1109/compsac.2007.104.

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

"Title Page i." In 2020 IEEE Workshop on Formal Requirements (FORMREQ). IEEE, 2020. http://dx.doi.org/10.1109/formreq51202.2020.00001.

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

"Title Page iiii." In 2020 IEEE Workshop on Formal Requirements (FORMREQ). IEEE, 2020. http://dx.doi.org/10.1109/formreq51202.2020.00002.

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

"[Copyright notice]." In 2020 IEEE Workshop on Formal Requirements (FORMREQ). IEEE, 2020. http://dx.doi.org/10.1109/formreq51202.2020.00003.

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

Reports on the topic "Formal requirements"

1

Syverson, Paul, and Catherine Meadows. Formal Requirements for Key Distribution Protocols. Fort Belvoir, VA: Defense Technical Information Center, January 1994. http://dx.doi.org/10.21236/ada463018.

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

Syverson, Paul, and Catherine Meadows. A Formal Language for Cryptographic Protocol Requirements. Fort Belvoir, VA: Defense Technical Information Center, January 1996. http://dx.doi.org/10.21236/ada465327.

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

Drusinsky, Doron. Computer-Aided Discovery of Formal Specification Behavioral Requirements and Requirement to Implementation Mappings. Fort Belvoir, VA: Defense Technical Information Center, January 2014. http://dx.doi.org/10.21236/ada596790.

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

Lee, Insup. Extracting Formal Models from Informal Requirements and Using Them for Validation. Fort Belvoir, VA: Defense Technical Information Center, January 2009. http://dx.doi.org/10.21236/ada499764.

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

Meadows, Catherine. What Makes a Cryptographic Protocol Secure? The Evolution of Requirements Specification in Formal Cryptographic Protocol Analysis. Fort Belvoir, VA: Defense Technical Information Center, January 2003. http://dx.doi.org/10.21236/ada463937.

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

Rivera, Romel. A Prototyping Metalanguage with Formal Semantics for the Xinotech Program Composer. Phase 1. Task 1. Definition of the Requirements and Objectives for the Design of the Metalanguage XML. Task 3. Definition of the Requirements and Objectives for the Design of the Semantic Notation XSSL. Fort Belvoir, VA: Defense Technical Information Center, October 1989. http://dx.doi.org/10.21236/ada214081.

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

O'Donnell, Kevin, and Anne Greene. A Risk Management Solution Designed to Facilitate Risk-Based Qualification, Validation, and Change Control Activities within GMP and Pharmaceutical Regulatory Compliance Environments in the EU—Part II. Institute of Validation Technology, July 2006. http://dx.doi.org/10.1080/21506590.wp7142006agko-rmsdii.

Full text
Abstract:
highlight the need for patient-focused and value-adding qualification, validation, and change control programmes for manufacturing and regulating medicinal products in the EU, which are cost-effective and in-line with current regulatory requirements and guidance. To this end, a formal risk management solution was presented that seeks to demonstrate, in a practical way, how Regulators and Industry in the EU may achieve these goals. This solution represents a formal and rigorous approach to risk management, offering a scientific and practical means for determining and managing, on a risk basis, the scope and extent of qualification and validation, and the likely impact of changes. Based on a ten-step, systematic process, this approach offers a ready-to-use and documented risk management methodology for these activities. This tool is not intended for use in all situations, or to address all risk areas or concerns encountered in GMP and Regulatory Compliance environments. Rather, its use should be commensurate with the complexity and/or criticality of the issue to be addressed, and in many instances, and in-line with ICH Q9 principles, a more informal approach to risk management may be more useful, and indeed proportionate.
APA, Harvard, Vancouver, ISO, and other styles
8

Flanagan, H., and N. Brownlee. RFC Series Format Requirements and Future Development. RFC Editor, May 2013. http://dx.doi.org/10.17487/rfc6949.

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

Arvidsson, J., A. Cormack, Y. Demchenko, and J. Meijer. TERENA'S Incident Object Description and Exchange Format Requirements. RFC Editor, February 2001. http://dx.doi.org/10.17487/rfc3067.

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

Brown, D. Format requirements of thermal neutron scattering data in a nuclear data format to succeed the ENDF format. Office of Scientific and Technical Information (OSTI), March 2014. http://dx.doi.org/10.2172/1183267.

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