Social Construction of Freaks by Robert Bogdan free essay sample

On my trip to come here and passing across some countries , I have the experience to see, it again in Guatemala, Mexico, and The United States, but the interesting thing about it was that in each place, it happened differently, regardless the resources, economy situation, and education level. It also continues happening in the life of youths in different scale, problems and obstacles. My purpose to write this paper is to show you what a talent show is , my reason to organize it, when and where it will happen, who will participate in it, and what I will learn by organizing it. This talent show will be free for all youthcare’s staff, clients and volunteers that donate their time as their money, and the most important thing is to share their love and contributions to change a lot of lives. Anyway, in this talent show 10 youths will be performing by showing different talents, and each one of them will get a prize for being brave to be on the stage in front of a lot of people. We will write a custom essay sample on Social Construction of Freaks by Robert Bogdan or any similar topic specifically for you Do Not WasteYour Time HIRE WRITER Only 13.90 / page In addition, there will be a talent winner that will be chosen by the audience in the event. The event’s theme will be hope and the scenery will be decorated with different hope’s quotes and people of hope. What does talent show mean? Well, I was looking up in the internet for the meaning of a talent show. I found the best and simple description on Wikipedia; it describe a talent show as an event where participants perform their talents of acting, singing, dancing, acrobatics, drumming, martial, arts, playing instruments, and others activities to showcase a unique form of talent . It’s sometimes for a reward, trophy or prize, school talents show awards of 1st, 2nd, and 3rd place. What does a talent show mean for me? for me, a talent show is a way to express, show our sentiments, and combine it whit the passion and skills that god give to each of us. Knowing what we have, to be able to show Its to the world. The beauty about a talent show, it’s that raze, skin color, gender, religion are on the side of the way, because the most important are yours skills, talents, and all the sentiments that you put in to it; the sentiments that come from you hearth, no from your color, nationality, gender, or religion. Your talents it’s the give that god gave to you, but you need o find it and when you realize how special, and talent you are; you will be ready to give to the world a strong bright, with the capacity to give light to everyone in your side. Before, I came to Seattle; I was in Houston, Texas, in a high security immigration program for under 18 immigrants youths whit criminal delist. Most of the kids there have criminal records in the United States. At the first day I was there one kids was broking a t. v. with a chair, the securities were trying to control him. In addition, I was so scary, because most of the clients were violents and mean each other; some of them were gangs members of two different sides in California. Anyway, no matter, how violents they were, I discovered something that surprised me. Most of these kids were no bad or deserved the word criminals. T hey just did things that were bad, but it don’t want to said that they were bad kids whit bad sentiments or bad human beings. In addition, almost most of this kids was listening me, respecting me, and getting alone with me, but not before respecting them, listening them, trying to understand they way to being; understanding were they came from, who they family members are, and the situations that happened in their life. I discovered that these guys only have needed and still need someone to listen, understand, and motivate to believe in their skills, capacities, talents, their dreams. People to do see them how valuable they are. Nobody like to be critiqued by others, but something sad about this world is that most of people do. It’s easy to critic and see the bad things that others do, the hard thing is to try to listening and under thing others. Anyway in Texas, juvenile jail for under 18 immigrants, rulers were astrictive, for instance we could out to the jail’s yard one hour a day and while that time, most of the youths were playing soccer because they loved; I also realized that other young loved dancing, singing, drawing, and make things by hands, most of them were so talents. In addition, I was having living there for two months. I wanted to looking for the way to show them how talent, they were, but for do it I need something better than word. I need actions and examples that show it to them; after a while of thinking about it. I came with the conclusion to ask to the staff there and get from them ideas, that could give me a gin about, what to do? to make possible motivate the kids from there, by showing their abilities. nyway when I asked to some of the staff for ideas no all reacting positive about it; some of them said it to me, â€Å"I can see your good intension; Carlos, but the only talent that I can see in most of them is to scream, and fight each other’’ this kind of negative commentaries didn’t stop me to continuo to looking for a way to organize something that show my friend’s talents that by that time, I was seeing them how brothers. In addition one of my favorite staff and friend gave me what I was looking for. Miss, Edith gave me the idea to organize a talent show, she is from, Colombia and the person that teaches me to use a computer, and some Basic English. Anyway, she came with the great idea that I need to encourage and to show to my latins brothers there how value they are; with the idea in my hands. I began to talk about it with them. I was so enthusiastic, because it will make them get more confidence in their self. Something interesting about my culture it’s that most latins don’t like to be parts of events, it mean doing anything in from of people. The main reason of it is because most latinos don’t like to lost or make in mistake from others. The thing is that was no easy to get them be part of the talent show, but tanks of god, they have confidence in myself and after of explain them that where nothing to lost, and a lot to win. After of be sure that the youth will participate in it, I need to get the premise from the jail director and the date that it be. She was agree about it, and she was also very happy about the idea she did believe that a what I wanted to do. in addition, after I talked with the director and have her authorization. I needed to find the date and time, therefore the weekend was a great time to do it because we didn’t have anything to do in at that time. In addition almost all the staff were so happy to help me with it. Some of them also were interesting on performer in the show; and I was so happy to said to them yes. Anyway the talent show were realized in a April’s weekend at the big living room of the C area; the talent show there was very inspire for the youths and worker there and also it was very inspire for me, because its really did a big impact and a positive experience for each of us. My experience with talent and hope in Seattle, Washington I really don’t know how, Seattle began to be a big part of my achievements and goals. In addition when the immigration programs send me, from Texas to here, I thought I andwas coming to the capital of the United States. I never imagnated that Seattle, was my destination, the city of the United States, that changed my life in a big scale. Anyway, I was transfer from a high security immigration program to a normal immigration program for under 18 immigrants. The program is call. Casa de los amigos that in English is mean; something like, home of the friends, in casa almost all the staff speak English, and Spanish, for me it was a great opportunity to learn some basic English; at that time I didn’t speak English, and casa’s staff where always happy to help me, with it. In addition, every day I was learning more, and more English’s words on a couples of days, I knew how to introduce myself, and some important English’s question. For instance, to ask for food and other kind of things. Anyway casa’s kids were very talents most them loved to sing an dance others liked better to draw, gymnastic, to play soccer, and tell stories. In addition, in casa I never organized a talent show, but I was always encourage them to don’t be embarrassing about to dance, or sing etc. some of the casa kids where desesperated, and they got obsess about to be in a place where, they can’t go out and the fact that we didn’t have any family close of us. It was very hard, we latins are accustom to always be together with our family, because it is our most important value, I knowing it. I began to encourage them to be patience with the staff there, and their cases. I knew that don’t matter how bad or good do you feel about it, time is time and is passing, it can’t stop. The point is how to use it and take bandage about the opportunities we have there, we could communicate with our family by phone 2 time a week. We also have a lot Latin food, and one of the best things in casa is that you can go outside 2 times a day. It never will happen in most of the immigration programs in the Unite State. In my own experience I can say that; Casa de los Amigos is one of the best program in The United States for immigrants under 18. When one of my friends talked to me about how, frustrate, sad and desperate he was feel. I just give my way to see the situation, and show him the big significant and positive things that we had there. I put them to think about the opportunity to grow how a youth and use the time learning and improving they talents, abilities, that they have and love. Getting better in then at the way that they can use it to overcome, successfully, and change their life. I talk the true to most of them about to don’t do nothing talking with them to just point, and argue about all the negative things, and problems that we all have. Because it just will make us feel sad and frustrated about the things in our life. I always talked to them that we have the power of choose the way to see things and problems in our life. We can choose between the positive or negative way. Anyway, in casa I was fighting an immigration case to state in the United Stated. Therefore my two layers got me the opportunity to go out of â€Å"Casa de los Amigos program† to go to a non immigration program where I could go to school, be more free, and go out for myself whit any adult’s supervision. While I was in there the immigration system and the state was desisted my future to state or be deportee to my country. Anyway go to other program motive and inspire me to continue working in my goals and objectives that I have for the future. It also motivated me to learn more and more the English to be able to communicate well with others, knowing that English is a universal language that will open doors to me, wherever a go. In addition, I can say from my own opinion that pathway’s program, at the time I was there was a very good place to grow, learn and discover new things. It also has a very good and professional people working there. Anyway, with the pass of the time I have living in it. I could understand and speak a little better the English language. For instance, speaking and understanding the English was a little easier. I could have a small conversation with the staff and youths there, it was a very good way to listen and understand the reason why the youths were there and no whit their family? In addition, the kids there have a lot to talk about it, each of them have a sad story about their life to share, no matter the fact of being a citizens in capitalist country where most people think , life is more easy and, because the economic situation and the support of the government. In addition, things are not that easy, almost all the kids from pathway program had have drugs addiction, and depression problems. Its, because they did have a unite family or others family’s problems etc. anyways, I met in there a lot talents kids, likewise Alyssa, and Max: They were like brother and Sister Alyssa, is one of the funniest person that I know, and Max is coolest guy ever met. By now, Alyssa and Max, have a lot done in their life, for instance both of them are going to college this is just emagazine. In Addition, both of them talked me that that they hate school about it, I just got them my humble opinion. I talked them that everyone that want to grow as a person in this glove need to go school and it is just a another step in our life to got the enough innollege to be able to get what we want, and the most important be a example in a positive way for the family that we will have in the future and also have the enough economic resources to have a stable life, support you family, and if we study what we love to do, we will be happy and our kids will be happy and proud of us, we will be able to say to them you can file your dreams you can do it, I could do it. Anyway, Max still working in is passion in life, that is music, he love play the guitar, and the thing is that he is so talent doing it. In addition, Alyssa love to act in the theater, and she is just has a naturally talents in it. Likewise, them I met inside, â€Å"Pathway† a lot of others talents kids with a lot struggles, and difficult situations in their life’s. Anyway, I love the kids I met in Pathway program. In addition actually they are like my American brothers, and sisters. They make a big change in my life, in the way of try to understand better and be more open mind about the youths from from here and they culture. Anyway Pathway for me, was a great learning and discovered experience. The staff really were like parents for me, and the kids were and still conder for me, as how it. In addition, after, I left from pathway. I went to passage’s program.

