Study Nile River Essay Example | Topics and Well Written Essays - 3000 words

Study Nile River - Essay Example The basin is home to the estimated population of over 160 million people with overwhelming majority depending on it directly or indirectly for land, water, shelter, and energy sources (Rahman, 2013). The use of the water resources has over the years become a source of conflict for the ten countries that depend on it directly or indirectly. The population of the river is expected to double in the next twenty years thus pressuring the already strained water resources thus tampering with its ability to meet the world’s social, environmental, and economic challenges in the region (Rahman, 2011). The Nile river basin represents an area with a traditional history that is strongly linked to the river due to its importance in an environment that experiences water scarcity. The region lacks tangible water alternatives hence they purely rely on the river and its resources to provide them with the essentials of their daily lives. The water governance highly favours Egypt at the expense o f riparian states thus breeding a lot of instability concerning water use in this region. The African communities are the most affected by the water resource problems due to persistent drought, increasing food security and political instability. Water is truly a strategic and vital resource and should thus be properly and sensitively managed to avoid pollution and prevent any possible conflict. The Nile water resource is subject to lots of pressures ranging from demographic, economic, growth of agglomerations, and ecological factors that threaten the smooth existence in the region. There are several organizations working round the clock to study and closely monitor the activities that are taking place in the Nile basin. There are several uses of water in this basin spreading in all the riparian states hence all of them want a voice in controlling the water usage. The continuous use of this water resource is exposing this basin to environmental degradation that threatens their ecosys tems in the near future. In an attempt to control this rare resource, trans boundary issues are developing that threatens the political and economic stability in the region, hence resulting in signing of several pacts between the riparian states. Relevant uses and users of water throughout the Nile basin The Nile basin contains a wide range of unique and highly productive ecosystems that provide food resources, medicine, fuel, and construction materials despite providing water for irrigation, industry, hydropower, and household use (Allan, 2009). These ecosystems provide a number of important hydrological functions that include flood mitigation, flow regulation, and water quality in the whole region despite being aesthetic, cultural and heritage significance. The ecosystems provide an intrinsic value to over 160 million people who depend on the Nile basin to provide for a range of livelihoods that include agriculture, fisheries, and urban dwelling (Rahman, 2011). The ecosystems also provide direct services that include water shelter, medicine, fuel, fish, plants and animal feeds that they use throughout the year for their daily survival. According to Allan (2009), the river is of great importance since it provides up to 80% of the calorie intake provided by goods and services directly related to Nile ecosystems. According to Cascao (2009), most of the riparian stat

What are your perceptions on the universal declaration Essay Example for Free

What are your perceptions on the universal declaration Essay One Amazing Thing by: Chitra Divakaruni. It was first published in the US in voice by Hyperion in 2009 and later published by Penguin books India February 2010. The book also has 240 pages. Chitra B. Divakaiumi is an award winning author poet. Her work is widely known, as she has been published in over 500 magazines. Including Atlantic Monthly and The New Yorker, and her writing has been included in over 50 anthologies. She was born in India and lived there until 1976. At which point she left Calcutta and came to the United States. A young woman Uma, sits in the waiting room of the India passport office. She starts to get very impatient, and she entertains herself by observing the other people in the waiting room with her. Everyone has a reason of why they want to enter into India. In the waiting area their waits an Africa American war veteran Cameron who takes charge, but some are unhappy about it. A Muslim names Tariq. An upper class Caucasian couple that really don’t get alone. A Chinese grandmother with a secret past, and her granddaughter, two visa office workers on the verge of and affair Malathi and Mr. Mangalam, and Uma. As they all set in the waiting area Uma starts to feel a little rumbling and that when the earthquake strikes. When everything settles down, there were some major injuries as well as some minor injuries. People started to go into survival mode, as there is little food to eat. The office starts to flood. So emotional stress seems to much for everyone to handle as they wait to be rescued or die. So that’s when Uma comes up with everyone telling â€Å"One Amazing Thing† , about themselves because she believes that no one can go through life without encountering at least one amazing thing. So everyone begin to tell one amazing thing that they have never told anyone before. With One Amazing Thing everyone discover so much from each other as well as their selves. Elderly Caucasian couple Mr. and Mrs. Pritchet going through a difficult time in their marriage, an Indian-Muslim man Tariq who is disillusioned and angry with the new US, as Chinese lady Jiang who loved and lost a man in her younger days, her granddaughter Lily, a middle age army officer haunted by his guilt Cameron, Malathi a visa officer who is engaging in a affair with her boss, Mr. Mangalam on the verge of an extra-martial affair, an Indian-American student Uma, who is confused by her parents decision to return to Kolkata after living in the US for over 20 years. The plot focuses on a group of strangers who are trapped in a visa office. Most customers even some staff have come and gone, but nine people remain in the office. When an earthquake rips through the afternoon, trapping these nine characters together, their focus first is to survive through the struggle. There is a little food from which came from what people had. The office begins to flood, and everyone starts to panic and get really scared and frustrated. So when the emotional stress seems to be to much for them to bear, the young lady Uma tells them to tell a personal tale about them that no one knows about â€Å"One Amazing Thing†, from what they have been through in life. So all of their stories from the romance, self-discovery, family, etc. This novel really proves the power of a lot of stories and the meaning of us as human’s expressions itself. In my opinion the book â€Å"One Amazing Thing†, is an engaging book because it reinforces the idea that all of us are different and unique in our own ways, and that we all have stories of our lives that may be interesting or not to tell. We all can connect to this book or see one another if we are willing to take the time out to listen to people. Because everyone has a something to tell, and amazing is not always positive words. But describes something that might have changed a life, or the course of someone life. Some of the stories are very heart breaking, but all of them paint a picture in some way of the characters and why they may be who they have become.

Regulatory Framework for UK Banks

