A Ticket Booking System For Theatre

A Ticket Booking System For Theatre The purpose of the online ticket booking system is to provide another way for purchasing cinema tickets in advance. It is an automatic system. This paper presents a formal use of the Object Oriented analysis and Design, we will illustrate our system by providing Use Case Diagrams with Specifications, Activity Diagrams, Class Diagrams, Sequence Diagrams, State Machines and Communication Diagrams on the functionalities of the system, also we will provide some process description and data dictionary. The goals of our system are: Record performance details Record customer details Record tickets sold Print tickets Print address labels for telephone booking Task 1: Functional Modelling Identification of Actors Use Cases Analyzing the existing system we figured out that, there are two main scopes to be covered in the system. The scopes are Performance Planning and Ticket Booking. We used the below table to identify the Actors and the Use Cases for the system. User Role Use Case Theatre Manager Performance planning Define the type of the performance and name it. Performance scheduling Define date and time of the performance. Artist booking Book an artist for the performance. Ticket pricing Determine a price for the ticket. Clerk Check schedule Check the performance schedule for a particular show on a date. Check seat availability Checks for available seats Capture customer information Record customer details Check ticket price Check for ticket price for particular show. Sell ticket Record tickets sold. Print ticket Print ticket for the customer. Print address label Print address label for telephone booking. Use Case Diagram Following diagram shows the overall view of the Ticket Booking System for Theatre. Figure 1: Use Case Diagram (Performance Planning Ticket Booking) Use Case Specification Table 1: Use Case of Performance Planning Number: UC01 Req. Doc Ref: Name: Performance Planning Status: Actors: Theatre Manager Pre-requisites: User should be logged in the system. Goal: Defining the performance type and naming it. Use Case Relationships: Extend:UC02, UC03 Include: Association: Generalization: Description: Index Actor Event 1 User enters the name of the performance. 2 User enters the type of the performance. 3 System checks for all required data entry. 4 System connects to the database. 5 System writes data into the database. 6 System shows a confirmation message after successful database writes. Alternatives: Index Actor Event A 3.1 Enter required information. A 4.1 Check network connectivity A 4.2 Check database connectivity A 4.3 Check database user role A 5.1 Theatre manager gets notification of unsuccessful operation. Table 2: Use Case of Performance Scheduling Number: UC02 Req. Doc Ref: Name: Performance Scheduling Status: Actors: Theatre Manager Pre-requisites: User should be logged in the system. Performance planning (UC01) should be inserted into the system. Goal: Define date and time of the performance. Use Case Relationships: Extend: Include: Association: Generalization: Description: Index Actor Event 1 User selects the desired performance from the system. 2 User enters the date of the performance. 3 User enters the time of the performance. 4 System checks for all required data entry. 5 System connects to the database. 6 System writes data into the database. 7 System shows a confirmation message after successful database writes. Alternatives: Index Actor Event A 3.1 Enter required information. A 5.1 Check network connectivity A 5.2 Check database connectivity A 5.3 Check database user role A 6.1 Theatre manager gets notification of unsuccessful operation. Table 3: Use Case of Artist Booking Number: UC03 Req. Doc Ref: Name: Artist Booking Status: Actors: Theatre Manager Pre-requisites: User should be logged in the system. Performance planning (UC01) should be inserted into the system. Goal: Book an artist for the performance. Use Case Relationships: Extend: Include: Association: Generalization: Description: Index Actor Event 1 User selects the desired performance from the system. 2 User enters the name of the desired artist. 3 System checks for all required data entry. 4 System connects to the database. 5 System writes data into the database. 6 System shows a confirmation message after successful database writes. Alternatives: Index Actor Event A 3.1 Enter required information. A 4.1 Check network connectivity A 4.2 Check database connectivity A 4.3 Check database user role A 5.1 Theatre manager gets notification of unsuccessful operation. Table 5: Use Case of Schedule Checking Number: UC04 Req. Doc Ref: Name: Schedule Checking Status: Actors: Clerk Pre-requisites: User should be logged in the system. Performance scheduling (UC02) should be inserted into the system. Goal: Check the performance schedule for a particular show on a date. Use Case Relationships: Extend: UC01 Include: Association: Generalization: Description: Index Actor Event 1 User selects a desired performance and a date. 2 System shows a confirmation message for the availability of the performance. 3 System allows the user to perform the next event (UC06). Alternatives: Index Actor Event A 1.1 System notifies the user that the performance is unavailable on the desired date. Table 6: Use Case of Check Seat Availability Number: UC05 Req. Doc Ref: Name: Check Seat Availability Status: Actors: Clerk Pre-requisites: User should be logged in the system. Schedule checking (UC05) should be performed by the user. Goal: Checks for available seats. Use Case Relationships: Extend: Include: Association: Generalization: Description: Index Actor Event 1 User selects a desired performance and a date. 2 System shows a confirmation message for the availability of the seat. 3 System allows the user to perform the next event (UC07). Alternatives: Index Actor Event A 1.1 System notifies the user that the seat is unavailable for the desired performance. Table 7: Use Case of Capturing Customer Information Number: UC06 Req. Doc Ref: Name: Capture Customer Information Status: Actors: Clerk Pre-requisites: User should be logged in the system. Seat checking (UC06) should be performed by the user. Goal: Record customer details. Use Case Relationships: Extend: Include: Association: Generalization: Description: Index Actor Event 1 User enters the name, address and telephone number of the customer. 2 System checks for all required data entry. 3 System connects to the database. 4 System writes data into the database. 5 System shows a confirmation message after successful database writes. Alternatives: Index Actor Event A 2.1 Enter required information. A 3.1 Check network connectivity A 3.2 Check database connectivity A 3.3 Check database user role A 4.1 User gets notification of unsuccessful operation. Table 8: Use Case of Checking Ticket Price Number: UC07 Req. Doc Ref: Name: Check Ticket Price Status: Actors: Clerk Pre-requisites: User should be logged in the system. Ticket pricing information (UC04) should be entered into the system. Goal: Check for ticket price for particular show Use Case Relationships: Extend: UC01 Include: Association: Generalization: Description: Index Actor Event 1 User selects a desired performance form the system. 2 System shows the defined pricing for the ticket. Alternatives: Index Actor Event A 2.1 Price not found is notified to the user. Table 9: Use Case of Selling Ticket Number: UC08 Req. Doc Ref: Name: Selling Ticket Status: Actors: Clerk Pre-requisites: User should be logged in the system. Check ticket price (UC08) should be performed by the user. Goal: Record tickets sold. Use Case Relationships: Extend: Include: Association: Generalization: Description: Index Actor Event 1 User selects the desired performance from the system. 2 User enters ticket selling date and the ticket price for the desired performance. 3 System checks for all required data entry. 4 System connects to the database. 5 System writes data into the database. 6 System shows a confirmation message after successful database writes. Alternatives: Index Actor Event A 3.1 Enter required information. A 4.1 Check network connectivity A 4.2 Check database connectivity A 4.3 Check database user role A 5.1 Theatre manager gets notification of unsuccessful operation. Table 10: Use Case of Printing Ticket Number: UC09 Req. Doc Ref: Name: Printing Ticket Status: Actors: Clerk Pre-requisites: User should be logged in the system. Check ticket price (UC08) should be performed by the user. Goal: Print ticket for the customer Use Case Relationships: Extend: Include: Association: Generalization: Description: Index Actor Event 1 User triggers the print command for the sold ticket. Alternatives: Index Actor Event A 1.1 Printer not found notification will be given to the user. Table 11: Use Case of Checking Ticket Booking Type Number: UC10 Req. Doc Ref: Name: Check Ticket Booking Type Status: Actors: Clerk Pre-requisites: User should be logged in the system. Print ticket (UC10) should be performed by the user. Goal: Determine the ticket booking type. Use Case Relationships: Extend: Include: Association: Generalization: Description: Index Actor Event 1 User selects the booking type to identify whether the ticket was booked over phone. Alternatives: Index Actor Event Table 12: Use Case of Printing Address Label Number: UC11 Req. Doc Ref: Name: Print Address Label Status: Actors: Clerk Pre-requisites: User should be logged in the system. Ticket booking type (UC11) should be performed by the user. Goal: Print address label for telephone booking Use Case Relationships: Extend: UC11 Include: Association: Generalization: Description: Index Actor Event 1 User triggers the print command to print the address label. Alternatives: Index Actor Event Activity Diagram Based on the system observation, a high level activity diagram is drawn modelling the process of ticket booking for theatre. The activity diagram will bring everybody on a common ground for understanding the system functionalities. Figure 2: Activity Diagram (Performance Planning Ticket Booking) Task 2: Structural Modelling Class Diagram (attributes operations) The following diagram depicts the relationships between the classes for Ticket Booking System along with the attributes and the operations. Figure 3: Class Diagram (Performance Planning Ticket Booking) Task 3: Behavioural Modelling Sequence Diagram The following diagram is a sequence diagram for buying ticket. There are few things I want to state, that this is just one of the sequences of buying ticket. There could be more alternative sequence for buying ticket. For example, we can choice a performance before buying ticket. But the overall structures of all buying ticket sequence are similar, so, others sequence will not be shown. Figure 4: Sequence Diagram (Performance Planning Ticket Booking) State Machine Diagram Below diagram is used to give an abstract description of the behaviour of the ticket booking system. This behaviour is analyzed and represented in series of events that could occur in one or more possible states. Hereby each diagram usually represents objects of a single class and tracks the different states of its objects through the system. Figure 5: State Machine Diagram (Performance Planning Ticket Booking) Communication Diagram Communication diagram is similar to sequence diagrams, but it provides an overview of the relationships between objects, rather than focusing on the order of messages between objects, as the software executes. Figure 6: Communication Diagram (Performance Planning Ticket Booking) Task 4: Data Protection Law Introduction In Bangladesh Cyber Acts are in a process to be implemented. The Government of Bangladesh has formed National Council for Science and Technology (NCST). The Executive Committee for NCST has also been formed to implement policies formulated by the Council. Currently NCST is working with the general boundaries to protect the ICT industry and specific laws are yet to be decided. For our application we can follow the acts and regulations from UK. Laws, Regulations and Best Practices The Data Protection Act gives individuals the right to know what information is held about them. It provides a framework to ensure that personal information is handled properly. The Act works in two ways. Firstly, it states that anyone who processes personal information must comply with eight principles, which make sure that personal information is: Fairly and lawfully processed Processed for limited purposes Adequate, relevant and not excessive Accurate and up to date Not kept for longer than is necessary Processed in line with your rights Secure Not transferred to other countries without adequate protection The second area covered by the Act provides individuals with important rights, including the right to find out what personal information is held on computer and most paper records. Data protection laws should be adequate enough to maintain the below options at a minimum- How to access information This allows one to find out what information is held about him/her on a computer and within some manual records, such as medical records, files held by public bodies and financial information held by credit reference agencies. Correcting information This allows one to apply to a court to order a data controller to correct, block, remove or destroy personal details if they are inaccurate or contain expressions of opinion based on inaccurate information. Preventing processing of information This means one can ask a data controller not to process information about him/her that causes substantial unwarranted damage or distress. The data controller is not always bound to act on the request. Preventing unsolicited marketing This means a data controller is required not to process information about one for direct marketing purposes if he/she asks them not to. Preventing automated decision making This means one can object to decisions made only by automatic means. For example, where there is no human involvement. Claiming compensation This allows one to claim compensation through the courts from a data controller for damage, and in some cases distress, caused by any breach of the act. Exempt information This allows one to ask the information commissioner to investigate and assess whether the data controller has breached the act. There should be a committee (in our case NCTS could be the choice) that will have legal powers to ensure that organizations comply with the requirements of the data protection laws. It is notable here that these powers are focused on ensuring that organizations meet the obligations of the act. To promote best practices the regulation- The committee should carry out consensual audits with data controllers to assess their processing of personal information. The committee should see auditing as a constructive process with real benefits for data controllers. The committee should adopt, wherever possible, a participative approach including working closely with the data controller to agree the timing and scope of the audit. Comply with Data Protection Law A short checklist can help us to comply with the data protection laws in our system. Maintaining all the items in the checklist does guarantee compliance but it should mean that we are heading in the right direction. We should store only the related information about the customer and the personnelà ¢Ãƒ ¢Ã¢â‚¬Å¡Ã‚ ¬Ãƒ ¢Ã¢â‚¬Å¾Ã‚ ¢s involved with the system. And we need to make sure that we know what we are going to do with the information. The person should know, what are the information we are holding. He/she should understand what it will be used for. Information should be held securely whether ità ¢Ãƒ ¢Ã¢â‚¬Å¡Ã‚ ¬Ãƒ ¢Ã¢â‚¬Å¾Ã‚ ¢s on the paper or on computer. The system should prevent any unwanted access of its resources. The information should be deleted as soon as there is no need for it. Access control list should be created with a strict need to know to prevent data access from all kind of users of the system. We should train the stuff in their duties and responsibilities under the act that we are putting them in to practice. Recommendations Being a strategic regulator means that, in so far as we have a choice, we have to be selective with our interventions. We will therefore apply our limited resources in ways that deliver the maximum return in terms of a sustained reduction in data protection risk. That is the risk of harm through improper use of personal information. There are priorities we have to set. We need to focus most attention on situations where there is a real likelihood of serious harm. We also need to focus on situations where our intervention is most likely to make a long term as well as a short term difference. When we intervene we must do so in a way that gives us the best possible return and remember that we will often be at our most effective when working closely with others. We are entitled to have legitimate expectations of those who are in a position to influence data protection risk. Our effectiveness depends on them seeking and welcoming our reasonable interventions. Furthermore we have an important international role. Data protection risk in the Bangladesh is increasingly influenced by events worldwide. Our risk-based approach is in line with good regulatory practice. It does not mean that we seek to remove all data protection risk. We do what we can to moderate the most serious risks and protect those who are most vulnerable to improper use of their information. But we will not try to take away freedom of choice and will remember that individuals themselves ought to be best placed to make decisions about their own interests. Part of our job is to equip individuals with the knowledge and tools to enable them to make their own well-informed decisions about the use and disclosure of their personal information. Being a strategic regulator also means extending our approach beyond simply improving (through guidance, persuasion and regulatory action) the behaviour of organisations that handle personal information. We also have a legitimate role in informing and influencing the market or political environment in which they operate. Thus we will seek to have long term influence over government and the legislature at Westminster and in the devolved administrations as well as over representative bodies and other stakeholders, to ensure privacy friendly outcomes. We will also seek to influence the legal framework that governs our own work to ensure that data protection requirements are simple, meaningful and proportionate and that we have the flexibility and tools to regulate effectively. Building public confidence in data protection is the key in our approach. We protect people, not just information. This means we need to engage with the public and explain what we do in a way that they can easily understand and relate to. This commitment is at the heart of how we approach our job as data protection regulator and will inform all our data protection tasks including complaints handling and the provision of advice. Task 5: Ticket Printing Produce Tickets To protect the tickets from being forged or copied we can use a barcode on each ticket. Weà ¢Ãƒ ¢Ã¢â‚¬Å¡Ã‚ ¬Ãƒ ¢Ã¢â‚¬Å¾Ã‚ ¢ll print a unique 10-digit number as a barcode on the tickets, which will be checked at the entrance with the software and a simple barcode scanner. As each barcode can only be used once to enter, copied or forged tickets are rejected and the revenues are protected. By default, the tickets will be labeled with random numbers with 10 digits, which will serve as copy protection. Figure 7: Sample barcode to print on tickets Seat Allocation Tickets will be printed with seat numbers, with serial numbers. Section names can be in different colours to facilitate orientation. For sections with an aisle a seat description can be added to the seat number (e.g. left, right), which helps the visitor to find the seat. Figure 8: Sample barcode to print on ticket with seat no. Hardware for printing tickets There are numerous tickets available in the market but I found D-Link printers suitable for our system. Below are the details of the hardware- Description: With the DSA-3100 and the DSA-3100P Ticket Printer, businesses and organizations can provide free or fee-based broadband Internet access to their customers or members. No complex billing system is required, guaranteeing a quick and convenient Internet experience for operators and their hot spot users. The DSA-3100P is hassle-free hot spot ticket printer that communicates with the DSA-3100 Public/Private Gateway to generate and print log-in usernames and passwords for the hot spot customers. Patented for easy loading, the DSA-3100P is connected to the DSA-3100 gateway via its RS-232 serial communication. With the DSA-3100P, the DSA-3100 gateway can manage and store up to 2,000 user accounts in its internal database and support up to 50 logged-in users at any time. Features: Printing Method: Thermal Dot Line Printing Print Speed: 80 mm/Second Connectivity: RS-232 Serial Compatibility: D-Link DSA-3100 Public/Private Gateway Specification: Manufacturer D-Link Manufacturer Part # DSA-3100P Device Type Thermal Line Label Printer Media Handling Media Type Receipt Paper Max Media Size 2.2 Max Printing Width 1.9 Roll Maximum Outer Diameter 3.3 Total Capacity 1 Roll Connectivity Interfaces 1 x RS-232 Serial Included Cables 1 x Serial Cable Power Requirements Power Supply External, 3.5 V DC Dimensions(H X W X D) Unit 4.6 x 3.8 x 6.3 Weight Unit 0.9 lbs Price: $375 Figure 9: D-Link DSA-3100P Ticket Printer Task 6: Database Design Database Design Figure 10: Database Design (Performance Planning Ticket Booking) Data Dictionary Table: Artist Attribute Data Type Length Primary Key Ref. Table ArtistID Integer Yes ArtistName Varchar 100 Table: Performance Attribute Data Type Length Primary Key Ref. Table PerformanceID Integer Yes PerformanceName Varchar 100 TicketPriceID Integer TicketPrice ArtistID Integer Artist Table: TicketPrice Attribute Data Type Length Primary Key Ref. Table TicketPriceID Integer Yes PerformanceID Integer Performance TicketPrice Numeric (18,2) Table: PerformanceSchedule Attribute Data Type Length Primary Key Ref. Table ScheduleID Integer Yes PerformanceID Integer Performance PerformanceDate Date Table: Customer Attribute Data Type Length Primary Key Ref. Table CustomerID Integer Yes Name Varchar 100 Address Varchar 250 Telephone Varchar 20 Table: Sales Attribute Data Type Length Primary Key Ref. Table SalesID Integer Yes PerformanceID Integer Performance ScheduleID Integer PerformanceSchedule TicketPriceID Integer TicketPrice CustomerID Integer Customer BookingType Boolean Table: SeatAllocation Attribute Data Type Length Primary Key Ref. Table SeatID Integer Yes SalesID Integer Sales SeatNoFrom Integer SeatNoTo Integer Task 7: Object-Orient Approaches vs. Standard Approaches Standard Approaches Standard approach includes many variations based on techniques used to develop information system with structured and modular programming. Standard analysis and design techniques are a software engineering methodology for describing systems as a hierarchy of functions. Below are the characteristics of Standard Approaches. Approach for structured analysis consists of the following objects: Data Flow Diagrams (DFD) Shows processes and flow of data in and out of these processes. Does not show control structures (loops) Contains 5 graphic symbols (shown later) Uses layers to decompose complex systems Can be used to show logical and physical Is a quantum leap forward to other techniques at the time, I.e. monolithic descriptions with globs of text. Context Diagram

