[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Don't Let Architecture Astronauts Scare You

• To: "XML Dev" <xml-dev@l...>
• Subject: RE: Don't Let Architecture Astronauts Scare You
• From: "James Fuller" <james.fuller@o...>
• Date: Wed, 18 Sep 2002 09:53:26 +0100
• Importance: Normal
• In-reply-to: <007c01c25ed1$2112c810$fe193044@tbp1>

> [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

• References:
  • Re: Don't Let Architecture Astronauts Scare You
    • From: "Thomas B. Passin" <tpassin@c...>

• Prev by Date: Re: Don't Let Architecture Astronauts Scare You
• Next by Date: Re: SGML query: SHUNCHAR
• Previous by thread: Re: Don't Let Architecture Astronauts Scare You
• Next by thread: RE: Don't Let Architecture Astronauts Scare You
• Index(es):
  • Date
  • Thread