Enterprise Resource Panning (ERP)

Nowadays everyone is talking about ERP everywhere in the corporate world.

ERP is being implemented very rapidly in whether it is a large scale or medium scale enterprises.

The benefits of implementing ERP have proven to be making effective use resources and using them.

TechYoddha team is also working hard in the direction of developing Business Software Solutions to be implemented by ERP or through ERP.

Contact : info@techyoddha.com

Lets look at the definition of ERP?

by Tech-Faq.com >> ERP stands for Enterprise Resource Planning. ERP is a way to integrate the data and processes of an organization into one single system. Usually ERP systems will have many components including hardware and software, in order to achieve integration, most ERP systems use a unified database to store data for various functions found throughout the organization.

by Wikipedia >> Enterprise resource planning (ERP) systems attempt to integrate several data sources and processes of an organization into a unified system. A typical ERP system will use multiple components of computer software and hardware to achieve the integration. A key ingredient of most ERP systems is the use of a unified database to store data for the various system modules.

The two key components of an ERP system are a common database and a modular software design. A common database is the system that allows every department of a company to store and retrieve information in real-time. Using a common database allows information to be more reliable, accessible, and easily shared. Furthermore, a modular software design is a variety of programs that can be added on an individual basis to improve the efficiency of the business. This improves the business by adding functionality, mixing and matching programs from different vendors, and allowing the company to choose which modules to implement. These modular software designs link into the common database, so that all of the information between the departments is accessible in real time.

Bots have arrived...

Sun Microsystems co–founder Bill Joy’s now well–known article in wired, titled ‘Why the future doesn’t need us’, begun with the subheading: “Our most powerful 21st century technologies–robotics, genetics engineering, and nanotech–are threatening to make humans an endangered species.” Joy went on to express his fears about the new technologies, saying, for example, that robot might be dangerous because they might replicate; that we may not survive our encounter with the new species, and so on.

Everyone has a point of view and something to say about this–some say Joy is exaggerating, some share his concern. But there’s no doubting the fact that robotics has come of age; it’s only a matter of time before we relegate more and more of our duties to the machines.

The ‘new species‘– humanoid, bot, part-human-part-bot, whatever– has already been born.

This article is courtsey Mr. Pravin K. Dubey.

FAQs for AJAX

01. Did Adaptive Path invent Ajax? Did Google? Did Adaptive Path help build Google’s Ajax applications?
Ans. Neither Adaptive Path nor Google invented Ajax. Google’s recent products are simply the highest-profile examples of Ajax applications. Adaptive Path was not involved in the development of Google’s Ajax applications.

02. Is Adaptive Path selling Ajax components or trade marking the name? Where can I download it?
Ans. Ajax isn’t something you can download. It’s an approach — a way of thinking about the architecture of web applications using certain technologies. Neither the Ajax name nor the approaches are proprietary to Adaptive Path.

03. Is Ajax just another name for XMLHttpRequest?
Ans. No. XMLHttpRequest is only part of the Ajax equation. XMLHttpRequest is the technical component that makes the asynchronous server communication possible; Ajax is a name for the overall approach described in my earlier articles, which relies not only on XMLHttpRequest, but on CSS, DOM, and other technologies.

04. Techniques for asynchronous serve communication have been around for years. What makes Ajax a "new" approach?
Ans. What’s new is the prominent use of these techniques in real-world applications to change the fundamental interaction model of the Web. Ajax is taking hold now because these technologies and the industry understand of how to deploy them most effectively have taken time to develop.

05. Is Ajax a technology platform or is it an architectural style?
Ans. It’s both. Ajax is a set of technologies being used together in a particular way.

06. What kinds of applications is Ajax best suited for?
Ans. I don’t know yet. Because this is a relatively new approach, my understanding of where Ajax can best be applied is still in its infancy. Sometimes the traditional web application model is the most appropriate solution to a problem.

07. Does this mean Adaptive Path is anti-Flash?
Ans. Not at all. Macromedia is an Adaptive Path client. As Ajax matures, I expect that sometimes Ajax will be the better solution to a particular problem, and sometimes Flash will be the better solution. I’m also interested in exploring ways the technologies can be mixed (as in the case of Flickr, which uses both).

08. Does Ajax have significant accessibility or browser compatibility limitations? Do Ajax applications break the back button? Is Ajax compatible with REST? Are there security considerations with Ajax development? Can Ajax applications be made to work for users who have JavaScript turned off?
Ans. The answer to all of these questions is "maybe". Many developers are already working on ways to address these concerns. I think there’s more work to be done to determine all the limitations of Ajax, and I expect the Ajax development community to uncover more issues like these along the way.

