| framwork [message #181100] |
Sat, 13 April 2013 11:42  |
pankaj21pathak
Messages: 1
Registered: April 2013
Karma: 0
|
Junior Member |
|
|
|
kindly suggest me which is best framework for erp development.
|
|
|
|
| Re: framwork [message #181101 is a reply to message #181100] |
Sat, 13 April 2013 12:15  |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 4/13/2013 7:42 AM, pankaj21pathak(at)gmail(dot)com wrote:
> kindly suggest me which is best framework for erp development.
>
That's like asking "What is the best car for getting to work?". Way too
many variables.
But this is a poor place to ask, anyway. People here for the most part
don't use frameworks, and those who do almost always use just one, with
little or no experience in any other framework. This means you'll get
their favorite one, whether it will fit your needs or not.
It would be much better to ask in an erp-related newsgroup.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
| Re: framwork [message #181104 is a reply to message #181100] |
Sat, 13 April 2013 19:52 |
Michael Vilain
Messages: 88
Registered: September 2010
Karma: 0
|
Member |
|
|
In article <a1ada2b3-ac77-40ef-9d2b-d738142e2d94(at)googlegroups(dot)com>,
pankaj21pathak(at)gmail(dot)com wrote:
> kindly suggest me which is best framework for erp development.
Depends on the customer needs. Do you have a functional spec? How will
you know 'the best framework' if you don't know what the customer wants?
Maybe you should do a per-project to write the spec for them, then bid
on developing it. Or they can shop it around and see if they can get it
done more cheaply in China or Pakistan rather than India.
--
DeeDee, don't press that button! DeeDee! NO! Dee...
[I filter all Goggle Groups posts, so any reply may be automatically ignored]
|
|
|
|
| Re: framework [message #181110 is a reply to message #181100] |
Sun, 14 April 2013 08:36 |
Tony Marston
Messages: 57
Registered: November 2010
Karma: 0
|
Member |
|
|
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(at)gmail(dot)com wrote in message
> news:a1ada2b3-ac77-40ef-9d2b-d738142e2d94(at)googlegroups(dot)com...
> kindly suggest me which is best framework for erp development.
|
|
|
|
| Re: framework [message #181113 is a reply to message #181110] |
Sun, 14 April 2013 12:53 |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 4/14/2013 4:36 AM, Tony Marston wrote:
> 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.
>
Yes, but then you never did define things the same way as the rest of
the world.
> 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).
>
ALL of your "front ends" are restricted - by your lack of ability.
> 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.
>
And some organizations do it the right way. But you wouldn't know what
that is.
And "designing and developing ... for several decades"? You've been
cheating your clients for that long. Everything I've ever seen you
publish has been crap.
> 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).
>
No, you haven't. You've developed a bunch of crap and called it an ERP
application. It didn't contain even 5% of what a REAL ERP application does.
> 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:
>
He's better off not trying to duplicate what you've done, but to do it
right.
> 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
>
Plugging your crap site again, Tony? Even your "opinions" show just how
stooped you are.
> I hope this helps.
>
Yes, this is the best help he could get - on exactly what NOT to do.
>> pankaj21pathak(at)gmail(dot)com wrote in message
>> news:a1ada2b3-ac77-40ef-9d2b-d738142e2d94(at)googlegroups(dot)com...
>
>> kindly suggest me which is best framework for erp development.
>
And don't top post, stoopid.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]