 problem with software programmer, information on what to expect-blueprint |
Welcome Guest ( Log In | Click here to Register a free account now! )
Register a free account to unlock additional features at BleepingComputer.com
Welcome to Bleeping Computer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.
 May 30 2005, 04:00 PM
Post
#1
|
|
|
New Member  Group: Members Posts: 8 Joined: 18-May 05 From: South Georgia Member No.: 20,493  |
1. Isn't there some kind of guide or template out there that states that step one is this -step 2 is this - and can give an outline that would tell us what we should expect a programmer to do, know and when and what we should be getting and expecting along the way to keep the project on course. 
|
 |
 
|
 |
Replies
(1 - 5)
|
May 31 2005, 08:28 AM
Post
#2
|
|
 Forum Addict Group: Members Posts: 2,159 Joined: 18-March 05 From: near Sydney, Australia Member No.: 14,809 |
QUOTE Isn't there some kind of guide or template out there No. Other than normal rules of business. Maybe you should be looking at the terms under which you employ the programmers - what's in the contract? Put in clauses about acceptability, usability, support, delivery timeframe, penalties for non-performance, and so on. Hey if I can think of this any competent lawyer should be able to tie these guys in knots. What kind of software are you talking about? Machine code? 4GL? Web page design? Maybe you should be taking the job to a company and getting a quote for the finished product rather than trying to find the right person to make it for you piece by piece? These are just my personal thoughts, others more experienced than I may have specific suggestions. -------------------- Soltek QBIC, Pentium 4 3.0GHz, 512MB RAM, 200GB SATA HDD, ATI Radeon 9600XT 256MB, Netgear 54Mb/s WAP, ridiculously expensive Satellite Broadband Windows XP Home SP2, Trend Micro Internet Security, Firefox, Thunderbird, AdAwareSE, Spybot S&D, SpywareBlaster, A-squared Free, Ewido Security Suite. |
|
|
|
 May 31 2005, 08:13 PM
Post
#3
|
|
|
New Member Group: Members Posts: 11 Joined: 18-March 05 Member No.: 14,736 |
I am a student.The most important thing for me is to study hard.Not only the books,but some practical exprience.I wish someday I can be hired by a famous computer company.
|
|
|
|
|
May 31 2005, 09:28 PM
Post
#4
|
|
 Forum Addict Group: Global Moderator Posts: 23,336 Joined: 11-April 04 From: Chicago, Il. Member No.: 113 |
As a project manager I know the kinds of problems you go through. Here is a simple analysis of the project life cycle:
http://www.maxwideman.com/papers/plc-models/texts.htm One of the best ways to manage a project is to learn to properly use software like MS Project to define and assign each step in the process. Even if you use outside resources to code, the preliminary definition and design of the program is really critical. Regards, John -------------------- Whereof one cannot speak, thereof one should be silent.
|
|
|
|
|
May 31 2005, 09:38 PM
Post
#5
|
|
 Forum Regular Group: Members Posts: 172 Joined: 6-January 05 Member No.: 8,797 |
Hello, does your husband hope to sell his product? i guess he probably doesm but if he doesn't you could put it out to the open source community.
--------------------  Special thanks to efizzer for the signature |
|
|
|
|
Jun 10 2005, 03:16 PM
Post
#6
|
|
|
New Member Group: Members Posts: 2 Joined: 10-June 05 From: Maplewood, NJ Member No.: 22,993 |
There are different approaches, but since this is a small project ( I guess, if there is only one programmer working on it at a time ), I would make sure the following steps are followed:
- Write down what the program is supposed to do. What are the inputs, and what are the outputs. Break this down into major components of functionality. - Have the programer write a proposal of how long each of the different components of the system will take. - Ask for a mock-up (prototype) of the application, if possible. - Ask for status reports every 2 weeks, and what he/she intends to do for the next 2 weeks. - Get an explanation why things are late. (And there will always be late deliverables, that's just the name of the game). - If your specs are unclear, or if you change direction/features during development, expect delays. -------------------- Webmaster of Biometrics Forums
|
|
|
|
 |
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:
| Lo-Fi Version | Time is now: 21st November 2009 - 07:36 PM |
© 2003-2009 All Rights Reserved Bleeping Computer LLC.