HMR Essay Example | Topics and Well Written Essays - 1750 words

HMR - Essay Example Human resource management looks after all these activities. HRM can be considered as a process which involves four main duties. These include acquisition, motivation, development and overall maintenance of the human resource of an organisation. HRM can be considered as that branch of management which is responsible for maintaining relationships among the employees and the organisation. The nature of HRM varies widely and depends on its role in the organisation. HRM is an inherent part of an organisation. From broader perspective, this role is followed by almost all members of an organisation rather than only the department for personnel management. The function of human resource management is pervasive. It has to be performed by managers at all levels and it is not limited to only one department or group. It permeates to each and every department of an organisation regardless of the category and function. Major activities of this department include manpower planning, placement, emplo yment, compensation and appraisal and training of the employees. HRM is a continuous process which is present at every stage of the organisation. The fundamental objective of human resource management is contributing to the goals of the business and organisation. The department functions by ensuring efficient utilisation of the human resource and also increasing the potential of the people in the organisation so that they can fully utilise the resources of the organisation (Maloney). HRM functions can be categorised as managerial and operative functions. The managerial functions include planning, organising, controlling and directing. On the other hand, operative functions include activities such as procurement and development of function, providing compensation and benefits to them, record keeping and maintenance of good industrial relations. The structure of human resource management in UK is very strict. Most of the organisations in UK, have highly delegated HRM departments which looks after the organisation. As early as from the 1980s, the centre has effectively delegated the responsibility of HRM to various agencies and department. This suit has been followed by a majority of public sector organisations in the UK. Big organisations and most of the private sectors are now focussing on maintaining their own HRM department. Human resource management is most evident in the health care sector in UK while local authorities and smaller groups do not have any proper human resource management format. The basic difference between human resource and human resource management is that human resource consists of a group of individuals who constitute the workforce of a business, organisation or an economy; they are tangible assets of an organisation. On the other hand, human resource management includes management of these assets for the best utilisation of the resources of a business or organisation. Principles of Equal Opportunities Equal opportunity in employment ref ers to equal rights in the field of jobs, services and benefits to all individuals, employees and perspective employees in an organisation (Equal Opportunity). Equal employment opportunity is determined to provide equal and fair outcomes in almost all employment areas which include functions such as selection, recruitment, information access, management

Self-healing Operating Systems Essay Example for Free

