1) Definition: think about what you want to do, have a good idea what it is you want.
2) Document: document the different software tasks, routine, operating system, how it all works and links together. Document communication paths, how tasks and routines communicate.
3) Create: code all the tasks, routins, communication paths, etc. etc.
4) Build it.. compile, link, resolve any errors.
5) Test it: if it all works as you intended, great. Most likely it won't the first time. Fix what is wrong and go back to 4)
6) Release it to the customer
7) Maintain it: most likely the great software you developed will have some small error in it. Correct that error and go back to 4)
What happens more often is that the customer loves what you did, it works exactly as intended.... But..... it would be so much better if it could do this one other thing, or it had this one feature.
You might be able to just add the feature and go to 4), or you might have to go to 1) defining the new feature..
After maintaining this software for a period of time:
8) End of Life: Your wonderful, well written code is no longer useful... :-( DOS, Windows 3.1, Comodore 64s were all great, but.....
So, call it done.
Of course you have all the code and knowledge to apply to the next projects SDLC.. (Software Development Life Cycle)
Also, if there are several members of your team, there may be "Code Reviews" before and after each of these steps...
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment