Architecting a .NET assembly?

Question

When they say that a good program has good architechture, what exactly do they mean.

I know about .NET and classes and object oriented technology, but before I write code, what makes the program have a good design and well thought out architechture?

Is it breaking up the program into the right classes, having the right access levels for class member, having the right interfaces and public function signatures? All the above? Anything else?

Answer 1

Yes, yes and yes. All the things you mentioned are aspects of good architecture. Essentially, a well-architected piece of software is one that is built from logical base classes into logical derived classes. Well-architected systems are easily extensible because the base classes are designed to be used in most situations - that means that if you need to add additional functionality later, you can reuse your existing code without having to modify it. Think of it as working with a provider model - design your classes in such a way that they provide a service that anyone could implement in any situation, rather than perform a specific action for a specific need.

Answer 2

You answered your own question.