Sunday, August 25, 2019
Organizational change part 3 Essay Example | Topics and Well Written Essays - 1500 words
Organizational change part 3 - Essay Example The challenges of managing organizational change often scare away some leaders who opt to avoid change. This often has its own consequences. Organizational change, if approached in the right way, can lead the organization in the best direction in the industry and helps to keep the organization prepared for any future changes. The most critical part of organizational change lies with the leaders. An organizationââ¬â¢s leaders have to manage the change through planning, assessment and evaluation and have to ensure that every stakeholder in the organization buys in to the ides of change and is involved in it (Hechanova, and Teng-Calleja, 2011). Organizational change can be said to be successful if it meets its objectives and the benefits of the change are realized by the management and employees of the organization. Readiness for change is one of the issues that change management experts have focused on in the recent few years by recommending strategies that organizations need to tak e in order to be fully prepared for change. Readiness for change is a very crucial concept in healthcare given the ever changing nature of treatment. Healthcare organizations have to be strategically positioned so as to meet the demands brought about by change. An organizationââ¬â¢s readiness for change depends on various factors such as organizational culture, flexibility of the organizationââ¬â¢s policies, and the ability of leaders to manage changes in the working environment. Managing change in a healthcare facility is not different from other organizations (Weiner, Lewis & Linnan, 2009). The leaders have to be very assertive and proactive in steering health organizations in the right direction. This requires constant assessment of the current level of operations in the organization and determining what needs to be done so as to help improve treatment of patients. The need for the proposed change has been brought up by the increase in the number of deaths occurring from in vasive interventional radiology procedures in recent years. Despite having qualified and dedicated personnel, the deaths have increased persistently for many people to notice. It came to our realization that this was due to insufficient staff. The number of patients has increased significantly increasing the ration between patients and employees. This situation has created the need for a change in the organization which would include hiring of two nurses who will specifically handle patients in the radiology room. There are likely to be barriers to implementing this change. Some of the challenges in implementing the proposed change include lack of funds to initiate and manage the change as well as lack of receptors. Implementing the proposed change require creating strategies that will be used as guiding principles throughout the process. A change implementation strategy for organizations includes various elements that have to be carefully analyzed before the change process is imple mented (Hechanova and Teng-Calleja, 2011). These elements include situational awareness, the structures supporting the change, and strategy analysis. Situational awareness involves understanding the implications of change on the organizations, knowing who will be affected by the impending change and gathering as much resources and knowledge about the change to be implemented. Supporting structures
Saturday, August 24, 2019
Assignment Essay Example | Topics and Well Written Essays - 750 words - 5
Assignment - Essay Example In his discourse, he equivalently points out defects existing in the Irish political system and the neglect of the ruling class which, according to Swift, ought to be blamed altogether for the crisis that had been worsened by the mercantilist structure of British control over his nation. Prior to the endeavour of illustrating the substance of his proposition, Swift initiates ââ¬Å"A Modest Proposalâ⬠by briefing readers with a concrete picture of the grounds which he thinks amounted to a grievance that deserved an unordinary level of attention. He confesses ââ¬Å"It is a melancholy object to those who walk through this great town or travel in the country, when they see the streets, the roads, and cabin doors, crowded with beggars of the female sex, followed by three, four, or six children, all in rags â⬠¦ this prodigious number of children in the arms, or on the backs, or at the heels of their mothers, and frequently of their fathers, is in the present deplorable state of the kingdom..â⬠(Swift, 5). ... By concretization of the problem parts, creating rich imagery in the minds that must be inclined to ponder on taking urgent course of action toward resolution, and by providing a sensible knowledge of statistical estimates and proportion between resources and human count, the satirist gradually manages to promote a conscious thought of the central theme of his philosophy and the grave predicament for which it should apply. So, on claiming that children may be sold for consumption to which he adds ââ¬Å"instead of being a charge upon their parents or the parish â⬠¦ they shall on the contrary contribute to the feeding, and partly to the clothing, of many thousandsâ⬠(6), one may be perceived to understand not the irrational and ever inhumane principle of cannibalism, rather the gravity of the present circumstances and its future implications if unsettled. Moreover, Swift may be observed to have systematically spread vital details in adequate support of his arguments. In the e laborate numeration of the advantages corresponding his schematic proposal, Swift speaks of the reduction in the number of Papists, improvement in the capacity of poorer tenants to pay their rents, and the optimal circulation of goods and monetary gain once the large quantity of youth within the most tender ages could be turned into profitable carcasses and textiles. Then he continues to argue that the materialization of such an idea would keep ââ¬Ëconstant breedersââ¬â¢ from the burden of maintaining their offspring during growth, aside from the other benefits being a great economy for the Irish nation which would hence be brought to experience good dishes out of
Friday, August 23, 2019
Light Photography Assignment Example | Topics and Well Written Essays - 250 words
Light Photography - Assignment Example Diffusion scatters light making the source broader and softer. For example, when clouds drift in front of the sun, shadows get less distinct. For the shadows to disappear, just add fog. Thirdly, bouncing light acts as diffusion. By aiming a narrow source of light at a broad matte surface such as wall and ceiling, it will not only reflect the light but will also diffuse it by scattering it over a wider area. The further the light source, the more it falls off meaning it gets dimmer on your subject. If light is moved twice as far from the subject you end up with only one quarter of it on the subject. Light fall-off can be used for varying the relationship between the light on your subject and your background. If a light source is placed close to the subject, the fall-off from the subject to the background will be more pronounced. When light is moved further from the subject, the background will be relatively brighter. Generally, I have learnt a lot from the light photography assignment. Light lessens shadows, the closer the source of light the closer the light, diffusion scatters light, and that bouncing light acts as diffusion. The further the light source, the more it falls off, Light falloff can be used to vary relationship and Front lighting deemphasizes
Building Background and Comprehensible Input Essay
Building Background and Comprehensible Input - Essay Example It is important to acknowledge that teachers must meet the needs of English learners while addressing the needs of the mainstream student. This is quite a task but one that is possible to tackle. This lecture will address strategies that are essential for English learners to acquire content knowledge and improve academic language proficiency but these strategies will be beneficial to all learners. The lessons: Building Background and Comprehensible Input are both very good tools for teaching students especially those who are at the "maturing" stage. However, as both are being asked to be rated, the verdicts are as of follows: Comprehensible Input lesson received a 95% while Building Backgrounds received 100%. Now, as for the explanations; taking into consideration all the aspects of teaching and learning, the first topic which was Building Backgrounds received the perfect score because it is the root of all the teaching and learning process that transfer from one teacher to the student. Without this, all the effort that the professor gives out will be futile. Building Backgrounds is what its title says; making a sturdy base for the learning of the students. As the description goes, it is important for teachers to consciously incorporate techniques for students to acquire content knowledge and vocabulary content simultaneously. The Comprehensible Input or what you call the dig estive system of the mind is the result of a very good lesson planning. A very well thought-of lesson will stay in the minds of the students for a very long time and it may possibly be their pushing force of the thing that drives them most. It may be hard at first but thinking of lesson plans is actually easy if professors include the students in thinking up ideas for the lesson plan. With this, the students will be able to participate in the decision-making of their classes and thus, be motivated in studying and listening more to the studies because they are the ones who have thought of it in the first place. The Comprehensible Input on the other hand, is solely based on the process of Building Backgrounds. The students will not simply absorb the lessons if the structure of the topic is not attractive and barely retainable in the minds or the students. What is needed here is that the lessons should be highly retainable in terms that the students will remember it for the longest time and that it will be embedded in their minds and will be used for their future. Now, that is the purpose why students are being placed in an institution called, schools and universities. So that in times when the parents can no longer support the growing years of their children, the schools will be there to maintain the foundation that was set up by the family. So in other words, the school becomes the second home of the children. As for the effectiveness of each lesson, it has been established in the previous paragraphs the importance and the uses of the said lessons. However, as have been discussed, only one lesson
Thursday, August 22, 2019
National Food Security Bill 2013 Essay Example for Free
National Food Security Bill 2013 Essay Only three percent of Indians pay income tax; our tax-GDP ratio is among the lowest in the world. This must change. Our elites must realise that Indiaââ¬â¢s poverty has damaging consequences for them, and that they can help decrease it. The food security bill, with all its limitations, will hopefully contribute to generating such awareness, says Praful Bidwai. After vacillating for years over taking any pro-people measures, the United Progressive Alliance finally did something bold and worthy by having the National Food Security Bill passed in Parliament a promise made in the UPAââ¬â¢s ââ¬Å"first 100 daysâ⬠agenda after its return to power in 2009. The Bill won a resounding victory in the Lok Sabha, with a margin exceeding 100, because non-UPA parties including the Janata Dal-United, the Dravida Munnetra Kazhagam and even the Shiv Sena felt they had no choice but to support it. It sailed through the Rajya Sabha too. The stage was set by a rare, spirited speech by Congress president Sonia Gandhi, in which she described the legislation as Indiaââ¬â¢s chance to ââ¬Ëmake historyââ¬â¢ by abolishing hunger and malnutrition, and emphasised that India cannot afford not to have the law: ââ¬Å"The question is not whether we can [raise the resources] or not. We have to do it.â⬠The NFSB has invested meaning, public purpose and a degree of legitimacy into the UPAââ¬â¢s otherwise corruption-ridden, shoddy and often appalling performance in government under an increasingly right-leaning leadership. This at once put the Bharatiya Janata Party on the defensive. Its leaders were reduced to opposing a measure that represents genuine social progress, and making thoughtless statements about the Bill being about ââ¬Ëvote securityââ¬â¢, not food security. The BJP now has nothing to offer to the nation but obscurantist programmes like building a temple at Ayodhya, and parochial, and predatory pro-corporate agendas under Narendra Modiââ¬â¢s rabidly communal leadership. The Bill is open to the criticism that it doesnââ¬â¢t go far enough. Instead of universalising subsidised food provision, it confines it to two-thirds of the population, and truncates it further by limiting the food quota to five kilos of grain per capita per month instead of the 35 kg per family demanded by right-to-food campaigners. The per capita quota puts small households, such as those headed by widows and single women, at a disadvantage. A universalised Public Distribution System, covering the entire population, has been proved to be more effective and less prone to leakage than one targeted at ââ¬Ëbelow-poverty-lineââ¬â¢ groups in Kerala, Tamil Nadu and even poor, backward Chhattisgarh. The relatively well-off wonââ¬â¢t stand in queues at ration shops; they select themselves out of a universal PDS. Besides, a large proportion even of those officially defined as poor donââ¬â¢t possess BPL ration cards. The ratio can be as high as 40 percent in some highly deprived states. The latest National Sample Survey reveals that 51 percent of rural people possessing less than one-hundredth of a hectare of land have no ration cards of any kind; less than 23 percent have BPL cards. The problem of identifying the poor remains unresolved. Nevertheless, the broader coverage proposed under the NFSB and the simple, attractive formula of rice at Rs 3 per kg, wheat at Rs 2, and coarse grains at Re 1 marks a definite improvement over the current situation. It creates a right or entitlement for the poor, which can go some way in reducing acute hunger. However, right-wing commentators, including neo-liberal economists, credit-rating agencies, multinational and Indian big business, and writers/anchors in the media, have vitriolically attacked the NFSB as an instance of reckless ââ¬Å"populismâ⬠. Some claim it will do to little to relieve malnutrition among Indian children, almost one-half of whom suffer from it. Yet others contend that the poor donââ¬â¢t want or deserve subsidies; they aspire to work, earn more and eat better. And almost all of them say the NFSB will entail excessive wasteful expenditure of Rs 1.25 lakh crores. This will aggravate Indiaââ¬â¢s growing fiscal crisis and further depress already faltering GDP growth, now down to four-five percent. Eventually, this will work against the poor. Besides, if investment and growth are to be revived, India canââ¬â¢t spend so much on food security.
Wednesday, August 21, 2019
Asymmetry and Polymorphism of Hybrid Male Sterility
Asymmetry and Polymorphism of Hybrid Male Sterility Kimberly Woosley Critical Review: Asymmetry and Polymorphism of Hybrid Male Sterility During the Early Stages of Speciation in House Mice In this study, the researchers sought to determine the genetic cause of male sterility in house mice when there was interbreeding among different but related species. The researchers took two breeds of two species of house mice, musculus and domesticus, and cross-bred wild-type with classic inbred type, from the laboratory, and wild-type with wild-type. They then conducted several generations of directional and reciprocal crosses and compared body weight, testis weight, motility and sperm count. These data were analyzed to determine sterility in the male offspring of the F1 generations. The researchers crossed same species but different breed mice as a control for the expected F1 offspring fertility. They then did eight crosses of the different breeds varying the maternal and paternal parentage. After all crosses were complete they let the mice grow to maturity at approximately 60 days. The researchers weighed the mice, they then dissected them to get the weight of the testes and used histology to examine the seminiferous tubules and spermatogenesis to determine sterility. The results of their study showed a decrease in fertility of the hybrid mice except for when a domesticus female was mated with a musculus male. In those two crosses, the hybrids showed similar or increased body weight, testes weight, motility, and sperm count when musculusPWK was the paternal mate regardless of which breed of domesticus was used. In the other six crosses, the F1 offspring all had decreased testes weight, decreased sperm count, and no motile sperm. The researchers then crossed the F1 males of the intrabred domesticusLEWES x WSB with the musculusPWK female and the F1 males of the intrabred musculusPWK x CZECH with the domesticusLEWES. Comparing the two, the researchers noted when the female domesticusLEWES was mated with the male musculus with only half the genes coming from musculusPWK the F1 males still showed an increase in testes weight and sperm count over the musculusPWK female from the first cross. Their results showed that there is a combination of genetic factors at play and that the musculus X chromosome has a large effect on the fertility of the F1 generations. The results varied in some crosses indicating that other loci were involved in the interference of spermatogenesis. However, they were unable to determine exactly which genes were epistatic on male reproductive growth and fertility. They did use their finding to infer polymorphism on autosomal traits when combined with some X, Y traits in certain breed crossings. The researchers acknowledge that this study was fixed on male sterility and did not take into account female sterility or decreases in immune function that could also lead to reproductive isolation. The conclusions drawn by the researchers is valuable for further research into the genetic makeup of which genes are interacting or epistatic on the fertility of hybrid species. Scientists could take the study deeper in an effort to isolate the genes involved and determine which are responsible for speciation in the wild. Overall, this was an excellent article, the authors explained the data clearly and used previous research to back up their hypothesis. The authors broke down each aspect of X-linked, Haldanes rule, D-M incompatibility, and polymorphism as it pertained to their results showing how their study supported previous results and could lead to future explanations of speciation. Reference Good, J., Handel, M., Nachman, M. (2007). Asymmetry And Polymorphism Of Hybrid Male Sterility During The Early Stages Of Speciation In House Mice. Evolution, 62(1), 50-65. doi:10.1111/j.1558-5646.2007.00257.x
Tuesday, August 20, 2019
Waterfall Model Lifecycle Model Information Technology Essay
Waterfall Model Lifecycle Model Information Technology Essay Waterfall approach was first Process Model to be introduced and followed widely in Software Engineering to ensure success of the project. In The Waterfall approach, the whole process of software development is divided into separate process phases. The phases in Waterfall model are: Requirement Specifications phase, Software Design, Implementation and Testing Maintenance. All these phases are cascaded to each other so that second phase is started as and when define set of goals are achieved for first phase and it is signed off, so the name Waterfall Model. All the method and process undertaken in Waterfall Model are more visible. Waterfall Model lifecycle modelE:PROGECTpicture]water fall model.JPG Figure 1. : Waterfall Model lifecycle model The stages of The Waterfall Model are Problem definition In this section, you give a short, general description of the system To be analyzed. This should contain a very short description of the Organization or the company for which the analysis is to be done as Well the reasons and advantages why the computerization is needed. The environment of the analysis being done is to come out clearly in This section Requirement Analysis All possible requirements of the system to be developed are captured in this phase. Requirements are set of functionalities and constraints that the end-user (who will be using the system) expects from the system. The requirements are gathered from the end-user by consultation, these requirements are analyzed for their validity and the possibility of incorporating the requirements in the system to be development is also studied. Finally, a Requirement Specification document is created which serves the purpose of guideline for the next phase of the model. System Design Before a starting for actual coding, it is highly important to understand what we are going to create and what it should look like? The requirement specifications from first phase are studied in this phase and system design is prepared. System Design helps in specifying hardware and system requirements and also helps in defining overall system architecture. The system design specifications serve as input for the next phase of the model. Testing As specified above, the system is first divided in units which are developed and tested for their functionalities. These units are integrated into a complete system during Integration phase and tested to check if all modules/units coordinate between each other and the system as a whole behaves as per the specifications. After successfully testing the software, it is delivered to the customer Implementation On receiving system design documents, the work is divided in modules/units and actual coding is started. The system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality; this is referred to as Unit Testing. Unit testing mainly verifies if the modules/units meet their specifications. Maintenance This phase of The Waterfall Model is practically never ending phase (Very long). Generally, problems with the system developed (which are not found during the development life cycle) come up after its practical use starts, so the issues related to the system are solved after deployment of the system. Not all the problems come in picture directly but they arise time to time and needs to be solve hence this process is referred as Maintenance. Advantages of the waterfall model The advantage of waterfall development is that it allows for departmentalization and managerial control. A schedule can be set with deadlines for each stage of development and a product can proceed through the development process like a car in a carwash, and theoretically, be delivered on time. Development moves from concept, through design, implementation, testing, installation, troubleshooting, and ends up at operation and maintenance. Each phase of development proceeds in strict order, without any overlapping or iterative steps. Needless to mention, it is a linear model and of lessons, linear models are the most simple to be implemented. The amount of resources required to implement this model is very minimal. One great advantage of the waterfall model is that documentation is produced at every step of the waterfall model development. This makes the understanding of the product designing procedure simpler. After every major stage of software coding, testing is done to test the correct running of the code. Prototyping Throw-away prototyping Throwaway or Rapid Prototyping refers to the creation of a model that will eventually be discarded rather than becoming part of the finally delivered software. After preliminary requirements gathering is accomplished, a simple working model of the system is constructed to visually show the users what their requirements may look like when they are implemented into a finished system. C:Documents and SettingsNIFRASDesktop1.JPG Figure 1.1: throw away proto typing Incremental Prototyping The final product is built as separate prototypes. At the end the separate prototypes are being merged in an overall design. C:Documents and SettingsNIFRASDesktop3.JPG Figure 1.2: Incremental Prototyping Evolutionary Prototyping Evolutionary Prototyping (also known as breadboard prototyping) is quite different from Throwaway Prototyping. The main goal when using Evolutionary Prototyping is to build a very robust prototype in a structured manner and constantly refine it. The reason for this is that the Evolutionary prototype, when built, forms the heart of the new system, and the improvements and further requirements will be builtC:Documents and SettingsNIFRASDesktop2.JPG Figure 1.3: Evolutionary Prototyping Advantages of prototyping Proto types make an ideal tool for defending discussing user interaction User can understand a prototype far easier than most of the standard base of communicating requirements in the form of the model Prototypes very quickly resolve misunderstanding between biasness manager analysis Disadvantages of proto typing Leads to implementing and then repairing way of building systems. Practically, this methodology may increase the complexity of the system as scope of the system may expand beyond original plans. The Spiral Model The spiral model, also known as the spiral lifecycle model, is a systems development method (SDM) used in information technology (IT). This model of development combines the features of the prototyping model and the waterfall model. The spiral model is intended for large, expensive, and complicated projects. The steps in the spiral model can be general as follows The new system requirements are define in as much detail as possible. This generally involves interviewing a number of users representing all the outside or internal users and other aspects of the existing method. A preliminary design is created for the new system. A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product. A second prototype is evolved by a fourfold procedure: evaluating the first prototype in terms of its strengths, weaknesses, and risks; defining the requirements of the second prototype planning and designing the second prototype constructing and testing the second prototype. At the customers option, the entire plan can be aborted if the risk is deemed too great. Risk factors might involve development cost overruns, operating-cost miscalculation, or any other factor that could, in the customers judgment, result in a less-than-satisfactory final product. The existing prototype is evaluated in the same manner as was the previous prototype, and, if necessary, another prototype is developed from it according to the fourfold procedure outlined above. The preceding steps are iterated until the consumer is satisfy that the developed Prototype represents the finishing product desired. The final system is constructed, based on the refined prototype. Advantages of spiral model The spiral model is a realistic approach to the development of large-scale software products because the software evolves as the process progresses. In addition, the developer and the client better understand and react to risks at each evolutionary level. The model uses prototyping as a risk reduction mechanism and allows for the development of prototypes at any stage of the evolutionary development. It maintains a systematic stepwise approach, like the classic life cycle model, but incorporates it into an iterative framework that more reflect the real world. Disadvantages of spiral model à à 1. Highly customized limiting re-usability à à 2. Applied differently for each application à à 3. Risk of not meeting budget or schedule à à 4. Risk of not meeting budget or schedule C:Documents and SettingsAdministratorDesktopspiral model.png Figure 1.4: spiral model Rapid Application Development (RAD) Methodology what is RAD? RAD (rapid application development) is a concept that products can be developed faster and of higher quality through: Gathering requirements using workshops or focus groups Prototyping and early, reiterative user testing of designs The re-use of software components A rigidly paced schedule that defers design improvements to the next product version Less formality in reviews and other team communication Advantages of RAD Early visibility Greater flexibility Standardized look and feel Increased user involvement Buying may save money compared to building Disadvantages of RAD This method may not be useful for large, unique or highly complex projects This method cannot be a success if the team is not sufficiently motivated and nor is unable to work cohesively together. Success depends on the extremely high technical skills of the developers. C:Documents and SettingsNIFRASDesktopproto type.jpg Figure 1.4: RAD model Dynamic System Development Method Dynamic System Development Method is another approach to system development, which, as the name suggests, develops the system dynamically. This methodology is independent of tools, in that it can be used with both structured analysis and design approach or object-oriented approach. Advantages of DSD An importance on testing is so strong that at least one tester is expected to be on each project group Sets stakeholder expectations from the starts of the project that not all requirements will make it into the final deliverable Has specific approach to determining how important each requirements is to iteration Disadvantages of DSD Access to material is controlled by a consortium, and fees may be charged just to access the reference material Probably the most heavy weight project compared in this surveyC:Documents and SettingsAdministratorDesktopdynamic-system-development-method.jpg figure1.2.1: DSD method During the below given reasons I have chosen Waterfall Model for this project It is a linear sequential model It is very simple model to implement Easy to use It is the first model. It needs very few resources to implement Suitable for small projects Water fall model: This is very simple model. It moves like water fall from top to down of SDLC. The drawback of this model is ineffectiveness of verification and Validation activities. TASK 02 The water fall modelE:PROGECTpicture]water fall model.JPG The water fall stages Problem definition Requirement analysis System design Coding testing Implementation Maintenance 1. Problem definition In this section, you give a short, general description of the system to be analyzed. This should contain a very short description of the Organization or the company for which the analysis is to be done as Well the reasons and advantages why the computerization is needed. The environment of the analysis being done is to come out clearly in this section 2. Requirement Analysis All possible requirements of the system to be developed are captured in this phase. Requirements are set of functionalities and constraints that the end-user (who will be using the system) expects from the system. The requirements are gathered from the end-user by consultation, these requirements are analyzed for their validity and the possibility of incorporating the requirements in the system to be development is also studied. Finally, a Requirement Specification document is created which serves the purpose of guideline for the next phase of the model. 3. System Design Before a starting for actual coding, it is highly important to understand what we are going to create and what it should look like? The requirements specifications first phase are studied in this phase and system design is prepared. From System Design helps in specifying hardware and method requirements and also helps in defining overall system architecture. The system design specifications serve up as input for the next phase of the model. 4. Coding Testing As specified above, the system is first divided in units which are developed and tested for their functionalities. These units are integrated into a complete system during Integration phase and tested to check if all modules/units coordinate between each other and the system as a whole behaves as per the specifications. After successfully testing the software, it is delivered to the customer 5. Implementation On receiving system design documents, the work is divided in modules/units and actual coding is started. The system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality; this is referred to as Unit Testing. Unit testing mainly verifies if the modules/units meet their specifications. 6. Maintenance This phase of (The Waterfall Model) is in effect never finish phase (Very long). Commonly, difficulty with the system developed (which are not found during the development life cycle) come awake later than its practical use start, so the issues related to the system are solved after deployment of the system. Not all the problems come in images directly but they arise time to time and needs to be solve hence this process is referred as Maintenance. 7. Specification Specification is the first step in the process. In this stage, companies find a problem they want to join and think of a viable result. They then write down the solution on paper and move on to the next stage in the waterfall standardization Testing includes verification and validation 1. Verification: Are we building the product right. 2. Validation: Are we building the right product 1. Validation Am I building the right product? Determining if the method complies with the requirements. And perform functions for which it is intended and meets and is performed at the finish of the project. Am I accessing the right data (in terms of the Data? Required to satisfy the requirement) High level activity Performs after a work product is produced against Established criteria ensuring that the product integrates correctly into the environment. Determination of correctness of the final software Product by a development project with respect to the user Needs and requirements. 2. Verification Am I building the product right? The review of interim work steps and interim Deliverables during a project to ensure them are Acceptable. To determine if the system is consistent, Adheres to standards, uses reliable techniques and prudent Practices, and performs the selected functions in the correct manner. Am I accessing the data right (in the right place; in? The right way) Low level activity Performed during development on key artifacts, like Walkthroughs, reviews and inspections, mentor feedback, Training, checklists and standards. My Opinion about This Task with Victoria Hospital The Victoria Hopital has some problems. The 1st problem is the victoria Hospital at presnt does not use Computer and not asystem to save data and details Appointment details, patient detail and payment detail. 2nd problem is cant V.H take a details in time of important.That problam is some time May be loss detail in physical fils so the V.H is face these problems becaus we can analysis requirements to the V.H those are need to V.H a good system to save details datas secent is the method should preparednes easy good to hendal to the operaters. 3rd problem is the implementations should have to a good system. 4th is give a good knowledge to operates.these implementations are want to V.H those are A Server Machine 5clients, 1GB Ram, or 512MB ,Laser Printer Dot matrix printer Bar code reader and the knowledge given by system supporters to Operater. Want to Operaters condect with system supporters and the system supporters must mainten the problems of system in time ofcoming problems. TASK 03 Data flow diagram Data flow diagrams can be use to provide an understandable representation of any business function. The system starts with an overall image of the business and continues by analyzing each of the functional areas of interest. This analysis can be carried out to precisely the level of detail required. The technique exploits a system called top-down expansion to conduct the analysis in a targeted way. C:Documents and SettingsAdministratorDesktopdfdg.JPG Figure 1.2.2: data flow diagram Process Processes show a transformation or manipulation of data flows within the system. The symbol used is a rectangular box which contains 3 descriptive elements: Firstly an identification number appears in the upper left hand corner. This is allocated arbitrarily at the top level and serves as a unique reference. Secondly, a location appears to the right of the identifier and describes where in the system the process takes place. This may, for example, be a department or a piece of hardware. Finally, a descriptive title is placed in the centre of the box. This should be a simple imperative sentence with a specific verb, for example maintain customer records or find driver. Data flow A data flow shows the flow of information from its source to its destination. A data flow is represented by a line, with arrowheads showing the direction of flow. Information always flows to or from a process and may be written, verbal or electronic. Each data flow may be referenced by the processes or data stores at its head and tail, or by a description of its contents. External entity An external entity is a source or destination of a data flow which is outside the area of study. Only those entities which originate or receive data are represented on a business process diagram. The symbol used is an oval containing a meaningful and unique identifier. Data storage A data store is a holding place for information within the system: It is represented by an open ended narrow rectangle. Data stores may be long-term files such as sales ledgers, or may be short-term accumulations: for example batches of documents that are waiting to be processed. Each data store should be given a reference followed by an arbitrary number. DFD context level diagram (0 level diagram) E:my project level df (1).jpg Figure 2.2.1: DFD context level diagram DFD 1st level E:PROGECTdrawing diagram dfdDrawing2.jpg Figure 2.3.1: DFD 1st level E:my project level df (5).jpg Figure 2.3.2 E:PROGECTdrawing diagram dfdDrawing4.jpg Figure 2.3.3 E:PROGECTdrawing diagram dfdDrawing5.jpg C:Documents and SettingsALLAHDesktop level df (11).jpg Entity relationship diagram C:Documents and SettingsAdministratorDesktopdfd4.JPG Entity A person, place, object events about which we need to compare store data are called as entities E.g. students, book, department Relational ship A relationship captures how two or more entities are related to one another. Relationships can be thought of as verbs linking two or more nouns. Relationships are represented as diamonds, connected by lines to each of the entities in the relationship. Relationship instance-link between entities (corresponds to primary key-foreign key equivalencies in related tables) Relationship type-category of relationshipà ¢Ã¢â ¬Ã ¦link between entity types Attributes Attributes are the properties of entities relationship in other attributes is used to describe entities relationship in the ER diagram an entity has many attributes there for it needs to identifier. A key is attributes, group of attributes which we can use to identify an entity uniquely. Entity types E:my projectpicture]dd.jpg ERD diagram for Victoria hospital system D:tt.JPG Appointment to Patient One patient must have one appointment this is called one to one relationship and this is mandatory One appointment must have one patient this is called one to one relationship and this is mandatory Appointment to GP One GP have many appointments this is called one to many relationship and this is optional One appointment must have one GP this is called one to one relationship and this is mandatory Appointment to nurse One nurse have many appointments this is called one to many relationship and this is optional One appointment have many nurse this is called one to many relationship and this is optional Appointment to treatment One treatment have many appointments this is called one to many relationship and this is optional One appointment have many treatment this is called one to many relationship and this is optional Treatment to clinic One treatment have many clinic this is called one to many relationship and this is optional One clinic have many treatment this is called one to many relationship and this is optional E:my project1235.jpg TASK 4 Requirement specification NO Requirements BSO 1 BSO2 BSO3 BSO4 BSO5 1 Register patient Ãâà ¼ â⠬à Ãâà ¼ â⠬à Ãâà ¼ â⠬à Ãâà ¼ â⠬à Ãâà ¼ 2 Invoice the patient Ãâà ¼ â⠬à Ãâà ¼ â⠬à Ãâà ¼ â⠬à Ãâà ¼ â⠬à Ãâà ¼ 3 Inquiring handling â⠬à â⠬à Ãâà »Ã¢â ¬Ã â⠬à â⠬à Ãâà » â⠬à Ãâà » â⠬à Ãâà ¼ â⠬à Ãâà ¼ 4 Accept patient ordering Ãâà ¼ â⠬à Ãâà ¼ â⠬à Ãâà ¼ â⠬à Ãâà ¼ â⠬à Ãâà ¼ 5 printing debater report Ãâà ¼ â⠬à Ãâà ¼ â⠬à Ãâà ¼ â⠬à Ãâà ¼ â⠬à Ãâà ¼ 6 Medical laboratories Ãâà » â⠬à Ãâà » â⠬à Ãâà ¼ â⠬à Ãâà ¼ â⠬à Ãâà ¼ 7 Arrange the delivery Ãâà ¼ â⠬à Ãâà » â⠬à Ãâà » â⠬à Ãâà » â⠬à Ãâà » 8 Printing a patient report Ãâà » â⠬à Ãâà ¼ â⠬à Ãâà ¼ â⠬à Ãâà » â⠬à Ãâà ¼ Business system option (BSO) The set of Business System Options which is compiled so that a selection can be made. The selected Business System Option is a description of a chosen system development direction. The description documents the system boundary, inputs, outputs and the transformation taking place within the boundary. Essentially, the description is textual with supporting products such as Data Flow Diagrams, a Logical Data Structure and a Work Practice Model Technical system option (TSO) The set of Technical System Options which has been developed so that the system development direction can be chosen. Each option documents the functions to be incorporated and details implementation requirements. Each description is textual with some planning information. Functional elements are taken directly from the Requirements Specification Logical System Specification NO requirement TSO1 TSO2 TSO3 TSO4 TSO5 1 Visual basic 2007 Ãâà ¼ Ãâà ¼ Ãâà ¼ Ãâà » Ãâà » 2 Windows 2003 Ãâà ¼ Ãâà » Ãâà ¼ Ãâà ¼ Ãâà ¼ 3 Java J2SE Development Kit (JDK) 5.0 Ãâà » Ãâà » Ãâà ¼ Ãâà » Ãâà ¼ 4 CCT camera Ãâà » Ãâà ¼ Ãâà » Ãâà » Ãâà ¼ 5 A Server Machine Ãâà ¼ Ãâà ¼ Ãâà » Ãâà » Ãâà ¼ 6 Firefox 9.02 latest version Ãâà » Ãâà » Ãâà ¼ Ãâà ¼ Ãâà ¼ 7 5 clients,1GB Ram,80GB Ãâà ¼ Ãâà » Ãâà » Ãâà ¼ Ãâà ¼ 8 SQL Server Ãâà ¼ Ãâà » Ãâà » Ãâà » Ãâà ¼ 9 Windows 2007 Ãâà » Ãâà » Ãâà ¼ 10 Laser Printer Ãâà ¼ Ãâà ¼ Ãâà ¼ Ãâà ¼ Ãâà ¼ 11 Scanner Ãâà ¼ Ãâà » Ãâà ¼ Ãâà » Ãâà ¼ 12 Credit Card reader Ãâà ¼ Ãâà ¼ Ãâà ¼ Ãâà ¼ Ãâà ¼ 13 JDBC 3.0 compliant driver Ãâà » Ãâà ¼ Ãâà ¼ Ãâà » Ãâà ¼ 14 IIS Server Ãâà » Ãâà » Ãâà ¼ Ãâà » Ãâà ¼ 15 Dot matrix printer Ãâà ¼ Ãâà ¼ Ãâà » Ãâà » Ãâà ¼ 16 Wi5 connection Ãâà » Ãâà » Ãâà ¼ Ãâà » Ãâà ¼ 17 Win 2003 server Ãâà ¼ Ãâà ¼ Ãâà ¼ Ãâà ¼ Ãâà ¼ 18 Barcode reader Ãâà » Ãâà ¼ Ãâà » Ãâà » Ãâà » 19 Credit card Ãâà ¼ Ãâà » Ãâà ¼ Ãâà » Ãâà ¼ . TASK 5 Fact-finding technique Interviews Questionnaires Observations Sampling Record-searching Fact-finding technique Fact-finding is a main activity in system investigation. In this chapter, the functioning of the method is to be understood by the system analyst to design the proposed system. Different methods are used for this and these are known as fact-finding techniques. The analyst needs to fully understand the current system. The analyst wants data about the requirements and demands of the project undertaken and the technique employed to gather this records are identified as fact-finding techniques. Various kinds of techniques are used and the most popular with them are interviews, questionnaires, record reviews, case tools and also the personal observations made by the analyst himself. Each of these techniques is additional dealt in next pages. Two people can go into the same area to gather facts and experience entirely different results. One spends weeks and gets incomplete and misleading data. The other is finished in a few hours and has complete and solid facts. This session outlines some of the things a person can do to achieve the latter. It covers: Interviews Interviewing is the one of the most common method in fact finding. It bring the analysis Into a direct contact with the users where he gets an opportunity to listen in to the opinion (advantage disadvantages) about the existing system also to identify the issues propose solutions the new system Interview is a very effective fact finding techniques. But the main problem is that it requires a lot of resources, especially time. So it is very important to plan the interview before hand the analysis is required to have considerable amount of skills Interview needs a start from the top level management to get permission also get an overview idea about the total system. Then the interview process can be move to which will provide more more specific details Interviews are not required to find out how exactly a system should work, but it needs to deter mine the needs of the users that we have to satisfy with a new system. The success of the interview depends upon the skills of the interviewer the preparation for the interview. Choose the person who is mostly appropriate for the interview Preparation for the interview Setting a proper date, and time ,venue the topic Correct sequence of questions These factors should include in an interview plan before conducing it. There are 3 types of questions usually asked in an interview Open questions Closed questions Probes questions Open question general questions that relates with the personal view on the subject Example-à à what do you think of .? à à à à à à à à à à à à à à à à à à à What is your opinion of ? à à à à à à à à à à à à à à à à à à à How could . be improved. Advantages à Puts the interviewee at ease. à Permits extra questioning into area that was not anticipated during interview scheduling. à Provide detail. Disadvantages à interview may get off the track (i.e. the interviewer lose control of the interview) can be time-consuming, particularly if the interviewer is experience Closed question > question that is needed direct answer
Subscribe to:
Posts (Atom)