Self-healing Operating Systems Essay The dependability of computer systems is one of the key issues in the technological era. Our daily lives are currently governed by complex computer systems (Haugk, Lax, Royer and Williams, 1985). Operating systems capable of managing key application on computer systems should be in a position to cope with the increasing rate of software problems, malicious attacks and hardware flaws (Parhami, 2005 and Lohr, 2001). One of the most significant requirements for operating systems is resilience to errors. Most of the operating systems stop operating once they encounter a problem with the hardware or software. This results to loss of applications and data running in the system. Some common examples of such issues are Windows blue screen errors and kernel panics in UNIX (David and Campbell, n. d). This is unfortunate since the main concern of the users is with the applications and data. They are afraid of losing data out of a fault that it not of their making. Even after a fault is encountered in the software or hardware, the users would want to have their data intact and recoverable. This problem has been taken care of by the invention of Self-healing operating systems. Self-healing operating systems refer to systems that automatically detect, diagnose and repair software and hardware problems that are localized. There are various techniques that are used by the operating system in recovery, once an error has been detected (Andrzejak, Geihs, Shehory and Wilkes, 2009). Code reloading Temporary memory errors or memory corruption as a result of an erroneous code can lead to errors like illogical instructions to the software code. Despite the fact that the ECC memory is capable of detecting and fixing some temporary memory faults, it is not capable of handling corruption faults that result from invalid instructions. The simplest most effective technique to handle such a problem is code reloading. This recovery technique reloads the flawed memory work from permanent memory. In case the fault is permanent, a case that can be identified through testing, there is a possibility of recovering through remapping of the faulty hardware page utilizing virtual memory support. In case the processing unit points to an undefined command exception, the command is reloaded by the handler from a copy of the system code in memory-mapped permanent memory and the command that is reloaded is executed. This recovery procedure is the simplest in implementation. However; the procedure is not capable of detecting memory corruption resulting from an opcode transforming into another legal opcode (David and Campbell, n. d). Regular checking of the operating system code is important to better detection of flaws in the memory. Hashing and checksums are simple methods of verifying of running system code. If a fault is detected a reload is triggered very fast. This is a preventive strategy that is capable of detecting flaws before they cause errors. The preventive strategy is also capable of detecting faults that make an opcode to result to another legitimate opcode (Demsky, and Rinard, 2002). CRC-32 checksum of critical kernel code is computed periodically by choices. This is makes sure that the memory where the instruction is stored has not been corrupted. In case the checksum changes as a result of corrupted memory, the block of the memory that is corrupted is reloaded from the permanent memory. Flushing of the instruction cache is carried out to ensure that all the affected commands are disposed of. The checksum can also be computed as soon as an operating system error is detected. This is done to make sure that the system and recovery code is not affected (Liedtke, 1995). Modern ARM-based processor designs consist of Run Time Integrity Checker (RTIC) hardware. This hardware is capable of being configured by the operating system for computation and verification of SHA-1 hashes of specific code areas. Once an error is identified, a communication is made to the processor via an interrupt. The same kind of checksum verification can be utilized in checking the integrity of fixed data. Checking the integrity of changing data is hard. One weakness of this recovery procedure is that it cannot be clearly used for codes that are created at run-time or for self-modifying code. This means that care must be taken to make sure that a replica of the created code is stored in a permanent memory (Shapiro, 2004). Component micro-rebooting This technique has been proven to be effective for application programs. Application of this technique to OS is also practicable (Voas and McGraw, 1998). The technique can help in recovery from temporary hardware flaws and some system bugs. For the Nooks project, this technique as extension restarts was utilized for recovery of the Linux Kernel. The technique involves reinitialising the corrupted part or destroying and recreating it and then re-requesting the component. While in code reloading errors are fixed only in processor commands, in this technique errors are fixed in kernel data structures. The technique works in collaboration with isolated components. The wrapper elements that offer isolation of the components are also utilised in the management of the recovery. The fault model that is addressed in micro-reboot is component-level flaw repression. This can be partly implemented by component isolation (Tanenbaum, Herder and Bos, 2006). Automatic service restarts In case crucial operating system service, like the paging daemon, stops working, it brings the entire system to a stop. Once the failure of such a crucial process is realised, a restart of the process can solve the problem and continue the operation of the operating system. The flaw model that is handled by automatic service restart is single-process failure. In this case there is usually no external state corruption. In micro-kernel OS, this basically involves detection and restarting of the affected system services that are run as application processes (David, Carlyle and Campbell, 2007). For instance, in Minix3, this operation is carried out by reincarnation server. A system process could be developed such that it is mechanically restarted once it encounters an exception. There is a particular system process that loops constantly awaiting a prepared process and acquiesces to the new process. This special system process is the process dispatcher. The system becomes completely useless once the process dispatcher crashes. This is the reason why in some systems the system dispatcher is executed as a restartable process that can be recovered once it crashes (Demsky and Rinard, n. d). Process restarts may fail to work where the process utilizes locks for accessing shared data structures. Such cases are common where the process dies while holding a single or more locks. Even in case the shared data structures are not affected or they can be corrected, recovery will not happen unless there is releasing of all the locks held by processes. This is why the system should be such that it can track all the locks help by processes and forcefully release any that is help once a process is halted. It is possible to implement lock tracking and force unlocking to ensure that the process runs once a fault has been identified and fixed (Tanenbaum, Herder and Bos, 2006). Watch-dog based recovery This technique utilises external hardware watchdog timers. They are utilised in error detection where the operating system is not doing any useful work. This is such a case where the OS is in an infinite loop. There is need for regular resetting of the timer by the operating systems. A signal is sent to the processor once the timer expires. The processor has a reset pin where the timers are usually cabled. They lead to a complete reboot of the system in case of failure. This process has a weakness for a complete reboot results to the loss of user data and applications that are currently in the volatile memory. However, since the memory is conserved after a process reset, reconstruction of both the operating systems and user state is possible. This makes it possible to continue operating after the reset. This way the user data is recovered resulting to higher reliability (Andrzejak, Geihs, Shehory and Wilkes, 2009). This technique has been successfully implemented in Linux and Choices. Once there is resetting of the memory management unit (MMU), interrupt subsystem, watchdog bites, and the processor, the system continues to operate effectively. To be able to avoid loosing the user data, the reset handler passes the usual boot procedure when the reset is instigated by the timer. The reset handler turns the memory management unit back on, there is deactivation of the running processes, reinitialising of the interrupts and skips to the OS’s process dispatch loop. After this the system runs the next ready process (Shapiro, 2004). All that is lost is the process state of the one that was running during the resetting of the processor. The process whose state is lost cannot be scheduled once more. As a result, it is eliminated from the process queue. A solution to the lock-up state is delivering of exception to the thread that is locked up. In this case, the thread is free to try local recovery rather than being forced to terminate. Watch-dog based recovery uses single process crash as a fault model without external state corruption. The technique utilises the lock tracking code in the release of pooled resources that are in a process that is terminated. Another kind of lockup that can initiate a watchdog timeout is a deadlock. Recovery in this case can be tried by restarting some parts so as to break cycles (Andrzejak, Geihs, Shehory and Wilkes, 2009). Transactional roll-back Once an error results to an exception during an operation, there could be a roll back of the state of the part. This can be achieved through the abortion of the operation. After abortion, the operation is then retried. In Choices, management of a transaction is carried out by the same wrapper elements that offer isolation. The transaction is aborted by the wrapper. Where there is unhandled exception, the state of the part is rolled back. It is also possible to use multi-threaded and non-blocking execution offered by RSTM for better performance (Brown and Patterson, 2001). Support of transactional model on parts results to expenses in terms of space and time. Expenses in terms of space are as a result of storage of backup copies of states prior to transactions. In terms of time, it is due to performance of memory copies and management of the memory during the set up and committing of a transaction (Marathe et al. 2006). Transactional roll-back differ from component micro-booting since the roll back is only on the current process, while the latter re-initialises the entire internal state of the process. Based on the kind of the component, either of the two techniques can be employed. Particularly, in case the component has crucial state information that can be lost if component micro-booting is used, then transactional roll-back can be utilised to retain the state. Component micro-booting is useful when the component can withstand state reinitialisation and has few overheads (Demsky and Rinard, n. d). Process-level recovery Where clear recovery cannot work, or in case the recovery process becomes erroneous, specific process states can be stored to permanent memory. This is carried out as the last option is all the others cannot work. Once the user states are stored, the system can attempt full reboot. The state of the processes can then be saved selectively into the computer. Every operating system state is reinitialised after the reboot probably removing fleeting errors. Process-level recovery ensures that user applications are not lost when the fault affects only a few system applications or immaterial operating system state. The technique can be used in collaboration with file system snapshots to make sure that the file integrity is not affected after the recovery process by going on to run erroneous processes. This procedure needs minimal support from the operating system. All it requires is an operational permanent memory drive and user process state management code. The stored processes can be restored selectively after the healing process (Ghosha, Sharman, Rao and Upadhyaya, 2007). Conclusion The reliability of computer systems is one of the key issues in the modern society. This is because computers have become central to our lives and we depend on them for many of our operations. A reliable computer system is one that can recover from a fault or an error effectively and without loss of either user applications or data. This is the reason why operating systems have been developed such that they are self-healing. This means that they can automatically detect, diagnose and repair software and hardware problems that are localized. The recovery techniques discussed on the paper include: Code reloading; Component micro-rebooting; Automatic service restarts; Watch-dog based recovery; Transactional roll-back; and Process-level recovery. Annotated Bibliography: Andrzejak, A. , Geihs, K. , Shehory, O. Wilkes, J. (2009). Self-Healing and Self-Adaptive Systems, Dagstuhl Seminar 09201, May 10-15, 2009. This paper presented in Dagstuhl Seminar tackles various aspects of self-healing and self-adaptive systems. Among the issues discussed in the paper include fault detection and diagnosis, recovery and repair techniques, frameworks and architectures for self-adaptive systems, self-healing solutions in IT infrastructures, and fault management for application systems. The discussion on recovery and repair techniques makes the paper an important resource for the project. Brown, A. , and Patterson, D. (2001). Embracing failure: A case for recovery-oriented computing (ROC). High Performance Transaction Processing Symposium, Asilomar, CA (October 2001). This paper is generally on recovery-oriented technology. Brown and Patterson discus various aspects related to recovery from faults and errors in computing. In their work, they have not left out the role of operating systems in recovery, which is the focus of this research. As a result, this paper provides very important information for the project. The authors are experts in data recovery and therefore the information provided is reliable in understanding recovery in computing. David, F. Campbell, R. (n. d). Building a Self-Healing Operating System, Urbana, IL: University of Illinois. This paper by David, F. Campbell, R. discusses the rationale behind development of Self-healing Operating Systems. They go further to discus the recovery techniques that ensure user applications and data in temporary storage are not lost when an operating system crashes. The techniques discussed include: Code reloading; Component micro-rebooting; Automatic service restarts; Watch-dog based recovery; Transactional roll-back; and Process-level recovery. This makes the paper an important resource for this project. David, F. Carlyle, J. Campbell, R. (2007). Exploring Recovery from Operating System Lockups. In USENIX Annual Technical Conference, Santa Clara, CA. In the recovery process, process restarts may be impossible where the process has locks. This mostly happens where the process terminates while holding a single or more locks. This resource provides crucial information on how to deal with these lock-ups for recovery to be effective. The paper introduces what lock-ups and how to handle them when using different recovery methods. This is what makes it important as an information source for this paper. Demsky, B. and Rinard, M. (2002). Automatic detection and repair of errors in data structures. Technical Report MIT-LCS-TR-875, MIT, Massachusetts Institute of Technology. This paper is on mechanical detection and repair of errors in computer systems. The idea of automatic detection and repair reveals the fact that the operation system is involved in the detection and recovery. The paper provides details on how the self-healing operating system detects and repairs errors in data structures. These are the techniques that are used for detection and recovery which are the main focus of the essay. Demsky, B. Rinard, M. (n. d). Automatic Data Structure Repair for SelfHealing Systems. Retrieved on August 3, 2010 from http://people. csail. mit. edu/rinard/paper/sms03. pdf The authors of this paper, Demsky, B. Rinard, M. talk about a system that they came up with that that accepts specifications of key data structure constraints, detects and repairs breaches of these constraints, making it possible for the program to recover from errors and continue working effectively. The paper offers the procedures that the authors use in detection and recovery of their system from the errors. This is what makes the paper significant for the research. Ghosha, D. , Sharman, R. , Rao, R. Upadhyaya, S. (2007). Self-healing systems: survey and synthesis, Decision Support Systems Volume 42, Issue 4. Ghosha, Sharman, Rao and Upadhyaya give a detailed analysis of Self-healing systems. Theirs is a contemporary software-based systems and applications analysis in a world where this has gained significance importance. They discus the ability of Self-healing systems in to manage conflicting resources and service different user needs. They go ahead to discus the need and how to discover and rectify system faults and recovery from errors. They have argued that these systems attempt to â€Å"heal† themselves by recovering from faults and regaining normal performance rates. Haugk, G. , Lax, F. , Royer, R. and Williams, J. (1985). The 5ESS(TM) switching system: Maintenance capabilities. ATT Technical Journal, 64(6 part2). This paper discusses maintenance capabilities of operating systems. It is a useful recourse for the essay that discusses self-healing of operating systems from an historic point of view. Computer systems have been affected by software bugs and hardware faults since the beginning. This article discusses how these bugs and faults that result to errors have been handled since the invention of computer hardware and software. Liedtke, J. (1995). On micro-kernel construction. In SOSP ’95: Proceedings of the fifteenth ACM symposium on Operating systems principles, New York: ACM Press. This book includes the proceedings of ACM symposium on Operating systems principles in 1995. The book contains a discussion of the component micro-rebooting that has been proven to be effective for application programs. The author also argues that the application of this technique to operating system is also practicable. For the Nooks project, this technique as extension restarts was utilized for recovery of the Linux Kernel. This book contains important information on component micro-rebooting as recovery technique for self-healing operating systems. Lohr, S. (2001). Go to: The Story of the Math Majors, Bridge Players, Engineers, Chess Wizards, Maverick Scientists, and Iconoclasts, the Programmers Who Created the Software Revolution. New York: Basic Books. This book provides important information on the evolution and working of software. The book offers reliable information on software management. Software bugs are some of the problems that cause errors on processes. The book offers a clear understanding of these bugs and ways of dealing with them. Marathe, V. et al. (2006). Lowering the Overhead of Software Transactional Memory. Technical Report TR 893, Computer Science Department, University of Rochester, Mar 2006. According to this paper, support of transactional model on parts results to overheads in terms of space and time. Expenses in terms of space are as a result of storage of backup copies of states prior to transactions. In terms of time, it is due to performance of memory copies and management of the memory during the set up and committing of a transaction. After providing this fact, the authors goes on to discuss ways of eliminating these overheads. Parhami, B. (2005). Computer Architecture: From Microprocessors to Supercomputers, New York: Oxford University Press. As the technology has been advancing, so are the changes and needs to have systems that are more reliable. This book has a section that discusses computer operations and it is the section that has significant information for the paper. Faults in computer hardware are as crucial in error detection and recovery as software. This makes the book important for the research. The research would not be complete without the understanding of computer hardware. Shapiro, M. ( 2004). Self-Healing in Modern Operating Systems. Retrieved on August 3, 2010 http://queue. acm. org/detail. cfm? id=1039537 Shapiro gives an introduction to the topic of self-healing operating systems by first discussing the role played by the operating system in a computer system. It is not possible to understand the concept of self-healing operating systems, without understanding operating systems in general. This is the strength of this article for this research. He goes on to discuss the self-healing system model, which leads to the self-healing operating systems, which is the center of this research. Tanenbaum, A. S. , Herder, J. N. and Bos, H. (2006). Can We Make Operating Systems Reliable and Secure? Computer, 39(5):44–51, The reliability of computer systems is one of the key issues in the modern society. This article provides the reasons why computer systems need to be made reliable and dependable. The authors go on to explain ways by which operating systems can be made more reliable in a computing environment prone to hardware faults and software bugs. This book is an important resource for the essay since it provides the solutions to the problem. Voas J. M. and McGraw G. (1998). Software Fault Injection. New York: Wiley, 1998. Software Fault Injection is a book that identifies the fact that software bugs can result to unreliability in computer systems. The book discusses ways in which these bugs and errors in computer systems can be identified and what should be done. The solution suggested by Voas J. M. and McGraw G. is related to the operating systems, leading us to what is referred to as self-healing Operating Systems. This section on how the system can solve the problems with the software is the one that offers important information for the research.