Regulatory Framework for UK Banks Introduction Berger, Molyneux and Wilson (2010) are of the view that banks provide a full range of financial services like banking, securities, and insurance under a single corporate structure and must be supported by the single capital base, the term â€Å"universal bank† has multiple meanings, but commonly it refers to the commercial banking that is making loans and collecting deposits along with investment banking in which there are issuing of underwriting and trading in securities. Ryan-Collins and Goodhart (2012) point out the broader view that universal banks offer a wide range of financial services including commercial banking, investment banking with other activities like insurance, it seems like the multipurpose financial market which provided both banking and financial services. Financial Times (2015) terms refers universal banking as financial services of retail, wholesale and investment banking services under one roof. Demirguc-Kunt (2010) refers that universal banking is a com bination of large banks operate extensive networks of branches, providing multiple services, holding claims that firms about participation in corporate management of firms. Forsyth and Verdier (2003) are of the view that universal banking began almost in 1930 to 1940 and Europe is the home of Universal Banking, although other countries also adopted it. Structure of United Kingdom Banking System Schumpeter (1939) refers the connection between banking and financial system in economic growth and it is most old history of this specified reference of this field. Beck and Rahman (2006) speculate that in the recent economic literature, banking system measures a reasonable ratio and access like banking, loan ratios in gross domestic products, and it is a direction to analyse other financial markets. Banking systems have many other multiple dimensions that bank assets may be kept in one house, the bank required few branches or a large number of branches, but it was very true in the early stages of banking when banks were in their development phase. Heffernan (1996) describes the financial system refers some points very clearly that the system can provide payments, can give support between savers and borrows and play major role in insurance against risk. The British banking industry has many changes from the last 20 years, besides forces which have the power to change the supply and demand functions, change has also been made due to domestic deregulations. Hsbcnet.com (2015) reports that The Bank of England has always shown keen interest in the structure of the financial system because financial stability may have an effect on cost and availability. Many new products emerged over the past 50 years and the United Kingdom banks have full range of financial services and become larger. United Kingdom banking system made a dramatic shift in size from past 40 years and the total assists rise from 100% to 450% of the nominal Gross Domestic Product, banking giants claiming that the UK banking system keeps this pace in future also. Salina and Peltonen (2013) describe that financial stability depends the potential impact size of UK banking, so ultimately there must be some factors behind this huge banking size, description about those factors is important and these are financial hub benefits, comparative advantages and historical factors. Bush, Knott and Peacock (2015) d escribe the size of the UK banking system as shown in figure 1.1 and figure 1.2 refers below. Size of GDP of UK Banking System (2013) Regulatory Challenges of Universal Banking Models Alworth and Bhattacharaya (1998) are in the view that in the recent decades, the banking sector has undergone due to the forces of globalization and lack of technology, secondly it is also recognized de-regulation is due to that higher degree of freedom to financial institutions as a so it requires strong supervisory authorities. Changes in the nature of banking risks, off-balance sheet business and complexity in the nature of transactions all these need strong internal risk management and strengthening of existing capital requirements in 1980 and early 1990 numbers of bank failures were due to the way banks were regulated. Quinn (2012) is in the view of that change is needed in the banking sector, there is some need to show the market trends of entry and switching are enough for competition where customer focus is on the front line. Different advance economies adopted structural bank regulation measures to face the regulatory challenges and one element is mandatory upon them that se paration of commercial banking from certain securities market activities. Treanor (2011) reported in the â€Å"Guardian†, that the United Kingdom is going to act upon Vickers Commission suggestions as a major measure the report, in which Sir John Vicker recommends to Britian biggest banks to implement reforms until 2019, this is going to be initiating after the collapse of Lehman Brothers in 2008. Conway (2011) is in the view that Vicker’s recommendation is going through to ring-fencing in the United Kingdom banking sector. The Economist (2012) reveils the report that universal banks merging investment banking complexities with commercial banking services, in one extent it is good offering services to the customer while on the other hand analyst have no second thoughts also, the famous universal banking giant Sandy Weill, the mergers of Citigroup saying that the megabanks should be broken up. Shrivastava, Pandey and Vidyarthi (2007) describe the view that banks facing information imbalance which will cause the lack of public confidence in the banking system, so there is the need to protect it from this high risk taking by banks. Because banks are critical for mobilizing the public savings, its safety and return to savers also, so banks need for their heavy regulation in this sense also. Mostly challenges have faced by bank regulators in the early 80s, due to deregulation of economic system, financial innovation waves and internationalization of financial flows all these challenges arise the potential of doubts about the bank’s risk management procedures. Orbell and Turton (2001) speculate that banks take deposits from public to investing these deposits in risky assets and businesses, ultimately banks are in a position to take risks excessively, secondly market discipline, where these deposited are invested, is a mechanism which curb the incentive in taking excessive risk more costly for banks. So after recent events of severe market and re gulatory failure in Europe and United States a point arisen that there should be need for reforms. While on the other hand single regulator model of United Kingdom widely accepted across the globe. Regulatory Challenges, and British Economy Kim and McKenzie (2010) argue that financial crises faced globally in 2008 laid many questions for strong measures to prevent any resemblance in future, bankers, regulators, politicians or economists nobody want accept the blames of crises. Particularly in British banking which has a rich history, which spread out on centuries, founding of the Bank of England in 1694. Bank of England has always had a dominant position in the British economy while other banks were underdeveloped. So due to small in size other country banks were inherently fragile, which made to face them financial crises in early nineteenth centuries, one major example is crises of 1825, and then the first time the Bank of England understood the role of lender of last resort. Gregory (1929) quoted ‘The Economist’ that â€Å"the limited liability of the wealthy may not be expected to prove as good if not better security than the unlimited liability of the poor†. Mullineus and Murinde (2003) urges th at the in 1986, main clearing banks ranked them fully integrated banking, invested more than one billion in the securities business. British banks highly enhanced their standing globally, commercial banking was higher profit gaining business in the United Kingdom and have much concern about the level of competition. Conway (2011) describes that the time of financial crises all had become universal banks, amalgamation of commercial and investment banking activities, on the other hand Barclays, HSBC and Standard Charted faced crises without government support. Treanor (2011) describes that British’s fifth largest mortgage lender Northern Rock, is going to run on, and this disaster situation was not seen in United Kingdom from over 100 years, most dramatic symptom of Northern Rock crises indicated the low grip on financial markets in the United Kingdom. Northern Rock has good use of structured products in funding before to the crises, but still impacted by the turmoil in America ’s mortgage market. The bank has a low deposit ration to loan failed to renew its short term financing and was forced to beg to the Bank of England for assistance. As soon as news broke, the customer quickly withdrew their savings, such panic situation which was not experienced in the United Kingdom since 1866. Salina and Peltonen (2013) describe that at the time of crises United Kingdom government need to inject billions into the industry, also the Bank of England funded many banks for keeping them in running and this bail out costs raised real concerns. Some lesson has been learned from Northern Rock incidents that the regulation of banks on liquidity along capital should be centralized, because Northern Rock faced reduction in the liquidity for securities mortgages rather than the inadequacy of capital. Financial crises and reactions of Regulatory Authorities The Economist (2012) explained that after 2007 to 2010 financial crises banking and finance market faced severe consequences specially on supervision and regulation aspects, the question was not only to build the public confidence again, which is also a very difficult in its but also the future evolution of the financial industry and banks at larger scale. Regulator and supervisors worked hard after crises and there was a lot of analysis has been conducted towards the causes and their solutions. Some of the measures have been taken by regulatory authorities which describes here one by one (i) Adjusting budgetary problems; failure of banks in many countries faced the common budgetary problems, there are many ways that can affect the real economy and budgets. (ii) Rebuilding the structure of responsibilities; in 1999, the G20 was established and made lots of contributions to shaping up international finance regulation. Biannual meeting was held in the early years, but greater frequency of meeting done in 2009 and 2010 due to the issuance of declarations and progress report. Multinational agency standards have been formalized and Finance Stability Board in 2009 formed with core responsibilities of coordination between national financial authorities and international standard setter. Bank of England (2014) in its news release reveals that The Prudential Regulation Authority (PRA) introduces a new (iii) accountability regime about insurance sector, PRA also consulted same regime for banking sector in July 2014. This regime will also take care and account of the need of new measures which relate to governance of individuals as a part of solvency. (iv) new international standards are coming into being both for regulatory activities for financial firms along with quantitative and qualitative approaches. Besides that there are many agreements done for betterment of the regulatory process, but it has also been clear that individual nations not waited for agreements on in ternational standards to regulate financial sectors. Financial Stability Board, (2010) issue a list of scope and scale of activities about reforms which is a) reforming compensations b) refurbish accounting standards c) strengthening supervisory and regulatory standards d) refining the regulatory perimeters. Brunnermeier et al. (2009) argue that (v) reforms in corporate governance were certainly needed to avoid futuristic failure of financial institutions and this was the main lesson to come out of the crises. (vi) Revision in remuneration structure also required as the mentioned structures of remuneration was very poor in financial institutions. The Financial Stability Board also produced some principles for solid compensation practices. (vii) Reforms in risk management practices also observed, as the failure of risk management systems is the most critical, unfortunately, it is shown in a lot of institutions like international banks specially. Johnson and Kwak (2010) speculate that the (viii) accounting reforms, accounting are a basic component of regulatory regime for example calculation of capital is cor dependent on reported, assessed values, one of the core areas of reforms is required in valuation and provisioning of accounting. One of the other lessons drawn from crises that is regarding (ix) risk identification and mitigation, actually authorities, in some views, are not good to identify or projecting the risk so capabilities to resolve these kind of issues need to be improved and financial policies need to follow proportionate principle. The bank should (x) act like a social contract, in the new regulatory paradigm, it is a major challenge that how bank again focuses on retail business, most banks are in the risk business about the turning liquid to liquid loans, while doing this job banks are badly failing in fulfilling their social contarct part and they need to build it up again. There should be (xi) new business models required as in the phase of crises no business model looked fixer of crises, the diversified banking model required in the scenario and that will help to secure the banking business as well as revenues and customers also. Salina and Peltonen (2013) posit the view that (xii) false sense of security is the core reason of financial disaster, describing further that capital provisions are important but only capital is not only sufficient to address the issue. It was also observed that (xiii) there is a need to redefine systemic risk, in current crises which reflects the unpredictable size of the losses and who will bear that losses. Loss distribution will come as battle in financial crises, bailing out also not a good practice and seems to be taking from one to give others. Regulatory Framework – Suggestions Some overhauling required in regulatory framework facing worst financial disaster in Europe and the rest of the world also, reforms are required on regulatory framework internationally in general, and the United Kingdom in particular. Including reinforcing macro-prudential oversight, giving the strength in the overall resilience of banks and shadow banking (or unregulated sectors needs to be in regulation). (i) Optimistic about pricing the assets and risks, much precaution required to observe in risk taking secondly, there is need to be more awareness about regulated and non-regulated structures on information sharing. (ii) Cross border banking resolution required in national and international approaches. (iii) Far-reaching changes required for shaping and functioning of financial institutions with the high pitch of transparency in regard to the financial instruments (iv) In future crises may differ in nature like size, type and its cross border exposure so consolidation and coordina tion among banks should required on local and international level, one other thing should remain in mind that for the survival, some business models may disappear but some may strengthen their risk management. (v) Measures which could be taken in the middle of crises need to be more supportive rather to hide them, it must be planned whether mega project should remain in the market or there is no need of them, there should be some policies without exacerbating the present crises for the long term view of financial systems. (vi) Financial sector scrutiny perimeter need to be expanded to a wider range of better prevention of banking sector and other financial institution. (vii) Management needs to encourage incentives and discourage regulatory arbitrage. (viii) Need to adopt the concept of systematic risk factoring among funding and effects of leverage. (ix) Buffering between good times and bad time, which can help for liquidity norms of capital provisioning (x) Progress required to ta ckle the regulation and resolution of cross border institutions for legal hitches. (xi) Flexibility for central banks in providing liquidity, focus also required in the attention on credit and asset booms. Many central banks, especially in emerging markets facing capital outflows so the provision for extra liquidity may more complex regarding foreign exchange reserves and may work fuel to drain for this. (xii) Better crises responses and fiscal support required from national authorities regarding to increase the concern about credit risk and realization of losses there also needs a clear exit policy for withdrawing market or transit to new markets. (xiii) Market discipline must not ineffective for constraining risk taking other than the banking sector. Consolidation rules required more strict specially for entities and risks, particularly with off balance sheet activities.

Can Officers Effectively Prosecute Domestic Violence Cases Without Vict

When prosecuting criminal domestic violence cases too many officers constructed their entire case only on statements made by the victim. However, â€Å"victims of domestic violence are more likely than victims of other violent crime to recant or refuse to cooperate in prosecutorial efforts† (Breitenbach, 2008, p. 1256). Officers must consider that victims of domestic violence may refuse to testify because of fear of retaliation, intimidation, financial dependence, emotional attachment, and/or because they reunited with the batterer. If the victim refused to testify during court, their statement against the abuser becomes hearsay evidence. Several recent cases have had a huge influence on how those statements and hearsay evidence may be utilized in court without the victim’s testimony. In 2004, the Supreme Court ruled on the case of Crawford v Washington and found that testimonial assertions were not exceptions to the hearsay rule (Breitenbach, 2008). Since the purpose of a testimonial statement was to prove and/or establish facts in a case, the defendant had a right to cross examination of that testimony. This right was termed the Confrontation Clause. Due to the confusion created by the Crawford standard, the Supreme Court provided more parameters in Davis v Washington in June 2006 (Ewing, 2007). Davis established victim accounts as either testimonial or non-testimonial. The courts also believed this included statements taken during the course of an interrogation conducted by law enforcement. If the declarations were acquired by law enforcement to determine an ongoing emergency then they were identified by the court as non-testimonial and not subject to the requirements of the Confrontation Clause. If the statements we... ...ion of the victim. Works Cited Breitenbach, K. G. (2008, Fall). Battling the threat: the successful prosecution of domestic violence after Davis v. Washington. Albany Law Review, 71(4), 1255+. Retrieved from http://go.galegroup.com/ps/i.do?id=GALE%7CA200252467&v=2.1&u=chazsu_main&it=r&p=AONE&sw=w Byrom, C. E. (2005). The Use of the Excited Utterance Hearsay Exception in the Prosecution of Domestic Violence Cases After Crawford v. Washington. Review Of Litigation, 24(2), 409-428. Ellison, L. L. (2002). Prosecuting Domestic Violence without Victim Participation. Modern Law Review, 65(6), 834-858. Ewing, D. (2007). Prosecuting Batterers in the Wake of Davis and Hammon. American Journal Of Criminal Law, 35(1), 91-106. Pence, E. & Paymar, M. (2001). Domestic violence: The law enforcement response. Minneapolis, MN: Law Enforcement Resource Center.

