Hansky, Help Better Software

Hybrid Development Environment Adaptability

Today’s computer technology is exploding. It seems everywhere you look these days, more and more choices of software and hardware spring up out of the thin blue sky. However, coupled with this abundance of options is an ever more complex development environment. You got operating systems to choose, IDEs to pick and hardware to consider. Facing this, can Firefly measure up to the situation and unite all your development resources under one king? You bet.

Portability

Firefly is portable. It is implemented using Java and works with the majority of operating systems: Windows 9X/2K, Windows XP, Windows 2003, Linux, all major Unix distributions: FreeBSD, SCO Unixware, IBM AIX, HP-UX, SGI/IRIX, Compaq Tru64, OS/400, etc. To put it in short, if your OS supports Sun Java, then you can use Firefly.

Firefly offers integration for your favorite IDEs such as Borland JBuilder, C++ Builder, Dephi (or any IDE that supports OpenTools API), Eclipse/WSAD, Microsoft Visual Studio, Visual Studio .NET, Sybase PowerBuilder (or any IDE that supports SCC API).

Distributed Development Support

Firefly gives you the power of software configuration management wherever you are. Firefly supports geographically distributed development environment with its TCP/IP based client/server structure. It doesn’t not matter weather your teammate is sitting across the room or across the ocean.

In fact, Firefly goes beyond that. It supports distributed development TEAMs. With Firefly ServerSync module, you can have multiple development teams and servers all over the globe and you will still feel like you are working in adjacent rooms. Server sync in Firefly is branch based. Let’s look at a real life scenario:

U.S. based Company A has outsource one of the modules in its project to a firm in India. It is not practical or efficient for the development team in India to logon to the server across ocean every time they want to check files in or out. Therefore, a second server in India was set up and a Dev stream was created for them to work on. All changes were done in local workspaces on developers’ computers in India and then merged into the Dev stream after approval. Then at a scheduled time or critical moments of the development process, the Dev stream was merged into the Integration stream on the US server.

Previous Next 1 2 3 4 5 6 7 8 9 10