Design patterns may not be suitable for complex projects. We have in-depth discussed during coursework how to manage complex and critical systems better.
“Especially, the cost can be a huge problem when applied to the complex system.”
The statement above got me interested, and I did some research. Armoush et al. (2009) propose a template of design patterns for critical safety systems. As depicted in the figure below, the traditional template makes up the upper part of this template, whereas the “implications” section deals with the effects of the pattern of the non-functional requirements such as reliability, safety, cost, modifiability and execution time. Further, this is supported by describing the implementation, consequences and related patterns.
Do you think design pattern template like this can ease the application of design pattern for critical systems? Where of course the programmers should have experience with them as well.
References:
Armoush et al. (2009) ‘Design Pattern Representation for Safety-Critical Embedded Systems’, J. Software Engineering & Applications, 2, pp. 1-12.
I have learn some good stuff here. Definitely value bookmarking for revisiting. I surprise how a lot effort you set to make such a magnificent informative site.
Excuse for that I interfere … I understand this question. I invite to discussion. Write here or in PM.
Very good info. Lucky me I discovered your website by accident (stumbleupon).
I’ve saved it for later!
I really like what you guys are up too. This type of clever work and exposure!
Keep up the terrific works guys I’ve incorporated you guys to my blogroll.
An impressive share! I have just forwarded this onto
a colleague who had been doing a little homework on this.
And he in fact ordered me breakfast because I found it for
him… lol. So allow me to reword this…. Thanks for the meal!!
But yeah, thanx for spending the time to discuss this subject here on your website.