Object-oriented analysis and design

2,963 views
2,818 views

Published on

Object-oriented analysis and design

Published in: Technology, Education
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,963
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
161
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

Object-oriented analysis and design

  1. 1. KETABY Library Management System Presented by: Ahmed Atef Elnaggar Amr Darwish Ibrahim Supervisor: Prof. Ahmed M. Elfatatry 1
  2. 2. Contents • How did we start? • Why do we choose library? (An example of the actual) • Who are we within the project? • How is the project going? (Applying PRINC2) • Revision history. • Purpose and audiences • Over all Library description – Inception phase – Requirements gathering – Feasibility study – Drawbacks of present system – Domain analysis – User categories and their characteristics – Functional ,Non-functional and technical requirements 2
  3. 3. 3 Contents – User documentation – The estimate cost LOC (line of code) / Priority and risk • Business activities (Main and Sub.) • Business process workflow • Use case diagrams and their descriptions • User Interfaces • Collaboration diagrams • Class diagrams • State diagrams • Unit testing – Integration testing – System testing • Conclusion
  4. 4. How did we start? • First we were hesitated about many projects – Attendance system – Hyper market system – Library management system • Finally we decided to go ahead with library management system. We met together many times and divided the work between us and sent Eng. Shimaa a formal email about our project. 4
  5. 5. 5 We decided to use some application like: 1- M.S. Office 2010 2- Software Ideas Modeler 6.10 3- Smart draw 2010 3- Adobe Reader XI
  6. 6. Why do we choose a library? "Books to the ceiling, Books to the sky, My pile of books is a mile high. How I love them! How I need them! I'll have a long beard by the time I read them." By Arnold Lobel 6
  7. 7. Why do we choose library? • Library is regarded as the brain of any institute and universities; many institutes understand the importance of the library to the growth of the institute and their esteem users. LMS supports the general requirement of the library. • Library management system offers many flexible and convenient features, allowing librarians and library users to maximize time and efficiency. It will track on the how many books available in library and books issued to the members. 7
  8. 8. 8
  9. 9. Who are we within the project? • We are students who registered for OOAD course • Or imagine a virtual scenario that we are working for IT company which is applying PRINCE2 standard. • May be PMP or CMMI or ITIL. • Any way PRINCE2 (Projects IN Controlled Environment) which is a de facto process-based method for effective project management. • Used extensively by the UK Government, PRINCE2 is also widely recognized and used in the private sector, both in the UK and internationally. • The key features of PRINCE2 are a: – focus on business justification – defined organization structure for the project management team – product-based planning approach – emphasis on dividing the project into manageable and controllable stages – flexibility that can be applied at a level appropriate to the project. 9
  10. 10. 10 How is the project going? (Applying PRINC2)
  11. 11. 11 Revision history Date D/M/Y version Description 1/4/2013 1.0 Library management sys. 1/5/2013 2.0 Library management sys.
  12. 12. DAVe Desirable Achieve Viable Must be available at all the time and stand to Executive manager. • Improved customer service through greater access to accurate info. • Increased productivity and job satisfaction among staff members as it eliminates duplication of effort. • More economical and safer means of storing and keeping track of information. • Easier access to Information like management reports and stock etc., as well as more accurate and faster results from statistical analyses. • Reduces errors and eliminating the ennui of long and repetitive manual processing. • Greater accountability and transparency in operations. • Improved efficiency and effectiveness in administration and management as it has unprecedented access to real-time information. • More reliable security for sensitive and confidential information. • Appropriate knowledge-based action and intervention can now take place in a timelier manner. 12
  13. 13. 13 Purpose This document describes the software requirements and specification (SRS) for LMS software. The document is intended for the customers and the developer (designers, testers, maintainers). The reader is assumed to have basic knowledge of LMS. Knowledge and understanding of Unified Modeling Language (UML) diagrams is also required. Intended Audience The intended audience consists of: Software Project Managers Software Engineers Software Developers Library Organizers Project Scope LMS is essentially meant of collections, It is a multi-user version and can take care of all the fundamental functions of a Library like Cataloguing, Circulation, Accessioning and Housekeeping. It can satisfactorily cater to all the basic functions of a small library.
  14. 14. 14 Overall Description (Brief) Modern Libraries are not made up of just books but CD ROM’s, articles, project reports. bound volumes are substantial part of the holding, managing the holdings manually is a not a simple job. There are few solutions but many a times, we find ourselves “making them works” by finding “ways to work around” system inadequacies. Moreover we have limited staff resources. these “work around” waste time, effort, and skills that should be sent on user services. Many solutions do not keep up with the technological changes and hence prove to be time wasters. Library management system is a small footprints software suitable for personal /individual libraries. You can store the information about the books and other material and control the movement of the same. Silent Features • Control the movement of books and other material and avoid loosing the same. • Search if you have a specific book in your collection based on the title. author etc. • Print the spine labels for the book, • Find what a specific person has borrowed from you. It offers the following modules Cataloguing, Circulation, Queries
  15. 15. 15 Cataloguing - Salient Features You can create a catalogue of your books, CDs, maps, drawings and all similar collections using this module. It supports various classification schemes like DDC, DD, and CC etc. The cataloguing module is based on AACR2 (Anglo American cataloguing rule Circulation) Circulation Module deals with issue and return of material from the library. It is a barcode & and smart card enabled system and hence the issue and return of material is handled uniformly. You can issue member cards and also do the transactions.
  16. 16. Inception phase • We have been asked to build a computer based library system that will handle the bookkeeping aspects of a library and provide user browsing facilities. • The first thing to do is to go and find out about the target library or libraries to see what they do now and what they would like to be able to do. • We get the following data: 16
  17. 17. Library description • Books and Journals. The library contains both books and journals. It may have several copies of the same book. Some of the books are for short term loans only. All other books may be borrowed by any library member for 3 weeks. After the selected day, they have to pay the fine per day (ten pounds). If the student lost the book he has to purchase the same book and submit to the library. Only members of staff may borrow journals. Members of the library can normally borrow up to 6 items at a time, but members of staff may borrow up to 12 items at a time. New articles arrive regularly and sometime disposed of the catalogue needs to be updated. The current year’s journals are sent away to be bound at the end of each year. • Borrowing. It is essential that the sys. keeps track of when books and journals are borrowed & returned. The new system should produce reminders when a book is overdue. It may be desirable to allow users to extend their loans if the book is not reserved. The system enforces the rules for borrowing given above. • Browsing: The sys. should allow users to search for a book on a particular topic or by an author or by the ISBN. The user should then be able to check if the book is on loan and if so to reserve the book. Requirements gathering 17
  18. 18. Feasibility study 18
  19. 19. Some of the problems being faced in manual system are as follows: 1. Fast report generation is not possible. 2. Tracing a book is difficult. 3. Information about issue/return of the books are not properly maintained. 4. No central database can be created as information is not available in database. 19 Drawbacks of present system
  20. 20. • This whole process in manually, we need to develop the fully automatic library that enables the user to search for the relevant book and they can also who have which book. • We need to computers in the library so that user can access to online books. • We need to bar code scanner, so the user just scans the code and the book will be issued. • The PCs used in the library must be connected to each other. • The system should be accessed from outside over the internet. • The user needs to enter his roll no and the details of the book. • We can also add new feature of member ship in the library in the starting of the year, then they can become the member and they will be issued the role number to run this software. 20 Domain analysis
  21. 21. • To start the design of the system it is useful to decide on a set of use-cases and use-cases involve actors so who are a suitable set of actors? • One way of choosing Actors is to read the description of what the system does and see what external people or systems are mentioned: Members/Patrons Administrator Librarians Guests Browsers User category 21
  22. 22. • Administrator Enough computer knowledge and experience. • Librarians and their assistances Skilled at library daily operation. No much prior computer knowledge. • Members/Patrons and guests Current students and staffs have basic computer knowledge. User characteristics 22
  23. 23. 23 Software project requirements
  24. 24. The Librarian 1. Add Article (Add books and their information of the books to the database) 2. Update Article (Edit the information of the existing books or mark as missing) 3. Delete Article (Wrong entry must be removed from system) 4. Inquiry Members (For enrolled members to view their details, check and print) 5. Inquiry Issuance (For all database articles to check and print) 6. Check out Article (borrow operation) 7. Check In article (return operation) 8. Inquiry waiting for approvals (Generate newly application to be in waiting list) 9. Reserve Article (Booking a book with the name of librarian, it can be pledged) Member 1. Authentication (own an account in the library before accessing system) 2. Search Article (view basic info. of book and its status) 3. Request Article (After successful searching ,can create or cancel booking) 4. Renew or Extension of a borrowed article 5. Check Account (View the history of books issued to him previously) Functional requirements 24
  25. 25. Assistance librarian or librarian :Prepare Library database. Administrator: 1. Add/delete a librarian. 2. Change the password of a librarian. 3. Add/delete a Member. System: 1. Send an email to member when due date comes. 2. Send an email to member when due date passed. 3. Calculate the penalty. Data base system: Proposed Database is intended to store, retrieve, update, and manipulate information related to library which include 1. All basic data related to the article stored in & books availability. 2. The borrow /return long for all action (depends on article). 3. The IDs & password for all the user (Staff information-Members details). 4. Determining level of user & maximum items which he can borrow. 5. Calculation of fines Guest :Register (Full fill all application form for registration, Record his contacts). Functional requirements 25
  26. 26. • Safety Requirements The database may get crashed at any certain time due to virus or operating system failure. Therefore backup is required. • Security Requirements Log in required because depending upon the category of user the access rights are decided. For example if the user is an administrator then he can be able to modify the data, delete, append etc. • Availability Requirements The system should be accessible to members through a website at all time. • Performance Requirements the web site searching engine system should response reasonably. The search time should be less than 5 seconds. The system should not make any mistake on the borrow/return action. • Software Quality Attributes The database should be user friendly. Non-functional requirements 26
  27. 27. • Hardware Constraints The system requires a database in order to store persistent data. The database should have backup capabilities. • Culture, political and religion requirement There are some anticipated category of articles doesn’t suites the Egyptian society. • Software Constraints The development of the system will be constrained by the availability of required software such as database and development tools. • Design Constraints The system must be designed to allow web usability. That is, the system must be designed in such a way that will be easy to use and visible on most of the browsers. Non-functional requirements 27
  28. 28. • Assumptions and Dependencies ,The product needs following third party (Microsoft SQL server to store the database. – Visual studio& IIS to develop Product.) • Hardware requirement : - Server side: -Client side: • Windows Processor: Pentium 4.0 GHz Pentium III or 2.0 GHz • Hard Drive: 80 GB or more 40 GB or more • RAM: 1 GB or higher 1 GB or higher – bar code scanner • Software requirement &Operating Environment – OS: Window 7 and supported for other platform such as Applet, Mac and UNIX. – Product is developed using ASP (Active Server Pages). – Most of the features will be compatible with the Mozilla Firefox, Opera and IE. – MS SQL server 2008 • Communications Interfaces – The Customer must connect to the Internet to access the Website. – Connection between computers inside library via LAN at the speed of 10MBps. – Dialup Modem of 56 kbps, Broadband connection with a Internet Provider. • Web Server: IIS (Internet Information Services is a powerful Web server that provides a highly reliable, manageable, and scalable Web app. infrastructure) 28 Technical(Build) requirements Supplementary requirements
  29. 29. ASP.NET is a Microsoft technology where you will have to purchase the development environment which is Visual Studio. There are many advantages that I have seen in ASP.NET 1. Ease of development where the burden of coding for large or huge web applications reduces while using this language. 2. Master Pages to Improve Efficiency 3. You got your source with You where the web application can be made in different languages as this technology is language independent. 4. Building the application with ASP.net is safe and secure because of windows inbuilt authentication. 5. The web pages written with this language can be easily maintained as the source code and HTML are together for this technology. 6. You get what you pay for 29 Why ASP.NET?
  30. 30. • This application can be easily implemented under various situations. We can add new features as and when we require. • Reusability is possible as and when require in this application. • There is flexibility in all the modules. • There will be no online help for the product at this moment. • A database of library will include magazines, microfilm, videos, audios, online sessions. • Allows patrons to search the database of library assets by date of publication, publisher or subject. 30 Future features requirements
  31. 31. • LMS should handle every day to day library problems and its GUI let the library management personal work very easily. With the help of multi-window opening person can do multiple task in same time. • The product will include user manual. • The user manual will include product overview, complete configuration of the used software (such as SQL server),technical details, backup procedure and contact information which will include email address. • The product will be compatible with the Internet Explorer 8.0 or higher. The data bases will be created in the Microsoft SQL server 2008 31 User Documentation
  32. 32. The estimate effort and cost 32 There are many considerations to estimate cost project like: • LOC(Line Of Code)approach One of the most effective direct measurements for software size is a count of the number of lines of source code that have been implemented. The time and effort involved in implementing a software programs linearly related to the software size in lines of code. • Advantages • Disadvantages. -LOC is a direct measure of S.W size. -LOC is easily counted. -Counting can be easily automated -Simplicity of categorizing code into reusable, new, changed, and reused -Lack of agreement on standards of S.W industry. -LOC counts vary with language. -Difficulty in visualizing LOC early in development. -The same automatic counter may not work for all programming styles in the same language. -A Line of Code is a strange term to most clients. -Some calculated statistics using LOC can be misleading Reference Considerations in Project Cost Estimation Prepared by Randall Colville July 2008
  33. 33. Function Estimated LOC Library user functions 800 Librarian functions 700 Administrator functions 900 Web site and related functions 1000 Library date base 1000 Integration 800 Software interface for Librarian 700 Software interface for administrator 700 Estimate total line of code 6.600 33 LOC(Line Of Code)approach • Quick Facts: development tools: C# Code ,Asp Code ,SQL Project Development Length: 30 days
  34. 34. 34 Given that – Average productivity for systems of this type =1,000 LOC/person-months – Burdened labor rate = 5,000 L.E per month Then – the cost per line of code = 1,000/5,000 = 5 L.E per line – estimated project cost = 6,600*5 = 33,000 L.E – Estimated effort = 66,000/1,000 = 6.6 person-months LOC(Line Of Code)approach
  35. 35. 35 The estimate priority& Risk • Each possible requirement is described in a few short sentences. • Additional information is provided for each requirement to indicate its estimated cost of development, the risk involved and its priority to the success of the system as a whole
  36. 36. 36 Given that – Burdened labor rate = 5,000 L.E per month – Number of working hours = 22days *8hours = 176 Hrs. Then – the cost of working hour = 5,000 L.E / 176 Hrs. = 28.5 L.E per hour – estimated project cost = 28.5 * 970 = 27,645 L.E – Estimated effort = 970 / 176 = 5.5 person-months Candidate requirements Prior. Hrs. Risk Maintains a database of library assets include books and journals. High 100 Low Allows librarian to add assets to the library database. High 10 Med Allows librarian to lend library assets to patrons. High 30 Med Allows librarian to set the length of time to overdue. High 30 Med Maintains a database of library patron accounts. High 80 Allows librarian to access patron account information. High 30 Med Automates the process of assigning fines to patrons when overdue. High 60 Med Allows librarian to generate a mailing of overdue notices. High 120 Med Allows patrons to search the database of library assets by title, author or ISBN. High 80 Med Allows patrons to determine whether an article is available. High 10 Med Allows remote library system to search the asset database. Med 120 High Allow patrons access to all functionality from a remote site via a web site. Med 300 High Total cost per hours 970
  37. 37. • Secured database. • User tracking • Search feature • Calculating fines • Asset tracking. • Rules and penalties 37 Business activities
  38. 38. Expedite onsite search /borrow /return /book sys. Handling online search / hold /send system Frequent updating back-end database system Main &Sub Business activities Log in Search articles Book article Cancel Booking Search articles Book article Cancel Booking Log in Check in articles Check out articles Delete article Updating article Add article IDs & Password of Users Info. of articles 38 Send email
  39. 39. 39 Business Process workflow 1
  40. 40. 40 Business process no 1 Activity name Add asset to database Brief description Using to maintain an asset database records Frequency of execution Every time have a new asset Business actors Admin, Librarian Scalability Able to scalable when adding new categories to database Criticality high Notes Scalability very soon Other non-functional requirement Performance ,speed replay and accuracy Exceptions Primary path Scan library card Authorize account Scan asset Enter asset type Enter book inf. Set due date Add to asset D.B Alternatives Enter account by K.B Enter asset by K.B Enter journal info Add asset to database activity
  41. 41. 41 Workflow diagram 2
  42. 42. 42 Business process no 2 Activity name Issue library card Brief description Using to issue a library card for every user and add record to database account Frequency of execution When doing any change in database like check in or out or reserve asset Business actors Admin, Librarian Scalability -- Criticality high Notes Admin issues for librarian but librarian issues for patron Other non-functional Requirement Should to be accurate Exceptions Primary path 1-Scan un issued library card 2-Enter patron information 3-Create account record Alternatives Issue library card activity
  43. 43. 43 Business process no 3 Activity name Access account info. Brief description Used to verify ,authorize user account Frequency of execution Every time have to login Business actors Admin, Librarian Scalability Able to scalable when adding new librarian or member Criticality high Notes Should to be secure Other non-functional requirement Security and accuracy Exceptions Primary path Scan library card Access account in D.B Display account info. Alternatives Enter account by K.B Access account info. activity
  44. 44. 44 Workflow diagram 3
  45. 45. 45 Business process no 4 Activity name Check in asset Brief description Using when asset return back to library Frequency of execution Business actors Librarian Scalability Criticality Mid Notes Should remove any mark with related asset Other non-functional requirement Speed and accuracy Exceptions Primary path Scan asset Check account balance No Unpaid fine Remove asset from patron's account + Mark asset as checked in Alternatives Enter asset by K.B unpaid overdue fine Display notice of overdue fine Check in asset activity
  46. 46. 46 Workflow diagram 4
  47. 47. 47 Business process no 5 Activity name Check out or reserve asset Brief description Using when asset return back to library Frequency of execution Business actors Librarian Scalability Criticality Mid Notes Should remove any mark with related asset Other non-functional requirement Speed and accuracy Exceptions Primary path Scan library card Authorize account Check account balance No Unpaid fine Scan asset Add asset to patron's account+Mark asset as checked Alternatives Enter account by k.B Unpaid overdue fine Pay overdue fine Reserve asset Check out or reserve asset activity
  48. 48. 48 Workflow diagram 5
  49. 49. 49 Business process no 6 Activity name Delete asset from D.B Brief description Using when asset lost or removed from D.B Frequency of Execution Business actors Librarian Scalability Criticality Mid Notes Should remove any mark with related asset Other non-functional requirement Accuracy Exceptions Primary path Scan library card Authorize account Scan asset Asset not checked out Delete from asset database Alternatives Enter account by K.B Enter asset by K.B asset checked out Remove asset from patron account Delete asset from D.B activity
  50. 50. 50 Workflow diagram 6
  51. 51. 51 Business process no 8 Activity name Pay overdue Brief description Using when asset lost or removed from D.B Frequency of Execution Business actors Librarian Scalability Criticality Mid Notes Should remove any mark with related member Other non-functional requirement Security and accuracy Exceptions Primary path Scan library card Authorize account Check account balance unpaid overdue fine Credit account Alternatives Enter account by K.B No unpaid fine Pay overdue activity
  52. 52. It is clear that the physical objects from the previous section • the member, books, library are correspond to entities • In the Entity-Relationship model, and the operations to be done on those entities • Holds, checkouts, and so on correspond to relationships. • However, a good analysis will minimize redundancy and attempt to store all the required information in as small a space as possible. • Optimize business processes before automating them. • Make activities parallel if possible • Delete unnecessary activities • Combine steps 52 Business process workflow
  53. 53. 53 Business process workflow diagram
  54. 54. 54 Use case Diagram 1
  55. 55. 55 Use case Diagram 2
  56. 56. 56 Use case Description 1 Use case number:1 Use case name: issue library card Goal: Create library card Brief description Add library card for new member to use it in for check out and check in books Actors: admin Frequency of execution When you need Scalability High Criticality Important Post conditions: Update accounts database Other non-functional requirements Use case number:2 Use case name: delete asset Goal: Delete asset Brief description Admin can delete asset from database Actors: admin Frequency of execution If necessary Scalability High criticality important Post conditions: Update assets database Other non-functional requirements
  57. 57. 57 Use case Description 2 Use case number:3 Use case name: add asset Goal: Add asset Brief description Add asset to database to check in or check out Actors: Admin., librarian Frequency of execution When needed Scalability High Criticality important Post conditions: Update assets database Other non-functional requirements Use case number:4 Use case name: generate asset report Goal: Generate report Brief description Generate report to get information about asset Actors: Admin., librarian Frequency of execution When needed Scalability Medium criticality important Post conditions: Update assets database Other non-functional requirements
  58. 58. 58 Use case Diagram 3
  59. 59. 59 Use case Description 3 Use case number:5 Use case name: search asset Goal: Search asset Brief description Search asset by name or author to determine which book to borrow Actors: member Frequency of execution When needed Scalability High Criticality important preconditions: Valid card Other non-functional requirements Use case number:6 Use case name: access account information Goal: Access account information Brief description Get information about member and overdue fines Actors: member Frequency of execution When needed Scalability High criticality important preconditions: Valid card Other non-functional requirements
  60. 60. 60 Use case Diagram 4
  61. 61. 61 Use case Description 4 Use case number:8 Use case name: check in asset Goal: check in asset Brief description Librarian check in asset which will update account database Actors: Librarian Frequency of execution daily Scalability High Criticality important Post conditions: Update asset database Update account database Other non-functional requirements Use case number:7 Use case name: check out asset Goal: check out asset Brief description Librarian check out asset for member which will update account database Actors: Librarian Frequency of execution daily Scalability High Criticality important preconditions: Pay overdue fines Post conditions Update account database Update asset database Other non-functional requirements
  62. 62. 62 Use case Diagram 5
  63. 63. 63 Use case Description 5 Use case number:9 Use case name: generate overdue notice Goal: generate overdue notice Brief description Librarian get information for overdue notice for member Actors: Librarian Frequency of execution when needed Scalability High Criticality important Post conditions Access account information Other non-functional requirements Use case number:10 Use case name: pay overdue notice Goal: Pay overdue notice Brief description Librarian pay overdue fine for member Actors: Librarian Frequency of execution when needed Scalability High Criticality important Post conditions Update account database Other non-functional requirements
  64. 64. 64 User Interface 1
  65. 65. 65 User Interface 2
  66. 66. 66 User Interface 3
  67. 67. 67 User Interface 4
  68. 68. 68 User Interface 5
  69. 69. 69 User Interface 6
  70. 70. 70 User Interface 7
  71. 71. 71 User Interface 8
  72. 72. 72 User Interface 9
  73. 73. 73 User Interface 10
  74. 74. 74 Collaboration Diagram 1
  75. 75. 75 Collaboration Diagram 2
  76. 76. 76 Collaboration Diagram 3
  77. 77. 77 Collaboration Diagram 4
  78. 78. 78 Collaboration Diagram 5
  79. 79. 79 Collaboration Diagram 6
  80. 80. 80 Class diagram
  81. 81. Another powerful way to model systems is in terms of their states and the transitions between states. A simple example for the class issue book is: The diagram shows how the state of book availability changes as a result of borrowing and returning of copies of the book. 81 State Diagrams
  82. 82. 82 State Diagrams
  83. 83. 83 Testing overview Unit testing Integration testing System testing
  84. 84. • Test of subprograms. • Choose 3 subprograms as the test points. • Cover most frequently used functions. • Black box testing – Equivalence testing – Boundary testing 84 Unit testing
  85. 85. • Feature :Search books • Testing content 85 Unit test :case 1 Equivalence classes Selected value inputs Book title only Software engineering Author only Roger S. Pressman Subject only Software development ISBN only 007-123840-9 Two search criteria with “and” relation (book title + author) Software engineering+ Roger S. Pressman Two search criteria with “or" relation (book title/author) Software engineering / Roger S. Pressman More search criteria with “and” relation (book title + author + subject) Software engineering +Roger S. Pressman + Software development More search criteria with “or” relation (book title /author / subject) Software engineering / Roger S. Pressman / Software development
  86. 86. • Feature :Check out assets • Testing content 86 Unit test :case 2 Equivalence classes Value for student ID Value for book number Patron ID without fine book type 1 Patron ID with fine under the limitation book type 1 Patron ID with fine over the limitation Book type 1 Patron ID without fine book type 2 Patron ID with fine under the limitation book type 2 Patron ID with fine over the limitation Book type 2
  87. 87. • Feature :Check in assets • Testing content 87 Unit test :case 3 Equivalence classes Selected value inputs Book of type 1 within due Book of type 1 overdue Book of type 2 within due Book of type 2 overdue
  88. 88. • Big bang method • Proposed test cases – Find books vs. Request – Request vs. Pick up requested book – Check out vs. Online renew • Regression testing at unit level 88 Integration testing
  89. 89. • The purpose of the system testing is to consider all the likely variations to which it will be suggested and push the systems to limits. • The testing process focuses on the logical intervals of the software ensuring that all statements have been tested and on functional interval is conducting tests to uncover errors and ensure that defined input will produce actual results that agree with the required results. • Program level testing, modules level testing integrated and carried out. • Proposed test cases (Non-functional requirements) • The response time of the system(performance) • The volume of the system (performance) • The login procedure of the system (security) 89 System testing
  90. 90. • Is the menu bar displayed in the appropriate contested some system related features included either in menus or tools? • Do pull –Down menu operation and tool-bars work properly? • Are all menu function and pull down sub function properly listed • Is it possible to invoke each menu function using a logical assumptions that if all parts of the system are correct, the goal will be successfully achieved .? • In adequate testing or non-testing will leads – to errors that may appear few months later. – This create two problem 1. Time delay between the cause and appearance of the problem. 2. The effect of the system errors on files and records within the system 90 Software testing
  91. 91. • There are two major type of testing they are (White Box Testing, Black Box Testing). • White Box Testing – White box some times called “Glass box testing” is a test case design uses the control structure of the procedural design to drive test case. – Using white box testing methods, the following tests where made on the system • All independent paths within a module have been exercised once. In our system, ensuring that case was selected and executed checked all case structures. The bugs that were prevailing in some part of the code where fixed • All logical decisions were checked for the truth and falsity of the values. • Black box Testing – Black box testing focuses on the functional requirements of the software. – This is black box testing enables the software engineering to derive a set of input conditions that will fully exercise all functional requirements for a program. • Black box testing is not an alternative to white box testing rather it is complementary approach that is likely to uncover a different • Class of errors that white box methods like.. 1) Interface errors 2) Performance in data structure 3) Performance errors 4) Initializing and termination errors 91 White &Black Box Testing
  92. 92. Our project is only a humble venture to satisfy the needs in a library. Several user friendly description have also adopted. This package shall prove to be a powerful package in satisfying all the requirements of the organization. The objective of software planning is to provide a frame work that enables the manger to make reasonable estimates made within a limited time frame at the beginning of the software project and should be updated regularly as the project progresses. Last but not least it is no the work that played the ways to success but ALMIGHTY Allah. From a proper analysis of positive points and constraints on the component, it can be safely concluded that the product is a highly efficient GUI based component. This application is working properly and meeting to all user requirements. This component can be easily plugged in many other systems. 92 Conclusion
  93. 93. 93

×