The Well Meadows Hospital Management System

The Well Meadows Hospital Management System This document describes an online management system for a small hospital named as wellmeadows. This system creates online data storage for all the information related to the proceedings of the hospital and hence making the information available as well as more reliable to the users. The information becomes easily accessible as well as more secure with the system being secured by user credentials. The hospitals current functionality is based on a register based system that involves the maintaining of every transaction, records of patients, doctors, nurses in huge files that are stored in hospitals store room. It is not only difficult to search for certain information but also very difficult to maintain historical data. The old files are prone to get damaged and it is very difficult to manage this huge collection of documents and keep it organized. The new system is based on a database management system that allows secure, easy and reliable storage of data and retrieval is also very easy. In the old system, a user needed to know in which register particular information is stored but in the new system a user has a graphical interface, where he can simply search for the information by doing some clicks and selecting the correct options (Liang 2010). The ease in accessing information not only improves the information management but also impacts the day to day activities of the hospital. It reduces the delay in information retrieval and the delay in providing necessary treatment to the patients as per their historic records is also reduced that will improve the efficiency and effectiveness of the treatment (Prokosch Dudeck 1995). Intended Audience and Reading Suggestions This document is meant for the users of the system i.e. the administrators and staff of the wellmeadows hospital. This document explains the system design and its usage and not meant for external users. This document not only guides the user how to operate the system but also tells how to use the system efficiently to match with requirements of the user and let him take the profit out of it. This document will also help the developers in the situation where modifications are required in the system. Project Scope The project currently is limited to the internal use of the hospital and is simply meant to store and provide useful information. The system doesnt generate any information or predictions of its own. The system will be helpful in better management of the hospital and will provide all the information in an organized manner. This project is not meant for users outside the hospital and will not allow any person outside the hospital to see the internal and personal information of the people connected to the system. The system will keep the information secure and will keep it limited to people with proper access only. Overall Description Product Perspective This product is a change of methodology for the hospitals and firstly, it will be implemented in the Wellmeadows hospital. There are several similar systems in other big hospitals but this system is designed to meet the cost and utility requirements of the small hospital. This product is an evolutionary product that will be improved in the future and more functionality will be added to it. Product Features The product is useful to the hospital in a number of ways as it provides following features to the hospital:- Easy, storage and retrieval of all patients information that not only helps to maintain track record but also helps the doctors as they can know the treatment history of the patients. Store the entire information about doctors that allow the hospital to decide, which patient will be treated by which doctor. This product not only helps in providing better treatment to the patients but also helps in building trust with patients. It also helps to know about the doctors, who are preferred by patients (Sumathi Esakkirajan 2007). Storage of staffs information that helps in smooth running of the hospital. Storage of all drugs used in the hospital and all drugs being prescribed to the patients that allows more control over the quality of drugs used. It also ensures uniformity among various doctors and to maintain the stock of drugs as per their requirements (Sumathi Esakkirajan 2007). User Classes and Characteristics The system will be used by internal users only and will be accessible to outside users in a limited form. Following are the users of the system: Hospital receptionists: The hospital receptionist will act as system administrators and will make all the entries in the system. They will have access to all the information in system and will take control of the normal proceedings of the hospital. Receptionists will register the patients, allocate staff to various wards, give appointments to patients and will maintain the central stock of medicines and drugs. Charge Nurses: The charge nurses will manipulate the information related to their specific ward and will be able to see all patients information in their ward and provide medication accordingly. They will also be able to see which staff is on duty in their ward and also will be able to see the stock of medicines in their ward. Consultants: The consultants will able to see the patients information and the list of appointments that have been allocated to them. The will be also able to see the wards in which they are assigned duties and will also be able to prescribe medicines to their patients. Patients: Patients will be able to see the appointments they have in the hospital and will be able to see the medicines that have been prescribed to them from the system. Operating Environment The system will be a web based system and can be accessed within and outside the hospital through a link over hospitals website. The users will login the system using a username and password that will be provided to them by the system administrator and the system will be independent of the operating system. Assumptions and Dependencies The system assumes that the information being added to the system is correct and authenticated. It is also assumed that the username and password will be kept secret and will not be shared with anyone. The users will be themselves responsible for losing passwords. This system doesnt include a mailing feature and hence the user should not lose their passwords in any case. The passwords will have to be reset by the database administrator only. System Flow A data flow diagram as its name suggests represents the flow of data in any system. There is a huge flow of data and information in any information system. This flow is analyzed with the help of data flow diagrams. Data flow diagrams can be used for visualization of data processing. On a DFD, data items flow from an external data source or an internal data store to an internal data store or an external data sink via an internal process (Calmet Pfalzgraf 1996). A data flow diagram is composed of several components: Entities: Entities are the sources of information in any system. These entities are the external sources of information in any system. It is very important to mention all the entities in a system. This ensures the proper flow of information in a system. These also act as external sinks for the system (Dennis, Wixom Roth 2006). Database or data store: A database stores the information in any system. These act as internal data sources for a system. It stores the information from one process and provides information to other processes. It also acts as internal sinks in the system. Processes: A process is a function performed by the system. Each process helps to access the information from database or an entity and provide the information back to the entity or database (Dennis, Wixom Roth 2006). The DFDs are represented in several levels. With increase in each level the details in the diagram also increased. Level-0 would contain minimum details, while level 1 would contain more details than level 0 and so on. This section explains flow of the system, how the system operates and its functionalities with the help of data flow diagrams. The level of details increases with each diagram. The system at the highest level is nothing but a hospital management system; the inner details are not specified in the data flow diagram level-0 (Johns 2002). Here is the zero level data flow diagram (DFD level: 0) The above diagram shows the four entities that will be involved in the system- patients, doctors, hospital staff and nurses. These are the four main sources of information in the system. As the system is broken down into several modules, these entities match up their desired roles (Johns 2002). This breakdown gives us the exact information about the operations performed by the system and the entities involved in each operation. (DFD level:1) In the DFD level -1, the system is divided into three major domains namely patient management system, stock management system and staff management system. Patient management system is related to patients that includes two types of patients- inpatients and outpatients. Inpatients are those, which get admitted in the hospital and stay there while the outpatients take appointments and visit the hospital at given date and time (Johns 2002). The second major section of the system is stock management system. In this, the requirements of the hospital are analyzed and accomplished such as clinical and non clinical requirements like drugs, bandages and other requirements. This part also maintains the division of these items among various wards and among various departments of the hospital. The third section of the system is about the staff allocation system that ensures that all staff is being assigned proper duties and each wards getting proper number of employees and nurses for its daily operations and also for emergency situations. It also ensures that the consultants are visiting the wards on time and each patient is getting proper attention. External Interface Requirements User Interfaces The user interface is simply a web interface, which is presented to the user through a web browser. This allows user to enter data and select from various drop down menus. These drop down menus show the content read from the database. By simply clicking to submit buttons, user can save data into database. The user interfaces will also implement checks for null values being entered into database (Galitz 2009). It displays the format for date values to be entered, but doesnt validate them. If there is any error in entering any values to the database, the system generates the error message and asks the user to retry. This helps the user to be ensured that the values have been entered and hence a consistency in the system is maintained (Galitz 2009). Hardware Interfaces As the system is a web based system, the website will be hosted on a central server machine with other machines getting access to it through the network. The other machines could be simple computers or especially dedicated machines that provide access only to the content. For our current implementation, we will rely on general desktop systems. Communications Interfaces The system uses HTTP (hypertext transfer protocol) for sending and receiving data over the internet (Groth, Skandier, Lammle Tedder 2005). When the system is used within the hospital, it is presented on same network hence its generally faster as the server is also located within the hospital, but outside the hospital the system is accessible via internet and hence a domain is needed to be registered with the DNS servers hosted at the ISP. Data Model This section explains the data model used for the system. The section begins with recognizing all the entities to be used in the system and their relationships and then converting those entities and relations to tables. These tables will be normalized to 3NF form. This section captures the cardinality and referential integrity rules needed to ensure that the data is of good quality for the users. The main aim of data models is to support the development of information systems by providing the definition and format of data. Entity-relationship model The E-R (entity-relationship) data model views the real world as a set of basic objects (entities) and relationships among these objects (Bai 2010). It is intended primarily for the DB design process by allowing the specification of an enterprise scheme. If the information system, being designed, is based on a database then the conceptual data model will later be mapped on to a logical data model, which in turn will be mapped on to a physical model during the physical design process (Bai 2010). The E-R diagram shows all objects involved in the system as entities and the function among them as relationships. Here is a description of entities used in our system:- Entity: An entity is nothing but an object that exists and is distinguishable from other objects. Entities could be concrete such as a person or it could be an abstract entity that is nothing but a concept (Stallings 2008). An entity could also be considered as a source of information for the system. There are following entities in well meadows:- Doctor or consultant (concrete) Change nurse (concrete) Patients (concrete) Wards (abstract) Drugs (concrete) Administrator (concrete) Staff (concrete) Qualification (abstract) Inpatient (concrete) Outpatient (concrete) Attributes: Attributes are unique qualities that can be possessed by both relationships and entities. Attributes are represented by ovals that are connected to the entity sets that possess them by a line. With the exception of weak entities, all entities have to a minimum amount of attributes. These make up the primary key of the entity (Stallings 2008). Following are the attributes of the various entities described above:- Doctor: id, name, address, telephone, duty shift, date of birth Change nurse: id, name, address, telephone, date of birth, ward allocated. Patients: id, name, address, telephone, date of birth Ward : ward_num, ward_name, location, in charge nurse, number of beds Drugs: id, name, type, dosage, methodology, price, stock Administrator:- username, password, name, address, telephone, date of birth Staff: id, name, address, telephone, date of birth, ward allocated. Qualification:- institution name, qualification name Inpatient:- id, name, address, telephone, date of birth, date of admit, expected stay, expected date of leaving, actual date of leaving Outpatient: id, name, address, telephone, date of birth, date of appointment, consultant name, location, time of appointment. Here is an entity relationship diagram for the given system:- (Entity Relationship Digram) The patients are categorized into inpatients and outpatients as explained above while the staff has two categories doctors and nurses. The remaining staff is covered under staff itself. Wards are there in the hospital that is controlled by the nurses while drugs are referred by the doctors and they are taken by the patients. Both the inpatients and outpatients are treated by the doctors, while inpatients have a separate relationship with wards that they are admitted to it. Database design and normalization Normalization can be defined as the process in which data is taken from problem and reduced to a set of relations through data integrity and elimination of data redundancy (Gunderloy Jorden 2008). Data integrity: The data in the database is consistent and satisfies the all integrity constraints. Data redundancy Data redundancy incurs if it is found in two different locations (direct redundancy). At the same time the calculation of data from other items (indirect redundancy) also creates redundancy (Oppel 2004). First normalized form: The multi valued attributes are removed that facilitate a single value at the intersection of each row and column in a table. Second Normal form: In second normal form, all the non key attributes must be dependent on complete primary key and not on a single part of primary key. Third normal form: In a third normal form, all the non keys are determined only by the primary keys (Oppel 2004). Boyce-Codd normal form: The anomalies have been removed that resulted from the functional dependancies (Gunderloy Jorden 2008). The normalized schemas of the tables used in our database are given below:- Drug drug_ID drug_name description dosage method Stock Reorder cost Patient patient_id First Name Last name Address telephone Date of birth Sex Marital status Date of registration Staff Staff_id First Name Last name Address telephone position Inpatient id Patient_id Ward number Bed number Date placed Expected Stay Expected Date of leaving Actual date of leaving Ward Ward number Name location extension Charge nurse id(staff.staff id) Outpatient id patient id Consultant id Date Time location Qualification id Staff_id Type Institution Completion date Weekly allocation Ward number Staff id shift date Prescription Patient_id drug_id Start Date Units per day End date Database implementation The database defined above needs to be implemented over a database system. We use a relational database management system as our designs are based on relational model. Considering the requirements of hospital that are not very large, we can use an open source, free of cost database management system named as MySQL. MySQL is a relational database management system (RDBMS) that runs as a server providing multi-user access to a number of databases. It works on most of the available operating systems and is generally the most popular choice for implementing small database applications. It also has a plug-in named as phpmyadmin that provides a GUI access to the database (Lambrix 2010). Here are the implementations of SQLs for the database:- phpMyAdmin SQL Dump version 3.2.4 http://www.phpmyadmin.net Host: localhost Generation Time: Dec 12, 2010 at 08:58 AM Server version: 5.1.41 PHP Version: 5.3.1 SET SQL_MODE=NO_AUTO_VALUE_ON_ZERO; /*!40101 SET @[emailprotected]@CHARACTER_SET_CLIENT */; /*!40101 SET @[emailprotected]@CHARACTER_SET_RESULTS */; /*!40101 SET @[emailprotected]@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8 */; Database: `hospital` Table structure for table `drug` CREATE TABLE IF NOT EXISTS `drug` ( `drug_num` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(100) NOT NULL, `description` varchar(100) NOT NULL, `dosage` varchar(100) NOT NULL, `method` varchar(100) NOT NULL, `stock` int(11) NOT NULL, `reorder` int(11) DEFAULT NULL, `cost` decimal(10,0) NOT NULL, PRIMARY KEY (`drug_num`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ; Dumping data for table `drug` Table structure for table `inpatient` CREATE TABLE IF NOT EXISTS `inpatient` ( `inpatient_id` int(11) NOT NULL AUTO_INCREMENT, `patient_id` int(11) NOT NULL, `expected_stay` int(11) NOT NULL, `date_placed` date NOT NULL, `date_leave` date DEFAULT NULL, `actual_leave` date DEFAULT NULL, `ward_num` int(11) NOT NULL, `bed_num` int(11) NOT NULL, `spouse_id` int(11) DEFAULT NULL, PRIMARY KEY (`inpatient_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ; Dumping data for table `inpatient` INSERT INTO `inpatient` (`inpatient_id`, `patient_id`, `expected_stay`, `date_placed`, `date_leave`, `actual_leave`, `ward_num`, `bed_num`, `spouse_id`) VALUES (1, 1, 5, 2010-08-12, 0000-00-00, 0000-00-00, 1, 45, 0); Table structure for table `outpatient` CREATE TABLE IF NOT EXISTS `outpatient` ( `appointment_num` int(11) NOT NULL AUTO_INCREMENT, `consultant_id` int(11) NOT NULL, `patient_id` int(11) NOT NULL, `date` date NOT NULL, `time` time NOT NULL, `location` varchar(100) NOT NULL, PRIMARY KEY (`appointment_num`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ; Dumping data for table `outpatient` Table structure for table `patient` CREATE TABLE IF NOT EXISTS `patient` ( `patient_id` int(11) NOT NULL AUTO_INCREMENT, `firstname` varchar(50) NOT NULL, `lastname` varchar(50) NOT NULL, `address` varchar(500) NOT NULL, `tel` varchar(20) NOT NULL, `dob` date NOT NULL, `sex` varchar(10) NOT NULL, `mar_status` varchar(20) NOT NULL, `reg_date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP, PRIMARY KEY (`patient_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=3 ; Dumping data for table `patient` INSERT INTO `patient` (`patient_id`, `firstname`, `lastname`, `address`, `tel`, `dob`, `sex`, `mar_status`, `reg_date`) VALUES (1, yash, yash, yash, 7799, 0000-00-00, Male, UnMarried, 2010-12-08 00:03:10); Table structure for table `prescription` CREATE TABLE IF NOT EXISTS `prescription` ( `prescription_id` int(11) NOT NULL AUTO_INCREMENT, `patent_id` int(11) NOT NULL, `drug_num` int(11) NOT NULL, `units per day` int(11) NOT NULL, `startdate` date NOT NULL, `enddate` date NOT NULL, PRIMARY KEY (`prescription_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ; Dumping data for table `prescription` Table structure for table `qualification` CREATE TABLE IF NOT EXISTS `qualification` ( `q_id` int(11) NOT NULL AUTO_INCREMENT, `staff_id` int(11) NOT NULL, `type` varchar(100) NOT NULL, `institution` varchar(100) NOT NULL, `date` date NOT NULL, PRIMARY KEY (`q_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ; Dumping data for table `qualification` Table structure for table `requets` CREATE TABLE IF NOT EXISTS `requets` ( `request_id` int(11) NOT NULL AUTO_INCREMENT, `ward_num` int(11) NOT NULL, `drug_num` int(11) NOT NULL, `quantity` int(11) NOT NULL, `date` date NOT NULL, `processed` int(11) NOT NULL DEFAULT 0, `process_date` date DEFAULT NULL, PRIMARY KEY (`request_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ; Dumping data for table `requets` Table structure for table `staff` CREATE TABLE IF NOT EXISTS `staff` ( `staff_id` int(11) NOT NULL AUTO_INCREMENT, `firstname` varchar(50) NOT NULL, `lastname` varchar(50) NOT NULL, `address` varchar(500) NOT NULL, `sex` varchar(10) NOT NULL, `dob` date NOT NULL, `tel` varchar(20) NOT NULL, `position` varchar(50) NOT NULL, PRIMARY KEY (`staff_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=4 ; Dumping data for table `staff` INSERT INTO `staff` (`staff_id`, `firstname`, `lastname`, `address`, `sex`, `dob`, `tel`, `position`) VALUES (1, abcd, pqrs, asasd, Male, 0000-00-00, 123123, Charge Nurse); Table structure for table `staffhier` CREATE TABLE IF NOT EXISTS `staffhier` ( `id` int(11) NOT NULL, `description` varchar(100) NOT NULL ) ENGINE=MyISAM DEFAULT CHARSET=latin1; Dumping data for table `staffhier` INSERT INTO `staffhier` (`id`, `description`) VALUES (1, consultant), (2, Charge Nurse), (3, physiotherapist), (4, nurse); Table structure for table `tblusers` CREATE TABLE IF NOT EXISTS `tblusers` ( `username` varchar(50) NOT NULL, `password` varchar(50) NOT NULL, `name` varchar(50) NOT NULL, `wrong_count` int(11) NOT NULL DEFAULT 0, PRIMARY KEY (`username`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1; Dumping data for table `tblusers` INSERT INTO `tblusers` (`username`, `password`, `name`, `wrong_count`) VALUES (admin, 123456, administrator, 1); Table structure for table `ward` CREATE TABLE IF NOT EXISTS `ward` ( `ward_num` int(11) NOT NULL AUTO_INCREMENT, `ward_name` varchar(50) NOT NULL, `location` varchar(100) NOT NULL, `ext` int(11) NOT NULL, `num_beds` int(11) NOT NULL, `nurse_id` int(11) NOT NULL, PRIMARY KEY (`ward_num`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ; Dumping data for table `ward` INSERT INTO `ward` (`ward_num`, `ward_name`, `location`, `ext`, `num_beds`, `nurse_id`) VALUES (1, ank, asasd, 6666, 3, 1); Table structure for table `weeklyallocation` CREATE TABLE IF NOT EXISTS `weeklyallocation` ( `allocation_id` int(11) NOT NULL AUTO_INCREMENT, `staff_id` int(11) NOT NULL, `ward_num` int(11) NOT NULL, `shift` varchar(50) NOT NULL, `startdate` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP, PRIMARY KEY (`allocation_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=4 ; Dumping data for table `weeklyallocation` INSERT INTO `weeklyallocation` (`allocation_id`, `staff_id`, `ward_num`, `shift`, `startdate`) VALUES (1, 1, 1, EARLY, 2010-12-07 18:52:40), (2, 1, 1, NIGHT, 2010-12-07 23:33:40), (3, 0, 1, , 2010-12-08 00:05:25); /*!40101 SET [emailprotected]_CHARACTER_SET_CLIENT */; /*!40101 SET [emailprotected]_CHARACTER_SET_RESULTS */; /*!40101 SET [emailprotected]_COLLATION_CONNECTION */; This script will create the database and will make few entries in the tables as well. The username and passwords are stored in a table named as tblUsers. The admin password is also stored in the same table. This is the dump of the database exported by using phpmyadmin. Same script can be executed using the tool or also can be imported using the import option in phpmyadmin (Lambrix 2010). This will setup the database and the application can now be configured. System implementation The software package we choose for this system is XAMPP. Xampp is a software package that is used for hosting websites and the combination of four software packages namely php, apache, mysql and phpmyadmin. Xampp is a simple program that can be run on any machine; it does not require any specific hardware. Xampp is free software and it is available for various operating systems such as Linux, Windows, Mac OS, and Solaris etc. The programs sets up a mysql server on the system as well as an apache web server on the machine. The package also configures php for the machine and also provides phpmyadmin for managing the mysql database (Newman Thomas 2008). Xampp provides a root directory named as htdocs that works for the web server. Xampp is the easiest way to host a website. Xampp is very easy to install and uninstall as compared to the separate installation and configuration of the services it provides. Xampp also includes support for filezilla, mercury etc. Developers Xampp is open source software developed by www.apachefriends.com. Apache friends were founded in 2002 by Oswald and Kay. Oswald is their webmaster, while Kay is the maintainer of apache for windows. Apache friends have Xampp as their only project (Newman Thomas 2008). There are no new projects till date. The software package is available through Sourceforge that hosted the download files on their website www.sourceforge.net and made this whole project possible. Benefits Xampp has several benefits that make web hosting easy. These are as below: It is available in many languages such as English, Dutch, Italian, French, Portuguese and Chinese etc. It makes database management very easy with support of phpmydmin. The sup

