Systems Engineering Patterns

Reference Architectures

More and more, the topic of reference architectures is crossing my workspace. A recently published article*  in the INCOSE Systems Engineering Journal was well received. In many ways, reference architecture are like system architecture pattrerns, though they provide more guidance, may be strongly based or influenced by standards, and my be driven by industry. I will begin blogging more on reference architectures in the future.

*Cloutier, Robert, Gerrit Muller, Dinesh Verma, Roshanak Nilchiani Eirik Hole & Mary Bone, The Concept of Reference Architectures, INCOSE SE Journal, Volume 13 Issue Number 1, ISSN: 1098-1241, p. 14-27, January 2010

Mining patterns

What is meant when it is said that patterns are mined? For the software community, that means actually looking at code, and finding the essence across multiple implementations. But what does it mean to mine a pattern for a system level pattern? At the hightest level, the pattern may be so abstract it is meaningless. Aircraft systems, for the most part, have a fuselage, wings, tail, and landing gears (hopefully). Not very useful. But what other system level patterns can be found? What are the common missions; or sub-missions? What does it mean to document the "transport passengers" operational pattern as opposed to "perform high altitude observation" operational pattern? The differences between those two patterns will affect the decomposition of the system as it is architected. What about the "perform maintenance" operational pattern that captures that mission for the two different types of aircraft? Something to consider.