The System Hacking Cycle

The System Hacking Cycle System hacking means to hack system password within the operating system. Many hacking attempts start with attempting to crack passwords. However, passwords are the key piece of information needed to access a system. Users, while creating a password, often select password that are prone to being cracked. Passwords may be cracked manually or with automated tools such as dictionary or brute-force method, each of which are discussed in this paper. Scanning and enumeration is the first part of ethical hacking and contains the hacker target systems . Enumeration is the follow-on step once scanning is complete and is used to identify computer names, usernames, and shares. Scanning and enumeration are discussed together because many hacking tools perform both. The system hacking cycle consists of six steps:- a. Enumeration b. Cracking Passwords c. Escalating Privileges d. Executing Applications e. Hiding files f. Covering tracks Enumeration occurs after making the IPv4 protocol independent of the physical network, the designers decided to make the maximum length of the IPv4 datagram equal to 65,535 bytes. This makes transmission more efficient if we use a protocol with an MTU of this size. HowÂÂ ­ ever, for other physical networks, we must divide the datagram to make it possible to pass through these networks. This is called fragmentation. The source usually does not fragment the IPv4 packet. The transport layer will instead segment the data into a size that can be accommodated by IPv4 and the data link layer in use. When a datagram is fragmented, each fragment has its own header with most of the fields repeated, but with some changed. A fragmented datagram may itself be fragmented if it encounters a network with an even smaller MTU. In other words, a dataÂÂ ­gram can be fragmented several times before it reaches the final destination. In IPv4, a datagram can be fragmented by the source host or any router in the path although there is a tendency to limit fragmentation only at the source. The reassembly of the datagram, however, is done only by the destination host because each fragment becomes an independent datagram. Whereas the fragmented datagram can travel through different routes, and we can never control or guarantee which route a fragmented dataÂÂ ­ gram may take, all the information is provided by other means such as the hop-by-hop options or other protocols. In its simplest form, a flow label can be used to speed up the processing of a packet by a router. When a router receives a packet, instead of consulting the routing table and going through a routing algorithm to define the address of the next hop, it can easily look in a flow label table for the next hop. In its more sophisticated form, a flow lab Many hacking attempts can initialize with to attempt crack passwords. Passwords are the important information which is required to login a system. Users, when creating passwords, often select passwords that are difficult to guess. Passwords are stored in the Security Accounts Manager (SAM) file on a Windows system and in a password shadow file on a Linux system. Manual Password cracking involves attempting to log on with different passwords. The hacker follows these steps: 1. Find a valid user account for password test. 2. You can create list of possible passwords. 3. Arrange the passwords according to possibility 4. Try each password. 5. Try and try for correct password. In its simplest form, a flow label can be used to speed up the processing of a packet by a router. When a router receives a packet, instead of consulting the routing table and going through a routing algorithm to define the address of the next hop, it can easily look in a flow label table for the next hop. In its more sophisticated form, a flow label can be used to support the transmission of real-time audio and video. Real-time audio or video, particularly in digital form, requires resources such as high bandwidth, large buffers, long processing time, and so on. A process can make a reservation for these resources beforehand to guarantee that real-time data will not be delayed due to a lack of resources. The use of real-time data and the reservation of these resources require other protocols such as Real-Time Protocol (RTP) and Resource Reservation Protocol (RSVP) in addition to IPv6. To allow the effective use of flow labels, three rules have been defined: 1. The flow label is assigned to a packet by the source host. The label is a random number between 1 and 224. A source must not reuse a flow label for a new flow while the existing flow is still active. 2. If a host does not support the flow label, it sets this field to zero. If a router does not support the flow label, it simply ignores it. 3. All packets belonging to the same flow have the same source, same destination, same priority, and same option. 2. ACCOUNTING MANAGEMENT The Internet is a wonderful thing. It allows knowledge to be shared with the world. But what if you want to use the Internet to share knowledge with just one person? When web pages, e-mail, and even passwords are transferred across the Internet, they are free to be seen by anyone who cares to look. You may ask, Who is going to be looking, anyway? The answer, in most cases, is nobody. Anonymity can be your security. This is especially true of your Internet presence from home. However, the situation changes when you use your credit card over the Internet, or when you are a business on the receiving end of a credit card transaction. In such cases, anonymity clearly doesnt provide enough security. Furthermore, what if you receive a sensitive document, but you are unsure if the person who sent it really is who they claim to be? How do you know that this same document wasnt tampered with between the time it was sent and the time you received it? And what if you need to protect sensitive data on your web site, or perhaps you want to protect the data in transit to the user, or authenticate the user with a stronger authentication method? It prevents users from monopolizing limited network resources. It prevents users from using the system inefficiently. Network managers can do short- and long-term planning based on the demand for network use. Integrated Windows authentication is the most secure method of authentication, but it is available only with Internet Explorer. This authentication type had been known previously as NTLM authentication and Windows NT Challenge/Response authentication. In Integrated Windows authentication, the users browser proves itself to the server using a cryptographic exchange during the authentication process. Integrated Windows authentication supports both the Kerberos v5 and the NTLM (NT LAN Manager) protocols for authentication through the Negotiate package. If you are using Active Directory, and the browser supports it (IE 5 or above with Windows 2000), Kerberos is used; otherwise, NTLM is used. Both Kerberos and NTLM have limitations on their use. Interestingly enough, each ones strength is the others weakness. Kerberos generally works with proxy servers, but it tends to have a hard time with firewalls. NTLM generally works through firewalls, but it tends to have a hard time with proxy servers. 1. A manager checks an agent by requesting information that reflects the behavior of the agent. 2. A manager forces an agent to perform a task by resetting values in the agent database. 3. An agent contributes to the management process by warning the manager of an unusual situation. 3. PASSWORD INTEGRITY Authentication is an important feature of any secure web site. Every time a client browses to a web site, it needs to be authenticated before it can access the resources it is requesting. By default, that authentication all takes place on the server, and the client isnt even involved. Some authentication settings can make for easy access to a web site, but sometimes you want to limit who sees what information on your site. This is where more restrictive types of authentication come in. If your computer is renamed, the Internet Guest Account does not change and continues to use the old machine name. Because user accounts use security identifiers (SIDs) to identify themselves, changing the computer name doesnt affect the account name. When IIS receives a request, it automatically attempts anonymous authentication first. If anonymous authentication fails, it attempts to log on the user using another logon method. If no other authentication methods are enabled, IIS sends a 403 Access Denied HTTP error message to the client. You can use any user account that you wish for anonymous access, including the Administrator account. You can change access settings in the items Properties windows Directory Security tab, accessible by right-clicking the item in the IIS Microsoft Management Console (MMC) snap-in and choosing Properties. (By the way, even though you can do it, dont use the Administrator account for anonymous access.) Basic authentication is a widely accepted means of authentication. Because all the information is presented and transmitted in clear text, its easy to use and makes for easy program interoperability, but the passwords can be found out faster than you can say security risk. Both the web server and FTP server components in IIS support Basic authentication. 4. CONCLUSION The simplest and the oldest method of entity authentication is the password, something that the claimant possesses. A password is used when a user needs to access a system to use the systems resources (log-in). Each user has a user identification that is public and a password that is private. We can divide this authentication scheme into two separate groups: the fixed password and the one-time password. In this group, the password is fixed; the same password is used over and over for every access. This approach is subject to several attacks. 4. REFRENCES www.ankitfadia.in for ethical hacking and password guessing techniques. www.ethicalhacker.net www.hackcommunity.com www.dl4hacks.com www.go4expert.com/forums www.ehacking.net www.govermentsecurity.org/forum/32003

