The Kite Runner Essay Example for Free

The Kite Runner Essay What would you do to redeem yourself for a very bad thing you’ve done? In the novel The Kite Runner, the main character, Amir, will redeem himself for what he had done in his childhood by doing good things. In Afghanistan, there is a segregation of ethnic groups between the Hazara and the Pashtun. Hazara people work for the Pashtun people. Hassan Is a Hazara and Amir is a Pashtun. Although Amir and Hassan are best friends, Amir never consider Hassan as his best friend or even a friend. Even though Amir is a mean and jealous character when he is young, he evolves into an entirely different person. He redeems himself by showing unselfishness and generosity to a stranger. He grants Rahim Khan’s last request and risks his life to go help Sohrab in Afghanistan. As a child, Amir’s character shows jealousy and selfishness because he doesn’t receive enough attention from his father. Amir is always jealous of Hassan for being treated the same as him by Baba. In his head, Amir thinks that he is Baba’s true and only son, so he doesn’t understand why Baba treats Hassan the same way he treats him. When Amir and Hassan go to buy kites, they get the same kind of kite, and when Amir asks for a fancier one, Baba buys the same for both of them. â€Å"Sometimes I wished he wouldn’t do that. Wished he’d let me be the favorite. † Amir doesn’t like Hassan to be treated the same way as him because he is jealous. He once thought that the orphans should have died along with their parents because he is jealous of the kids that get to spend time with his father. This shows that when Amir is young, he was mean and selfish. To run away from his jealousy and guilt, he frames Hassan for stealing his watch and money by placing it under the mattress. After Amir frames Hassan for stealing his watch and money, he never had the chance to see Hassan again in his life. Although he purposely pushes Hassan out of his life, Amir is obsessed with Hassan throughout the novel. He thinks about Hassan when there was war, wonders if Hassan is still alive. He thinks about Hassan when he was grown up, wonders if Hassan was alive or if he has any wife yet. Its because Amir is full of guilt and obsession over Hassan. Deep inside, he thinks that if Hassan dies, it might be because of him. Amir also regrets the action in the past. Amir regrets that he wasnt mature enough to understand that Hassan is his best and only friend. He regrets that he wasnt strong enough to stand up for himself. He regrets how he was ignorant, and didnt know that Hassan is his brother. Throughout the novel, Amir has evolves into an entirely different character. He changes from a mean and jealous boy to a generous and kind man. Amir plants fistfuls of crumpled money under the mattress. He shows kindness to a stranger like Farid. Amir wants to help Farid’s family because he understands what his family has to go through in Afghanistan. When Amir was searching for Sohrab at Afghanistan, he met a beggar that knew his mother. Amir gave the beggar on the streets three dollars. Three dollars is not a lot of money but to give three dollars to a beggar is not a common thing that happens. This proves that Amir also evolves into a character that has empathy towards people, and changes into another level of kindness. He also evolves into a character that has more courage. As a child, he won’t fight people back and needs Hassan to help him. He also couldn’t stand up to the General but now he can finally stand up to the general, when he said to the general that, â€Å"you will never again refer to him as’ Hazara boy’ in my presence. He has a name and it’s Sohrab. † â€Å"There is a way to be good again†. These words come out from Rahim Khan’s mouth. He convinces Amir to be a good person after he finds out what Amir has done in the past. Amir tries to redeem himself by meeting with Rahim Khan and grants him his last request before he dies. He goes back to Afghanistan to help Sohrab out of that poor and dangerous place. This shows Amir’s commitment to Hassan. He redeems himself to Hassan. Amir would risk his life to go help Sohrab, even though he has other responsibilities like how he has his wife at America. If he dies in Afghanistan, it will really affect Soraya’s life. He even accepts Sohrab in his family and adopts him. It shows that Amir is really dedicated to this redemption. The novel shows the evolution of Amir as a character. He becomes more kind and generous to other people. He also redeems himself for the bad things that he did to his half brother. His regrets lead him to his redemption. After Amir finds out that Hassan is his half brother, and that he has passed away, that is when Amir starts to evolve into a different character. He starts showing kindness and generosity because it is Amir’s way of redeeming himself. I think at last Amir really did become a good person.

Motherly Love in Amy Tan’s Joy Luck Club Essay -- Joy Luck Club Essays

