Implementation of Information System Essay Example | Topics and Well Written Essays - 2500 words

Implementation of Information System - Essay Example The identification and listing of stakeholders is very important and the initial step in an Is project. The list of the stakeholders should include all the people who have the power to effect the system. The second category of stakeholders includes the people whose position and power will be affected by the project. The third and most important category is the users of the project. It is important to recognise the actual stakeholders of the project. The representatives of these stakeholders should be included in all the discussions related to the project in order to sketch the clear vision and necessities of project. After the identification process it is important to determine the problem statement. The entire stakeholder should reach an agreement on the definition of problem in order to design a project to fit the problem size for all the stakeholders. The stakeholders can be divided into different groups according to their expectations regarding the project. The use and expectation of the stakeholders will help in designing the project in right way. It is seen in case of different projects that the developers and the involved stakeholders do not know about what they exactly want from the project. The development of an internal model regarding the perceptions of developers and stakeholders regarding the project will help all the people involved to expect, create, build and effectively use and support the system. 3. Identify and List Use Cases Use cases are the core of the whole process. The use cases present the complete functionality of the system. A use case in defined as an interaction between the user and the system. The use cases of the different stakeholders differ according to their expectations. They are an effective and meaningful tool to manage and organise the project. The use case collection in undertaken according to three steps: 1. To discover the use case while discussing with the stakeholders this step involves a general overview of two to three sentences of the use case. 2. At the second stage an analysis of

The Values of Life Essay Example | Topics and Well Written Essays - 750 words

The Values of Life - Essay Example I’m still 23, and I’m in the second year in the university, which I need to use them in order to get my bachelor degree. Accomplishment is a value that drives a person to meet their personal goals and objectives in the sense that, there is that need to be somewhere after going through the education program. In my case, I want to accomplish so much in life, for example, I want to ensure that by the time I get to 30, years I will have a well-established career, and I will be financially stable. Additionally, I will give back to the society by helping the needy as it is the society that has helped in shaping my values. Honesty is a virtue that should be owned by every individual this us because it allows people to move forward and to correct mistakes that were made in the process of achieving goals and objectives. Honesty as a value allows people to have good relationships because there is a creation of the trust, which is very important in the lives of people. Am living in accordance with these value by ensuring that in each and every activity I undertake I am first honest with myself and then to other people. There is a need to treat every individual equally and fairly and by so doing, other people will not feel left out. Being fair means that there is justice when it comes to serving people and also treating them. This value is important to me because it allows me to see every person as an equal which in turn allows me to respect every person despite their social, cultural or economic background. Strength is another value that I have become accustomed to especially through my education because sometimes being a university student is not easy. This is because it requires strength and dedication to ensure that a person completes their course. This is because sometimes school can be frustrating, but with adequate strength, I set my mind to the goals and objectives I want to receive in life.

The Life and Times of a Nobel Laureate Essay Example for Free

The Life and Times of a Nobel Laureate Essay One of the more important historical figures within the scientific community was what Werner Heisenberg contributed to quantum physics. Born in Germany on December 5, 1901 to Dr. August Heisenberg and Annie Wecklem, the influences were already prominent for Werner to excel in sciences as he father had already excelled in his own dominance of â€Å"Middle and Modern Greek languages at the University of Munich† (Nobel Foundation, n. d. ) After graduation from the University of Munich in 1920, he excelled substantially in the field of physics and worked under such great physicists as Max Born, Franck and Hilbert and became an assistant under Max Born after receiving his Ph. D. in 1923. Heisenberg’s life moved on to become one of the better known physicists in German and until the Second World War he was a â€Å"Professor of Physics at the University of Berlin and the Director of the Kaiser Wilhelm Institute of Physics. † (Nobel Foundation, n. d. ) Dominance in Physics Heisenberg continued his dominance in the field of physics well after the War and continued to pursue his lifelong love of physics well past the War with his â€Å"return in 1946 to Germany and reorganized, along with colleagues, the Institute for Physics at Gottingen and in 1948 it was renamed the Max Planck Institute for Physics†. (Nobel Foundation, n. d. ) Perhaps the best association the world of physics has with the Heisenberg name is through the publishing of his â€Å"theory of quantum physics, published in 1925, when he was only 23 years old. For this theory and the applications of it which resulted in the discovery of allotropic forms of hydrogen, Heisenberg was awarded the Nobel Prize for Physics in 1932† (Nobel Foundation, n. d. ). This theory was based only â€Å"on what was observed, that is to say, on the radiation emitted by the atom. We cannot, he said, always assign to an electron a position in space at any given time, nor follow it in its orbit, so that we cannot assume that the planetary orbits postulated by Neils Bohr actually exists. Mechanical quantities, such as position, velocity, etc. should be represented, not by ordinary numbers, but by abstract mathematical structures called â€Å"matrices† and he formulated his new theory in the terms of matrix equations. † (Nobel Foundation, n. d. ) Heisenberg’s theories were not simply limited to quantum physics but he was also famous for his â€Å"principle of uncertainty† which â€Å"lays it down that the determination of the position and the momentum of a mobile particle necessarily contains errors the product of which cannot be less than the quantum constant h and that, although these errors are negligible on the human scale, they cannot be ignored in the studies of the atom†. (Nobel Foundation, n. d. )

