An old concept but still going strong, the important cracks in the MBSE wall to fix is what’s in between; in between the different domains, disciplines, methods and ideas.
Visar inlägg med etikett mbse. Visa alla inlägg
Visar inlägg med etikett mbse. Visa alla inlägg
torsdag 30 december 2010
söndag 5 december 2010
March in December
Later this year I will do a short guest appearance, again, in the Vinnova-funded VCC project March/DFEA2020 so today I’m doing a bit of reading, catching up if you will. One of my recurring concerns in the area of MBSE is that there’s really not that much to catch up to. It still seems as if the prevailing ideas are the top-down approach in some form where either method has their solution to achieve traceability and a “Russian doll” situation.
I’m more interested in what aspects of modeling and systems engineering that will benefit your organization and constantly improve performance. To me most of the large MBSE initiatives/methods are very bulky and impose a clear and present risk of putting a lid on engineering and innovation.
Some random questions I find interesting:
How do you move focus from verification to validation? The ability to do trial and error, short prototyping loops etc. are vital, what do you need to support this?
How do you push “decision power” closer to the problem? With an over-weight top-down approach this is impossible. How about creating a more loosely coupled architecture based on patterns and some well-placed poles in the ground designed to keep the solution within acceptable boundaries compared to important attributes?
If you product is multi-faceted you will be using different tools and languages to describe it (don’t try to dig with a fork if you have spoon), how can you provide aid to minimize hand-offs, or at least confusion in hand-offs? Instead of attacking traceability you might need to start in a different end, to really understand the information need and information structure in your organization.
If you are implementing parts of the system in-house you want to give the SW-department the best possible pre-requisites in order to do their job, how can we do the same for those parts developed by suppliers? Can models help us increase transparency where needed in our supplier communication?
Models instead of documents push towards construction and engineering, if our organization has started to lose touch with those disciplines we are in danger of applying Models Based Systems Drawing instead. How can we mitigate that imminent risk?
And why is it that it is so rare to find the notion of a lean or agile mindset in conjunction with MBSE? If we want to run our implementation according to agile principles we need to understand the implications and changes in approach needed when it comes to architecture, integration, systems engineering etc.
I’m more interested in what aspects of modeling and systems engineering that will benefit your organization and constantly improve performance. To me most of the large MBSE initiatives/methods are very bulky and impose a clear and present risk of putting a lid on engineering and innovation.
Some random questions I find interesting:
How do you move focus from verification to validation? The ability to do trial and error, short prototyping loops etc. are vital, what do you need to support this?
How do you push “decision power” closer to the problem? With an over-weight top-down approach this is impossible. How about creating a more loosely coupled architecture based on patterns and some well-placed poles in the ground designed to keep the solution within acceptable boundaries compared to important attributes?
If you product is multi-faceted you will be using different tools and languages to describe it (don’t try to dig with a fork if you have spoon), how can you provide aid to minimize hand-offs, or at least confusion in hand-offs? Instead of attacking traceability you might need to start in a different end, to really understand the information need and information structure in your organization.
If you are implementing parts of the system in-house you want to give the SW-department the best possible pre-requisites in order to do their job, how can we do the same for those parts developed by suppliers? Can models help us increase transparency where needed in our supplier communication?
Models instead of documents push towards construction and engineering, if our organization has started to lose touch with those disciplines we are in danger of applying Models Based Systems Drawing instead. How can we mitigate that imminent risk?
And why is it that it is so rare to find the notion of a lean or agile mindset in conjunction with MBSE? If we want to run our implementation according to agile principles we need to understand the implications and changes in approach needed when it comes to architecture, integration, systems engineering etc.
söndag 12 september 2010
Fight the power
And in my context, the power is time. Been a while since the last proper update, is it because my days are uneventful? On the contrary, it’s quite the opposite.
Met with Scania last week, had an interesting 2-hour session with a team there discussing MBSE together with two colleagues of mine. I can’t help myself to be impressed with their relentless focus on the customer. -In-every-context-. Of course one could argue that sometimes it gets too much, but I think it is in their consistency and endurance to keep that focus you’ll find the explanation to their edge. Anyhow the discussion was really pleasant, they have a lot of ideas and the people there like to twist and turn the arguments which make for a fruitful dialogue.
Have to comment on my SAAB assignment as well, passed the 6-month mark now and by then you are starting to get settled in. In the beginning I liked the assignment a lot, and I have to say that it only keeps getting better. Guess that’s easy though when you are working with great people, interesting technology, new challenges and opportunities almost daily, and all in an environment moving towards agile. For me it has been extra rewarding so far since it’s been a while since I got to work the full scope down to the smallest bit and byte, something that definitely improves my ability to work with the bigger picture.
Outside the scope of SAAB there’s a lot going on. Since 1st of July I’m standing in for a colleague in Gothenburg as Business Area Manager. We have great people working with architecture and MBSE and I try to help them channel all that knowledge. There are a lot of great ideas and with all those talented consultants it will be really interesting to see what we have achieved given some time. Next big check-point is our conference coming up soon. Let creativity flow.
Funny, when I read through the post I notice how positive it is… I guess when I stop and contemplate over “now” for a second I realize that life’s really good at the moment. Uppåt! Framåt!
Just text makes for a boring post… so why not a clip from Grandaddy. No matter how much money you have nothing beats a good idea, I love the simplicity of this video. It will be really interesting to see what the guy behind it come up with making a video for Tomas Halberstad.
Oh, and reading a book from Jim Coplien on Lean Architecture at the moment (will probably share some thoughts here later). He quoted someone (who I apparently forgot the name of). Think about it.
"Live simple, be complicated."
Met with Scania last week, had an interesting 2-hour session with a team there discussing MBSE together with two colleagues of mine. I can’t help myself to be impressed with their relentless focus on the customer. -In-every-context-. Of course one could argue that sometimes it gets too much, but I think it is in their consistency and endurance to keep that focus you’ll find the explanation to their edge. Anyhow the discussion was really pleasant, they have a lot of ideas and the people there like to twist and turn the arguments which make for a fruitful dialogue.
Have to comment on my SAAB assignment as well, passed the 6-month mark now and by then you are starting to get settled in. In the beginning I liked the assignment a lot, and I have to say that it only keeps getting better. Guess that’s easy though when you are working with great people, interesting technology, new challenges and opportunities almost daily, and all in an environment moving towards agile. For me it has been extra rewarding so far since it’s been a while since I got to work the full scope down to the smallest bit and byte, something that definitely improves my ability to work with the bigger picture.
Outside the scope of SAAB there’s a lot going on. Since 1st of July I’m standing in for a colleague in Gothenburg as Business Area Manager. We have great people working with architecture and MBSE and I try to help them channel all that knowledge. There are a lot of great ideas and with all those talented consultants it will be really interesting to see what we have achieved given some time. Next big check-point is our conference coming up soon. Let creativity flow.
Funny, when I read through the post I notice how positive it is… I guess when I stop and contemplate over “now” for a second I realize that life’s really good at the moment. Uppåt! Framåt!
Just text makes for a boring post… so why not a clip from Grandaddy. No matter how much money you have nothing beats a good idea, I love the simplicity of this video. It will be really interesting to see what the guy behind it come up with making a video for Tomas Halberstad.
Oh, and reading a book from Jim Coplien on Lean Architecture at the moment (will probably share some thoughts here later). He quoted someone (who I apparently forgot the name of). Think about it.
"Live simple, be complicated."
söndag 27 juni 2010
West side
Spent two days last week in Gothenburg with all the nice colleagues at our main office.
A lot of business development discussions involving our Vinnova projects, product management and software/system architecture for agile or lean organizations.
A lot of business development discussions involving our Vinnova projects, product management and software/system architecture for agile or lean organizations.
As usual it was great fun and a learning experience. Thanks all.
Tomas Sandén discussing model-based systems engineering
onsdag 3 mars 2010
Building an aircraft
Starting a new assignment today at exactly 1245 at SAAB (not the Spyker-kind but the flying-kind) and I’m really looking forward to it. It will be a nice change of pace compared to the more research-oriented Vinnova-projects I’ve been involved in recently.
Unfortunately I don’t think I will able to blog about basically anything I do over the coming months, being very secret and all… but since I will keep one foot going in both our architecture and MBSE group I’m sure there will be stuff to share and discuss.
Additionally you can look forward to some guest-blogging around both DCI and Lean from Mats and Gunilla. The pressure is on.
Unfortunately I don’t think I will able to blog about basically anything I do over the coming months, being very secret and all… but since I will keep one foot going in both our architecture and MBSE group I’m sure there will be stuff to share and discuss.
Additionally you can look forward to some guest-blogging around both DCI and Lean from Mats and Gunilla. The pressure is on.
Prenumerera på:
Inlägg (Atom)