Cart
[Home] [By Thread] [By Date] [Recent Entries]
> [Paul Prescod > > It is precisely the job of > > the architect to take existing components and combine them into > > something new. a software architect should; - the development of any application creates an adhoc framework; a good architect knows this so plans for creating this framework in as sane and stable a way as possible - in a world where there are many emerging technologies architects tries to perform 'software hedging'...which is either backing all similar technologies, knowing when to implement an abstraction layer( e.g. JAXP api ) or going native with a particular flavor ( e.g. writing specific c calls to sablotron )....justifying this operation in context of a single applications requirements and budget is sometimes unrealistic; which is why an architect has to take a framework ( no flames pls relise that framework can be intrepreted in a million different ways ) approach to development - must know when to export functionality to the framework....or when to build something specific for that application knowing they need to get something done and working; this is in general a reoccuring coding decision - ultimately tries to convert inheritance relationships to component relationships cheers, jim fuller
|
