Over a year after you posted this, I have just barely discovered the absolute best video and phase breakdown description about the SDLC online. Thank you, sir, your hard work is much appreciated!
Al Zimmerman Yes , thank you so much for taking time to reply. WE were studying SDLC yesterday and my trainer played your video and just carried us along as you explained and answered our questions. And we were couldn't stop talking about how much information we got from it and enjoyed it.
I'm a nurse who is taking on the position on a PM and wow this is an awesome video!! So much good advise. It has helped me plan how I'm going to start my first day. I'm in the deployment phase and I feel more confident and excited!! Thank you.
superb planning and execution of your presentation Mr. Al Zimmerman . I like the crystal clear explanation, attention to every key detail and the flow of explanation,especially about how planning falls in to all the phases( my lecturers never taught me that). Best lecture I have ever listened to, and hey, it didn't even last 30 minutes. looking forward to more of your videos Al. *subscribes pap*
Outstanding! Not only is this a major help in a degree program I'm working on, but it actually clarifies some problems I've witnessed in roll-outs and "upgrades" on my current and past jobs. Too bad you weren't on those teams. :)
I'm glad you liked the video. This one used Camtasia on a PC (running on VMWare on a Mac), Keynote on an iPad, being viewed via an AirPlay app called Reflector. The camera and headset are from logitech. I used natural lighting from a nearby window. I used Camtasia because of the "automatic" captioning capability.
Thanks for this helpful and informative breakdown of SDLC. I've got a Business Systems Management exam tomorrow and I needed something to brush up on my SDLC knowledge :)
+ Al Zimmerman this is basically similar to systems analysis and design BUT this is an EXCELLENT tutorial, extremely helpful and worth every second of the 22 mins of this video!!!!!! Thank you Al :D :D :D
Thank you very much, you explained System Development very well, you even squeezed in a little ice breaker "Executicle"......:) ....lol. I will surely remember all you said because of that joke.
Thank you for the clear explanation. getting resume for interviews for a business analyst position. This helps tremendously. If you have any other materials on youtube that could be beneficial, pls let me know. thanks
May I ask why you wait until the deploy phase to check on the scale of the project. I understand its an iterative process but if the client or competitor have relevant information on the subject are we not obligated to flush that out sooner rather than stumble later? ps- I loved your video and this is not a slam. Recently, I'm being looked at for a PM position and need all the info I can get. Thanks in advance for you response.
I'm sorry it took so long for me to respond - i've messed up my comment notifications, apparently. It's good to know the scale from the beginning. You are absolutely right. It will influence your architectural choices. But many projects never attain the scale their designers hope for, or as fast as they hope for. So, spending the money (by putting in the effort) to do a giant system from the start is premature. You might learn a lot from a small beta program with a couple hundred or few thousand users and realize you need an entirely different system to capture a significant market. Also, when you are first developing, it's challenging enough to get the system working at all. You need to get the system working on one server before you getting working on ten, or a hundred. So I misspoke if I said don't think about scaling at all until you are preparing for deployment. That would indeed be too late. But you SHOULD wait until 1) you understand how to build the product and 2) You've tested your product with a smaller number of users so you are reasonably certain you are building what people will pay for. :-)
That's an excellent question! Unfortunately, I don't know the answer. You might do a search on quora.com for "google development process" -- some times the answers there are offered up by people who actually know what they are talking about. Good luck!
I'm afraid they wouldn't pay any more attention to me than you! What I've found is that people tend to not answer questions if they think the answer is already available to the public. Not polite perhaps, but there you are. Have you tried googling for the answer? This sort of question is probably already answered out there on the web. People often share how they work and what they've learned. Do research if you can. Try looking through quora.com or look up "talks at google" on youtube. There are also a whole bunch of blogs published by development people at google. Look around on the google developer web site.The google maps team has a blog and quite a lot of information on the web. There's lot's of information out there. I'm sure you can find the answer to your question if you dig a little.
Although tutorial is good, but cannot agree with presenter's description of role of Project Manager. Because so far i have perceived that Project manager is man who thinks that nine women can deliver baby in one month
If I used the both terms, that was sloppy. The process described works for any system, not just software-based systems. Systems with hardware, off the shelf systems, etc, require different activities and different time frames, but the principles are the same: small increments, check with the customer all the time and reduce risk in each phase.
I don't believe you did, but it seems like the terms are used interchangeably (Like if you google 'SDLC'), and the steps are pretty much identical. I'm just curious if there are any clear distinctions besides one being specifically for software and the other being a general system development methodology.
I can only speak from my own experience here. There are a lot of people more qualified to talk about software-specific development methodologies. And even more who have opinions. :-) One of the reasons that software development is hard is that there are few physical constraints we are forced to work with. So, we are always experimenting with better ways to do things. Like most experiments, a lot of these ideas fail. Or fail to catch on. So you'll see a lot of people focusing on software lifecycles because we are still figuring it out. In other systems, like architecture or shipbuilding, we have a lot experience and a lot of physical constraints that our process must accomidate. So, there is less discussion and experimentation. Less opportunity for discovery-based processes like agile and SCRUM. And far fewer blog posts by people with a few years experience who think they've discovered the One True Way. But, even with these more traditional, physical system development processes, there is still a lot of back-and-forth with customers, an emphasis on design before development, risk reduction, and other generic principles. What I'm looking for in this video is a way of talking about all systems at a high enough level that we can introduce those general principles.
Over a year after you posted this, I have just barely discovered the absolute best video and phase breakdown description about the SDLC online.
Thank you, sir, your hard work is much appreciated!
To the point, nothing extra, nothing time wasting here.
Great explanation, thanks for the video.
Your video was used in a training I attended, you're so precise and clear. Thank you so much.
Thank you! Can you tell me more about the training?
Al Zimmerman Yes , thank you so much for taking time to reply. WE were studying SDLC yesterday and my trainer played your video and just carried us along as you explained and answered our questions. And we were couldn't stop talking about how much information we got from it and enjoyed it.
I'm a nurse who is taking on the position on a PM and wow this is an awesome video!! So much good advise. It has helped me plan how I'm going to start my first day. I'm in the deployment phase and I feel more confident and excited!!
Thank you.
Thank you for creating it. You have a real talent explaining difficult topics. I enjoyed it a lot.
One of the best overviews I've seen on UA-cam. Thank you.
superb planning and execution of your presentation Mr. Al Zimmerman . I like the crystal clear explanation, attention to every key detail and the flow of explanation,especially about how planning falls in to all the phases( my lecturers never taught me that). Best lecture I have ever listened to, and hey, it didn't even last 30 minutes. looking forward to more of your videos Al. *subscribes pap*
Outstanding! Not only is this a major help in a degree program I'm working on, but it actually clarifies some problems I've witnessed in roll-outs and "upgrades" on my current and past jobs. Too bad you weren't on those teams. :)
It is very nice and useful. Crisp and Clear.
I am an agile coach for my organisation and impressed by your presentation.
I must say, that was a brilliant tutorial. Thank you sir!!!
+Steve Aryeetey Thank you!
Very helpful video.. The explanation was crystal clear !!! Looking forward for some more videos !! XxX thank you
I'm glad you liked the video.
This one used Camtasia on a PC (running on VMWare on a Mac), Keynote on an iPad, being viewed via an AirPlay app called Reflector. The camera and headset are from logitech. I used natural lighting from a nearby window.
I used Camtasia because of the "automatic" captioning capability.
Thanks for this helpful and informative breakdown of SDLC. I've got a Business Systems Management exam tomorrow and I needed something to brush up on my SDLC knowledge :)
I wish I had you as a teacher !
great clear explanations, looking forward to more videos
I must say, that was a brilliant tutorial. Thank you!!!
You are a fantastic lecturer. Great job
So nice of you. It's fun!
+ Al Zimmerman
this is basically similar to systems analysis and design BUT this is an EXCELLENT tutorial, extremely helpful and worth every second of the 22 mins of this video!!!!!!
Thank you Al :D :D :D
Great short explanation of the SDLC. I'll use this in my classroom.
it was nice presentation waiting for more videos from you.
This was extremely helpful. You also went very slow, and it was very helpful to refresh myself with SDLC...
I have truly learnt alot... Very very informative
College lectures should be like this
Awesome slides
THAT S TRUE
Great presentation - simple - informative and effective. Thanks!!
Excellent video! very good explanation and easy to understand. thank you
I enjoyed watching this and learned a few things
That was a very good video/summary. Thanks for your expertise!
Thank you very much, you explained System Development very well, you even squeezed in a little ice breaker "Executicle"......:) ....lol. I will surely remember all you said because of that joke.
PERFECT! Thank you for talking so clear and really making it simple. Really helped me on my essay!
Very nice tutorial, I see on Brazil! Tanks for your time!
Thanks for the tutorial Al, this really helped me!
great presentation. pure wisdom. thank you
Bravo 👏🏼 excellent presentation Mr. Zimmerman !
thank u so much sir..........it is a simple , but wonderful tutorial, may god bless u sir
it's a crystal clear expliantion
Very informative and well paced video - thank you!
Thank you so much Al, I really like your presentation it was very clear and concise.
This is an awesome explanation
Anyone applying for system analyst job should whatch this video before the interview.
Thank you for this video. learned a lot about SDLC
Very good explanation!
This was clear and very informative. Thank you sir😊
Great work! Great teacher! Thank you!
Great Information, this truly is gold!
Thanks Al, this is great!
Very helpful and great insight.
Excellent video!
Thank you. I am delighted.
Thank you for the clear explanation. getting resume for interviews for a business analyst position. This helps tremendously. If you have any other materials on youtube that could be beneficial, pls let me know. thanks
I love this AL. bless you.
Dude. That was amazingly concise.
wow i really admire the lesson, cheers
Do you have any videos on documenting functional and nonfunctional requirements?
No, I'm afraid not. Let me know if you find one out there!
This is great explanation!
vary nice you help me so much in my graduation project
sooooo many thanks to you
Excellent class !
very practical approach.
Thanks a lot, Al !
Great explanation of iterative method.
I hope you create Agile method too :( . that would be awesome.
Very good video. I have an interview and I want to brush up on SDLC.
It is very nice and useful presentation.
Thanks a lot.
Thank you this was very helpful
Excellent video, cheers!
really something helpful... loved it!!:)
awesome video! thank you for the information.
nice ...lovely piece of info..
Thanks, it was very good explanation
Well explained and clear. Thank You!
Great explanation! Thank you.
May I ask why you wait until the deploy phase to check on the scale of the project. I understand its an iterative process but if the client or competitor have relevant information on the subject are we not obligated to flush that out sooner rather than stumble later?
ps- I loved your video and this is not a slam. Recently, I'm being looked at for a PM position and need all the info I can get. Thanks in advance for you response.
I'm sorry it took so long for me to respond - i've messed up my comment notifications, apparently.
It's good to know the scale from the beginning. You are absolutely right. It will influence your architectural choices. But many projects never attain the scale their designers hope for, or as fast as they hope for. So, spending the money (by putting in the effort) to do a giant system from the start is premature. You might learn a lot from a small beta program with a couple hundred or few thousand users and realize you need an entirely different system to capture a significant market. Also, when you are first developing, it's challenging enough to get the system working at all. You need to get the system working on one server before you getting working on ten, or a hundred.
So I misspoke if I said don't think about scaling at all until you are preparing for deployment. That would indeed be too late. But you SHOULD wait until 1) you understand how to build the product and 2) You've tested your product with a smaller number of users so you are reasonably certain you are building what people will pay for. :-)
Great, Thank you Al
Hello Al. Great video! What Software did you use to create your video?
So informative...thank u so much
My pleasure 😊
Thank you so much for sharing.
Great talk, Thanks
Thank you for sharing this video it is very helpful, God Bless...
Thanks for making simple explanation...
very helpful thank u very much, can u pls explain system development approaches tooo
thank you for this video sir :)
teacher , what Software Development Life Cycle (SDLC) does google map follow?
That's an excellent question! Unfortunately, I don't know the answer. You might do a search on quora.com for "google development process" -- some times the answers there are offered up by people who actually know what they are talking about. Good luck!
i ask them but i don't receive any answer :(
could you do me a favor and ask them ?
I'm afraid they wouldn't pay any more attention to me than you! What I've found is that people tend to not answer questions if they think the answer is already available to the public. Not polite perhaps, but there you are. Have you tried googling for the answer? This sort of question is probably already answered out there on the web. People often share how they work and what they've learned. Do research if you can. Try looking through quora.com or look up "talks at google" on youtube. There are also a whole bunch of blogs published by development people at google. Look around on the google developer web site.The google maps team has a blog and quite a lot of information on the web. There's lot's of information out there. I'm sure you can find the answer to your question if you dig a little.
It's a wonderful tutorial. Thanks sir.
Great explanation! :) thanks!
Very helpful, thank you very much!
that was informative i liked it
Great... Really superb:)
"always plan in between each phase" it always echo on my brain
Great job!
Thank you for this informative video; really helped with Nursing Informatics course!
Thank you for this great video👍
Great video
love it!!!
Good explanation.i'll use it for teaching my students..
Nice video. Thanks.
Thanks, very helpful.
Although tutorial is good, but cannot agree with presenter's description of role of Project Manager. Because so far i have perceived that Project manager is man who thinks that nine women can deliver baby in one month
Naveed, I've met those kind of PM's too. :-) I hope you have the opportunity to work with more professional PM's in the future. Cheers!
Thank u,very helpful.
very good!
So, I'm a bit confused here. What is the difference between the Software Development Life Cycle, and the System Development Life Cycle?
If I used the both terms, that was sloppy. The process described works for any system, not just software-based systems. Systems with hardware, off the shelf systems, etc, require different activities and different time frames, but the principles are the same: small increments, check with the customer all the time and reduce risk in each phase.
I don't believe you did, but it seems like the terms are used interchangeably (Like if you google 'SDLC'), and the steps are pretty much identical. I'm just curious if there are any clear distinctions besides one being specifically for software and the other being a general system development methodology.
I can only speak from my own experience here. There are a lot of people more qualified to talk about software-specific development methodologies. And even more who have opinions. :-)
One of the reasons that software development is hard is that there are few physical constraints we are forced to work with. So, we are always experimenting with better ways to do things. Like most experiments, a lot of these ideas fail. Or fail to catch on. So you'll see a lot of people focusing on software lifecycles because we are still figuring it out.
In other systems, like architecture or shipbuilding, we have a lot experience and a lot of physical constraints that our process must accomidate. So, there is less discussion and experimentation. Less opportunity for discovery-based processes like agile and SCRUM. And far fewer blog posts by people with a few years experience who think they've discovered the One True Way.
But, even with these more traditional, physical system development processes, there is still a lot of back-and-forth with customers, an emphasis on design before development, risk reduction, and other generic principles.
What I'm looking for in this video is a way of talking about all systems at a high enough level that we can introduce those general principles.
Interesting, definitely gave me something to think about. Thank you for your thoughtful responses!
Very interesting response. I'd never thought of the lack of physical constraints aspect. Such a good point!
Interesting! Good! :)
Thank you so much 👐👌