 Re: The life cycle of a project
|
Ausef Machaino |
|
2/22/2008 2:33:19 AM |
Hi,
You posted this in the Articles section. I'll go ahead and move it to the Forum where an Expert will be more likely to find it.
The experts on this site are more than happy to help you with your problems but they cannot do your assignment/program for you. You have not asked a question. Attempt the assignment/program yourself first and post questions regarding any difficulties you have or about a particular function of the code that you don't know how to achieve.
Please read the Posting Guidelines and particularly the Coursework Posting Guidlines.
Then when you are ready post a new question in this thread.
Post Comments |
|
Re: The life cycle of a project |
Bechara Murkot |
|
2/22/2008 2:34:50 AM |
Search the net for Software Development Life cycle. You will find plenty of good examples.
Post Comments |
|
Re: The life cycle of a project |
Carolina Peipenji |
|
2/22/2008 2:36:18 AM |
Hi
software development life cycle is the very broad and depth topic. I can tell you that first step is the requirement analysis. For good understanding of SDLC read book of Hudson By oxford press.
Post Comments |
|
Re: The life cycle of a project |
Deiv Esteipan |
|
2/22/2008 2:47:39 AM |
The software development life cycle begins with requirements for the cycle. These can be changes to existing code or new programming.
The specifications for each unit of the project are given to a programmer, DBA, QA person, etc. After the programmer makes the necessary changes or additional programs, the programmer tests his/her code in a test environment.
When testing by the programmer is complete, a quality assurance person (QA), who has written test scripts, will try to break your program. If the QA person finds issues with the programmer's code, the code goes back to the programmer for further tweaking and that process continues until the QA person can no longer break the program.
System Test: Usually, there is another environment, considered a clean environment, to test the code again. All new code is put into this clean environment and testing (by QA) starts again.
When all issues are clear and the system test arena is running clean, the new code is installed into production. QA and usually some users test the new code along with all existing code to make sure that everything works as required.
Sometimes an emergency release is needed if an issue isn't caught until after install.
Then, it starts all over again. I've worked for companies that did bi-monthly and quarterly releases. This means that I either had two months or four months to go through the entire development lifecycle.
Hope this helps.
Post Comments |
|
Re: The life cycle of a project |
Edmond Polstock |
|
2/22/2008 2:49:31 AM |
1) Your manager asks you "Is it possible to do ill-defined process X?"
2) You answer it is possible generally to do X, assuming a bunch of details are given.
3) Your manager asks when it can be finished
4) You say you can have a prototype within a week or two as soon as you can get the details.
5) The manager gives you one page of notes to work from.
6) The next day, the manager's boss informs you your manager is going on a business trip for a week and he wants "something to show the CIO"
on your project by the middle of this week. When you explain it can't be done without more information he looks at you as if you've just boiled his cat. He begins interrogating you as to the details of exactly how you're going about developing the software, makes a pointed suggestion that you should just do "the necessary pieces"
and again "communicates"
to you that it needs to be done by the middle of the week. He then goes out to lunch.
7) You call your manager to get a meeting, and the manager, having no backbone, tells you to write something for his boss.
8) After a few hours of fuming and wondering how you're going to avoid getting fired, you give up and just decide to get another job. As a farce, you put together a powerpoint presentation explaining the workings of the northwind database and email it to the boss'
boss.
9) This mindless VP of nothingness, being almost completely unconscious, thinks you've written the next killer app. You are awarded a seat at the meeting, where you get free lunch for your efforts.
10) Your boss calls starts calling you a genius, assigns you to liaise with this useless VP, and creates a new management position for you.
11) You quit coding and choose a career in executive "management".
Post Comments |
|
