Hi Stephane, - the architecture
This is how you construct an application and the code that is used to call various aspects of your application. Just like a building has architectural plans created before it is built, so do applications. Note also, that the architecture establishes building codes that each part of it must adhere to, meaning it creates rules for how different parts of it interact with other parts. - the micro-architecture This is a sub structure that can be used to also concrete a way an application patterns itself for reuse. It's a way to establish a standard of programming that can be relied upon when a team of developers are using the same code base. - the application programmatic interface or API This is a class's public interface. This means that when you specify; public function getUsers():Users You are stating that outside classes can call this method and expect a Users object. The outside application does not care about how the class that defined getUsers() actually is 'getting' the users. This is the black box of Object Oriented Programming. It all hinges on the public interface defined by the classes within a framework architecture. - the interface or ISomething This is the same idea as the API, but it decouples a concrete class IE a class that defines getUsers(). So instead of requiring an instance of a class to be a UserReturn.getUsers() class an interface makes it possible to have many classes that will return a Users object. These classes will implement the IUsers interface that holds a public API method called getUsers():Users It's up to the implementing class to decide how it returns or 'creates' this Users object. Thus, the word polymorphism. The ability to change something without being coupled to a concrete class that has a public method called getUsers(). - the software development kit or SDK This just means that it is a package of classes, utilities, compilers that create the runtime object that will be presented to a user of your application. - the framework This is just another word for architecture. Usually this term is used by lowlevel developers that are creating reusable components that an architecture will use on an application level. An architecture usually is spoken from an Application developers perspective and framework is spoken from a component developers perspective. Anyway, that is my 2cents, there are somany interpretations of these words. Peace, Mike On 9/15/07, flexindesign <[EMAIL PROTECTED]> wrote: > > Hello everyone, > > I just get started with my development consultancy and need a clearer > definition of some of the most recurrent terms. I know their > definition, what I am interested in finding out is how the most expert > of you would describe the differences or similarities between: > > - the architecture > - the micro-architecture > - the application programmatic interface or API > - the interface or ISomething > - the software development kit or SDK > - the framework > > Thanks! > > Stephane Beladaci > www.linkedin.com/in/flexdesigner > > > -- Teoti Graphix http://www.teotigraphix.com Blog - Flex2Components http://www.flex2components.com You can find more by solving the problem then by 'asking the question'.