The HR Professional as Thinking Performer and Business Partner Essay ex

The HR Professional as Thinking Performer and Business Partner A lot has been written about the need for HR professional to be a â€Å"thinking performer† and a â€Å"business partner†. How can I demonstrate these two attributes within my own organisation? Let us begin by defining exactly what it is to be a â€Å"thinking performer† and â€Å"business partner†. Business Partner The very idea of being a strategic business partner was the subject of a CIPD (2004)1 survey which showed that 56% of those questioned aspired towards being considered a strategic partner. The fit of business partners into the organisation is as a combination of strategic HR and proactive HR. The same CIPD survey suggested that strategic partners are defined thus: a) Their current role profile for the HR function is perceived to be more strategic-proactive as opposed to operational-reactive b) They believe they have more involvement and influence in the business strategy process c) They are generally more positive about CEO and management perceptions of the HR function d) They spend greater time on strategy and less time on implementation of HR administration e) They place more emphasis on the HR competencies of strategic thinking, business knowledge and leadership abilities f) They perceive themselves as working for organisations in which HR performance outcomes are measured If we look at the above definitions, it appears that, a strategic business partner is combination of mind-set and the ability to spend more time on strategy. The HR Business Partner ensures that the best people solutions meet the strategic aims of the business. Ulrich defines the qualities of a HR business partner as follows: * Focus on outcomes and not process * Measure results * Help to resolve business problems * Be able to hold their own in discussion with business partners * Ensure that HR strategy is aligned with business strategy The change of HR’s role to business partner is well documented in HR publications and on HR websites. However, Lengnick Halls’ research of 1988 concluded â€Å"that there is little empirical evidence to suggest that strategic HR directly influences organisational performance or competitive advantage†. More recent research, Wright and Snell (1998) recently reviewed all of the studies attempting to demonstrate the fit b... ... advising of the internal processes that will affect delivery deadlines or payment terms. I would also recommend the development of an intranet to allow HR and business managers to get closer to employees by encouraging feedback on all aspects of employment. The intranet should be integrated with other systems to allow for easy use but any comments posted by employees should be anonymous to allow for honesty from employees. Indeed, Deloitte & Touche’s CEO and Managing Partner – John Connolly, believes that by surveying their employees on a regular basis, they have been enabled to understand what it is that drives their staff commitment to the firm. Engaging their staff is considered to be a key part of their HR strategy and to do this, they need to have a solid understanding of the issues that concern them. These are but some of the ways in which I would demonstrate my value in terms of being a business partner and thinking performer. It is my belief that all employees of our organisation should demonstrate both of these qualities in all aspects of their work to enable us to better deal with the unpredictable nature of our business, the market and our economy.

