100. Medical Transcription
Medical transcription, also known as MT, is an allied health profession, which deals in the process of transcription, or converting voice-recorded reports as dictated by physicians and/or other healthcare professionals into text format. Medical transcription is the process of converting / typing health care professionals dictated notes into written transcripts. Medical transcription is the act of translating from oral to printed form (on paper or computer) the record of patient's medical history and treatment. It is mandatory and legally binding on the health care professionals to hardcopy any type of medical treatment, procedure, diagnostic test, etc. and it must be documented into a patient's permanent medical record. The patient information is dictated by health professional into a digital or analog recorder and/or through the use of a phone dictation system.
Basic MT knowledge, skills and abilities: Knowledge of basic to advanced medical terminology is essential. Average verbal communication skills. Above-average memory skills. Ability to sort, check, count, and verify numbers with accuracy. Demonstrated skill in the use and operation of basic office equipment/computer. Ability to follow verbal and written instructions. Records maintenance skills or ability. Above-average typing skills. Knowledge and experience transcribing (from training or real report work) in the Basic Four work types. Knowledge of and proper application of grammar. Knowledge of and use of correct punctuation and capitalization rules. Demonstrated MT proficiencies in multiple report types and multiple specialties.
Medical transcription is challenging, but it is also very rewarding. Medical Transcriptionists are an integral part of the healthcare industry; they are active participants in the care-giving process. Medical Transcription is also a skill which continues to teach. With every new medical specialty, with every new medical procedure, with every new disease or treatment program, the medical transcriptionist is constantly learning. Likewise, professional medical transcriptionists are ALWAYS in demand, because people will continue to need medical care throughout their lives.
Medical Transcriptionist uses a computer and their favorite word processor to transcribe this information into a typed document. These typed documents either in hardcopy or softcopy are then forwarded to the dictator for verification and approval. After approval these signed documents become part of a patient's permanent medical record. These documents can be Initial Evaluation / Consultation, Progress Note, Follow-up Visit, Reassessment Sheet, Psychological Test, 6-month Psychological Evaluation, Letter, Lab/Test Results, SOAP Note, Nutritional Assessment, Preoperative Assessment, Postoperative Assessment, Workmen's Comp, Telephone Conversation, Treatment Plan Summary, Completion Note, History & Physical examination, Discharge Summary etc.
Sunday, March 1, 2009
99. Graphics Designer
Graphics (from Greek γραφικός; see -graphy) are visual presentations on some surface, such as a wall, canvas, computer screen, paper, or stone to brand, inform, illustrate, or entertain. Examples are photographs, drawings, Line Art, graphs, diagrams, typography, numbers, symbols, geometric designs, maps, engineering drawings, or other images. Graphics often combine text, illustration, and color. Graphic design may consist of the deliberate selection, creation, or arrangement of typography alone, as in a brochure, flier, poster, web site, or book without any other element. Clarity or effective communication may be the objective, association with other cultural elements may be sought, or merely, the creation of a distinctive style. Graphics can be functional or artistic. The latter can be a recorded version, such as a photograph, or an interpretation by a scientist to highlight essential features, or an artist, in which case the distinction with imaginary graphics may become blurred.
It's common for people in conversation to routinely use the terms "images," "artwork," and "graphics" interchangeably. As instructional designers, it is very important to recognize that those terms mean different things and that those differences have a profound effect on what type of people have to be involved, what technical resources are required, and what kind of time frame is necessary for production. It's also important to recognize that all visual support material does not fit neatly into these definitions. The edges of each category blend together in a continuum. Furthermore, these definitions are not universally recognized. That said, most people, most of the time will understand the distinctions you are making when using these terms. When we talk about images, we are talking about digital photography. Whether it is on-the-scene documentation of events or studio setups both involve capturing less than a second's worth of the real world (with some notable exceptions) in real-time. Volumes have been written about the professional photographer's "eye" or ability to be at the right place and time. This method for producing visual support material is nevertheless the most rapid and easiest to accomplish (assuming you have made the financial investment in equipment of adequate quality for the application.).
Graphics (also called illustrations or artwork) form a fundamental part of multimedia materials, be they pictures, drawings, diagrams, charts, graphs, photographs, paintings, cartoons, or maps. Indeed, one would be hard pressed to attach the label "multimedia" to an instructional program that doesn't contain any graphics. Graphics are the overarching "containers" for artwork, and/or digital photographic images assembled into a single presentation area to support the conveyance of a message or the creation of an impression. The range of element types, and infinite combinations of those elements pose a potential stumbling block in production time, but good element cataloging, and judicious element creation can mean rapid development times with a minimum of creative effort, greater cost efficiency (through repurposing), and greater flexibility in meeting instructional requirements. Artwork is the term we use to describe two dimensional visual support materials that is drawn, painted or otherwise assembled from abstract components (e.g., polygons) into meaningful information. These items require the most talent to accomplish, the most technical skill to execute, and take the longest to produce.
Until recently, however, graphics have not been used as widely as they might have been in instructional materials because they were expensive to produce and to duplicate, particularly if they used color. The advent of computer-based multimedia development tools has changed that significantly, by putting in the hands of virtually any author the capability of producing graphics that are simple or lavish, full-color or black-and-white. Collections of clip art and stock photographs, and sophisticated graphics production programs, have diminished the need for manual graphic skills. However, producing effective and attractive graphics still isn't a completely straightforward process. Even the most powerful graphics programs can be used to produce ugly and ineffective graphics (and if the World Wide Web is any indication, they most certainly are!)
98. Extensible Markup Language (XML)
XML is a text-based markup language that is fast becoming the standard for data interchange on the Web. It is classified as an extensible language, because it allows the user to define the mark-up elements. XML's purpose is to aid information systems in sharing structured data, especially via the Internet, to encode documents, and to serialize data; in the last context, it compares with text-based serialization languages such as JSON, YAML and S-Expressions. As with HTML, you identify data using tags (identifiers enclosed in angle brackets, like this: <...>). Collectively, the tags are known as "markup". But unlike HTML, XML tags tell you what the data means, rather than how to display it. Where an HTML tag says something like "display this data in bold font" (...), an XML tag acts like a field name in your program. It puts a label on a piece of data that identifies it (for example:... ).
XML is an open, text-based markup language that provides structural and semantic information to data. This "data about data," or metadata, provides additional meaning and context to the application using the data and allows for a new level of management and manipulation of Web-based information. XML, a subset of the popular Standard Generalized Markup Language (SGML), has been optimized for the Web. This helps make XML a powerful, standards-based complement to HTML that could be as important to the future of information delivery on the Web as HTML was to its beginning. XML is intended to be used by content creators as well as by programmers. Since XML is text-based, it can be read and worked with easily in relatively nontechnical situations, but its ability to organize, describe, and structure data also makes it ideal for use in highly technical applications. XML thus provides common ground for creating structured data and making it available for manipulation and display.
XML provides a basic syntax that can be used to share information between different kinds of computers, different applications, and different organizations. XML data is stored in plain text format. This software- and hardware-independent way of storing data allows different incompatible systems to share data without needing to pass them through many layers of conversion. This also makes it easier to expand or upgrade to new operating systems, new applications, or new browsers, without losing any data. With XML, your data can be available to all kinds of "reading machines" (Handheld computers, voice machines, news feeds, etc), and make it more available for blind people, or people with other disabilities. XML provides a gateway for communication between applications, even applications on wildly different systems. As long as applications can share data (through HTTP, file sharing, or another mechanism), and have an XML parser, they can share structured information that is easily processed. Databases can trade tables, business applications can trade updates, and document systems can share information. It supports Unicode, allowing almost any information in any written human language to be communicated.
It can represent common computer science data structures: records, lists and trees. Its self-documenting format describes structure and field names as well as specific values. The strict syntax and parsing requirements make the necessary parsing algorithms extremely simple, efficient, and consistent. Content-based XML markup enhances search ability, making it possible for agents and search engines to categorize data instead of wasting processing power on context-based full-text searches. XML is heavily used as a format for document storage and processing, both online and offline. It is based on international standards. It can be updated incrementally. It allows validation using schema languages such as XSD and Schematron, which makes effective unit-testing, firewalls, acceptance testing, contractual specification and software construction easier. The hierarchical structure is suitable for most (but not all) types of documents. It is platform-independent, thus relatively immune to changes in technology. Forward and backward compatibility are relatively easy to maintain despite changes in DTD or Schema. Its predecessor, SGML, has been in use since 1986, so there is extensive experience and software available.
XML is a text-based markup language that is fast becoming the standard for data interchange on the Web. It is classified as an extensible language, because it allows the user to define the mark-up elements. XML's purpose is to aid information systems in sharing structured data, especially via the Internet, to encode documents, and to serialize data; in the last context, it compares with text-based serialization languages such as JSON, YAML and S-Expressions. As with HTML, you identify data using tags (identifiers enclosed in angle brackets, like this: <...>). Collectively, the tags are known as "markup". But unlike HTML, XML tags tell you what the data means, rather than how to display it. Where an HTML tag says something like "display this data in bold font" (...), an XML tag acts like a field name in your program. It puts a label on a piece of data that identifies it (for example:
XML is an open, text-based markup language that provides structural and semantic information to data. This "data about data," or metadata, provides additional meaning and context to the application using the data and allows for a new level of management and manipulation of Web-based information. XML, a subset of the popular Standard Generalized Markup Language (SGML), has been optimized for the Web. This helps make XML a powerful, standards-based complement to HTML that could be as important to the future of information delivery on the Web as HTML was to its beginning. XML is intended to be used by content creators as well as by programmers. Since XML is text-based, it can be read and worked with easily in relatively nontechnical situations, but its ability to organize, describe, and structure data also makes it ideal for use in highly technical applications. XML thus provides common ground for creating structured data and making it available for manipulation and display.
XML provides a basic syntax that can be used to share information between different kinds of computers, different applications, and different organizations. XML data is stored in plain text format. This software- and hardware-independent way of storing data allows different incompatible systems to share data without needing to pass them through many layers of conversion. This also makes it easier to expand or upgrade to new operating systems, new applications, or new browsers, without losing any data. With XML, your data can be available to all kinds of "reading machines" (Handheld computers, voice machines, news feeds, etc), and make it more available for blind people, or people with other disabilities. XML provides a gateway for communication between applications, even applications on wildly different systems. As long as applications can share data (through HTTP, file sharing, or another mechanism), and have an XML parser, they can share structured information that is easily processed. Databases can trade tables, business applications can trade updates, and document systems can share information. It supports Unicode, allowing almost any information in any written human language to be communicated.
It can represent common computer science data structures: records, lists and trees. Its self-documenting format describes structure and field names as well as specific values. The strict syntax and parsing requirements make the necessary parsing algorithms extremely simple, efficient, and consistent. Content-based XML markup enhances search ability, making it possible for agents and search engines to categorize data instead of wasting processing power on context-based full-text searches. XML is heavily used as a format for document storage and processing, both online and offline. It is based on international standards. It can be updated incrementally. It allows validation using schema languages such as XSD and Schematron, which makes effective unit-testing, firewalls, acceptance testing, contractual specification and software construction easier. The hierarchical structure is suitable for most (but not all) types of documents. It is platform-independent, thus relatively immune to changes in technology. Forward and backward compatibility are relatively easy to maintain despite changes in DTD or Schema. Its predecessor, SGML, has been in use since 1986, so there is extensive experience and software available.
97. Hypertext Transfer Protocol (HTTP)
HyperText Transfer Protocol, or HTTP, is the underlying and primary communications protocol used by the World Wide Web (WWW); other Internet protocols include File Transfer Protocol (FTP), Gopher, and Telnet. HTTP is the protocol used in the transfer of HyperText Markup Language (HTML) files and stands at the very core of the World Wide Web. HTTP and HTML are closely linked; one defines connectivity, the other defines interface. HTTP is the transport or transfer protocol offering the base method by which all clients (meaning your Web browser program installed on your computer) and servers (the Web server hosting a Web site displayed in your browser) communicate with each other. HTML, on the other hand, is the base standard by which content is formatted and displayed effectively in Web pages in browsers. The communications protocol used to connect to Web servers on the Internet or on a local network (intranet). Its primary function is to establish a connection with the server and send HTML pages back to the user's browser. It is also used to download files from the server either to the browser or to any other requesting application that uses HTTP.
As the transport protocol, HTTP defines how information is formatted and transmitted, and what actions Web servers and browsers take in response to commands you send over the Internet. For example, when you enter a URL, or Uniform Resource Locator, in the "Location" or "Address" field of your browser, you are sending an HTTP command to the Web server (which hosts that URL or Web site), directing it to fetch and transmit the requested Web page with its various media embedded--text, graphics, audio, or video. The HTTP protocol uses the concept of reference provided by the Universal Resource Identifier as a Location (URL) or Name (URN). When a hyperlink is composed in HTML, the URL uses the general form http://host:port-number/path/file.html. In HTTP/0.9 and 1.0, the connection is closed after a single request/response pair. In HTTP/1.1 a keep-alive-mechanism was introduced, where a connection could be reused for more than one request. Such persistent connections reduce lag perceptibly, because the client does not need to re-negotiate the TCP connection after the first request has been sent.
HTTP is a "stateless" request/response system. The connection is maintained between client and server only for the immediate request, and the connection is closed. After the HTTP client establishes a TCP connection with the server and sends it a request command, the server sends back its response and closes the connection. The first version of HTTP caused considerable overhead. Each time a graphics file on the page was requested, a new protocol connection had to be established between the browser and the server. In HTTP Version 1.1, multiple files could be downloaded with the same connection. It also improved caching and made it easier to create virtual hosts (multiple Web sites on the same server). Methods PUT and DELETE are defined to be idempotent, meaning that multiple identical requests should have the same effect as a single request. Methods GET, HEAD, OPTIONS and TRACE, being prescribed as safe, should also be idempotent. HTTP is a stateless protocol.
By contrast, the POST method is not necessarily idempotent, and therefore sending an identical POST request multiple times may further affect state or cause further side effects (such as financial transactions). In some cases this may be desirable, but in other cases this could be due to an accident, such as when a user does not realize that their action will result in sending another request, or they did not receive adequate feedback that their first request was successful. While web browsers may show alert dialog boxes to warn users in some cases where reloading a page may re-submit a POST request, it is generally up to the web application to takes responsibility for handling cases where a POST request should not be submitted more than once. Note that whether a method is idempotent is not enforced by the protocol or web server. It is perfectly possible to write a web application in which (for example) a database insert or other non-idempotent action is triggered by a GET or other request. Ignoring this recommendation, however, may result in undesirable consequences if a user agent assumes that repeating the same request is safe when it isn't.
HyperText Transfer Protocol, or HTTP, is the underlying and primary communications protocol used by the World Wide Web (WWW); other Internet protocols include File Transfer Protocol (FTP), Gopher, and Telnet. HTTP is the protocol used in the transfer of HyperText Markup Language (HTML) files and stands at the very core of the World Wide Web. HTTP and HTML are closely linked; one defines connectivity, the other defines interface. HTTP is the transport or transfer protocol offering the base method by which all clients (meaning your Web browser program installed on your computer) and servers (the Web server hosting a Web site displayed in your browser) communicate with each other. HTML, on the other hand, is the base standard by which content is formatted and displayed effectively in Web pages in browsers. The communications protocol used to connect to Web servers on the Internet or on a local network (intranet). Its primary function is to establish a connection with the server and send HTML pages back to the user's browser. It is also used to download files from the server either to the browser or to any other requesting application that uses HTTP.
As the transport protocol, HTTP defines how information is formatted and transmitted, and what actions Web servers and browsers take in response to commands you send over the Internet. For example, when you enter a URL, or Uniform Resource Locator, in the "Location" or "Address" field of your browser, you are sending an HTTP command to the Web server (which hosts that URL or Web site), directing it to fetch and transmit the requested Web page with its various media embedded--text, graphics, audio, or video. The HTTP protocol uses the concept of reference provided by the Universal Resource Identifier as a Location (URL) or Name (URN). When a hyperlink is composed in HTML, the URL uses the general form http://host:port-number/path/file.html. In HTTP/0.9 and 1.0, the connection is closed after a single request/response pair. In HTTP/1.1 a keep-alive-mechanism was introduced, where a connection could be reused for more than one request. Such persistent connections reduce lag perceptibly, because the client does not need to re-negotiate the TCP connection after the first request has been sent.
HTTP is a "stateless" request/response system. The connection is maintained between client and server only for the immediate request, and the connection is closed. After the HTTP client establishes a TCP connection with the server and sends it a request command, the server sends back its response and closes the connection. The first version of HTTP caused considerable overhead. Each time a graphics file on the page was requested, a new protocol connection had to be established between the browser and the server. In HTTP Version 1.1, multiple files could be downloaded with the same connection. It also improved caching and made it easier to create virtual hosts (multiple Web sites on the same server). Methods PUT and DELETE are defined to be idempotent, meaning that multiple identical requests should have the same effect as a single request. Methods GET, HEAD, OPTIONS and TRACE, being prescribed as safe, should also be idempotent. HTTP is a stateless protocol.
By contrast, the POST method is not necessarily idempotent, and therefore sending an identical POST request multiple times may further affect state or cause further side effects (such as financial transactions). In some cases this may be desirable, but in other cases this could be due to an accident, such as when a user does not realize that their action will result in sending another request, or they did not receive adequate feedback that their first request was successful. While web browsers may show alert dialog boxes to warn users in some cases where reloading a page may re-submit a POST request, it is generally up to the web application to takes responsibility for handling cases where a POST request should not be submitted more than once. Note that whether a method is idempotent is not enforced by the protocol or web server. It is perfectly possible to write a web application in which (for example) a database insert or other non-idempotent action is triggered by a GET or other request. Ignoring this recommendation, however, may result in undesirable consequences if a user agent assumes that repeating the same request is safe when it isn't.
96. Enterprise Resource Planning (ERP)
The concept of ERP seems to have evaluated way back in the 1960, but its name – ERP was born around 1972. The ERP was the vision of a group of ex-IBM managers. They then formed a company, which today stands tall, SAP. Over the years ERP has undergone a lot of changes, yet the basic concept of integration remains the same. Taking one word at a time ERP will literally mean Enterprise – an undertaking, especially one with some scope, complication and risk. Resource – something that can be used as a support or help. Planning – A scheme program or method worked out beforehand for accomplishment of an objective. ERP software aids and controls the ERP management system, which is a system that integrates and automates all facets of business operations. This includes planning, manufacturing, and sales, while more recent ERP software products encompass marketing, inventory control, order tracking, customer service, finance and human resources as well.
Of the three words the word enterprise has more relevance with the other two trying to add importance. But ERP is always defined focusing on its role to integrate. ERP integrates the entire operations of any organization. In simple terminology ERP is software which can be used by both small and big organizations to integrate all its operations across departments. There was a time when ERP was a word of nightmares, when ERP was 'walking on landmines' and ERP was meant only for the 'big and the rich' companies. But today the benefits are understood, talked about. We have a number of small players entering into the ERP race. We have a number of ERP products to meet needs of even the SMEs we even have vertical ERPs.
In the absence of an ERP system, a large manufacturer may find itself with many software applications that neither talk to each other nor interface effectively. Tasks that need to interface with one another may involve: Integration among different functional areas to ensure proper communication, productivity and efficiency. Design engineering (how to best make the product). Order tracking, from acceptance through fulfillment. The revenue cycle, from invoice through cash receipt. Managing inter-dependencies of complex processes bill of materials. Tracking the three-way match between purchase orders (what was ordered), inventory receipts (what arrived), and costing (what the vendor invoiced). The accounting for all of these tasks: tracking the revenue, cost and profit at a granular level.
Some security features are included within an ERP system to protect against both outsider crime, such as industrial espionage, and insider crime, such as embezzlement. A data-tampering scenario, for example, might involve a disgruntled employee intentionally modifying prices to below-the-breakeven point in order to attempt to interfere with the company's profit or other sabotage. ERP systems typically provide functionality for implementing internal controls to prevent actions of this kind. ERP vendors are also moving toward better integration with other kinds of information security tools.
No matter which ERP system you ultimately choose, how do you know you're making the *right* choice for your company? No two manufacturers run exactly the same way, and similarly no two ERP systems run exactly the same way. So, it’s critical to research the product and the vendor to ensure that you select the right system for your business. You've got to have a system that fully integrates all aspects of running your manufacturing business, offers advanced features and options but is intuitive and easy to use, and adapts to the way you do business rather than forcing you to adapt to the software. With ERP, you’re buying more than just a software package. You’re engaging in a long-term relationship with a business partner that will have a huge impact on the future of your company. The more time you spend in the research process, the better your chances of selecting the best ERP product and the right partner for your business.
The concept of ERP seems to have evaluated way back in the 1960, but its name – ERP was born around 1972. The ERP was the vision of a group of ex-IBM managers. They then formed a company, which today stands tall, SAP. Over the years ERP has undergone a lot of changes, yet the basic concept of integration remains the same. Taking one word at a time ERP will literally mean Enterprise – an undertaking, especially one with some scope, complication and risk. Resource – something that can be used as a support or help. Planning – A scheme program or method worked out beforehand for accomplishment of an objective. ERP software aids and controls the ERP management system, which is a system that integrates and automates all facets of business operations. This includes planning, manufacturing, and sales, while more recent ERP software products encompass marketing, inventory control, order tracking, customer service, finance and human resources as well.
Of the three words the word enterprise has more relevance with the other two trying to add importance. But ERP is always defined focusing on its role to integrate. ERP integrates the entire operations of any organization. In simple terminology ERP is software which can be used by both small and big organizations to integrate all its operations across departments. There was a time when ERP was a word of nightmares, when ERP was 'walking on landmines' and ERP was meant only for the 'big and the rich' companies. But today the benefits are understood, talked about. We have a number of small players entering into the ERP race. We have a number of ERP products to meet needs of even the SMEs we even have vertical ERPs.
In the absence of an ERP system, a large manufacturer may find itself with many software applications that neither talk to each other nor interface effectively. Tasks that need to interface with one another may involve: Integration among different functional areas to ensure proper communication, productivity and efficiency. Design engineering (how to best make the product). Order tracking, from acceptance through fulfillment. The revenue cycle, from invoice through cash receipt. Managing inter-dependencies of complex processes bill of materials. Tracking the three-way match between purchase orders (what was ordered), inventory receipts (what arrived), and costing (what the vendor invoiced). The accounting for all of these tasks: tracking the revenue, cost and profit at a granular level.
Some security features are included within an ERP system to protect against both outsider crime, such as industrial espionage, and insider crime, such as embezzlement. A data-tampering scenario, for example, might involve a disgruntled employee intentionally modifying prices to below-the-breakeven point in order to attempt to interfere with the company's profit or other sabotage. ERP systems typically provide functionality for implementing internal controls to prevent actions of this kind. ERP vendors are also moving toward better integration with other kinds of information security tools.
No matter which ERP system you ultimately choose, how do you know you're making the *right* choice for your company? No two manufacturers run exactly the same way, and similarly no two ERP systems run exactly the same way. So, it’s critical to research the product and the vendor to ensure that you select the right system for your business. You've got to have a system that fully integrates all aspects of running your manufacturing business, offers advanced features and options but is intuitive and easy to use, and adapts to the way you do business rather than forcing you to adapt to the software. With ERP, you’re buying more than just a software package. You’re engaging in a long-term relationship with a business partner that will have a huge impact on the future of your company. The more time you spend in the research process, the better your chances of selecting the best ERP product and the right partner for your business.
95. Software Testing
Software testing is oriented to "detection". It's examining a system or an application under controlled conditions. It's intentionally making things go wrong when they should not and things happen when they should not. Software Testing is an empirical investigation conducted to provide stakeholders with information about the quality of the product or service under test, with respect to the context in which it is intended to operate. This includes, but is not limited to, the process of executing a program or application with the intent of finding software bugs. Testing involves operation of a system or application under controlled conditions and evaluating the results (eg, 'if the user is in interface A of the application while using hardware B, and does C, then D should happen'). The controlled conditions should include both normal and abnormal conditions. Testing should intentionally attempt to make things go wrong to determine if things happen when they shouldn't or things don't happen when they should. It is oriented to 'detection'.
Testing software is operating the software under controlled conditions, to (1) verify that it behaves “as specified”; (2) to detect errors, and (3) to validate that what has been specified is what the user actually wanted. Verification is the checking or testing of items, including software, for conformance and consistency by evaluating the results against pre-specified requirements. Error Detection: Testing should intentionally attempt to make things go wrong to determine if things happen when they shouldn’t or things don’t happen when they should. Validation looks at the system correctness – i.e. is the process of checking that what has been specified is what the user actually wanted. The purpose of inspection is trying to find defects and problems mostly in documents such as test plans, specifications, test cases, coding etc. It helps to find the problems and report it but not to fix it. It is one of the most cost effective methods of software quality. There might be different numbers of people can join the inspections but normally one moderator, one reader and one note taker are mandatory.
In other words, validation checks to see if we are building what the customer wants/needs, and verification checks to see if we are building that system correctly. Both verification and validation are necessary, but different components of any testing activity. The definition of testing according to the ANSI/IEEE 1059 standard is that testing is the process of analyzing a software item to detect the differences between existing and required conditions (that is defects/errors/bugs) and to evaluate the features of the software item. The purpose of testing is verification, validation and error detection in order to find problems – and the purpose of finding those problems is to get them fixed. Quality Assurance makes sure the project will be completed based on the previously agreed specifications, standards and functionality required without defects and possible problems. It monitors and tries to improve the development process from the beginning of the project to ensure this. It is oriented to "prevention".
A primary purpose for testing is to detect software failures so that defects may be uncovered and corrected. This is a non-trivial pursuit. Testing cannot establish that a product functions properly under all conditions but can only establish that it does not function properly under specific conditions. The scope of software testing often includes examination of code as well as execution of that code in various environments and conditions as well as examining the aspects of code: does it do what it is supposed to do and do what it needs to do. In the current culture of software development, a testing organization may be separate from the development team. There are various roles for testing team members. Information derived from software testing may be used to correct the process by which software is developed.
Software testing is oriented to "detection". It's examining a system or an application under controlled conditions. It's intentionally making things go wrong when they should not and things happen when they should not. Software Testing is an empirical investigation conducted to provide stakeholders with information about the quality of the product or service under test, with respect to the context in which it is intended to operate. This includes, but is not limited to, the process of executing a program or application with the intent of finding software bugs. Testing involves operation of a system or application under controlled conditions and evaluating the results (eg, 'if the user is in interface A of the application while using hardware B, and does C, then D should happen'). The controlled conditions should include both normal and abnormal conditions. Testing should intentionally attempt to make things go wrong to determine if things happen when they shouldn't or things don't happen when they should. It is oriented to 'detection'.
Testing software is operating the software under controlled conditions, to (1) verify that it behaves “as specified”; (2) to detect errors, and (3) to validate that what has been specified is what the user actually wanted. Verification is the checking or testing of items, including software, for conformance and consistency by evaluating the results against pre-specified requirements. Error Detection: Testing should intentionally attempt to make things go wrong to determine if things happen when they shouldn’t or things don’t happen when they should. Validation looks at the system correctness – i.e. is the process of checking that what has been specified is what the user actually wanted. The purpose of inspection is trying to find defects and problems mostly in documents such as test plans, specifications, test cases, coding etc. It helps to find the problems and report it but not to fix it. It is one of the most cost effective methods of software quality. There might be different numbers of people can join the inspections but normally one moderator, one reader and one note taker are mandatory.
In other words, validation checks to see if we are building what the customer wants/needs, and verification checks to see if we are building that system correctly. Both verification and validation are necessary, but different components of any testing activity. The definition of testing according to the ANSI/IEEE 1059 standard is that testing is the process of analyzing a software item to detect the differences between existing and required conditions (that is defects/errors/bugs) and to evaluate the features of the software item. The purpose of testing is verification, validation and error detection in order to find problems – and the purpose of finding those problems is to get them fixed. Quality Assurance makes sure the project will be completed based on the previously agreed specifications, standards and functionality required without defects and possible problems. It monitors and tries to improve the development process from the beginning of the project to ensure this. It is oriented to "prevention".
A primary purpose for testing is to detect software failures so that defects may be uncovered and corrected. This is a non-trivial pursuit. Testing cannot establish that a product functions properly under all conditions but can only establish that it does not function properly under specific conditions. The scope of software testing often includes examination of code as well as execution of that code in various environments and conditions as well as examining the aspects of code: does it do what it is supposed to do and do what it needs to do. In the current culture of software development, a testing organization may be separate from the development team. There are various roles for testing team members. Information derived from software testing may be used to correct the process by which software is developed.
94. Receptionist
A receptionist is a person in an office/administrative support position. The work is usually performed in a waiting area such as a lobby or front office desk of an organization or business. The title "receptionist" is attributed to the person who is specifically employed by an organization to greet any visitors, patients, or clients. A receptionist is usually expected to have a high school diploma or the equivalent, but a receptionist may also possess a vocational certificate/diploma in business and office administration. Although a post secondary degree is not normally required for this position, some receptionists may hold four year university degrees in a variety of majors. Some receptionists may even hold advanced degrees. A receptionist controls access to executives and other staff, answers questions, schedules appointments, and handles other interpersonal interactions. He or she is literally the face of the business.
Computer skills including proficiency with word processing, spreadsheet and database software including extensive Windows 2000 and Microsoft Office applications experience essential. Proven ability to be organized, detail oriented and accurate when working under deadlines. Excellent written and oral communication skills essential. Proven ability to maintain confidentiality when dealing with sensitive information. Past experience in settings where providing customer service was critical is important. Strong personal commitment to VEIC’s mission and values. Internal- Work is normally performed in climate controlled office environment, where exposure to conditions of extreme heat/cold, poor ventilation, fumes and gases is very limited. Noise level is moderate and includes sounds of normal office equipment (computers, telephones, etc.). No known environmental hazards are encountered in normal performance of job duties. External- Normal functions do not routinely require travel. Travel to special events and/or off site meetings required periodically.
While many persons working as receptionists continue in that position throughout their careers, some receptionists may advance to other administrative jobs such as customer service representative, dispatcher, interviewers, secretary, production assistant, personal assistant, Marketing and executive assistant. In smaller businesses, such as doctor's or lawyer's office, a receptionist may also be the office manager who is charged with a diversity of middle management level business operations. When receptionists leave the job, they often enter other career fields such as sales and marketing, public relations or other media occupations. The advancement of office automation has eliminated some receptionists' jobs. For example, a telephone call could be answered by an automated attendant. However, a receptionist who possesses strong office/technical skills and who is also adept in courtesy, tact and diplomacy is still considered an asset to a company's business image, and is still very much in demand in the business world.
In offices which only network with other businesses, as might be the case with a wholesaler, a receptionist is still a vital member of the team. He or she is expected to be a friendly face for companies which might want to do business, place orders, or cooperate on projects. The receptionist will manage schedules for the staff; make appointments, schedule meetings, and answer queries from other businesses in the course of a day's work. A good receptionist can be a difficult thing to find. Receptionists must be skilled at multitasking and remaining cheerful and courteous at all times, even when extremely frustrated. They must also be good at quickly reading people and their needs, determining, for example, whether someone should really be allowed to meet with a company executive. In addition to being good at managing the public, a receptionist has to be on top of the staff of the business that he or she works for, ensuring that people have the most current information about their schedules.
A receptionist is a person in an office/administrative support position. The work is usually performed in a waiting area such as a lobby or front office desk of an organization or business. The title "receptionist" is attributed to the person who is specifically employed by an organization to greet any visitors, patients, or clients. A receptionist is usually expected to have a high school diploma or the equivalent, but a receptionist may also possess a vocational certificate/diploma in business and office administration. Although a post secondary degree is not normally required for this position, some receptionists may hold four year university degrees in a variety of majors. Some receptionists may even hold advanced degrees. A receptionist controls access to executives and other staff, answers questions, schedules appointments, and handles other interpersonal interactions. He or she is literally the face of the business.
Computer skills including proficiency with word processing, spreadsheet and database software including extensive Windows 2000 and Microsoft Office applications experience essential. Proven ability to be organized, detail oriented and accurate when working under deadlines. Excellent written and oral communication skills essential. Proven ability to maintain confidentiality when dealing with sensitive information. Past experience in settings where providing customer service was critical is important. Strong personal commitment to VEIC’s mission and values. Internal- Work is normally performed in climate controlled office environment, where exposure to conditions of extreme heat/cold, poor ventilation, fumes and gases is very limited. Noise level is moderate and includes sounds of normal office equipment (computers, telephones, etc.). No known environmental hazards are encountered in normal performance of job duties. External- Normal functions do not routinely require travel. Travel to special events and/or off site meetings required periodically.
While many persons working as receptionists continue in that position throughout their careers, some receptionists may advance to other administrative jobs such as customer service representative, dispatcher, interviewers, secretary, production assistant, personal assistant, Marketing and executive assistant. In smaller businesses, such as doctor's or lawyer's office, a receptionist may also be the office manager who is charged with a diversity of middle management level business operations. When receptionists leave the job, they often enter other career fields such as sales and marketing, public relations or other media occupations. The advancement of office automation has eliminated some receptionists' jobs. For example, a telephone call could be answered by an automated attendant. However, a receptionist who possesses strong office/technical skills and who is also adept in courtesy, tact and diplomacy is still considered an asset to a company's business image, and is still very much in demand in the business world.
In offices which only network with other businesses, as might be the case with a wholesaler, a receptionist is still a vital member of the team. He or she is expected to be a friendly face for companies which might want to do business, place orders, or cooperate on projects. The receptionist will manage schedules for the staff; make appointments, schedule meetings, and answer queries from other businesses in the course of a day's work. A good receptionist can be a difficult thing to find. Receptionists must be skilled at multitasking and remaining cheerful and courteous at all times, even when extremely frustrated. They must also be good at quickly reading people and their needs, determining, for example, whether someone should really be allowed to meet with a company executive. In addition to being good at managing the public, a receptionist has to be on top of the staff of the business that he or she works for, ensuring that people have the most current information about their schedules.
Subscribe to:
Posts (Atom)