The Boston Irish essays

The Boston Irish essays During the times of immigration to the United States conflicts arose between the Yankees and Catholic immigrants. These two cultures, which couldnt have been more different at that time, were separated as two classes on the political spectrum. Secret farming organizations like members of the Steelboys engaged in voyaging to North America. Rebellious countrymen such as these would later tend to be the ones who would start later uprisings against the Yankee Americans. Much like members of gangs today these, organizations would resort to violence, muggings, and other things of that nature for simply a rise out of society or a radical political view. Along with the other Irish immigrants making their way across the Atlantic, Wild Geese also were among. These Wild Geese were remnants of Irish nobility and surviving rebels that offered their services to the courts of Englands enemies in France, Austria, and Spain. After nearly a century, the descendants of these Wild Geese would later become involved in liberation acts in Latin American countries. Many of the other immigrants that made their way over to the US came because of the intensely poor conditions most of which were from Western Ireland. The majority of these immigrants would stay with their relatives or friends that had already settled into Boston. In the war of 1812, numbers in the armed forces were severely decimated. To compensate for the losses volunteer militias were setup to hopefully strengthen a basic line of defense for self-protective reasons. In return for serving the basic militia duties, the soldiers were given new and brilliant uniforms and with these uniforms they were allowed to attend certain balls and social activities that they previously would not have been allowed to attend. With this new system of volunteering and the pleasing benefits, many of the Irish gladly with reason to benefit...

Hand Sanitizer Fire Project - Instructions

Hand Sanitizer Fire Project - Instructions Here is an easy fire project that produces flames cool enough for you to hold. The secret ingredient? Hand sanitizer! Hand Sanitizer Fire Materials Be sure your hand sanitizer lists ethyl alcohol or isopropyl alcohol as the active ingredient. Other chemicals may not work or they may burn too hot. Hand sanitizer gelLighter or match Instructions On a fire-proof surface, make a pattern using the gel.Ignite the edge of the gel. The flame will spread.If you like, you can touch the flame. Be careful! Although the hand sanitizer flame is relatively cool, its still fire and it can burn you. Colored Fire You can mix colorants into the hand sanitizer gel to produce a colored flame. Boric acid or borax (found in cleaners and pest control products) will produce a green flame. Potassium chloride (lite salt) will give you a purple flame. You can create cool special effects by applying the burning gel to other surfaces. For example, coating a metal object will form a halo of flame around it, which makes a great effect for photos. If you choose to coat a flammable object (e.g. a stuffed animal or a cardboard shape), soak it in water first. While this wont completely protect flammable matter from damage, it will keep it from bursting into flame. Watch the video of this project. How to Put the Fire Out Because hand sanitizer is a mixture of water and alcohol, once some of the alcohol burns, the water puts the fire out on its own. How quickly this happens depends on the specific product youre using but its usually around 10 seconds. If you want to put out the flames before that, you can simply blow them out, as you would a candle. Its also safe to douse the flame with water or suffocate it by covering it with the lid of a pot. About Hand Sanitizer Fire Hand sanitizer has applications beyond killing germs. Gels that contain ethyl alcohol or isopropyl alcohol produce a relatively cool flame that is made more manageable by the high percentage of water in the product. You can use the gel to draw with fire or for projects in which you need to hold fire. Keep in mind, the flame is still hot enough to burn you if you hold it too long and it can also ignite paper, fabrics, etc. Take care to perform this project in a safe location, away from flammable material. As with any fire project, its a good idea to have a fire extinguisher or at least a glass of water handy. Hand sanitizer fire is an adult-only project. Fun Fire Projects If you liked making fire using hand sanitizer, try these related flame science experiments. How to Breathe Fire, Safely: Using a nonflammable, edible chemical to breathe fire.Handheld Fireballs: Water is the key ingredient to creating a flame cool enough to hold.Make Green Fire: You can use the same chemical to color hand sanitizer flames.More Fire Projects: Were just getting started!

Process of the supreme court Essay Example | Topics and Well Written Essays - 250 words

Process of the supreme court - Essay Example This also gives room for the consideration of various shades of opinions based on individual interpretation of the law. Since verdicts must also adhere to the 200 year old United States constitution, this enhances the dispensation of justice to all citizens. The amendments to the constitution for example, in what is referred to as the second bill of rights have assured all citizens of equal rights, making the document very useful in the operations and decisions of the Supreme Court. All the same there are weaknesses in the Supreme Court process. The workload is immense, considering that each Justice is responsible for verification whether appeals, which come from all over the United States qualify for consideration. Though each Justice is assigned a small staff, they are responsible for each appeal or case. The process is long and complicated and the ramification of this is that it will implicate denying justice to those affected due to the long procedures involved in declaring the verdict. Decisions reached by the Justices are also binding and open to scrutiny and, some people may feel that some decisions made were incorrect since they were made by only a few

Team article review #3 Essay Example | Topics and Well Written Essays - 250 words

Team article review #3 - Essay Example pany, Under Armour, also tried to sign Kevin Durant for the sale of its sneakers, but Nike signed him back first, because if Durant had gone to Under Armour, then a lot of clients of sneakers would have turned to Under Armour. Hence, this all is a game of one competitor thinking about strategies to win over another competitor in business. This is why, this article is very interesting for my team, as it talks about very remarkable strategies that business adopt to earn huge revenues while losing some of it or investing some of it. This is kind of an investment that Nike has done in Kevin Durant, and then, it is also a business deal for Durant as it will benefit him too. Businesses and companies have to move very strategically while thinking about how to attract clients. Making one wrong decision, or taking one wrong step, can lead to disastrous results. Losing Kevin Durant and watching him go to Under Armour would have been a huge setback for Nike, because it would have meant losing c ustomers. The sense of competition and strategic management of business is what caused my team to choose this article. Stock, K. (2014). Nike needs Kevin Durant, even if he cant sell enough shoes. Bloomberg Businessweek. Retrieved November 14, 2014, from

Evidence Collection Policy Essay Example for Free

