E co World Site design full report
project report tiger|
Active In SP
Joined: Feb 2010
25-02-2010, 10:46 AM
E co World Site.doc (Size: 1.1 MB / Downloads: 80)
E co World. Com
[An ecommerce web application]
Rinu John Vimal K.Viswan
An E-Commerce application become worth if dynamicity as well as it supports online transaction. In spite of much of the E-commerce web sites existing today there are only little hope for Dynamicity. We have tries to make it worth for entertainment, messaging &Knowledge.
EcoWorld.com aims to meet the present days essential online needs. 'EcoWorld.com' focus mainly on Dynamicity. It is a system for managing needs of internet relying peoples.
We try to implement this using the latest technologies in Java. Technology is given at most importance in our project and implimentation. It also consists of forum where the online group can share their knowledge and informations. As a part of entertainment we are providing online gaming where the users can have fun with the latest games available in the market. To make the communication easy between the users EcoWorld includes online chatting and mailing services. Chatting can be personal as well as in a room where different users exist. Mailing has the option for composing and sending it. Bidding is another option we are providing where the users can get the desired product at the cheapest and reliable price. By Resume posting we mean to extend our hands to the job seekers who the job seekers suitable for their need.
The concept of WWW (World Wide Web) can be truly implemented if the Web applications existing are dynamic and able to process online transactions. In spite of much of the E-commerce web sites existing today there are only little hope for Dynamicity. We have also tried to make it worth for entertainment, messaging &Knowledge.
EcoWorld.com is specially developed to meet the present days essential online needs 'EcoWorld.com' focus mainly on Dynamicity. It is a system for managing needs of internet relying peoples.
A usual E-commerce website only aims at sale of their product but we have tried to meet the varying needs of today. We have tried to implement this using the latest technologies in Java. For making it online we are trying to make the transactions using the credit cards (Visa and Master card).To make it a knowledge Repository we have included Forum where the online group can share their knowledge and informations.As a part of entertainment we are providing online gaming where the users can have fun with the latest games available in the market. To make the communication easy between the users EcoWorld has included online chatting and mailing services. Chatting can be personal as well as in a room where different users exist. Mailing has the option for composing and sending it. Bidding is another option we are providing where the users can get the desired product at the cheapest and reliable price. By Resume posting we mean to extend our hands to the job seekers who the job seekers suitable for their need.
We have tried to include the latest features of Java, like jsp, servlets, beans and we have used apache Tomcat server which support above mentioned features of Java. The use of latest technologies helped us to make our web application dynamic and user friendly.
OBJECTIVE AND SCOPE
The online transactions and dynamicity are the unavoidable need today as web users needs are fast and dynamic. EcoWorld meets these purposes to a great extend. This has two kinds of users, Administrator and the guest user. Where the Administrator enjoys all the privileges of Administration. The guest user can access all the features of EcoWorld but he lacks the power of Administration. Each user is provided with a username and a password which is unique. The user can check the use of Ecoworld using his username and password .proper Authentication facility is provided using the username and
EcoWorld can be considered as a package of latest web applications, it includes
> Shopping cart
Shopping cart (EcoWoiid.com) mainly aims at online transactions. Security of user data is given much importance here, this shopping cart is dynamic so that user can make changes during any point of time.
Forum (Ecoforum.com) is useful for those who share information through net. It can be used as a knowledge repository where user share, raise queries online.
Chatting (EcoChat.com) it have both personal as well as chat rooms, it is very user-friendly. User can have secure transfer of message through this. EcoChat reduces the communication gap that exists in the present world.
Ecomail.com, it supports both official as well as friendly purpose. Here also we provide a secure transfer of mails between the users. We try to update this according to user demands.
EcoGame.com, i.e. online gaming provides user access to the online games that exist in the present market the games will be downloaded and put in our site which the user can access
DEFINITION OF THE PROBLEM
It is the need of time to provide online transaction, information sharing in the world which is growing at a high speed. The present web application does not include all the features that we have included in our package. The facility for online transaction and dynamicity are the need of the time. In today's world here is no web application which supports all the features that we have included. Forum, mailing, chatting and online gaming are the added features of EcoWorld.com
The security is another feature we have given importance Here there are two types of users l.Adminstrator and 2.the User where the administrator are given the full privilege over the system .even though user can have access to all the features of EcoWorld.com they have limited access to administration. Ecoworld mainly focus on online transfer of products and information in the web.
Initial investigation is performed for clarifying the problems in detail. It helps us to strengthen our background knowledge about the system. It is the collection of informations that helps to evaluate the merits of the project and implimentation. It also gives a meaningful judgment of the feasibility of the system. Initial investigation
S8, CSE-S'NCjC'E ecoworCd.com
is performed by identifying the users needs for a new system. By this the problems related with the old system are identified and thus those problems were overcome in the new system.
First we identified the need for a new and improved system, because of the unsatisfactory performance of the existing system. An initial investigation is performed to define the problem in detail. Initial investigation means studying the existing system and identifying the need for the new system.
Initial investigation consists of the following:
> Background Analysis >Direct observation
Ã‚Â¦ Background Analysis
Background analysis is carried out in order to become familiar with the LAN environment and the physical processes related to the system and also processes involved in designing a remote database access system were studied in detail.
Ã‚Â¦ Direct Observation
It is carried out in order to identify the limitations of existing system.
A number of discussions with network administrators have been carried out in order to study the existing system.
Ã‚Â¦ Fact finding
After acquiring the background knowledge, processes involved in the system are studied. All the facts that form input to the system are collected.
Presently existing system are not dynamic and thus does not have the support for all the features in EcoWorld.com. All the existing system cannot make changes online, they have only limited facilities. The added features of Ecoworld.com are of great help for its users
Even though there exist many forum. There is no forum wiiich mainly aims at transfer of knowledge. Though the user can access the informations in forum they have limitations for raising queries.
Online gaming which exist now support only their products the new games which is of other developers are not provided in those sites. The mails and online chat in web also have many faults which are removed in our system
LIMITATIONS OF EXISTING SYSTEM
> Is not that Dynamic
> Does not meet the user requirements.
> Information transfer is not that safe in a usual e-commerce site
The online transactions and dynamicity are the unavoidable need today as web user's needs are fast and dynamic. EcoWorld meets these purposes to a great extend. This has two kinds of users, Administrator and the guest user. Where the Administrator enjoys all the privileges of Administration. The guest user can access all the features of EcoWorld but he lacks the power of Administration. Each user is pro\ided with a username and a password which is unique. The user can check the use of Ecoworld using his username and password .proper Authentication facility is provided using the username and password.
In addition to the shopping cart we have included forum, chatting, mailing, online gamming, .etc .This is a combination of all the advanced web features; we have put all this together. The user data is given at most importance in our system, which other system doesn't give.
ADVANTAGES OF PROPOSED SYSTEM
> Supports online transfer of products.
> Suitable in Linux, Windows or any other platform.
> Better management of user information.
> User friendliness.
Feasibility study is a test of a proposed system according to work ability, impact on the organization's ability to meet user needs and effective use of resources. Feasibility study is performed by considering the factors such as development cost, operating cost, response time, development time, accuracy and reliability. Not all requested project and implimentations are feasible .We compare the proposed system with the existing system. In feasibility study we develop more than one solution to solve the existing system problems. From this we can select the feasible one and then we prepare detailed description of that system.
Â¢ Technical Feasibility
The J2ee features helps us to make the system dynamic, all the features which support in the secure information transfer and keeping the user sessions are
Â¢ Operational Feasibility
System is a menu type of program and quite user friendly. Any novice can use the system with a little orientation. Much experience is not required at operational level.
Â¢ Financial and Economical Feasibility
Once it is hosted saves a lot of time and the client can get the request processed with no time.
J 2 EE OVERVIEW
TODAY, more and more developers want to write distributed transactional applications for the enterprise and thereby leverage the speed, security, and reliability of server-side technology. In the fast-moving and demanding world of e-commerce and information technology, enterprise applications must be designed, built, and produced for less money, with greater speed, and with fewer resources than ever before. To reduce costs and fast-track application design and development, the Javaâ€žÂ¢2 Platform, Enterprise Edition (J2EEâ€žÂ¢) provides a component-based approach to the design, development, assembly, and deployment of enterprise applications .The J2EE platform offers a multitiered distributed application model, reusable components, a unified security model, flexible transaction control, and Web services support through integrated data interchange on Extensible Markup Language (XML)-based open standards and protocols. Not only can user deliver innovative business solutions to market faster than ever, but also the platform-independent J2EE component-based solutions are not tied to the products and application programming interfaces (APIs) of any one vendor. Vendors and customers enjoy the freedom to choose the products and components that best meet their business and technological requirements.
Distributed Multitiered Applications
The J2EE platform uses a distributed multitiered application model for enterprise applications. Application logic is divided into components according to function, and the various application components that make up a J2EE application are installed on different machines depending on the tier in the multitiered J2EE environment to which the application component belongs. J2EE Components
Â¢ Client-tier components run on the client machine.
Â¢ Web-tier components run on the J2EE server.
Â¢ Business-tier components run on the J2EE server.
Â¢ Enterprise information system (ElS)-tier software runs on the EIS server.
J2EE multitiered applications are generally considered to be threetiered applications because they are distributed over three locations: client machines, the J2EE server machine, and the database or legacy machines at the back end. Three-tiered applications that run in this way extend the standard twotiered client and server model by placing a multithreaded application server between the client application and back-end storage.
J2EE Application 1
J2EE Application 2
dynamic HTML Pages
J2EE applications are made up of components. A J2EE component is a self-contained functional software unit that is assembled into a J2EE application with its related classes and files and that communicates with other components. The J2EE specification defines the following J2EE components:
Â¢ Application clients and applets are components that run on the client.
Â¢ Java Servlet and JavaServer Pagesâ€žÂ¢ (JSPâ€žÂ¢) technology components are Web components that run on the server.
Â¢ Enterprise JavaBeansâ€žÂ¢ (EJBâ€žÂ¢) components (enterprise beans) are business components that run on the server.
Ã‚Â¦ J2EE components are written in the Java programming language and are compiled in the same way as any program in the language. The difference between J2EE components and "standard" Java classes is that J2EE components are assembled into a .I2EE application, are verified to be well formed and in compliance with the J2EE specification, and are deployed to production, where they are run and managed by the J2EE server.
A J2EE client can be a Web client or an application client.
A Web client consists of two parts:
(1) Dynamic Web pages containing various types of markup language which
are generated by Web components running in the Web tier.
(2) A Web browser, which renders the pages received from the server.
A Web client is sometimes called a thin client. Thin clients usually do not query databases, execute complex business rules, or connect to legacy applications. When use a thin client, such heavyweight operations are off-loaded to enterprise beans executing on the J2EE server, where they can leverage the security, speed, services, and reliability of J2EE server-side technologies.
A Web page received from the Web tier can include an embedded applet. An applet is a small client application written in the Java programming language that executes in the Java virtual machine installed in the Web browser. However, client systems will likely need the Java Plug-in and possibly a security policy file in order for the applet to successfully execute in the Web browser. Web components are the preferred API for creating a Web client program because no plug-ins or security policy files are needed on the client systems. Also, Web
components enable cleaner and more modular application design because they provide a way to separate applications programming from Web page design. Personnel involved in Web page design thus do not need to understand Java programming language syntax to do their jobs.
An application client runs on a client machine and provides a way for users to handle tasks that require a richer user interface than can be provided by a markup language. It typically has a graphical user interface (GUI) created from the Swing or the Abstract Window Toolkit (AWT) API, but a command-line interface is certainly possible. Application clients directly access enterprise beans running in the business tier. However, if application requirements warrant it, an application client can open an HTTP connection to establish communication with a servlet running in the Web tier.
The JavaBeansâ€žÂ¢ Component Architecture
The server and client tiers might also include components based on the Java- Beans component architecture (JavaBeans components) to manage the data flow between an application client or applet and components running on the J2EE server, or between server components and a database. JavaBeans components are not considered J2EE components by the J2EE specification. JavaBeans components have properties and have get and set methods for , accessing the properties. JavaBeans components used in this way are typically simple in design and implementation but should conform to the naming and design conventions outlined in the JavaBeans component architecture.
J2EE Server Communications
The client communicates with the business tier running on the J2EE server either directly or, as in the case of a client running in a browser, by going through JSP pages or servlets running in the Web tier. J2EE application uses a thin browser-based client or thick application client. In deciding which one to use, user should be aware of the trade-offs between keeping functionality on the
client and close to the user (thick client) and offloading as much functionality as possible to the server (thin client). The more functionality you off-load to the server, the easier it is to distribute, deploy, and manage the application; however, keeping more functionality on the client can make for a better perceived user experience.
Figure 1-2 Server Communications
J2EE Web components are either servlets or pages created using JSP technology. Servlets are Java programming language classes that dynamically process requests and construct responses. JSP pages are text-based documentsthat execute as servlets but allow a more natural approach to creating static content. Static HTML pages and applets are bundled with Web components during application assembly but are not considered Web components by the J2EE specification. Server-side utility classes can also be bundled with Web components and, like HTML pages, are not considered Web components. The
Web tier, like the client tier, might include a Java- Beans component to manage the user input and send that input to enterprise beans running in the business tier for processing.
Business code, which is logic that solves or meets the needs of a particular business domain such as banking, retail, or finance, is handled by enterprise beans
running in the business tier.
Web Tier and J2EE Applications
. cit orid.com
Web Browser ^ Web Pages, m Applets, and Optional JavaBeans Components
Application Client and Optional JavaBeans Component* I
F JSP Pages
JavaBeans , Components j : (Optional)
Entity Beans Session Beans
and Legacy Systems
Business and EIS Tiers
There are three kinds of enterprise beans: session beans, entity beans, and message- driven beans. A session bean represents a transient conversation with a client. When the client finishes executing, the session bean and its data are gone. In contrast, an entity bean represents persistent data stored in one row of a database table. If the client terminates or if the server shuts down, the underlying services ensure that the entity bean data is saved. A message-driven bean combines features of a session bean and a Java Message Service (JMS) message listener, allowing a business component to receive JMS messages asynchronously.
Enterprise Information System Tier
The enterprise information system tier handles EIS software and includes enterprise infrastructure systems such as enterprise resource planning (ERP), mainframe
transaction processing, database systems, and other legacy information systems. For example, J2EE application components might need access to enterprise information systems for database connectivity.
Normally, thin-client multitiered applications are hard to write because they involve many lines of intricate code to handle transaction and state
management, multithreading, resource pooling, and other complex low-level details. The component- based and platform-independent J2EE architecture makes J2EE applications easy to write because business logic is organized into reusable components. In addition, the .I2EE server provides underlying sendees in the form of a container for every component type. Because user do not have to develop these services himself, users are free to concentrate on solving the business problem at hand.
Containers are the interface between a component and the low-level platform specific functionality that supports the component. Before a Web, enterprise bean, or application client component can be executed, it must be assembled into a J2EE module and deployed into its container. The assembly process involves specifying container settings for each component in the J2EE application and for the J2EE application itself. Container settings customize the underlying support provided by the J2EE server, including services such as security, transaction management, Java Naming and Directory
Interfaceâ€žÂ¢ (JNDI) lookups, and remote connectivity. Here are some of the highlights:
Â¢ The J2EE security model lets you configure a Web component or enterprise bean so that system resources are accessed only by authorized users.
Â¢ The J2EE transaction model lets you specify relationships among methods that make up a single transaction so that all methods in one transaction are treated as a single unit.
Â¢ JNDI lookup services provide a unified interface to multiple naming and directory services in the enterprise so that application components can access naming and directory services.
Â¢ The J2EE remote connectivity model manages low-level communications between clients and enterprise beans. After an enterprise bean is created, a client
invokes methods on it as if it were in the same virtual machine. Because the J2EE architecture provides configurable services, application components within the same J2EE application can behave differently based on where they are deployed. For example, an enterprise bean can have security settings that allow it a certain level of access to database data in one production environment and another level of database access in another production environment. The container also manages nonconfigurable services such as enterprise bean and servlet life cycles, database connection resource pooling, data persistence, and access to the J2EE platform APIs . Although data persistence is a nonconfigurable service, the J2EE architecture lets you override container-managed persistence by including the appropriate code in the enterprise bean implementation when user wants more control than the default container-managed persistence provides.
The deployment process installs J2EE application components in the J2EE containers
J2EE Server and Containers
The runtime portion of a J2EE product. A J2EE server provides EJB and Web containers.
Enterprise JavaBeans (EJB) container
Manages the execution of enterprise beans for J2EE applications. Enterprise beans and their container run on the J2EE server. Web container
Manages the execution of JSP page and servlet components for J2EE applications. Web components and their container run on the J2EE server.
Application client container
Manages the execution of application client components. Application clients and their container run on the client. Applet container
Manages the execution of applets. Consists of a Web browser and Java Plug-in running on the client together. Web Services Support
Web services are Web-based enterprise applications that use open, XML-based standards and transport protocols to exchange data with calling clients. The J2EE
XML is a cross-platform, extensible, text-based standard for representing data. When XML data is exchanged between parties, the parties are free to create their own tags to describe the data, set up schemas to specify which tags can be used in a particular kind of XML document, and use XML stylesheets to manage the display and handling of the data. For example, a Web service can use XML and a schema to produce price lists, and companies that receive the price lists and schema can have their own stylesheets to handle the data in a way that best suits their needs. Here are examples:
Â¢ One company might put XML pricing information through a program to translate the XML to HTML so that it can post the price lists to its intranet.
Â¢ A partner company might put the XML pricing information through a tool to create a marketing presentation.
Â¢ Another company might read the XML pricing information into an application for processing.
SOAP Transport Protocol
Client requests and Web service responses are transmitted as Simple Object Access Protocol (SOAP) messages over HTTP to enable a completely interoperable exchange between clients and Web services, all running on different platforms and at various locations on the Internet. HTTP is a familiar request-and response standard for sending messages over the Internet and SOAP is an XML based protocol that follows the HTTP request-and-response model.
The SOAP portion of a transported message handles the following:
Â¢ Defines an XML-based envelope to describe wrhat is in the message and how to process the message
Â¢ Includes XML-based encoding rules to express instances of application defined data types within the message
Â¢ Defines an XML-based convention for representing the request to the remote service and the resulting response
A J2EE application is delivered in an Enterprise Archive (EAR) file, a standard Java Archive (JAR) file with an .ear extension. Using EAR files and modules makes it possible to assemble a number of different J2EE applications using some of the same components. No extra coding is needed; it is only a matter of assembling (or packaging) various J2EE modules into J2EE EAR files. An EAR file contains J2EE modules and deployment descriptors. A deployment descriptor is an XML document with an .xml extension that describes the deployment settings of an application, a module, or a component. Because deployment descriptor information is declarative, it can be changed without the need to modify the source code. At runtime, the J2EE server reads the
deployment descriptor and acts upon the application, module, or component accordingly.
There are two types of deployment descriptors: J2EE and runtime. A J2EE deployment descriptor is defined by a J2EE specification and can be used to configure deployment settings on any j2EE-compliant implementation. A runtime deployment descriptor is used to configure J2EE implementation-specific parameters. For example, the Sun Java System Application Server Platform Edition 8 runtime deployment descriptor contains information such as the context root of a Web application, the mapping of portable names of an application's resources to the server's resources, and Application Server implementation-specific parameters, such as caching directives. The Application Server runtime deployment descriptors are named sun-module Type, xml and are located in the
same directory as the J2EE deployment descriptor.
Resource dapter Module
EAR File Structure
A J2EE module consists of one or more J2EE components for the same container type and one component deployment descriptor of that type. An enterprise bean module deployment descriptor, for example, declares transaction attributes and security authorizations for an enterprise bean. A J2EE module without an application deployment descriptor can be deployed as a stand-alone module.
The four types of J2EE modules are as follows:
Â¢ EJB modules, which contain class files for enterprise beans and an EJB deployment descriptor. EJB modules are packaged as JAR files with a .jar extension.
Â¢ Web modules, which contain servlet class files, JSP files, supporting class files, GIF and HTML files, and a Web application deployment descriptor. Web modules are packaged as JAR files with a .war (Web archive) extension.
Â¢ Application client modules, which contain class files and an application client deployment descriptor. Application client modules are packaged as JAR files with a .jar extension.
Â¢ Resource adapter modules, which contain all Java interfaces, classes, native libraries, and other documentation, along with the resource adapter deployment descriptor. Together, these implement the Connector architecture for a particular EIS.
Resource adapter modules are packaged as JAR files with an .rar (resource adapter archive) extension.
> That all about the front end,the Backend we have used is MYSQL which is very user friendly.it is supported in all the platforms.the connection . between the front end and back end is established as given below. JDBC (Java Database Connectivity)
Java Database Connectivity classes are Java classes that allow an application to send sql statement to a DBMS system and retrieve the results. One of the JDBC's strength is inter- operability- a developer can create JDBC applications without targeting a specific DBMS.
Analysis is the detailed study of various operations performed by a system and their relationships within and outside of the system. Once the problem is identified, we must find how to solve the problem. Detailed analysis of the system is done and various modules to be implemented in the system are studied in detail.
The new system is being developed with the following features Login check for both users and administrator
Online transfer of products and information
Secure transfer of information
Dynamic updating Online gaming.
Input design is the process of converting user inputs into computer-based format. Input data is collected and organized into groups of similar data. The goal behind designing input data is to make the data entry easy and make it free from logical errors. Example: The input entry to all type of clients is the user name and password. If they are valid the client is allowed to enter into the software.
> To achieve the highest possible level of accuracy.
> To ensure that the input is acceptable and understandable.
The different types of components that come under this application are:
2. search for product
3. validation of data.
4. secure transfer of information in chatting and
5.user updating dynamically 6.credict card transaction 7.session keeping
Here the user of Ecoworld gets the confirmation online and by door delivery of product outputs are the most important and direct source of information to the user. Efficient and eligible output design should improve the system's relationship with the user and help in decision making. Output design generally deals with the results generated by the system. In this system output
design for forum, chat and mailing ensures secure data transfer between the users.
The general theme behind a database is to handle information as an integrated whole. A database is a collection of interrelated data stored with minimum redundancy to serve many users quickly and efficiently. The general objective is to make information access easy, quick, inexpensive and flexible for the user. The concept behind a database is an integrated collection of data and pro\ides a centralized access to the data from the program. While designing database, several objectives must be considered:
> Controlled Redundancy
> Data Independence
> More information at low cost
> Accuracy and Integrity
> Privacy and Security.
The. different tables that this shopping cart has to maintain are:
1. Card types tables
2. Categories tables
3. Editorial categories Table
4. Editorials Table
5. Items Table
6. Members Table
7. Orders Table
l. CARD TYPES TABLES
Primary key: id
This table is maintained to have a detail of all the card that has been used
Table Name: card_type
Field Name Data Type Size
Name Character 20
Id Number 30
2. CATEGORIES TABLES
Table Name: categories
This table is maintained to for storing the categories of products.
Primary key: Category_id
Field Name Data T\pe Size
Name Character 20
Category_id Number 1
3. EDITORIAL CATEGORIES TABLE
This table is maintained to for storing the editorial categories. Table Name: editorial_categories Primary key: Editorial_cat_id
Field Name Data Type Size
Editorial_cat_name Character 20
Editorial_cat_id Number 1
4. EDITORIALS TABLE
This table is maintained to for storing the editorials available
Table Name: editorials Primarv kev: article_id
Field Name Data Type Size
Editorial_cat_id Number 3
Article_id Number 3
Article_title Character 20
Article_desc Character 50
Item_id Number 3
5. ITEMS TABLE
This table is used for storing the details of items.
Table Name: items Primary key: item_id
Field Name Data Type wSize
item_id Number 3
Category _id Character 20
Name Character 50
Auther Character 30
Price Character l
Product_url Character 20
Image_url Character 20
Notes Character 50
Is_rcommended boolean 1
Rating number 5
Rating_count number 5
6. MEMBERS TABLE
This table is used to store the details members
Table Name: members Primary key: member_id
Field Name Data Type Size
Member_login Character 30
member_id Number 3
Member_level Character 30
Member_password Character 30
First_name Character 30
Last_riame Character 30
Email Character 30
Phone Character 30
SS, CS'E-S'MjQE ecoworW.com.
Address Character 30
Notes Character 30
: Card_type_id Number 3
Card_number Number 3
7. ORDERS TABLE
This table is used to store the orders placed by the clients.
Table Name: orders Primary key: order_id
Field Name Data Type Size
order_id Number 3
Member_id Number 3
Item_id Number 3
Quantity Number 3
The table that the forum used is
This is used for storing the messages in the forum.
Table Name: messages Primary key: message_id
Field Name Data Type Size
message_id Number 3
Message_parent_id Number 3
cat_id Number 3
Topic Character 30
Author Character 30
Message Character 30
Date_entered date -
> PERT CHART
Project Evaluation and review Technique is a management and planning tool that uses a graphical display called a network to show relationship between activities and events.
ACTIVITY DURATION (WEEKS) DESCRIPTION
Act a l Site Observation
Actb l Findinguser requirements
Act c 2 Defining the problems
Actd 1 Output design
Act e 2 Input design
Actf 2 Data Base design
Act g 1 H/w and S/w selection
Acth 4 Program coding
Act i 2 Debugging & Testing
Act j 2 Implementation
Implementation is an activity that is foreseen throughout the development phase. It is a process of bringing a developed system into operational use and turning it over to the user. The new system and its components are to be tested in a structured and planned manner. A successful system should be delivered and users should have confidence that the system would work efficiently and effectively. The more complex the system being implemented the more involved will be the system analysis and design effort required for implementation. The implementation plan involved the following:
Testing to confirm effectiveness Detection and correction of errors
Making necessary changes so as to satisfy the requirements
"EcoWorld" is developed at Sree Narayana Gurukulam Engg College Campus.
Operating system. : Linux /Win XP/ Win 2000/Win 98
Front end. : Java-.l2EE
Backend. : MYSQL
Processor. : Pentium (III) or higher
Memory. : 128 MB
Hard Disk Capacity.: 8GB Hard Disk or more
MAINTENANCE AND EVALUATION
Maintenance is an unavoidable factor, in a software engineering. It is the process of managing the changes made in the software. Once this is hosted, the application is used for many years. However, the users may change. Therefore the application will have to be undoubtedly maintained. Modification and changes will be made to the software, files or procedures to meet emerging user requirements. Since the credit card transaction is not implemented now it is not ready for such transactions. Usually once the system is implemented, the software developers and the customer would sign a contract. According to the time mentioned in the contract, all errors and requirements would be done free of cost. Once the maintenance period is over all the logical errors will be corrected free of cost were as all extra requirements would be charged.
During the contract period we would frequently visit the site and check the system performance such as response time and also how it works at peak hours. If any problem is found if is corrected. EVALUATION
Our system the system is not implemented in a real environment Since credit card subscription rates are much high. Since the existing system is manual, if the newly developed system is implemented actually, it would be very much helpful to the web users as it saves a lot of time.
COST AND BENEFIT ANALYSIS
Cost benefit analysis is a procedure that gives a picture of the various cost benefits and rules associated with a system. The determination of cost and benefits entails the following steps.
A system is expected to provide benefits. The first task is to identify each benefit and then assign a monitory value to it for cost/benefit
analysis. The major benefits are online transaction, entertainment, closed group communication and dynamicity. The performance category emphasis secure transaction of money and information also access to the system by authorized users. Minimizing through an efficient system, error control or reduction of time and also measured and included in cost/benefit analysis.
Estimated cost for system development
Software Development Cost- Rs 20,000
Web Hosting Charge Rs 1,000
Credit card charges Rs 20000
Yearly charges Rs 1,000
The group of pupils benefited from our project and implimentation includes a wide range. Shopping cart is a great help for the group interested in online transactions.Ecochat reduces communication gap that exist in the present world.Ecomail supports official as well as friendly messaging .online gaming is mainly for fun.. The overall benefit is mainly the customer satisfaction.
DETAILED LIFECYCLE OF THE PROJECT
This web Application has the following major parts:
Ã‚Â¦ Administrator side operations.
Ã‚Â¦ User side operations.
Administrator side operations:
l.processing user inputs 2.user Authentication 3.Registering new users 4.validate data entry 5.View ,Edit items 6.Delete User 7.Handling User Orders 8.Setting User Permissions 9.data security
User side operations:
2. product search
3. Adding products to the cart 4.user registration
5.creation of new thread in forum 6.user responses
7. online chat
9. Online Game
METHODOLOGY USED FOR TESTING
Software test is a critical element of software quality assurance and represents the ultimate review specification, design and coding. System testing makes a logical assumption that all of the parts of the system are correct; goal will be successfully achieved.
1. Testing is a process of executing a program with the aim of finding an error.
2. A good test case is one that has a high probability of finding an error that is not
3. A successful test is one that uncovers an error that is not yet discovered.
Unit Testing focuses on verification efforts on the smallest unit of software design of the module. This is also known as 'Module Testing'. This testing was carried out during programming stage itself. In this step each module is found to be working satisfactorily as regards to expected output from the module.
Integration Testing is a systematic testing for constructing the program structure, while at the same time conducting tests to uncover the errors associated with the interface. The objective is to take the tested unit module and build a program structure. All the modules are combined and listed as a whole. Here corrections are difficult because the vastness of the program complicates the isolation of cause, thus in the integration step, all the errors uncovered are corrected for the next testing step.
Validation succeeds when the software functions in a manner that can be reasonably expected by the customer.
No system will be useful if it does not produce the user required output in the specified format. The output generated while the system was under construction is compared with the format suggested by the user.
- . Ã‚Â«... TTIM.tmnmtmmm
Frie Edil View favorites Took Help
V Ã‚Â«8 -
HTML & Web design
D V Mil WfMMMlt
MySQL & PHP From Scratch Wade Maxfield
To gel inside C#. Microsoft's new OO progismmmg language, use A Preview of C# as a guide 11 offers a preview of Visual Studio NET and an overview of the NET framework. and demonstrates how C# is integrated with ASP + , ADO+, and COM* in .NET applications You'll get examples ofC#m action, too
Fhc Edit View Favorites Took Help
This dynamic site was generated w.iT-1
i Local Ã‚Â»Ã‚Â¦*<-Ã‚Â»,Ã‚Â»'-
Ã‚Â«te VÃ‚Â»w Favoijres Tool* Help
i^B*.k - 3 *^ Z. J Search ^jj^ FÃ‚Â«vor*e* ^P*"Ã‚Â¦
Ad* Ã‚Â«Ã‚Â¦-.; 4g hrte://loca^st:8060rtwoWixe/AcÃ‚Â»Ã‚Â«fV-WÃ‚Â»o.t5P
vjsÃ‚Â«Ã‚Â«rchWob ,^ Sj* gg* fjj) j Ã‚Â£D_Mal.Ã‚Â» .Ã‚Â®MyYÃ‚Â«hool
Members Orders View All Items Categories Editorials
Editorial Categories Card Types
Tfli3 dynamic site was generated with
. FIE EÃ‚Â« VtoM Favortei Took Hdp
! Ã‚Â©BÃ‚Â«k Â¢ O ' B iÃ‚Â«! *i,'Â¢Â¢Ã‚Â»Â¢Â¢Ã‚Â» ^r'Ã‚Â«Ã‚Â»Ã‚Â«Ã‚Â« â€šÂ¬> ad Â¢ BÃ‚Â£1 ^ -ft
Enter Ml or partial login, first or last name
Name I f Search ]
Members1 oqm Maitm ' >*s1 Nvmt
admin Adm nistrator Account Administrator
dd rJ 'l Membei
febir- tl Member
quest A:" r ount Mr-mbei
pnya pnya N Membei
nnu nnu |r,hr, Member
virnal virna kv Member
*^ Local ntranet
E* P*voÃ‚Â«w Tod* wp
O8** Â¢ o - a ft e & as - y aa
i i tfi localYÃ‚Â»t:e060/bookstorVOrdersGrrd.tsp v' E3 50
Web Database Development : Step by Step Programming Perl (3rd Edition)
Perl and CGI for the World Wide Web: Visual QuickStart Guide
Edit Flash 4 Magic (WITH CD-ROM) Edit
MySQL (OTHER NEW RIDERS) PHP and MySQL Web Development MySQL & PHP From Scratch MySQL and mSQL
Web Application Development with PHP 4.0 (with CD-ROM)
| Edit Beginning ASP Databases
Larry Wall, Tom Christiansen, Jon Qrwant Elizabeth Castro Paul DuBois
Luke Welling, Laura Thomson Wade Maxfield
Randy Jay Yarger, George Reese, Tim King
David J. Emberton, J. Scott Hamlin, David Emberton
Tobias Ratschiller, Till Gerken
John Kaufman, Thearon Willis, David Buser, Kevin Spencer, kauffrnan, John KaurTman
39.99 Databases Yes
39.96 Programming No
15 19 Programming No
39 99 Databases No
39.99 Programming No
23 99 Programming Yes
27.96 Databases Yes
36 HTML & Web design No
36 Programming No
39.99 Databases Yes
Ffa Edtf view Favorites Too**
- - Ã‚Â¦ too /Awthe** hi>n,,Nviv'.>n/vJ4L*o>ir*Ã‚Â«Ã‚Â«ki ti;
HTML & Web design
Fite E* view Favorites Tod* rlnÃ‚Â»
^PHuUwto ' & Music * C|iMyWeto> >
oÃ‚Â« - o Ã‚Â¦ a 11 ft p*Ã‚Â«> *r"Ã‚Â»Ã‚Â«Ã‚Â« â€šÂ¬>! & as Â¢ B Ã‚Â£1 4
*3ff ' ! v j Search Web Â¢ ij$ ' i* 'Mail Ã‚Â» >^ My Yahoo I Â¢ C^Answers. ' J^r,
Thi* dynamic site was g*Ã‚Â»nÃ‚Â«iat*Ã‚Â»ct with
First Name vimal
Last Name kv
'i i ,
Umiajts ititUu z item Piif* Quantity JtuiM
Details 4 Professional Java Server Programming J2EE Edition 47.99 1 47.990001E78467
FU- E* Vtew Pevontas Tools rvMp
Back Â¢ iÃ‚Â»] )2jj[j fj%, Search ^ Favor*e* ^> Ã‚Â£
Ã‚Â¦5Ã‚Â» Ã‚Â« Â¢ u Ã‚Â£1 *3S
vimel0^7<agfT>o.l.corri sree 8hoilom.kan|irametftom.emakjjlem 04842741766
Credit Card Type American Express
Credit Card Number r.14765EG4236
Re9'sle' I i ConceM
Current Rating Not rated yet
Your Rating Deficient
file Edit Vtew Favorites Tools Help
O**: 6 a Ã‚Â£ "*Ã‚Â«-* e-f>& ai - a *
t(Ã‚Â«ni* fotifnt: 36
Pretittct 100'! Web Site Construction Tips and Tricks Company Richard Schwartz, Kris Jamsa, D. Runnoe Connally Prlc* 39.95 Category HTML & Web design
<cvvcv> nbnbnbnb <cvvcv> nbrinbrnn <cvvcv> tanbbn
Ã‚Â¦ * 'Ã‚Â¦ - Ã‚Â¦)..Ã‚Â¦Ã‚Â¦Ã‚Â¦Ã‚Â¦: - a-, ,.Ã‚Â¦,>...:Ã‚Â¦-Ã‚Â» Ã‚Â¦-(Ã‚Â¦:, <6 IOQ-J cvcvcvc
M<;r>SÃ‚Â«3Ã‚Â» ; heHool Seoi! to AM Users
:-.'.fhj*r.t Ã‚Â¦ ..7H.Ã‚Â«Ã‚Â«!Ã‚Â»
r â€ Ã‚Â¦ Ã‚Â¦ Ã‚Â¦ Ã‚Â¦ Ã‚Â¦ ^â€žÂ¢ "' Ã‚Â¦ Ã‚Â¦ m
3 Private Chat Board Microsoft Internet Explorer a
1 Message : jhelloooo rj Chatroom : computer
Send to : rj close this window Subject : software
Messages sent from tn/s window are private. p : : Ã‚Â¦ . : ji.y : ' ^
Login : [system
File Ed* view Favorites Took Help
<*Â¢Â¢* Â¢ -3 id lj fi p*-* -fcÃ‚Â«wtÃ‚Â« (3- al Â¢ U iJ **'
# Open Ã‚Â« chntraom
# Backup fiiatronms
- Setup parameters to open a chatroom -
.placement j placement!
Name : Subject : Max. users ; Display mode :
I Bufferad-f ramed (JSP) v
Ã‚Â¦P SearchWeto * _ G tÃ‚Â£*- Ã‚Â£|* (J) j QÃ‚Â»W Ã‚Â» Ã‚Â©MyYahoot * QjtaMw* Â¢ a^Games - ^pHoUobs ' ft Musk
My Web *
* Open a chat room
Â¢T Mods nil nrv
* H(irkii|i r.hntrnom*;
* i oqmit
- echochat Moderators -
RomovR moderator T Update moderator
Username (loqin) ;
Cmail : vhmaiCid'fagrriaii.eorn
Password : Â¢Â¢Â¢
Confirm password :
Flip CdK Vl*vÃ‚Â» tÃ‚Â»VM^'. Tool* H*lp t hit
MÃ‚Â«* Â¢ iJ^Myyahooi - Q Answer* - ii
\> Musk: - i"Ã‚Â£ My wet. -
Pie Ed* ^ Back
Search * 4*0*1". X;
""ST * ^* Search web Ã‚Â»
.Mail Â¢ i^htyvahooi Ã‚Â» iyi Answers Ã‚Â» a^^me^ Â¢ t^HotJobs Â¢ Ã‚Â£*Musie - L>MyWebÃ‚Â» J>
eo. Ã‚Â¦ . HPS
iHnimrl JN.-w Tliri-a.ll
Add New Thread
topic world cup Author jfebin
.lust 3 days tc gc |
This dynamic site was generated with FeViRi Soft
I Suhmit j
* j Local intranet
Hie EdK View Favorites Tools Help
Ã‚Â©Beck - LWJ g) ft >.> Search ^Favorites ! *
"Vf * <* [""" v Search Web - > jfc' Ã‚Â® C." .
Ã‚Â§& Ã‚Â«s -a
From Email nnu|ohn00@gmaii com To wtmÃ‚Â«l047Ã‚Â®gmoil com
! From Name t^rinu
Attar hrnrnts | Add/Romciv> Attachments j
p iw SESSB
J Return receipt
Send i j Cancel
FBe Ed* View Favor**
Ã‚Â¦^"f Ã‚Â» v search Web * - 0 ..'.Maii * '^My Yahooi ' ^Answers - ^Games * ^HotJobs * 0 Music * C^MyWeb-
'-<Ã‚Â¦ Back to corarjojer
Select a file to attach ;
: X-ouini*r,i:- Ã‚Â»r,.j **n.r.c|V\uÃ‚Â«eAOe^op\bi Â¢ BiOÃ‚Â«*e I | -.n.i..t. | â€ t-iz-i$i5$ attachmerits â€
j Remove j
Total size : 1248 5 KB
iraM.iisÃ‚Â«nd.r e Copyright FfVl^i <rft 2006-2008
*vf Local intranet
The main aim of developing this web package is to provide online transaction and have all the benefits of the web used in full extend. User friendliness is a must that we have given much importance Other important requirements of software are data security, extensibility and maintainability. All these features are included in this software.
. The project and implimentation greatly helped in understanding the various phases in website development
and exposure to a new programming language J2EE and database MYSQL.
Â¢ The Complete Reference: Java J2SE 5 Edition, Herbert Schildt
Â¢ Java 2 : A Beginner's Guide,Herbert Schildt
Â¢ The Complete Reference: Java J2EE