Wednesday, October 9, 2019

Network design and simulation Essay Example | Topics and Well Written Essays - 1750 words

Network design and simulation - Essay Example More importantly, it will be analyzed and properly assess to estimate the cost of networking. Study and recommendations for appropriate networking topology based on physical structure of the building. The advantage and disadvantage of such recommended topology. The works include surveys, cabling, server, workstations and network adapter configurations, installation of switches in strategic locations, operating systems, utilities and application software and commissioning. Installation of Microsoft Windows Server 2003 in the Network Server. It is a multipurpose operating system competent of handling a varied set of server roles such as file and print serving functions. In the anticipated expansion it will provide World Wide Web services such as e-mail, terminal, streaming media, remote access and virtual private networking. Dependable, "Windows Server 2003 is the fastest, most reliable, most secure Windows server operating system ever offered by Microsoft. Windows Server 2003"(Microsoft, 2002). It provides IT infrastructure that delivers fundamental value: improved reliability, better availability, and increased scalability. This includes application platforms with built-in traditional application server functionality on top of "extensive operating system capabilities and integrated information worker infrastructure that helps keep business information... This includes application platforms with built-in traditional application server functionality on top of "extensive operating system capabilities and integrated information worker infrastructure that helps keep business information secure and accessible" (Microsoft, 2002). The business will now have a LAN that combines intranets and Internet sites (in the future). This will also increase system security, which is critical in a network. 2. Workstation Operating System Along with the Microsoft Windows 2003 Server, the installation of its Client on every workstation in the network will be implemented. The client also have the same reliability and functionality that would match modern computer applications. 3. Document Processing The installation of Microsoft Office 2003 that includes business solutions such as Microsoft Word, Excel, PowerPoint and Access. A complete package that would enable worker collaboration, file sharing that would increase workers productivity. Question 3: Comparative Traffic Flow Rates (to use the information I send to you by the "Estimating traffic volumes and patterns) Traffic Volume The proposed network will be divided into understandable segments. Using the White Box approach let us identify the 5 segments of the proposed networks with their estimated usage of various applications : (since the network currently do not have remote access, computations will be base on local traffic only) 1. Accounts a. word processing - 50% b. spreadsheets - 90% c. files- 10% 2. Sales a. word processing - 50% b. spreadsheets - 90% c. files - 10% 3. Service a. word processing -20% b. spreadsheets - 20% c. files- 60% 4. Customer Service a. word processing - 70% b. spreadsheets - 20% c. files - 10% 5.

Tuesday, October 8, 2019

Art History Essay Example | Topics and Well Written Essays - 1250 words - 5

Art History - Essay Example Herein, it should be noted that criteria of Claire Bishop, Jacques Rancià ©re, and Willi Bongard will be applied in this paper to assess the position of Tracy Emin. As a matter of fact, various research works have been carried out in order to assess the impact that artists have made on the art market. At the same time, art market has been greatly impacted by demand of quality. It is due to this reason that a number of viewpoints were inhibited to assess and judge art work. Thus, the subjective nature of judgments is further questioned as far as dematerialization of arts is concerned. At this point, Claire Bishop’s criterion rather helps in judging a work to be good in the contemporary arts. Claire Bishop stated that any art work can be considered as good if only it tends to follow roots of aesthetics and it allows enough space that can help one argue and question. In addition, Claire Bishop also marked that a good work creates a hope for development anew. Claire Bishop, who is a well-known curator and art critic, maintains the viewpoint that art rather became a collaborative practice for most of the artist in the beginning of 20th century. It was the era when communism collapsed from the society. At this point, there was little or no difference between art and society itself. The criterion of Claire Bishop notes that there are two significant wings of art revolution. Firstly, it is the painting and sculpture that is being created for the need of art market while on the other hand; there are creative artists of the modern world who are able to undertake radical work. Bishop has been observed to call modern artists to be avante-garde. As per the analysis of Claire Bishop of a good art work, it comes to understanding that an art work needs to be defined within the context of aesthetes. In this case, Tracy Emin can notably regard as a generator of good art. It is because her artistic works