Evidence Collection Policy Essay 1.What are the main concerns when collecting evidence? That you are thorough, collect everything, do it in the proper and official manner, and that you do not tamper with or alter anything. 2.What precautions are necessary to preserve evidence state? Usually what is done is all of the evidence is duplicated several times and any processes involved with the investigation are done with the duplicates to ensure that the actual evidence isn’t altered in any way. 3.How do you ensure evidence remains in its initial state? It is duplicated and then stored in climate controlled conditions. 4.What information and procedures are necessary to ensure evidence is admissible in court? Whoever conducts the investigation does so in a previously mandated, official, and legally recognized manner. Information Systems Security Incident Response Policy I. Title A. Name: Information Systems Security Incident Response Policy B. Number: : 20070103-secincidentresp C. Author(s): David Millar (ISC Information Security) and Lauren Steinfeld (Chief Privacy Officer) D. Status: Approved E. Date Proposed: 2005-10-24 F. Date Revised: G. Date Approved: 2007-01-03 H. Effective Date: 2007-01-16 II. Authority and Responsibility Information Systems and Computing is responsible for the operation of Penn’s data networks (PennNet) as well as the establishment of information security policies, guidelines, and standards. The Office of Audit, Compliance and  Privacy has authority to develop and oversee policies and procedures regarding the privacy of personal information. These offices therefore have the authority and responsibility to specify security incident response requirements to protect those networks as well as University data contained on those networks. III. Executive Summary This policy defines the response to computer security incidents. IV. Purpose This policy defines the steps that personnel must use to ensure that security incidents are identified, contained, investigated, and remedied. It also provides a process for documentation, appropriate reporting internally and externally, and communication so that organizational learning occurs. Finally, it establishes responsibility and accountability for all steps in the process of addressing computer security incidents. V. Risk of Non-compliance Without an effective incident response process, corrective action may be delayed and harmful effects unnecessarily exacerbated. Further, proper communication allows the University key learning opportunities to improve the security of data and networks. Individuals who fail to comply are subject to sanctions as appropriate under Penn policies. VI. Definitions Confidential University Data includes: * Sensitive Personally Identifiable Information–Information relating to an individual that reasonably identifies the individual and, if compromised, could cause significant harm to that individual or to Penn. Examples may include, but are not limited to: Social Security numbers, credit card numbers, bank account information, student grades or disciplinary information, salary or employee performance information, donations, patient health information, information Penn has promised to keep confidential, and account passwords or encryption keys used to protect access to Confidential University Data. * Proprietary Information–Data, information, or intellectual property in which the University has an exclusive legal interest or ownership right, which, if compromised could cause significant harm to Penn. Examples may include, but are not limited to, business planning, financial information, trade secret, copyrighted material, and  software or comparable material from a third party when the University has agreed to keep such information confidential. * Any other data the disclosure of which could cause significant harm to Penn or its constituents. Security Incident. There are two types of Security Incidents: Computer Security Incidents and Confidential Data Security Incidents. * A Computer Security Incident is any event that threatens the confidentiality, integrity, or availability of University systems, applications, data, or networks. University systems include, but are not limited to: servers, desktops, laptops, workstations, PDAs, network servers/processors, or any other electronic data storage or transmission device. * A Confidential Data Security Incident is a subset of Computer Security Incidents that specifically threatens the security or privacy of Confidential University Data. User. A Penn user is any faculty, staff, consultant, contractor, student, or agent of any of the above. VII. Scope This policy applies to all Users. It applies to any computing devices owned or leased by the University of Pennsylvania that experience a Computer Security Incident. It also applies to any computing device regardless of ownership, which either is used to store Confidential University Data, or which, if lost, stolen, or compromised, and based on its privileged access, could lead to the unauthorized disclosure of Confidential University Data. Examples of systems in scope include, but are not limited to, a User’s personally owned home computer that is used to store Confidential University Data, or that contains passwords that would give access to Confidential University Data. This policy does not cover incidents involving the University of Pennsylvania Health System (UPHS) information systems, which has a separate incident response policy. ISC Information Security will coordinate with UPHS as appropriate when UPHS computing devices, data, or personnel are involved. VIII. Statement of Policy A. Overview of Penn’s Incident Response Program All Computer Security Incidents must be reported to ISC Information Security promptly. See Section B below. All Confidential Data Security Incidents must: a. Generate the creation of an Immediate Response Team, as designated by the  Information Security Officer (ISO), on a per incident basis. See Section C below. b. Follow appropriate Incident Handling procedures. See Sections C and D below. iii. ISC Information Security, under the direction of the Vice President for Information Systems and Computing (VP-ISC) is responsible for logging, investigating, and reporting on security incidents. See Sections D and E below. B. Identifying and Reporting Computer Security Incidents i. Users and Local Support Providers (LSPs). In the event that a User or an LSP detects a suspected or confirmed Computer Security Incident, the User must report it to his or her Local Security Officer or IT Director for issues including but not limited to viruses, worms, local attacks, denial of service attacks, or possible disclosure of Confidential University Data. ii. Local IT Management. Local IT Management must notify ISC Information Security of all Computer Security Incidents, except for categories of incidents that ISC Information Security may designate in Appendix I of this policy. iii. ISC Information Security. ISC Information Security shall notify appropriate systems administrators and other personnel of all emergency and attack incidents, as well as all suspicious activity incidents when it believes that an administrator’s system is at risk. The system’s administrators will then work with ISC Information Security to properly address the incident and minimize the risk of future occurrences. C. Immediate Response Team i. Purpose. The purpose of each Immediate Response Team is to supplement Penn’s information security infrastructure and minimize the threat of damage resulting from Computer Security Incidents. ii. Per Incident Basis. An Immediate Response Team shall be created for Confidential Data Security Incidents. iii. Membership. Membership on the Immediate Response Team shall be as designated by the ISO. In most cases, members shall include a representative from ISC Information Security and from the affected School or Center’s technical and management staff. iv. Responsibilities. Responsibilities of the Immediate Response Team are to assess the incident and follow incident handling procedures, appropriate to the incident as determined by the ISO. v. Confidentiality. Immediate Response Team members will share information about security incidents beyond the Immediate  Response Team only on a need-to-know basis, and only after consultation with all other team members. D. Incident Handling. For incidents requiring the formation of an Immediate Response Team, the following is a list of response priorities that should be reviewed and followed as recommended by the ISO. The most important items are listed first: i. Safety and Human Issues. If an information system involved in an incident affects human life and safety, responding to any incident involving any life-critical or safety-related system is the most important priority. ii. Address Urgent Concerns. Schools and Centers may have urgent concerns about the availability or integrity of critical systems or data that must be addressed promptly. ISC Information Security shall be available for consultation in such cases. iii. Establish Scope of Incident. The Immediate Response Team shall promptly work to establish the scope of the incident and to identify the extent of systems and data affected. If it appears that personally identifiable information may have been compromised, the Immediate Response Team shall immediately inform the VP-ISC and the Chief Privacy Officer (CPO). iv. Containment. Once life-critical and safety issues have been resolved, the Immediate Response Team shall identify and implement actions to be taken to reduce the potential for the spread of an incident or its consequences across additional systems and networks. Such steps may include requiring that the system be disconnected from the network. v. Develop Plan for Preservation of Evidence. The Immediate Response Team shall develop a plan promptly upon learning about an incident for identifying and implementing appropriate steps to preserve evidence, consistent with needs to restore availability. Preservation plans may include preserving relevant logs and screen captures. The affected system may not be rebuilt until the Immediate Response Team determines that appropriate evidence has been preserved. Preservation will be addressed as quickly as possible to restore availability that is critical to maintain business operations. vi. Investigate the Incident. The Immediate Response Team shall investigate the causes of the incident and future preventative actions. During the investigation phase, members of the incident response team will attempt to determine exactly what happened during the incident, especially the vulnerability that made the incident possible. In short, investigators will attempt to answer the following questions: Who? What? Where? When? How? vii. Incident-Specific Risk  Mitigation. The Immediate Response Team shall identify and recommend strategies to mitigate risk of harm arising from the incident, including but not limited to reducing, segregating, or better protecting personal, proprietary, or mission critical data. viii. Restore Availability. Once the above steps have been taken, and upon authorization by the Immediate Response Team, the availability of affected devices or networks may be restored. ix. Penn-Wide Learning. The Immediate Response Team shall develop and arrange for implementation of a communications plan to spread learning from the security incident throughout Penn to individuals best able to reduce risk of recurrence of such incident. E. Senior Response Team (SRT). If the ISO or CPO in their judgment believe that the incident reasonably may cause significant harm to the subjects of the data or to Penn, each may recommend to the VP-ISC or Associate Vice President for Audit, Compliance and Privacy (AVP-OACP) that a Senior Response Team be established. The Senior Response Team shall be comprised of senior-level officials as designated by the VP-ISC or AVP-OACP. The Senior Response Team shall: i. Establish whether additional executive management should be briefed and the plan for such briefing. ii. Determine, with final approval by the General Counsel, whether Penn shall make best efforts to notify individuals whose personal identifiable information may have been at risk. In making this determination, the following factors shall be considered: a. legal duty to notify b. length of compromise c. human involvement d. sensitivity of data e. existence of evidence that data was accessed and acquired f. concerns about personnel with access to the data g. existence of evidence that machine was compromised for reasons other than accessing and acquiring data h. additional factors recommended for consideration by members of the Immediate Response Team or the Senior Response Team. iii. Review and approve any external communication regarding the incident. F. Documentation i. Log of security incidents. ISC Information Security shall maintain a log  of all reportable security incidents recording the date, School or Center affected, whether or not the affected machine was registered as a critical host, the type of Confidential University Data affected (if any), number of subjects (if applicable), and a summary of the reason for the intrusion, and the corrective measure taken. ii. Critical Incident Report. ISC Information Security shall issue a Critical Incident Report for every reportable security incident affecting machines qualifying as Critical Hosts, or other priority incidents in the judgment of ISC Information Security describing in detail the circumstances that led to the incident, and a plan to eliminate the risk. iii. Annual Summary Report. ISC Information Security shall provide annually for the VP-ISC and AVP-OACP a report providing statistics and summary-level information about all significant incidents reported, and providing recommendation s and plans to mitigate known risks. IX. Best Practices A. Preserving Evidence: It is essential to consult Penn Information Security when handling Computer Security Incidents. However, if Information Security is not available for emergency consultation, the following practices are recommended: i. Generally, if it is necessary to copy computer data to preserve evidence for an incident, it is a good idea to use bit-wise file-system copy utilities that will produce an exact image, (e.g.UNIX dd) rather than to use file level utilities which can alter some file meta-data. ii. When making forensic backups, always take a cryptographic hash (such as an SHA-1 hash) of both the original object and of the copied object to verify the authenticity of the copy. Consult your System Administrator if you have questions. iii. Assigning members to an Immediate Response Team: In cases where an incident involves an investigation into misconduct, the School or Center should consider carefully whom to assign to the Immediate Response Team. For example, one may not wish to assign an IT professional who works closely with the individual(s) being investigated. X. Compliance A. Verification: ISC Information Security and the Office of Audit, Compliance and Privacy will verify any known computing security incidents as having been reported and documented as defined by this policy. B. Notification: Violations of this policy will be reported by ISC Security  and the Office of Audit, Compliance and Privacy to the Senior Management of the Business Unit affected. C. Remedy: The incident will be recorded by ISC Information Security and any required action to mitigate the harmful affects of the attack will be initiated in cooperation with the Business Unit Security Officer/Liaison. D. Financial Implications: The owner of the system shall bear the costs associated with ensuring compliance with this policy. E. Responsibility: Responsibility for compliance with this policy lies with the system administrator, system owner, and Business Unit’s Senior Manager. F. Time Frame: All incidents involving critical hosts systems and networks must be reported immediately. All other incidents should be reported within one business day of determining something has occurred. G. Enforcement: Compliance with this policy will be enforced by disconnecting any machines that may compromise the University network, or other machines with Confidential University Data. Workforce members not adhering to the policy may be subject to sanctions as defined by University policies. H. Appeals: Appeals are decided by the Vice President for Information Systems and Computing. XI. References 1. PennNet Computer Security Policy at www.net.isc.upenn.edu/policy/approved/20040524-hostsecurity.html 2. Critical PennNet Host Security Policy at www.net.isc.upenn.edu/policy/approved/20000530-hostsecurity.html 3. Policy on Computer Disconnection from PennNet at www.upenn.edu/computing/policy/disconnect.html 4. Adherence to University Policy at www.hr.upenn.edu/policy/policies/001.asp 5. Policy on Security of Electronic Protected Health Information (ePHI) at www.upenn.edu/computing/security/policy/ePHI_Policy.html Appendix I The following category of incidents need not be reported to Penn Information Security: * Unsuccessful network scans

tv-dont use this paper :: essays research papers

In Bill Mckibben essay â€Å"Daybreak† he writes about how TV has changed the way we look at the world. A little less than half of all American’s get â€Å"most of their information from television†. There are some things that people would never see in their life if it wasn’t for TV, but there are things that people could go without seeing at times too. TV is one of the greatest things ever to happen to some people and the worst for others. For some people television is the best way to take part in the world. Many American’s watch 7 hours of TV in one day, some people think the best way to live and learn is outside the living room and in the wilderness. Some people learn more when they’re out in nature, that’s what there into. Others do better in the house watching TV. MiKibben had friends tape every channel on the Fairfax network for 24 hours. Then he spent 10 hours a day for 2 months watching TV. After watching all the channels, he then went and spent two days on Crow Mountain watching nature. He found that there are things in nature that you would never get the whole effect of watching them on television. Then there are things on TV you would never even see without watching TV. I myself use both of them in everyday life. TV is a way for me to see what’s going on in the world. I watch TV three to fours a day. It goes from MTV to ESPN to the News. I do watch a lot of movies. I can see how people think TV is bad, and don’t want to have anything to do with it. There are shows that could be taken off the air but at the same time TV gives people a glimpse of things in the world that they would never see in real life. To get away from all the TV and things that go on in the world is the wilderness. Its goes the same way for the wilderness as it does for TV. There are things in the wilderness that you would never see or experience on TV. All people need to do is find a happy medium and use both to benefit themselves. I would rather go out and spend the day in the woods then sit home and watch TV there is some people that would rather stay inside.