An Evaluation of the Work of Jan Svankmajer :: essays research papers

An Evaluation of the Work of Jan Svankmajer Jan Svankmajer is an animator like no other that I know of. Surrealist in style, his artistic work encompasses a broad range of mediums- film, sculpture, painting, graphic design, prose and poetry. His filmic work often involves a combination of animation, puppetry and live action- a challenging style for any filmmaker to use effectively. Svankmajer films are by trademark dark and macabre tales, told not for the sake of aesthetic or technique, but always to serve a very personal purpose, which I will talk about shortly. In this essay, I will deal mainly with the work that Svankmajer created as an animator. To put it in context, however, I will first give a rough overview of his background and the work for which he is best known. Svankmajer was born in Czechoslovakia in 1934. His parents were both artistically inclined; his father was a window dresser while his mother was a dressmaker. After studying puppet theatre for four years in Prague, Svankmajer began his career as a director, designer and puppeteer at the State Puppet Theatre in Liberec. During the Early 1960s he collaborated with several different theatre companies in Prague to stage a variety of plays. In 1964 his interests turned to filmmaking. In this medium he felt that more would be possible technically, and that his work would reach a wider audience. After creating various award-winning short films like The Last Trick, his work underwent a decisive transition from Mannerism to Surrealism in 1968. As a surrealist Svankmajer would create many highly acclaimed films involving animation and live action. Svankmajer’s work became surrounded by political controversy with the making of the film Antonio’s Diary (1972). The film was not intended to have political meaning, but the Czech authorities banned him from making films for seven years simply because it contained unauthorised footage depicting everyday Czech life. Dimensions of Dialogue (1982) became his best-known short, and won several international awards. Like Antonio’s Diary, however, it was banned in Czechoslovakia, and was also shown to the ideology commission of the Central Committee of the Czechoslovak Communist Party as an example of the kind of film that should not be made. Alice (1985-87), based on the book by Lewis Carol, was Svankmajer’s first feature film, and his first to reach an American audience. Since then he has made two more feature-length films: Faust (1993) and Conspirators of Pleasure (1996).