Monday, October 7, 2019

HCM367-0801B-01 The Health Care Organization - Phase 2 Project Essay

HCM367-0801B-01 The Health Care Organization - Phase 2 Project - Essay Example own lovingly as Doc Vinny is well respected and admired by both the board of directors and the other senior leaders of Vitruvian health plan and Vitruvian physician partners. A change in the environment brought along with change in the senior management is always hard to accept at first; however it becomes easy if the change brings out more positive outcomes than negative consequences. Doc Vinny is a very pleasant and affable person, which makes it easier for the patients and the workforce to get along wit him. He seems to be the type that will allow everyone to perform their tasks with their control and allow freedom of decision making but under a strict eye. A lot of success and growth of Vitruvian Health plan can be accredited to his personalized of way of dealing with people. When it comes to being a leader, your human skills are as important as your technical knowledge. Doc Vinny fulfills both criteria at par. As a CFO, I know how important business clients are to this organizat ion; it is not only the patients but people who invest in the company that matter. Dr. Durro’s leadership style appeals to all and he has used his style to make relationships and ties that have helped him to build a several related companies that contributed to his "healthcare for all" philosophy that he has believed in ever since has graduated from medical school. His leadership style is more participative and democratic, which I think in today’s world is the key to success. His leadership style will have a positive impact on the people of VH as well people from VPP as his easygoing nature and people skills will keep the team close to each other. he is capable of creating an open and friendly organizational culture. (Clark, 1997) Doc Vinny, unlike Dr. Montenegro is completely inspired by technology. Dr. Montenegro did not believe in investing in expensive technology and investing in the computer systems. He was used to working with more traditional methods of management. Since

Sunday, October 6, 2019

Quitting Smoking Essay Example | Topics and Well Written Essays - 500 words

Quitting Smoking - Essay Example One of the major reasons for reverting back to smoking is that it has become a source of leisure time for me and an excuse to get outside the house for a breath of fresh air, a walk around the block or to the store. Still, the endeavors of quitting smoking have been a result of the realization of the financial, as well as the health problems related to it. The cost of a cigarette pack may seem trivial to an occasional smoker but the small amount of $7 tends to have a significant effect on the budget of a serious smoker who has greater consumption than an occasional one. Alongside the monetary effect of the addiction, smoking tends to increase one’s chances of getting cancer. It is usually witnessed that some instances prove to be life altering and compel the individual to adopt different paths. One such incident also took place in my life that made me realize that the harmful habit of smoking tends to effect the smoker, as well as the people around him. This notion was realized when I had to face the dilemma of having a 17 year old move into my mother’s house. His transition into my mother’s house not only meant that a teenager was being exposed to smoking all the time, it also brought up the situation in which he wanted me to sponsor his smoking. When this occurrence was revealed to my sister, she was very concerned about her son’s well being and disappointed in me for being an unconstructive influence on her son’s life. After suffering ethical issues and disappointment from my family, I finally took the decision of quitting smoking and trying to relieve myself from its addiction. Alongside making the decision of quitting smoking, I encouraged my nephew to quit too but my nephew turned a deaf ear to all of my reasoning of quitting smoking. My decision also proved to come in between my relationship with him since our common ground of communication had disappeared. Still, I stayed persistent and

Friday, October 4, 2019

The relationship between iron and zinc status and treatment of ADHD Essay