Anglo-saxon Belief In Fate And Christianity :: essays research papers

The Unity of the Unknown and the Eternal Security: The Anglo-Saxon Belief in Christianity and Fate Imagine a life in which one is simply a pawn at the hands of a mysterious higher force stumbling and meandering through life's tribulations. Until Pope Gregory the Great was sent to spread Christianity throughout England, the Anglo- Saxons believed solely in this passive, victimizing philosophy. These pagans still clung to much of their heathen culture after the wave of Christianity swept through England leaving no one behind. Literature derived from this period (including Beowulf, "The Seafarer," and "The Wanderer") directly reflects the maintaining of Christian ideals, as well as the belief in fate's unknown and often grim path. For example, the epic poem, Beowulf , declares, "...Fate will unwind as it must!" (line 284). Meanwhile, the same work implies God has the authority in this great world by stating, "And all his glorious band of Geats/Thanked God their leader had come back unharmed," (598-599) as if God was the deciding factor in the great protector's health. The joining convincedness in God and fate influences the culture, outlook on life, and the various independent life paths of Anglo- Saxons. These early Germanic people believe "fate"- an anonymous power - controls the present, future and past; yet, they also believe the power of God is a resolute supremecy not to be denounced. Our earliest warriors put aside their heroic independence and let wyrd's foreign agency control their views and their lives' paths time and time again. These pagans even allow destiny to influence their view of life which was fatalistic and desolate. "The Wanderer" proves the Anglo-Saxons had little to live for and much to fear as it tells the tale of an anonymous man stripped from his gold-lord. This literary work illustrates stoic solitude and grim hopelessness by using phrases like, "...what a bitter companion/Shoulder to shoulder sorrow can be,"(lines 26-27) and "Wretchedness fills the realm of earth," (98). Along with their outlook on life as a whole, fate controls the pagans decisions and lack there of. "The Seafarer" shows an example of the Anglo-Saxons submissive role by voicing the story of a sailor suffering through hardships because he was meant to be a sailor and is drawn to the familiar sea. The sailor explains his painful lifestyle by stating, "...my soul/Called me eagerly out..." (lines 36-37) implying this harrowing lifestlye is not a conscious choice, but more of an obligation to something other than his mind and heart. Even the bravest warrior fell victim to this unsafe and unpredictable fortress. Beowulf, who is "...-greater/And stronger than anyone anywhere in this world, " (110-111), explained on his

