As you may noticed I am mostly engaged in Microsoft technology. So yesterday I set myself a new target on my way to becoming a software-architect. I want to certifie as a "Microsoft Certified Professional Developer: Enterprise Applications Developer" - one of the new certification tracks for .NET framework 2.0 and Visual Studio 2005.
To get the certifications I have to pass five exams:
Foundation
1) Exam 70-536 TS: Microsoft .NET Framework 2.0 - Application Development Foundation
This exam covers the topics I am just dealing with in the C# tutorials so I map this to my definition of things a software-developer must know (at least if he uses c#).
MCTS Credentials
The next part consists of three exams to get the Microsoft Certified Technology Specialist (MCTS) credentials:
2) Exam 70–528: TS: Microsoft .NET Framework 2.0 - Web-Based Client Development
3) Exam 70-526: TS: Microsoft .NET Framework 2.0 - Windows-Based Client Development
4) Exam 70–529: TS: Microsoft .NET Framework 2.0 - Distributed Application Development
This exams still cover topics for a software-developer.
MCPD: Enterprise Applications Developer Exam
This is the final exam and this exam covers topics of a software-engineer, therefore climbing the ladder up for becoming a software-architect.
5) Exam 70–549: PRO: Designing and Developing Enterprise Applications by Using the Microsoft .NET Framework
So this is the "achievements roadmap" which can be mapped to the C#-learning roadmap.
For now...let's go for 70-536!
Wednesday, December 13, 2006
Thursday, December 07, 2006
Mock Objects Rock!
As a support of my C# studies I started a "real-life" private project in C# (budget-planning tool). My plan is to apply the "lessons learned" in that project to get a real feeling for it as soon I am ready with the specific lesson. Also sometimes the "lessons learned" may seem to be violently pressed into my solution, its all about the academic value.
For supporting the refactoring which will occure by the constant change of the code I installed NUnit again. After completing the NUnit Quickstart on Nunit.org I studied the article Test-Driven Development in Dotnet by Peter Provost which gives a little deeper insight in NUnit.
In the second half of the article a method for testing user interfaces in a Model-View/Controller environment is introduced by also introducing Mock Objects. That example really hit me. So I quickly downloaded http://sourceforge.net/projects/dotnetmock/ and tried the example. It's great how the mock-objects simulates the view in that example, and by just passing a View-Interface to the model you can exchange the mock-view with a real winform or webform.
The example is based on an idea of the article The Humble Dialog Box and reading Martin Fowler's Mocks Aren't Stubs article will complete the introduction to mock objects and testing.
A really important topic for software-developing, imho. Also i recognized how my code quality improved by using the TDD approach (keyword "Tell Don't Ask" Principle!).
For supporting the refactoring which will occure by the constant change of the code I installed NUnit again. After completing the NUnit Quickstart on Nunit.org I studied the article Test-Driven Development in Dotnet by Peter Provost which gives a little deeper insight in NUnit.
In the second half of the article a method for testing user interfaces in a Model-View/Controller environment is introduced by also introducing Mock Objects. That example really hit me. So I quickly downloaded http://sourceforge.net/projects/dotnetmock/ and tried the example. It's great how the mock-objects simulates the view in that example, and by just passing a View-Interface to the model you can exchange the mock-view with a real winform or webform.
The example is based on an idea of the article The Humble Dialog Box and reading Martin Fowler's Mocks Aren't Stubs article will complete the introduction to mock objects and testing.
A really important topic for software-developing, imho. Also i recognized how my code quality improved by using the TDD approach (keyword "Tell Don't Ask" Principle!).
Subscribe to:
Comments (Atom)