RE: Manufacturing programs/er needed.
Dan...
I'm not sure that this will help... but i am offering it in the hope that it will.
I have been developing applications for over 20 years and the following has been my experience w.r.t. the overall picture of app dev (painted with VERY large brush strokes):
I am assuming that the app that you want tracks/facilitates your mainline business... ie is going to be a reasonably complicated app for a small well defined business... ie it is not just a small sideline app to track non-critical sideline information.
1) Most applications that are developed for mainline purposes in small to medium sized companies CANNOT be developed by someone who has NOT been extensively trained (school or experience)... an inexperienced 'developer' using Alpha can create small, personal apps but I would not trust my mainline business App development to this process;
2) ~80% of the App developement challenge is creating A) the Functional Specifications (a 'black-box' illustrating data inputs and outputs ie 'what does this thing do) and B) The Design Specifications ('what does this thing look like'?... 'how do people interact with it?... what do they see?'
3) The role of Specification Writer (at some levels a.k.a. 'knowledge engineer') is not trivial and is often assigned to an experienced professional. However, based on what you described, i am pretty sure that you, as the main player (since you know the business rules and procedures), assisted by the developer can produce these Specifications.
4) Specification writing takes MOST of the time devoted to the development of an app... be prepared to put in MANY hours learning how to do this and then doing it... In the long run, it will pay off !!! Otherwise, you (and the unfortunate developer) are likely to be caught in the dreaded 'bottom-up' app dev cycle... ie the development of the app 'evolves'... usually forever... or until folks run out of money and patience!
5) After you are sure that the Specs are solid... THEN start paying for the coding...
The Specs are the mechanism by which you communicate your businnes process to the developer... if you have ever created an ISO9000 Quality System you will see the similarities... Say what you do Do what you say... in such a manner that an auditer, inexperienced with your business can conduct a reasonable audit. The app developer is like the auditor and the Specs are like the Quality Manual and The Procedure Manual. The SOPs are like the actual code... (sort-of).
Sorry if this sounds daunting... but better to go in with your eyes open. It's a question of 'pay me now... or pay me later'... you won't like the latter option!
... for what it's worth!
David
Dan...
I'm not sure that this will help... but i am offering it in the hope that it will.
I have been developing applications for over 20 years and the following has been my experience w.r.t. the overall picture of app dev (painted with VERY large brush strokes):
I am assuming that the app that you want tracks/facilitates your mainline business... ie is going to be a reasonably complicated app for a small well defined business... ie it is not just a small sideline app to track non-critical sideline information.
1) Most applications that are developed for mainline purposes in small to medium sized companies CANNOT be developed by someone who has NOT been extensively trained (school or experience)... an inexperienced 'developer' using Alpha can create small, personal apps but I would not trust my mainline business App development to this process;
2) ~80% of the App developement challenge is creating A) the Functional Specifications (a 'black-box' illustrating data inputs and outputs ie 'what does this thing do) and B) The Design Specifications ('what does this thing look like'?... 'how do people interact with it?... what do they see?'
3) The role of Specification Writer (at some levels a.k.a. 'knowledge engineer') is not trivial and is often assigned to an experienced professional. However, based on what you described, i am pretty sure that you, as the main player (since you know the business rules and procedures), assisted by the developer can produce these Specifications.
4) Specification writing takes MOST of the time devoted to the development of an app... be prepared to put in MANY hours learning how to do this and then doing it... In the long run, it will pay off !!! Otherwise, you (and the unfortunate developer) are likely to be caught in the dreaded 'bottom-up' app dev cycle... ie the development of the app 'evolves'... usually forever... or until folks run out of money and patience!
5) After you are sure that the Specs are solid... THEN start paying for the coding...
The Specs are the mechanism by which you communicate your businnes process to the developer... if you have ever created an ISO9000 Quality System you will see the similarities... Say what you do Do what you say... in such a manner that an auditer, inexperienced with your business can conduct a reasonable audit. The app developer is like the auditor and the Specs are like the Quality Manual and The Procedure Manual. The SOPs are like the actual code... (sort-of).
Sorry if this sounds daunting... but better to go in with your eyes open. It's a question of 'pay me now... or pay me later'... you won't like the latter option!
... for what it's worth!
David
Comment