The relationship between iron and zinc status and treatment of ADHD (subject to modification) - Essay Example Diagnosis is therefore rather subjective and obtaining epidemiological data is cumbersome. Co-morbidities are often present and these make diagnosis even more difficult (Rowland, Lesesne et al. 2002). Despite these limitations, there are valid data that suggest that ADHD seems to have a higher rate of occurrence in white children than in black children in the USA (1.7% to 4.4% in 1997) according to treatment records obtained by physicians. (Olfson, Gameroff et al. 2003). Also, the national epidemiological survey in UK showed a lower prevalence of ADHD in black children than in white children (0.4% to 1.6%) (Meltzer, Gatward et al. 2000). There is the postulation that cases of ADHD in black children could possibly have been under-diagnosed in these societies simply because black families possibly lack access to health facilities due to poorer economic status. This argument may not be valid considering that even higher access to facilities by black families have not resulted in increas ed diagnosis of cases of ADHD in them. Moreover, the U.K epidemiological survey cuts across racial and socioeconomic barriers. ... The ADHD Help-Seeking model is a basis of understanding factors that are predictive of service access and utilization, with a view to using such understanding to break the barrier to service utilization in ADHD treatment (Eiraldi, Mazzuca et al. 2006). The model proposes that for effective treatment, there must first be problem identification on the part of the affected, and then the decision to seek help must follow. Also, service selection and service access by the affected are integral parts of the model pathway. It is believed that through its predictive nature, the model will provide answers to various questions regarding disparities in access to healthcare by various ethnic and racial groups. (Eiraldi, Mazzuca et al. 2006). The model however needs to be made stronger by reconstructing it on factors that are less general and are more specific for affected groups, so that individual needs could be more effectively met (Eiraldi, Mazzuca et al. 2006). Cultural influences could play a very significant role in the Teacher and Parent Ratings across cultural divides (Olfson, Gameroff et al. 2003). The prevalence rates for ADHD from 1997-2001 among African American, Hispanic and White children (6-11 years old) were obtained using a National Health Interview Survey. Information was obtained from parents about health and socio-demographic characteristics of their children. Drug therapy history was taken. Again, White children were found to have the highest rate of ADHD than any other ethnic group, though occurrence of learning disability was higher in the African American and Hispanic children. About 1% of Hispanic children were reported to have ADHD without LD, against 4% white children. Compared to white children, the percentage of

Throughout Ken Keseys tremendous novel Essay Example for Free

Throughout Ken Keseys tremendous novel Essay It is another meeting though with McMurphy which causes the most drastic and evident change to Chief Bromdens character. In the midst of a bed time conversation with the Chief, McMurphy gives him a packet of chewing gum, the Chief replies Thank you. The chief then goes on to state this again. This comment from the Chief can be taken in two separate ways; metaphorically the Chief has said thank you to McMurphy, but, on the other hand he has thanked McMurphy for the allowing him to open up and talk and realise that he is not, in fact, insane. As well as that, it also shows how all along McMurphys inclination about the Chief was right. During that night time conversation with McMurphy the Chief talks about how small he is, demonstrating how the combine has affected him. Youre lot bigger, toughern I am. McMurphy then replies, You stand a head tallern any man on the ward. There aint a man here you couldnt turn every way but loose, and thats a fact! The Chief then dismisses this comment No. Im way too little. I used to be big, but not no more. Youre twice the size of me. This repetitive negative, Not no more, illustrates how he feels negative towards himself too, and how broken a man he is due to his time spent in the combine. McMurphy realises that, with the size of the Chief, he could use him to lift the control panel which he hadnt been able to lift at the beginning of the novel. He begins to build up the chiefs morale by complementing him in a descriptive metaphor, giving an image of how life will change for the good, Oh man I tell you, youll have women trippin you and beatin you to the floor. He offers him a free place in his special body-buildin course, and as McMurphy walks down the hall to sign the Chief up for the fishing trip he pulls the covers off him and states Look there, Chief. Haw what did a tell ya? You growed a half foot already. This again is used by McMurphy to build Chief Bromdens self image. Due to the character building of McMurphy and the Chiefs ability to find the cause of his illness he grows into a new man, a man able to be rebellious and able to pull away from the tight grasp which the combine has upon him. This point of rebellion expresses the Chiefs refusal to mop the hall. They stuck a broom out for me to do their work up the hall, I turned around and walked back to the dorm, telling myself, the hell with that. This emphasises the change in Chief Bromdens character as he is now confident enough to refuse duties from the black boys. This alliteration in the description of the boys is used extensively throughout the novel, emphasisng there colour, in 1962 (when it was first published) there was a lot of racism, white people were far more superior, and also their age, showing how even boys are running the institute, telling the white men what to do. But the main change to the Chief is his ability to laugh. I could look down and see myself with the rest of the guys and watch them, us, swinging in laughter. This is an effective use of imagery, as this metaphor emphasises how the Chief has grown mentally stronger as a man, as earlier on in the novel he states, You cant really be strong until you can see the funny side to things. His mental strength is illustrated through his physical strength in the shower room. So I picked him off and threw him in the shower. He was full of tubes; he didnt weigh moren ten or fifteen pounds. Demonstrating how McMurphys plan of making the Chief grow back to his real size is working. The character of Chief Bromden develops even further as when he notices a fog being produced by the combine and refuses to, slip off and hide in it. No never again, as he knows, this time I had them beat, thus emphasising how he has nearly recovered from his sickness. Finally the Chiefs transformation is complete, when McMurphy comes back down to the ward after his lobotomy the chief kills him out of compassion and escapes by throwing the control panel at the screened window. After the lobotomy, McMurphy states that he cannot do things like he used to, hobbled like this, the metaphor highlights that the institute has now got total control over McMurphy, even though he is not literally hobbled, as in cannot walk properly, he cannot think for himself, is a vegetable, he is hobbled. However though, the path the Chief ventures out on after escaping from the hospital is the same as the ill fated dog took earlier on in the novel when chasing a goose as it met the oncoming headlights of a vehicle, thus emphasising the battle between animals and machinery and how machinery will always win. In conclusion Chief Bromdens character develops extensively through out the novel from being a fully fledged member of the chronics to conversing with McMurphy and even going on a fishing trip with the other patients. As the novel develops the Chief grows back to his original size, commits an empathy killing on McMurphy to save him from the life of a chronic and escapes from the grasp of the combine. However, the reader is left in a state of uncertainty at the end of the novel as they are unsure whether the story is being told by the Chief as a free man out with the hospital or if the combine have taken him back into their tight grasp and he is telling the story from recollection to another inmate. Show preview only The above preview is unformatted text This student written piece of work is one of many that can be found in our GCSE Ken Kesey section.

