Business-to-business (B2B) describes commerce transactions between businesses, such as between

a manufacturer and a wholesaler, or between a wholesaler and a retailer. Contrasting terms are business-to-
consumer (B2C) and business-to-government (B2G).
The volume of B2B (Business-to-Business) transactions is much higher than the volume of B2C transactions. The primary
reason for this is that in a typical supply chain there will be many B2B transactions involving sub components or raw
materials, and only one B2C transaction, specifically sale of the finished product to the end customer. For example, an
automobile manufacturer makes several B2B transactions such as buying tires, glass for windscreens, and rubber hoses
for its vehicles. The final transaction, a finished vehicle sold to the consumer, is a single (B2C) transaction.

Business-to-consumer (B2C, sometimes also called Business-to-Customer) describes activities of businesses serving
end consumers with products and/or services.
An example of a B2C transaction would be a person buying a pair of shoes from a retailer. The transactions that led to the
shoes being available for purchase, that is the purchase of the leather, laces, rubber, etc. However, the sale of the shoe
from the shoemaker to the retailer would be considered a (B2B) transaction.

Cyberlaw is a new phenomenon having emerged much after the onset of Internet. Internet grew in a completely unplanned and
unregulated manner. Even the inventors of Internet could not have really anticipated the scope and far reaching consequences of
cyberspace. The growth rate of cyberspace has been enormous. Internet is growing rapidly and with the population of Internet
doubling roughly every 100 days, Cyberspace is becoming the new preferred environment of the world.
With the spontaneous and almost phenomenal growth of cyberspace, new and ticklish issues relating to various legal aspects of
cyberspace began cropping up. In response to the absolutely complex and newly emerging legal issues relating to
cyberspace,CYBERLAW or the law of Internet came into being. The growth of Cyberspace has resulted in the development of a new
and highly specialised branch of law called CYBERLAWS- LAWS OF THE INTERNET AND THE WORLD WIDE WEB.
There is no one exhaustive definition of the term "Cyberlaw". However, simply put, Cyberlaw is a term which refers to all the legal
and regulatory aspects of Internet and the World Wide Web. Anything concerned with or related to, or emanating from, any legal
aspects or issues concerning any activity of netizens and others, in Cyberspace comes within the ambit of Cyberlaw .

E-commerce (electronic commerce or EC) is the buying and selling of goods and services on the Internet,
especially the World Wide Web. In practice, this term and a newer term, e-business, are often used
interchangably. For online retail selling, the terme-tailing is sometimes used.
E-commerce can be divided into:
 E-tailing or "virtual storefronts" on Web sites with online catalogs, sometimes gathered into a
"virtual mall"
 The gathering and use of demographic data through Web contacts
 Electronic Data Interchange (EDI), the business-to-business exchange of data
 E-mail and fax and their use as media for reaching prospects and established customers (for
example, with newsletters)
 Business-to-business buying and selling
 The security of business transactions

Compare Info Base:

The company is leading provider of e-commerce portals and IT solutions. The company manages about 1500 websites and
portals with 4000 domain names. It has web presence in Maps,Software Development,GIS Travel,Education,Media,Greetings
etc. The company is a significant name in developing and selling E business. It specializes in Content development
services,Website development services,PHP Programming & Development etc.It has its office in Mumbai, Kolkata, San Jose,
Delhi.

HashPro Technologies :

It offers e-business and traditional analysis, development, implementation, design and strategic planning. It is a leader in the
provider of integrated talent management software organization in India. It is key technology consulting provider. It renders
services like the E-commerce Hosting,Internet Marketing,Human Resources. The e-Workforce initiative of the company will
enable the company to become a 100 percent e-Corporation.

ERP (Enterprise Resource Planning) is the evolution of Manufacturing Requirements Planning

(MRP) II. From business perspective, ERP has expanded from coordination of manufacturing
processes to the integration of enterprise-wide backend processes. From technological aspect, ERP
has evolved from legacy implementation to more flexible tiered client-server architecture.

The following table summarizes the evolution of ERP from 1960s to 1990s.

Timeline System Description

1960s Inventory Inventory Management and control is the combination of information
Management & technology and business processes of maintaining the appropriate level of stock
Control in a warehouse. The activities of inventory management include identifying
inventory requirements, setting targets, providing replenishment techniques and
options, monitoring item usages, reconciling the inventory balances, and
reporting inventory status.
1970s Material Requirement Materials Requirement Planning (MRP) utilizes software applications for
Planning (MRP) scheduling production processes. MRP generates schedules for the operations
 and raw material purchases based on the production requirements of finished
goods, the structure of the production system, the current inventories levels and
the lot sizing procedure for each operation.
1980s Manufacturing Manufacturing Requirements Planning or MRP utilizes software applications
Requirements for coordinating manufacturing processes, from product planning, parts
Planning (MRP II) purchasing, inventory control to product distribution.
1990s Enterprise Resource Enterprise Resource Planning or ERP uses multi-module application software
Planning (ERP) for improving the performance of the internal business processes. ERP systems
often integrates business activities across functional departments, from product
planning, parts purchasing, inventory control, product distribution, fulfillment,
to order tracking. ERP software systems may include application modules for
supporting marketing, finance, accounting and human resources.

Most of my entries in this blog have focused on proactive measures that can be taken to ensure ERP or IT success.
However, what happens if you're already in the middle of a failed ERP implementation?
The good news is that troubled IT implementations can be fixed, even if they are way over budget, behind schedule, and
creating great organizational strain. In these types of instances, I often advise clients to reposition their projects as
business improvement projects rather than IT projects.