Flowers For Algernon :: essays research papers

The story Flowers for Algernon depicts the meaning of intelligence in a very deep sense. The narrow definition intelligence is the capacity to learn, to understand, or to deal with new or trying situations. It is a concrete definition in such a way that it also means the ability to apply knowledge to manipulate one’s environment or to think abstractly as measured by objective criteria as tests. Yet the story goes beyond this concrete explanation of what intelligence really is. It shows a whole new perspective of the meaning intelligence. The novel gives a theory of the more intelligent you become the more problems you will obtain. As a result your intellectual growth is going to outstrip your emotional growth. This theory is shown in the novel with Charlie having two growths, intellectual and emotional. These two growths interact by reason of once there is a high intellectual growth that is rapidly out growing, the emotional growth will stay the same or increase at a much lowe r speed.   Ã‚  Ã‚  Ã‚  Ã‚  The definition of intelligence that is explained in the book is having certain attributes that help you become a stronger individual. The qualities are having honesty, ethics morals and compassion. One has to achieve this intelligence thoughtlessly; Charlie shows this before he has his operation. By reaching this type of intelligence a person does not have to have a lot knowledge or a high I.Q, but you may reach peace in life by being a spiritually kind person that is previously show in the abstract definition.   Ã‚  Ã‚  Ã‚  Ã‚  The only positive effects of the intellectual growth that one can gain is to be able to experience what the concrete definition was like in one’s own personal experience. Yet the negative effects of the operation, which were great, was the intellectual and emotional growth colliding.