Motherly Love in Amy Tan’s Joy Luck Club A mother’s love for a daughter is an intense feeling; some times it can be very joyful or very painful.   Most mothers just want their daughters to have everything that they didn’t have, they try to give their daughter all their hopes and dreams.   The relationship between a mother and daughter should be one of the greatest relationships a woman can have with another woman. Some time a mother can push a daughter to hard, some mother don’t mean to make their daughter feel bad or to make them up-set, the mothers just want the daughter to have better then what they had.   A mother gives her daughter advice about everything in life.   â€Å"A Mother’s Advice to her Daughter.† â€Å"Be strong.   Be intelligent. Smile knows that beauty has everything to do with how you feel about yourself and nothing to do with looks or other people’s opinions.   Never do anything just because everyone else is if you believe it’s wrong.   Always be true to yourself.   Expect the best from life and that’s what you’ll get.   Learn from your mistakes and failures.   Believe in magic and wish on stars.   Love and trust and be compassionate.   Make faces.   Play in mud puddles.   Take bubbles baths.   Turn off all the lights and watch lightning storms.   Dance, laugh, cry, and sing when you want to.   Read everything you can get your hands on.   Stand up for what is right especially if you stand-alone.   Don’t allow yourself or people around you to tolerate prejudices of, any kind.   Don’t be afraid to at least once a week.   Run through snowdrifts.   Spin in circles and roll down hills.   Pet after noon naps.   Stay up to watch the sunrise.   Never apologize for being a woman or for being yourself.   Never forget that I Love you more than any ... ...omen, she did not want to look and see what her husband was doing.   Each marriage was not stable in any kind of way and some kind of household item was a sensible of their marriages. How each item broke too sensible that their marriage had fallen apart. The lives of eight Chinese women are told throughout the book The Joy Luck Club.   How their childhood was, their first marriage was and all their hopes and dreams that they wish to come true.   A mother’s love for a daughter can some be joyful or very painful.   In the case of these women all the mothers want was their daughter would not make the same mistakes that they did in the past, and for them to learn for those mistake.   That is the love for a daughter from her mother. A mother gives her daughter advice about everything in life. WORKS CITED    Tan, Amy. The Joy Luck Club. New York: Random House, 1989.

Srs of Library Management

