• Twitter
  • LinkedIn
  • Xing
+49 7353 981781
Heicon Ulm
  • HOME
  • COMPANY
  • PRODUCTS
  • HEICON BLOG
  • English
    • English
  • Menu Menu
You are here: Home1 / IEC61508 Verification

Tag Archive for: IEC61508 Verification

Specification Architecture Requirement in IEC 61508; Is there any difference?

FuSa_Industrial

Specification Architecture Requirement : For an increasing number of systems in the industrial automation functional safety requirements must be fulfilled. The IEC 61508 compliance must be demonstrated for the software development.
On the other hand, there are commercial requirements which often severely limit the product development budget.
The solution lies in an efficient development process that meets the safety-relevant requirements. A prerequisite for a successful implementation of such a process is a deep understanding of the standard and a clear definition of used terms. In the following blog, I discuss the three terms Specification Architecture Requirement.
Read more

22. December 2016/1 Comment/by HEICON Global Engineering GmbH
https://heicon-ulm.de/wp-content/uploads/2019/12/DI1A6149_klein_Industry.jpg 446 548 HEICON Global Engineering GmbH https://heicon-ulm.de/wp-content/uploads/2020/07/heicon-logo-5.png HEICON Global Engineering GmbH2016-12-22 00:36:092021-01-04 22:25:21Specification Architecture Requirement in IEC 61508; Is there any difference?

How many level of Software requirements are necessary and useful?

A_Requirement Engineering

In my daily projects in the automotive and industrial automation industry I’m continually confronted with the following question: How many levels of software requirements have to be written? That’s an interesting question, especially if we take the aerospace industry also into account. Software requirement level are a key topic if you want to improve your requirement engineering process. Therefore, I want to highlight in this blog post this topic a bit closer. I will compare the specifications of functional safety standards IEC 61508, ISO 26262 and DO-178B / C. In the final conclusion I will provide project best practices based on my more than 15 years of experience.

In my view, a good software specification is divided into two major parts: architecture / design and textual requirements.
The architecture describes, most predominantly in graphical form, the structure and design of the software. In particular, the data and control flows are shown. The focus of textual requirements is on the description of the functionality, and the time demands on the system.
The initial question of this blog refers to the number of levels of textual requirements. Not included is the level of system requirements, which must always be present. Read more

30. May 2016/0 Comments/by HEICON Global Engineering GmbH
https://heicon-ulm.de/wp-content/uploads/2020/08/DI1A6236_klein_Requirement_Eng.jpg 475 684 HEICON Global Engineering GmbH https://heicon-ulm.de/wp-content/uploads/2020/07/heicon-logo-5.png HEICON Global Engineering GmbH2016-05-30 18:18:362021-02-02 21:56:39How many level of Software requirements are necessary and useful?

Categories

  • A_Requirement Engineering
  • B_Validation and Verification
  • C_Config- / Change Management
  • D_Security
  • FuSa__General
  • FuSa_Aerospace
  • FuSa_Agriculture
  • FuSa_Automotive
  • FuSa_Industrial
  • FuSa_Railway

Contact

HEICON Global Engineering GmbH
Dipl. Ing. (FH) Martin Heininger
Kreuzweg 22
88477 Schwendi

Phone: +49 7353 – 98 17 81
Mobile: +49 176 – 24 73 99 60

Email: info[at]heicon-ulm.de

IMPRINT  |  DATA PROTECTION

Scroll to top