Revengeful Justice in William Shakespeares Hamlet :: William Shakespeare Hamlet Revenge Essays

Revengeful Justice in William Shakespeare's Hamlet   Ã‚  Ã‚  Ã‚  Ã‚  Hamlet's motives rally between those of both revenge and justice, and it becomes this internal conflict which sets the pace of events throughout Shakespeare's entire play. Revenge serves Hamlet as his initial goal in the pursuit for vindication of his father's death. Soliloquy later reveals Hamlet's torn sensibility and care for justice, which decelerates his ability to proceed in action against Claudius. Not until Hamlet confronts his own procrastination, does the inaction cease. Hamlet defeats his inner struggle by melding opposing forces and internally justifying revenge.   Ã‚  Ã‚  Ã‚  Ã‚  Hamlet does not initially have a strong enough will to act solely on revenge. Even though Hamlet had proclaimed that he would be "swift" and "sweep to my revenge,"In the "rogue and peasant slave" soliloquy, Hamlet admits that he has been "unpregnant of my cause" and wonders whether he is a "coward". Not until Hamlet becomes completely fed up with his own inaction, does he finally examine the guilt of Claudius. However this task is thwarted when Hamlet witnesses Claudius praying. His will is rationalized by the notion that Claudius' soul might escape eternal damnation. Hamlet finally address his "dull revenge" in his climactic soliloquy admitting," I do not know/ Why yet I live to say This thing's to do/ Sith I have cause and will and strength and means/ To do't" Here Hamlet finally swears against his previous inaction "O! From this time forth,/ My thoughts be bloody or be nothing worth"   Ã‚  Ã‚  Ã‚  Ã‚  Hamlet's overly intellectual mind inhibits him from taking decisive action and he concedes this in two very important soliloquies . First in the "To be or not to be" soliloquy, Hamlet concludes, "Thus conscience does make cowards of us all/ And thus the native hue of resolution Is sicklied over with the pale cast of thought" While being exiled to England, hamlet thinks his procrastination is a result of " some craven scruple/ Of thinking too precisely on the event" His insightful mind examines his problems to such an extent that it creates dilemmas rather than solving them.