| |Software Requirements Specification | For A-Flex Automated Library Management System Version 1. 2 Prepared by A-FLEX Group |Jude Marlon B. Alegro |111694 |[email  protected] com | |Arnel G. Abagua |082198 |[email  protected] com | |Jun Jun G. Abanag |102206 |[email  protected] om | |Ronaldo R. Arbes |061491 |[email  protected] com | |Amado C. Tan |101078 |[email  protected] com | | | | | |Instructor: |Prescilla F.Catalan | |Course & Year: |BS in Information Technology 3 | |Schedule: |TTH 7:30 – 9:00 AM | |Date: |April 16, 2013 | | | | Table of Contents title pagei table of contentsii table of figuresiii Revisionsiv 1Introduction5 1. 1Document Purpose5 1. 2Product Scope5 1. Definitions, Acronyms and Abbreviations5 1. 4References6 1. 5Overview6 2Overall Description7 2. 1Product Perspective7 2. 2Product Functionality8 2. 3Users and Characteristics8 2. 4Operating Environment9 2. 5Design and Implementation Constraints9 2. 6User Documentation10 2. 7Assumptions and Depen dencies10 3Specific Requirements11 3. 1External Interface Requirements11 3. 1. 1User Interfaces†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 14 3. 1. 2Hardware Interfaces†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. †¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 14 3. 1. 3Software Interfaces†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 14 3. 1. 4Communication Interfaces†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 15 3. 2Functional Requirements†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 15 3. 2. 1Librarian Use Cases†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 5 3. 2. 2Clerk Use Cases†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 19 3. 2. 3Borrower Use Cases†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã ¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 24 4Other Non-functional Requirements27 4. 1Performance Requirements27 4. 2Safety and Security Requirements27 4. 3Software Quality Attributes28 4. 3. 1Functionality†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 28 4. 3. Usability†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 28 4. 3. 3Reliability†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 28 4. 3. 4Supportability†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 28 Appendix A – Data Dictionary. 30 Appendix B – Group Log. 31 InDEX. 33 Table of Figures Figure 1 Context diagram7 Figure 2 Operating environment9 Figure 3 Main interface11Figure 4 Logging station for Librarian12 Figure 5 Clerk station for connection13 Figure 6 Clerk station14 Librarian Use Cases15 Log in†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã ¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 15 Log out†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 16 Search book†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 6 Issue book†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 17 Update database†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â ‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 18 Clerk Use Cases19 Log in†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 19 Log out†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. †¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 9 Search book †¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â ‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 20 Issue book†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 21 Return book†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 21 Add book†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢ € ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 2 Update database†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 23 Borrower Use Cases24 Log in†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 24 Borrow book†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 24 Retu rn book†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 5 Revisions |Version |Primary Author(s) |Description of Version |Date Completed | |1. 2 |Jun Jun G. Abanag, Jude |The revision of this SRS was done by request. Error |04/16/13 | | |Marlon B. Alegro |corrections to some parts of the document were needed to fully| | | | |complete an accurate Software Requirements Specification.Some| | | | |specified features were removed because it was uncompleted due| | | | |to lack of time and preparation. Some small details in | | | | |chapters were also corrected and Content page was revised. | | | | |Finally, to finish the SRS, then Appendix B and Index were | | | | |added. | Introduction 1 Document Purpose This Software Requirements Specification will provide a c omplete description of all the functions and specifications of the project, A-Flex Automated Library Management System. It will explain the purpose and the features of the system, the interface of the system, what the system will do, the constraints under which it must operate and how the system will react to external stimuli. This document is intended for both of the stakeholders and the developers of the system and will be proposed to the College Library of Samar College. Product Scope The A-Flex Automated Library Management System will be designed for the librarian, the staff and clerks and especially for the students of SC Library to maximize their productivity by providing tools to assist in automating the: production and transaction; logging in; monitoring materials; borrowing and returning of books and other library materials; assessing the overdue; inventorying; and creation of statistics and reports, which otherwise have to be performed manually in an ordinary daily basis.M ore specifically, this system will allow a certain user to manage, organize and monitor the data and attendance of the clerks, the status of the books and other library properties and the library records of the registered students to the library. Nevertheless the access to these capabilities will depend on the user privilege of an account. It will automatically provide statistical reports based on the data stored in its associate database which is updated consistently. Therefore the software will give an ease to do these tasks that are vital in managing the library. Definitions, Acronyms and Abbreviations |Term |Definition | |Borrower |Any person who wishes to borrow books inside the school library. | |Clerk |Any person who assists the librarian in minor tasks needed performed inside the library. | |Database |A collection of all data produced by the system. | |Librarian |A person who is assigned responsible in generally managing the school library. |QR Code |Quick Response code, a type of bar code/encrypted code that will be used for the project in identification | | |purposes. | |Requirements |Refers to the â€Å"what† the product has to do, not the â€Å"how† it is be done. | |SC |Abbreviation of the name of the school where the system will be proposed. The Samar College | |SRS |Software Requirements Specifications.A document that completely describes all of the functions of a proposed| | |system and the constraints under which it must operate. For example, this document. | |Stakeholder |Any person with an interest to the project but is not a developer. | |User |Any person who operates or interacts directly with the product. | |VB |Visual Basic, a building/programming software used in creating the system | |XAMPP |An application used to have a connection between the product and its database. 4 References IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements Specifications. IEEE Computer Society, 1998. [IEEE] The applicabl e IEEE standards are published in â€Å"IEEE Standards Collection,† 2001 edition. [Bruade] The principal source of textbook material is â€Å"Software Engineering: An Object- Oriented Perspective† by Eric J. Bruade (Wiley 2001). [Reaves SPMP] â€Å"Software Project Management Plan Jacksonville State University Computing and Information Sciences Web Accessible Alumni Database. † Jacksonville State University, 2003. 5 OverviewThe next chapter, the Overall Description section, of this document gives an overview of the functionality of the product. It describes the informal requirements and is used to establish a context for the technical requirements specification in the next chapter. The third chapter, Requirements Specification section, of this document is written primarily for the developers and describes in technical terms the details of the functionality of the product. Both sections of the document describe the same software product in its entirety, but are i ntended for different audiences and thus use different language. Overall DescriptionThis section provides a more detailed overview of the system, including a description of the product’s functions and overarching constraints. 1 Product Perspective A – Flex Automated Library Management System Figure 1 – Context diagram As shown in the Figure 1, A-Flex Automated Library Management System (A-Flex ALMS) is independent from other system and has three active actors and one database (where all information is stored and retrieved from). The Borrower, Clerk and the Librarian have a privilege to access the library system. However, the Librarian alone has the privilege to access the database, i. e. eleting, updating and/or adding such records and making reports. A-Flex ALMS uses Interaction Model, a Use Case Diagram, to make stakeholders easily view the system operation. 2 Product Functionality The product has the following major functionalities: †¢ Automated logging in of students into the library †¢ Automated borrowing and returning of books †¢ Enables to show the status of the books †¢ Enables the clerk to customize the due time of returning books for photocopying purpose †¢ Enables the user to search for a particular book using the system’s specialized built-in search engine †¢ QR code scanner functionality Database data storage 3 Users and Characteristics There are essentially three users for the system and are expected to be computer-literate: the borrower, as this project is being made so obviously the main client for this system who wishes to borrow materials in the library. The students of the school are not only the borrower, faculty and other employees of Samar College who are in the list of the school’s employees, for confirmation, may borrow books if they give envelop to librarian, this envelop will serve as their record of borrowing. The borrower may also be a student from other schools, that are required to register (P 50. 0) to school’s registrar to access a privilege and utilize the offered 8 hours services; the librarian, the main user of the system who manages the library and its database and responsible for activities such as adding book records, deleting book records, updating book status such as if book is issued and etc. ; the clerk, the assistant librarian and secondary user of the system who has a privilege to lend books, they are expected to have a different privilege as to librarian. 4 Operating Environment XAMPP Link from proposed system Figure 2 – Operating environmentThe system will be operated in the Samar College Library, as it was proposed to. When the user interacts into the system, the system will pass the user to the database, through XAMPP v. 3. 0. 12 which allows Windows program to transfer data to and from the database to record every interaction of the user. 5 Design and Implementation Constraints The current constraints on the pro ject are related to the provision of hardware resources to implement and test high-performance features. At present, an Intel Dual-core processor is needed, with a 2 GB RAM, serves as the server, with XAMPP running on top of the Windows 7 operating system.For better performance analysis, a number of dedicated workstations would be beneficial for the student workstation. The hardware that the project will be running on may constrain some design decisions pertaining to real-time and performance, as well as the scanner’s accuracy. Also, certain required hardware within the library imposes specific requirements on the project. The following is a list of constraints pertaining to the accuracy of the library system: †¢ The information of all the users must be stored in a database that is accessible by the system. The students must have logged in upon entering the library before they can borrow materials or books. †¢ The librarian only has the privilege and responsibility for the system’s security and privacy. †¢ Clerk and librarian have different privileges upon using the system. †¢ LAN is not implemented. †¢ BIOS of the system unit should be working to get the real-time in issuing of the books to the borrowers. 6 User Documentation The user can easily understand of the usage of the system with a user’s manual to be delivered with the system.The manual would be helpful with the some screen shoots within it. User can easily learn operation of the system by displaying corresponding shortcuts on controls for simple task. Contacts numbers of the developers will be given to the school librarian for further assistance when complex problems arise. 7 Assumptions and Dependencies A number of factors that may affect the requirements specified in the SRS include: †¢ The users have sufficient knowledge of computers. †¢ The users know the English language, as the user interface will be provided in English. Hardware and syst em specifications might not compatible. †¢ System might not supported by the operating system. †¢ It is assumed that librarian and/or clerk might forget their password for logging in. Specific Requirements 1 External Interface Requirements Below is a list of enumerated requirements that provides additional specifications for the behaviour and functionality of the system. 1 User Interfaces Using this system is fairly simple and intuitive. A user, who has a familiarity with basic logging in navigation, should be able to understand all functionality provided by the system.As Figure 3 shows, the user with different privileges can now select his workstation, with corresponding shortcuts for options, so that the system may give the user an access to these and may let the not be able to use those of privilege he usually should not have. [pic] Figure 3 – Main interface If the user selects the Open Librarian (Ctrl + L), system now then identify him as Librarian, a Server, an d Figure 4 will display with a pop-up form that lets the Librarian to have a three (3) attempts of logging in. If the user failed to log in successfully, system then will automatically shuts down. pic] Figure 4 – Logging station for Librarian If the user selects the Open Clerk (Click + C), system now then identify him as Clerk and Figure 5 then will display asking for an IP address sin order to have a connection to Librarian Workstation, server. [pic] Figure 5 – Clerk station for connection As the Clerk workstation has successfully connected to its server, then Figure 6 now will be displayed. Letting the Clerk to log in, as same of Librarian, if the Clerk failed to log in successfully it will automatically shuts down. [pic] Figure 6 – Clerk station 2 Hardware InterfacesSince the system will be installed in a Local Area Network (LAN) for collecting data from the users and also for updating the Library System and making reports, it is recommended by the developers , in order to have a maximum usage of the system, that the library should have the following: †¢ at least one camera for students’ easy logging in and scanning of books; †¢ printer for making reports; and †¢ computer unit(s) for the Clerk Workstation(s). The librarian then has to decide the number of units whether the library’s clerks would use. 3 Software InterfacesThe system will use only one external software, XAMPP v. 3. 0. 12, for the connection between the system and database. The system has a built in QR (Quick Response) Code Reader. 4 Communications Interfaces The system will be installed and run in a LAN of computer units. 2 Functional Requirements This section provides the detailed list of all product operation with their corresponding specific use case. 1 Librarian Use Cases 1 Use case: Log in Diagram: Brief Description The Librarian accesses the system, and can do various tasks. Initial Step-By-Step DescriptionBefore this use case can be init iated, the Librarian has already set up or prepared the units to be used. 1. The Librarian hits Ctrl + L, the option log in for a Librarian. 2. The system displays the pop-up login for the Librarian. 3. The Librarian selects the log in. 4. The system records the info into the database. 2 Use case: Log out Diagram: Brief Description The Librarian is signing off the system. Initial Step-By-Step Description Before this use case can be initiated, the Librarian has already successfully logged in. 1. The Librarian clicks his name at the left top of the form. . The system displays the pop-up confirmation for log out. 3. The Librarian selects the OK button. 4. The system records the info into the database. 5. The Librarian has logged out. 3 Use case: Search book Diagram: Brief Description The Librarian gets the list of books and info. Initial Step-By-Step Description Before this use case can be initiated, the Librarian has already successfully logged in. 1. The Librarian selects the form fo r books, borrowers, etc. then chose the book. 2. The system displays the list of books and shows the different categories. 3.The Librarian selects the category. 4. The system gets the selected category to dataset and at the same time records it. 5. The system displays the matched book(s). 6. 4 Use case: Issue book Diagram: Brief Description The Librarian is able to issue the book(s) to the borrower(s). Initial Step-By-Step Description Before this use case can be initiated, the Librarian confirmed the borrower that he has a validated registration. 1. The system Librarian searches the books in the list. 2. The system displays the list of books and shows whether the book is listed and/or available. a.If the book’s copy is more than one (1) and is available, the Librarian sets the due date/time. b. If the book is not available due to some reason, the system will automatically alerts the Librarian that the requested book(s) is not available and thus will automatically gives the re ason(s). 3. The system gets the due date/time to be recorded to the database. 4. The system will give a confirmation that the transaction is successful. 5 Use case: Update database Diagram: Brief Description The Librarian wanted to do some tasks the he/she needed the data be manipulated in the database.He or she also can update the database. Initial Step-By-Step Description Before this use case can be initiated, the system has verified that the Librarian is logged in. 1. The system displays categorized options of the entire data. 2. The Librarian selects the category. 3. The system gives other options of that selected category. 4. The system gets the selected category to dataset and at the same time records it. 5. The system displays the matched selected category. 2 Clerk Use Cases 1 Use case: Log in Diagram: Brief Description The Clerk accesses the system, and can do various tasks.Initial Step-By-Step Description Before this use case can be initiated, the Clerk has already set up o r prepared the units to be used. 1. The Librarian hits Ctrl + C, the option log in for a Clerk. 2. The system displays the pop-up login for the Clerk. 3. The Clerk selects the log in. 4. The system records the info into the database. 2 Use case: Log out Diagram: Brief Description The Clerk is signing off the system. Initial Step-By-Step Description Before this use case can be initiated, the Clerk has already successfully logged in. 1. The Clerk clicks his name at the left top of the form. . The system displays the pop-up confirmation for log out. 3. The Clerk selects the OK button. 4. The system records the info into the database. 5. The Clerk has logged out. 3 Use case: Search book Diagram: Brief Description The Clerk gets the list of books and info. Initial Step-By-Step Description Before this use case can be initiated, the Clerk has already successfully logged in. 1. The Clerk selects the form for books, borrowers, etc. then chose the book. 2. The system displays the list of book s and shows the different categories. 3.The Clerk selects the category. 4. The system gets the selected category to dataset and at the same time records it. 5. The system displays the matched book(s). 4 Use case: Issue book Diagram: Brief Description The Clerk is able to issue the book(s) to the borrower(s). Initial Step-By-Step Description Before this use case can be initiated, the Clerk confirmed the borrower that he has a validated registration. 1. The system Clerk searches the books in the list. 2. The system displays the list of books and shows whether the book is listed and/or available. . If the book’s copy is more than one (1) and is available, the Clerk sets the due date/time. b. If the book is not available due to some reason, the system will automatically alerts the Clerk that the requested book(s) is not available and thus will automatically gives the reason(s). 3. The system gets the due date/time to be recorded to the database. 4. The system will give a confirma tion that the transaction is successful. 5 Use case: Return book Diagram: Brief Description The Clerk returns the book he/she has borrowed. Initial Step-By-Step DescriptionBefore this use case can be initiated, the Clerk, now as borrower, must return the book on time. 1. The Clerk himself may return the book he has borrowed. 2. The Clerk selects the Borrowed tab on the Borrowed form. 3. The system will display on the grid the borrowed books including his book. 4. The Clerk may scan the book with QR Code, or he may manually put the accession number of the book. 5. The system them will check for its due date and time, evaluates the time consumed for penalty if the clerk wasn’t able to return the book on time. 6. The system records info into the database.Note: All Librarian assistants in the school’s library are working students, so therefore they may somehow be a â€Å"borrower†. 6 Use case: Add Diagram: Brief Description The Clerk adds some info, it might be addi ng books or borrowers to the database. Initial Step-By-Step Description Before this use case can be initiated, the Clerk has given permission from the Librarian and thus he has already data to be stored in the database. And he has successfully logged in to the Clerk’s form. 1. As he logged in, the clerk clicks the â€Å"Add† tab on the Clerk’s workstation. 2.The system displays an option on whether what the clerk wants to add or store. 3. The clerk chooses an option. 4. The system displays needed data to be filled out whether it’s either a new book or new borrower. 5. The system then evaluates the input before storing to the database. a. If the required data is completed, the system displays a message box as notification of a new data. b. If some required data is missing, otherwise, a message box will be displayed to notify that some important data are not properly filled out. 7 Use case: Update database Diagram: Brief DescriptionThe Clerk modifies some d ata that are stored in the database. Initial Step-By-Step Description Before this use case can be initiated, the Clerk scanned some info, might in the book or borrower, and is incorrect. 1. The Clerk selects the â€Å"Update† tab on the Clerk’s workstation. 2. The system displays the pop-up options of the data to be updated to be edited. 3. The system displays the info that the Clerk wanted to update. 4. After the Clerk verified the correct records, the system then will display the updated data of a specified record. 3 Borrower Use Cases 1 Use case: Log inDiagram: Brief Description The Borrower, if student, logs in through the scanner by swapping their IDs with QR Code. Otherwise, if the scanner is not available he can manually input his student number. The faculty who wants to borrow has no record of logging in but they have to provide an envelope that the librarian refers to. Initial Step-By-Step Description Borrower enters the library. 1. The Borrower looks for the needed book(s) to borrow. He can ask the clerk to search the book(s) through the system. 2. The system displays the possible results for the input info. Use case: Borrow Diagram: Brief Description The Borrowers, either a student or faculty, borrows their needed book. Initial Step-By-Step Description Before the Borrower can have the needed book(s), he successfully logged in inside the library. 1. The Clerk selects the tab for borrowing within the Clerk’s workstation. 2. The system displays the required data to be filled out for the borrowing. 3. After the Clerk or Librarian hits the OK button, the system will evaluates the borrower if he or she has due book(s) that not yet been returned. 4.The system displays the notification and due date and time of the borrowed book(s) upon the request of the Clerk for borrowing the book then records it to the database. 3 Use case: Return Diagram: Brief Description The Borrower returns the book he or she has borrowed. Initial Step-By-Step De scription Before this use case can be initiated, the Clerk Borrower must log in inside the library. 1. The Borrower asks anyone among the Clerks for returning assistance. 2. The Clerk selects the â€Å"Borrowed† tab from the Borrowed form. 3. The system will display on the grid all the borrowed books including his book. 4.The Clerk may scan the book with QR code or he may manually input the accession number of the book. 5. The system them will check for its due date and time, evaluates the time consumed for penalty if the Borrower wasn’t able to return the book on time. 6. The system records info into the database. Other Non-functional Requirements 1 Performance Requirements 1. Response Time – The Splash Page should be able to be load within seconds using a Windows 7 32-bit Operating System and at least 1 GB memory (RAM). The information is refreshed every two minutes. The access time for the computer unit should be less than a minute.The system shall respond to the member in not less than two seconds from the time of the request submittal. The system shall be allowed to take more time when doing large processing jobs. 2. Administrator/Librarian Response – The system shall take as less time as possible to provide service to the administrator or the librarian. 3. Throughput – The number of transactions is directly dependent on the number of users, the users may be the Librarian, employees of the Library and also the people who use the Library for checking-out books, returning books and checking library account. . Resource Utilization – The resources are modified according the user requirements and also according to the books requested by the users. 2 Safety and Security Requirements The server on which the Library System resides will have its own security to prevent unauthorized write/delete access. There is no restriction on read access. The use of email by an Author or Reviewer is on the client systems and thus is ext ernal to the system. The PC on which the Clerk resides will have its own security. Only the Editor will have physical access to the machine and the program on it.There is no special protection built into this system other than to provide the editor with write access to the Library System to publish reports. 3 Software Quality Attributes 1 Functionality Logon Capabilities The system shall provide the users with logon capabilities. Alerts The system can alert the Librarian or the administrator with notifications regarding the status of the books and in case of any problem. 4 Usability †¢ The system shall allow the users to access the system from a stand-alone client or its derivative technologies for public inquiries of the students.The system uses another computer unit for the client interface. †¢ The system is user friendly. 5 Reliability The system has to be very reliable due to the importance of data and the damages incorrect or incomplete data can do. Availability The s ystem is available 100% for the user. The system shall be operational 8 hours a day and 7 days a week. Accuracy The accuracy of the system is limited by the accuracy of the speed at which the employees of the library and users of the library use the system. Access Reliability The system shall provide 100% access reliability. 10 SupportabilityThe system designers shall take in to considerations the following supportability and technical limitations. Information Security Requirement The system shall support the information security requirements. Maintenance The maintenance of the system shall be done as per the maintenance contract. Standards The coding standards and naming conventions will be as per the American standards. Appendix A – Data Dictionary |Borrower – Any person who wishes to borrow books inside the school library. | |Clerk – Any person who assists the librarian in minor tasks needed performed inside the library. |Database – A collection of all data produced by the system. | |Librarian – A person who is assigned responsible in generally managing the school library. | |QR Code – Quick Response code, a type of bar code/encrypted code that will be used for the project in identification purposes. | |Requirements – Refers to the â€Å"what† the product has to do, not the â€Å"how† it is be done. | |SC – Abbreviation of the name of the school where the system will be proposed, the Samar College | |SRS – Software Requirements Specifications.A document that completely describes all of the functions of a proposed system and the | |constraints under which it must operate. For example, this document. | |Stakeholder – Any person with an interest to the project but is not a developer. | |User – Any person who operates or interacts directly with the product. | |VB – Visual Basic, a building/programming software used in creating the system | |XAMPP – An applic ation used to have a connection between the product and its database. Appendix B – Group Log Notes Taken during our first meeting with Jun, Arnel & Marlon on January 23, 2013. †¢ Interview the librarian †¢ interview the library employees †¢ understand the flow of data in the library †¢ understand the processes used in transactions in the library †¢ new design †¢ lan network †¢ create a floor plan including 3 units for 3 stations of the whole system †¢ 3 stations: Admin station, Clerk Station, Log in Station †¢ provides photocopies of authentic documents from the library †¢ learn the penalty system of the library copy the list of books †¢ list the basic requirements †¢ Software Requirements Specification for Page 12 †¢ fix the QR scanner †¢ dry run the system †¢ Should we try this for different operating system environment? †¢ We might need licenses, ask if necessary. †¢ Given our budgets, th is is the best we can do. †¢ Set up servers. †¢ Began looking through test cases †¢ Will work on SRS †¢ Jun Abanag †¢ Created QR code samples for ID †¢ Will work on SRS. †¢ Marlon Alegro. †¢ Will work on SRS. †¢ Jun Abanag. †¢ Will work on SRS. †¢ Scrum Meeting 2/8/2013 †¢ Marlon Alegro Downloaded licensed software. †¢ Worked on SRS. †¢ Will work on feedback to finalize SRS. †¢ Nicholas Cross †¢ Worked on SRS. †¢ Will work on feedback to finalize SRS. †¢ Jun Abanag & Marlon Alegro †¢ Worked on SRS. †¢ Will wait on feedback from mentor to finalize SRS. Group activities †¢ Overnight sessions (starts at 10 in the evening up to 5 in the morning: 7 hours) Most of us have part time jobs during day time and we have different schedules for Software Engineering so we used our time to work during evening and midnight because of the busy schedule during day time.We spend seven hours during midnight to work on our system and the SRS. ? Alegro Residence one a week ? Abagua Residence one a week 11/15/2012 11/18/2012 11/19/2012 11/23/2012 12/4/2012 12/12/2012 12/15/2012 †¢ Group meetings Since we have different schedules for Software Engineering, we try to meet up during free hours. And most of the times we are not complete because of the busy schedule. So what we do is two of our group mates meet up at certain time and the other one would discuss it to the other member when they meet.So in that way we can exchange ideas even though we don’t meet properly. Afterwards, the other few members will also catch up with updates from the recent group discussion. ? Samar College, twice a week. Every Monday, Wednesday and Friday ? Alegro Residence one a week ? Abagua Residence one a week 11/15/2012 11/18/2012 11/19/2012 11/23/2012 12/4/2012 12/12/2012 12/15/2012 Index |A |Log out (use case), | |A –Flex ALMS, 5, 7, 8 | Clerk, 19 | |Add book (use case), 22 | Lib rarian, 16 | |Assumptions and Dependencies, 9 | | | |O | |B |Operating environment, 9 | |book, (use case) |Overall Description, 7 | | Borrow, 24 |Overview, Product, 6 | | Issue, 21, 1 7 | | | Search, 16, 20 |P | | Return, 21, 25 |Performance Requirements, 27 | |Borrower, 5, 7,8 |Product | | | Functionality, 8 | |C | Perspective, 7 | |Clerk, 5, 8 | | | use cases, 19 |Q | | station, 14 | QR (Quick Response), 5, 13 | |Context Diagram, 7 | | |Communication Interface, 15 |R | |References, 6 | |D |Reliability, 28 | |Delete (use case), 7 |Requirements | |Document purpose, 5 | External Interface, 11 | | | Functional, 15 | |E | Other Non-Requirements,27 | |External interface, 11 | Performance, 27 | | | Safety and Security, 27 | |F | Specific, 11 | |Functional Requirements, 15 |Return book (use case), 21, 25 | |Functionality, 8, 28 | | | |S | |I |Safety and Security Requirements, 27 | |Interfaces |SC, 6 | | Communication, 15 |Search book (use case), | | Hardware, 14 | Clerk, 20 | | Software, 14 | Librarian, 16 | | User, 14 |Software Interface, 14 |Issue, 17, 21 |Software Quality Attributes, 28 | | |Specific Requirement, 11 | |L |SRS, 6 | |Log in (use case) |Stakeholders, 6 | | Borrower, 24 |Supportability, 28 | | Clerk, 19 | | | Librarian, 15 | | | | | U | | |Use cases | | | Borrower, 24, 25 | | | Clerk, 19, 20, 21,22, 23 | | | Librarian, 15, 16, 17, 18 | | |User, 5, 6, 8 | | | characteristic, 8 | | | documents, 10 | | | interfaces, 9 | | | | |X | | |XAMPP, 6, 9, 14 | | ———————– Borrow books Librarian Clerk Search User System Database Librarian Update database Log in Article Borrower Issue book DATABASE Issue books Add Article Report Delete Article Update Librarian < include > < include > < include > < include > < include > Librarian Search book Log out Return books Log out Librarian Log in Librarian Log in