Quality Assurance Question Bank

Question bank Q1. Why software needs to be tested? Ans. Every software product needs to be tested since; the development process is unable to produce defect free software. Even if the development process is able to produce defect free software, we will not be able to know unless & until we test it. Without testing it, we shall not be having enough confidence that it will work. Testing not only identifies and reports defect but also measures the quality of the product, which helps to decide whether to release the product, or not. Q2.What is the reason that Software has Bugs? Ans. Following factors contribute to the presence of bugs in the software applications:- a. Software development tools like visual tools, class libraries, compilers, scripting tools, etc. usually introduce their own bugs in the system. b. To err is human. Likewise programmers do make mistakes while programming c. In fast-changing business environments continuously modified requirements are becoming a fact of life. Such frequent changes requested by the customer leads to errors in the application already nearing completion.Last minute design changes leads to many chaos like redesign of the whole system, rescheduling of engineers, scrapping of the work already completed, fresh requirements of compatible hardware etc d. A quickly written but poorly documented code is bound to have bugs. It becomes difficult to maintain and modify such code that is badly written or poorly documented. – its tough to maintain and modify code that is badly written or poorly documented; the result is bugs. In many organizations management provides no incentive for programmers to document their code or write clear, understandable, maintainable code.In fact, it’s usually the opposite: they get points mostly for quickly turning out code, and there as jobs security if nobody else can understand it (if it was hard to write, it should be hard to read). e. When project deadlines come too close & time pressure s come, mistakes are bound to come Q3. What is the difference between QA and Testing? Ans. QA stands for â€Å"Quality Assurance†, and focuses on â€Å"Prevention† of defects in the product being developed. It is associated with the â€Å"Process† and activities related to the Process Improvement.Quality Assurance measures the quality of the processes employed to create a quality product. Whereas â€Å"Testing† refers to â€Å"Quality Control†, and focuses on Detection of Defect and removal thereafter. Or Quality Control measures the quality of a product. Q4. What is the difference between Software Testing and Debugging? Ans. Testing is the process of locating or identifying the errors or bugs in a software system. Whereas Debugging is the process of Fixing the identified Bugs. It involves a process of analyzing and rectifying the syntax errors, logic errors and all other types of errors identified during the process of testing.Q5. What is the diff erence between a Bug and a Defect? Ans. â€Å"Bug† is a problem or an error in the software code, which is found in the application during Testing. Bug is responsible for failure of the application to comply with the desired specifications. Whereas â€Å"Defect† is problem reported by the customer during usage of the software application. Q6. What is the difference between a Bug and an Enhancement? Ans. â€Å"Bug† is a problem or an error in the software code, which is found in the application during Testing.Bug is responsible for failure of the application to comply with the desired specifications. Whereas â€Å"Enhancement† is the additional feature or functionality found and added to the application as desired by the end user / real word customer or tester during the testing process. Q7. What is the difference between Requirements & Specifications? Ans. â€Å"Requirements† are statements given by the customer as to what needs to be achieved by t he software system. Later on these requirements are converted into specifications which are nothing but feasible or implementable requirements.Whereas â€Å"Specifications† are feasible requirements derived from various statements given by the customer. These are the starting point for the product development team. Q8. What is the difference between Verification and Validation? Ans. â€Å"Verification† involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications to confirm whether items, processes, services, or documents conform to specified requirements or not. This can be done with the help of checklists, issues lists, walkthroughs, and inspection meetings. The purpose f verification is to determine whether the products of a given phase of the software development cycle fulfill the requirements established during the previous phase or not. Whereas â€Å"Validation† is the determination of the correctness of the final progr am or software product produced from a development project with respect to the user needs and requirements. This involves actual testing of the product and takes place after verifications are completed. â€Å"Software Verification† raises the question, â€Å"Are we building the Product Right? † that is, does the software conform to its specification. Software Validation† raises the question, â€Å"Are we building the Right Product? † that is, the software doing what the user really requires. Q9. What is difference between Waterfall Model and V Model? Ans. â€Å"Waterfall Model† Is a sequential software development model (a process for the creation of software) in which development is seen as flowing steadily downwards (like a waterfall)through the phases of requirements analysis, design, implementation, testing (validation),integration, and maintenance. To follow the waterfall model, we proceed from one phase to the next in a purely sequential manne r.In traditional waterfall model, testing comes at the far end of the development process. Whereas â€Å"V Model† or â€Å"Life Cycle Testing† involves carrying out verification of consistency, completeness and correctness of software at every stage of the development life cycle. It aims at catching the defects as early as possible and thus reduces the cost of fixing them. It involves continuously testing the system during all stages of the development process rather than just limiting testing to the last stage. Q10. What are Baseline Documents? Ans.Baseline documents are the documents, which have been approved by the customer and will not have any more changes. Baseline Documents cover all the details of the project and have undergone â€Å"walkthrough† process. Once a document is Base-lined it cannot be changed unless there is a change request duly approved by the customer. Service Level Agreement (SLA) & Business Requirement Documents (BRD) are the examples o f Baseline Documents. Q11. What is Defect Density? Ans. â€Å"Defect Density† Is a software metric defined as: Total number of defects per LOC (lines of code).Alternatively it can be: Total number of defects per Size of the Project. Here the measure of â€Å"Size of the Project† can be number of Function Points, Number of Feature Points, number of Use Cases or KLOC (Kilo Lines of Code) etc. Q12. What is Quality? Ans. Quality software is software that is reasonably bug-free, delivered on time and within budget, meets requirements and expectations and is maintainable. However, quality is a subjective term. Quality depends on who the customer is and their overall influence in the scheme of things.Customers of a software development project include end-users, customer acceptance test engineers, testers, customer contract officers, customer management, the development organization’s management, test engineers, testers, salespeople, software engineers, stockholders an d accountants. Each type of customer will have his or her own slant on quality. The accounting department might define quality in terms of profits, while an end- user might define quality as user friendly and bug free. Q13. What is an Inspection? Ans.An inspection is a formal meeting, more formalized than a walkthrough and typically consists of 3-10 people including a moderator, reader (the author of whatever is being reviewed) and a recorder (to make notes in the document). The subject of the inspection is typically a document, such as a requirements document or a test plan. The purpose of an inspection is to find problems and see what is missing, not to fix anything. The result of the meeting is documented in a written report. Attendees should prepare for this type of meeting by reading through the document, before the meeting starts; most problems are found during this preparation.Preparation for inspections is difficult, but is one of the most cost-effective methods of ensuring quality, since bug prevention is more cost effective than bug detection. A14. What is Six Sigma? Ans. â€Å"Six Sigma† means Six Standard Deviations from the mean. It is a methodology aimed to reduce defect levels below 3. 4 Defects Per one Million Opportunities. Six Sigma approach improves the process performance, decreases variation and maintains consistent quality of the process output. This leads to defect reduction and improvement in profits, product quality and customer satisfaction.Q15. What is difference between CMM and CMMI? Ans. â€Å"CMM† means â€Å"Capability Maturity Model† developed by the Software Engineering Institute (SEI). It is a process capability maturity model, which aids in the definition and understanding of an organization’s processes. CMM is intended as a tool for objectively assessing the ability of government contractors’ processes to perform a contracted software project. Whereas â€Å"CMMI† means â€Å"Capabil ity Maturity Model Integration† & it has superseded CMM. The old CMM has been renamed to Software Engineering CMM (SE-CMM).Q16. What is Verification? Ans. Verification ensures the product is designed to deliver all functionality to the customer; it typically involves reviews and meetings to evaluate documents, plans, code, requirements and specifications; this can be done with checklists, issues lists, walkthroughs and inspection meetings. Q17. What is Validation? Ans. Validation ensures that functionality, as defined in requirements, is the intended behavior of the product; validation typically involves actual testing and takes place after verifications are completed. Q18.What is a Test Plan? Ans. A software project test plan is a document that describes the objectives, scope, approach and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product. The complet ed document will help people outside the test group understand the why and how of product validation. It should be thorough enough to be useful, but not so thorough that none outside the test group will be able to read it. Q19. What is a Walkthrough? Ans.A walkthrough is an informal meeting for evaluation or informational purposes. A walkthrough is also a process at an abstract level. It’s the process of inspecting software code by following paths through the code (as determined by input conditions and choices made along the way). The purpose of code walkthroughs is to ensure the code fits the purpose. Walkthroughs also offer opportunities to assess an individual’s or team’s competency. Q20. What is Software Life Cycle? Ans. Software life cycle begins when a software product is first conceived and ends when it is no longer in use.It includes phases like initial concept, requirements analysis, functional design, internal design, documentation planning, test plann ing, coding, document preparation, integration, testing, maintenance, updates, re-testing and phase-ou Q21. What is the Difference between STLC & SDLC? Ans. STLC means † Software Testing Life Cycle†. It starts with activities like : 1) Preparation of Requirements Document 2) Preparation of Test Plan 3) Preparation of Test Cases 4) Execution of Test Cases 5) Analysis of Bugs 6) Reporting of Bugs 7) Tracking of Bugs till closure.Whereas SDLC means † Software Development Life Cycle† is a software development process, used by a systems analyst to develop an information system. It starts with activities like : 1) Project Initiation 2) Requirement Gathering and Documenting 3) Designing 4) Coding and Unit Testing 5) Integration Testing 6) System Testing 7) Installation and Acceptance Testing 8) Support or Maintenance Q22. What is the Difference between Project and Product Testing? Ans. If any organization is developing the application according to the client specifi cation then it is called as project.Accordingly its testing is known as â€Å"Project Testing† Whereas If any organization is developing the application and marketing it is called as product. Hence its testing is known as â€Å"Product Testing† Q23. How do you introduce a new software QA process? Ans. It depends on the size of the organization and the risks involved. For large organizations with high-risk projects, a serious management buy-in is required and a formalized QA process is necessary. For medium size organizations with lower risk projects, management and organizational buy-in and a slower, step-by-step process is required.Generally speaking, QA processes should be balanced with productivity, in order to keep any bureaucracy from getting out of hand. For smaller groups or projects, an ad-hoc process is more appropriate. A lot depends on team leads and managers, feedback to developers and good communication is essential among customers, managers, developers, t est engineers and testers. Regardless the size of the company, the greatest value for effort is in managing requirement processes, where the goal is requirements that are clear, complete and testable. Q24. What is configuration Management? Ans.Configuration Management (or CM) is the processes of controlling, coordinating and tracking the Standards and procedures for managing changes in an evolving software product. Configuration Testing is the process of checking the operation of the software being tested on various types of hardware. Q25. What is the role of QA in a software producing company? Ans. QA is responsible for managing, implementing, maintaining and continuously improving the Processes in the Company and enable internal projects towards process maturity and facilitate process improvements and innovations in the organization.Tester is responsible for carrying out the testing efforts in the company. In many companies QA person is responsible both the roles of Testing as wel l as creating and improving the processes. Q26. What is Failure Mode and Effect Analysis (FMEA)? Ans. Failure Mode and Effect Analysis is a systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to prevent their occurrence. Q27. What is Test Maturity Model or TMM? Ans.Test Maturity Model or TMM is a five level staged framework for test process improvement, related to the Capability Maturity Model (CMM) that describes the key elements of an effective test process. Q28. What is the difference between API & ABI? Ans. Application Programming Interface (API) is a formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services. Whereas Application Binary Interface (ABI) is a specification defining requirements for portability of applications in binary forms across different system platforms and environments.Q29. What is I V & V? Ans. I V & V mean s Independent Verification and Validation. Verification typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. Verification can be done with the help of checklists, issues lists, walkthroughs, and inspection meetings. Whereas Validation typically involves actual testing and takes place after verifications are completed. Q30. What are the benefits of Software Validation? Ans. Software validation is an important tool employed to assure the quality of the software products.Few benefits are as under: 1) It increases the usability and reliability of the device software, resulting in reduced failure rates, less recalls and corrective actions, less liability to device manufacturers. 2) It reduces the long term costs by making it easier and less costly to reliably modify software and revalidate software changes. 3) It helps to reduce the long-term cost of software by reducing the cost of validation for each subsequent release of the sof tware. Q31. What is the role of Design Reviews in Software Development Life Cycle? Ans.Design review is a primary tool for managing and evaluating software development projects. Design reviews allow management to confirm that all goals defined in the software validation plan have been achieved. Formal design reviews are more structured and include participation from others outside the development team. Design reviews are documented, comprehensive, and systematic examinations of a design to evaluate the adequacy of the design requirements, to evaluate the capability of the design to meet these requirements, and to identify problems.Design reviews include examination of development plans, requirements specifications, design specifications, testing plans and procedures, all other documents and activities associated with the project. Q32. What is the need of Software Validation after a change? Ans. When any change even a small one is made to the software, following activities need to be performed: 1) Re-establishment of the validation status of the software. 2) Conducting necessary validation analysis – not for the sake of validation of the individual change, but o to know the effect of the change on the entire software system. ) Conducting suitable level of regression testing to show that unchanged but vulnerable portions of the system have not been adversely affected. Regression testing is meant to provide a confidence that the software has been validated after the change. Q33. How would you convince upper management that company needs a formal QA testing team? How would you explain that Software quality would not improve if the company get rid of QA team? Ans. Developing amazing applications isn’t the same as testing them, ut a experienced QA tester, I would rather have a developers testing application than the testers who can just plainly submit bug reports.QA team needs to build quality into software development life cycle. The bug in software d esign is 15times cheaper than a bug in code. QA productivity is really hard to measure. If QA team is doing testing right, , everything just happens smoothly, but if testers mess up even a little, everyone knows about it. To be successful, QA team must create test plans, create test harnesses, create test cases and use testing tools. QA should ensure whether the application code is effectively delivering on the business requirements provided.The developers should unit test their own code and deliver ‘perfectly good code’ , while QA testers should deliver ‘code that actually addresses business needs’. For a company that make software applications, a rock-solid QA department is absolutely irreplaceable. Q34. WhatQuality Assurance and Quality Control activities are done differently for COTS / GOTS project than for a traditional custom development project? | Ans. The activities themselves are broadly the same, but with different stakeholders, and different deta iled procedures for verification and validation.Often the challenge for SQA is to pin down the ownership of the requirements, which may be represented by a complex debate between marketing departments, technical eggheads, user groups, customer focus groups and other interested parties. | | Q35. What in your opinion is the role of SQA personnel with respect to inspections or testing? | Ans. Formally, the role is to make the inspection process or testing process visible, both to the participants (so they can see what they are achieving, how effective they are being) and to management (so that they can assess progress and risk).In practice, SQA personnel often need to act as facilitators or coaches. They are often regarded (wrongly) as the owners or custodians of the inspection or testing process, or even as the owners/custodians of the whole software process. Part of the training and mentoring for SQA personnel should address the difficult dilemma of how to be adequately engaged in th e software process without being landed with the responsibility for it. | | Q36. What are the most likely quality consequences of choosing an inappropriate life cycle model for a software project? | Ans. The most likely consequence is that the project will not deliver anything at all.Not because the lifecycle couldn? t be made to work technically, but because it will fail to contain the political tensions between stakeholders. | | Q37. What in your opinion, are the most important changes that occurred in the role of Software Quality Assurance during the last 5 to 10 years? Ho| Ans. rowing awareness and importance of public domain models such as SEI SW CMM, BOOTSTRAP and SPICE. Changing nature of software development, especially model-based development (CASE) and component-based development (CBD). Growing need to connect software of different ages and sources.Software projects not pure software development, but including maintenance, package selection and implementation, and other so ftware activities. (Perhaps software projects never were pure development, but such topics as project management, quality management and configuration management used to be taught as if they were. )   Faced with these changes, SQA needs to be both reductionist (giving close attention to the quality of components from various sources) and holistic (giving broad attention to the emergent properties of the whole assembled system, in terms of its overall fit to business requirements).As I see it, the mandate of SQA is to make defects in software products and processes visible to management. SQA fits into a context of software quality management where this visibility leads to corrective and preventative action (not itself part of SQA), and to general software process improvement. | Q38. Someone complains that during system testing the application often crashes. What likely process problem does that indicate? | Ans. Systematic failure to carry out proper unit testing.OR inconsistency be tween the development/unit test environment and the system test environment. AND ALSO management failure to respond promptly to the situation with corrective and preventative action. | | Q39. What exposure have you had to auditing? Internal? External? Certification related? | Ans. I have been trained as a lead assessor for ISO 9000 and also as an examiner for the European Quality Award. I have conducted internal audits and informal external assessments but not formal external audits. I have advised organizations on steps towards certification. | Q40. What in your opinion are the most significant fundamental differences between SEI SW-CMM and ISO 9000-3? | Ans. The main difference is what the two models tell you. ISO 9000-3 gives you a yes/no answer, whereas SEI SW-CMM gives you a more complex assessment. This implies different ways of using the models for SQA and process improvement. | 1. Difference is ISO is a standard and CMMI is a model with framework. 2. Other one is Specific pr actices should be determinded in ISO and where as CMMI model having predefined useful specific and general practices. | Q41. In your experience, who are the most important allies of SQA within an organization? | Ans. SQA is a form of risk awareness, and is therefore potentially allied to any senior management with a risk management focus. Within some companies/industries (e. g. insurance), software risks are seen as having mainly financial consequences, and so the main ally might be the financial director. Within other companies/industries (e. g. retail), software risks are seen as having mainly customer service implications, and so the main allies may be in marketing roles.In one client, we had useful conversations with the Company Secretariat, because of the due diligence implications of some software risks. These conversations were triggered by Y2K issues, but ranged much more widely. In practice, SQA often fails to make these alliances, because it gets bogged down in obscure sof tware technicalities and trivialities, which it is incapable of communicating effectively even to software engineers, let alone anybody else. | Q42. A company recruits its first and only SQA â€Å"specialist†. The person is new to the area.The company is relatively young, operates in a competitive commercial domain and has no previous SQA presence. The SQA specialist feels he needs to show some results during the next 6 to 9 months. What advice will you give him? | Ans. Start with a risk assessment, to identify the significant software risks and their business implications. Identify managers directly affected by these implications, who may be recruited as allies. Select a small number of issues to address in the initial phase. Try to include some quick wins, as well as some improvements that could be achieved within 3-6 months.Don? t try to do everything at once. At this stage, use whichever model you prefer (ISO 9000-3 or TickIT or SW-CMM or SPICE) merely as a framework, so that you know how what you? re doing fits into a larger picture. | Q43. What advice would you give to someone who asked you where to start to introduce to their company a metrics and quality reporting program? | Ans. Use the GQM approach to derive relevant metrics from personal and corporate goals. Select a small number of key metrics that will be directly relevant to project managers and/or software engineers.Put the metrics into the hands of the workers, as a tool for personal performance improvement. | | | | Q44. What is Total Quality Management? Ans. A company commitment to develop a process that achieves high quality product and customer satisfaction. Q45. What is Quality Circle? Ans. A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality. | | | | | | | | | | | | | | | | | Quality Assurance Question Bank Question bank Q1. Why software needs to be tested? Ans. Every software product needs to be tested since; the development process is unable to produce defect free software. Even if the development process is able to produce defect free software, we will not be able to know unless & until we test it. Without testing it, we shall not be having enough confidence that it will work. Testing not only identifies and reports defect but also measures the quality of the product, which helps to decide whether to release the product, or not. Q2.What is the reason that Software has Bugs? Ans. Following factors contribute to the presence of bugs in the software applications:- a. Software development tools like visual tools, class libraries, compilers, scripting tools, etc. usually introduce their own bugs in the system. b. To err is human. Likewise programmers do make mistakes while programming c. In fast-changing business environments continuously modified requirements are becoming a fact of life. Such frequent changes requested by the customer leads to errors in the application already nearing completion.Last minute design changes leads to many chaos like redesign of the whole system, rescheduling of engineers, scrapping of the work already completed, fresh requirements of compatible hardware etc d. A quickly written but poorly documented code is bound to have bugs. It becomes difficult to maintain and modify such code that is badly written or poorly documented. – its tough to maintain and modify code that is badly written or poorly documented; the result is bugs. In many organizations management provides no incentive for programmers to document their code or write clear, understandable, maintainable code.In fact, it’s usually the opposite: they get points mostly for quickly turning out code, and there as jobs security if nobody else can understand it (if it was hard to write, it should be hard to read). e. When project deadlines come too close & time pressure s come, mistakes are bound to come Q3. What is the difference between QA and Testing? Ans. QA stands for â€Å"Quality Assurance†, and focuses on â€Å"Prevention† of defects in the product being developed. It is associated with the â€Å"Process† and activities related to the Process Improvement.Quality Assurance measures the quality of the processes employed to create a quality product. Whereas â€Å"Testing† refers to â€Å"Quality Control†, and focuses on Detection of Defect and removal thereafter. Or Quality Control measures the quality of a product. Q4. What is the difference between Software Testing and Debugging? Ans. Testing is the process of locating or identifying the errors or bugs in a software system. Whereas Debugging is the process of Fixing the identified Bugs. It involves a process of analyzing and rectifying the syntax errors, logic errors and all other types of errors identified during the process of testing.Q5. What is the diff erence between a Bug and a Defect? Ans. â€Å"Bug† is a problem or an error in the software code, which is found in the application during Testing. Bug is responsible for failure of the application to comply with the desired specifications. Whereas â€Å"Defect† is problem reported by the customer during usage of the software application. Q6. What is the difference between a Bug and an Enhancement? Ans. â€Å"Bug† is a problem or an error in the software code, which is found in the application during Testing.Bug is responsible for failure of the application to comply with the desired specifications. Whereas â€Å"Enhancement† is the additional feature or functionality found and added to the application as desired by the end user / real word customer or tester during the testing process. Q7. What is the difference between Requirements & Specifications? Ans. â€Å"Requirements† are statements given by the customer as to what needs to be achieved by t he software system. Later on these requirements are converted into specifications which are nothing but feasible or implementable requirements.Whereas â€Å"Specifications† are feasible requirements derived from various statements given by the customer. These are the starting point for the product development team. Q8. What is the difference between Verification and Validation? Ans. â€Å"Verification† involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications to confirm whether items, processes, services, or documents conform to specified requirements or not. This can be done with the help of checklists, issues lists, walkthroughs, and inspection meetings. The purpose f verification is to determine whether the products of a given phase of the software development cycle fulfill the requirements established during the previous phase or not. Whereas â€Å"Validation† is the determination of the correctness of the final progr am or software product produced from a development project with respect to the user needs and requirements. This involves actual testing of the product and takes place after verifications are completed. â€Å"Software Verification† raises the question, â€Å"Are we building the Product Right? † that is, does the software conform to its specification. Software Validation† raises the question, â€Å"Are we building the Right Product? † that is, the software doing what the user really requires. Q9. What is difference between Waterfall Model and V Model? Ans. â€Å"Waterfall Model† Is a sequential software development model (a process for the creation of software) in which development is seen as flowing steadily downwards (like a waterfall)through the phases of requirements analysis, design, implementation, testing (validation),integration, and maintenance. To follow the waterfall model, we proceed from one phase to the next in a purely sequential manne r.In traditional waterfall model, testing comes at the far end of the development process. Whereas â€Å"V Model† or â€Å"Life Cycle Testing† involves carrying out verification of consistency, completeness and correctness of software at every stage of the development life cycle. It aims at catching the defects as early as possible and thus reduces the cost of fixing them. It involves continuously testing the system during all stages of the development process rather than just limiting testing to the last stage. Q10. What are Baseline Documents? Ans.Baseline documents are the documents, which have been approved by the customer and will not have any more changes. Baseline Documents cover all the details of the project and have undergone â€Å"walkthrough† process. Once a document is Base-lined it cannot be changed unless there is a change request duly approved by the customer. Service Level Agreement (SLA) & Business Requirement Documents (BRD) are the examples o f Baseline Documents. Q11. What is Defect Density? Ans. â€Å"Defect Density† Is a software metric defined as: Total number of defects per LOC (lines of code).Alternatively it can be: Total number of defects per Size of the Project. Here the measure of â€Å"Size of the Project† can be number of Function Points, Number of Feature Points, number of Use Cases or KLOC (Kilo Lines of Code) etc. Q12. What is Quality? Ans. Quality software is software that is reasonably bug-free, delivered on time and within budget, meets requirements and expectations and is maintainable. However, quality is a subjective term. Quality depends on who the customer is and their overall influence in the scheme of things.Customers of a software development project include end-users, customer acceptance test engineers, testers, customer contract officers, customer management, the development organization’s management, test engineers, testers, salespeople, software engineers, stockholders an d accountants. Each type of customer will have his or her own slant on quality. The accounting department might define quality in terms of profits, while an end- user might define quality as user friendly and bug free. Q13. What is an Inspection? Ans.An inspection is a formal meeting, more formalized than a walkthrough and typically consists of 3-10 people including a moderator, reader (the author of whatever is being reviewed) and a recorder (to make notes in the document). The subject of the inspection is typically a document, such as a requirements document or a test plan. The purpose of an inspection is to find problems and see what is missing, not to fix anything. The result of the meeting is documented in a written report. Attendees should prepare for this type of meeting by reading through the document, before the meeting starts; most problems are found during this preparation.Preparation for inspections is difficult, but is one of the most cost-effective methods of ensuring quality, since bug prevention is more cost effective than bug detection. A14. What is Six Sigma? Ans. â€Å"Six Sigma† means Six Standard Deviations from the mean. It is a methodology aimed to reduce defect levels below 3. 4 Defects Per one Million Opportunities. Six Sigma approach improves the process performance, decreases variation and maintains consistent quality of the process output. This leads to defect reduction and improvement in profits, product quality and customer satisfaction.Q15. What is difference between CMM and CMMI? Ans. â€Å"CMM† means â€Å"Capability Maturity Model† developed by the Software Engineering Institute (SEI). It is a process capability maturity model, which aids in the definition and understanding of an organization’s processes. CMM is intended as a tool for objectively assessing the ability of government contractors’ processes to perform a contracted software project. Whereas â€Å"CMMI† means â€Å"Capabil ity Maturity Model Integration† & it has superseded CMM. The old CMM has been renamed to Software Engineering CMM (SE-CMM).Q16. What is Verification? Ans. Verification ensures the product is designed to deliver all functionality to the customer; it typically involves reviews and meetings to evaluate documents, plans, code, requirements and specifications; this can be done with checklists, issues lists, walkthroughs and inspection meetings. Q17. What is Validation? Ans. Validation ensures that functionality, as defined in requirements, is the intended behavior of the product; validation typically involves actual testing and takes place after verifications are completed. Q18.What is a Test Plan? Ans. A software project test plan is a document that describes the objectives, scope, approach and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product. The complet ed document will help people outside the test group understand the why and how of product validation. It should be thorough enough to be useful, but not so thorough that none outside the test group will be able to read it. Q19. What is a Walkthrough? Ans.A walkthrough is an informal meeting for evaluation or informational purposes. A walkthrough is also a process at an abstract level. It’s the process of inspecting software code by following paths through the code (as determined by input conditions and choices made along the way). The purpose of code walkthroughs is to ensure the code fits the purpose. Walkthroughs also offer opportunities to assess an individual’s or team’s competency. Q20. What is Software Life Cycle? Ans. Software life cycle begins when a software product is first conceived and ends when it is no longer in use.It includes phases like initial concept, requirements analysis, functional design, internal design, documentation planning, test plann ing, coding, document preparation, integration, testing, maintenance, updates, re-testing and phase-ou Q21. What is the Difference between STLC & SDLC? Ans. STLC means † Software Testing Life Cycle†. It starts with activities like : 1) Preparation of Requirements Document 2) Preparation of Test Plan 3) Preparation of Test Cases 4) Execution of Test Cases 5) Analysis of Bugs 6) Reporting of Bugs 7) Tracking of Bugs till closure.Whereas SDLC means † Software Development Life Cycle† is a software development process, used by a systems analyst to develop an information system. It starts with activities like : 1) Project Initiation 2) Requirement Gathering and Documenting 3) Designing 4) Coding and Unit Testing 5) Integration Testing 6) System Testing 7) Installation and Acceptance Testing 8) Support or Maintenance Q22. What is the Difference between Project and Product Testing? Ans. If any organization is developing the application according to the client specifi cation then it is called as project.Accordingly its testing is known as â€Å"Project Testing† Whereas If any organization is developing the application and marketing it is called as product. Hence its testing is known as â€Å"Product Testing† Q23. How do you introduce a new software QA process? Ans. It depends on the size of the organization and the risks involved. For large organizations with high-risk projects, a serious management buy-in is required and a formalized QA process is necessary. For medium size organizations with lower risk projects, management and organizational buy-in and a slower, step-by-step process is required.Generally speaking, QA processes should be balanced with productivity, in order to keep any bureaucracy from getting out of hand. For smaller groups or projects, an ad-hoc process is more appropriate. A lot depends on team leads and managers, feedback to developers and good communication is essential among customers, managers, developers, t est engineers and testers. Regardless the size of the company, the greatest value for effort is in managing requirement processes, where the goal is requirements that are clear, complete and testable. Q24. What is configuration Management? Ans.Configuration Management (or CM) is the processes of controlling, coordinating and tracking the Standards and procedures for managing changes in an evolving software product. Configuration Testing is the process of checking the operation of the software being tested on various types of hardware. Q25. What is the role of QA in a software producing company? Ans. QA is responsible for managing, implementing, maintaining and continuously improving the Processes in the Company and enable internal projects towards process maturity and facilitate process improvements and innovations in the organization.Tester is responsible for carrying out the testing efforts in the company. In many companies QA person is responsible both the roles of Testing as wel l as creating and improving the processes. Q26. What is Failure Mode and Effect Analysis (FMEA)? Ans. Failure Mode and Effect Analysis is a systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to prevent their occurrence. Q27. What is Test Maturity Model or TMM? Ans.Test Maturity Model or TMM is a five level staged framework for test process improvement, related to the Capability Maturity Model (CMM) that describes the key elements of an effective test process. Q28. What is the difference between API & ABI? Ans. Application Programming Interface (API) is a formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services. Whereas Application Binary Interface (ABI) is a specification defining requirements for portability of applications in binary forms across different system platforms and environments.Q29. What is I V & V? Ans. I V & V mean s Independent Verification and Validation. Verification typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. Verification can be done with the help of checklists, issues lists, walkthroughs, and inspection meetings. Whereas Validation typically involves actual testing and takes place after verifications are completed. Q30. What are the benefits of Software Validation? Ans. Software validation is an important tool employed to assure the quality of the software products.Few benefits are as under: 1) It increases the usability and reliability of the device software, resulting in reduced failure rates, less recalls and corrective actions, less liability to device manufacturers. 2) It reduces the long term costs by making it easier and less costly to reliably modify software and revalidate software changes. 3) It helps to reduce the long-term cost of software by reducing the cost of validation for each subsequent release of the sof tware. Q31. What is the role of Design Reviews in Software Development Life Cycle? Ans.Design review is a primary tool for managing and evaluating software development projects. Design reviews allow management to confirm that all goals defined in the software validation plan have been achieved. Formal design reviews are more structured and include participation from others outside the development team. Design reviews are documented, comprehensive, and systematic examinations of a design to evaluate the adequacy of the design requirements, to evaluate the capability of the design to meet these requirements, and to identify problems.Design reviews include examination of development plans, requirements specifications, design specifications, testing plans and procedures, all other documents and activities associated with the project. Q32. What is the need of Software Validation after a change? Ans. When any change even a small one is made to the software, following activities need to be performed: 1) Re-establishment of the validation status of the software. 2) Conducting necessary validation analysis – not for the sake of validation of the individual change, but o to know the effect of the change on the entire software system. ) Conducting suitable level of regression testing to show that unchanged but vulnerable portions of the system have not been adversely affected. Regression testing is meant to provide a confidence that the software has been validated after the change. Q33. How would you convince upper management that company needs a formal QA testing team? How would you explain that Software quality would not improve if the company get rid of QA team? Ans. Developing amazing applications isn’t the same as testing them, ut a experienced QA tester, I would rather have a developers testing application than the testers who can just plainly submit bug reports.QA team needs to build quality into software development life cycle. The bug in software d esign is 15times cheaper than a bug in code. QA productivity is really hard to measure. If QA team is doing testing right, , everything just happens smoothly, but if testers mess up even a little, everyone knows about it. To be successful, QA team must create test plans, create test harnesses, create test cases and use testing tools. QA should ensure whether the application code is effectively delivering on the business requirements provided.The developers should unit test their own code and deliver ‘perfectly good code’ , while QA testers should deliver ‘code that actually addresses business needs’. For a company that make software applications, a rock-solid QA department is absolutely irreplaceable. Q34. WhatQuality Assurance and Quality Control activities are done differently for COTS / GOTS project than for a traditional custom development project? | Ans. The activities themselves are broadly the same, but with different stakeholders, and different deta iled procedures for verification and validation.Often the challenge for SQA is to pin down the ownership of the requirements, which may be represented by a complex debate between marketing departments, technical eggheads, user groups, customer focus groups and other interested parties. | | Q35. What in your opinion is the role of SQA personnel with respect to inspections or testing? | Ans. Formally, the role is to make the inspection process or testing process visible, both to the participants (so they can see what they are achieving, how effective they are being) and to management (so that they can assess progress and risk).In practice, SQA personnel often need to act as facilitators or coaches. They are often regarded (wrongly) as the owners or custodians of the inspection or testing process, or even as the owners/custodians of the whole software process. Part of the training and mentoring for SQA personnel should address the difficult dilemma of how to be adequately engaged in th e software process without being landed with the responsibility for it. | | Q36. What are the most likely quality consequences of choosing an inappropriate life cycle model for a software project? | Ans. The most likely consequence is that the project will not deliver anything at all.Not because the lifecycle couldn? t be made to work technically, but because it will fail to contain the political tensions between stakeholders. | | Q37. What in your opinion, are the most important changes that occurred in the role of Software Quality Assurance during the last 5 to 10 years? Ho| Ans. rowing awareness and importance of public domain models such as SEI SW CMM, BOOTSTRAP and SPICE. Changing nature of software development, especially model-based development (CASE) and component-based development (CBD). Growing need to connect software of different ages and sources.Software projects not pure software development, but including maintenance, package selection and implementation, and other so ftware activities. (Perhaps software projects never were pure development, but such topics as project management, quality management and configuration management used to be taught as if they were. )   Faced with these changes, SQA needs to be both reductionist (giving close attention to the quality of components from various sources) and holistic (giving broad attention to the emergent properties of the whole assembled system, in terms of its overall fit to business requirements).As I see it, the mandate of SQA is to make defects in software products and processes visible to management. SQA fits into a context of software quality management where this visibility leads to corrective and preventative action (not itself part of SQA), and to general software process improvement. | Q38. Someone complains that during system testing the application often crashes. What likely process problem does that indicate? | Ans. Systematic failure to carry out proper unit testing.OR inconsistency be tween the development/unit test environment and the system test environment. AND ALSO management failure to respond promptly to the situation with corrective and preventative action. | | Q39. What exposure have you had to auditing? Internal? External? Certification related? | Ans. I have been trained as a lead assessor for ISO 9000 and also as an examiner for the European Quality Award. I have conducted internal audits and informal external assessments but not formal external audits. I have advised organizations on steps towards certification. | Q40. What in your opinion are the most significant fundamental differences between SEI SW-CMM and ISO 9000-3? | Ans. The main difference is what the two models tell you. ISO 9000-3 gives you a yes/no answer, whereas SEI SW-CMM gives you a more complex assessment. This implies different ways of using the models for SQA and process improvement. | 1. Difference is ISO is a standard and CMMI is a model with framework. 2. Other one is Specific pr actices should be determinded in ISO and where as CMMI model having predefined useful specific and general practices. | Q41. In your experience, who are the most important allies of SQA within an organization? | Ans. SQA is a form of risk awareness, and is therefore potentially allied to any senior management with a risk management focus. Within some companies/industries (e. g. insurance), software risks are seen as having mainly financial consequences, and so the main ally might be the financial director. Within other companies/industries (e. g. retail), software risks are seen as having mainly customer service implications, and so the main allies may be in marketing roles.In one client, we had useful conversations with the Company Secretariat, because of the due diligence implications of some software risks. These conversations were triggered by Y2K issues, but ranged much more widely. In practice, SQA often fails to make these alliances, because it gets bogged down in obscure sof tware technicalities and trivialities, which it is incapable of communicating effectively even to software engineers, let alone anybody else. | Q42. A company recruits its first and only SQA â€Å"specialist†. The person is new to the area.The company is relatively young, operates in a competitive commercial domain and has no previous SQA presence. The SQA specialist feels he needs to show some results during the next 6 to 9 months. What advice will you give him? | Ans. Start with a risk assessment, to identify the significant software risks and their business implications. Identify managers directly affected by these implications, who may be recruited as allies. Select a small number of issues to address in the initial phase. Try to include some quick wins, as well as some improvements that could be achieved within 3-6 months.Don? t try to do everything at once. At this stage, use whichever model you prefer (ISO 9000-3 or TickIT or SW-CMM or SPICE) merely as a framework, so that you know how what you? re doing fits into a larger picture. | Q43. What advice would you give to someone who asked you where to start to introduce to their company a metrics and quality reporting program? | Ans. Use the GQM approach to derive relevant metrics from personal and corporate goals. Select a small number of key metrics that will be directly relevant to project managers and/or software engineers.Put the metrics into the hands of the workers, as a tool for personal performance improvement. | | | | Q44. What is Total Quality Management? Ans. A company commitment to develop a process that achieves high quality product and customer satisfaction. Q45. What is Quality Circle? Ans. A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality. | | | | | | | | | | | | | | | | |