Emotionism religion Essay

I call my invented religion Emotionism. My religion will be based mainly on the belief that emotions are a manifestation of one’s faith. It will have the historical drama that is found in Roman Catholicism in that it will deliver faith by rooting this in accounts of people in the past who have been in contact with the founder of the faith. These accounts will be the foundation of my religion because they will fortify the faith by validating the love and compassion that one Jesus Christ had for His people. However, it will have none of the ritualistic practices of Catholicism because all these make it difficult to worship using the heart; instead, they focus on worship with the mind and the body. In the manner of adoration and worship, my religion will follow the ways of Buddhism and will focus on meditation and contemplation. Emotionism will seek to establish the beauty of worship using states of the mind and the heart. It will encourage journeys into one’s consciousness and discoveries into one’s self; and so, like Buddhism, will value man’s intelligence and encourage it to flourish. Emotionism, like Buddhism, will base its practices on the philosophies of transcendentalism so that each Emotionist will seek to rise beyond one’s current level. Emotionists will encourage links between the heart and the elements, between the mind and nature, and the spirit and the universe. My invented religion will promote harmony instead of division, which, although addressed by Catholicism through ecumenism, still exists among the many Christian sects. Emotionism will recognize the universality of things like Hinduism does. It will also adapt the religious passion of Hindus who believe that emotions are a potent force in altering one’s state of being. One other aspect of Hinduism that Emotionism will take into its folds is seeing beyond the physical self and recognizing the connection one human has with another in terms of the spirit – that each spirit comes from a single source and that all spirits are linked together by one common thread. Emotionism will also promote religious zeal the way Muslims do. The religious fervor and faithfulness of Muslims transcend barriers of time and space. Muslims live their faith and this is the kind of quality that I would like Emotionism to have. Emotionists will seek to defend themselves the way they defend their faith and vice versa, something Muslims are known for. Emotionism will therefore have the historical foundations of Catholicism, the adoration methods and philosophical precepts of Buddhism, the passion and recognition for emotions of Hinduism and the religious fervor of Islam. These elements of the various religions that I would like to combine would make for an almost perfect religion so that all the undesirable elements of each religion are discarded and only the desirable aspects adapted. While it is perhaps impossible that such a religion could exist, it is an exercise in intellect to know that religion can in fact be a conglomeration of beliefs and elements emanating from various other, more ancient practices and cultures. I envision my religion to be all encompassing so that no rules and laws determine who can join my religion. The most important aspect of my religion is the fact that it will attempt to unite all those divided by the eccentricities of religion, especially Christians and Muslims. It will seek to propagate understanding and the reality that even with different religions, all the peoples of the world actually just subscribe to a singular concept, and that is the concept of love and compassion.