Is it a good idea to write your new program in an oject-oriented-language ? .

If we want to write a program for controlling a device for instance for a mobile phone we have a lot of details to pay attention to: We have a to supply a method to insert the number, the display must be updated, the numbers inserted should be saved in case of a correction, a tone when you press the buttons should be installed, you have to send the phone number to the mobile phone provider etc.

It tends to be confusing because of the variety of all the tasks. If we programm in an object-oriented-language, we have the ability to divide these tasks to different classes. You find datails in the agendas of the seminars like that: .NET Framework in C#,VB.NET(German).

So what is a class ?
A class is a container of data and methods. A class is a blueprint and has data and associated methods. For the display, keyboard, provider we provide classes. These classes are concentrating only on their own task. The methods for each one of the classees can only change their own data. The object-oriented-language offers us with mechanisms to avoid access of data from one class to another class.

Through inheritance a class is reused. The derived class inherits all the data and methods of her base class. If the base classes are well examined, program faults need to be find only in the derived new classes. Those technics are used in the folowing seminars: Vektor-orientierte Oberflächen mit WPF(German).

The time for testing is significantly shorter. Of course you should check the interaction of the classes. The individual tasks are packed into many manageable classes. Troubleshooting and maintaining of the program needs less effort and is less expensive. An excellent way to improve your teams C-Sharp skills, is by booking a Inhouse Dotnet-Training(German) .

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.