Biography of Harriet Tubman

Biography of Harriet Tubman Free Online Research Papers Harriet Tubman was a runaway slave who was known as the â€Å"Moses of her people.† Over the course of ten years at her own risk, she led many slaves to freedom using the Underground Railroad. The Underground Railroad was a secret network of safe houses where runaway slaves could stay on their journey north to freedom. Later in her life she became a leader in the abolitionist movement and a spy for the federal forces in South Carolina. Harriet Tubman was born in 1820 in Dorchester County, Maryland. She was born into slavery and was beaten as a child by her various owners. One of her owners hit her in the head with a heavy metal weight intended to hit another slave. She suffered a traumatic head injury which caused disabling headaches, seizures, powerful visionary and dream activity, and spells of hypersonic which occurred throughout her life. In 1849 she escaped to Philadelphia and went back and took her family with her including her 70 year old parents. She traveled in the night with extreme secrecy and never lost a fugitive. The fugitive slave law was passed in 1950 made it harder for slaves to escape. After that law was passed she started leading fugitives further north into Canada. If any of her fugitives she was helping tried to go back she would take out a gun and threaten to kill then because that would all of them in risk of being caught. She made 19 trips to Maryland which were all dangerous trips. When the Civil War began Harriet Tubman worked for the Union Army. She worked as a cook and a nurse then as an armed scout and spy. She was the first women to lead an armed expedition which freed more than seven hundred slaves. After the war she went to a family home in Auburn, New York to take care of her aging parents and other people in need. She also worked in her later years to promote the cause of woman’s suffrage, she worked with many woman including Susan B. Anthony and Emily Howland. In 1911 Harriet became very frail and was admitted into a rest home named in her honor. On March 13, 1913 she died of pneumonia. Harriet Tubman will be remembered as someone who helped many people throughout her life. Research Papers on Biography of Harriet Tubman19 Century Society: A Deeply Divided EraBook Review on The Autobiography of Malcolm XQuebec and CanadaComparison: Letter from Birmingham and CritoPersonal Experience with Teen PregnancyHip-Hop is ArtAppeasement Policy Towards the Outbreak of World War 2Mind TravelWhere Wild and West MeetTrailblazing by Eric Anderson

