How do you use formal methods or standards to specify and verify system requirements?

由人工智能和领英社区提供技术支持

System requirements are the specifications and constraints that define what a system should do, how it should behave, and what qualities it should have. They are essential for designing, developing, testing, and maintaining a system that meets the needs and expectations of the stakeholders. But how do you use formal methods or standards to specify and verify system requirements? In this article, we will explain what formal methods and standards are, why they are useful, and how they can be applied in the system requirements process.

此文章中的业界达人

由社区从 9 条内容中精选。了解更多

Kai Tse

Digital Payments x Mobility | Product and Business Innovator

1 What are formal methods and standards?

Formal methods are rigorous and mathematical techniques that can be used to model, specify, analyze, and verify system requirements. They use formal languages, logic, and proofs to express and check the consistency, completeness, correctness, and feasibility of system requirements. Formal methods can help to avoid ambiguity, errors, and inconsistencies in system requirements, as well as to detect and resolve conflicts, gaps, and redundancies. Formal standards are established and widely accepted guidelines, rules, or criteria that define the best practices, processes, methods, and tools for specifying and verifying system requirements. They provide a common framework, terminology, and notation for communicating and documenting system requirements. Formal standards can help to ensure the quality, reliability, safety, security, and interoperability of system requirements, as well as to facilitate the verification, validation, and traceability of system requirements.

添加您的观点

Kemi Lewis

Getting Magic Done Practitioner | C-Suite Advisor | Systems Engineering Yoda| Chief Systems Engineer | IFEC Expert | Gracie Jiu-Jitsu Brown Belt
举报内容
Use formal methods like UML or SysML to precisely define system requirements. Apply industry standards such as IEEE 29148 for requirements specification. Employ formal verification techniques—model checking, theorem proving—to ensure requirements are consistent and complete. Keep documentation clear and unambiguous to avoid misinterpretation. Validate requirements through rigorous reviews and testing. Prioritize precision and rigor to eliminate errors early. Stay disciplined, use the right tools, and get it done.

已翻译

赞

2 Why use formal methods and standards?

Formal methods and standards for specifying and verifying system requirements can bring many advantages to system development and maintenance. These include improved clarity, precision, and completeness of system requirements, as well as reduced risk of errors, defects, and failures. Furthermore, formal methods can increase the confidence and trust in system requirements, ensure that they meet the expectations of stakeholders, support verification and validation of system requirements, and enable reuse and adaptation of system requirements. All of these benefits can lead to greater efficiency and effectiveness in system development and maintenance.

添加您的观点

Randall Satterthwaite, ESEP

MBSE Transformation Expert, System Modeler, MBSE Architect, & Product Owner
举报内容
Methods provides a repeatable assessment for the requirements and if implemented effectively, will allow for fair A/B comparisons between design decisions. Standards, while trying to be absolute, always have interpretation involved and are primarily used for regulatory compliance assessment and compatibility with other systems. Care needs to be taken with compatibility; compatibility with the standard does not mean compatibility with other systems conforming to the standard. Requirements for validation of compatibility are critical for this.

已翻译

赞
Kemi Lewis

Getting Magic Done Practitioner | C-Suite Advisor | Systems Engineering Yoda| Chief Systems Engineer | IFEC Expert | Gracie Jiu-Jitsu Brown Belt
举报内容
They ensure precise, unambiguous specifications and verifications, reducing the risk of errors or misinterpretations. These methods improve system safety, reliability, and compliance, particularly in high-risk sectors like aerospace, defense, and healthcare.

已翻译

赞

3 How to use formal methods and standards?

Using formal methods and standards to specify and verify system requirements requires a systematic and disciplined approach, which can be achieved by following some key steps. Firstly, identify the scope, purpose, and context of the system requirements. Define the stakeholders, goals, objectives, and assumptions of the system requirements. Secondly, select the appropriate formal methods and standards for the system requirements based on the type, complexity, and criticality of the system requirements, as well as the availability and suitability of the formal methods and standards. Thirdly, use the formal languages, logic, and proofs to model, specify, analyze, and verify the system requirements. Follow the formal standards to structure, format, and document the system requirements. Fourthly, review and refine the system requirements. Evaluate the quality, validity, and feasibility of the system requirements. Identify and resolve any issues or problems in the system requirements. Finally, manage and maintain the system requirements by keeping track of changes in dependencies or impacts of the system requirements. Update or revise as needed.

添加您的观点

Kemi Lewis

