Throwfire

If we want to write a program for controlling a device for instance for a mobile phone we are quickly confronted with numerous different tasks: A method for inserting the number is required, we need to update the display, the numbers entered should be saved in case of a correction, a tone when you push 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 Seminare in C#,VB.NET(German).

So what is a class ?
A class is a container of data and methods. You can think of a class as a blueprint defining data and methods. We define a class for the keyboard, the display, the provider, etc.. These classes focusing only on their own task. The methods of each class can only change their own data. It is not possible to change data from outside the class.

Existing classes can be inherited and thus reused. All data and methods are inherited from the base class. If the base classes are well examined, program errors require to be find only in the derived new classes. Those technics are used in the folowing seminars: Webanwendungen mit ASP.NET (German).

Time for testing is shorter and less stressful. Of course you should check the interaction of the classes. If we want to realize today’s complex programs in a moderate time we are well advised to use object-oriented-programs. Object-oriented-programs keeps the time for editing and debugging moderate and is less expensive. A very good way to improve your teams dotnet skills, is by booking a Inhouse Training(German).

Leave a Reply