At this point, you have forget about ERP. During or after a failed implementation, the software is likely creating huge
difficulties. Just the mere mention of the letters E, R, and P probably cause employees to cringe, so it's important to focus
less on ERP per se and more on how you are going to fix your business operations. With this change in mindset, you use
ERP only as necessary to make business improvements to get your organization back on track.

Definition: An entity-relationship (ER) diagram is a specialized graphic that illustrates the interrelationships between
entities in a database. ER diagrams often use symbols to represent three different types of information. Boxes are
commonly used to represent entities. Diamonds are normally used to represent relationships and ovals are used to
represent attributes.
Also Known As: ER Diagram, E-R Diagram, entity-relationship model
Examples:
Consider the example of a database that contains information on the residents of a city. The ER digram shown in the
image above contains two entities -- people and cities. There is a single "Lives In" relationship. In our example, due to
space constraints, there is only one attribute associated with each entity. People have names and cities have
populations. In a real-world example, each one of these would likely have many different attributes.
Suggested Reading

A database is to be designed for a Car Rental Co. (CRC). The information required includes a
description of cars, subcontractors (i.e. garages), company expenditures, company revenues and customers. Cars are to be described
by such data as: make, model, year of production, engine size, fuel type, number of passengers, registration number, purchase price,
purchase date, rent price and insurance details. It is the company policy not to keep any car for a period exceeding one year. All major
repairs and maintenance are done by subcontractors (i.e. franchised garages), with whom CRC has long-term agreements. Therefore
the data about garages to be kept in the database includes garage names, addressees, range of services and the like. Some garages
require payments immediately after a repair has been made; with others CRC has made arrangements for credit facilities. Company
expenditures are to be registered for all outgoings connected with purchases, repairs, maintenance, insurance etc. Similarly the cash
inflow coming from all sources - car hire, car sales, insurance claims - must be kept of file.CRC maintains a reasonably stable client
base. For this privileged category of customers special credit card facilities are provided. These customers may also book in advance a
particular car. These reservations can be made for any period of time up to one month. Casual customers must pay a deposit for an
estimated time of rental, unless they wish to pay by credit card. All major credit cards care accepted. Personal details (such as name,
address, telephone number, driving licence, number) about each customer are kept in the database.

The Systems Development Life Cycle (SDLC), or Software Development Life Cycle insystems engineering, information
systems and software engineering, is the process of creating or altering systems, and the models and methodologies that
people use to develop these systems. The concept generally refers to computer or information systems.

In software engineering the SDLC concept underpins many kinds of software development methodologies. These
methodologies form the framework for planning and controlling the creation of an information system[1]: the software
development process.

Waterfall ModelThis is the most common and classic of life cycle models, also referred to as a linear-
sequential life cycle model. It is very simple to understand and use. In a waterfall model, each phase
must be completed in its entirety before the next phase can begin. At the end of each phase, a review
takes place to determine if the project is on the right path and whether or not to continue or discard the
project. Unlike what I mentioned in the general model, phases do not overlap in a waterfall
model.Waterfall Life Cycle Model Advantages
 • Simple and easy to use.

• Easy to manage due to the rigidity of the model – each phase has specific deliverables and a review
process.

• Phases are processed and completed one at a time.

Disadvantages
• Adjusting scope during the life cycle can kill a project

• No working software is produced until late during the life cycle.

V-Shaped ModelJust like the waterfall model, the V-Shaped life cycle is a sequential path of execution of
processes. Each phase must be completed before the next phase begins. Testing is emphasized in this
model more so than the waterfall model though. The testing procedures are developed early in the life
cycle before any coding is done, during each of the phases preceding implementation.Requirements begin
the life cycle model just like the waterfall model. Before development is started, a system test plan is
created. The test plan focuses on meeting the functionality specified in the requirements gathering.The
high-level design phase focuses on system architecture and design. An integration test plan is created in
this phase as well in order to test the pieces of the software systems ability to work together.The low-level
design phase is where the actual software components are designed, and unit tests are created in this
phase as well.The implementation phase is, again, where all coding takes place. Once coding is complete,
the path of execution continues up the right side of the V where the test plans developed earlier are now
put to use.

Incremental ModelThe incremental model is an intuitive approach to the waterfall model. Multiple
development cycles take place here, making the life cycle a “multi-waterfall” cycle. Cycles are divided up
into smaller, more easily managed iterations. Each iteration passes through the requirements, design,
implementation and testing phases.A working version of software is produced during the first iteration, so
you have working software early on during the software life cycle. Subsequent iterations build on the
initial software produced during the first iteration.Incremental Life Cycle Model Advantages
• Generates working software quickly and early during the software life cycle.

• More flexible – less costly to change scope and requirements.

Disadvantages
• Each phase of an iteration is rigid and do not overlap each other.

• Problems may arise pertaining to system architecture because not all requirements are gathered
up front for the entire software life cycle.

Spiral ModelThe spiral model is similar to the incremental model, with more emphases placed on risk
analysis. The spiral model has four phases: Planning, Risk Analysis, Engineering and Evaluation. A
software project repeatedly passes through these phases in iterations (called Spirals in this model). The
baseline spiral, starting in the planning phase, requirements are gathered and risk is assessed. Each
subsequent spirals builds on the baseline spiral.Requirements are gathered during the planning phase. In
the risk analysis phase, a process is undertaken to identify risk and alternate solutions. A prototype is
produced at the end of the risk analysis phase.Software is produced in the engineering phase, along with
testing at the end of the phase. The evaluation phase allows the customer to evaluate the output of the
project to date before the project continues to the next spiral.In the spiral model, the angular component
represents progress, and the radius of the spiral represents cost