Crumbling Dreams in Arthur Millers Death of a Salesman :: Death Salesman essays

Crumbling Dreams in Arthur Miller's Death of a Salesman Arthur Miller's Death of a Salesman is a play best summed up in its title, it is just that, the death of a salesman. This death is not necessarily the physical end to a human life, but the crumbling end to the dreams of Willie Loman, the play's main character. The three main parts to Willie's world are his job, his family, and his image as seen by the rest of the world. Although these parts are interwoven and interrelated, they are best divided and given separate analysis. The first part of Willie's world is his job. Willie is a salesman for a large company in New York. Willie's self-image and much of his self-worth are based in his job. In his own mind he is still as he used to be, well known and well respected among the clientele in the New England area. Things have changed though and the people Willie once knew in the business are no longer there and he no longer has the connections he once had. His inability to cope with and adapt to this changing business has caused, among other things, a loss in pay. Willie has lost his competitive edge, and with it his feeling of self worth and identity. The second part of Willie's world is his family, more specifically his son, Biff. Biff is the firstborn and favorite son of Willie. Willie has high expectations of, and transfers his dreams, as so many fathers do, onto Biff. Biff can not live up to the expectations of his father and has dreams of his own which cause Willie to see him as a loafer, a shiftless bum with no desire to succeed. Although Willie's dreams are not realized in Biff, his son's respect is still important. This respect is lost when Biff catches his father in an affair with a young lady. Even though this is not talked about (Biff never told anyone, not even his mother) it still creates tension and causes Biff to lose the respect he once held for Willie. Willie's main philosophy in life is "Be liked and you will never want" and this is the cause of the problems in the third part of Willie's life, his image. Image is everything to Willie. In his past he was a well liked, well known, respected man who turned his image into his success, but his image has changed.

