Parle Products History Essay Example for Free

Parle Products History Essay The original Parle Company was split into three separate companies, owned by the different factions of the original Chauhan family. †¢Parle Products, led by Vijay, Sharad and Anup Chauhan (owner of the brands Parle-G, Melody, Mango Bite, Poppins, Monaco and KrackJack) †¢Parle Agro, led by Prakash Chauhan and his daughters Schauna, Alisha and Nadia (owner of the brands such as Frooti and Appy) †¢Parle Bisleri, led by Ramesh Chauhan In 1929 a small company by the name of Parle products emerged in british dominated India at Parle, world’s largest selling biscuits started in vile parle. It was owned by the Chauhan family of Vile Parle, Mumbai. The intent was to spread joy and cheer to children and adults alike, all over the country with its sweets and candies. The company knew that it wouldn’t be an easy task, but they decided to take the brave step . a small factory was set up in the suburbs of Mumbai, to manufacture biscuits as well. since then, the parle name has grown in all directions, won international fame and has been sweetening peoples lives all over India and abroad. A part from the factories in Mumbai and Bangalore Parle also has factories in Bahadurgarh in Haryana and Neemrana in Rajasthan, which are the largest biscuit and confectionery plants in the country. Additionally, Parle products also have 7 manufacturing units and 51 manufacturing units on contract. AWARDS Since the first entry at the monde selection in 1971,parle products have been shinning in golds and silver consistently Monde selection is an international institute for assessing the quality of foods Currently, it is the oldent and the most respected organization in the field of selecting quality foods worldwide ABOUT THE COMPANY Initially a small factory was set up in the suburbs of Mumbai city, to manufacture sweets and toffees. The year was 1929 and the market was dominated by famous international brands that were imported freely. Despite the odds and unequal competition, this company called Parle Products, survived and succeeded, by adhering to high quality and improvising from time to time . A decade later, in 1939, Parle Products began manufacturing biscuits, in addition to sweets and toffees. Having already established a reputation for quality, the Parle brand name grew in strength with this diversification. Parle Glucose and Parle Monaco were the first brands of biscuits to be introduced, which later went on to become leading names for great taste and quality. For around 75 years, Parle have been manufacturing quality biscuits and confectionery products. Over the years Parle has grown to become a multimillion-dollar company with many of the products as market leaders in their category. The recent introduction of Hide Seek chocolate chip biscuits is a product of innovation and caters to a new taste, being India’s first ever chocolate-chip biscuits. All Parle products are manufactured under most hygienic conditions. Great care is exercised in the selection and quality control of raw material and standards ensured at every stage of the manufacturing process. Parle Products has 4 manufacturing units for biscuits and confectionaries at Mumbai, Haryana, Rajasthan and Karnataka. It also has 14 manufacturing units for biscuits 5 manufacturing units for confectioneries, on contract. All these factories are located at strategic locations, so as to ensure a constant output easy distribution. Today, Parle enjoys a 40% share of the total biscuit market and a 15%share of the total confectionary market, in India. The marketing mix of Parle for this project has been studied from the point of view of Parle biscuits; mainly Parle-G and Parle hide seek. Biscuit goodies: Parle G, Krackjack, Krackjack Crispy Creams, Monaco, Kreams, Hide andSeek, Hide Seek Milano, Digestive Marie, Parle Marie, Milk Shakti, Parle20-20 Cookies, Nimkin Sweets: Melody, Mango Bite, Kaccha Mango Bite, Poppins, Kismi Toffee, KismiGold, Orange Candy, XHale Munch on snacks! Musst Bites, Monaco Bites Cheeslings, Sixer, Musst Stix Musst Chips

The Well Meadows Hospital Management System

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

Lekta & the Dialectic Essays -- Philosophy Philosophical Essays