System Analysis Cinema Booking Information Technology Essay

System Analysis Cinema Booking Information Technology Essay Waterfall Life Cycle: Waterfall life cycle is the most familiar and classic life cycle model. It is sometimes referred to as the classic life cycle or the linear sequential model. It the simplest type of life cycle and very easy to use and understand. In the waterfall life cycle, each phase needs to be completed before the next phase can start. Each phase is separate and does theres no overlapping. Requirements Analysis System Design Implementation Unit Testing Integration System Testing Operation Maintenance Phases: Requirement Analysis: Requirements are collected from end-user consultations and then analyzed. A requirement Specification Document is created which guides the next phases of the model. System Design: System design is prepared by studying the requirements specification from the 1st phase. The hardware requirements are specified in this stage and a picture of the overall system architecture is produced. Implementation Unit Testing: In this phase, the work is divided in small units; actual coding starts. Testing makes sure that the software successfully meets the required specification; and that any errors are identified. Integration System Testing: All units are integrated and tested to ensure that the system meets the requirements. At the end of this stage, the software is delivered to the customer. Operation Maintenance: This is the longest phase in the model. The software is updated in this phase to correct any errors, make the software more efficient and to meet the changing needs of the customers. Advantages: It is a linear sequential model Very easy simple to implement; therefore well suited for small projects It is also cheaper Minimal amount of resources are required to implement this model Testing is done after each phase to ensure the project is on the right path Easily manageable because model is rigid; each phase has certain deliverables a review process after a phase is over, which makes understanding of the designing procedure simpler. Disadvantages: High risk uncertainty. Not suited for long projects where the requirements may change. The working software is only produced late during the life cycle. It is difficult to estimate the cost and time for each stage. No back tracking possible; if an error occurred in the earlier stages of the cycle, it cant be corrected for that batch. V-Shaped Model: The V-Shaped Model is very similar to the Waterfall model life cycle, but testing is done upfront instead of later in the life cycle like in Waterfall model. Like Waterfall model, V-Shaped Model is also a sequential cycle and a new phase is only started after the completion of the previous phase. Each development stage is matched with its respective testing stage; Requirements Æ’Â   System Testing, High-Level Design Æ’Â   Integration Testing, Low-Level Design Æ’Â   Unit Testing. V-Shaped model is very useful for systems which require high reliability. System Testing Requirements Integration Testing High-Level Design Low-Level Design Unit Testing Implementation Phases: Requirements: Commences the life cycle; system test plan is created. High-Level Design: Focuses on design system architecture; integration tests are created. Low-Level Design: Software components are designed unit tests are created. Implementation: Coding takes place in this phase. Advantages: Its easy to use; but not as easy as the waterfall model. More chance of success than the waterfall model due to the early testings. Project moves quickly to the implementation stage. Useful for small projects; considering the requirements are easily understood known upfront. Disadvantages: Bugs in the final stage are very costly to fix. Total development time of v-shaped model is more than the waterfall model. Does not contain any risk analysis activities Throwaway Prototyping model: Very useful in situations the users needs and requirements are not clear. The main objective of this model is to validate or drive the system requirements. This model is developed to reduce the requirement risks. This prototype is developed and then delivered to the user for experiments and then it is discarded, hence throw away prototype; and it should not be considered as a final system. Advantages: Requirement risks are fewer If delivered model does not meet the users needs, then it can be discarded and new models can be developed. Disadvantages: Can be undocumented Developers may be push to deliver the throw away prototype as the final system, which is not recommended. System structure may be degraded due to the changes made during the software development process. Evolutionary Prototyping model: In evolutionary prototyping, the initial prototype is developed and it is then refined through number of stages to final stage. The main objective is to deliver the working system to the user. Verification is not possible because there is no specification. Requirement gathering, Refinement Quick Design Building Prototype Refine Requirement End-User Evaluation End Product Refine Prototype Advantages: System development involves the user Working system is delivered fast A more useful system can be delivered Disdvantages: Time required to complete project is unknown. May have problems; Management, Maintenance and Verification problems. Incremental model: The incremental model is similar to the Waterfall life cycle model, but there are multiple development cycles here, which makes it a multi-waterfall cycle. It has an iterative approach (repeating), and each iteration passes through each of the phases. A working version of software can be produced during the first iteration, which means a functioning software is available early in the cycle. 1st Increment Analysis Test Code Design 1st Increment delivery 2nd Increment 2nd Increment delivery Analysis Test Code Design nth Increment Test Code Design Analysis nth Increment delivery Time Advantages: Working Software can be developed quickly early during the life cycle. Its less costly to change requirements therefore; Flexible. Easier to test and fix errors End-users get to see working software early in the software development life cycle. Disadvantages: The total development cost is higher Well defined project planning is required to distribute the work properly. Spiral Model: Also known as Spiral lifecycle model. This model combines the features of the waterfall model and the prototyping model. The Spiral Model is most commonly used in large, complicated and expensive projects; and constant review is needed to stay on target. The main area in which Spiral model is used is Game development due to the constantly changing goals size of the large project. Cumulative Cost Progress 1. Determine Objectives, Alternatives, Constraints 2. Evaluate alternatives. Identify, and resolve risks. Review 3. Development Tests 4. Plan next Phases Advantages: Important issues can be discovered earlier, which makes estimation of budget schedule more realistic reliable. Good amount of risk analysis Really good for large projects Software can be conceived early in the life cycle. Flexible allows for multiple iterations. Disadvantages: Not suitable for smaller projects Success of the project depends on the risk analysis Costly Requires knowledgeable staff; for risk analysis. 2. Identification of the Functions and Purpose of a Systems Life Cycle. The systems life cycle is a series of well-defined phases in the development of systems. It is very important that a project should meet the required specification, should be within budget and delivered on time. Large system developments can take a long time to be developed and can be very costly too; therefore most organisations use the systems life cycle (stages) to develop systems because it saves time isnt as costly. Programming Maintenance Installation Design Feasibility Study Analysis 1. Feasibility study Different solutions are examined in this stage. First step of this stage is to discover the funds available and then compare with the benefits of the company, in view of their requirements because sometimes in order to arrive at final decision a trade-off (give and take) has to be accepted e.g. less functionality for less cash. There are three different options that a company could choose: Options Benefit Cost Performance Company does not change anything No interference to the business. Least cost System remains outdated. Less efficient N/A Company updates half of the system Least efficient parts are redesigned to improve performance while best parts of the system are not changed Moderate, light training for staff 40% improved Complete upgrade More profitable High, New equipments, Upgraded Software, Training for staff. 80% improved (over the old system) 2. Investigation and Analysis Investigation First step of this stage is to investigate the old system and problem it is causing. There are different ways to find out the problems: Questionnaires and Interviews Observing people using the old system Following the information from the point it enters the system till the point of output. Taking the cause of the problem These steps should lead toward the true cause of the problem Analysis The next part is to analyze how the existing system works how information is handled and how people interact with it. To Analyze, different methods are used e.g. System diagrams This shows the dealings between different systems in the company or outside. System diagram shows how they interact and what depends on what and so on. Data Flow Diagram This shows the movement through the system, how the system deals with the information, how information flows through the system, how dose it connect and disconnect and what the outputs are. Process Diagram This shows how people interact with the system for example an employee makes a claim, first it will go to manager who will counter-sign the claim it will then go to account manager who authorizes payment and so on. 3. Design This stage defines the system in greater detail and the best way to start this stage is to write down exact details of the new system e.g. The data Inputs The data Outputs Screen Layouts Documents that are printed out Procedure of the data that flows through the system The structure of any files that store data How information is accessed And so on The testing procedure comes after the system has been built. In my opinion it is really useful to build a test procedure before starting to build a system because, if you know how the system will be tested, it will lead you towards a better design. Prototype Prototype is something that allows you to build a program without having to worry about the details, it is to confirm that design is likely to work. The master document created in this stage is called System Requirement Document. 4. Programming This stage takes the design forward and put it into practice and this stage take place when the client has agree on what needs to be done (Requirement Specification) and the Analyst has clearly described what needs to be done(System Requirement Document). There are several terms involved in this stage so it is reasonable to break down the System Requirement Document into sections that each can develop. At this stage following things may take place: The software developers write code The hardware people develop equipment The testing team develops test plans The user-testing groups follow the test plans and check the system works as expected 5. Installation Now the system is developed and tested and it is working correctly and doing what client wanted. The key events in this stage are: Data conversion: Data stored on the old system are now converted into the correct format for the new system. System Change Over: switch off the old system and turn on the new system, which is not as simple as it sound. Alternatives Run the old and new system in parallel for a time Customer does not care what your IT system is made up of, they are only concerned about their order. One method is to run the old system along the new one, then in the quiet time the new system store the old system data and is then fully loaded and ready to go. Training Training is the vital part of this stage, staff training must take place. Staff needs to be shown how to use the new system How to access help when they run into difficulties Member of a development team should be available on call A user manual should be available for staff 6. Maintenance The new system is running smoothly and it will need to be looked after so maintenance stage takes care of the following that can take place: Problems are cleared as they occur Tweaks to the system are applied to improve performance The system has to be moved due to office movement Data is backed up and kept safe Equipment are replace as required Basically this stage never ends until the new system becomes old and is then switch with new system. 3. Undertake a User Needs Analysis (UNA) for your system. SYSTEM USED: CINEMA BOOKING SYSTEM UNA is the first stage in the system development process. UNA in system developing includes task that is demanded by the user for new or different system. Requirements must be actionable, measurable, and testable and must be related to user needs. The best way to undertake UNA in my view is to have a workshop with the users who will use the new system. This will give me one clear idea of what the new system must do. When working on developing the new system Ill have a better idea of what users wants from the new system, keeping every users requirements in mind. So Ill set up a workshop, in which Ill ask users what they want from the new system. I will document their requirements as I go along. Basically Ill ask different questions from the users and then the users themselves will work out what kind of a new system they want. Questions that Ill ask users: What the new system should do? Do you want it to be networked with other computers? How long the information needs to be saved? Should staff login when using the system? Anything needs to be printing? What information needs to be print out? Payment procedure/ types of cards? Discounts: student Inputs, process and outputs Internet booking/ serial number only for internet booking This is how Ill design the system, keeping in view the users requirements. It will be an advanced system which will be quite reliable and it will be easy for the users to use this system. System Requirements: Inputs Serial number only for Internet booking Name Payment Age/ discount Name of the movie Date Process Theater Number Discount reduction Output Movie ticket for customer Information saved in the system This program is supposed to save the information of the customer and print out a movie ticket containing the required information. Print out of the ticket Name Age payment Discount Payment after discount Theater Number Movies name Date System will show this information on the Ticket. 4. Produce a Systems Context Diagram for your system. User/ Staff New system Customer Info given Input filled Data saved Ticket Process Calculate discount if applied and check for seats in theatre Saved in server for 3 days and is access able by any member of staff Checks the Ticket Ticket given Check movie and time Login Administrator Login Update Movie Data Delete Old Data Updates the system This Diagram explains the program I am building for the Cinema. Circles in the diagram mean the first thing is done by Administrator, User/ Staff and the customer. Explanation: Administrator must update the system by inserting new movies and deleting old movies. User/ Staff is the person who can access the system by login in and takes the details (info given) of the customer. User/ Staff then enter the details (input filled) in the system. News System will process the input and process it, calculate discount if applied and check for seats available in theatre. Itll then give two outputs Data Saved and Ticket. Data Saved meaning the data will be saved in a server for three days and is access able by any member for staff but the saved data cannot be changed after the Ticket is printed out. Ticket will be printed out and is going to be checked by the staff. Staff will give the ticket to the customer. 5. Produce a Level 1 Current Physical Data Flow Diagram for your system. D1 User/ Staff/ counter Enquires Deposits and Withdrawals Process customer data Tickets recheck Data store System Cash Customer Customer details/ data Print Ticket Details are checked Ticket handed to the customer Resource Flow Data Flow Outside data Process D2 In this Physical Data flow diagram customer, who is outside data, goes to the counter to purchase a ticket for the movie. Counter/ staff take his query and process it, system then stores the data and process a ticket, which is given to the customer. 6. Produce a Level 1 Required Logical DFD for your system. Admin User/ Staff Customer System Process Data Stored Ticket Updates the System Customer details/ data Ticket Input customer detail/ data Calculates discounts Theatre No. Stores in a server Print out Ticket details are checked by user/ staff Data Flow Source of Data In this Diagram Admin is updating the data for the system and user is taking the detail/ data of the customer and entering it in the system to process a Ticket for customer. 7. Decompose one of the processes to a Level 2 Required Logical Data Flow Diagram for your system. Admin System Process Data Stored Updates the System Adding new movie data Deleting old movie data Stores admin new data Stores customer data Movie is suitable for customer (age) Theatre availability Calculate discounts Store data in server Auto deletes 3 days old customer data Access to old data In this Diagram Admin is updating the data for the system and system is processing customer details against admin updated data and it is then stored in a server for three days. 8. Construct a Logical Data Structure for the system you are producing. Customer Staff/ counter Ticket Enquires Ticket Customer will seek staff on counter for any enquiry or to purchase a movie ticket Provide service to customer Staff will take customer details from customer for a movie ticket To process a Ticket, staff will have to enter customer details in the system for a movie ticket Ticket is handed to the customer after staff checks for any errors 9. With the aid of your Logical Data Structure, produce an Entity/Event Matrix for your database system. Customer Purchasing a ticket for a movie Enquiry Staff/ Counter Staff/ Counter Solve the issue Yes No Job done Admin Enter customer details in the system System process Ticket Data stored Staff (checks it) Customer (takes ticket) Server 10. Describe the Required Physical Data Model. Customer details/ data Admin Admin login Update new movie data Delete old movie data Problem solving Staff Customer service System operator Staff login handle customer details Ticket Cashier Customer Enquires Ticket purchaser Updates the System Input customer detail/ data System Customer internet serial no. Customer name Customer age Payment method Discount Amount paid Name of the movie Theatre number Date Stores admin updated data Access to old data Check for any errors on the ticket Process Movie is suitable for the customer (age) Discount reduction Theatre number Draft ticket Print out Data stored Stored in server Access able Auto delete 3 days old data Ticket Customer name Customer age Payment method Discount Amount paid Movies name Theatre number Date Admin updates the system and solve problems Staff handles the customers and input the customers details in the system System processes the data and check for availabilities Data is stored for 3 days Ticket is issued for customer as a receipt