Quality Improvement Plan Essay

Executive Summary Chattanooga Cares is a privately owned, not-for-profit HIV/AIDS clinic located in downtown Chattanooga. Owned and operated by Dr. Jay Sizemore, it was founded in December 2003 to provide medical needs for the underserved HIV positive patients in Chattanooga, Tennessee and 22 surrounding counties. Although its staff is small, consisting of a full-time work force of less than 30, they serve their community by offering AIDS testing, counseling, HIV treatment plans, and assistance with employment, housing, transportation, and childcare. Chattanooga Cares has one very important goal – reducing the levels of sickness in HIV/ AIDS patients. Therefore, the management team has designed a Quality Improvement Plan to tackle this goal. This aspiration has two components; the first concerns itself with the education of the community, and the second revolves around reducing the levels of sickness in already affected patients. Implementation begins with education of the staff in areas of HIV/AIDS protection, treatment, and counseling. Outreach programs, taught by the staff, will be offered to guide the community in AIDS awareness. Data collection tools such as patient tracking system and disease specific flow charts will be utilized to scrutinize the effectiveness of the program. The plan-do-study-act approach to collecting data, monitoring, evaluating, and adjusting will be used to ensure that constant changes can be made to reach our goals. Chattanooga Cares will use competitive benchmarking to determine if their levels of sickness are in line with other clinics in the area. Finally, each person will compile his set of data and report to the management team for evaluation of the plan. The team will use the information collected to make adjustments going forward. This collaboration will be completed on a monthly, quarterly, and annually basis. Chattanooga Cares Quality Improvement Plan Quality improvement cannot be implemented without setting the performance standards needed to determine how improvement can succeed. Chattanooga Cares, a non-profit HIV/AIDS clinic, bases its quality improvement plan around the consumers of their services. Chattanooga Cares is a privately-owned AIDS and sexually transmitted disease clinic in downtown Chattanooga, Tennessee. It consists of a small staff of medical personnel, counselors, administrative staff, and volunteers. The staff offers HIV/AIDS testing, medical treatment plans, counseling, life coaching, and economic assistance through various housing, childcare, and financial institutions. The clinic derives its funding from government grants and community fund-raising events. Chattanooga Cares (2013) mission statement is, â€Å"Our focus is AIDS: education, prevention and support for all people affected by HIV† (About Us). Since the patient, and the patient’s network of friends and family, are the central elements in Chattanooga Cares’ mission statement, the role of the patient is integral in quality improvement plans. There are few goals that do not involve the client. Although the clinic is privately-owned, it proudly displays its goals to the public. Because of its grant status, the treatment center must supply statistical information to the governmental agencies that provide the grants. All this information is readily available to the clients that consume their services. Goals and Objectives Some of the quality improvement goals of Chattanooga Cares are reducing the number of new patients infected by AIDS each year; lowering the economic hardships on their clients; maximizing efficiency and cost effectiveness within the office; and increasing training and education of staff. The clients play a major role in what performance standards are chosen. A few of the quality indicators that consumers use in regard to Chattanooga Cares are health outcomes and length of survival rates, screening and treatment frequencies, and satisfaction evaluations. Using feedback from stakeholders effects the way in which future services are conducted and funding is attained. In order to begin a quality improvement plan, certain quality performance standards need to be determined to measure the levels of improvement. Performance standards concern themselves within a health care organization. Palmer (1997) suggests that clinicians must set performance  standards on their individual practices and offer feedback to health care authorities. Two examples of these standards are defining the rate of re-admittance after completing a procedure and setting a limit for number of patients seen daily. Once the standards are determined and goals are set, compilation of everything is developed into the quality improvement plan. The quality improvement plan is the all-encompassing strategy while the performance standards are the steps needed to achieve it. Scope, Description, and Quality Improvement Activities The first part of the improvement goal of Chattanooga Cares is one of reducing the current levels of HIV/AIDS in the 23 counties the organization serves (â€Å"Chattanooga Cares†, 2013). By reducing the number of people affected by the disease, the overall health status of the community will improve and the economic effect on the health care system will be positive. Since 65% of current patients (â€Å"Chattanooga Cares†, 2013) cannot currently obtain health insurance due to their health status, a decline in the infected population will mean less public monies are needed to support the health care of the indigent population infected by the AIDS disease. The best outcome of reaching this goal is a suppression of the AIDS infected population. Education in the community improves the knowledge base of the community as they learn the risk factors of AIDS contraction and hopefully use that wisdom to make wiser choices in sexual partners and intravenous drug usage. Through careful management of current patients’ progress, the team at Chattanooga Cares can evaluate and adjust the health regimen and assure that proper techniques and medication are being used. Data Collection Tools The main goal of Chattanooga Cares revolves around reducing the level of sickness in patients. The data needed are tracking patient progress through the treatment process, and current information of HIV/AIDS manifestation and control. Following patient progress is achieved through the usage of a reminder tracking system. As soon as a new patient is entered into the electronic medical records of the clinic, a tracking system immediately forms to trace the medical journey of the client (Hashim, Prinsloo, & Mirza, 2013). The system sends out emails, automated phone messages, or  texts to patients reminding them of doctor and counseling appointments. It prompts the case manager to contact the patient personally and ask them questions about their general health, response to medication, mental state, and other factors such as housing, employment, and childcare status. By entering information into the tracking system, adjustments can be made to assure that the patient does not degrade in physical and mental health status. This tool can help prolong the lifespan of the patient and help them get better. Over long periods of time, as a patient has developed an effective health regimen, the system stills tracks their progress and reminds the case manager to touch base from time to time. The strengths of this system are that a patient does not drop out of the program and their health status is continually monitored and improved upon. The weakness is that the ongoing information must be entered into the system to be effective; if the staff is too busy or forgets to follow up, then the health of the patient may be compromised. The measurement and display of this tool could be shown through weekly reports which show the number of patients whose contact reminders have not been completed. The last data tool used to track current information on HIV/AIDS is a disease specific flow sheet (Hashim, Prinsloo, & Mirza, 2013). This chart contains information on the steps needed to test and treat people affected by HIV/AIDS. It allows clinicians to follow a prescribed course of medication and counseling for patients and permits changes in the course of health management. The benefits of using this flow chart is that treatment is spelled out for virtually every type of AIDS related illnesses and gives doctors a reference to follow. The only detriment is that the clinic must make sure to have current flow sheets which show new drugs and regimens for patients. If the clinicians are using outdated materials, then best practices are not being put to use. Quality Improvement Processes and Methodology The plan-do-study-act (PDSA) approach to quality improvements is one of small cyclical changes between processes and outcomes. It focuses on making little changes instead of large, broad strokes that can sometimes be too large to tackle at one time. Hughes stated (2008) that the purpose of PDSA is one that tries to â€Å"establish a functional or causal relationship between changes in processes (specifically behaviors and capabilities) and  outcomes† (p. 33 Chapter 44). The PDSA cycle begins by defining the disposition and extent of the issue, what modifications can and should be made, a strategy for a specific change, who should be participating, what should be gauged to comprehend the effect of change, and where the stratagem will be directed. Change is executed and data and materials are collected. The results are studied and clarified by using key measurements that show the levels of success or failure. New steps are developed based on the results and the process begins again (Hughes, 2008). This approach to quality improvement is positive in that allows extensive problems to be disentangled at a rate not overwhelming to those involved. Because PDSA is readily achievable and results are easy to decipher, almost instant gratification can occur. This makes a monumental task easier to tackle – much like eating the proverbial elephant one bite at a time. The drawbacks to this approach are that it is reactive and relies on people to accept constant change in their facility that can result in change fatigue (Hughes, 2008). To achieve the QI goal, the clinic must review continually the data retrieved from the tracking system of patients’ progress through the treatment process. Therefore, the methodology chosen for Chattanooga Cares’ QI plan is PDSA. Because this system focuses on small, continual changes, it will be helpful in staying on track. Another reason for this choice is that the clinic is small and is used to a frantic pace, therefore change is commonly accepted and a part of the norm. Comparative Databases, Benchmarks, and Professional Practice Standards  Hughes (2008) describes benchmarks in health care as â€Å"the continual and collaborative discipline of measuring and comparing the results of key work processes with those of the best performers in evaluating organizational performance† (p. 38, Chapter 44). Competitive benchmarking can be used to compare Chattanooga Cares’ levels of sickness to other organizations offering the same services (Kay, 2007). By using reports from other HIV/AIDS clinics, Chattanooga Cares can compare their levels of sickness to the patients serviced by other treatment centers. Authority, Structure, and Organization The authority structure of Chattanooga Cares is straightforward and simple. Because it is privately owned, there is no board of directors. Instead, Dr. Jay Sizemore, the physician who owns and runs the clinic is the head of the organization (â€Å"www.chattanoogacares.org/†, 2013). Five other positions comprised of a registered nurse, a medical assistant, an LPN, a patient health coordinator, and an office manager, finish out the authoritative staff at the clinic. Although the doctor leads the team, the other five mentioned have equal standing in decision-making and quality improvement implementation. QI issues are discussed within the confines of these six people and all decisions are handed down from them. Each holds their own position within the organization, however, out of necessity, all of them work interchangeably within other people’s job duties. Communication Because of the intimate nature of Chattanooga Cares, quality plans are shared among all the staff. If a particular strategy involves essentially one person’s performance, that person will hold most of the responsibility for implementing, measuring, and ultimately, evaluating the effective of the plan. For instance, one goal is to improve the levels of sickness in the HIV/AIDS patients the clinic serves (â€Å"www.chattanoogacares.org/†, 2013). A tool for implementing and measuring this is a patient tracking system that follows a patient’s progress through the system. The person responsible for this quality improvement device would be the case manager for that patient. This person would monitor the tracking system, collect data through reports, assemble data for team review, evaluate the effectiveness of the QI plan, and ultimately, apply needed improvements. Each person is responsible for his part(s) in any given QI plan as well as gathering data and reporting such data to the team. Education All medical staff must be board certified and all case managers must have a background in social work and be at a minimum a licensed LPN. All education and prevention staff must be state certified in HIV/AIDS testing and prevention counseling (â€Å"www.chattanoogacares.org/†, 2013). Annual training and certification is required by all employed and volunteer  staff to meet conditions of state and federal grant programs. To implement the patient tracking system quality improvement plan, each person working with patients will be included in the introductory training of the software program and be introduced to the goals of the QI plan. This will be communicated by the person overseeing the process, most likely the case manager. Because staffing at the clinic is minimal, this training can take place efficiently, with little loss of productive medical time with patients. The process will be covered from the initial contact with a patient and will continue as long as the patient wished to be under the clinic’s health care plan. Therefore, it is ultimately the responsibility of the entire staff and not just the case manager, to ensure that current information is uploaded to the tracking system, and that prompts by the system are met in a timely manner. Annual Evaluation The evaluation of the QI plan for improving sickness levels in patients’ is done on monthly, quarterly, and annually bases. Because continual evaluation is needed for the plan to succeed, data must be collected before it becomes overwhelming in numbers. If this plan was left entirely to an annual evaluation, it would take weeks, if not months, to assemble, evaluate, and implement changes. The factors gauged are made of up several items – reports showing the follow-up times of patients, data indicating how many patients did not receive required contact during the time period, and the time frames of between the system prompts and response intervals. When complied, this data shows the breakdown in interaction and allows the team to make changes to ensure that patients do not lack in communication between themselves and the clinic. Monitoring the data on a weekly, if not daily basis, allows the QI plan to be more effective by making changes using the PDSA approach. References Hashim, M. J., Prinsloo, A., & Mirza, D. M. (2013, Spring). Quality Improvement Tools for Chronic Disease Care – More Effective Processes are Less Likely to be Implemented in Developing Countries. International Journal of Health Care Quality Assurance, 26(1), 14-19. DOI:10.1108/09526861311288604 Hughes, R. G. (2008). Patient Safety and Quality: An Evidence-Based Handbook for Nurses. Rockville, MD: Agency for Healthcare Research and Quality. Retrieved from: http://www.ncbi.nlm.nih.gov/books/NBK2682/ Kay, J. F. (2007, February). Health Care Benchmarking. The Hong Kong Medical Diary, 12(2), 22-7. Retrieved from: http://www.fmshk.org/database/articles/06mbdrflkay.pdf Palmer, H. R. (1997, October). Using Clinical Performance Measures to Drive Quality Improvement. Total Quality Management, 8(5), 305-11. Retrieved from http://search.proquest.com.ezproxy.apollolibrary.com/docview/219816031 www.chattanoogacares.com (2013). Retrieved on September 3, 2013 from: http://www.chattanoogacares.org/about-us.html