The development of a practice framework Essays

The development of a practice framework Essays The development of a practice framework Essay The development of a practice framework Essay Although there appears to be a emphasis on adopting an eclectic approach The development of a practice framework for professionals working in the area of human services and although the individual may not necessarily have control over whether they will experience loss throughout their life, they can control how they respond to them. However, Reactions to traumatic events seem to be determined by a number of variables such as the nature of the event, the character, personality, previous and present experiences, beliefs, attitudes and expectations, beliefs of the individual involved (Parkinson, 1997). Positives and negatives of various theoretical approaches What difference does their approach have in relation to grief and loss Some people work purely from theory while others work predominantly from personal experience. whereas sympathy seeks to console, empathy works to understand empathy requires a certain emotional distance you have to step away from grief, fear, and anger to create a space in which your thoughts can exert a calming influence on your feelings (Ciaramicoli Ketcham, 2000). Empathy Traditional forms of mutilation for bereavement were, and in some instances still are, practiced among the indigenous people of Australia. For example, in Queensland many aboriginal tribes slashed their bodies or foreheads to show sorrow at the death or injury of a kin (Wilson, 1982). Many Westerners who work at assisting the bereaved have notions of grief pathology such as grief that is never expressed, grief that goes on to intensely for too long, grief that is delayed, grief that involves delusions, grief that involves threat to others, and grief that involves self-injury (Parkes, 1997). Professionals who work with people who have suffered loss must prepare themselves psychologically and philosophically for this work, and a key aspect of this is to be able to accept suffering as endemic to life (Kennedy, 1990). Grief can be expressed through such masked appearances as school absenteeism and bed wetting in children, delinquency and drug abuse in adolescents (and adults), and promiscuity, suicide, and diverse physical and mental illnesses in adults (Fiefel, 1995). Stroebe and Stroebe (19 ) state that grief is a normal affective response to the loss of a loved one which, if it runs an uncomplicated course does not require therapeutic intervention (p. 8). However, the focus of the majority of early research into grief and loss has been in relation to conjugal bereavement ( ) and the terminally ill patient ( ). Research into the area of grief and loss during the latter part of the 20th has identified a broad range of losses, albeit tangible or intangible, that can initiate a grief response. Furthermore, the literature on grief and loss has recognized the impact of traumatic events and a broad range of factors that include the individuals interpretation of the event ( ), the nature of the event (Parkinson, 2000; Davidson Baum, 1990), gender (Kritsberg, 1993), age (Rosenthal, 2000), level of maturity, previous experience and coping strategies (Davies Holden, 1997), support networks (Figley, 1988; Miller, 1994), and cultural display rules (Moos, 1995; Atkinson, 1997). is not yet a fully recognized academic discipline (Miller Omarzu, 1998). Unlike trauma which is acknowledged Loss is a subjective experience and, for this very reason, two or more people encounter the same the persons reaction In psychology, modernism has given rise to the machine metaphor of human functionality. When applied to grief, this view suggests that people need to recover from their state of intense emotionality and return to normal functioning and effectiveness as quickly and efficiently as possible (Stroebe, Gergen, Gergen Stroebe, 1995, p. 233). 1995, 226). Beginning with Freud, theorists have understood the purpose of grief as relinquishing the lost object so that new attachments in the present can be formed and that failure to sever the bond has been defined as pathological or complicated grief (Klass, 1995). Theoretical approaches based on psychodynamics, attachment theory, social construction of loss, cognitive theories and constructivist psychology constitute the major movements that have evolved over the twentieth century with respect to our knowledge about loss and grief (Murray, 2003). Answers perhaps as to why people do not go through a normal grieving process. According to the romanticist concept of grief the death of a beloved person was a defining event in the life of the bereaved, signaling the beginning of what was often a lifelong memorialisation of the deceased (DeSpelder Strickland, 1995). Since mourning is a process and not a state, incompleted tasks can impair further growth and development, although the tasks do not necessarily follow a specific order, there is some ordering suggested in the definitions, you cannot handle the emotional impact of a loss until you first come to terms with the fact that the loss has happened (Worden, 1991). Grieving does not proceed in a linear fashion, it may reappear to be reworked (Worden, 1991). There is not definitive time for when mourning is finished four months, one year, never (Worden, 1991). Only when the lost person has been internalized and become a part of the bereaved is the mourning process complete (Parkinson, 2000). The process of psychological debriefing should be an essential component in our response to survivors of traumatic events (Parkinson, 2000) As with adults, children follow different paths through their grief experiencing different reactions at different times (Fitzgerald, 1992). The most significant variable contributing to response to bereavement was having a history of psychological disturbance and those having a history were more likely to describe themselves as anxious and depressed, socioeconomic status was a significant contributor to depression and state and chronic anxiety levels in the bereaved individuals (Bartrop, Hancock, Craig, Porritt, 1992). A number of risk factors that have the potential to complicate normal grief reactions include sudden, unexpected death, traumatic events, ambivalence in a relationship, pre-existing psychopathology, concurrent crises, perceived preventability, lack of social support (McKissock, 1998). Of all the risk factors, centrality, the degree of significance the person who has died has in our everyday life, to our identity or our sense of well being, is the most likely to indicate the intensity of grief we experience (McKissock, 1998). Bereaved people dont let go, the reconnect through memories and changing perceptions to form a new relationship with the person who has died (McKissock, 1998). Men and women grieve differently, men tend to seek solace in the warmth of familiar sexual intimacy with their partners whereas women long for emotional closeness, or hugs that dont demand a response (McKissock, 1998).

