Your browser does not support JavaScript!
http://iet.metastore.ingenta.com
1887

Deriving architectural flexibility requirements in safety-critical systems

Deriving architectural flexibility requirements in safety-critical systems

For access to this article, please select a purchase option:

Buy article PDF
£12.50
(plus tax if applicable)
Buy Knowledge Pack
10 articles for £75.00
(plus taxes if applicable)

IET members benefit from discounts to all IET publications and free access to E&T Magazine. If you are an IET member, log in to your account and the discounts will automatically be applied.

Learn more about IET membership 

Recommend Title Publication to library

You must fill out fields marked with: *

Librarian details
Name:*
Email:*
Your details
Name:*
Email:*
Department:*
Why are you recommending this title?
Select reason:
 
 
 
 
 
IEE Proceedings - Software — Recommend this title to your library

Thank you

Your recommendation has been sent to your librarian.

Safety-critical embedded systems are constrained by safety regulations that require the designers of the system to explain its operation. This includes the operation of any flexibility mechanisms present in the design, and the rationale for their inclusion. The ability to place such flexibility where it is most needed is a crucial factor in reducing the cost and risk of safety-critical system development. In this paper an analysis technique that the designer can apply when faced with potential requirements problems is described and evaluated. The technique derives flexibility requirements from indicators of customer uncertainty in the way the requirement is expressed. This allows the designer to quickly describe the required flexibility in the architecture and proceed with design even when the requirement is expected to change. The evaluation shows a significant improvement in the ability of a design to manage change when it contains flexibility that is targeted using the uncertainty analysis technique, compared with flexibility that is generated through more conventional means.

References

    1. 1)
    2. 2)
      • C. Hofmeister , R. Nord , D. Soni . (2000) Applied software architecture.
    3. 3)
      • Bush, D., Finkelstein, A.: `Requirements stability assessment using scenarios', Proc. 11th IEEE Int. Conf. on Requirements Engineering, September 2003, p. 23–32.
    4. 4)
      • D.A. Stokes . (1990) Requirements analysis, Software engineer's reference book.
    5. 5)
      • A. van Lamsweerde . From system goals to software architecture. Form. Methods Softw. Archit. , 25 - 43
    6. 6)
      • Stephenson, Z.: `Uncertainty analysis guidebook, Technical report', May 2005.
    7. 7)
      • V. Gervasi , B. Nuseibeh . Lightweight validation of natural language requirements: a case study. Softw.-Pract. Exp. , 2 , 113 - 133
    8. 8)
    9. 9)
      • M.E.C. Hull , K. Jackson , A.J.J. Dick . (2010) Requirements engineering.
    10. 10)
      • E. Gamma , R. Helm , R. Johnson , J.M. Vlissides . (1994) Design patterns: elements of reusable object-oriented software.
    11. 11)
      • G.-C. Roman . A taxonomy of current issues in requirements engineering. Computer , 14 - 22
    12. 12)
      • Stephenson, Z.R.: `Change management in families of safety-critical embedded systems', 2002, PhD, The University of York.
    13. 13)
      • G.B. Davis . Strategies for information requirements determination. IBM Syst. J. , 1 , 4 - 30
    14. 14)
      • T. Saarinen , A. Vepsalainen . Managing the risks of information systems implementation. Eur. J. Inf. Syst. , 4 , 283 - 295
    15. 15)
      • Mathiassen, L., Stage, J.: `Complexity and uncertainty in software design', Proc. of the IEEE Conf. on Computer Systems and Software Engineering, 1990, p. 482–489.
    16. 16)
      • D.M. Weiss , C.T.R. Lai . (1999) Software product-line engineering: a family-based development process.
http://iet.metastore.ingenta.com/content/journals/10.1049/ip-sen_20045050
Loading

Related content

content/journals/10.1049/ip-sen_20045050
pub_keyword,iet_inspecKeyword,pub_concept
6
6
Loading
This is a required field
Please enter a valid email address