Thursday, October 3, 2019

Estimation Model And Decomposition

Estimation Model And Decomposition In this lecture we introduce project estimation to estimate project resource requirements, time duration, human effort, and cost. We also discuss the models and techniques used in the project estimation. We also discuss the estimation methods such as comparative, top-down, bottom-up (engineering), historical analogy and expert judgment. Then we presented decomposition technique to break down the project into tasks to assist us in estimating the project. We focus on the work breakdown structure (WBS) decomposition method. Learning Outcomes Understand estimation model Understand decomposition technique and planning tools 1.0 Introduction In this lecture we continue discussion of project management in software engineering. We start by introducing the project estimation to estimate project resource requirements, time duration, human effort, and cost. We discuss the models and techniques used in the project estimation. We also discuss the estimation methods such as comparative, top-down, bottom-up (engineering), historical analogy and expert judgment. Then we present decomposition technique to decompose the project into tasks to assist us in estimating the project. We focus on the work breakdown structure (WBS) decomposition method. 2.0 Estimation Model Project estimation is a highly subjective and person-dependent process. A project task could be done in one day by one person but could take a few hours by another person. Hence, different estimates could be given by different persons of the time it takes to perform a task. After actual execution and performing of the task, the time it has taken to be performed is a measured, actual and real time. Accordingly, any time estimate to performing the task that is not close to the actual time is inaccurate. Project estimates are established at early in a project by the software development team and corporation management. These estimates are required for project resources, work to be done, project cost, project schedule, and time to delivery. Project estimates are required during project planning which is a crucial phase of the project lifecycle. Project estimating techniques are available based on metrics accumulated from past similar project experiences. Projects should be estimated in a structured and formal way, otherwise, estimates are inaccurate and projects could be handed in late. Structured and formal project estimation methods that use sound techniques and understanding have the following advantages: They make estimates more accurate They allow the project team to reach a consensus on the estimates They improve the accuracy of those estimates They make it much more likely that projects will come in on time Project planning requires estimates of the: Resource requirements Human effort- in person-months Time project duration- in calendar time Project cost and budget In practice, project history and past experience are often used as a guide in estimating the above values. The estimation usually requires breaking the project into pieces. At early stages in a project the software development team and management team must establish estimates for resources required (human resources, equipment, software, space, tools, etc.), work to be done and time to product delivery. Cost, time, and resource estimating techniques are available based on metrics accumulated from past similar project experiences. Usually, several approaches and methods are used to estimate these values. Then, estimated values that result from different estimation methods are compared. If these values vary widely, then this variance is taken as an indication of the need for more information. Projects could fail due to different causes related to project estimation. For example, the initial estimation of the budget needed for the completion of the project could be too little or too much. This can also be applied to the duration of the project, as some projects fail due to too little time being assigned for completion. As well as this, another factor that leads to project failure is ill planning, where the whole project is not planned out right from the start. Also, the goals and objectives of a project, which are developed at the start of the project may be regularly altered/changed which as a result causes confusion within the workforce. In addition to this, due to technology being a fast-paced industry, the personnel of the project need to stay up-to-date with this rapid change in order to use the correct the technology for the project. Finally, a lack of or ineffective communication between the workforce of the project, regardless of their role and position, can also l ead to broken interactions and project failure. Estimates could be inaccurate due to different reasons including people injury, sickness, or resign. Project development teams could run into unexpected technical problems, etc. Therefore, the objective of estimation is that people in the organization who have the training and knowledge to give an honest, well-informed opinion of the effort (time, cost, resources, etc. ) required to do a task. The uncertainty about the project could be reduced and more accurate estimates could be generated by producing well-documents about the project scope and vision by the organizations management and by reaching a consensus on the tasks that must be performed by the development team members. This consensus could be reached through discussion of assumptions. The following are some project estimation techniques (models): Source Lines of Code (SLOC): Source Lines of Code (SLOC) is the oldest metric for estimating project effort and thus is the primary input of older cost estimation models. The accurate estimation of a software project estimate is based on size of the project to be built. Project size is translated into human effort, time and money. Software Equation: In software equation estimate data is collected for thousands of similar projects and a the estimation model is a software equation as given below: EPM = (L x Sk(1/3) / PP)3 x (1/d4) Where EPM- is the Effort in Person Months L is the number of code Line Sk is the factor of Special sKills PP is the Parameter of Productivity D is the project Duration Using SLOC as input for cost estimation has some disadvantages because estimating the SLOC early in the software development lifecycle can be difficult. Therefore, if the SLOC estimate is inaccurate, the output of the dependant cost estimation model will be inaccurate. Software LIfecycle Management (SLIM): SLIM was developed in the late 1970s. Wideband Delphi: Wideband Delphi is an effective technique in estimating software tasks. Proxy Based Estimating (PROBE): This is an estimation method that looks at the history of a person in terms of components he has built in the past. It states that a person constructing a component that he has previously constructed (or one similar to it) then the amount of effort that will go into building this component will roughly be the same. The Constructive Cost Model (COCOMO): COnstructive COst MOdel (COCOMO) is a software cost and schedule estimating method which was developed in the early 1980s. It was developed through an experiment which involved the analyzing and evaluating of results for 63 software development projects. COCOMO was updated in 1991 for modern development life cycles, in order to accommodate larger sets of data. It is calculated on the basis of 15 cost factors. These factors, sometimes called variables, cover the cost of the software needed, any computer hardware that will be used, and the cost of labor (wages). These are inputted into the model and as a result, an output is arrived at estimating the size and effort that need to be put into the project for it to succeed. The Planning Game: The Planning Game is the software project planning method developed by Extreme Programming (XP). It was developed in the 1990s. It is basically used to manage the negotiation between the development team and the stakeholders (Business customers). Unlike Delphi, PROBE, and COCOMO, the Planning Game does not require a documented description of the scope of the project to be estimated. Rather, it is a full planning process that combines estimation with identifying the scope of the project and the tasks required to complete the software. Estimates use comparative estimate, grass roots estimate, engineering estimate (bottom-up), top-down estimate, historical analogy estimate, expert judgment estimate, models estimate, and/or rules-of-thumb estimate. Typically, estimates are made using some combination of these/some of these estimate methods. These estimate methods are described in the following paragraphs. Comparative estimate: Comparative estimate compares project with past similar projects. One advantages of this method is that estimates are based on actual experience. One disadvantages of this method is that truly similar projects must exist. Engineering estimate (Bottom-up): Engineering Estimate (Bottom-up) assigns different components of the project to individuals to estimate. Then, component estimates are summed to obtain total estimate of the project. Advantages of this method include generation of accurate estimates because of detailed basis for estimate, promotion of individual responsibility, and support of project tracking. Some disadvantages of this method are that the method is time- consuming, detailed data is needed which may not be available, especially before the project starts or early in the project, and integration costs may be disregarded. Top-Down estimate: Top-Down estimate partitions the project into lower level components where life cycle phases begin at highest level. Some advantages of this estimate are that it is more applicable to early project estimates, it considers system level activities, it is faster, and easier to implement. Some disadvantages of this estimate is that it is less accurate than other methods, it tends to overlook lower-level components, and it provides little detail. Historical analogy estimate: Historical analogy estimate is based on using the software size, effort, or cost of a comparable project from the past. The comparison is made using measures or data that has been recorded from completed software projects. Analogical estimates can be made at high levels using total software project size and/or cost for individual Work Breakdown Structure (WBS) categories in the process of developing the main software cost estimate. Expert judgment estimates: Expert judgment estimates specifies that software development team consults with one or more experts. Some advantage of this estimate is that little or no historical data are needed, and it is good for new or unique projects. Some disadvantages of this estimate is that experts tend to be biased, and their knowledge level is sometimes questionable. This is a subjective estimate based upon what the estimator remembers from previous projects and gets modified mentally as deemed appropriate. If the estimator has significant recent experience in both the software domain of the planned project then, expert judgment can be relatively accurate. Model-based estimate: Model-based estimate uses mathematical relationships or parametric cost models. Parametric cost models are empirical relationships derived by using statistical techniques applied to data from similar previous projects. Rules-of-thumb estimate: Rules-of-thumb estimate come in a variety of forms and can be a way of expressing estimates as a simple mathematical relationship (e.g. cost = Lines_of_Code / 10) or as percentage allocations of effort over activities or phases based upon historical data (e.g. coding task is 22% of Total Effort). The popular project estimates approach is to use several methods and compare values. If these values vary widely, then this variance is taken as an indication of the need for more information. Model-based estimates along with high-level analogies are the principal source of estimates in early conceptual stages. At early stages of the project or before it starts, we usually do not have a clear estimates, but as a project matures and the requirements and design are better understood, analogy estimates based upon more detailed functional decompositions become the primary method of estimation, with model-based estimates used as a means of estimate validation or as a correctness check. Whatever method is used, it is most important that the assumptions and formulas are documented to enable more thorough review and to make it easier to revise estimates at completion of the project when assumptions may need to be revised. Expected Value for Software Size is computed as follows: Suppose that: Expected value for estimation variable (size) estimate = S, Weighted Average of Optimistic estimate = (S opt) Most likely estimate (S m) Pessimistic estimate (S pess ) Then, S can be computed as: S = (S opt +4 S m + S pess)/6 The calculation of the effort put in, in terms of persons-month, in a dynamic multi variable model can be defined as follows: Software Equation (E) = [LOC * B0.333/P]3 *(1/t4) Where: E is effort in person-months, t is the duration of the project, B is special skills factor, P is productivity. 2.1 Decomposition Technique Decomposition technique is used to estimate the project as presented in the previous section. After decomposing the entire project into a number of smaller tasks, we make project estimates. It is easier to handle smaller tasks than to handle a very larger project as a whole. So, the entire project (problem) is broken down into number of smaller tasks (problems) and then each smaller problem could be solved easily. Decomposition technique is used as a technique or model for cost and project estimate. It is difficult to estimate the project as one task. Therefore, the project is decomposed into smaller tasks and each task is estimated individually and then the partial estimations of project tasks are added up for the whole project. Decomposition technique is used as a technique or model for cost and project estimate. It is difficult to estimate the project as one task. Therefore, the project is decomposed into smaller tasks and each task is estimated individually and then the partial estimations of project tasks are added up for the whole project. A sound and formal estimate starts with a work breakdown structure (WBS). A WBS is a list of project major phases, deliverables, and work components (tasks) that will be built by the project that, when completed, will produce the final product. These work components/tasks can then be broken down into the activities that are required to build them. The concept of this technique is to break down the work into smaller tasks. Each task can in turn be broken down further. This technique is very useful for the project development team and project management team to become familiar with the scope of the project, identifies work tasks, needed resources, and cost estimation. It also helps to monitor the projects progress. Project managers use the Work Breakdown Structure (WBS) to estimate projects and make complex projects more manageable. Some advantages of using WBS include: Assists with more accurate project estimation in cost, effort, resources, and schedule Assists with project organization Helps with assigning responsibilities to project development team members. A WBS that is correctly designed allows for the easy assignment of tasks to a specific element of the WBS, cutting down on confusion/duplication of assigned tasks. Shows the control points and project milestones Helps explain the project scope to customers and stakeholders Assist in planning and control of the project Tasks and Subtasks are related to each other in the sequence of project task networks. Project Task networks graphically visualize the tasks/sub-tasks and their relationships. Project Task networks are also known as activity networks. The Work Breakdown Structure is a tree structure. The root of the tree is the whole project and the children of the root are the main tasks at first level of the tree which compose the project. At level 2 of the tree are the sub-tasks of the main tasks of the project at level 1. The rest levels of the tree are constructed similarly. Using the tree structure of the WBS allows the determining of secondary costs for tasks, resources, etc., into their advanced level parent tasks, materials, etc. The WBS is the basis for dividing work into defined tasks from which the, schedule, cost, and labor hour reporting can be established. There are many ways to decompose a project into tasks. Different project break-down ways lead to different estimates. If the generated WBS is incorrect, then the project estimates are wrong and time is wasted in doing the estimates. The project can be broken down by feature, by project phase (requirements tasks, design tasks, programming tasks, QA tasks, etc.), or by some combination of the two. WBS uses similar previous projects history and previous experience of projects that have been developed to generate project t estimates. Large projects are broken into more tasks than smaller projects or they can be broken into larger tasks than smaller projects. WBS, when created, is used by the project team to create an estimate of the effort required to perform each task. The most accurate estimates are those that rely on similar projects history and prior experience. Team members should review previous project results and find how long similar tasks in previous projects took to complete. Sources of delays in the past should be taken into account when making current estimates. The level of granularity of WBS varies depending on the level of abstraction and what information is available. At lower-levels of the WBS, expert judgment is the primary method used, while at higher levels of the WBS model-based estimates are more common. It is not possible to define a task set for the project uniquely. No set of tasks is appropriate for all types of projects. Project breakdown into tasks is dependent on the size of the project, complexities involved in the project, constraints of the projects and the skill set and capabilities of the team members working on the project. Project tasks have to be properly distributed according to the needs of the project deadlines and schedule. To develop a project schedule, a task set must be distributed on the project time line. The project set of tasks is defined based on the category of the project which is dealt with by the development team. Summary In this lecture we introduce project estimation to estimate project resource requirements, time duration, human effort, and cost. We also discuss the models and techniques used in the project estimation. We also discuss the estimation methods such as comparative, top-down, bottom-up (engineering), historical analogy and expert judgment. Then we presented decomposition technique to break down the project into tasks to assist us in estimating the project. We focus on the work breakdown structure (WBS) decomposition method. Exercises Is it possible to create a realistic estimate before the project team has agreed on the technical design for the software? When the team is working together to generate an estimate, should the testers estimate tasks which will be performed by the programmers? List three models of project estimate. What is estimated using project estimate? Describe the objectives of using decomposition technique? List advantages of decomposition technique for company managers. Describe the Source Lines of Code (SLOC) estimation method. List two advantages and two disadvantages of using The Constructive Cost Model (COCOMO). What is the difference between Engineering estimate (Bottom-up) and top-down estimate? Explain decomposition techniques. How do you define a task set for the software project? What are project task networks?