CLA Exam Format Change
Started by jgcode, Jul 21 2010 01:46 AM
9 replies to this topic
#1
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.
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.
#4
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 :-)
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
Posted 22 July 2010 - 05:38 PM
neil, 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.
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
Posted 22 July 2010 - 08:51 PM
Daklu, 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
#8
Posted 22 July 2010 - 11:35 PM
Darren, 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.
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.
#10
Posted 23 July 2010 - 06:15 AM
jgcode, 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.
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.