Creon’s Perspective in Oedipus Rex and Sophocles Antigone :: Antigone essays

Creon’s Perspective in Oedipus Rex and Antigone   Ã‚   The role of the king in the time of Greek tragedies was simultaneously desired and dreaded because of the king's responsibility to the people and because of the effects of the position on the king's character. Creon reveals such ambivalent thoughts towards the kingship in his speech defending himself from Oedipus's conspiracy accusation in Oedipus the King; these ambivalent thoughts reveal much about the nature of the kingship, especially in conjunction with Creon's later actions in Antigone.   Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚   In attempting to refute Oedipus's assertion that Creon has taken part in a conspiracy to obtain the kingship, Creon evaluates the nature of the kingship and of his present role. First, he says, "Consider, first, if you think any one/ would choose to rule and fear rather than rule and sleep" (36.584-585). By this, Creon means that the main difference between his position and the king's is that of the accompanying action to ruling. In both positions, one is a ruler who holds great power over the state. However, the king is placed in a greater place of accountability to the people. This accountability is what Creon says inspires "fear" in the king, for if affairs of state or of the people fall into decline, the king is the first person whom the citizenry look to blame. This is analogous to executive leaders throughout history, as one can see in looking at American presidents and the correlation between the present conditions and events of the nation to the public's opinion of the president, regardless of the actual impact that his decisions may have made in these conditions. Creon maintains that he has the same amount of power as the king but without the accountability that inevitably leads a king to distress. Creon's reasoning concerning the equality between his power and Oedipus's leads him to state:    I was not born with such a frantic yearning to be a king- but to do what kings do. And so it is with every one who has learned wisdom and self-control. (36.587-590)    He means that he has never desired the position of king, because he sees no advantage over his present position in the state. Rather, he sees the disadvantage of the fear that accompanies the position of king. Creon has evaluated this situation for his circumstances and then goes further in stating that anyone with wisdom and self-control would come to such a conclusion as well.