Narrative Of The Narrative Paradigm Theory - 1830 Words

Narrative Paradigm Theory The narrative paradigm theory stresses the effectiveness of influence through narration, which is persuasion through storytelling. This means that advertisements use storytelling to persuade which is highly used in the Superbowl ads. When the narrative used appears to flow smoothly, makes sense and is believable it is said to have narrative coherence. In addition, when the narrative used in persuasion looks like it is honest, and aligns with our own experiences, we can say there is narrative fidelity. In order to accept a narrative as believable, a person must perceive the narrative’s fidelity first, because without fidelity, coherence does not matter. â€Å"Advertising can assume the form of either arguments or narratives. Argumentative advertising tends to present fact-based information that persuades through logical arguments and lectures, whereas narrative advertising tells a story about product consumption or related experiences or presents the consequences of the product’s usage and achieves persuasion by appealing to the consumer’s affective and emotional responses. Narrative advertising often uses drama and story telling, humor, and/or editorial narrative to evoke a person’s emotions and empathy with the characters in the story.† (Ching, Pingsheng, Chen, and Chen, 2013) The narrative paradigm theory expands on Aristotle’s three means of persuasion: ethos, pathos and logos. Ethos, being the ethical mean of persuasion, plays on the receiver’sShow MoreRelatedThe Theory Narrative Paradigm 1696 Words   |  7 PagesThe theory â€Å"Narrative Paradigm† by Fisher focuses on the use of narration as one of the human communication mechanisms. His publication or article which he wrote in 1985 was supported by several people as one of the wonderful and great works done in the 21st century. Fisher’s narrative has been a valued concept starting from the period of Aristotle’s poetics. Fisher came up with narrative paradigm as retaliation to the conflict that he saw in Epistemology and Axiology. In his remarks the theory ofRead MoreThe Narrative Theory / Paradigm1477 Words   |  6 PagesThe narrative theory/paradigm states that everything we do can be laid out as a story (Fisher, 1984). The main points of the theory/paradigm a re the following: humans are essentially storytellers; decisions that humans make are based off of good reasons rather than proof; what we do and how we think is swayed by accounts of history, biography, culture and character; our rationality is determined by our sense of probability (the coherency of the narrative) and narrative fidelity (whether the storyRead MoreThe Narrative Paradigm And Family Systems Theory1333 Words   |  6 Pagesbeen conducted to examine this marginalized community? Through the narrative paradigm theory, this section will further investigate some of the factors that led certain families to become homeless while trying to recognize the limits that the narrative paradigm provides. Narrative Paradigm Family Systems Theory The narrative paradigm created by Walter Fisher states that, â€Å"[it is] a theoretical framework that views narratives as the basis of all human communication† (Griffin, Ledbetter, SparksRead MoreWalter Fishers Narrative Paradigm Analysis727 Words   |  3 PagesNike, Coca-Cola and Motel 6 respectively, you are correct. These slogans you may have seen or heard are a prelude to stories aimed to entice consumers. Walter Fisher created the narrative paradigm in 1984. Our book lists several communication theories under the heading of group and public communication; narrative paradigm is one of them. Fisher contends it is human nature to communicate using storytelling. Relating events in this manner helps us make decisions. Stories passed down from generationRead MoreThe Narrative Paradigm By Scott Stroud1299 Words   |  6 Pages Scott Stroud in his article Multivalent narratives: Extending the Narrative Paradigm with Insights from Ancient Indian Philosophical Texts critiques the narrative paradigm by pointing out its weaknesses and proposing revisions to the existing paradigm using ancient Indian philosophical narratives. Stroud claims that Fisher’s paradigm is too limiting and conservative when dealing with foreign concepts and texts. The narrative paradigm does not allow people to experience new stories that may differRead MoreReassessing Surrealism: Constructivism and Postcapitalist Appropriation1090 Words   |  5 Pagesis the fatal flaw, and subsequent economy, of deconstructivist society. It could be said that Sontag promotes the use of subcultural discourse to modify and attack sexual identity. Marx uses the term ‘postcapitalist appropriation’ to denote not theory, but neotheory. However, Lyotard’s analysis of constructivism holds that the media is part of the collapse of art. Derrida uses the term ‘postcapitalist appropriation’ to denote the rubicon, and eventually the futility, of pretextual society. ButRead MoreThe Three Paradigms of Biblical Studies Essay852 Words   |  4 Pagesworld. These scholars use various methods developed by other disciplines in order to study ancient texts along with other approaches that are distinctive to the biblical studies. Biblical scholars have recently divided the profession into three paradigms which are commonly referred to as the three worlds. Particularly, some scholars focus on the world within the text; others explore the world in front of the text; and others focus on the world behind the text. Firstly, scholars who look at theRead MoreJohn Oliver Rhetorical Analysis1401 Words   |  6 PagesUsing Theories to Assess Improve Messaging: John Oliver and the New York Yankees Analyzing communication messages through late-night shows varies. Mixing humor with specific news stories provides an interesting message, depending on the audience. Last Week Tonight With John Oliver uses specific news segments and analyzes it through the use of extensive research and humor. This includes his segment on the New York Yankees, where he makes it very clear which position he is taking on the issueRead MoreExpressionism And Structuralist Dematerialism : The Primary Theme Of La Fournier s1839 Words   |  8 Pagesdialectic paradigm of reality that includes culture as a reality. If one examines structuralist dematerialism, one is faced with a choice: either reject postcultural dialectic theory or conclude that narrativity is used to exploit the Other. Many narratives concerning the genre, and therefore the futility, of pretextual society may be found. Therefore, we have to choose between expressionism and the subtextual paradigm of narrative. A number of dematerialisms concerning capitalist narrative exist. StructuralistRead MorePositive Evaluation Of Attractive Movie Characters And Advertising Models2129 Words   |  9 Pagesliking of the ad and therefore, the product. However, if there is a same-sex situation where the beauty-is-good stereotype is present, it can also contradict the social comparison-jealousy theory. In Praxmarer’s research, it was found through empirical support that the level of attractiveness determines which theory and action takes effect. If the presenter is moderately attractive, then the presenter’s physical attractiveness will lead to the beauty-is-good stereotype. However, if the presenter’s attractiveness