Flowers for Algernon and The Garden of Eden Essay

Daniel Keyes’s fictional story, â€Å"Flowers for Algernon†, drew on themes, patterns of events, and character types from the Biblical story of the Garden of Eden. Both stories had a mutual theme: Ignorance is bliss. Both stories also shared a similar pattern of events. Charlie Gordon, the protagonist in â€Å"Flowers for Algernon†, and Adam and Eve, the main characters in the Garden of Eden, all started out in a state of innocence, unaware of evil, until they were encouraged to become smarter. After they had gained intelligence, their eyes were opened to all of the badness in the world, and they suffered the consequences. There were also similarities in the characters in both stories, such as between the Serpent and Miss Kinnian and between Eve and Algernon. Daniel Keyes rendered the material new by changing the setting, the characters, and the events of the story to something much more modern. In â€Å"Flowers for Algernon†, Charlie wanted to become smart, but once he did, he realized that people used to make fun of him, and most people stopped talking to him as often as they used to, either because they were scared of him or couldn’t understand him. Algernon died, and Charlie lost all of his intelligence. In the Garden of Eden, God warned Adam and Eve not to eat from the tree of the knowledge of good and evil, but they didn’t listen. The serpent convinced Eve to eat the forbidden fruit, and then Eve convinced Adam to eat it as well. When they ate the fruit, they gained knowledge and wisdom, became aware of evilness, and realized they were naked. God condemned them to a life of suffering and eventually death. The common theme of these two stories is ignorance is bliss. Sometimes it’s better to know nothing than something. The pattern of events in â€Å"Flowers for Algernon† mirror those of the Garden of Eden. In the Garden of Eden, God created Adam and Eve. They were completely innocent and pure, but not perfect. God warned them not to eat from the tree of the knowledge of good and evil. The evil serpent convinced Eve to eat the forbidden fruit anyway. When Adam and Eve ate from the tree of knowledge, their eyes were opened, and they gained knowledge and wisdom, but they were also exposed to evil, and they felt naked. Their state of innocence was lost. When God found out about this, He punished Adam and Eve. In â€Å"Flowers for Algernon†, Charlie Gordon had a disability and lacked intelligence. Miss Kinnian persuaded Charlie to go through with the operation. He agreed to undergo the surgery that the doctors thought would triple his intelligence, even though he was aware of the risks involved. The operation made Charlie incredibly smart, but it also made him aware that people made fun of him. At one point, Charlie stated that he felt as if he was naked. His intelligence eventually deteriorates, and Algernon dies. In both stories, the main characters start off in a state of ignorance, are persuaded to increase their intelligence, decide to gain knowledge, despite knowing the risks involved, and then they have to pay the consequences. Some of the characters in â€Å"Flowers for Algernon† and the Garden of Eden are very similar. For example, Charlie, Adam, and Eve are similar because they are the main characters, they started out in a state of ignorance, and they all received knowledge. Secondly, the serpent and Miss Kinnian are alike because they both persuaded the main characters to become smarter. Lastly, Eve and Algernon were both the first characters to acquire knowledge. Daniel Keyes rendered the material new by changing the setting, the characters, and the events. The Garden of Eden happened in the beginning, while â€Å"Flowers for Algernon† took place in the 20th century. Instead of a talking snake encouraging somebody to eat magical fruit, Daniel Keyes used Miss Kinnian to persuade Charlie to do the operation. Thirdly, in the Garden of Eden, the forbidden fruit gave knowledge to Adam and Eve, but in Flowers for Algernon, an operation caused Charlie to become more intelligent. Themes, patterns of events, and character types found in Flowers for Algernon mirror those found in the Biblical story of the Garden of Eden. The stories both share the same theme: Ignorance is bliss. They both have similar patterns of events: The main characters start out in a state of innocence and ignorance, then they are persuaded to increase their intelligence. The main characters agreed, despite the risks involved. The main characters had to face the consequences of receiving knowledge. Adam, Eve, and Charlie, the serpent and Miss Kinnian, and Eve and Algernon all mirror each other. Daniel Keyes modernized the Biblical story of the Garden of Eden by changing the  setting, the characters, and the events, although the overall theme, patterns of events, and types of characters are similar in both stories.

Ooad Lab Manual