Lekta & the Dialectic The scope of Stoic logic encompasses various aspects of their philosophy and serves as the primary method through which the rest of their opinions about the world are shaped. Stoic logic is easily divisible into two realms, the realm of the dialectic, and that of rhetoric. Rhetoric, with all its breadth and superfluity, seems less valuable to Stoic logic than the more simplistic dialectic. For the Stoics, the wise man is always the dialectician, for the dialectic distinguishes the true from the false with brevity and completeness. One of the most interesting aspects of Stoic logic, the concept of sayables or lekta pertains to this dialectic. There are numerous characteristics and conditions of sayables which ultimately reveal a great deal about the whole of Stoic philosophy and pose interesting questions about the continuity of their theory. Distinct from speech, sound, voices and utterances, lekta possess qualities which distinguish them from other aspects of communication and thought. At its most simple form, absent of various other conditions, a lekton is simply a piece of language that articulates a state of affairs, carries a truth value, and â€Å"subsists in accordance with a rational impression† (LS 196). Now, while lekta cannot be simply termed as speech or ideas, they are linked in a special sense with both speech and a concept to form an opinion. â€Å"†¦three things are linked together, ‘the signification’, ‘the signifier’, and ‘the name-bearer’. The signifier is an utterance, for instance ‘Dion’; the signification is the actual state of affairs revealed by an utterance, and which we apprehend as it subsists in accordance with our thought†¦ the name-bearer is the external object, for instance, Dion ... ...olded various lekta to create their propositions, forming questions which could be universally comprehended and evaluated. Without lekta, the dialectic could not have existed. The Stoic lekta, which I believe to be a corporeal part in the Stoic hierarchy of ‘somethings,’ provide a means through which logicians and philosophers could engage in the dialectic which developed various truths which we read about today. Whether lekta are a body or not, it remains that their strong independence and resilience as somethings can be used as a means to the end of scientific truth. Engaging in rational debate with propositions filled with subjects and predicates was the cornerstone of Stoic philosophy. Without logic, and the sayables which pieced together their dialectic, the Stoics would have been unable to provide perspective on those truths which have persisted through time.

The Presidency of Bill Clinton :: William Jefferson Clinton Essays

The Clinton Presidency William Jefferson Clinton?s eight-year term as president of the United States of America was one of the most corrupt, and possibly the most damaging ever. There is evidence connecting him to hundreds of deaths, injuries, and explosions. He, along with his administration, made a number of ?Faustian bargains and policy blunders? (Timperlake) that allowed a malicious, rancorous government to gain more power in Washington. He acted dangerously and impulsively, and befriended all of the wrong people, including Chinese arms dealers, spies, pimps, and gangsters, among others. Clinton also compromised U.S. safety on more than one occasion. He is a cold, racist, corrupt man who has proven many times over that he does not care about the people, only in using them and obtaining money. In the following pages, one will see facts proving all of this. One could begin with the issue of genocide. In 1994, between half a million and a million members of the Tutsi tribe were slaughtered by Hutu tribal militias. Even though this massacre was widely covered by the news, the United States did nothing to help stop the killing. President Clinton offered an explanation to survivors in Kilagi for this. He said that he ?did not fully appreciate the depth and the speed with which [the survivors] were being engulfed by this unimaginable terror.? (Kelly) This explanation was not quite true. The U.S. government watched the killings in Rwanda closely. Clinton was completely familiar with the genocide; he knew what was going on as hundreds of thousands were being murdered. And yet, he still did nothing to stop it. He is also quoted as saying that he only ?did not act quickly enough to stop it after the killing began.? (Kelly) Actually, he personally denied urgent requests from the U.N. to send a small force of non-U.S. troops into Rwanda. Then on May 24, 1994, with the estimate number of the dead at 400,000 and rising, Clinton said, ?We cannot solve every such outburst of civil strife or militant nationalism simply by sending in our forces.? (Kelly). One may ask, if he considers a million corpses a ?civil strife?, does he really care about the world and the human race at all? Then, one may look at what happened with Mena, and the two teenage boys, Don

War Poems: Totoy’s War, State of Siege, and War is Kind Essay -- Totoy