Leakey, Richard :: essays research papers fc

Richard Leakey- Homo habilis Richard Leakey was born December 19, 1944 in Nairobi, Kenya. His parents were the esteemed anthropologists Louis and Mary Leakey. Richard first became a tour guide in Kenya, but changed his mind when he found an extinct human jaw. He then schooled himself by completing a two-year secondary education program in six months. From 1967-77 he and his co-workers dug up around 400 fossils, that accounted for 230 individuals. The most important discovery was an almost complete skull found in 1977, which Richard believe to be a new species called Homo habilis. Richard Leakey’s accomplishments are discovering the crania of Australopithecus boisei in 1969 with the archaeologist Glynn Isaac on the East shores of Lake Turkana, Homo habilis in 1972, and Homo erectus in1975. He was appointed administrative director in 1968 of the National Museum of Kenya, and in director 1974. Since 1989 he has been director of the Wildlife and Conservation Management Service, Ke nya. His publications include Origins in 1977 and The Making of Mankind in 1981, both with Roger Lewin. Australopithecus africanus inhabited the earth roughly 3 - 1.6 million years ago. The characteristic difference between the Ausrtalopithicus afarenis and africanus is the height and brain capacity. The height of the africanus is 1.4 m and the brain capacity is approximately 400 - 600 cc. Smaller incisor teeth and a slightly flatter face are also noted. The afarensis has a height of 1.2 m and a cranial capacity of 380 - 450 cc. Sticks, and stones were most likely used to gather food by the Australopithecus africanus. Homo habilis (also known as "handy man") is theorized to have lived with Australopithecus africanus. Homo habilis was known as â€Å"handy man† because he used primative stone tools. The flat face and large molars of the Homo habilis resemble the Australopithecus lineage. The brain size of the Homo habilis is about 700 cc which is larger than the Austr alopithecus). The "apelike" body structure with long arms and a small body was a characteristic of the Homo habilis. Recent discoveries, such as from Lake Turkana, of better-preserved fossils have revealed new insights on early Homo in the Plio-Pleistocene. Of this new habilis material, the most amazing is a nearly complete cranium discovered in 1972 at East Lake Turakana. This individual, with a cranial capacity if 775 cm3, is clearly outside the known range for Australopithecines and it overlaps the lower boundary for Homo.