Getting Magic Done Practitioner | C-Suite Advisor | Systems Engineering Yoda| Chief Systems Engineer | IFEC Expert | Gracie Jiu-Jitsu Brown Belt
举报内容
Start by selecting the appropriate standards for your industry and system type. Use formal methods like model checking or theorem proving to specify requirements mathematically. Implement these alongside industry standards to ensure the system’s design and verification processes adhere to regulations. Trace requirements throughout design, development, and testing for alignment.

已翻译

赞

4 Examples of formal methods and standards

There are many formal methods and standards that can be used to specify and verify system requirements, such as Z, a formal language that uses mathematical notation and symbols to define data types, state variables, operations, and constraints; UML, a standard that uses graphical diagrams and symbols to model system requirements; IEEE 830, a standard that defines the format and content of a software requirements specification (SRS) document; and ISO/IEC 29148, a standard that defines the processes and activities for eliciting, analyzing, specifying, verifying, validating, and managing system requirements. Z allows for the analysis and verification of system requirements using logical reasoning and proofs. UML supports the verification and validation of system requirements using simulation and testing tools. IEEE 830 provides a template and guidelines for writing a clear, consistent, and complete SRS document as well as specifying the quality attributes and characteristics of a good SRS document. ISO/IEC 29148 provides a framework and best practices for performing the system requirements process as well as covering the roles and responsibilities of the system requirements stakeholders.

添加您的观点

Kemi Lewis

Getting Magic Done Practitioner | C-Suite Advisor | Systems Engineering Yoda| Chief Systems Engineer | IFEC Expert | Gracie Jiu-Jitsu Brown Belt
举报内容
Model checking, Z notation, and the B method are common formal methods. Standards like ISO 26262 (automotive), DO-178C (aerospace), and IEEE 830 (software requirements) provide frameworks to ensure your system is specified and verified accurately.

已翻译

赞

5 Tips and tricks for using formal methods and standards

Using formal methods and standards to specify and verify system requirements can be challenging and time-consuming, but there are some tips and tricks that can help. Plan ahead and allocate enough time and resources to use formal methods and standards, taking into account the learning curve, complexity, and effort involved. Consider using a combination of formal methods and standards that suit your needs, rather than relying on one single method or standard. Additionally, use tools and software that support formal methods and standards to create, edit, check, and document your system requirements. Finally, get feedback from other stakeholders by involving them in the process and collaborating with them using formal methods and standards.

添加您的观点

Kai Tse

Digital Payments x Mobility | Product and Business Innovator
举报内容
Keep verification in mind when writing your requirements. One easy question to ask yourself is "How would I know if I'd met this requirement?". Or more likely, "In 18 months time, what would I say to a tired and stressed test engineer when they came to me to ask how I expected them to prove that they'd met my requirement!" To do this, I write the requirement, and an indicative test case at the same time (or at least before I've finished with the requirement set). If I can't think of a sensible test to do, then it's probably not a testable requirement. That's not to say the intent of the requirement itself is wrong, but it just means that I've not written it such that it's testable. Write testable requirements!

已翻译

赞
John Terry

Senior Surfing Fellow, Senior Principle Back Country Hiker, and Midway Volunteer Docent
举报内容
In support of writing testable requirements write coherent and easy to understand requirements and avoid complexity ( or creative writing) where possible. Remember not only will somebody have to write a test plan based on the requirements, typically, multiple engineers from different disciplines will be reviewing.

已翻译

赞
Kemi Lewis

Getting Magic Done Practitioner | C-Suite Advisor | Systems Engineering Yoda| Chief Systems Engineer | IFEC Expert | Gracie Jiu-Jitsu Brown Belt
举报内容
Start with a clear understanding of the system scope and industry requirements. Collaborate with experts in formal methods for complex systems. Use automated tools to simplify verification and ensure compliance. Regularly review and update the specification as the system evolves.

已翻译

赞

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Kemi Lewis

Getting Magic Done Practitioner | C-Suite Advisor | Systems Engineering Yoda| Chief Systems Engineer | IFEC Expert | Gracie Jiu-Jitsu Brown Belt
举报内容
Balance between formal methods and practical implementation—formal methods are rigorous but can be time-consuming. Ensure that the methods and standards you use align with both project goals and stakeholder expectations, adapting them as needed for the system’s complexity and risk profile.

已翻译

赞

System Requirements

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

How do you use formal methods or standards to specify and verify system requirements?

1

2

3

4

5

6

1 What are formal methods and standards?

2 Why use formal methods and standards?

3 How to use formal methods and standards?

4 Examples of formal methods and standards

5 Tips and tricks for using formal methods and standards

6 Here’s what else to consider

System Requirements

给文章评分

感谢您的反馈

更多System Requirements相关文章

更多相关阅读内容