Re: A little off topic, but ...
From: Paul O'Connell (poc_at_globalnet.co.uk)
Date: 10/09/04
- Next message: Ramtin: "DBGrid Header Titles Problem !"
- Previous message: Dirk Reske: "Re: socket transmission problem"
- In reply to: James Divine: "RE: A little off topic, but ..."
- Next in thread: Nick Malik: "Re: A little off topic, but ..."
- Reply: Nick Malik: "Re: A little off topic, but ..."
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 9 Oct 2004 13:23:52 +0100
Personally I think that keeping the networks separate is a sound idea. that
way your production environment cannot be affected by the developers.
Ideally you should also have a separate test network that is a duplicate of
the production environment so that when you test the software you know that
its going to behave as it should in the production environment.
If the cost of the hardware is an issue then possibly using Vitual PC could
work. There are a number of companies offer software for this, a couple of
examples are MS Virtual PC/Server and VMWare.
What you really need is a sound Configuration Management policy. This will
allow all of the networks to kept in sync and manage any changes to the
networks and software. CM covers more that just having something like
SourceSafe to check the source code in and out. It applies to the software
you install on the computers and the patches that are applied. The way the
software is configured, which includes the operating system, networks etc,
all of the documentation that is relevant, the way bugs are raised, fixed
and released and new changes are requested by the users.
Paul.
"James Divine" <JamesDivine@discussions.microsoft.com> wrote in message
news:B6D3D033-0408-456E-ACD0-E286E1AD5999@microsoft.com...
>
>
> We use a 4-tier development system for our enterprise software. We have a
> production server, a quality insurance server (for final testing), a
> development server and a sandbox server. Each of the last three are
'clones'
> of the production server that are refreshed periodically.
>
> My advice would be to follow something similar. If you are maintaining
your
> dev servers seperately, and patching them seperately, that will weaken
their
> ability to be good 'test' servers for production, since you can't
guarantee
> that they are the environments are the same.
>
> -James
>
>
> "Tim Gallivan" wrote:
>
> > I'm a developer for a government ministry (I'll let you guys figure out
the
> > rest). The IT "powers-that-be" have stipulated that all software
development
> > be performed on a separate network that in no way connects to the "main"
> > network - ever. IT's blanket reason is "network security". These
separate
> > networks cost a lot of money - a second database server, app server and
a
> > couple of development machines, they are unpatchable (can't connect to
the
> > web to get updates), you've got to burn a cd everytime you bring out a
new
> > version, and burn a DVD to move big database updates back and forth. OK,
> > enough griping!
> >
> > Would any of you be able to point me at some resources dealing with
software
> > development strategies, or even personal examples of how they do it
where
> > you work? I need to come up with a strategy for my department.
> >
> > Thanks in advance,
> > Tim Gallivan
> > I know I'm a great teacher because when I give a lesson, the person
never
> > comes back.
> >
> >
> >
- Next message: Ramtin: "DBGrid Header Titles Problem !"
- Previous message: Dirk Reske: "Re: socket transmission problem"
- In reply to: James Divine: "RE: A little off topic, but ..."
- Next in thread: Nick Malik: "Re: A little off topic, but ..."
- Reply: Nick Malik: "Re: A little off topic, but ..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|