â€Å"Totoy’s War† by Luz Maranan, â€Å"State of Siege† by Eric Gumalinda, and â€Å"War is Kind† by Stephen Crane Throughout our history, both recorded and unrecorded, there have been countless violent battles fought. From small skirmishes to full on declarations of war, humans have been involved with battling on another for all the reasons that they have. The only thing alarming is that, as time and technology progresses, the number of casualties and collateral damage have been increasing as well. In addition, the implications to the human mind, brought upon by the excessive violence, can be equally damaging. With that being said, the psychological implications brought upon by war can be reflected in several art forms, such as poetry. War poems usually deals with how the persona of a particular poem, reacts to life altering events such as war. â€Å"Totoy’s War† by Luz Maranan, â€Å"State of Siege† by Eric Gumalinda, and â€Å"War is Kind† by Stephen Crane are just three examples of the many war poems that exist. Each of the poems conveys different messages, as well as utilizing different methods to convey the said message, despite having one common theme. The Fear of the Children â€Å"Totoy’s War† by Luz Maranan is easier to read poem, as compared to the other two poems mentioned. The poem is about the fear that people have during war times and how it affects various people, of all ages. The poem itself has no subliminal message that it wants to portray to its readers and is very direct with the matter of war – no use of metaphors, ironies, or difficult figurative language, whatsoever. The dramatic situation in the poem is that a child, Totoy, came to the persona asking â€Å"Is there a war?† (Maranan 2) with fear in his eyes. The persona then goes into c... ..., as well as the readers. Stephen Crane’s poem in contrast, uses irony to try and convey the message about the ugliness war brings. Eric Gumalinda’ poem on the other hand, is the one that is sort of off-tangent to the two. This poem in particular, shows the readers a glimpse of what is happening on a damaged person’s mind. It shows the readers a first-hand view on what people during war times could do, and all their intentions. Works Cited Crane, Stephen. "War Is Kind by Stephen Crane." About.com Poetry. About.com, n.d. Web. 7 Feb. 2015. . Gumalinda, Eric. Lyrics from a Dead Language poems 1977-1991. Manila: Anvil Publishing Inc., 1991. Print. Santiago, Lillia. In the Name of the Mother: 100 Years of Philippine Feminist Poetry (1898-1989). Manila: University of the Philippines Press , 2002. Print.

Brokeback Mountain: Wester or Romance Essay

