Situation Simulation in Nursing | Research

Situation Simulation in Nursing | Research INTRODUCTION Background In nursing education, simulation is a mainstay for clinical learning (Tanner, 2006), particularly in the areas of safety, problem solving, and communication (Durham Alden, 2008). Also simulation-based education leads to improved self-confidence in performance (Cant and Cooper, 2010) According to Jefferies (2005), successful learning using simulation requires alignment of the design, teaching activities, competencies, and learning outcomes. The case scenario, including simulations of actual clinical problems, provides an interactive learning environment, engaging students in the learning process and encouraging them to make connections between and among concepts. Environmental interactivity and feedback typically is achieved through the use of a high-fidelity patient simulator supplemented with role-play techniques (Good, 2003). Although simulation has been used successfully, more recently, in medical and nursing education programs (King Reising 2011; Tan, Ti, Ho, Lee, 2002), its use as an evaluative tool is still not fully developed. Student performance evaluation is a very important step during simulation-based practice. There is limited research in the use of simulation in nursing education and the evaluation of student competency (Reed, 2010). The instrument, developed by Jenkins (1985), is a self-report measure in which respondents are asked to identify processes or strategies used in deriving clinical decisions. Because one used for evaluating the quality, the validity of a general self-report measure would be questionable. Faculty evaluation of student performance was found to be the primary evaluation method, with student report of performance second and evaluation of videotaped performance third (Nehring Lashley,2004). Radhakrishnan et al.(2007) described using simulation to evaluate clinical skill performance in several areas: safety, basic assessment, prioritization, problem-focused assessment, ensuing interventions, delegation, and communication. Lasater (2007) also developed Lasater Clinical Judgment Rubric (LCJR) based on Tanner’s Clinical Judgment Model (noticing, interpreting, responding, and reflecting). The LCJR defines what is meant by noticing, interpreting, responding, and reflecting with 11 dimensions with four scale levels. Although, LCJR has relevance for all clinical contexts, including acute care, long-term care, and community health (Lasater, 2007), for simulation evaluation with emergency situation such as asthma, competency evaluation in clinical decision making should be undertaken. It is reported in both the nursing and medical literature (Edwards, 2007; Ottestad, Boulet, Lighthall, 2007) that real-time observation may be necessary to appropriately evaluate clinical decision making because it can reveal contextual and communication factors that may not otherwise be uncovered. Furthermore, to enhance the effectiveness of simulations in nursing education, a reliable and valid evaluation instrument is needed to measure students’ performance. Asthma mostly leads to emergency conditions because it shows spasmodic respiratory relapses and unpredictable occurrences. Especially, if asthma continues for a long time, it can progress into chronic lung disease and patient can experience suffering (Ko et al., 2010). Therefore it has to be considered as first priority problem in nursing care and nursing students must be prepared to provide emergency nursing care with high-fidelity simulation experiences for caring patients with asthma. Accordingly, simulation modules may help to provide a comprehensive understanding of asthma and asthma management. The purpose of this article are ; (a) to develop a scenario for patients with asthma for simulation education of nursing students, (b) to develop the evaluation checklist, and (c) to evaluate students’ performances. METHODS Design This study is a methodological study to evaluate students’ performance according to developing and applying of simulation scenario for patients with asthma in emergency units. Context and Participants The study was conducted at a regional school of nursing that offers a Bachelor of Nursing program in South Korea. In 2013, following ethics approval, third year (N=112) nursing students undertaking their first simulated learning experience were informed about the study. Total participants were divided 28 groups and the member of each group was 4 students (the role of doctor, nurse1, nurse2, family). The allocation of team and participants` role was assigned by randomization. The participants ages ranged from 20 to 24 years. The majority of students (88.9%) were women. Development process of asthma scenario with algorithm and evaluation checklist nursing journals (Poirier et al., 2000; Sarrell et al., 2002; Walsh et al. 2006). Issues included signs and symptoms of dyspnea, coughing with sputum, and anxiety related to the validity of the simulation evaluation by expert review. This scenario was based on a real dyspnea case with asthma that had occurred in emergency center of general hospital. To evaluate student performance in simulation, a team of researcher developed a template of an evaluation tool to include key elements from simulation course objectives. The following three main contents were identified: patient safety (infection control and error identification), communication, and critical thinking related to patient assessment, problem identification with nursing diagnosis, and intervention with evaluation. The items of evaluation checklists were selected, reviewed, and analyzed by 9 expert panel including 2 internal medicine doctors, 3 emergency center nurses, and 4 nursing educators. All items of checklist include a core set of key behaviors expected in this simulation course. The evaluation checklist based on three main contents (patient safety, communication and critical thinking) was formulated according to nursing process Finally, 4 items were deleted and 24 items reached by consensus (Table 1). The preparation subdomain consisted of three checkpoints, while the assessment subdomain was divided into seven checkpoints. Three nursing problems were included in the problem identification subdomain. The intervention with evaluations subdomain consisted of eleven checkpoints (Table 1). The evaluation checklist score was based on a 3-point Likert scale (1: not fulfill, 2: partially fulfill, 3: fulfill). The higher the evaluation checklist score, the higher the performance rating. Content validity is an important part of scale development because the results gained from an instrument with high representative nature are more reliable (Waltz Bausell, 1981). Content Validity Index (CVI) is a commonly used indicator of scale validity and in particular content validity. A content validity test was conducted with 10 nurses who worked in a medical-surgical unit in one of the three general hospitals sampled; each had at least three years of experience in the unit. According to Lynn (1986), an expert panel ideally includes about ten people. Each expert checked validity using the 4-point Likert scale; 1 means ‘not validate at al’, 2 means ‘not validate’, 3 means ‘validate’ and 4 means ‘very validate’. There were 24 items in total; the mean score of each item ranged from 3.30 to 3.90. The results of the Content Validity Index were above 80% (Waltz Bausell, 1981). Data collection A 20 minute scenario requiring students to use their clinical reasoning ability to identify and respond to a deteriorating ‘patient’ with asthma was presented. Four nursing students were engaged in the simulation at the same time. One operator and one instructor observed the simulations from the control room. Evaluators had simulation exercise for conformity degree of evaluation using two group students selected for evaluation practice. The evaluation of students’ performance was completed two times, immediately following simulation practice and reviewing of video-recording by two instructors. For accurate evaluation, evaluators rechecked and discussed item by item to decrease evaluation bias replaying video. Their performance was evaluated as a group. Data analysis method Collected data were analyzed using SPSS 18.0 for Windows (SPSS Inc, Chicago, IL) to calculate descriptive and t-test statistics for the evaluation checklist. RESULTS Algorithm with a scenario of simulation-based asthma management The simulation-based asthma scenario in this study was developed to identify and solve patient’s problems applying nursing skills and utilizing critical thinking. Development of this scenario was based on a real dyspnea case with asthma that had occurred in an emergency center. 1. Learning objective Learning objectives were formulated as follows: Explain pathophysiology of asthma Assessment of asthma patient Explain medication and effects of asthma drug Identified nursing diagnosis based on critical thinking Effectively communicate with the patient and colleague Implementation of evidenced based adequate nursing interventions 2. Development of a simulation-based asthma scenario The contents of scenario based on four steps was formulated; preparation, assessment, problem identification, interventions and evaluation. The preparation subdomain was consisted of the preparation content that should be cared for patients who admitted to emergency unit. The assessment subdomain were included in check the chief complaint, identify symptom related to chief complaint (dyspnea pattern, cyanosis, delayed expiration, pallor, color of mucus membrane, check SpO2, identify vital signs, auscultate respiratory sounds, check EKG rhythm with cardiorespiratory monitoring equipment), and identify past history. Problem identification subdomain organized that student can be present nursing diagnosis related to asthma; 1) Ineffective airway clearance related to excessive secretion, 2) Ineffective breathing pattern related to airway obstruction, 3) Anxiety related to dyspnea. Intervention and evaluation were organized focusing on the nursing process for dyspnea care(high fowler`s position), encourage of deep breathing (pursed-lip breathing, abdominal breathing), notify doctor and receive treatment order, administration of O2 and medication, nursing care for dyspnea control(drainage sputum with coughing), reassess patient`s condition(vital signs repeatedly, SaO2, EKG monitoring, respiratory status, physical examination, , SpO2, ABGA), educate coping behavior when symptoms are aggravated(deep breathing, coughing, drinking water, and aging nurses), support patient and family with therapeutic communication(explain easy, listening, relieve anxiety, communicate clearly with peers), arrange materials and instruments and wash hands, and record the nursing implementations. 3. Development of algorithm The algorithm proceeded as follows: patient safety (Step 1) and critical thinking and communication(Step 2)(Figure 1). Evaluation checklist The evaluation checklist consisted of four subdomains based on nursing processes: preparation, assessment, problem identification, intervention, and evaluations. The mean score of each subdomain is shown in Table 1. Table 1. Means of Items of Developed Evaluation Checklist The total mean score of the evaluation checklist was 2.39 ( ± .15). The mean score of each subdomain was as follows: preparation 2.05( ±.49), assessment 2.52 ( ± .33); problem identification 2.74 ( ± .33); intervention and evaluation 2.22 ( ± .30). The interobserver reliability between evaluators (Cohen`s Kappa score) was 0.949 % and there were no statistical significant differences among each item. The evaluation of students’ performance In the subdomain of preparation, students showed the highest mean score in the item ‘identify patient by name care and asking’ (2.46 ±.54) while the lowest item was ‘introducing self to the patient his/her parent(s)’ (1.68 ±.86). In the subdomain of assessment, the strong practice areas that student was well done were ‘identify vital signs’ (2.93 ±.26) while the lowest mean score was ‘auscultate respiratory sounds’ (2.11 ±.73). In the subdomain of problem identification, the highest mean score was ‘ineffective breathing pattern related to airway obstruction’ (2.93 ±.83) while the lowest mean score was ‘ineffective airway clearance related to excessive secretion’ (2.55 ±.74). In the subdomain of interventions and evaluations, the highest mean score was ‘notify doctor and receive treatment order if needed’ while the lowest mean score was ‘educate coping behaviors when symptoms are aggravated’ (1.93 ±.60). DISCUSSION In this study, the contents of simulation was formulated with asthma situation which is the most high frequency and required nursing care with education to improve an appropriate coping ability of nursing students. For this, the 3rd year students who have experienced only theoretical learning about respiratory care were selected to identify clinical performance ability according to learning objectives. So, the contents of scenario in this study was focused to achieve clinical performance ability of nursing students with three main contents (patient safety, communication and critical thinking) There are few studies which was dealt with respiratory problem. A simulation scenario for emergency care of patients with dyspnea used by Hur Park (2012) included only contents to train theoretical education as the nursing process. In case of other research dealing with simulation case for patients with asthma in emergency units (Ko et al, 2010), the contents of scenario was formulated into five categories as follows: problem recognition, focused assessment, nursing diagnosis, intervention and problem resolution. However, there was a limitation about testing clinical performance ability. We suggest that three domains and contents of a scenario developed in this study are more suitable to improve students’ clinical performance. Lindsay(2010) suggest that measuring the performance of nursing care directly is more effective than using psychological variables as testing the effect of simulation learning. The evaluation checklist used in this study was developed to examine students’ critical thinking as well as their knowledge and skills in proper nursing care and validated by expert panels. The evaluation domain, which fully implements high-fidelity simulations, offers information to nursing educators about students learning outcomes. The use of simulations to evaluate clinical ability provides a more direct correlation to actual clinical settings than other commonly used forms of evaluation. The evaluation indicated that the focus was on performance rather than learning. The studys evaluation checklist would also be a useful and established guide for nursing educators evaluating student performance through simulations. This checklist describes the overall evaluation process and clarifies the evaluations target subject and procedure. This encourages students to repeat checkpoint reviews, leading to the correction of earlier mistakes. The effect of reviewing past checkpoints cr eates an integrative, rather than a static learning experience (Reed, 2010). To test evaluation validity, the consensus between evaluators was identified and showed almost similar evaluation results with no statistical significant difference. In the domain of patient safety, students showed the highest mean score in the item ‘identify patient by name care and asking, while the lowest item was ‘introducing self to the patient his/her parent(s)’. This result implies that addressing to introduce oneself to patient before caring patients as a part of simulation education is necessary. The research (Kim et al., 2013) which was developed simulation-based fever management module and evaluated student performance showed that ‘introducing self to the patient his/her parent(s)’ was identified as the lower mean score among other evaluation items. These similar results suggest that noticing themselves to the patient is so important to protect patient’s safety. In the domain of critical thinking and communication, the strong practice areas that student was well done were ‘identify vital signs’ in assessment, ‘ineffective breathing pattern related to airway obstruction’ in problem identification, and ‘notify doctor receive treatment order if needed’ in interventions and evaluations. However the weak practice areas which education and practice will be needed were ‘auscultate respiratory sounds’ in assessment, ‘ineffective airway clearance related to excessive secretion’ in problem identification, ‘educate coping behaviors when symptoms are aggravated’ in interventions and evaluations. It is required that students needs high level practice of assessment and performance skill with critical thing. Jeffries (2005) suggests that simulation education through direct participation and prompt feedback is effective learning method to reinforce clinical performance ability. In this study, theoretical class and orientation about simulation situation was given before simulation practice to find more effective nursing intervention. As a next step, students could enhance the strong point and make up week areas in the process applying nursing care with direct participation. Based on this result, we suggest that integrated simulation approach after learning of theoretical knowledge and nursing skill training could be effective education method to improve clinical performance ability and critical thinking of nursing students. The study of Kim et al (2007) supports these aspects that simulation education is more effective than lecture focused on knowledge and simple skill practice i n acquisition clinical performance skill of nursing students. CONCLUSION This study could provide a clinical performance or starting point for educators who desire to introduce simulation as teaching-learning strategy with high-fidelity simulation experiences for caring patients with asthma. The results provide evidence to support the integration of simulation as an effective teaching strategy that helps to improve nursing students` safety, problem solving, and communication in applying clinical skills using evaluation checklist. Annotated Bibliography: Portrayal of Women in the Media Annotated Bibliography: Portrayal of Women in the Media Literature Review The last 20 years has been a steady increase in the number of women professionals, although most common in the media business, politics and the economy continues to rely on men as experts in. Mostly Women portrayal news stories about accidents, natural disasters, or domestic violence instead of their professional capabilities or proficiency. Women in politics are similarly sidelined. Canadian journalist Jenn Goddu analyzed newspaper and magazine 15 years on the treatment of three women’s lobby groups. She found that journalists likely more focus on the domestic issues of the politically participated woman’s life (such as their fashion, routine life and way of living and dealing) rather than her point on the issues. Pdf _______________________________________________-04 http://www.mediaawareness.ca/english/issues/stereotyping/index.cfm Arpita Sharma, studied the Portrayal of Women in Mass Media in India. He stated that Indian sate have a free and responsible press. He investigated the issue women were sold in Eluru of Andhra Pradesh that issue news published in 1998. On such kinds of incidents he found two major aspects. One is women still only sold and purchased and unwanted away if you cursed suffer discrimination and degrading of women in various parts of the country may be a reflection of goods is considered one of the eateries. Second, but only a few sensational newspapers flashed on issues, emphasizes the role of the media in public construction. Usually, it is determined the place in the newspaper. He added that in India a few newspapers are running women’s page that represents the beauty tips, recipes and fashion. He also studied the womens magazines seek constantly to lead the feminine energies in narrow channels and define their concerns, concerns and aspirations within imposed arbitrarily framework of womens work. Apart from the looks and dresses stress it comes to the development of the mental faculties and the behavior in a way that they can fit into womens male dominated social structure. He studied the structure of the stories in magazines and described that women are described with the ambition of life get a straight man and his retention at all costs. The media advocacy group studied, the womens and mens news and current affair programs (1994) they stated that women have traditionally been associated with areas limited relationship programs. Even those women call their exterior prettified setting; can be seen to give their views on topics related to home and family. In conclusion words, Sharma says that Media in India not to discuss serious issues related to women and womens roles in society is equal to its own rights and makes a sufficient effort to ready to play. To change this situation, the benefits and disadvantages of the bride and the media constantly monitor is required. Arpita, Portrayal of Women in Mass Media The news media is changing to reflect their increasing womens representation in political status as elected representatives and community participation and and New Zealand national policy is clear. But it does not mean that the old adage applies better. Every day on television, radio broadcasts and print media increased visibility of women, in politics, structural, systematic gendering. This time, however, Women themselves with tolerance, gendering of tolerance and the representation of women in politics sexist media feeds. The media does not reflect the truth in politics or outdated, the ladies sexist images and words and concepts are mired in the private sphere about womens place (van Acker, 1999). New Zealand while on top of the world in terms of womens political resources are represented as instances of the trivialisation and condemnation, and continue to occur, in some cases, trivial media portrayals of women employed by the public relations strategies for political gain. I would suggest. Neglect, in its original form, dotted with high-profile women in the contemporary political scene, but the evidence is less relevant to the concept of womens perspectives, is still in some places is omitted. Journalism educators in the 21st century in terms of visibility/invisibility of gender theory, news and media, you must reboot for the quality of less represented. Susan Fountaine, Judy McGregor, Reconstructing gender for the 21st century: News media framing of political women in New Zealand With more than 50 State Capitol Hill each year representing the women, many women politicians have noted that the same treatment is not allowed, such as media men. In a study of women politicians on the news focuses on character traits and its policy more arguments less than male colleagues for that. 03. News coverage of female politicians focuses on personality, males on the issues Date: July 3, 2013, Source: SAGE Publications Dunaway et. al studied the Traits versus Issues: How Female Candidates Shape Coverage of Senate and Gubernatorial Races, in the State Elections of 2006 and 2008 elections, approximately 10,000 newspaper articles covering the data collected across the USA. The study authors Dunaway et. al, the focus in terms of the [political] stated that the net change between the races. The previous literature and their own expectations, in General, women candidates are racing against male races more likely the property feature stories. They found that Only 6% of the time and the character traits to choose coverage problems% 34.5 time, male-female issues from time to time the races, properties,% 10.8% focused on articles and only male selections, 33.0 character properties is focused on the issues from time to time,% 9.4% 32.1 found stories stories. The researchers concluded that, personal characteristics and properties of the candidates with a more focused news races women candidates and finding the Governor campaigns especially stark. J. Dunaway, R. G. Lawrence, M. Rose, C. R. Weber.Traits versus Issues: How Female Candidates Shape Coverage of Senate and Gubernatorial Races. Political Research Quarterly, 2013; DOI:10.1177/1065912913491464 In nature, this paper adopted the content analysis method. This did it begins with the small Big Naira Kobo, entrepreneurship is a leading national newspaper in Nigeria, a property of the column to explore womens participating in the media frame Because he was selected to work in the newspaper business desk signature page column. Analysis, paper print media framing, enhancing their socio-economic empowerment for Women Entrepreneurship is important for the world as a tool that can serve as the finish. Therefore, the Mission of becoming a real instrument of social change punch newspaper to fulfill this while maintaining his begins with the small Big Naira Kobo column property of the positive image you will have to increase the numerical quota framework womens characterization, frame. To the extent that these are three of the four women featured in the successful entrepreneur, the punch is acting as a complementary agency of women empowerment, Women womens ability to use their own aspects of the control is defined while they participate in the way of effective group work for social change. Samuel Okere, Justina Sam-Okere, Print Media Framing of Women in Entrepreneurship: Prospects for Women Empowerment IOSR Journal Of Humanities And Social Science (IOSR-JHSS) Volume 9, Issue 6 (Mar. Apr. 2013), PP 31-38 e-ISSN: 2279-0837, p-ISSN: 2279-0845. The depiction of women in the Indian media, its just a bad time is rude. Newspapers to give news about rape, crime, politics, scandals, sports and Economy, serious discussions and debates on womens issues in General is completely missing. Local media reported the woman Gets a share of only pages where the colorful portrayal of a lot of players in the TV serial or movie stars, as well as some of the warm welcome, and pin-up about the grapevine. The British press, hot babes snaps and party-Mania lives on the provision of very erotic Photo Gallery star hotels. Even sports stars are a way of depicting their physical attraction photos. The woman in the Indian media, be it Movies, TV series, news, media, Visual advertising, or modernized traditional media, social science research and studies of people indeed for a space is a big concern. Some studies have found women (status and equality of opportunity) the inevitable social issues related to the sensational stories of crime stories in the newspapers about women with less than nine percent between 52 to 63 percent. (Nitin Jugran Bahuguna) Dr. Sanjeev K. Sharma Depiction of Women in Indian Media- A Case of Introspection for Media Planners. Published in Samaj Vigyan Shodh Patrika, Amroha, Vol. I, No.1, April-Sep.2005, pp.32-36 Grant (2013) argued that analysts tend to think in terms of two broad categories: visibility, reporting and quality. How much a person shows the visibility or discussed, and how important is placed in a newspaper or news broadcast coverage. Women election participants from time to time get a lot of news coverage due to their novelty value because they associate with powerful man, as in the case of Chow, who married with former NDP leader Jack Layton is mentioned in every newspaper stories according to Grant analyses of coverage of the 2006 Canadian federal election. Such kind of women coverage portrayal women as different because of their sex, likely norm of as the men view however, it is not clear that it would be a direct electoral drawback for women. In fact, depending on the quality of the coverage more coverage may be useful for candidates. Grant also found in his study that important issue ofhowmen and women news story are covered differently. He stated that coverage of female candidates usually fall under the four categories; sex object, mother, pet, and iron maiden, each of which is equal to the representation of women in politics more generally, as well as for the danger of gender equality. However, Iron Maiden is another popular and at the same time, the male toughness while unfeminine implicitly criticized the women candidates is my discovery book news, intruder behavior with exaggerated. This news depiction of women politicians, aggressive behavior is actually harmful to the voter may be to find the book for the evaluation. He concluded that when a woman goes on the distasteful, voters’ evolutes her news stories more negatively, and a result that was not produced for her male comparators in this portion of the study. The general attitude and reporting directly link between news media under the cross-hairs of women assessing the political. Grant. G, Elizabeth News Media Coverage of Elections Contributes to Women’s Political Under-Representation 2013 http://womensuffrage.org/?p=22202 The study focused on womens issues related to the Newspapers by the welcome. The two daily newspapers in Hindi, Amar Ujala Jagran Danik is taken to work and . Both papers published and in Dehradun (capital of Uttarakhand state) circulation of Uttarakhand. Researcher analyized the newspapers about equality womens issues such as Health, education, sexual harassment, violence against women, police brutality and crime-related issues. All kinds of printed material on these issues articles, news, analysis, opinions, Editor, the letter was taken for analysis as a separate column, and etc. the year 2006 was selected to examine the contents of the newspaper. Newspapers are less indicates that the percentage of womens issues. Usually, the newspaper is a good place for an eye-catching image of women in the news; property, or ads. Womens issues in terms of sexual harassment such as more coverage to violence, crime and police brutality than the equality health, education, health coverage. The newspapers give a high rate of sexual abuse against women, developmental problems and other issues less coverage than this issue. The analysis also indicates that the given space vs. equality, health, womens education, as well as other topics to Newspapers by negligible. The newspaper society in a changing world does not provide a balanced picture of womens diverse lives and contributions to the data. He concluded that participation, representation and advancement of women in the media and its impact on access and use, and as a tool for empowerment of women. Dr Vandana Nautiyal Mr Jitendra Dabral WOMEN ISSUES IN NEWSPAPERS OF UTTARAKHAND Global Media Journal – Indian Edition/ISSN 2249-5835 , Summer Issue / June 2012 Vol. 3/No.1 Women in the absence of mass circulation Urdu language newspaper in a way that is evident in the senior ranks, in addition to smaller circulation in shaping social attitudes which the province plays a very important role in the regional press. Independent press, but applications of self-censorship and ethics, the outlook varies according to demand and audience made the newspapers. For example, while some shun the violence and disregard for others are projecting to highlight the needs of the people. The main concern in a way that the projection of women. Even while direct damage, this time the female victim, rape, wife-beating and humiliation of names through print, photo or both, always hinted at this without the permission of their privacy by. Objections to grow poor especially disadvantaged and often â€Å"made outcast. References Butt Mourion (1996) studied the portrayal of women in general press, is practically non-existent with the exception of magazine sections and limited news. The Womens lack of realism in private press and exhibits extreme offers the sad situations with fantasizing or is over-whelming portrayal. In addition, the scope of women in rural production, womens education, health, etc. is your own level of performance compared to the low level. The woman seems to be unaware of the needs of communities, and the private press skill does not address the various layers in a positive direction, whereby, in a variety of trades and social assistance programs is displayed, and a comprehensive and realistic way to portray positive women taught in different areas of our society contributes to this by the media projected us and women real projection would be a turning point for the progress and development of Women in the country. Butt, A. G. Mourion (1996). Portrayal of Women in the Communication Media, Lahore: Pakistan Women’s Institute. Gibbons (2006), in her latest study of women in journalism, found that women continue to be the breaking and making news away from the second sex. Radio, television and newspaper content on the same day, a full day after 76 countries that ignore the issues and resources for underrepresented and sometimes downright notice, regardless of the medium also commented. Women outnumber men as newsmakers in single big news. The effect of gender-based violence, intense women even stories like inserts; the judge is the voice of a man. This report, women second class status, grossly, and in general the judge reveals. Gibbons, S. (2006) â€Å"Womens Lowly News Status Is a Global Insult† Women News, Run Date: 02/22/06, http://www.womensenews.org/article.cfm?aid=2646, Retrieved on 19th July, 2006 Tiongson (1999), presented an outline of Isis International-Manila, Violence against Women in Media, a media pack, March 1998. She said that the depiction of women in the media that the victims, nurturing, selfless, obedient, and dependent, his mother and his wife, being heterosexual, sex-object, whore, mistress in Asia – the characteristic was consistent, she said and also contributing to the development process, many women workers, farmers and professionals. To make matters worse, some members of the media tend to the efforts of womens organizations or alleviate the cartoon. News womens visibility is often sensational stories, rape, sexual harassment, domestic violence and other violence-related. She further assumed that Asian media stereotypes, inaccurate and Biased media portrayal of women persistent content and pictures of stereotypical and traditional roles of women, thus perpetuating patriarchal and sexist gender identities, and to strengthen the relationships between men and women. Constant negative portrayal of women and freedom of expression in print, broadcast and Film screening has become a license for. This is an insult to womens portrayal of the nature of, in fact, its hard to pinpoint in the last few years has been more subtle and insidious.

Hollywood moves influence in society Essay

Hollywood movies have had an important effect on cinema across the world since the early 20th century. Its history is sometimes separated into four main periods: the silent film era, classical Hollywood cinema, New Hollywood, and the contemporary period. Is clear that Hollywood movies have an impact and influence in society. From my point of view the Hollywood movies are not a bad influence to society. Most of these movies are made after books and we don’t say that books have a bad influence on us. The combinations of themes that have these movies are magnificent so we can’t say that because they have some violent movies the whole industry is bad. Also the movies that contain violence tell us that violence is not the right way of doing things. Almost every movie has his good teaching. Even that they have some of this kind of movies that people can understand are a bad influence from society these haven’t been proved. Movies should be taken as what they are not reality. Movies are just a way of entertainment. I personally think that Hollywood films can be positive as they offer different views and concepts to many people and in turn allow people to think over certain ideas and formulate their own ones. The main objective of these movies is entertainment. People choose the stars of these movies as a role model, and these movies became a part of or life. Also I don’t agree with the ideal of beauty the media does obviously show, but you can’t really blame them when is just the reality, these ideal is show not only in movies but everywhere. Hollywood produces are in fact a mixture of our life or of some of us. It is a mixture of biographies, love stories, dramas, science fiction, horror stories, action films and documentaries. If some people get bad habits from seeing these movies we can blame the movie because they are not maid to cause any problem.

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() { }

The Difference Between a Weak and Strong Verb

The distinction between a weak verb and a strong verb is based on how the past tense of the verb is formed. Weak verbs (more commonly called regular verbs) form the past tense by adding -ed, -d, or -t to the base form—or present tense—of the verb, such as call, called and walk, walked. Strong verbs (usually called irregular verbs) form the past tense or the past participle (or both) in various ways but most often by changing the vowel of the present tense form, such as to give, gave and stick, stuck. Strong vs. Weak In Garners Modern American Usage, author Bryan Garner explains the difference between a week and strong verbs: Irregular verbs are sometimes called strong verbs because they seem to form the past tense from their own resources, without calling a The term strong has been inherited from Old English grammar, and many of todays irregular forms are descendants of common Old English verbs. Although fewer than 200 modern English verbs are strong, these irregulars—most of which are just one syllable in length—are among the most common in the language. Examples of Weak Verbs With week verbs, the stem vowel does not change in the past or past participle tense. Take the word walk, for example. The past and past participle of this verb would be walked because the stem vowel does not change. Another example would be work, where the verb becomes worked in the past and past participle. Other examples of the week, or regular, verbs would be as follows, where the verb is listed on the left with the past/past participle on the right: Add addedBeg beggedCall calledDamage damagedEarn earnedMark markedTaste tastedYell yelled The past tense or past participle of these verbs looks roughly the same as the present tense because, as noted, the stem vowel does not change. Strong Verbs Examples By contrast, strong verbs generally do have a change in the stem vowel in the past or past participle. For example, the past tense and past participle of bringing is brought. At other times, the stem vowel in a strong verb might change in the past tense but not in the past participle, such as arise, which becomes arose in the past tense but arisen in the past participle (as in he has arisen.) Other examples of strong verbs would be: Blow blew (past tense), blown (past participle)Break broke (past tense), broken (past participle)Do did (past tense), done (past participle)Feed fed (past tense and past particle)Lie (down) lay (past tense), lain (past participle)Speak spoke (past tense), spoken (past participle) As you can see, there is no hard-and-fast rule for determining if a verb is a week or strong. Since there are fewer than 200 strong verbs in English, the best method is to memorize their use in the past and past participle.