Impact of Christianity in Australia Essay

* The proportion of Christians in the Australian population continues to decline. * Internationally, the proportion of Christians in developing countries is tending to increase, whereas the proportion of Christians in developed countries generally is decreasing. * This paper first provides a brief overview of the current Australian demographic data and trends in relation to Christian denominations and other religious groups over the past 100 years. * Based on Christianity’s past contribution to Australian society, it then posits a framework for a way forward to contribute to the current and future issues and problems confronting Christianity in Australian society. * Christianity had a significant impact on education and public morality in Australia whin the years of 1788-1900. In relation to public morality, I discuss the significance that the Christian church had on Australian society in the 1800’s by the establishing of the Temperance movement as well as several other actions involving education. * While Christianity played a crucial part in all aspects of Australian society throughout the pre-federation years 1788 to 1900, it had a significant impact on education and public morality. * The influence of Christianity in education was evident through the establishment of a separate education system and, in public morality the formation of the temperance movement as well as other actions. * Education was greatly influenced by Christianity during 1788 through to 1900. Settlers concerned to leave religious divisions in Britain believed that ties between church and state should be eradicated and that churches be supported by their own followers. * Subsequently, with numerous denominations supporting this idea, concerns were partly met by the granting of financial aid to the major religious groups, including the Church of England. * Individuals churches used this aid to maximise its religious and educational influence. * Governor Bourke later extended the state financial aid and attempted to introduce government schools based on the national system in his native Ireland. * However, non-Anglican Protestants, who had formed in 1835 a society for promoting schools where the Bible would be a basis for general education, insisted on its wider use in the proposed national schools than was permitted in the Irish system. * Catholics supported the Governor’s proposal which further angered the Protestants. The successive alliance between the Anglicans and the Protestant denominations favourably brought about an anti-Catholic move to condemn concessions to a religious minority at the expense of national school systems based on the religious teachings of the Bible. * In the past, Christianity has made a sustained and valuable contribution to Australian communities. * To focus on the changing religious demographics in Australia may be discouraging for many Christians, but Christianity again can make a valuable contribution to contemporary societies – if its attention is focussed on the community and not on itself. * This paper proposes that Christians learn from the past and, rather than introspectively focussing on maintaining the two first positions described above, accept the third position and engage with existing communities by utilising communal practical life-style Christian principles. * Perhaps from this new perspective, Christianity will become relevant and re-invigorate the traditional (Christian) Australian values as Described by Linder (2006), values of justice and a fair go, self-sacrifice for the good of the community, mateship based on selflessness, and neighbor love.