Lecture – 1 Introduction to Software Engineering
Lecture Series on Software Engineering by Prof.NL Sarda, Prof. Umesh Bellur,Prof.RKJoshi and Prof.Shashi Kelkar, Department of Computer Science & Engineering ,IIT Bombay . For more details on NPTEL visit nptel.iitm.ac.in
Brilliant and excelent lecture
brilliant introductory lecture!
cool
good day sir! i am a 3rd year college student and this semester i am going to take the subject software engineering.i have seen that your videos are too helpful for others because they can have an idea on how they can start there software engineering process.& i have learned some idea’s from your video about the software engineering.thank you sir.more power…
good day! i am a college instructor at cebu institute of technology teaching ICT courses, i found your video very enriching as a supplementary material for course that i am teaching right now this semester which is software engineering, i’d like to ask from you if i could possibly download your video for me to share with my student also in our class. thank you so much and more power!
use Nero vision….its come with nero cd write package which also include movie make!
New versions of Real Player allow you to download multimedia content from a webpage, another one is “YouTube Downloader” just do a google search
beta edition or which one?! XD
yo mamma
the waterfall model works fine, as long as you iterate back to previous phases when necessary.
It’s a berry berry funny joke.
may i know what software was used in making this video?
why?
orbit dowloader. Google it
how can i download this video
is this is a joke
First of all congratulations to Prof.N.L. Sarda for shaping up such a good video presentation on S/W engineering. Few comments though:
In my experience, S/w engineering principles have changed quite significantly over the last decade or so. New models such as Agile methods takes software engineering in a very different way.
The waterfall model is argued by many to be a bad idea in practice because it is nearly impossible to get one phase perfected before moving on to the next phases.
(6) My experience is that many companies state they follow the Waterfall Model, but when you look into the projects, you discover that managers and developers skew that model into some form of an iterative method, which is often down without any documentation. I dont know anyone who follows the Waterfall Method as it was originally intended! Again, nice introduction to the topic!
(4) Prediction is not binary. Qualitative prediction has to do with what you mean by actual values being CLOSE TO expected values. I can predict I will be close to expected results but it may not be statistically based. (5) Process models (process descriptions) should explicitly identify forms of feedback that are the basis for improvement and evolution.
(3) A process is simply something that is done to produce some output. You do not have to have objectives, exit criteria, or documented steps to have a process. When a trained engineer follows a documented process description, which states inputs, outputs, entry and exit criteria, etc. then there is process maturity. Objectives defined should be measured at the conclusion of the process and should be the basis for improvement. A defect is something that is a variant between objective and result.
A nice video. Some comments. (1) I believe a process should encompass all aspects of PDCA cycle, so a process should integrate both the planning and improvement actions as well as the Doing.” (2) A process is not the same as a methodology, which you are describing. No matter if I am using a waterfall, spiral, iterative or rapid development method, I can use the same design process. A methodology only restricts when in my lifecycle I can perform which processes; e.g., no Design in Reqts Analysis
very helpful
Funny stuff! I loved it.
thank you for your help