 ॐ ॐ ॐ ॐ ॐ ॐ ॐ ॐ ॐa ॐ a ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐa ॐ दिजानिग can be done by using the high level designing and low level designing दिजानिग and low level designing, by using some UML diagrams दिजानिग can be done, in coding all programs are prepared जिवाय program, database program, interface programs are prepared in coding phase, and testing phase आल program are tested and bugs are removed, in maintain phase the software deployed to the customer side and then we have to provide अपट्रिष्ट ल्ज़ाद software, to the users So, users can make the operational use of the software in the last phase. The objectives of softening models, maintainability, it should be feasible for the software to all meet changing requirements. Correctness, a software product is correct if the requirements are specified in the SRS document, have been correctly implemented, reusability. A software product has good reusability in different models of the product, can easily be reused to develop new products. Testability, here software facilitates both the establishment of test criteria and the evaluation of software with respect to those criteria. Reliability, it is an attribute of software quality, the extent to which a program can be expected to perform its desired function over an arbitrary time period. Voltability, in this case software can be transferred from one computer system or environment to another. Adaptability, in this case software allows using different system constraints and user needs. To be satisfied by making changes to the software. Now, we are going to see the time boxing model. So, this is the diagram of time boxing model and this is the software which is we are going to develop. For that the TB1 means time boxing frame 1, TB2 time boxing frame 2, TB3 time boxing frame 3. In TB1, the constraint of 3 activities, analysis, implementation and deployment. In implementation, we are designing and coding can be done in the implementation. So, here the parallel activities can be carried out and individual teams are working in every time boxing frame activity. So, after completion of analysis work of time box 1, TB1, the working of analysis of the TB2 can be started and also the implementation work also starts of TB2. So, after finishing the analysis and this analysis of TB2 finished, the TB3 framework working can be started. So, here parallel working can be done by using the time frame activity, TB1, TB2 and TB3. TB means time boxing framework. So, in this way the software can be developed by using the parallel activity in time boxing model. So, in the time boxing model the development done iteratively as in the iterative enhancement model. In time boxing model each iteration is done in a time box or fixed duration. The functionality to be developed it adjusted to fit the duration of the time box. Moreover each time box is divided into sequence of fixed stages where each stage performs a clearly defined task such as analysis, implementation and deployment that can be done independently. This model also requires that the time duration of each stage is approximately equal so that pipelining concept is employed to have the reduction in development time and product releases. So, time boxing model there is an individual team for each stage so that the work can be done in pipelining. The stages can be chosen such as a way that each stage performs some logical unit of work that becomes the input to the next stage. So, in each time boxing framework some task is achieved and then we are going to perform another task. So, likewise after completing the second task we are going to start the third task. Likewise we have to carry out the parallel operation in the time boxing model. The time boxing and iterative development but fix an iteration duration then determines the specifications. Time boxing model divide iteration into few equal stages. Use pipelining concept to execute iteration in parallel. So, this diagram shows there are two types of time boxing, linear time boxing and pipeline time boxing. In linear time boxing what exactly in the first framework TB1 we are doing the activity requirements, analysis, building and deployment. After completing the first activity of TB1 means after completing TB1 we have started the second activity that is TB2. Gathering the requirements, building the software and deployment of that software. In building we can done designing and coding can be done in the build phase of the time boxing execution. So, in linear time boxing after finishing the work of time boxing 1 then we are going to start the work of time boxing 2. But in pipeline time boxing the parallel work can be done means what the requirements of TB1 can be finished. Then we are starting the to build the requirements in the TB2 we are starting the work of the next task that is requirement build and deploy. Again after finishing the work requirements of TB2 we are starting the work of doing TB3 that is requirements of TB3. After finishing TB3's work we are going to start the work of TB4 means after finishing the work of TB3 requirements we are going to start TB4 requirements. Likewise we have to complete TB1, TB2, TB3, TB4 this all the time framework can be carried out parallelly they are performing their operations parallelly in this time boxing execution. So, time box iterations generally iterative development fix the functionality of each iteration then plan and execute it. In time box iteration fix the duration of iteration and adjust the functionality to fit it complete completion time is fixed the functionality to be delivered in flexible. So, fixed time box is given that is the some time duration given for executing the task here. So, first type is linear time boxing this is itself very useful in many situations had predictable delivery times over product releases and marketing can be better planned makes time non-negotiable parameter and helps focus attention on schedule prevents requirements floating overall development time is still unchanged pipeline time boxing multiple iterations executing in parallel can reduce the average completion time by exploiting parallelism for a parallel execution can borrow pipelining concept from hardware this leads to pipeline time boxing process model pipeline execution a team starts executing it 1 a team finishes hands over it to 1 to b starts executing it to a team finishes it to hands over to b team b team finishes it 1 hands over to b team at starts of 3 b team starts second but d team it first think and write now I am going to ask one question to all the students you have to pause the video and write the answer in time boxing model each iteration is done in a in a dash dash dash of fixed duration option a time box option b framework frame box option c duration box option d none of these so pause the video and read the answer the correct answer is time box in time boxing model each iteration is done in a time box of fixed duration time boxing execution duration of each iteration is still the same total work done in a time box is also the same productivity of a time box is same yet average cycle time or delivery time has reduced to a third team size large teams can be made in linear execution of iteration the same team perform all stages if each stage has a team of size t then in linear execution the total time team size is t in the pipeline execution the total team size is 3 times 1 for each stage total team size in time boxing is larger and this what reduces cycle time time boxing allows structured way to add human resources to reduce cycle time in time boxing model we cannot change the time of iteration work allocation different to allow larger teams to function properly so this is the work allocation the team the requirements team that is the requirements analysis of tb1 tb2 tb3 tb4 building team after finishing 1 build 1 build 2 build 3 build 4 then deployment after finishing build tb1 then deployment tb1 tb2 tb3 like where the work allocation of the teams can be done advantages it shorten delivery times it is an iterative in nature it make distributed execution it speed up the development process and shorten the delivery time this model is well suited to develop projects with a number of features in short time period time boxing is well suited for project that require a large number of features to be developed in short time around stable architecture using stable technologies disadvantages larger teams are required where high synchronization needed project management configuration management is harder complexity in project management not suited to projects in which entire development work cannot be divided into multiple iteration of almost equal duration applicability used when short delivery times used when architecture stable flexibility in feature grouping for larger heavily managed teams these are the references thank you