 | |
#121
 
| |||
| |||
|
Re: Calculated value dilemma -
07-21-2008
, 01:35 PM
|
6. Make sure you thoroughly know and understand how this information is recorded and managed now. I'm assuming it is a manual system. Being really familiar with current practice will provide valuable information in both the design of your underlying data model and the overall implementation. Don't try to just replicate the process using technology - your solution wil almost certainly require those who manage the process to refine their process, but make sure you understand their current process before trying to design them a new one. |
Quote:
|
Finally, make sure there isn't an affordable or open source solution that would suffice. Building such an application is a fun project and if its for an organisation you feel warrants such support, its generally a good thing. However, all applications need maintenance and support. If your not prepared or unable to provide this maintenance and support, they need to get it from somewhere else and it can come at a cost - particularly for one off custom apps. Given you have never designed and implemented a database and application before, you are almost certainly going to get things wrong. I've been working in the industry for over 20 years and I still get things wrong - the only difference is that I get it wrong less often and when I do it tends to be less critical. good luck Tim -- tcross (at) rapttech dot com dot au |
#122
| |||
| |||
|
|
6. Make sure you thoroughly know and understand how this information is recorded and managed now. I'm assuming it is a manual system. Being really familiar with current practice will provide valuable information in both the design of your underlying data model and the overall implementation. Don't try to just replicate the process using technology - your solution wil almost certainly require those who manage the process to refine their process, but make sure you understand their current process before trying to design them a new one. |
Quote:
|
Finally, make sure there isn't an affordable or open source solution that would suffice. Building such an application is a fun project and if its for an organisation you feel warrants such support, its generally a good thing. However, all applications need maintenance and support. If your not prepared or unable to provide this maintenance and support, they need to get it from somewhere else and it can come at a cost - particularly for one off custom apps. Given you have never designed and implemented a database and application before, you are almost certainly going to get things wrong. I've been working in the industry for over 20 years and I still get things wrong - the only difference is that I get it wrong less often and when I do it tends to be less critical. good luck Tim -- tcross (at) rapttech dot com dot au |
#123
| |||
| |||
|
|
6. Make sure you thoroughly know and understand how this information is recorded and managed now. I'm assuming it is a manual system. Being really familiar with current practice will provide valuable information in both the design of your underlying data model and the overall implementation. Don't try to just replicate the process using technology - your solution wil almost certainly require those who manage the process to refine their process, but make sure you understand their current process before trying to design them a new one. |
Quote:
|
Finally, make sure there isn't an affordable or open source solution that would suffice. Building such an application is a fun project and if its for an organisation you feel warrants such support, its generally a good thing. However, all applications need maintenance and support. If your not prepared or unable to provide this maintenance and support, they need to get it from somewhere else and it can come at a cost - particularly for one off custom apps. Given you have never designed and implemented a database and application before, you are almost certainly going to get things wrong. I've been working in the industry for over 20 years and I still get things wrong - the only difference is that I get it wrong less often and when I do it tends to be less critical. good luck Tim -- tcross (at) rapttech dot com dot au |
#124
| |||
| |||
|
|
6. Make sure you thoroughly know and understand how this information is recorded and managed now. I'm assuming it is a manual system. Being really familiar with current practice will provide valuable information in both the design of your underlying data model and the overall implementation. Don't try to just replicate the process using technology - your solution wil almost certainly require those who manage the process to refine their process, but make sure you understand their current process before trying to design them a new one. |
Quote:
|
Finally, make sure there isn't an affordable or open source solution that would suffice. Building such an application is a fun project and if its for an organisation you feel warrants such support, its generally a good thing. However, all applications need maintenance and support. If your not prepared or unable to provide this maintenance and support, they need to get it from somewhere else and it can come at a cost - particularly for one off custom apps. Given you have never designed and implemented a database and application before, you are almost certainly going to get things wrong. I've been working in the industry for over 20 years and I still get things wrong - the only difference is that I get it wrong less often and when I do it tends to be less critical. good luck Tim -- tcross (at) rapttech dot com dot au |
#125
| |||
| |||
|
|
6. Make sure you thoroughly know and understand how this information is recorded and managed now. I'm assuming it is a manual system. Being really familiar with current practice will provide valuable information in both the design of your underlying data model and the overall implementation. Don't try to just replicate the process using technology - your solution wil almost certainly require those who manage the process to refine their process, but make sure you understand their current process before trying to design them a new one. |
Quote:
|
Finally, make sure there isn't an affordable or open source solution that would suffice. Building such an application is a fun project and if its for an organisation you feel warrants such support, its generally a good thing. However, all applications need maintenance and support. If your not prepared or unable to provide this maintenance and support, they need to get it from somewhere else and it can come at a cost - particularly for one off custom apps. Given you have never designed and implemented a database and application before, you are almost certainly going to get things wrong. I've been working in the industry for over 20 years and I still get things wrong - the only difference is that I get it wrong less often and when I do it tends to be less critical. good luck Tim -- tcross (at) rapttech dot com dot au |
#126
| |||
| |||
|
|
6. Make sure you thoroughly know and understand how this information is recorded and managed now. I'm assuming it is a manual system. Being really familiar with current practice will provide valuable information in both the design of your underlying data model and the overall implementation. Don't try to just replicate the process using technology - your solution wil almost certainly require those who manage the process to refine their process, but make sure you understand their current process before trying to design them a new one. |
Quote:
|
Finally, make sure there isn't an affordable or open source solution that would suffice. Building such an application is a fun project and if its for an organisation you feel warrants such support, its generally a good thing. However, all applications need maintenance and support. If your not prepared or unable to provide this maintenance and support, they need to get it from somewhere else and it can come at a cost - particularly for one off custom apps. Given you have never designed and implemented a database and application before, you are almost certainly going to get things wrong. I've been working in the industry for over 20 years and I still get things wrong - the only difference is that I get it wrong less often and when I do it tends to be less critical. good luck Tim -- tcross (at) rapttech dot com dot au |
#127
| |||
| |||
|
|
6. Make sure you thoroughly know and understand how this information is recorded and managed now. I'm assuming it is a manual system. Being really familiar with current practice will provide valuable information in both the design of your underlying data model and the overall implementation. Don't try to just replicate the process using technology - your solution wil almost certainly require those who manage the process to refine their process, but make sure you understand their current process before trying to design them a new one. |
Quote:
|
Finally, make sure there isn't an affordable or open source solution that would suffice. Building such an application is a fun project and if its for an organisation you feel warrants such support, its generally a good thing. However, all applications need maintenance and support. If your not prepared or unable to provide this maintenance and support, they need to get it from somewhere else and it can come at a cost - particularly for one off custom apps. Given you have never designed and implemented a database and application before, you are almost certainly going to get things wrong. I've been working in the industry for over 20 years and I still get things wrong - the only difference is that I get it wrong less often and when I do it tends to be less critical. good luck Tim -- tcross (at) rapttech dot com dot au |
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.