Jump to content


- - - - -

CLA Exam Format Change


9 replies to this topic

#1 jgcode

    LabVIEW Renegade

  • Premium Member
  • 2,348 posts
  • Location:Australia
  • Version:LabVIEW 2009
  • Since:2005

Posted 21 July 2010 - 01:46 AM

In case you didn't know....

The exam format for the CLA has now changed from: 40% written and 60% coding, to 100% coding.
The exam is still four hours and the new one now requires you to track requirements too.

#2 Darren

    Extremely Active

  • NI
  • 354 posts
  • Location:Austin, TX
  • Version:LabVIEW 2012
  • Since:1999

Posted 21 July 2010 - 05:54 AM

View Postjgcode, on 21 July 2010 - 01:46 AM, said:

In case you didn't know....

Thanks for posting this, JG. I have written a new post on my blog regarding the changes to the CLA exam.




#3 jgcode

    LabVIEW Renegade

  • Premium Member
  • 2,348 posts
  • Location:Australia
  • Version:LabVIEW 2009
  • Since:2005

Posted 21 July 2010 - 06:37 AM

View PostDarren, on 21 July 2010 - 05:54 AM, said:

Thanks for posting this, JG. I have written a new post on my blog regarding the changes to the CLA exam.



Well, I am off to read it then :)



#4 neil

    Very Active

  • Members
  • PipPipPip
  • 209 posts
  • Location:Surrey, UK
  • Version:LabVIEW 2011
  • Since:2004

Posted 22 July 2010 - 03:51 PM

I wish I had known this before taking a week off (unpaid) to do the Advanced Architectures and S/W Engineering courses! D'oh!

Its not that the courses were bad, just that I did not leave with any real new knowledge (other than Req Gateway which is quite cool).

Oh well, this is the bit of the CLA I was worried about (the written potion), so I suppose its good news :-)

#5 Daklu

    Learning LabFu Daily

  • Premium Member
  • 1,493 posts
  • Location:Seattle
  • Version:LabVIEW 2010
  • Since:2006

Posted 22 July 2010 - 05:38 PM

View Postneil, on 22 July 2010 - 03:51 PM, said:

Oh well, this is the bit of the CLA I was worried about (the written potion), so I suppose its good news :-)

Not so good for some of us. I was counting on the written portion helping me overcome my generally slow coding. I haven't checked out the sample exam yet but I'm a bit nervous about the requirements tracking bit, not having been exposed to the Requirements Gateway at all.
Certified LabVIEW Architect
Good software is an investment. Bad software is an expense. Choose wisely.

Dak's First Law of Problem Solving: If the solution looks simple, I don't know enough about the problem.

There are two secrets to success:
Secret #1 - Never tell everything you know.

#6 Darren

    Extremely Active

  • NI
  • 354 posts
  • Location:Austin, TX
  • Version:LabVIEW 2012
  • Since:1999

Posted 22 July 2010 - 08:51 PM

View PostDaklu, on 22 July 2010 - 05:38 PM, said:

...I'm a bit nervous about the requirements tracking bit, not having been exposed to the Requirements Gateway at all.

As I mention in my blog post, Requirements Gateway is only used for *grading* the exam. You don't need to know Requirements Gateway in order to *take* the exam, you just need to follow the instructions in the exam regarding how to document requirements tracking in the code you write.

-D

#7 jgcode

    LabVIEW Renegade

  • Premium Member
  • 2,348 posts
  • Location:Australia
  • Version:LabVIEW 2009
  • Since:2005

Posted 22 July 2010 - 10:18 PM

View PostDaklu, on 22 July 2010 - 05:38 PM, said:

I was counting on the written portion helping me overcome my generally slow coding.


Me too, I am worried I won't be able to get it all down on the BD in that much time!



#8 Daklu

    Learning LabFu Daily

  • Premium Member
  • 1,493 posts
  • Location:Seattle
  • Version:LabVIEW 2010
  • Since:2006

Posted 22 July 2010 - 11:35 PM

View PostDarren, on 22 July 2010 - 08:51 PM, said:

As I mention in my blog post, Requirements Gateway is only used for *grading* the exam. You don't need to know Requirements Gateway in order to *take* the exam, you just need to follow the instructions in the exam regarding how to document requirements tracking in the code you write.

Thanks for the info Darren. Since we have almost twice as much time to do the coding, are we expected to produce a more complete application?
Certified LabVIEW Architect
Good software is an investment. Bad software is an expense. Choose wisely.

Dak's First Law of Problem Solving: If the solution looks simple, I don't know enough about the problem.

There are two secrets to success:
Secret #1 - Never tell everything you know.

#9 jgcode

    LabVIEW Renegade

  • Premium Member
  • 2,348 posts
  • Location:Australia
  • Version:LabVIEW 2009
  • Since:2005

Posted 22 July 2010 - 11:41 PM

View PostDaklu, on 22 July 2010 - 11:35 PM, said:

Thanks for the info Darren. Since we have almost twice as much time to do the coding, are we expected to produce a more complete application?


I asked the same thing - check out Darren's blog comments for his response.

#10 Daklu

    Learning LabFu Daily

  • Premium Member
  • 1,493 posts
  • Location:Seattle
  • Version:LabVIEW 2010
  • Since:2006

Posted 23 July 2010 - 06:15 AM

View Postjgcode, on 22 July 2010 - 11:41 PM, said:

check out Darren's blog comments for his response.

Note to self -- Follow the links before asking questions. (It's really easy...)
Certified LabVIEW Architect
Good software is an investment. Bad software is an expense. Choose wisely.

Dak's First Law of Problem Solving: If the solution looks simple, I don't know enough about the problem.

There are two secrets to success:
Secret #1 - Never tell everything you know.