I am not talking for a lack of training or knowledge of the functions embedded into the application...
I am talking rather for a specific end user attitude, when a new (or even a regular) task demands an action, first intent usually is to grab a piece of paper or open an Excel spreadsheet, and spend hours exporting, copying/pasting or hand rewriting data from the computer monitor of the costly "Company's ERP master database" down to, non-standardized form.
Such an attitude, by me, is an indicator for poor business software design and/or implementation. It is easy to blame the end user for not knowing enough how to do its job effectively, but is not as easy to make the product to be an "Ultimate Application" and to suit better organizational business model and culture.
This blog is intending to create base guidelines from which an ultimate application could be developed. The general manufacturing area is Injection Plastic Molding, specifically tasks related to Quality Department duties ...
During this process the more formal definition of ultimate business application should be developed and marketing ...
Close to the topic, copied below is a text from Wikipedia (talk section)...
Would be nice to have some more info regarding:
1. Is custom software owned by the sponsor or is it licensed by the software developer? I believe it would be determined by a contract between the developer and the sponsor. In lieu of a contract then both parties would have a legal claim of ownership. A contract is typically a license to use the custom software under an EULA. But there is more to it I am sure.
2. If a software developer writes the custom software for a sponsor/company, do they have a legal obligation to maintain it and provide a warranty? Again probably determined by a EULA but what happens when there isn't one? How do the laws of the land effect things when there is no EULA and also when there is an EULA.
3. If the author of the custom software is a contractor to the customer i.e. the customer got an external company/contractor to write the custom software, is the author liable for or legally bound to the custom software?
4. Does the author as an employee of the sponsor whom develops the custom software for the company have any rights of ownership (e.g. intellectual property)? Can the author develop that software into a product and register patents for it etc. Should the author sign a contract with the company relinquishing any ownership rights?
5. What is the status quo and legal position in regard to the above?
6. Exactly how is custom software treated differently with respect to packaged software from the sponsors perspective and the developers perspective?
Signed Coder —Preceding unsigned comment added by 220.237.52.243 (talk) 19:42, 28 February 2008 (UTC)
