1 Software Engineering Prof. N. L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture - 2 Introduction to Software Engineering Challenges, Process Models etc (Part 2) This is second lecture on introduction to software engineering. Let us start by summarizing by what we saw in the first lecture. We understood the challenges in developing the large software. We want to do it in given time, within given resources and meet user s requirement. This is indeed very challenging. We then saw the benefits of engineering approach which consists of defining different milestones, different stages in the development and carrying out periodic review and having a well-defined methodology for the development. Then we have talked about different types of software processes. These are processes for development of software, for project planning and management, for configuration management and then for managing the software processes themselves, because they are not fixed and static. They keep changing. So any large software development organization will need to invest time and resources in keeping the software processes up to date and state of art. (Refer Slide Time: 01:52)
2 Then we defined a typical step in a software development process we identified that the step will consist of some entry criteria, exit criteria, it will have some specific task to do, it will take certain inputs, it will provide some outputs and also the step will be under management control. So this is a very important definition of the typical step in the software development process. Then we also saw characteristics of good processes. And one of the most important characteristic was that it should be predictable, it should be well defined, and it should be repeatable. This is primarily what we focused on in the first lecture. And towards the end we began to look at the waterfall model for software development. We briefly introduced this last time. We said that a waterfall model consists of many steps organized in a linear order. So that one step produces the right kind of outputs for the next step. (Refer Slide Time: 03:34) There is a linear or sequential order in which the different activities are performed. It follows what we may call; specify, design, build sequence of activities, which should appear to be quite obvious. What it really means is that, you cannot design something which is not clearly specified. And if you have not done the design, naturally you cannot build. This is like going to market without knowing what you want to buy. Naturally you can t buy them or you can t compare different products. You need to have clear specifications in mind before you go and want to buy something. Similarly when you want to build something, you must define what needs to be build, what are the functions that need to be performed, and then carry out a design which is efficient, effective. And finally only when the design or the blue print is done, we start building. So we say that this sequence of activities appear to be obvious and natural. This is what the waterfall model tries to do. Waterfall model produces many intermediate deliverables. There is a deliverable at every step in the model. For each of these, proper standards have been defined. Most of these deliverables are actually documents which have a standard format.
3 (Refer Slide Time: 05:00) Many of these documents will act as a baseline for future reference. In fact some of these baselines are in the nature of contractual obligations. You may be an independent agency who is doing software development for a client. So there has to be a baseline, there has to be a reference which clearly defines what your obligations to the customer are and what kind of product you should make for him. So such kind of baselines would be produced in the process of development. And waterfall model defines such baselines or other deliverables or other documents which are required for subsequent steps. One important point about this deliverables is that, once a step is completed, the output of that step is clearly defined in the form of a document, which can be then handed over to people who will perform the next step. So this model facilitates change of people from step to step. We are not making it necessary that the same people who have done the analysis should do the design; the same people who have done the design should do the implementation. In fact we saw that in the example of civil engineering, we have different people with different expertise and different people are called upon to do certain specific things at different points in the life cycle of a project. Same thing happens in a software development. We define these documents, they are of certain formats, and they are handed over to the next team who will perform the next step. So there is an interchangeability of the people and different steps can employ people of different skills as necessary for that step. These documents also play an important role for quality assurance, project management and so on. This methodology is also very widely used. There are some variations possible, but it is commonly followed because of the natural development cycle on which it is based. Especially when the requirements can be clearly defined, waterfall model is an ideal model for development software. So let us see what the different steps are.
4 (Refer Slide Time: 07:35) This diagram identifies different stages in the waterfall model. Let us look at each one of them briefly. Then later on we will look at each of them in some more details. So the first step is the system engineering step where you try to understand the overall problem and identify which of the problem elements are to be handled through the software. It is possible that certain requirements of the problem may need to be done manually, because automation may not be possible whereas some other functions will be performed by the software. So one of the goals in system engineering is to understand the overall context of the problem. And then identify what would be the responsibilities to be met through the software. After doing that we undertake the analysis phase. In the analysis phase we understand the problem domain of the user in more detail. We understand what kind of information is involved what kind of data is involved, what functions need to be performed, what are the performance and interfacing requirements. This part is the analysis part whose purpose is to identify or clearly define the requirements which are to be met thru the development of the software along with. In the analysis we also try to carry out project planning either as a part of the same step or if it is large project, the project planning step may be made as a separate step. And the purpose of project planning is to identify how we will carry out the project what are the different steps, what are the deliverables, and what would be the time frame what could be the resources allocated. That is what a project planning is all about. After the analysis is done, the next step leads to the design step. In the design step we translate the requirements into the software architecture when we prepare the database design and so on. So this is a primarily a technical step and in this step the requirements are translated into an implementation framework, which will be implemented in the next phase that is the coding phase, in which the actual programming and implementation will be done.
5 So you have a design and the design is followed by implementation. In fact as it notes here the design itself may be divided into two stages called high level design and detailed design. Again this would depend on the complexity of the task. After you have done the implementation or carried out the programming phase, when the individual units of the software are ready, you would get into the next phase called testing phase and integration phase. In this all the individual pieces of the software are individually first tested, and then the whole software is put together. The objective is to test first the logic of individual modules. And then when we put all of them together we want to test their interfaces, so that they work collectively in a manner in which they were intended to work. This is the testing and integration phase and this is followed by actual deployment of the software. Now the software is ready. It is deployed and implemented. The user will take control and will start using the software. After the deployment there is an ongoing maintenance phase. In the maintenance phase, we have to make the necessary changes; if any errors are encountered we will have to remove the errors. If the software is not meeting the performance requirements we may have to review the software, maybe we have to go back and look at the design whether the design can be modified or if there is something else that can be done in order to improve the performance. So this is an ongoing step which may generally be called a maintenance phase. And in this phase, the software is either enhanced or is perfected or is ported to new hardware or new machines. This is an ongoing activity which needs to be done throughout the life time of the software. These are the different phases through which a typical software development goes through. We have identified here the main steps. Each of the steps has certain deliverable. Let us enumerate the different deliverables which come out in a given sequence when we perform these various steps. One of the important deliverable is the project plan. We will be carrying out the project according to the plan that we make. Of course the plan needs to be revised periodically as we progress through the project. One of the deliverable could also be the feasibility report. The feasibility report is a report which defines the cost effectiveness of the approach and the whole software project, whether it is a good investment we are making, whether the software will be cost effective, whether it will give the kind of benefits we are expecting from the software.
6 (Refer Slide Time: 14:48) So the project plan is one deliverable, feasibility report is another deliverable. One of the important deliverable is requirements document which is also called software requirement specification or SRS for short. SRS is very important baseline and defines the functions that the software will perform for us. Obviously the SRS comes from the analysis step. The next step is the design document. It defines the different components of the software and how they will be implemented. You may have a detailed design document. This document may specify individual units which will be implemented by different programmers. We may have then specific test plans and expected test reports. What it implies is that testing is not a on the fly kind of the task. Tests are planned well in advance. They define what inputs will be given to the system and what outputs are expected and whether the expected outputs are correct and the performance is as expected. So test plans are made well in advance and as soon as the software is ready the test plans are carried out and the workability of the software is demonstrated through the test plans. Of course the source code is an important deliverable and a deliverable which is in executable form. Unlike other deliverables which are documents, this is a deliverable which actually would be loaded on the computer and will be executed which actually defines the software contents. And then we will also have different types of manuals or documents which will be important for users and for administration of the software, for installation of the software and so on.
7 (Refer Slide Time: 15:49) So these different types of deliverables are identified from different stages or different steps in the waterfall model. At the end of each step, if you recall we had said that every step ends in a validation and verification step. Similarly in the waterfall model when we move from one step to another there would be such reviews. Each step would end in a review. These review reports are very important inputs for identifying whether the development proceeded as per the plans, whatever the short comings whether the defects will were detected and were properly addressed. So review report is basically a catalog of how the development went through and it is an important input to the development team as well as to the management. So these are different deliverables. Many of them are important of which SRS is obviously one of the baseline. Design document is also very important for future maintenance. Source code definitely is important as it is executable and without this user manual, installation manual, some administration manuals and the system cannot be effectively used. So as you see here these different documents are essential part of the software. So software is not just the source code but all this documents which accompany software. Now as we go through this waterfall model and we perform the different steps, naturally we are investing more effort. The diagram shows the cost effort distribution as we run through the different steps in the waterfall model. So there are different steps are shown here.
8 (Refer Slide Time: 17:41) As you see that some of the earlier steps have smaller effort than the subsequent steps. For example the detailed design implementation is very effort intensive steps. The line here is a cumulative task and as you see it increases rapidly as we progress in the development. Accumulated cost increases dramatically as we go from initial steps to later steps. Because as we move along the steps we are committing the time of programmers, technical people and computer time, all this is naturally a cost factor. This effort distribution is important for us to understand. Because it clearly brings out that we must take all efforts to remove errors as early as possible in the lifecycle. We must discover and fix these errors as early as possible. Because fixing them subsequently will be a very costly operation. So suppose there is a misunderstanding or the analysis phase has not clearly identified the functional requirement, now that if it is not detected at the review phase of the analysis, it would be carried over design, detailed design and implementation. And it is possible that we discover that mistake during the operational part of the software; when the users have started using the software. In order to make the correction we will have to undo the code design etcetera and go back right up to the analysis phase and identify what was missed out what was wrongly understood, and carry out the design and implementation and testing process again. So it is important that such errors are captured as early as possible and they are not allowed to slip into the subsequent steps. So in any software development approach it is important to understand, how the cost and efforts are distributed, not only for project planning, but for emphasizing an error free activity in each step.
9 (Refer Slide Time: 20:55) There are some shortcomings in the waterfall model. One of the main criticisms of waterfall model is that it goes linearly and it assumes that all the requirements can be clearly defined during the analysis phase. There are many situations where requirements may not be clearly known. This often happens when there is no manual counterpart for the problem that we are solving. If a manual counterpart exist, that means the function business function is already been carried out manually and we are planning to automate that, then in this case it is easy to define the requirements. But in a situation where there is no such manual counterpart, when the system is been planned first time, then the requirements may not be clearly known. Here is an example. We know that railway reservation has now been automated fully. Before that, however the manual system existed. We knew what is the role or what are the tasks involved in the railway reservation. You want to reserve a seat on the particular train, you may want to cancel it, you may get waitlisted, waitlists have to be arranged and there is a method for arranging. All those things were already defined as functional activities. And therefore one can say that as far as the railway reservation is concerned the manual system existed, and therefore it is possible to clearly define the requirements in this case. But there can be other examples where there may be no manual counterpart. For example, say a central bank wants to build a knowledge management system. It believes that there is so much knowledge that is available with its employees in order to carry out their day to day task. It would like to capture this knowledge, build a repository, so that this knowledge is easily available to all other people in the organization. Now this is something which is quite new and it is difficult to define a SRS for an application like this. There is obviously some kind of uncertainty involved in terms of what it will consists of.
10 So this is clearly one issue when we try to apply for the waterfall model, Which the requirements may not be clearly known and it may not be possible to carry out analysis phase once for all and then never come back for revising the requirements. The other issue is that the waterfall model assumes that the requirements are quite stable and that they do not change with time. Now, this is not the case because the software development itself may be a long process, requiring months or years and during this time one cannot assume that the requirements will not change. (Refer Slide Time: 24:00) So in the process what may happen is that when the software is finally built, the users may find that it does not meet their requirements. In such a situation it is probably a good idea to develop the software in parts or in smaller increments and then release them and get the feedback of the user. So there may be different approaches rather than using a strictly linear waterfall model in such situations. Waterfall model is also considered very documentation-heavy, what it means is that too much documentation is being produced as part of the project. This may not be really necessary in all types of projects. So other models have been proposed in order to take care of some of the short comings or to handle some specific situations in project development scenarios.
11 (Refer Slide Time: 24:54) One of them is the prototyping model. In the prototyping model we try to build a prototype rather than the final solution. And we do this especially when the customer is either not aware of his requirements that what exactly he would like to how the software would do for him. Or the developer is not sure about how to develop the software, how to implement the business rules which are generally required for the software. So he may not be certain about the best algorithms that need to be implemented in order to meet the requirements. Or if efficiency is primary criteria, we are trying to let us say build software which will give very high response time, then what kind of techniques one should use in order to guarantee that kind of efficiency or response time. Now these may be some of the unknowns either to the customer or to the developer. In such situation we might rather decide to build a simple prototype and to find out either the requirements or the techniques for implementation. So prototyping model is an intermediate model or intermediate kind of a step in trying to define the requirements or the solution approach. Usually, we will develop a prototype and we will do it in different stages. And to begin with the prototype that we will build will be based on the user needs as we currently understand them. Or the solution approaches as we understand them in the beginning and we will review and refine them.
12 (Refer Slide Time: 27:12) Prototype might be either a working system or it may even be a paper prototype. So idea in the case of prototype is to do a quick design and implementation and to illustrate the approach or to illustrate the functionality to the user when these are clear. So we do not want to spend too much time and effort as well as resources in building a prototype with too much detail. We want to do a quick design and in fact those features which are clearly known or clearly understood need not be implemented. In the case of prototype the focus will be on what is unknown, or not properly understood. So prototype will be tuned as we develop it. And when we try to satisfy customer needs, many iterations may be required to incorporate the changes. Every time we complete the prototype we will evaluate it, tune it and decide what needs to be done further. Final product then would be built after the prototype is completed and is found to be acceptable. This final product may be built using the standard waterfall type of methodology, where we will go through the design, build and test life cycle. So here is the diagram which illustrates possible steps in the prototyping model. We start by quickly gathering the requirements. Then focus on those which are not clear and which need to be experimented. Then we need a quick design, we build a prototype. While building the prototype we may not care about doing too much documentation or look at the maintainability issues or even consider performance issues even if they are not relevant. Idea is to do a proof of the problem by demonstrating the unknown or un-understood.
13 (Refer Slide Time: 28:54) (Refer Slide Time: 29:49) Then after we have built the prototype, we evaluate and refine. And if necessary we go back and repeat this whole cycle. When the evaluation leads to clearly defined requirements, then we are ready to build the product. And this is done using the standard engineering approach. So product development takes place once the prototyping cycles are gone through and we have come to a clearly defined requirements document for the final product. Now there are of course some limitations to prototyping. There are situations where prototyping is ideal, but at the same time we need to be aware of these limitations. First the customer may be happy with the prototype itself and may demand that the prototype be released for his operations or functions.
14 This is not really appropriate because the prototype may work in the beginning for some time, but it may not be maintainable. It may not give the kind of performance and it may not have the rugged design that is required for sustained operations. The second problem could be that the process of prototyping. The developer gets so attached to some of the approach he has used, that he doesn t try to refine them or look for better way of building the same functionality. In that case we may actually have difficulties with the quality performance or other attributes of the software. What it really means is that, we develop a some kind of blindness towards other possible techniques or better way of doing things, because whatever way we implemented something in the prototype, we continue the same in the product. Good tools need to be acquired in order to do a prototype because we want to complete the prototype quickly in the minimum cost. So this is an investment we may have to make which adds to the cost of the project. So one of the problems with prototyping is that it may lead to a higher project cost and there are other problems that we have just mentioned. So when we have such difficulties based on the requirements or based on the situation we might choose some other development methodologies, one that may seem again obvious is the iterative development. (Refer Slide Time: 32:23) In the iterative development we define the initial scope and try to build a product which will meet the initial scope that was identified and then release it quickly to get customer feedback. Here iterative development is a good methodology for those software projects which want to build products, which will be of use to many customers. So here we are developing a product whose functionality may not be clearly known or there may be too many features that we may want to provide. But we would rather like to release a product quickly capture the market and get customer feedback. So this is the situation which is ideal for iterative development.
15 Here the development takes place in multiple iterations and many versions of the software may be released. You must be already familiar that some of the products such as database products or packages like pay roll or accounting packages are available in the market in versions. Basically the latest version represents additional features which have been added from the previous version based on the requirements as perceived or based on the customer s feedback. When we develop the initial version we may of course follow any method. For example, we may follow the waterfall method for the initial version of the product. (Refer Slide Time: 34:53) We generally maintain a list of features which have to be implemented in future releases and we will come out with the versions in the future as we implement these features and release the product. Each version will be analyzed and we will keep on updating our featured list. So our third methodology is the iterative development. Finally we have methodology called spiral model. In the spiral model we go through the development in cycles and each cycle is divided into four quadrants. These quadrants as you see here are named; the first quadrant, we tried to define the objectives alternatives what are the constraints. So this is the starting point. Then we evaluate those alternatives and clearly identify the risks. Now these risks may be pertaining to the interfaces, pertaining to performances and so on. Based on these risks in the third quadrant of the cycle, we tried to define what implementation will perform, and after the third in the fourth quadrant we identify how we will plan the subsequent cycle.
16 (Refer Slide Time: 36:00) So in this case we have development going on in cycles and as we go through the cycles the different risk issues are addressed and more refinements are done to our strategies, to the functionalities in the case of spiral model. So spiral model basically identifies risks at every step and it identifies the ways of addressing those risks either by following the prototyping methods, or going through simulations, or carrying out benchmarking. So at every development step we will decide in what way we want to follow. It is primarily a risk driven approach. The spiral model consists of different cycles. In each cycle we try to address some risk element that we see. And we plan the development, in order to identify ways of addressing that risk. So if we have a risk perception about what kind of user interfaces we should build, then we do prototyping. If a user interface and performance issues are quite well understood, then the risk may be just the development risk. In that case we decide to follow the waterfall model.
17 (Refer Slide Time: 37:00) So in the case of spiral model, it s a risk driven model it allows us to use a mix of different approaches, which may be specification oriented approaches like waterfall model, or prototyping, or simulation. So unlike the incremental model where we try to release the different versions in the features of the product, here in the spiral model as we go through the different cycles, we try to address different risks. This model was proposed by Boehm and here is a diagram which defined a few cycles of the development process in the spiral model. (Refer Slide Time: 38:28)
18 You can probably see it on any of the books. In each cycle the four quadrants basically try to address what we mentioned earlier. They enumerate alternatives, and then they evaluate those alternatives, try to identify the risks and build a development and carry out evaluation for the next phase. So the spiral model addresses the different risks and can be used in large projects where both the requirement risk is present and development risk is present. We have seen these different development methodologies. We saw three or four of them the waterfall model the prototype model. Now let us move on to another process which is equally important and you are going to study this in more details. But at this point i will only give an overview of the management process. As we said earlier, any large project needs to be managed. We prepare a project plan and we then manage the whole project according to that plan. So naturally the project management runs in parallel to the whole development process. As the development is progressing we are having a continuous management oversight. So in the case of project management, we have primarily, activity of defining the project plan. In the project plan we will identify different activities, resources, deliverables, and timelines and so on. So once the plan is ready then we will monitor it and also control as it progresses. A project plan indicates how the project will be executed. And there are very important things we must understand about the planning. A project plan is absolutely essential for successful completion of the project. Therefore we must appreciate some of the points which are important in a project plan. The first is that if you do not have a plan then there is no management. There is no question of doing any management if the plan does not exist. Then without making any measurements, it is not possible to prepare any plans. (Refer Slide Time: 40:35) This is a very important truth that in order to prepare a plan, you must identify the activities not only qualitatively but quantitatively.
19 You must learn to measure those aspects which we want to bring under the management control. So without measurement, planning is not possible. Without planning, management is not possible. It is very important that first we learn to make measurements; we measure those aspects of the project which we want to bring under the control of the management. Make a plan and then perform the management as we continue with the development. That plan allows progress to be measured. Since it consists of different activities, as we complete these activities, and as we know the effort distribution among these activities, we know how far we have progressed and how much still remains to be done. So when you have the plan you can measure the progress. We generally prepare this plan before the development begins. As we said earlier it may be produced along with the analysis or even before the analysis is completed. So we prepare a plan as soon as we have a good idea about the complexity of the project and we start getting a good feel of the requirements. Once we have done this, obviously this plan needs to be constantly updated. We will get management inputs from the development team. And based on the progress of the work, we may have to update the plans we have already made. How do we prepare the project plan? What are the important steps that need to be taken in this? The first important step is that we must estimate the cost and effort. This is the quantification that we talked about just now. We need to measure how much effort is involved in carrying out a project. Now this will naturally be based on the complexity of the project, the scope of the project, productivity levels of our people, who will be implementing the project, and also other historical data of similar projects. We will naturally benefit from the previous experiences. So we should clearly keep a record of other projects performed by us. Understand our productivity levels and then estimate the effort or the cost for the new projects that we are undertaking. There are different models available for cost and effort estimation. And in this course later on you will learn more about these models. Once we have done the effort estimation, then we select the right development process. We said earlier that there can be many different types of processes. So you choose the one which is best suited for task at hand. You define the milestones and you prepare a schedule. In order to prepare this schedule we of course need to know how the effort is distributed over the different steps. We had seen one graph where we had shown the relative effort distribution over different steps in a typical waterfall kind of a methodology. We should have our own data from our past experiences. So that the overall effort estimated by us can be distributed over these different steps and we can prepare a detailed schedule for execution of the project. And then we decide on project staffing; who will perform the different steps, how many people will be made available, what are the scheduling requirements, what are the overall calendar time in which the project needs to be completed. We will also make explicit quality control plans. In the overall plan, we will schedule reviews and inspections at appropriate points.
20 (Refer Slide Time: 45:42) We will define testing strategies, so that we can maintain a control over the defects and we can ensure a quality product from our approach. These are the different steps in the preparation of a project plan. You need to identify the effort. You need to know how the effort is being distributed, you need to commit resources for different steps and you need to make explicit quality plans. Because quality will naturally have cost implications, you will need to spend effort in identifying the defects, which might go from one step to another through the various deliverables that the steps produce. So these are the different project plan elements. Once the project plan is in place we will use it for monitoring and control. The plan defines the various activities we may represent it in different ways. There are Gantt chart, Time bar chart or PERT by CPM type of activity networks which are used for representing a plan. Essentially the plan shows the different activities. It shows expected durations for different steps and what kinds of resources have been allocated to those activities. In a network of activities like this, we can identify which is the critical path. If we do not meet the schedule requirements for the critical path then the project may get delayed. So we identify which are the critical activities and how to keep them under control. So that they are carried out in the expected duration and in the expected cost. If it is not done then there is going to be a significant impact on the overall project.
21 (Refer Slide Time: 47:05) So these are important project monitoring aspect and we use different types of analysis techniques by representing the project plan in a proper form such as a bar chart or as activity network. Each development step you will recall, will give information for tracking the progress of the development. We had said earlier that every step produces input for the management and this information will be used by the management for identifying possible bottom necks and the reason for delays if there is any. And we will enable the management to take corrective action. So project plan allows you to monitor the project and also control over the progress of the project. Let us now summarize we have in this particular lesson. We have we have introduced the software engineering topic. We have looked at the importance of applying engineering approach to development of large software project. We define what we mean by engineering. So now we should be very clear how we benefit by applying an engineering approach to software development. We identified different types of software processes. We defined a stepwise process definition where the software methodology consists of multiple steps. We made a very rigorous definition of what we mean by a software development step. It has entry criteria exit criteria something specific to be done, some techniques to be employed some documentation, or some other output to be produced which will be used by subsequent steps. So the essence of engineering approach is to define a stepwise methodology for carrying out the project. We saw the waterfall model and other models. We tried to understand their strengths and their weaknesses. We saw that the waterfall model consists of many steps arranged in a proper sequence and it identifies many different deliverables which are very important not only for completing the project but for future maintenance of the project. We saw then limitations of waterfall model and how other models tried to address those limitations such as the prototyping model or the spiral model.
22 And finally we briefly talked about the project planning. Key observations we made here is that if you do not have a project plan you cannot manage the project. And project management is actually very important in any large project. And another key point was that, in order to prepare a project plan it is important that we learn measurement techniques. We keep historical data, we learned how to effort how to do the effort estimation. We also understand how the effort is distributed in different steps. So once we have a good understanding about these issues and we also maintain data about similar projects that we might have done in the past, we will be able to prepare the project plan with a great amount of confidence and we will be able to carry out the whole project as per the plan.
4 Software Development Life Cycle M MAJOR A J O R T TOPICSO P I C S Objectives... 52 Pre-Test Questions... 52 Introduction... 53 Software Development Life Cycle Model... 53 Waterfall Life Cycle Model...
CHAPTER_3 SOFTWARE ENGINEERING (PROCESS MODELS) Prescriptive Process Model Defines a distinct set of activities, actions, tasks, milestones, and work products that are required to engineer high quality
Software Development Life Cycle (SDLC) Supriyo Bhattacharjee MOF Capability Maturity Model (CMM) A bench-mark for measuring the maturity of an organization s software process CMM defines 5 levels of process
Module 2 Software Life Cycle Model Lesson 4 Prototyping and Spiral Life Cycle Models Specific Instructional Objectives At the end of this lesson the student will be able to: Explain what a prototype is.
Process Models and Metrics PROCESS MODELS AND METRICS These models and metrics capture information about the processes being performed We can model and measure the definition of the process process performers
What is a life cycle model? Framework under which a software product is going to be developed. Defines the phases that the product under development will go through. Identifies activities involved in each
Process Methodology for Wegmans Deli Kiosk Version 1.0 Prepared by DELI-cious Developers Rochester Institute of Technology September 15, 2013 1 Table of Contents 1. Process... 3 1.1 Choice... 3 1.2 Description...
What is a system? Software Engineering Software Processes A purposeful collection of inter-related components working together to achieve some common objective. A system may include software, mechanical,
Chapter 7 - Project Scheduling and Tracking Overview The chapter describes the process of building and monitoring schedules for software development projects. To build complex software systems, many engineering
International Journal of Research in Information Technology (IJRIT) www.ijrit.com ISSN 2001-5569 A Comparison between Five Models of Software Engineering Surbhi Gupta, Vikrant Dewan CSE, Dronacharya College
CHAPTER 24 SOFTWARE PROJECT SCHEDULING Overview The chapter describes the process of building and monitoring schedules for software development projects. To build complex software systems, many engineering
LECTURE 1. SYSTEMS DEVELOPMENT 1.1 INFORMATION SYSTEMS System A system is an interrelated set of business procedures used within one business unit working together for a purpose A system has nine characteristics
Classical Software Life Cycle Models SWEN 301 Trimester 1, 2015 Lecturer: Dr Hui Ma Engineering and Computer Science Lecture slides make use of material provided on the textbook's companion website Motivation
Using Simulation to teach project management skills Dr. Alain April, ÉTS Montréal email@example.com Agenda of the workshop 1 The software project management theory overview (40 minutes) 2 Why use SDLC
SWEBOK Certification Program Software Engineering Management Copyright Statement Copyright 2011. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted
Software Development Process Models Balasankar C S1 M.Tech CSE 1 / 24 Software Development Process Models Activities directly related production design, coding, testing Specifies major development & quality
Engineering Process We need to understand the steps that take us from an idea to a product. What do we do? In what order do we do it? How do we know when we re finished each step? Production process Typical
SE464/CS446/ECE452 Software Life-Cycle and Process Models Instructor: Krzysztof Czarnecki 1 Some of these slides are based on: Lecture slides by Ian Summerville accompanying his classic textbook software
Software Development Life Cycle (SDLC) and Development Methods There are some enterprises in which a careful disorderliness is the true method. Herman Melville Capability Maturity Model (CMM) A Capability
INTERNATIONAL JOURNAL OF ADVANCES IN COMPUTING AND INFORMATION TECHNOLOGY An International online open access peer reviewed journal Research Article ISSN 2277 9140 ABSTRACT Analysis and tabular comparison
Chapter 3 Chapter 3 Project Management Learning Objective...to give an appreciation for and to introduce project management and to place it into context and give some of the fundamentals to project management
Processing Models Of SDLC Mrs. Nalkar Sanjivani Baban Asst. Professor, IT/CS Dept, JVM s Mehta College,Sector 19, Airoli, Navi Mumbai-400708 Nalkar_sanjivani@yahoo.co.in Abstract This paper presents an
Project Time Management Plan Schedule Management is the process of establishing the policies, procedures, and documentation for planning, developing, managing, executing, and controlling the project schedule.
Software Life Cycle Lecture Objectives What happens in the life of software To look at the life cycle of a software To understand the software process and its related elements To relate to the different
Audit Checklist The following provides a detailed checklist to assist the audit team in reviewing the health of a project. Relevance (at this time) How relevant is this attribute to this project or audit?
(Refer Slide Time: 00:54) Management Information System Prof. B. Mahanty Department of Industrial Engineering & Management Indian Institute of Technology, Kharagpur Lecture - 18 Data Flow Diagrams - III
Foundations for Systems Development ASSIGNMENT 1 Read this assignment introduction. Then, read Chapter 1, The Systems Development Environment, on pages 2 25 in your textbook. What Is Systems Analysis and
Project and Production Management Prof. Arun Kanda Department of Mechanical Engineering Indian Institute of Technology, Delhi Lecture - 9 Basic Scheduling with A-O-A Networks Today we are going to be talking
Project Audit & Review Checklist The following provides a detailed checklist to assist the PPO with reviewing the health of a project: Relevance (at this time) Theory & Practice (How relevant is this attribute
Various Software Development Life Cycle Models Sahil Jindal, Puneet Gulati, Praveen Rohilla Dronacharya College of Engineering, India Abstract:An SDLC model is a conceptual framework describing different
N CYCLES software solutions Development Methodologies Compared Why different projects require different development methodologies. December 2002 Dan Marks 65 Germantown Court 1616 West Gate Circle Suite
Ensuring Reliability in Lean New Product Development John J. Paschkewitz, P.E., CRE Overview Introduction and Definitions Part 1: Lean Product Development Lean vs. Traditional Product Development Key Elements
General Problem Solving Model Software Development Methodology These focus on understanding what the problem is about Chapter 2A Concerned with understanding more about the nature of the problem and possible
Software Engineering Introduction & Background Department of Computer Science Kent State University Complaints Software production is often done by amateurs Software development is done by tinkering or
Software Process Models The Basic Waterfall Model In Defense of Prescriptive Models Issues in Waterfall Models concurrent development phase transitions and overlap Issues in Evolutionary Models incremental
CS/SWE 321 Sections -001 & -003 Software Project Management Copyright 2014 Hassan Gomaa All rights reserved. No part of this document may be reproduced in any form or by any means, without the prior written
J.S. Bradbury, J.R. Cordy Software Process I Quality in Context In order to understand the roles of quality assurance in software development, we must understand how software development works - we cannot
Software Process for QA Basic approaches & alternatives CIS 610, W98 / M Young 1/7/98 1 This introduction and overview is intended to provide some basic background on software process (sometimes called
Module 10 Coding and Testing Lesson 23 Code Review Specific Instructional Objectives At the end of this lesson the student would be able to: Identify the necessity of coding standards. Differentiate between
JOURNAL OF OBJECT TECHNOLOGY Online at www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2006 Vol. 5. No. 8, November-December 2006 Requirements Engineering Tasks Donald Firesmith,
2. Analysis, Design and Implementation Subject/Topic/Focus: Software Production Process Summary: Software Crisis Software as a Product: From Programs to Application Systems Products Software Development:
PROJECT SCHEDULING AND TRACKING PROJECT SCHEDULING AND TRACKING Software project scheduling is an activity that distributes estimated effort across the planned project duration by allocating the effort
Example Software Development Process. The example software development process is shown in Figure A. The boxes represent the software development process kernels. The Software Unit Testing, Software Component
CSE 435 Software Engineering Sept 16, 2015 2.1 The Meaning of Process A process: a series of steps involving activities, constraints, and resources that produce an intended output of some kind A process
pm4dev, 2015 management for development series Project Schedule Management PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS A methodology to manage development
Contents Introduction Software Development Processes Project Management Requirements Engineering Software Construction Group processes Quality Assurance Software Management and Evolution Last Time - Software
6. Software Lifecycle Models A software lifecycle model is a standardised format for planning organising, and running a new development project. Hundreds of different kinds of models are known and used.
Unit I Introduction Product Life Cycles Products also have life cycles The Systems Development Life Cycle (SDLC) is a framework for describing the phases involved in developing and maintaining information
SPECIFICATION BY EXAMPLE How successful teams deliver the right software Gojko Adzic MANNING Shelter Island Brief Contents 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 Preface xiii Acknowledgments xxii
University of Dublin Trinity College ST3006 - Software Engineering Anthony Harrington Department of Computer Science Trinity College Dublin Anthony.Harrington@cs.tcd.ie Lifecycles A software project goes
5/19/2014 1 Professor Lili Saghafi MANAGING INFORMATION TECHNOLOGY Lecture 9 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT By : Prof. Lili Saghafi 1-2 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT Large
IV. Software Lifecycles Software processes and lifecycles Relative costs of lifecycle phases Examples of lifecycles and processes Process maturity scale Information system development lifecycle Lifecycle
CS4507 Advanced Software Engineering Lectures 2 & 3: Software Development Lifecycle Models A O Riordan, 2015 Some diagrams from Sommerville, some notes from Maciaszek/Liong Lifecycle Model Software development
Introduction to Systems Analysis and Design What is a System? A system is a set of interrelated components that function together to achieve a common goal. The components of a system are called subsystems.
Project management Organising, planning and scheduling software projects Software management distinctions The product is intangible The product is uniquely flexible Software engineering is not recognized
The Plan s Journey From Scope to WBS to Schedule Presented by: Rick Clare, CBAP, PMP, OCP, CSM PM Centers USA, LLC. 2013 Company Background Consulting and Training (Virtual, Public and Private Training)
Software Engineering Prof.N. L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-12 Data Modelling- ER diagrams, Mapping to relational model (Part -II) We will continue
Volume 4, Issue 6, June 2014 ISSN: 2277 128X International Journal of Advanced Research in Computer Science and Software Engineering Research Paper Available online at: www.ijarcsse.com Comparative Analysis
System/Software Development Life Cycle Anurag Srivastava Associate Professor ABV-IIITM, Gwalior Why Life Cycle Approach for Software? Life cycle is a sequence of events or patterns that are displayed in
PHASE 3: PLANNING PHASE The ning Phase focuses principally on required project planning work. Proper comprehensive project planning is essential to a successful IT project, and incomplete project planning
Software Engineering Objectives Designing, building and maintaining large software systems To define software engineering and explain its importance To discuss the concepts of software products and software
Software Development Process A software development process, also known as software development lifecycle, is a structure imposed on the development of a software product. Similar terms include software
Work Breakdown Structure (WBS) The building blocks of a schedule start with a Work Breakdown Structure (WBS). The WBS is a hierarchical reflection of all the work in the project in terms of deliverables.
Custom Software Development Approach Our approach to custom software development combines benefits from several standard development process models. We tend to have a well-defined, predictable and highly
Software Engineering Prof. Shashi Kelkar Department of Computer Science and Engineering Indian Institute of Technology, Bombay Lecture - 31 Project Time Management Today we are going to talk about project
Project Scheduling & Tracking Traditional Techniques: Work Breakdown Structure (WBS) Gantt Charts Precedence Diagrams Earned Value Planning It is the mark of an instructed mind to rest satisfied with the
Nova Software Quality Assurance Process White Paper Atlantic International Building 15F No.2 Ke Yuan Yi Road, Shiqiaopu, Chongqing, P.R.C. 400039 Tel: 86-23- 68795169 Fax: 86-23- 68795169 Quality Assurance
Noorul Islam College of Engineering M. Sc. Software Engineering (5 yrs) IX Semester XCS592- Software Project Management 8. What is the principle of prototype model? A prototype is built to quickly demonstrate
PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME > Date of Issue: < date > Document Revision #: < version # > Project Manager: < name > Project Management Plan < Insert Project Name > Revision History Name
International Journal of Soft Computing and Engineering (IJSCE) ISSN: 2231-2307, Volume-3, Issue-1, March 2013 Evolving a New Software Development Life Cycle Model SDLC-2013 with Client Satisfaction Naresh
Introduction & Procedural Programming Sample Courseware Introduction to Software Paradigms & Procedural Programming Paradigm This Lesson introduces main terminology to be used in the whole course. Thus,
Project Scheduling Goals of the Unit Making the WBS into a schedule Understanding dependencies between activities Learning the Critical Path technique Learning how to level resources!2 Initiate Plan Execute
Agile Software Engineering Practice to Improve Project Success Dietmar Winkler Vienna University of Technology Institute of Software Technology and Interactive Systems firstname.lastname@example.org
RESEARCH ARTICLE International Journal of Computer Techniques - Volume 2 Issue 4, July - Aug Year Evolving a Ultra-Flow Software Development Life Cycle Model Divya G.R.*, Kavitha S.** *(Computer Science,
SLCM 2003.1 Artifacts in a Nutshell ( as of 01/21/2005) Project Development Phases Pension Benefit Guaranty Corporation s (PBGC) System Life Cycle Methodology (SLCM) is comprised of five project development