Maybank S Core Values As Organization Values Accounting Essay Essays

Maybank S Core Values As Organization Values Accounting Essay Essays Maybank S Core Values As Organization Values Accounting Essay Essay Maybank S Core Values As Organization Values Accounting Essay Essay Introduction Khoo Teck Puat went to work for OCBC, get downing his calling as a simple bank clerk. By the 1950s, Khoo had risen to a place of senior executive. By the terminal of the decennary, nevertheless, Khoo recognized that his chances at OCBC remained limited. Given the deficiency of farther promotion unfastened to him at OCBC, every bit good as what he considered the company s narrow position on its hereafter, Khoo decided to put up his ain bank and applied for a banking licence. That licence was granted to Khoo and a figure of other OCBC executives who left the bank to organize Malayan Banking Berhad in 1960. Malayan Banking Berhad or Maybank was incorporated in Malaysia on 31 May 1960 and commenced operations on 12 September 1960. On 17 February 1962, Maybank was listed on the so Kuala Lumpur Stock Exchange ( today Bursa Malaysia ) . Maybank is today among the top companies by market capitalization on Bursa Malaysia. Maybank is Malaysia s largest fiscal services group with entire assets transcending RM330 billion. The Group has an extended planetary web of 1,750 offices in 14 states viz. Malaysia, Singapore, Indonesia, Philippines, Brunei Darussalam, Vietnam, Cambodia, China, United Kingdom, U.S.A. , Bahrain, Papua New Guinea, Pakistan and Uzbekistan The Group offers a comprehensive scope of fiscal services and merchandises runing from commercial banking, investing banking, Islamic banking, cards issue, offshore banking, leasing and hire purchase, insurance, factorization, legal guardian services, plus direction, stock broking, campaigner services, venture capital and Internet banking. Today, the Maybank Group has over 40,000 employees who serve over 18 million clients worldwide, with 9.5 million clients in Malaysia entirely. MAYBANK S CORE VALUES AS ORGANIZATION VALUES Beginning: www.maybank2u.com.my Maybank has five nucleus values as foundation of concern which came out from their Logo ( T.I.G.E.R ) , all its staffs are guided by five nucleus values, which they are to uphold, emulate and body these values in their day-to-day working lives. A DECISION MAKING PROCESS Decision doing procedure is an of import function for senior direction to guarantee sustainability of its administration success. Due to excellence amp ; efficiency as one of its cardinal value, transparence is really of import in determination devising procedure. For illustration, the composing of the Board reasonably reflects the involvement of the bulk stockholder, which is adequately represented by the assignment of its nominee managers without compromising the involvement of the minority stockholders. The influence of the campaigners for the major stockholder of Maybank is balanced by the presence of the independent managers on the Board whose corporate positions carry important weight in the Board s deliberation and decision-making procedure. In this respect, the independent managers are in consequence stand foring the involvement of the minority stockholders by virtuousness of their functions and duties. The independent managers do non take part in the twenty-four hours to- twenty-four hours direction of the Group and do non prosecute in any concern dealing or other relationships with the Group in order to guarantee that they remain genuinely capable of exerting independent judgement and act in the best involvements of the Group and its stockholders. Further, the Board is satisfied and assured that no person or group of managers has unchained powers of determination that could make a possible struggle of involvement. The Board believes that the quality of its managers, each of whom offers a wide scope of accomplishments, cognition and experience, ensures that they are able to dispute, develop and drive the Group s vision and scheme, and that the administration criterions are continuously upheld. The Chairman will ever guarantee that the Board s determinations are based on consensus of the bulk, and any concerns or dissenting positions expressed by any managers on any affairs deliberated at meetings of the Board or any of its Committees every bit good as the meeting s determination, will consequently be addressed and recorded in the relevant proceedingss of meetings. The nucleus values are non merely intend for the direction squad, it besides has affects its in-between direction, line directors and its staff. The nucleus values are the guideline for its staff to base at for determination devising procedure. For an illustration, if the supervisor is measuring their staff public presentation, it will be made base on its nucleus value on how the staff has met the ends set upon them such as Teamwork, Integrity, Growth, Excellence A ; Efficiency A ; Relationship Building. POLICIES A ; PROCEDURES Policies and processs are the nervus of an organisation. Its failure will hold inauspicious impact on company s public presentation. As such, Maybank has ensured conformity with internal control, and the prescribed Torahs and ordinances by the regulators. These policies and processs are set out in the Group s Standard Practice Instruction and updated from clip to clip in tandem with alterations to the concern environment or regulative guidelines. As unity is one of its cardinal value, they has established necessary controls to safeguard the bank and supply value added services to its stockholders and clients such as: aˆ? An one-year concern program and budget is submitted to the Board for blessing. Actual public presentations are reviewed against the targeted consequences on a monthly footing leting timely responses and disciplinary actions to be taken to extenuate hazards. The Board besides reviews regular studies from the direction on the key runing statistics, every bit good as legal and regulative affairs. The Board besides approves any alterations or amendments to the Group s policies. aˆ? The Board has besides set up several Board Committees to help the Board in executing its inadvertence maps. Specific duties have been delegated to these Board Committees, all of which have formalised footings of mention. These Committees have the authorization to analyze all affairs within their range and study to the Board with their recommendations. aˆ? Group Executive Risk Committee, Group Management Committee, Group IT Steering Committee, Group Management Credit Committee, Group Procurement Tender Committee ( now restructured and known as Group Procurement Committee GPC ) , Group Staff Committee, Internal Audit Committee, Asset and Liability Committee and Credit Committee are besides established as portion of its stewardship map to guarantee effectual direction and supervising of the countries under the several Committee s horizon. aˆ? Recruitment and publicity policies/guidelines within the Group are established to guarantee appropriate individuals of quality are selected to make full places available. Formal preparation programmes either face-to-face or through e-learning, semi and one-year public presentation assessments and other relevant processs are in topographic point to guarantee that staff are competent and adequately trained in dispatching their responsibilities and duties efficaciously. Proper guidelines are besides drawn-up for expiration of staff. aˆ? A clearly defined model with appropriate authorization and authorization bounds has been approved by the Board for acquisitions and disposals of assets, presenting stamps, writing-off of operational and recognition points, contributions, every bit good as O.K.ing general and operational disbursals. Based on their reappraisal, the external hearers have reported to the Board that nil had come to their attending that causes them to believe that the Statement on Internal Control is inconsistent with their apprehension of the procedures the Board have adopted in the reappraisal of the adequateness and unity of the internal control of the Group. Bottom of Form PLANNING A ; CONTROL A It is of the position that the internal control model is designed to pull off the Group s hazards within an acceptable hazard net income, instead than extinguish the hazard of failure to accomplish the policies, ends and aims of the Group. It can therefore lone supply sensible instead than absolute confidence of effectivity against material misstatement of direction and fiscal information or against fiscal losingss and fraud. Maybank has put in topographic point an ongoing procedure for placing, measuring, monitoring and pull offing important hazards that may impact the accomplishment of concern aims. The procedure which has been instituted throughout the Group is updated and reviewed from clip to clip to accommodate the alterations in the concern environment and this ongoing procedure has been in topographic point for the whole fiscal twelvemonth under reappraisal. The function of Management includes: identifying and measuring the hazards faced ; explicating related policies and processs to pull off these hazards ; designing, runing and supervising a suited system of internal controls ; and implementing the policies approved by the Board. A Control Structure A The cardinal procedures that the Directors have established in reexamining the adequateness and unity of the system of internal controls include the followers: Risk Management Framework Maybank has established an administration construction with clearly defined lines of duty, bounds of authorization and answerability aligned to concern and operations demands which support the care of a strong control environment. It has extended the duties of the Audit Committee to include the appraisal of internal controls, through the Internal Audit ( IA ) map. The Board has besides delegated the duty of reexamining the effectivity of hazard direction to the Risk Management Committee. The effectivity of the hazard direction system is monitored and evaluated by the Group Risk Management map, on an ongoing footing. Risk direction rules, policies, processs and patterns are updated on a regular basis to guarantee relevancy and conformity with Torahs and ordinances and are made available to all employees. To farther enhance hazard consciousness within the Maybank Group, a series of Risk Awareness Programs have been conducted at all degrees of staff underscoring the importance of control environment. The Group has besides adopted a whistle blowing policy, supplying an avenue for employees to describe existent or suspected misconduct or misdemeanors of the company s policies and ordinances in a safe and confidential mode. Constitution of the three ( 3 ) lines of Defence concept hazard taking units, hazard control units and internal audit. The hazard taking units are responsible for the daily direction of hazards built-in in their concern activities while the hazard control units are responsible for puting the hazard direction model and development tools and methodological analysiss. Complementing this is internal audit, which provides independent confidence of the effectivity of the hazard direction attack. A INFORMATION PROCESSING A ; COMMUNICATION Maybank Group s Code of Ethics and Conduct sets out the sound rules and criterions of good pattern in the fiscal services industry, which are observed by the managers and its employees. A Both managers and employees are required to continue the highest unity in dispatching their responsibilities and in traffics with stakeholders, clients, fellow employees and regulators. This is in line with the Group s Core Values which give accent on behavioral moralss when covering with 3rd party and fellow employees. The Group communicates the Code to all managers and employees upon beginning of their employment and is deemed to be portion of the Footings and Conditions of Service. A Maybank, as a keeper of public financess, has a duty to safeguard its unity and credibleness. It is on this apprehension that the administration sets out clearly the codification of moralss and behavior for its staff. The codification stipulates the sound principles that will steer all Maybank staff in dispatching their responsibilities. It sets out the criterions of good banking pattern. A In add-on to these, staff should: A Ensure unity and truth of records and/or minutess. Ensure carnival and just intervention in all concern traffics on behalf of the Bank. Keep the highest criterion of service in their relationship with clients. Maintain confidentiality of all dealingss and traffics between the Bank and its clients. However, confidential information refering a client may be given or made available to third parties merely with anterior written consent of the client or when revelation is authorised under the Banking and Financial Institutions Act, 1989. Pull off their fiscal affairs good and non capable to monetary embarrassment. Observe and comply with Torahs and ordinances associating to the operations of the Bank. Show grasp, regard and client centricity Develop long-run and reciprocally good relationships Build client trueness and understand their outlooks Develop strong and friendly working relationship with co-workers to accomplish concern ends Embrace and support diverseness of work force ( e.g. gender, race, experiences A ; positions ) Build reciprocally good relationship with all stakeholders Decision At Maybank, staffs are guided by its Core Values of Teamwork, Integrity, Growth, Excellence A ; Efficiency and Relationship edifice. As an built-in portion of its staff day-to-day attempts, these values guide them to pursuit for growing and excellence. Any aspiration can come true with the right chance is the cardinal word of Maybank. The direction squad has set their sights on choosing the brightest heads to be portion of their squad. The hunt is on for divine persons who are ready to travel the distance with one of the taking fiscal establishments in Malaysia. Maybank offers the needed chances for growing and excellence to accomplish a reciprocally good partnership and winning border. A Maybank focuses on capturing growing chances in high growing while taking a proactive and conservative attack to capital direction by go oning to set up their presence in high growing markets. Maybank s strong path record of fiscal strengths and high recognition evaluations allow them to maintain their impulse and continue with robust public presentation even amidst the current environment. The re-energised Core Values, i.e. acronym T.I.G.E.R. which stands for Teamwork, Integrity, Growth, Excellence A ; Efficiency and Relationship Building was the consequence of the focal point groups conducted with Maybankers from assorted units across Sectors. This simplified version purposes to complement our bing Core Values and to do it easy for all employees to retrieve and understand the values. Note: The bing Core Values remains unchanged The Re-energized Core Valuess are the simplified version that complement the current Core Valuess The Core Values is the foundation that supports Maybank Group s Aspirations The Core Valuess are values or behavioral features that form the foundation on which we perform work and behavior ourselves By beef uping their nucleus concern and franchise, they gain competitory advantage by accomplishing synergisms across their diverse group. Domestically, they aim to accomplish leading across cardinal and profitable sections. Internationally, they capture value from new investings and go on to prosecute organic enlargement by presenting invention and superior client value. They are the top recruiter of endowment and view their leading pool and talent grapevine as cardinal to gaining their aspirations. They invariably seek to heighten public presentation direction and accomplish cost optimization by concentrating on effectual Information Technology operations and heightening employee productiveness.