Ang Lee’s Brokeback Mountain displays all the traditional characteristics of a romantic tragedy or a Western film, but upon its release it failed to be labeled as such. It was instead placed in the â€Å"gay and lesbian† film category. While obviously there is no harm in being labeled a â€Å"gay† film, it does distract from the purpose of the film, which is to show the touching story of these two characters. The film is merely a tragic depiction of two people, both of whom happen to be men, who fall in love with each other. It is a romantic tragedy in that contains the genre’s strongest and most popular theme: forbidden love. Simultaneously, however, the film can be classified as a Western due to the two main characters’ stereotypical embodiment of the cowboy persona. Brokeback Mountain is also eligible to be placed in the romantic tragedy genre. Lee tries to advertise this as the film’s main characterization with his use of landscape, advertisement, and themes. Lee’s use of landscape plays a huge part in the film’s development and push for a romance label. Jack and Ennis are first introduced and begin their love affair on Brokeback Mountain, which is emphasized and featured extensively. The landscape is very grand and lush and demonstrates the nature of their relationship on the mountain: natural and open. One of the biggest problems in their relationship is that their love is not welcome in their close-minded society, but in this vast open land it there are no restrictions, literally or socially. The landscape illustrates a theme of freedom and vulnerability in its openness and provides color, as well as contrast to the other set designs which are built upon a dull, grayscale color palette. This emphasis illustrates to the audience why the characters constantly want to return to Brokeback. The way the film was advertised pushed for a romantic label as well, in addition to revealing a lot of the major plot points. Lee has said that he modeled the poster after James Cameron’s 1997 famous romantic tragedy, Titanic. This was because he wanted the film to be known as a romance, rather than a â€Å"gay† film. On the poster, Jack Twist and Ennis Del Mar are placed in similar positions as Rose and Jack; however, instead of being placed above a ship they are instead surrounded by Brokeback Mountain, which is in a sense their Titanic. Every romantic film has one main object that is either the center or the origin of their love. In Titanic, it was the ship of the same name, while in this film it is the mountain. The placement of the characters on the poster foretell their futures in the story; Jack Twist follows Jack Dawson’s tragic ending and Ennis follows Rose. This plot point giveaway was never given any attention because the main focus was on the relationship of the two men rather than the story. The reaction of the public was not solely responsible for the film’s characterization; traditional cinematic stereotypes played a role as well. At the time of the release, the romance genre was (and can be argued, still is) stereotypically based on a relationship between a man and a woman. In the early days of film, homosexuality might have been hinted at but never outwardly displayed. As time went on, the social climate began to change and it became more acceptable to deviate from the typical on-screen heterosexual relationships, but with caveats: gay characters rarely played more than peripheral or supporting roles, and were often depicted as stereotypical or flamboyant. Brokeback Mountain was able to show another form of a homosexual relationship, one that was â€Å"normal†, accurate, and believable. The film does develop a popular and well-used theme in romantic tragedies, forbidden love. Such a theme has been widely popular and used in many great classic romance novels and films, such as Romeo and Juliet and the aforementioned Titanic. There is something epic and incredibly romantic about forbidden love, because it demonstrates the fight for and the strength of love between any two characters. These characters show the most fight for their love, because they live in a time and society that their love is scrutinized and could never be shown. Ennis, at one point in the film, mentions that his father took him to see a body of a man that was tortured and brutally killed at a very young age. These actions were later replicated to Jack when he was killed for being a homosexual. When people think of Western films and characters, masculinity is immediately brought to mind. A Clint Eastwood-esque character is summoned: the rugged macho man. When Brokeback Mountain was first released, it was immediately overlooked as a Western because its two main characters were in love with each other, something that was considered un-masculine. However, in looking beyond their relationship for a moment, the characters do actually display characteristics of a true cowboy. Many scenes illustrate characteristics of theirs that indicate traditional â€Å"masculinity. † For example, one way of demonstrating their â€Å"cowboy† persona is their attire. Marit Allen, the costume designer, has stated that she emphasized the cowboy look because it was thought that the characters would otherwise be overlooked and not given their credit. They wear the classic cowboy hats to cowboy boots, and at times dressed head to toe in denim attire; these are costume pieces that are common throughout traditional Western films. Another example are plot points in the storyline that depict Jack and Ennis as average men doing masculine things. Ennis is the primary caregiver in his family; he is shown as a hard worker and in constant search of jobs to feed his family. When it comes time to protect his wife and daughters, he shows he is not someone to be taken lightly. In various scenes Ennis is shown getting into fights, one example being the Fourth of July scene where he threatens to fight nearby men making crude comments within earshot of his daughters. Ennis prevails and is shown victorious and dominant, and while the other men lay on the ground submissive, with Ennis towering over them. Meanwhile, Jack also struggles to work traditionally masculine jobs to support himself, partaking in the quintessential cowboy sport, rodeo. Even the two men’s flirtation is done through traditionally masculine behavior. They constantly roughhouse and often get into fights just before they act on their relationship, such as in their first sex scene. These features, among others, illustrate that the characters fit the true masculine cowboy persona and thus the film can be classified as a Western. Labeling the film as a gay and lesbian film restricts the films plot because it is not solely about being gay, it is just merely a topic. If the film was categorized under a western or romantic, which are both broad genres, then the audience can focus on a variety of situations that the film shows. The film is entirely eligible to be labeled both, because the film demonstrates the same characteristics seen in both genres. It is a romantic tragedy because it contains one of the most popular and widely used themes: forbidden love and it can also be classified as a western because the two characters and backdrop embody the classic western persona.

Srs on Management System