Ex. no: 1 STUDY OF UML DIAGRAMS Date: UML DIAGRAMS There are three classifications of UML diagrams: †¢ Behavior diagrams. A type of diagram that depicts behavioral features of a system or business process. This includes activity, state machine, and use case diagrams as well as the four interaction diagrams. †¢ Interaction diagrams. A subset of behavior diagrams which emphasize object interactions. This includes communication, interaction overview, sequence, and timing diagrams. †¢ Structure diagrams. A type of diagram that depicts the elements of a specification that are irrespective of time. This includes class, composite structure, component, deployment, object, and package diagrams. |Diagram |Description |Learning Priority | |Activity Diagram |Depicts high-level business processes, including data flow, or to model the |High | | |logic of complex logic within a system. | |Class Diagram |Shows a collection of static model elements such as classes and types, their |High | | |contents, and their relationships. | | |Communication Diagram |Shows instances of classes, their interrelationships, and the message flow |Low | | |between them. Communication diagrams typically focus on the structural | | | |organization of objects that send and receive messages. Formerly called a | | | |Collaboration Diagram. | | |Component Diagram |Depicts the components that compose and application, system, or enterprise. |Medium | | |The components, their interrelationships, interactions, and their public | | | |interfaces are depicted. | |Composite Structure Diagram |Depicts the internal structure of a classifier(such as a class, component, or|Low | | |use case), including the interaction points of the classifier to other parts | | | |of the system. | | |Deployment Diagram |Shows the execution architecture of systems. This includes nodes, either |Medium | | |hardware or software execution environments, as well as the middleware | | | |connecting them. | | |Interaction Overview Diagram |A variant of an activity diagram which overviews the control flow within a |Low | | |system or business process. Each node/activity within the diagram can | | | |represent another interaction diagram. | |Object Diagram |Depicts objects and their relationships at a point in time, typically a |Low | | |special case of either a class diagram or a communication diagram. | | |Package Diagram |Show how model elements are organized into packages as well as the |Low | | |dependencies between packages. | |Sequence Diagram |Models the sequential logic, in effect the time ordering of messages between |High | | |classifiers. | | |State Machine Diagram |Describes the states an object or interaction may be in, as well as the |Medium | | |transitions between states. Formerly referred to as a state diagram, state | | | |chart diagr am, or a state-transition diagram. | |Timing Diagram |Depicts the change in state or condition of a classifier instance or role |Low | | |over time. Typically used to show the change in state of an object over time | | | |in response to external events. | | |Use Case Diagram |Shows use cases, actors, and their interrelationships. |Medium | USE CASE DIAGRAM: A use case diagram is a type of behavioral diagram defined by the Unified Modeling Language (UML). Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors, their goals- represented as use cases- and any dependencies between those use cases. Use case diagram depict: †¢ Use cases. A use case describes a sequence of actions that provide something of measurable value to an actor and is drawn as a horizontal ellipse. †¢ Actors. An actor is a person, organization, or external system that plays a role in one or more interactions with your system. Actors are drawn as stick figures. †¢ Associations. Associations between actors and use cases are indicated in use case diagrams by solid lines. An association exists whenever an actor is involved with an interaction described by a use case. Associations are modeled as lines connecting use cases and actors to one another, with an optional arrowhead on one end of the line. The arrowhead is often used to indicating the direction of the initial invocation of the relationship or to indicate the primary actor within the use case. The arrowheads are typically confused with data flow and as a result I avoid their use. System boundary boxes (optional). You can draw a rectangle around the use cases, called the system boundary box, to indicate the scope of your system. Anything within the box represents functionality that is in scope and anything outside the box is not. System boundary boxes are rarely used, although on occasion I have used them to identify which use cases will be delivered in each major release of a system. †¢ Packages (o ptional). Packages are UML constructs that enable you to organize model elements (such as use cases) into groups. Packages are depicted as file folders and can be used on any of the UML diagrams, including both use case diagrams and class diagrams. I use packages only when my diagrams become unwieldy, which generally implies they cannot be printed on a single page, to organize a large diagram into smaller ones. [pic] RELATIONSHIPS IN USE CASE DIAGRAM: Three relationships among use cases are supported by the UML standard, which describes graphical notation for these relationships. Include In one form of interaction, a given use case may include another. The first use case often depends on the outcome of the included use case. This is useful for extracting truly common behaviors from multiple use cases into a single description. The notation is a dashed arrow from the including to the included use case, with the label â€Å"†. This usage resembles a macro expansion where the included use case behavior is placed inline in the base use case behavior. There are no parameters or return values. Extend In another form of interaction, a given use case, (the extension) may extend another. This relationship indicates that the behavior of the extension use case may be inserted in the extended use case under some conditions. The notation is a dashed arrow from the extension to the extended use case, with the label . This can be useful for dealing with special cases, or in accommodating new requirements during system maintenance and extension. To make the points at which extension may occur explicit extension points may be defined in use cases which are listed in a compartment below the use case name. Generalization In the third form of relationship among use cases, a generalization/ specialization relationship exists. A given use case may be specialized form of an existing use case. The notation is a solid line ending in a hollow triangle drawn from the specialized to the more general use case. This resembles the object-oriented concept of sub-classing, in practice it can be both useful and effective to factor common behaviors, constraints and assumptions to the general use case, describe them once, and deal same as except details in the specialized cases. SEQUENCE DIAGRAM: The well-known Message Sequence Chart technique has been incorporated into the Unified Modeling Language (UML) diagram under the name of Sequence Diagram. A sequence diagram shows, as parallel vertical lines, different processes or objects that live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order in which they occur. This allows the specification of simple runtime scenarios in a graphical manner. Sequence diagrams are typically used to model: 1. Usage scenarios. A usage scenario is a description of a potential way your system is used. The logic of a usage scenario may be part of a use case, perhaps an alternate course. It may also be one entire pass through use case, such as the logic described by the basic course of action or a portion of the basic course of action, plus one or more alternate scenarios. The logic of a usage scenario may also be a pass through the logic contained in several use cases. For example, a student enrolls in the university, and then immediately enrolls in three seminars. 2. The logic of methods. Sequence diagrams can be used to explore the logic of a complex operation, function, or procedure. One way to think of sequence diagrams, particularly highly detailed diagrams, is a visual object code. 3. The logic of services. A service is effectively a high-level method, often one that can be invoked by a wide variety of clients. This includes web-services as well as business transactions implemented by a variety of technologies such as CICS/COBOL or CORBA-compliant object request brokers (ORBs). [pic] ACTIVITY DIAGRAM: In the Unified Modeling Language, an activity diagram represents the business and operational step-by-step workflows of components in a system. An activity diagram shows the overall flow of control. Describing the basic notations: †¢ Initial node. The filled in circle is the starting point of the diagram. An initial node isn’t required although it does make it significantly easier to read the diagram. †¢ Activity final node. The filled circle with a border is the ending point. An activity diagram can have zero or more activity final nodes. †¢ Activity. The rounded rectangles represent activities that occur. An activity may be physical, such as Inspect Forms, or electronic, such as Display Create Student Screen. †¢ Flow/edge. The arrows on the diagram. Although there is a subtle difference between flows and edges I have never seen a practical purpose for the difference although I have no doubt one exists. I’ll use the term flow. Fork. A black bar with one flow going into it and several leaving it. This denotes the beginning of parallel activity. †¢ Join. A black bar with several flows entering it and one leaving it. All flows going into the join must reach it before processing may continue. This denotes the end of parallel processing. †¢ Condition . Text such as [Incorrect Form] on a flow, defining a guard which must evaluate to true in traverse the node. †¢ Decision. A diamond with one flow entering and several leaving. The flows leaving include conditions although some modelers will not indicate the conditions if it is obvious. Merge. A diamond with several flows entering and one leaving. The implication is that one or more incoming flows much reach this point until processing continues, based on any guards on the outgoing flow. †¢ Partition. Activity Diagram is organized into many partitions, also called swim lanes, indicating who/what is performing the activities (the Applicant, Registrar, or System). †¢ Sub-activity indicator. The rake in the bottom corner of an activity, such as in the Apply to University activity, indicates that the activity is described by a more finely detailed activity diagram. †¢ Flow final. The circle with the X through it. This indicates that the process stops at this point. [pic] CLASS DIAGRAM: In the Unified Modeling Language (UML), a class diagram is a type of static structure diagram that describes the structure of a system by showing the system’s classes, their attributes, and the relationships between the classes. Relationships A relationship is general term covering the specific types of logical connections found on class and object diagrams. UML shows the following relationships: †¢ Instance-Level Relationships o Link A Link is the basic relationship among objects. It is represented as a line connecting two or more object boxes. It can be shown on an object diagram or class diagram. A link is an instance or an association. o Association An Association represents a family of links. Binary associations (with two ends) are normally represented as a line, with each end connected to a class box. Higher order associations can be drawn with more than two ends. In such cases, the ends are connected to a central diamond. An association can be named, and the ends of an association can be adorned with role names, ownership indicators, multiplicity, visibility, and other properties. There are five different types of association. Bi-directional and uni-directional associations are the most common ones. For instance, a flight class is associated with a plane class bi-directionally. Associations can only be shown on class diagrams. o Aggregation Class diagram showing Aggregation between two classes Aggregation is a variant of the â€Å"has a† or association relationship; composition is more specific than aggregation. As a type of association, an aggregation can be named and have the same adornments that an association can. However, an aggregation may not involve more than two classes. Aggregation can occur when a class is a collection or container of other classes, but where the contained classes do not have a strong life cycle dependency on the container—essentially, if the container is destroyed, its contents are not. In UML, it is graphically represented as a clear diamond shape on the containing class end of the tree of lines that connect contained class(es) to the containing class. o Composition Composition is a stronger variant of the â€Å"has a† or association relationship; composition is more specific than aggregation. Composition has a strong life cycle dependency between instances of the container class and instances of the contained class(es): If the container is destroyed, every instance that it contains is destroyed as well. The UML graphical representation of a composition relationship is a filled diamond shape on the containing class end of the tree of lines that connect contained class(es) to the containing class. o Differences between Composition and Aggregation The whole of a composition must have a multiplicity of 0.. 1 or 1, indicating that a part must be for only one whole. The whole of an aggregation may have any multiplicity. When attempting to represent real-world whole-part relationships, e. g. , an engine is part of a car, the composition relationship is most appropriate. However, when representing a software or database relationship, e. g. , car model engine ENG01 is part of a car model CM01, an aggregation relationship is best, as the engine, ENG01 may be also part of a different car model, CM02. This is often called a â€Å"catalog† relationship. †¢ Class Level Relationships o Generalization Class diagram showing generalization between one super class and two subclasses The generalization relationship indicates that one of the two related classes (the subtype) is considered to be a specialized form of the other (the supertype) and supertype is considered as GENERALIZATION of subtype. In practice, this means that any instance of the subtype is also an instance of the supertype. The relationship is most easily understood by the phrase ‘A is a B’. The UML graphical representation of a Generalization is a hollow triangle shape on the supertype end of the line (or tree of lines) that connects it to one or more subtypes. The generalized relationship is also known as the inheritance or â€Å"is aâ€Å" relationship. The supertype in the generalization relationship is also known as the â€Å"parent†, super class, base class, or base type. The subtype in the generalization relationship is also known as the â€Å"child’, subclass, derived class, derived type, inheriting class, or inheriting type. †¢ Generalization-Specialization relationship A is a type of B E. g. †an oak is a type of tree†, â€Å"a sedan is a type of vehicle† o Realization In UML modeling, a realization relationship is relationship between model elements, in which one model element (the client) realizes the behavior that the other model element (the supplier) specifies. A realization is displayed in the diagram editor as a dashed line with an unfilled arrowhead towards the supplier. †¢ General Relationship o Dependency(UML) A dependency exists between two defined elements if a change to the definition of one would result in a change to the other. This is indicated by a dashed pointing from the dependent to the independent element. Several named varieties exist. A dependency can be between instances, class, or both. †¢ Multiplicity The association relationship indicates that (at least) one of the two related classes makes reference to the other. In contrast with the generalization relationship, this is most easily understood through the phrase ‘A has a B’{a mother cat has kittens, kittens have a mother cat}. The UML representation of an association is a line with an optional arrowhead indicating the role of the object(s) in the relationship, and an optional notation at each end indicating the multiplicity of instances of that entity ( the number of objects that participate in the association). Common multiplicities are: Indicator Meaning 0.. No instances, or one instance(optional, may) 1 Exactly one instance 0.. * or * Zero or more instances 1.. * One or more instances(at least one) n Exactly n instances(n>1) 0.. n Zero or n instances(n>1) 1.. n One or n instances(n>1) [pic] COMPONENT DIAGRAM: In the Unified Modeling Language, a component diagram depicts how a software system is split up into physical components and shows the dependencies among these components. Physical components could be, for example, files, header, link libraries, modules, executables, or packages. Component diagrams can be used to model and document any system’s architecture. Component diagrams are particularly useful with larger teams. Your initial architectural modeling efforts during cycle 0 should focus on identifying the initial architectural landscape for your system. UML component diagrams are great for doing this as they enable you to model the high-level software components, and more importantly the interfaces to those components. Once the interfaces are defined, and agreed to by your team, it makes it much easier to organize the development effort between sub teams. You will discover the need to evolve the interfaces to reflect new requirements or changes to your design as your project progresses, changes that need to be negotiated between the sub teams and then implemented appropriately. [pic] INTRODUCTION TO RATIONAL ROSE Rational rose Rational Rose is an object-oriented Unified Modeling Language(UML) software design tool intended for visual modeling and component construction of enterprise-level software applications. In much the same way a theatrical director blocks out a play, a software designer uses Rational rose to visually create(model) the framework for an application by blocking out classes with actors(stick figures), use case elements(ovals), objects(rectangles) and messages/relationships(arrows) in a sequence diagram using drag-and-drop symbols. Rational Rose documents the diagram as it is being constructed and then generates code in the designer’s choice of C++, Visual Basic, Java, Oracle8,CORBA or Data Definition Language. Two popular features of Rational Rose are its ability to provide iterative development and round-trip engineering. Rational Rose allows designers to take advantage of iterative development(sometimes called evolutionary development) because the new application can be created in stages with the output of one iteration becoming the input to the next. (This is in contrast to waterfall development where the whole project is completed from start to finish before a user gets to try it out. ) Then, as the developer begins to understand how the components interact and makes modifications in the design, Rational Rose can perform what is called â€Å"round-trip engineering† by going back and updating the rest of the model to ensure the code remains consistent. Rational rose is extensible, with downloadable add-ins and third-party applications. It supports COM/DCOM(ActiveX), JavaBeans, and Corba component standards. Views in UML/Rational Rose There are four views for a model created in Rational Rose, each representing the system from a different point of view. The Use Case View The use case view contains the diagrams used in analysis(use case, sequence, and collaboration), and all the elements that compromise these diagrams(e. g. , actors). More recent versions of Rational Rose also allow for additional documentation in the form of word-processed documents and/or URLs to Web-based materials. The purpose of the use case view is to envisage what the system must do, without dealing with the specifics of how it will be implemented. Logical View The logical view contains the diagrams used in object design(class diagrams and state transition diagrams). It offers a detailed view of how the system envisaged in the use case view will be implemented. The basic element in this view is the class, which includes an outline of its attributes and operations. This directly corresponds to a class created in your chosen implementation language. From the logical view, skeletal code can be generated for implementation into a computer language. More recent versions of Rational Rose not only can generate skeletal code for Visual C++, Visual Java, or Visual BASIC, but also reverse engineer programs created in these languages into Rational Rose models. This allows existing components to be included in documented models, if there is access to the source code. In addition, changes that need to be made during implementation can be reflected in the documentation of the design model. Component View The component view is a step up from the logical view and contains diagrams used in system design(component diagrams). This includes information about the code libraries, executable programs, runtime libraries, and other software components that comprise the completed systems. Components can be pre-existing; for example, a Windows program in Visual C++ will utilize Microsoft Foundation Class to provide the framework for the Windows interface. Components that do not exist and need to be created by the developers will have to be designed in the logical view. Deployment View The deployment view illustrates how the completed system will be physically deployed. This view is necessary for complex applications in which a system will have different components located on different machines. For example, interface components may be located on a user machine while other components may be located on a network server. INTRODUCTION TO VISUAL BASIC Visual Basic (VB) is an event driven programming language and associated development environment from Microsoft for its COM programming model. Visual Basic was derived from BASIC and enables the rapid application development(RAD) of graphical user interface(GUI) applications, access to databases using DAO, RDO, or ADO, and creation of ActiveX controls and objects. Scripting languages such as VBA and VBScript are syntactically similar to Visual Basic, but perform differently. A programmer can put together an application using the components provided with Visual Basic itself. Programs written in Visual Basic can also use the Windows API, but doing so requires external function declarations. LANGUAGE BASICS: Visual Basic was designed to be easy to learn and use. The language not only allows programmers to create simple GUI applications, but can also develop fairly complex applications as well. Programming in VB is a combination of visually arranging components or controls on a form, specifying attributes and actions of those components, and writing additional lines of code for more functionality. Since default attributes and actions are defined for the components, a simple program can be created without the programmer having to write many lines of code. Performance problems were experienced by earlier versions, but with faster computers and native code compilation this has become less of an issue. Forms are created using drag and drop techniques. A tool is used to place controls (e. g. , text boxes, buttons, etc. ) on the form (window). Controls have attributes and event handlers associated with them. Default values are provided when the control is created, but may be changed by the programmer. Many attribute values can be modified during run time based on user actions or changes in the environment, providing a dynamic application. For example, code can be inserted into the form resize event handler to reposition a control so that it remains centered on the form, expands to fill up the form, etc. By inserting code into the event handler for a keypress in a text box, the program can automatically translate the case of the text being entered, or even prevent certain characters from being inserted. Unlike many other programming languages, Visual Basic is generally not case sensitive, although it will transform keywords into a standard case configuration and force the case of variable names to conform to the case of the entry within the symbol table entry. String comparisons are case sensitive by the default, but can be made case insensitive if so desired. The Visual Basic compiler is shared with other Visual Studio languages(C, C++), but restrictions in the IDE do not allow the creation of some targets (Windows model DLL’s) and threading models. Result: Thus the UML diagrams and introduction to Visual Basic was studied. PASSPORT AUTOMATION SYSTEM Ex. No: 2. a Date: Aim: To Study the software requirements specification for passport automation system. Problem Statement Passport Automation System is used in the effective dispatch of passport to all of the applicants. This system adopts a comprehensive approach to minimize the manual work and schedule resources, time in a cogent manner. The core of the system is to get the online registration form (with details such as name, address etc. ,)   filled by the applicant whose testament is verified for its genuineness by the Passport Automation System with respect to the already existing information in the database. This forms the first and foremost step in the processing of passport application. After the first round of verification done by the system, the information is in turn forwarded to the regional administrator's (Ministry of External Affairs) office. The application is then processed manually based on the report given by the system, and any forfeiting identified can make the applicant liable to penalty as per the law. The system also provides the applicant the list of available dates for appointment to ‘document verification' in the administrator's office, from which they can select one. The system forwards the necessary details to the police for its separate verification whose report is then presented to the administrator. The administrator will be provided with an option to display the current status of application to the applicant, which they can view in their online interface. After all the necessary criteria has been met, the original information is added to the database and the passport is sent to the applicant. Software Requirements Specification 1. 0 Introduction Passport Automation System is an interface between the Applicant and the Authority responsible for the Issue of Passport. It aims at improving the efficiency in the Issue of Passport and reduce the complexities involved in it to the maximum possible extent. 1. 1 Purpose If the entire process of ‘Issue of Passport' is done in a manual manner then it would take several months for the passport to reach the applicant. Considering the fact that the number of applicants for passport is increasing every year, an Automated System becomes essential to meet the demand. So this system uses several programming and database techniques to elucidate the work involved in this process. As this is a matter of National Security, the system has been carefully verified and validated in order to satisfy it. 1. 2 Scope †¢ The System provides an online interface to the user where they can fill in their personal details and submit the necessary documents (may be by scanning). The authority concerned with the issue of passport can use this system to reduce his workload and process the application in a speedy manner. †¢ Provide a communication platform between the applicant and the administrator. †¢ Transfer of data between the Passport Issuing Authority and the Local Police for verification of applicant's information. †¢ Users/Applicants will come to know their status of application and the date in which they must subject themselves for manual document verification. 1. Definitions, Acronyms and the Abbreviations  Ã‚  Ã‚     Ã‚  Ã‚   †¢ Administrator – Refers to the super user who is the Central Authority who has been vested with the privilege to manage the entire system. It can be any higher official in the Regional Passport Office of Ministry of External Affairs. †¢ Applicant – One who wishes to obtain the Passport. †¢ PAS – Refers to this Passport Automation System. †¢ HTML – Markup Language used for creating web pages. †¢ J2EE – Java 2 Enterprise Edition is a programming platform and it is the partof the java platform for developing and running distributed java applications. HTTP – Hyper Text Transfer Protocol. †¢ TCP/IP – Transmission Control Protocol/Internet Protocol is the communication protocol used to connect hosts on the Internet. 1. 4 References IEEE Software Requirement Specification format. 1. 5 Technologies to be used †¢ HTML†¢ JSP†¢ Javascript †¢ Java†¢ XML†¢ AJAX 1. 6 Tools to be Used †¢ Eclipse IDE ( Integrated Development Enivronment) †¢ Rational Rose tool ( for developing UML Patterns) 1. 7 Overview SRS includes two sections overall description and specific requirements – Overall description will describe major role of the system components and inter-connections. Specific requirements will describe roles & functions of the actors. 2. 0 Overall Description 2. 1 Product Perspective The PAS acts as an interface between the ‘applicant' and the ‘administrator'. This system tries to make the interface as simple as possible and at the same time not risking the security of data stored in. This minimizes the time duration in which the user receives the passport. 2. 2 Software Interface †¢ Front End Client – The applicant and Administrator online interface is built using JSP and HTML. The Administrators's local interface is built using Java. †¢ Web Server – Glassfish application server(Oracle Corporation). Back End – Oracle database. 2. 3 Hardware Interface The server is directly connected to the client systems. The client systems have access to the database in the server. 2. 4 System Functions †¢ Secure Registration of information by the Applicants. †¢ Schedule the applicants an appointment for manu al verification of original documents. †¢ Panel for Passport Application Status Display by the Administrator. †¢ SMS and Mail updates to the applicants by the administrator. †¢ Administrator can generate reports from the information and is the only authorized personnel to add the eligible application information to the database. . 5 User Characteristics †¢ Applicant – They are the people who desires to obtain the passport and submit the information to the database. †¢ Administrator – He has the certain privileges to add the passport status and to approve the issue of passport. He may contain a group of persons under him to verify   Ã‚  Ã‚     Ã‚  Ã‚     Ã‚  Ã‚   the documents and give suggestion whether or not to approve the dispatch of passport. †¢ Police – He is the person who upon receiving intimation from the PAS, perform a personal verification of the applicant and see if he has any criminal case against him before or at present. He has been vetoed with the power to decline an application by suggesting it to the Administrator if he finds any discrepancy with the applicant. He communicates via this PAS. 2. 6   Constraints †¢ The applicants require a computer to submit their information. †¢ Although the security is given high importance, there is always a chance of intrusion in the web world which requires constant monitoring. †¢ The user has to be careful while submitting the information. Much care is required. 2. 7 Use Case Model Description The usecase model is a representation of the interaction between the users and the system. It captures the goals of the users and the responsibility of the system to the users. It is a special flow of events through the system. Grouping of usecases can manages the complexities and reduce the number of usecases in the package. The usecase model describes the uses of the system and show the courses of events that can be performed. A usecase is an interaction between user and system; it captures the goals of the user and the responsibility of the system to its users. It defines what happens in the system when the usecase is performed. 2. 8   Assumptions and Dependencies The Applicants and Administrator must have basic knowledge of computers and English Language. †¢ The applicants may be required to scan the documents and send. Result: Thus the software requirements specification for passport automation system was studied. Gantt Chart for Passport Automation System Ex No : 2. b Date: Aim: To develop a risk management and project plan for passport automation system using Gantt Chart. Introduction: A Gantt chart is a type of bar chart that illustrates a project schedule. Gantt charts illustrate the start and finish dates of the terminal elements and summary elements of a project. Terminal elements and summary elements comprise the work breakdown structure of the project. Some Gantt charts also show the dependency (i. e. , precedence network) relationships between activities. Gantt charts can be used to show current schedule status using percent-complete shadings and a vertical â€Å"TODAY† line as shown here. [pic] Passport Automation System For the project, the activities considered are: 1. Requirement Analysis 2. Literature Survey and Specification 3. Preliminary Design 4. Detailed Design 5. Testing 6. Operation and Maintenance [pic] Result: Thus the risk management and project plan for passport automation system was designed using Gantt Chart. EX. NO:2 c DATE: PASSPORT AUTOMATION SYSTEM AIM: To analyze and design a system for Passport Automation using Rational Rose tool. 1. PROBLEM STATEMENT To create a software system for the applicant(s), applying for the passport by verifying the information provided by them. 2. OVERALL DESCRIPTION The modules are for 1. Applicant Applicant has to provide the information like Name, Gender, Age, Qualification, Parents’ Name, Communication address, Phone no, etc. Also, they need to provide the DD details. . Passport Issuing Authority This system will verify the details provided by the applicant. And check whether the applicant is provided with passport or not. The details of the applicant are stored in the Database. 3. Database This will store the details of the applicant for future reference. 2. 1 SOFTWARE REQURIEMENTS 1. Rational Rose 2. 2 HARDWARE REQURIMENTS 1. 128MB RAM 2. Pentium III Processor 3. DESIGN 1. USE CASE DIAGRAM [pic] 3. 2 CLASS DIAGRAM [pic] 3. 2 SEQUENCE DIAGRAM [pic] 3. 3 COLLABORATION DIAGRAM [pic] 3. 4 COMPONENET DIAGRAM [pic] JAVA CODING: Database. java ublic class database { private int applicantDetails; public database() { } public void storeTheDetails() { } public void issueDetailsToAuthortiy() { } } Applicant. java public class APPLICANT { private int firstName; private int surname; private int Sex; private int DOB; private int placeOfBirth; private int district; private int qualification; private int height; private int weight; private int presnetAddress; private int permanentAddress; private int fathersName; private int mothersName; private int emailId; private int phoneNumber; private int DDNO; private int DDDATE; ublic passportIssueAuthority thePassportIssueAuthority; } public APPLICANT() { } PassportIssueAuthority. java public class passportIssueAuthority { private int authorityName; private int authorityId; private int work Place; public APPLICANT theAPPLICANT; public database theDatabase; public passportIssueAuthority() {} public void issuePassport() { } public void verify() { } public void cancellation() { } } RESULT: Thus the UML diagrams for Passport Automation System was analyzed and designed using Rational Rose. EXNO:3 DATE:BOOK BANK 1. OBJECTIVE: a. To implement book bank system online. . To provide the students with the information on books and scheduled times of book rental available. c. To ensure validity and security in the online book bank management system. 2. SCOPE OF THE PROJECT: The book bank system project is a software tool created to help and access the students gather required information about the various books in the institution the project is web based interactive application. Focus is laid solely on the book display,schedule,categories,syllabus and payment as per required. 3. PROJECT DESCRIPTION: USER PERSONAL AND CHARACTERISTICS: The target client for our software are students who lively are interested in rental of books be it either from engineering or medical genre in the institution. They can log into our website and browse the courses which they have aspiration to study. The student must register themselves online,which is free. The booking or reservation of the books is online,the detailed description about their book package and necessary terms and condition norms would be emailed to the students registered email address which he/she may provide during the time of registration. PRODUCT PERSPECTIVE: This product requires a web browser which is capable of playing flash media. †¢ This program will not be dependent on any other software and is not a component of another program. †¢ This program does not require any new hardware. 4. REQUIREMENTS: (a). FUNCTIONAL REQUIREMENTS: A functional requirement defines a function of a software system on its component. A function is described as a set of inout ,the behaviour and output. i. A main menu including a brief help section. ii. Login iii. Viewing book details. iv. Displaying details. v. Maintain and update book details. vi. Logout. . REQUIREMENTS: The system should have the requirements of the project. The developer should prepare the requirements of the project. The should prepare the requirements which are need for the software. 2. ANALYSIS: Analyze the requirements whether it provides proper operations/output and performs the task. 3. DESIGN: Project manager should design the layout of the project before going to implement time allocation,cost allocation and staff allocation wil coming under design process. 4. IMPLEMENTATION: After encomposing all the diagrams,we have to generate code for each and every diagrams i. from usecase to deployment. 5. TESTING: Afteer implementing the diagram with domain language,we have to test the particular projects. 6. MAINTAINENCE: The system should be easily updated. The system should utilize t he interchangeable plugins software developed should maintain the cost and time schedule of the project. (b). NON- FUNCTIONAL REQUIREMENTS: Nonfunctional requirements define the needs in terms if performance, logical database requirements, design constraints, standard compliance, reliability, availability, security, maintainability and portability. i. PERFORMANCE REQUIREMENTS: Performance requirements define acceptable response times for system functionality. †¢ The total time for user interface screens will take no longer than two seconds. †¢ The login information shall be verified within the seconds. †¢ Queries shall results within five seconds. ii. DESIGN CONSTRAINTS: The software shall be a standard system running in a windows environment. The system shall be developed using rational enterprise suite and oracle 10i database. iii. RELIABILITY: Specify the factors required to establish the required reliability of the software system at time of delivery. iv. AVAILABILITY: The system should have an availability of 99. 99%. v. PORTABILITY: †¢ The system should be extremely via the usb drive. †¢ The system shall be easy to migrate or backed up via another use drive. vi. MAINTAINABILITY: †¢ The system shall utilize interchangeable plugins. †¢ The system shall be easily updateable for fixes and patches. (c). HARDWERE REQUIREMENTS: |1. |Processor |- |Intel Pentium IV-2. 0 GHZ. | |2. |Hardware |- |40 GB. | |3. |RAM |- |512mb | |4. |DVD RAM |- |1 nos. | | | | |(d). SOFTWARE REQUIREMENTS: | | | |1. |OS |- |Windows XP/vista. | |2. |Front end Tool |- |Rational Rose Enterprise suite. | |3. |Back end Tool |- |MSAccess | | | | | |5. MODULE DISCRIPTION: | | | In this project we have defined different modules to enable the Book Bank system in successful manner. i. REGISTER: The register module contains the application form or registration form which contains following details. †¢ Name, Address, Contact number, E-mail id, Password etc. ii. LOGIN: The Login module contains the form which contain membership name and member password. It includes Username and Password. iii. SEARCH BOOK: The search book module contain list of books, from this list we search for the book which we need. This also contains another field called as categories where can select the category of the book. iv. DISPLAY DETAILS: Display the details about the students particulars, the payments, the books, rental and schedule times for books etc. v. MAINTAIN BOOK DETAILS: The administrator maintains the details of books. vi. LOGOUT: To sign off from the webpage or your account log off. 6. DOMAIN MODEL: A domain model is a visual representation of conceptual classes or real situations object in a domain. In object oriented analysis, the domain model is the most important. †¢ It illustrates the concept in the domain. †¢ It act as a source of inspiration for designing some software objects. 7. PARTIAL LAYERED ARCHITECTURE: Sequence diagram is an interaction overview diagram. It provides a big picture overview of how a set of interaction are related in terms of logic and process flow. This P artial layer architecture shows the interface of the sequence diagram, here the administrator shows the interface by displaying actor symbol. 8. LOGICAL ARCHITECTURE: The Logical architecture is large scale organization of software class into packages, sub system layer, It is called logical architecture because there is no direction about how these elements are display on different operating system. 9. RISK ACTIVITY: †¢ Personal short falls. †¢ Unrealistic schedules and budgets. †¢ Developing the wrong functions and programs. †¢ Developing the wrong user interface. †¢ Continuing stream of requirements changes. †¢ Short falls in externally furnished component. †¢ Real time performance short falls. †¢ Straining computer science capabilities. RISK ASSESSMENT: Figure out what the risks are and what to focus on. †¢ Making a list of all of the potential dangers that will affect the project. †¢ Assessing the probability of occurrence and potential ross of each item listed. RISK CONTROL: †¢ Monitoring the effectiveness of the strategies and the changing levels of risk throughout the project. †¢ T echniques and strategies to migrate the highest ordered risks. 10. GANTT CHART: It describes the time schedule for the planning to complete the corresponding and after completion of core product, what the time is taken for the project action of core product. 11. POST- FUNCTION AND PRE-FUNCTION: MODULE: Registering PRE-FUNCTION: †¢ Login to the website. †¢ Collection the required documents to be submitted for registration. POST-FUNCTION: †¢ Verification of documents submitted. †¢ Conformation email sent accessing that authentication can be prevailed for the individual. MODULE: Display book details PRE-FUNCTION: Analyze the course of semester of logger. POST-FUNCTION: Display the required book details. 12. UML PACKAGE DIAGRAM: A package diagram provides a way to group element. Here we have grouped the 6 main elements of software project grouped the in order register, login, search book. It goes to update and sales record. A package name may be based on tab if the package shows the member of main package. 13. TECHNICAL SERVICES LAYER: Technical service layer describes the relationship between different actors, components of the software process for any admin seek the registration for new visitor. So that the new visitor can login the website and search for book and if need can buy it. 14. DOMAIN SERVICES LAYER: After technical services layer from partial layered architecture, we are going to generate the coding in java or VB the project domain is now finalized in JAVA/VB. 15. USER INTERFACE LAYER: . ADMIN: The administrator is used to register a new visitor for the website. Admin can keep those records update. Admin keep sales record i. e. , now much book is downloaded and how much book is buyed newly with copy write etc. ii. REGISTERED USER: Registered user can search the book whatever needs and can read the book in online. If user is satisfied with this book, can d ownload the book but after payment. iii. VISITOR: The visitor can register the application form and become a member of the website. The visitor can search books and read the boook but he must register to buy or download the book. UML USECASE DIAGRAM: Uml provides use case diagram notation to iilustrate the names of use case and author relationship between them. Use case diagram and case relationship are secondary in use case work use case text document. UML CLASS DIAGRAM: The Uml class diagram is to illustrate class interfaces as their actions. They are used for static object modeling, we have already introduced and used their uml diagram while domain modeling. UML SEQUENCE DIAGRAM: A sequence diagram illustrate a kind of format in which each object interact via message. It is generalize between two or more specialized diagram. PARTIAL LAYER ARCHITECTURE DIAGRAM: Sequence diagram is an interaction overview diagram. It provides a big picture overview of how a set of interaction are related in terms of logic and process flow. This Partial layer architecture shows the interface of the sequence diagram, here the administrator shows the interface by displaying actor symbol UML COLLABRATION DIAGRAM: COLLABRATION diagram illustrate that object interact on a graph or network format in which object can be placed where the diagram. In collaboration diagram the object can be placed in anywhere on the diagram. The collaboration comes from sequence diagram. UML STATE CHART DIAGRAM: A Uml state machine represents the interaction events and states of an object and behavior of an object in reaction to an event.. Transaction shown as allows labeled with their event. It is included with initial pseudo state and fins end state UML ACTIVITY DIAGRAM: A Uml activity diagram shows sequential and parallel activates in a process, work flows, data flows and compiler algorithm. UML COMPONENT DIAGRAM: Components are slightly fuzzy concept in this Uml, because both class and components can be used to model the something. UML DEPLOYEMENT DIAGRAM: Deployment diagram shows the assignment of concrete software artifact to computational nodes. It shows the deployment of software elements to the physical elements. Deployment diagram are useful to communicate or deployment architecture. IMPLEMENTATION: After the completion of UML diagrams for BOOK BANK SYSTEM we should generate the code. Select the tools option from main menu then select the sub option program module in which we are going to generate the code in JAVA/VB/J2EE. Then go ahead and select the generate code option as a result of code generation. TESTING: To perform the testing for the generated code again select the tools option from menu bar and choose quality architecture option a sub window gets opened. We are going to perform Unit Test and Scenario testing for our project. So, select these testing option one by one and testing activity is carried out for all the coding and testing is carried out. CONCLUSION: Thus the project for BOOK BANK SYSTEM has been successfully executed and codes are generated. STOCK MAINTENANCE SYSTEM Ex. No: 4 Date: AIM: To analyze and design a system for Stock Maintenance System using Rational Rose tool. Problem Statement: INVENTORY SYSTEM is a real time application used in the merchant’s day to day system. This is a database to store the transaction that takes places between the Manufacturer, Dealer and the Shop Keeper that includes stock inward and stock outward with reference to the dealer. Here we assume our self as the Dealer and proceed with the transaction as follows: The Manufacturer is the producer of the items and it contains the necessary information of the item such as price per item, Date of manufacture, best before use, Number of Item available and their Company Address. The Dealer is the secondary source of an Item and he purchases Item from the manufacturer by requesting the required Item with its corresponding Company Name and the Number of Items required. The Dealer is only responsible for distribution of the Item to the Retailers in the Town or City. The Shop Keeper or Retailer is the one who is prime source for selling items in the market. The customers get Item from the Shop Keeper and not directly from the Manufacturer or the Dealer. The Stock is the database used in our System which records all transactions that takes place between the Manufacturer and the Dealer and the Dealer and the Retailer. USE CASE DIAGRAM : [pic] ACTIVITY DIAGRAM : [pic] SEQUENCE DIAGRAM : [pic] COLLABORATION DIAGRAM : [pic] COMPONENT DIAGRAM : [pic] CLASS DIAGRAM : [pic] DEPLOYMENT DIAGRAM : [pic] Javacoding: Manufacturer. java public class manufacturer { private int manufacturername; private int companyname; private int dateofmanufactured; private int addres; private int contactno; private int name; public dealer theDealer; public manufacturer() { } public void purchase() { } public void sales() { } } Dealer. java public class dealer { private int dealername; private int dateofitemsreceived; private int address; private int contactnumber; rivate int price; private int noofitemsordered; private int noofitemssold; public manufacturer theManufacturer; public shopkeeper theShopkeeper; public dealer() { } public void purchase() { } public void sales() { } public void showstockdetails() { } } Shopkeeper. java public class shopkeeper { private int shopkeepername; private int address; private int contactnum ber; private int price; private int numberofitemsordered; public dealer theDealer; public shopkeeper() { } public void purchase() { } public void sales() { } } RESULT: Thus the UML diagrams for Stock Maintenance was analyzed and designed using Rational Rose. Ex No: 5 Date: ONLINE COURSE REGISTRATION SYSTEM AIM: To create a system through which students can register to the courses desired by them, using Rational Rose tool. Problem statement ? The system is built to be used by students and managed by an administrator. ? The student and employee have to login to the system before any processing can be done. ? The student can see the courses available to him and register to the course he wants. ? The administrator can maintain the course details and view all the students who have registered to any course. System requirements Rational Rose Software Use-case diagram The course registration system has the following use-cases Login View course details Registration Display details Maintain course details Logout The actors involved in the system are 1. Student 2. Administrator Use-case name: Login The user enters the username and password and chooses if the user is student or administrator. If entered details are valid, the user’s account becomes available. If it is invalid, an appropriate message is displayed to the user. Use-case name: View course details In this use case, a student can search all the courses available to him and choose the best course he wants. The student can view the course duration, faculty and department of the courses he may choose. Use-case name: Registration When a student has successfully chosen a course, he can register to that course. Upon registration, the student’s details are stored in the database. Use-case name: Display details After registration to any course, the student may see the details of his current course. He may wish to know details about fees and other information. The administrator also has the privilege to display details of the the students and the corresponding course for which they have registered. Use-case name: Maintain course details The administrator has to perform the duties of maintaining the course details. Any change to the course structure is maintained by the administrator. Use-case name: Logout After all the desired transactions are made, the user may choose to logout from the system to save all he changes they have made. Use-case diagram for course registration system [pic] Class diagram The class diagram is a graphical representation of all the classes used in the system and their operations, attributes and relationships. The course registration system makes use of the following classes: . Stud(student details) 2. Administrator 1) Stud It consists of the details of all the students present in the database. The attributes present in this class are student id, password, name, age, sex, course and attendance. The object of this class is created as soon as the student registers to a course. The operations available to this class are login (), logout (), confirmation () , register (), and view course details (). 2) Administrator It consists of details of all the courses available to the student. The attributes present in this class are username, password, course fees, fees due, marks, and attendance. The operations available to this class are login (), logout (), ma course details (), display course (), and confirmation (). Class diagram for course registration system [pic] Sequence diagram Sequence and collaboration diagram for login to the system [pic] [pic] Sequence and collabaration diagram for logout [pic] [pic] Sequence and collabaration diagram for registration to a course [pic] [pic] ACTIVITY DIAGRAM : [pic] JAVA CODE: Public class stud { Private int sid; Private string passwd; Private int age; Private int sex; Public admin; Public stud() { } Public void logout() { } Public void confirm() { } RESULT: Thus the Online course registration system was designed and analyzed using Rational Rose. Ex No: 6 Date: ONLINE TICKET RESERVATION SYSTEM (E – Ticket) AIM: To analyze and design a system for Online Ticket Reservation System (E – Ticket) using Rational Rose tool. 1. PROBLEM STATEMENT To book a ticket for a user online ticket reservation system software and to confirm the ticket booking, making the payment, printing the tickets has to designed using Rational Rose tool. . OVERALL DESCRIPTION 1. LOGIN †¢ Before entering the system, users have to login †¢ Get the username and password from existing users. †¢ Give new users the option to sign up. 2. AVAILABILITY †¢ Get the source and destination. †¢ Provide a dropdown box for the date. †¢ Check availability of tickets. 3. RESCHEDULE †¢ If tickets are available, get the number of passengers. †¢ Get the name and age of all passengers. †¢ If tickets are not available, reschedule. 4. PAYMENT DETAILS †¢ Print the cost of the tickets. †¢ Get the payment details from the user. †¢ Confirm the details and the ticket. Display confirmed ticket to the user. USECASE DIAGRAM [pic] ACTIVITY DIAGRAM [pic] CLASS DIAGRAM [pic] SEQUENCE DIAGRAM [pic] COLLABORATION DIAGRAM [pic] STATE CHART DIAGRAM [pic] COMPONENT DIAGRAM [pic] DEPLOYMENT DIAGRAM [pic] Javacoding: Customerdetails. java public class customerdetails { private int name; private int address; private int email; private int age; public booking theBooking; public customerdetails() { } public void book() { } } Booking. java public class booking { private int booking_no; private int date; private int total; private int status; private int name; public payment thePayment; ublic booking() { } public void pay() { } } Payment. java public class payment { private in t date; private int amount; public payment() { } } RESULT: Thus the Online Ticket Reservation System have been designed and verified using Rational Rose Tool. Ex No:7 Date: SOFTWARE PERSONNEL MANAGEMENT SYSTEM AIM: To analyze and design a system for Software Personnel Management System using Rational Rose tool. 2. PROBLEM STATEMENT To compute the gross pay of a person using the software personnel management system software and to add new details to the existing database and update it, using Rational Rose tool. . OVERALL DESCRIPTION The three modules are 1. Login The employee details has to be entered and if needed the details can be edited. 2. Pay slip It contains details such as employee id, employee name, department, experience, and basic pay. 3. View Updated database would be present. The details of the employee can be used for further reference. 2. 1 SOFTWARE REQURIEMENTS: 1. Rational Rose 2. 2 HARDWARE REQURIMENTS: 4. 128MB RAM 5. Pentium III Processor 3. DESIGN USECASE DIAGRAM [pic] CLASS DIAGRAM [pic] SEQUENCE DIAGRAM [pic] COLLABORATION DIAGRAM [pic] SEQUENCE DIAGRAM [pic] COLLABORATION DIAGRAM [pic] ACTIVITY DIAGRAM [pic] JAVA CODING: PAYROLLLOGIN. JAVA public class payrolllogin { private int enterdetails; private int editdetails; public payslip thePayslip; public viewdetails theViewdetails; public payrolllogin() { } public void exit() { } } VIEWDETAILS. JAVA public class viewdetails { private int eid; private int ename; private int dept; private int exp; private int basicpay; private int hra; private int da; private int bpf; private int gpay; public viewdetails() { }