Medical Assistant Ethics

There are numerous ethical issues that a medical assistant may encounter in a daily office or hospital setting. It is unethical to have a conversation with a fellow coworker regarding a patient. The patient may overhear or worse they may be related to someone in the office. It is no one’s business as to why the patient had an appointment. Another unethical behavior that is unacceptable is foul language in front of the patients. They do not need to hear that kind of language under any circumstances. When a patient comes in to see you and smells of urine or alcohol, be courteous to the patient and do not judge the patient. This patient may not have the means to shower daily or they may be sick and are unaware of the odor. A good thing to remember when dealing with an ethical issue is always do the right thing at the right time and it will never become an issue. Medical Assistants need to put themselves into the shoes of the patient. They need to ask themselves, how would I want to be treated? How would I like to be recognized in the eyes of the health care worker? How would I want my family treated? In doing this little experiment on a daily basis they will come to realize that we all are human and need to be treated equally, no matter what the situation may be. The general skills of a Medical Assistant consist of basic customer service. They must be able to communicate between the doctors and the patients. They need to do this within the legal and ethical boundaries. Document every conversation because if it is not documented then the conversation never happened. Educate the patient within the scope of practice. Let the patient know of community resources for future reference of patients’ needs. Operational functions are also a part of the daily duties of a Medical Assistant. Performing inventory of supplies and equipment so items can be replenished. Doing these functions will always help in maintaining the highest quality of care for the patient. Clinical skills of the CMA of general patient care to make them as comfortable as possible. Many diagnostic procedures are required of the CMA; from collecting specimens to performing radiology tests. Fundamental principles consisting of sterilizing rooms and equipment are skills that a CMA will do daily. Doing these clinical skills while practicing standard precautions must be a high priority for everyone in the health care facility. Administrative skills are essential for a CMA to do the job that is required of them. It is all done via computer so there typing skills must be adequate for them to succeed. From patient schedules to bookkeeping to insurance forms, all is done on a daily basis. Licensure is when a government agency authorizes individuals to work in a job. A CMA does not need a license to work. Professions needing licenses are nurses and therapists. Registration is a professional organization in a specific health care field that administers exams and/or maintains a list of qualified individuals. CMA’s can apply for a registration credential. This would give them a better paying job and more responsibilities at their present facility. Certification involves the issuing of a certificate and credentials by a professional organization to someone who has met the experience and education guidelines of that organization. This basically tells everyone that you have finished your schooling for Medical Assisting. For a Medical Assistant to maintain his/her certification they must recertify either by passing the CMA exam again or by receiving sixty recertification points, thirty of which must be AAMA approved CEU’s. The points must be as follows 10 administrative, 10 clinical, 10 general and 30 from any combination of the above three categories. You must also submit proof (photocopy of the card and length of program) of current, provider level CPR certification. Continuing education units (CEU’s) can be received by reading online books and taking a test when finished. The AAMA sponsors many workshops, seminars, and county, state, and national conferences for MA’s to remain current in their field and earn the CEU’s. For the safety of the patient and employee, an MA should never perform any tasks that are outside the scope of the MA practice. Outside the scope of a Medical Assistant’s practice would be suturing a wound, administering a pap test for a female patient, or possibly giving the patient the diagnosis of the symptoms they are experiencing. A physician should never delegate the full range of physical therapy to anyone other than a physical therapist. Under no circumstances should the Medical Assistant do any duties that are outside their scope of practice. If I were approached by my supervisor to perform outside of my scope of practice, I would calmly and rationally refuse the request. I do not feel that any job is worth losing if you are asked to perform it wrong. I would explain to my supervisor politely that I am not qualified to perform the task asked and I would suggest someone else in the facility that is capable. I would let them know I would be willing to help out with any other task that is within my scope of practice. In order to find the article listed, I went to google. com and found an article from AAMA website on scope of practice act for Wisconsin. You can also go to AAMA website. Click on site map. Go to CMA today and scroll down. Click on Public Affairs Articles. Scroll down until you see the article found on google. If I were approached by a patient or a fellow coworker and referred to as a nurse, I would explain to them that I am a Medical Assistant and explain some of my job functions. I would let them know that there is a big difference and the title does need to be corrected. I would let them know that if I were to acknowledge the comment of being called a nurse, I could lose my job as well as my career. They may not understand that it is a very serious offense. I would explain them that the actual nurses would not be able to be titled as a doctor so the same holds true for me. When a medical assistant misrepresents herself/himself, they are in fact making the entire profession look bad in the eyes of the patient. The disciplinary results that could happen to the medical assistant are far greater than the prestige of stating you are who you are not. State disciplinary actions can result in fines and other criminal penalties. All office personnel should avoid referring to the medical assistant as a nurse also not just the patient. The doctor can also lose his career and/or a fine. I could lose my certification also.