Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.php > #9054

Re: framework

Show all headers | View raw

Is this ERP application going to have a web front end? Whether it does or 
does not I would always define an ERP application as being a back-end 
administrative application which has restricted access. A front end website 
on the other hand is open to all members of the public.

The other major difference is that a front-end website is fairly restricted 
in what it does - display products and accept orders - whereas the back-end 
application has to do everything else. This "everything else" covers the 
maintenance of the product details as well as order processing (also known 
as order fulfilment, logistics, or supply chain management).

Some organisations build the front and back end applications as separate 
applications which do not share any code, only the database. Sometimes this 
is because they develop each in a different language, or they use different 
development teams which do not talk to each other. I have been designing and 
developing these back-end applications for several decades, and I now 
develop them in PHP. This enables me to create a web front-end in the same 
language, but this in itself is not good enough. What you really need is an 
application architecture which allows components to be easily shared, and 
the best architecture for this (IMHO) is the 3 Tier Architecture (3TA). This 
has separate components in each of the Presentation, Business and Data 
Access layers. Some people seem to think that the only benefit of the 3TA is 
that you can change the Data Access component so that you can switch to 
another DBMS, but what they fail to notice is that you can also change the 
Presentation layer to give another view or window into the same code base. 
This means that you can develop your back-end application with its own 
Presentation, Business and Data Access layers, then build a front-end 
website consisting of nothing more than a different Presentation layer which 
shares the Business and Data Access layers of the back-end application.

I have actually built a commercial ERP application as a package which is now 
being used by several different organisations which sell different 
products - custom jewellery, baby clothes, and photographic prints - each 
with their own unique front-end websites but each sharing the same back-end 
application (but different copies).

To duplicate what I have done you need a framework which specialises in 
back-end applications, not front-end websites, and which utilises the 3 Tier 
Architecture. It should also include a mechanism for Role Based Access 
Control, Audit Logging, and perhaps a Workflow system. All this is explained 
in the following documents:

Why you should build your web application back-to-front - 
http://www.tonymarston.net/php-mysql/back-to-front.html
What is a Framework? - 
http://www.tonymarston.net/php-mysql/what-is-a-framework.html

I hope this helps.

> pankaj21pathak@gmail.com wrote in message 
> news:a1ada2b3-ac77-40ef-9d2b-d738142e2d94@googlegroups.com...

> kindly suggest me which is best framework for erp development. 

Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

framwork pankaj21pathak@gmail.com - 2013-04-13 04:42 -0700
  Re: framwork Jerry Stuckle <jstucklex@attglobal.net> - 2013-04-13 08:15 -0400
  Re: framwork Michael Vilain <vilain@NOspamcop.net> - 2013-04-13 12:52 -0700
  Re: framework "Tony Marston" <TonyMarston@hotmail.com> - 2013-04-14 09:36 +0100
    Re: framework Jerry Stuckle <jstucklex@attglobal.net> - 2013-04-14 08:53 -0400

csiph-web