09. Some of the Google examples you cite don’t use XML at all. Do I have to use XML and/or XSLT in an Ajax application?
Ans. No. XML is the most fully-developed means of getting data in and out of an Ajax client, but there’s no reason you couldn’t accomplish the same effects using a technology like JavaScript Object Notation or any similar means of structuring data for interchange.

10. Are Ajax applications easier to develop than traditional web applications?
Ans. Not necessarily. Ajax applications inevitably involve running complex JavaScript code on the client. Making that complex code efficient and bug-free is not a task to be taken lightly, and better development tools and frameworks will be needed to help us meet that challenge.

11. Do Ajax applications always deliver a better experience than traditional web applications?
Ans. Not necessarily. Ajax gives interaction designers more flexibility. However, the more power we have, the more caution we must use in exercising it. We must be careful to use Ajax to enhance the user experience of our applications, not degrade it.


These FAQs are a compilation of Mr. Pravin Kumar Dubey from below references.
We are proud to have a member like him, and thank him for keeping the blog live.

References:

• www.ajaxian.com
• www.ajaxreview.com
• java.sun.com
• www.crockford.com
• www.informationweek.com

Introducing AJAX

This article is researched and presented to us by Mr. Pravin Kumar Dubey.

If anything about current interaction design can be called "glamorous", it’s creating Web applications. After all, when was the last time you heard someone rave about the interaction design of a product that wasn’t on the Web? (Okay, besides the iPod.) All the cool, innovative new projects are online.
Despite this, desktop applications have a richness and responsiveness that has seemed out of reach on the Web. The same simplicity that enabled the Web’s rapid proliferation also creates a gap between the experiences web application can provide and the experiences users can get from a desktop application.
That gap between the web application and the desktop application is closing. Take a look at Google Suggest. Watch the way the suggested terms update as you type, almost instantly. Now look at Google Maps zoom in. Use your cursor to grab the map and scroll around a bit. Again, everything happens almost instantly, with no waiting for pages to reload.
Google Suggest and Google Maps are two examples of a new approach to web applications that the people at Adaptive Path have been calling AJAX. The name is shorthand for Asynchronous JavaScript and XML, and it represents a fundamental shift in what’s possible on the Web.

References:

• www.adaptivepath.com/publications/essays/archives/000385.php

Java Web Start

Ms. Sindhu Kumari, a TechYoddha member has done some readings on this topic. Below are her summarizations.

Java Web Start, introduced in Java 2, is a framework developed by Sun Microsystems that allows running the applications for the Java Platform over the Web by clicking a link on a website, and on a desktop icon thereafter……….

Important Web Start features include:

1) The ability to automatically download and install a JRE in the case where the user does not have Java installed, and for programmers to specify which JRE version is needed to run a given program.

2) The user does not have to remain connected to the Internet to execute the downloaded programs, because they execute from a locally-maintained cache.

3) Finally, automatic updates of the software from the Web are available when the user is connected to the Internet, thus easing the burden of deployment.

This technology offers a nice compromise between the ease of distribution provided by Java applets and the power of Java applications.

Version 1.0 of Web Start was introduced by Sun in March 2001. Since J2SE version 1.4 it has been included by default with the Java Runtime Environment (JRE) and does not have to be installed separately.

JNLP is free; developers are not required to pay a license fee in order to use it in programs.

Java Web Start is similar to Click Once in the .NET framework.

From user’s point of view, this technology is amazing, coz it frees the user from downloading, installing and keeping track of latest version of the application. For him everything is happening automatically...on just a single click at a link on their web browser. But for a developer, it is quite a headache. Because web start maintains the cache of the application at some place, it renames all the resource files and keeps them all at different- different locations. And all this information is maintained by web start only. So while developing the application, a lot of care needs to be taken.

To conclude, Java Web Start is a very useful technology, if implemented carefully.

References:

http://java.sun.com/products/javawebstart/developers.html

http://en.wikipedia.org/wiki/Java_Web_Start

http://articles.techrepublic.com.com/5100-10878_11-1049931.html?tag=rbxccnbtr1

About Us....

We are a team of trained professionals from NIIT through an Industry Endorsed Curriculum 'GNIIT' which is as per the industry standards and requirements.

We have got the best skilled team members who have been the excellent performers at their training period.

Contact Us : info@techyoddha.com