Software Requirements Specification For Attendance Tracking System, Release 1. 0 Version 1. 0 Prepared by Lee Bell, Graham Kennedy, Jonathan Loudin, Roger Seagle February 9, 2003 Table of Contents Table of Contents†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ i Revision History†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. †¦ i 1. Introduction†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 1 1. 1 Purpose†¦Ã ¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 1 1. 2 Document Conventions†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 1 1. 3 Intended Audience and Reading Suggestions†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 1 1. 4 Project Scope†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 1. 5 References†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 1 2. Overall Description†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ . 1 2. 1 Product Perspective†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ 1 2. 2 Product Features†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ 1 2. 3 User Classes and Characteristics†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ â₠¬ ¦ †¦ 1 2. 4 Operating Environment†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ . 2 2. 5 Design and Implementation Constraints†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ .. 2 2. User Documentation†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ . 2 2. 7 Assumptions and Dependencies†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ 2 3. System Features†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ â₠¬ ¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ 3 3. 1 Roll Mode†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ . 3 3. 2 Edit Mode†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ . 4 3. 3 Statistics Mode†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ . 6 4. External Interface Requirements†¦ †¦ †¦ †¦ †¦ à ¢â‚¬ ¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ .. 7 4. User Interfaces†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ . 7 4. 2 Hardware Interfaces†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ . 7 4. 3 Software Interfaces†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ .. 7 4. 4 Communications Interfaces†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ â₠¬ ¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ . 8 5. Other Nonfunctional Requirements†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ .. 8 5. 1 Performance Requirements†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ .. 8 5. 2 Safety Requirements†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ 8 5. Security Requirements†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ . 8 5. 4 Software Quality Attributes†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ . 8 6. Other Requirements†¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ †¦ 9 Revision History Name Everyone Everyone Date February 9, 2003 February 12, 2003 Reason For Changes Initial Draft Revise Draft Version 1. 0 draft 1 2. 0 Final Version 1. Introduction The following document describes the functional and non-functional requirements for the Attendance Tracking System release version 1. . The contents are intended to be utilized by the software engineering class as guidelines for implementation and testing. This Software Requirements Specification document only covers the main s ystem and does not describe the implementation of the database in which the main system interacts. All the requirements stated in this document are slated for implementation in version 1. 0, unless otherwise specified. 1. 1 Purpose 1. 2 Document Conventions As of the latest version of this Software Requirements Specification, there are no document conventions.The intended audience is the software engineering class, who will be implementing and testing the Attendance Tracking System. Also, the document is to be utilized by the software engineering professor to evaluate the software’s design and features. The Attendance Tracking System will allow professors to maintain a record of attendance of students in their respective classes from a Pocket PC. Also, the system will permit the instructor to send a student a notification email of their absence. Furthermore, the program provides different modes to edit attendance, view tatistics, and take notes on elements pertaining to atten dance. The goal is to provide a professor with an easy, portable solution to attendance record maintenance and attendance statistics. 1. 3 Intended Audience and Reading Suggestions 1. 4 Project Scope 1. 5 References 1. Weigers, Karl. Software Requirements Specification Template, http://www. processimpact. com/process_assets/srs_template. doc 2. Overall Description The Attendance Tracking System is intended to replace the manual model of attendance record keeping by means of roll call and paper records.The roll call and paper records are replaced with a single interaction between the professor and the Attendance Tracking System. Professors will be able to view pictures of students on their Pocket PC and quickly maintain attendance records. The features expressed in this Software Requirements Specification document are intended to be fully implemented in version 1. 0. The system will be developed in such a way to provide easy addition of enhanced features, which may be desired in subs equent versions. The main feature of the Attendance Tracking System is for a professor to take roll from the Pocket PC.Pictures will be displayed for each student in the class, so the professor can recognize students without having to manually call roll. If students are absent, the system sends a notification email to the student stating the current number of absences the student has accumulated. Also, the system allows the professor to view pertinent statistics on student’s attendance record for the specified class. Finally, another feature of the Attendance Tracking System is the ability to easily edit the attendance record for any given day. Professors 2. 1 Product Perspective 2. 2 Product Features 2. User Classes and Characteristics A professor is a faculty member of Wake Forest University in Winston Salem, North Carolina. There are 357 faculty members at the university and it is estimated that almost all faculty members will utilize the Attendance Tracking System. Profes sors will have multiple classes and interaction with the system will occur at multiple times throughout the day from multiple professors. The professor should be allowed to take, edit, and view attendance records at any desirable time. All professors have wireless Internet access through their Pocket PC’ s while on campus.This connection provides the backbone of the Attendance Tracking System. Figure 1: Context diagram for Attendance Tracking System. 2. 4 Operating Environment OE-1: OE-2: OE-3: The Attendance Tracking System shall function on the Pocket PC provided by the university. This entails the system to operate on the Windows CE platform. The Attendance Tracking System shall interface between Windows CE and a Linux server designated to store the attendance records. The Web Server and Database Software have not been established at this point.Updated versions of this document will include information pertaining to these specific operating environments. The Attendance Tra cking System will operate with a yet to be established email client for notification of absences sent to students. CO-1: CO-2: CO-3: 2. 5 Design and Implementation Constraints The time allotted for this project will be limited to the Spring 2003 semester. The language for the project will be Visual C++ and the development environment will be the embedded Visual C++ 3. 0 environment. All the HTML code for the user manual will conform to the HTML 4. 0 standard. UD-1: UD-2: . 6 User Documentation The system will provide an online user manual in HTML that describes the functionality and options available to the user. The system will provide a hard copy of the user manual, which is identical to the manual outlined in UD-1 AS-1: AS-2: 2. 7 Assumptions and Dependencies The database mentioned within this Software Requirements Specification document is previously administered with the correct information needed by the Attendance Tracking System. For attendance policies, since professors do n ot usually tabulate tardiness, it is assumed a student is either present or absent.The notes functionality allows the professor the option to comment on tardiness and the edit mode allows the professor to correct attendance due DE-1: DE-2: 3. System Features to tardiness. Class data being used for setup and student recognition is dependent on information in a database administered outside of the capabilities of the Attendance Tracking System. Statistics on student attendance is dependent on a professor’ s consistent utilization of the system for each class period. Figure 2: State Diagram for transition between modes within the system. 3. 1 Roll Mode 3. 1. 1 Description and PriorityA user whose identity has been verified will be able to retrieve a roster and take roll at class time. The Pocket PC will determine the correct roster for the current date and time, retrieve that roster from a database server, and display it for the purposes of taking roll. The user will be able to designate each class member as present or absent, and upload that status information to the server. The server will notify the class members marked as absent by e-mail. Priority = High. 3. 1. 2 Stimulus/Response Sequences Stimulus: Response: Stimulus: Response: Stimulus: Response: Stimulus: Response: User loads system.System queries server and if a class exists for the current date, time, and user, then that roster is retrieved and displayed. User requests that a class member be marked absent. The class member is designated as absent. User requests that a class member be marked present. The class member is designated as present. User requests that the data be sent to the server for storage. The absence data for the current roster are transmitted to the server. Stimulus: Response: Server receives data indicating a class member has been recorded absent. E-mail is sent to that class member. 3. 1. 3 Functional Requirements Roll. Retrieve. Time: Roll.Retrieve. Date: Roll. Retrieve. Roste r: Roll. Retrieve. Roster. No: Roll. Display. Roster: Roll. Display. Members: Roll. Mark. Present: Roll. Mark. Absent: Roll. Transmit. Data: Roll. Notify. E-mail: The system shall retrieve the current time. The system shall retrieve the current date. The system shall retrieve the roster from the server that matches the current time and date. If no roster is found to match current time and date, default menus will be displayed. The system will display the roster on screen. The roster will display the pictures and names of class members. Members have the ability to be marked as present.Members have the ability to be marked as absent. The system will transmit the status of each class member in the active roster to the server. The system will notify all class members by e-mail if they are marked as absent along with their current status within the attendance policy. 3. 2 Edit Mode Figure 3: State Transitions within Roll Mode. 3. 2. 1 Description and Priority A user whose identity has be en verified who wishes to change the absence status of one or more class members as is related to a past class period will have the ability to retrieve the roster data for that class period from the server.Absence data may then be adjusted and the corrections uploaded to the server. Any new absences will result in notification by e-mail to the class member in question. A change from absent to present will result in a notification that an absence has been removed. Priority = High. 3. 2. 3 Stimulus/Response Sequences Stimulus: Response: Stimulus: The user requests to view absence data from a certain date and time. The roster and absence data are retrieved from the server and displayed. The user requests that a class member’ s status be changed to absent. Response: Stimulus: Response: Stimulus: Response:The class member’ s status is changed to absent. The user requests that a class member’ s status be changed to present. The class member’ s status is changed to present. The user indicates that they are finished making changes. The altered data is uploaded to the server and server data is updated to reflect the changes. E-mail notification is sent to the class members affected. 3. 2. 3 Functional Requirements Edit. Retrieve. Time: Edit. Retrieve. Date: Edit. Retrieve. Roster: Edit. Retrieve. Roster. No: Edit. Display. Roster: Edit. Display. Members: The system shall allow the user to choose the date of the roster to be retrieved.The system shall allow the user to choose the date of the roster to be retrieved. The system will retrieve the roster and absence data from the requested date and time. If no such roster exists, an error message will be displayed. The system will display the roster on screen. The roster will display the pictures and names of class members along with current absence status on screen. Members will have the ability to have their status changed to present. Members will have the ability to have their status changed t o absent. The system will transmit the new status of each class member in the active roster to the server.The system will notify all class members by e-mail if their status has been changed to absent along with their current status within the attendance policy. The system will notify all class members by e-mail if their status has been changed to present along with their current status within the attendance policy. Edit. Mark. Present: Edit. Mark. Absent: Edit. Transmit. Data: Edit. Notify. Absent: Edit. Notify. Present: Figure 4: State Transitions within Edit Mode. 3. 3 Statistics Mode 3. 3. 1 Description and Priority A user whose identity has been verified may request absence statistics for class members in classes under their control.Statistics for an individual class member may be retrieved and displayed with regard to number, frequency, date of absences as well as the percentage of classes missed over a user-defined period of time. A list of class members who were absent for a chosen class period may also be retrieved. Priority = High. 3. 2. 3 Stimulus/Response Sequences Stimulus: Response: User requests a statistical record. Statistics are calculated, retrieved from the server, and displayed. 3. 3. 3 Functional Requirements Stats. Define. Range: Stats. Request. Number: Stats. Request. Dates: Stats. Request. Frequency: Stats. Request. Percentage: Stats.Request. List: Stats. Retrieve. Number: Stats. Retrieve. Dates: Stats. Retrieve. Frequency: Stats. Retrieve. Percentage: Stats. Retrieve. List: The user shall have the ability to set the date or range of dates for which statistics will be retrieved. The user shall have the ability to request the number of absences for a class member. The user shall have the ability to request the dates of the absences for a class member. The user shall have the ability to request the frequency of absences for a class member. The user shall have the ability to request the percentage of class periods that a class member was a bsent.The user shall have the ability to request a list of the class members absent on a given date. The system shall have the ability to calculate and retrieve the number of absences for a class member from the server. The system shall have the ability to calculate and retrieve the dates of the absences for a class member from the server. The system shall have the ability to calculate and retrieve the frequency of absences for a class member from the server. The system shall have the ability to calculate and retrieve the percentage of class periods that a class member was absent from the server.The system shall have the ability to retrieve a list of the class members absent on a given date from the server. The system shall have the ability to display the number of absences for a class member. The system shall have the ability to display the dates of the absences for a class member. Stats. Display. Number: Stats. Display. Dates: Stats. Display. Frequency: Stats. Display. Percentage: Stats. Display. List: The system shall have the ability to display the frequency of absences for a class member. The system shall have the ability to display the percentage of class periods that a class member was absent.The system shall have the ability to display a list of the class members absent on a given date. Figure 5: State Transitions within Statistics Mode. 4. External Interface Requirements 4. 1 User Interfaces UI-1: UI-2: UI-3: UI-4: UI-5: The Attendance Tracking System shall provide pictures above the names of students in the class to aid in taking roll. These pictures can be clicked with a stylus in order to indicate whether a student is present or absent. All modifications to the database will be done through a stylus, the keyboard would only be needed to enter passwords.The Attendance Tracking System will provide a help link that will download a user manual and project it onto the screen in case the user has difficulty in using the program. The program will provide a page that produces current statistics on class attendance. 4. 2 Hardware Interfaces HI-1: HI-2: HI-3: The Attendance Tracking System will reside on the Pocket PC, however, it will be able to report its data to a database set up on a Solaris machine. The Attendance Tracking System will also be able to tell the Solaris machine to send emails to students who have missed class.The Pocket PC will use a wireless Ethernet card to communicate with the database set up on the Solaris machine. 4. 3 Software Interfaces SI-1: SI-1. 1: SI-1. 2: SI-1. 3: SI-2: SI-2. 1: SI-2. 2: Attendance Tracking System This software will transmit the attendance of a class to a database on a Solaris machine via wireless Ethernet. The user will be allowed to modify attendance records at any time. If the user forgets to transmit the information, the system will automatically send it for them at the end of the class. Database The Attendance Tracking System will communicate with the database to perform the followin g options.To allow a user to enter attendance. To allow a user to modify attendance. SI-2. 3: SI-3: To allow a user to query a system to gain statistics concerning individual and class attendance. Mail Message Generator If a student is absent, the database will send the necessary information to this interface and an e-mail message will be sent to the student. 4. 4 Communications Interfaces CI-1: CI-2: CI-3: The security of a user must be consistent through the use of passwords. The Attendance Tracking System will signal the mail message generator when it needs to send an email to the student.The Attendance Tracking System will communicate to the database through a wireless Ethernet system. 5. Other Nonfunctional Requirements 5. 1 Performance Requirements PE-1: PE-2: PE-3: PE-4: PE-5: PE-6: PE-7: The program must be able to be run concurrently by multiple professors. During peak times of usage (9:00 AM to 2:00 PM), the system shall support approximately 20 users. Transmission of roll data shall occur in under 5 seconds using the wireless network card. Acknowledgement of roll received (confirmation) shall be returned within 8 seconds. Queries upon the database shall be performed in less than 5 seconds.Upon start of the roll program, roll information shall be displayed on the instructor’ s Pocket PC within 10 seconds. Email messages to absent students shall be sent within one hour of the conclusion of a class. The program shall support taking roll for class sizes of up to 100 students. With a maximum class size, performance must still conform to all performance requirements. 5. 2 Safety Requirements No safety requirements have been identified. 5. 3 Security Requirements SE-1: SE-2: SE-3: SE-4: An instructor shall permitted to view and edit absence information in the database for only his/her classes.In order to take roll or edit database information, the instructor shall be required to enter a password. This password shall be stored on the instructorâ€⠄¢ s Pocket PC after initial entry in order that it must only be entered once. Passwords shall be stored in an instructor database and verified upon each session of roll or database modification. An instructor shall be allowed to change his/her password only by supplying his/her existing password. The updated password shall be stored in the instructor database and on the instructor’ s Pocket PC. 5. Software Quality Attributes Availability-1: The system shall be available to all instructors through Information Systems during their normal hours of operation. Reliability-1: Reusability-1: Robustness-1: Robustness-2: Updatability-1: Usability-1: 6. Other Requirements Due to the use of a wireless network, reliability of the system at all times is not guaranteed. However, overall reliability of the system and roll information shall be achieved through the process of database manipulation. The system shall be able to be reused for each new semester.If no network connection can be es tablished to receive the roll information, the instructor shall be allowed to enter roll later. If a network connection is lost during roll, the program shall allow the instructor to transmit roll information at a later time. The system shall allow for addition or deletion of instructors, students, and classes while incorporating new semesters. Usability of the system shall be achieved through an online help pages and an introductory training session for all instructors upon installation of the program on their Pocket PCs. 6. 1 Database RequirementsDA-1: DA-2: DA-3: DA-4: The system shall include three databases: student, class, and instructor. The student database shall contain student information including name, email address, and student identification number. The class database shall contain information about classes including class title, department code and course number, meeting times, students enrolled, and absences. The class database shall be grouped by department code and course number. The instructor database shall contain information about instructors including name, email address, password, and classes taught.