by webadmin | Feb 7, 2012 | general, legacy modernization, main, Software Development
Software migration, also known as computer migration, data migration or Personal Computer (PC) migration is moving the data and applications from one computer to another. The reasons can be because the user has either purchased a new computer, or the computers at the workplace have been upgraded to new systems. Due to the importance, or difficulty of replacing the original files and programs, the user prefer to have everything go with them to the new machine or system. Usually software migration can be done manually using software tools specific for this operation, over a data transfer cable, the link between the two computers. More often than not, full transfer of all the data and software from the source to the destination machine is not entirely necessary. Software migration in the above mentioned fashion can be entirely avoided by making use of external storage devices that will manage to store all the necessary data. Other organizations provide an internet solution for software migration, in that they allow for internet storage. This means instead of using an external hard disk for example, the user will use the internet to keep all the necessary information, and then download it onto the new machine. This removes the need for a full software migration. However, these methods do not work in the business environment. This is because some software has its necessary files in sections of the hard disk that cannot be accessed by users for one reason or another. This would result in the application reverting to the default settings, or completely malfunctioning, resulting in the need to reinstall. Files, for instance registry...
by webadmin | Feb 7, 2012 | .NET, general, main, Software Development
Power builder is an integrated development environment used to create applications. PowerBuilder to .Net is a combination of PowerBuilder and Microsoft’s .Net platform; the latest in software migration that has revolutionized the world of applications development. Though originally designed to compete with Microsoft developed IDE’s, the Power Builder to .Net integration was created to allow continuity for the PowerBuilder project and to take advantage of the .Net platform that many developers are now using to create business critical applications. The PowerBuilder to.Net IDE is preferred by many application developers as it is a fast, cost-effective and easy application development software. The typical PowerBuilder to .Net business application is high performance and data driven. Technology used in PowerBuilder to.Net is also unique in that it continuously evolves to accommodate the latest software advances and business needs. This ability to keep up with advances in VUI (Visual User Interface) advances as well as functionality creates valuable competitive advantage for businesses that use the PowerBuilder to .Net platform. One of the reasons the PowerBuilder to .Net platform is favoured as rapid application development software by developers is its speed and simplicity. This development speed is attributed to the original PowerBuilder to .Net ‘DataWindow’ technology. This function imported from the PowerBuilder Classic version allows developers to use minimal coding to create data rich applications. Thanks to DataWindow, developers using PowerBuilder to .Net only need to use five lines of coding script to apply custom business logic. The simplicity created by the PowerBuilder to .Net technology through its declarative programming environment, coupled with increased levels of abstraction reduces complexities of development...
by webadmin | Feb 7, 2012 | general, JAVA, Software Development
PowerBuilder has for years been considered the best application development software among RAD softwares. Its main benefits are speed and simplicity, which are offered by its DataWindow component. Unfortunately though, due to advances in technology, programming languages as well as business needs PowerBuilder is falling into obscurity. The results of this are diminished support services as PowerBuilder experts are becoming scarce and a lack of extensibility for Power Builder based applications. This has necessitated migration to modern platforms such as Java and Microsoft .Net platforms. Legacy migrations such as PowerBuilder to Java have their benefits as well as complications. The main benefit that is reaped from the PowerBuilder to Java migration is platform flexibility. Other advantages associated with this migration are both platforms have the same type of look and feel and PowerBuilder to Java has some degree of automation. There is error handling and security as well as near exact replication. As an upgrade, the PowerBuilder to Java migration provides similar services as the PowerBuilder Classic version, just with more efficient technology. As such the Power Builder to Java upgrade should be able to provide the same productivity levels and higher in a modern environment; little to no limitations on the target server platform as well as an open, flexible platform development environment. This means the upgrade should enable application design and creation using the latest software development methods. Maintenance costs should also be reduced. As with any legacy system migration, quite a bit of money and expertise is needed. Further more migrations such as PowerBuilder to Java can be risky and complex as critical business...
by webadmin | Feb 7, 2012 | general, JAVA, main, Software Development
The Common Business Oriented Language, abbreviated as COBOL is among the oldest languages used in programming. Created in the late 1950’s most organizations legacy systems are in fact based on COBOL programming. Due to this though, most companies are finding it hard to update their business processes to reflect the changes in technology. The main problem that is associated with using COBOL legacy systems is that it is an expensive platform to maintain, especially since the number of programmers that are familiar with COLBOL keeps reducing each year. Furthermore it prevents companies from being able to standardize their technology as modern software is not compatible with these older platforms. Since rewriting the source code is equally expensive most firms are viewing migration from COBOL to Java as a more viable option. If you’re not entirely convinced to jump on the COBOL to Java bandwagon you can review the other alternatives available and compare the cost and benefits of all the options. Two other methods of dealing with the issues presented by legacy system use are modernization or re-writing. Modernization entails upgrading to the latest program which will standardize coding format and make it easier to maintain code. The drawback of this though is that the firm will continue to incur COBOL maintenance costs and the system still cannot be integrated with modern technologies. Rewriting entails translating COBOL into a modern code, which while the cleanest method to use is very expensive very slow. The beauty of Java as a programming language is that it can run on practically any operating system platform. COBOL to Java migration should be a...
by webadmin | Feb 7, 2012 | Code Generation, Software Development
Code generation is a technique that is used in the development of applications. There are many types of code generators on the market, each with their unique capabilities. Visual basic code generator is currently the favourite among programmers. This rapid application development tool is generally used to create windows applications. A task it efficiently completes in a short period of time. The basic task of the visual basic code generator is to convert source code data from intermediate language form into a language that can easily be read and enacted by a computer. Code generators such as the visual basic code generator can normally perform dual functions. Aside from intermediate representation conversion, they also try to improve on the code. This optimization can be pursued on the instructional level; where the generator opts for either faster or fewer instructions. It can also be pursued at the more advanced stage through exploitation of available registers and avoidance and elimination of redundant computations. The typical process that the visual basic code generator goes through includes selection, scheduling, allocation and debugging. At the first two stages of the process, the visual basic code generator chooses the set of instructions that it is going to implement. It then determines the order in which these instructions are to be executed. This step could also contribute in terms of speed optimization; especially in the case of pipe-lined machines. In the third step, allocation refers to the collection of associated variables to the available processor register. The final stage of the visual basic code generator is the debugging process. This ensures that there is...
Recent Comments