25-08-2017, 09:32 PM
RIA based E- Shopping Portal for Electronic Gadgets
RIA based E- Shopping.doc (Size: 1.35 MB / Downloads: 34)
INTRODUCTION
E- Shopping is a form of electronic commerce where consumers directly buy goods or services from a seller over Internet without an intermediary service. An online shop, e-shop, e-store, Internet shop, web shop, or virtual store evokes the physical analogy of buying products or services at a bricks-and–mortar retailer or shopping centre. The process is called as business-to-customer (B2C) online shopping. When a business buys from another business, it is called as business to business (B2B) online shopping.
The Application “RIA based e-shopping Portal for Electronic gadgets” is a place where a user can compare the items and get the details of electronic gadgets such as notebooks, Televisions of various brands and user can select any product and check out the product details such as information, features, warranty, price, etc. User needs to enter the range (costs) he want, and/or options which he is searching. Then a list of products will be displayed (with images) on user interface. Here user can buy the products where all the transaction details are stored and even user can view all the transaction, which he/she has done. User needs to enter the range (costs) he want, and/or options which he is searching. Then a list of products will be displayed (with images) on user interface.
Requirements Specification Document:
According to Roger Pressman in Software Engineering: A Practitioner's Approach (McGraw-Hill Publications) [SEPA–1997], the requirement specification document is produced at the end of Analysis of the system. This document is a very comprehensive document & contains all the User requirements & Analysis diagrams.
UseCaseDiagram:
A use case illustrates a unit of functionality provided by the system. The main purpose of the use-case diagram is to help development teams visualize the functional requirements of a system, including the relationship of "actors" (human beings who will interact with the system) to essential processes, as well as the relationships among different use cases.
Use-case diagrams generally show groups of use cases — either all use cases for the complete system, or a breakout of a particular group of use cases with related functionality (e.g., all security administration-related use cases). A use-case diagram is typically used to communicate the high-level functions of the system and the system's scope.
FLEX 5:
Adobe Flex is a software development kit (SDK) released by Adobe Systems for the development and deployment of cross-platform rich Internet applications based on the Adobe Flash platform. Flex applications can be written using Adobe Flash Builder or by using the freely available Flex compiler from Adobe.
Traditional application programmers found it challenging to adapt to the animation metaphor upon which the Flash Platform was originally designed. Flex seeks to minimize this problem by providing a workflow and programming model that is familiar to these developers. MXML, an XML-based markup language, offers a way to build and lay out graphic user interfaces. Interactivity is achieved through the use of Action Script, the core language of Flash Player that is based on the ECMA Script standard.
Adobe Flash Builder:
Adobe Flash Builder (previously known as Adobe Flex Builder) is an integrated development environment (IDE) built on the Eclipse platform meant for developing rich Internet applications (RIAs) and cross-platform desktop applications, particularly for the Adobe Flash platform. Support for cross-platform desktop applications was added in Flex Builder 3 with the introduction of AIR.
Adobe Flash (formerly Macromedia Flash) is a proprietary multimedia platform used to add animation, video, and interactivity to Web pages. Flash is frequently used for advertisements and games. More recently, it has been positioned as a tool for "Rich Internet Applications" ("RIAs").
Rich Internet application
Rich Internet Applications (RIAs) are web applications that have many of the characteristics of desktop applications. These are typically delivered either by way of a site-specific browser (is a software application that is dedicated to accessing pages from a single source (site) on a computer network such as the Internet or a private Internet.), via a browser plug-in, or independently via sandboxes or virtual machines. Adobe Flash, Java and Microsoft Silverlight are currently the three top platforms, with penetration rates around 95%, 80% and 45% respectively. However, as new web standards emerge, the principles behind RIAs stay unchanged in that they serve as the kinetic force behind new forms of Business Intelligence.
RIA background:
At Adobe, we coined the term “rich Internet application” in 2002 when we introduced a major upgrade to Adobe Flash Platform. Since then, we have enabled more RIA sites than any other organization through our products, consulting group and partner network. In 2006, with the introduction of Adobe Flex 2, a new generation of RIAs will be brought to market that are faster, more compelling and easier to build than ever.
RIAs do not replace websites. They work within the framework of an organization’s existing infrastructure to deliver better user experiences and functionality than sites that are solely HTML -based.
The value of RIAs:
Creating and delivering a superior user experience is not merely about making an interface that looks pretty. The look and feel of an application is important and helps retain the user’s focus, but the essence of great user experiences is the ease and efficiency with which the user’s goals are met. In this context, it is important to ensure that RIAs deliver measurable results.
Increased revenue: more online transactions due to speed, task completion rate, and return. For example, when the Broad moor resort (www.broadmoor) introduced its RIA reservation system, it doubled the conversion rate from browser to buyer.
Embedded rich media:
You have probably experienced the excitement of discovering that a favorite movie clip or song is available to be played directly on the web. This enthusiasm is quickly dampened by the need to answer several questions about bandwidth and media player version. After getting through these questions, the desired media usually appears in a separate window. This makes the entire experience awkward and less immersive (and therefore much easier to abandon).
You often do not notice it when you encounter a site with embedded media, however. It feels natural to have audio or video part of an integrated site experience. An example of this is Google video (video.google.com), where a user can play a video directly on the page.
The value of embedded rich media goes beyond entertainment. Many online businesses have discovered the improved customer experience of using rich media to provide in-context guidance, educational content, or simple orienting introductions. Consider the advantage of having audio or video tutorials on the same page as the loan application you are trying to fill out. Night’s line-up, the application returned to the server to fetch a new page. The application was well engineered, so each subsequent page generally loaded in less than three seconds.
Web Service Standards
Web services are registered and announced using the following services and protocols. Many of these and other standards are being worked out by the UDDI project, a group of industry leaders that is spearheading the early creation and design efforts.
Universal Description, Discovery, and Integration (UDDI) is a protocol for describing available Web services components. This standard allows businesses to register with an Internet directory that will help them advertise their services, so companies can find one another and conduct transactions over the Web. This registration and lookup task is done using XML and HTTP(S)-based mechanisms.
Simple Object Access Protocol (SOAP) is a protocol for initiating conversations with a UDDI Service. SOAP makes object access simple by allowing applications to invoke object methods or functions, residing on remote servers. A SOAP application creates a request block in XML, supplying the data needed by the remote method as well as the location of the remote object itself.
Web Service Description Language (WSDL), the proposed standard for how a Web service is described, is an XML-based service IDL (Interface Definition Language) that defines the service interface and its implementation characteristics. WSDL is referenced by UDDI entries and describes the SOAP messages that define a particular Web service.
CONCLUSION
The application will be developed using FLEX Builder 4.5. The user can view different types of electronic gadgets, compares their features and buy the product
Advantages:
• As the project is based on Rich Internet Application the server responsiveness is very fast.
• The user can View different type of electronic Gadgets.
• High graphical user Interface.
• The Application “RIA based e-Shopping Portal for Electronic gadgets” is a place where a user can get the details of electronic gadgets such as notebooks, Televisions of various brands.
• User can select any product and check out the product details such as information, features, warranty, price etc.
• Here user can buy the products where all the transaction details are stored.
• User can view all the transaction which he/she has done.
• The user will be presented with an integrated application wherein he has to enter the price range, features which he is looking at in a mobile.
• The selected products featured details along with the images will be displayed.
The user can even compare the products of two different companies.