Visar inlägg med etikett incose. Visa alla inlägg
Visar inlägg med etikett incose. Visa alla inlägg

onsdag 21 oktober 2009

Interception

Jets threw 6 interceptions vs Bills on Sunday. How is that even possible in NFL? And no, I'm not gonna do some cheezy reference to product development now. It's that bad.

The INCOSE/MODPROD seminar yesterday was interesting. I’ve heard most of the keynote with regards to Modelica before but some repetition is always nice, and I didn’t know about the effort to integrate it with Autosar into Modelisar (one more link). Even though I have never worked with Modelica I have done some exercises and I kind of like the acasual equation-style modeling.

Following the keynote there were three small talks from the INCOSE conference in Singapore earlier this year. The most interesting one was about model-based technical planning using SysML. Interesting enough for me to try to find the paper behind the presentation and read some more. I admit that I’m not sold on the concept but it is a new angle to a Gantt-heavy discipline.

The afternoon was spent in workshops and our group discussed systems engineering from a process perspective. Our group were quite small which made room for interesting discussions about everything from CMMi to Lean (and of course the mandatory question “what is systems engineering”).

With regards to Speeds I am not any wiser, contracts-based engineering with assumptions and promises looks ok but I think I would start to change other things first...


Anyhow, interesting day and the EuSEC in May 2010 might be worth visiting.


6 interceptions?! Gasp.

måndag 19 oktober 2009

Speeds

Just finished reading a white-paper on Speeds, the idea is of course good but I remain skeptical. To integrate different development environments and modelling tools is sometimes seen as the holy grail but to do it for just one company is hard enough, to do a one-size fits all... we'll I don't know. Especially since we have different tools with different semantics for different purposes, when you connect them you will always have semantic conflicts that can only be solved by interfering with the original idea of the tool.

The other part about Speeds I'm having some issues with is the idea to provide a "working" process accompanied with methods. Usually the process becomes a goal on its own and it won't take long until a big organization has staff dedicated to just that process, to maintain it, to educate, to adapt etc.

The upside is that tomorrow I will get a chance to hear a speech about Speeds and ask some questions. Maybe I'll be a bit wiser and less skeptical after that, who knows?