To the more seasoned people around here, how do CMMI ratings act as a predictor of level of software engineering maturity? I realize that's what the rating is supposed to be, but I didn't know if many organizations put up a front when auditors come around and then throw it all out when they leave.

What I am getting at is, can the OP use metrics like CMMI rating to accurately judge an organizations software process maturity when deciding if he or she wants to work there?

My place isn't like that at all. Everyone works together to get the job done. Managers, for the most part, stay out of the way. It has changed as the scope of my project has been better defined, etc. It was sort of chaos in the beginning though.

Funny you mention the tester though. I can just picture some mad tester guy running into your office ranting and raving throwing his arms all around in the air.

I think some of it also depends upon your level of experience. Someone fresh out of college likely has little or no professional experience (I would recommend open source if I had a time machine). So putting languages you have had classes in is acceptable. But, me personally, after being out of school for a year world and a professional, I wouldn't put the VHDL work I did as an undergraduate. I couldn't do any meaningful work in it without relearning everything.

So I think it would kind of depend on your situation.

Oh, and my advice, whatever languages/things you put on a resume, be absolutely prepared to discuss them for a 30 minute interview session. I naively put a project I worked on as a sophomore when I was looking for a job as a senior. I didn't think a whole lot about it, but one guy I interviewed with drilled me about it. Wanting in depth details about our design decisions, etc. And he was absolutely in the right to do so. Heck, [b]I [/b] put it on the resume. But I was woefully unprepared to give in depth details and sounded really dumb. So don't be like me.

Thanks for you input guys. I have been and will continue to think about this. I actually have access to oscilloscopes and power supplies/function generators at work, but NASA can be a pain in letting people use them for non NASA related work.

I am going to see what I can work out and will continue to think about this and give it a proper reply in a few days.

Thanks again.

loctan Newbie Poster

I am working towards my masters degree through an online university. As part of this I need to have a final project. I enjoy doing embedded work, but due to the lack of oscilloscopes, power supplies, machining tools to build a robot, I am looking towards doing another kind of application.

I was thinking it would be interesting to create an eclipse plugin that would collect various software metrics. This plugin would integrate seamlessly in the IDE and could collect various metrics about a software project/module/function such as:

1) SLOC
2) Level of cohesion
3) Amount of coupling between modules
4) Cyclomatic Complexity
5) Number of times a module/function is called to suggest good areas for optimization

Some of this information could even be displayed graphically or in list format. For instance, the cyclomatic complexity could on a per function basis such that a user could see which functions have the highest and this would imply that it may be necessary to simplify the code, etc. The amount of coupling between the various modules could also be displayed to show poor design, etc.

I guess my basic question is what you guys think of something like this? Can you offer any other interesting metrics to collect?