Srs of Library Membership System Free Essays

SOFTWARE REQUIREMENTS SPECIFICATION (SRS) for the System Name UNISEL LIBRARY MEMBERSHIP SYSTEM Prepared For: MDM NOR AZLIANA AKMAL JAMALUDIN Prepared By: MOHAMAD HAFIZ BIN MOHAMAD NOOR 4111017111 LOGGESWARAN SINNAIH4111009881 MUHAMMAD ABDUL HAKIM BIN ZAINI 4111022751 SYED AHMAD RIDHWAN BIN SYED MOKHTAR 4111023651 Authenticated by __________________Approved by__________________ Date ___________________Date __________________ TABLE OF CONTENTS 1. Scope†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 4 1. We will write a custom essay sample on Srs of Library Membership System or any similar topic only for you Order Now 1 IDENTIFICATION†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 1. 2 Module overview†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 4 1. 3 Document Overview†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 6 1. 4 Relationship to other plan†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 6 2. reference†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 7 2. 1 Government Documents†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 7 2. 2 Non-Government Documents†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. †¦Ã¢â‚¬ ¦7 2. 3 Contractual documents†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. †¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 7 2. 4 Non-contractual document†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. †¦.. 7 3. Engineering Document †¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 8 3. 1 System Context Diagram†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 3. 1. 1 Unisel library Membership System†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 9 3. 1. 1. 1 Description†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦10 3. 1. 1. 2 Association†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦10 3. 1. 1. 3 Description†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦10 3. 1. 1. 4 Association†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ †¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦10 3. 2 General System Requirements†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 11 3. 2. 1 Use Case Name 1 (SRS_REQ1_001)†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 13 1 3. 2. 1. 1Brief Description†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. †¦Ã¢â‚¬ ¦13 2 3. 2. 1. 2Characteristic of Activation†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. †¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦13 3 3. 2. 1. 3Pre-Condition†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦13 4 3. 2. 1. 4Basic Flow†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 13 5 3. 2. 1. 5Alternative Flow†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 3 3. 2. 2 Use Case Name 1 (SRS_REQ1_002)†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã ¢â‚¬ ¦.. 14 6 3. 2. 2. 1Brief Description†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 14 7 3. 2. 2. 2Characteristic of Activation†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 14 8 3. 2. 2. 3Pre-Condition†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦14 9 3. 2. 2. 4Basic Flow†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 14 10 3. 2. 2. 5Alternative Flow†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. †¦Ã¢â‚¬ ¦15 3. 2. 3 Use Case Name 1 (SRS_REQ1_003) †¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 15 11 3. 2. 3. 1Brief Description†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. †¦.. 15 12 3. 2. 3. 2Characteristic of Activation†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 1 5 13 3. 2. 3. 3Pre-Condition†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 15 14 3. 2. 3. 4Basic Flow†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. †¦Ã¢â‚¬ ¦ 15 15 3. 2. 3. Alternative Flow†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 15 3. 2. 4 Use Case Name 1 (SRS_REQ1_004)†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 16 16 3. 2. 4. 1Brief Description†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦16 17 3. 2. 4. 2Characteristic of Activation†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. †¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦16 18 3. 2. 4. 3Pre-Condition†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦16 19 3. 2. 4. 4Basic Flowâ₠¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. †¦Ã¢â‚¬ ¦16 20 3. 2. 4. 5Alternative Flow†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. †¦Ã¢â‚¬ ¦16 3. 3 Exception Flow †¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 17 3. 3. 1 Post condition†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 17 3. 3. 2 Rules (s) †¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 17 3. 3. 3 Constraint (s) .. †¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 17 3. 3. 4 Note (s) †¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. †¦Ã¢â‚¬ ¦ †¦Ã¢â‚¬ ¦. 18 4. Gui †¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 19 3. 4. 1 Main Screen†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦19 3. 4. 2 Registration†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦19 3. 4. 3 Logging in†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 19 3. 4. 4 About us page†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 19 3. 4. 5 Database page†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 19 3. 5CSCI Internal Interfaces †¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚ ¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 24 3. 6 Module data element requirements†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 24 3. 7 Adaptation Requirements†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 25 3. 8 Sizing and Timing Requirements†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 5 3. 9Safety Requirements†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 25 4. 0Requirements Traceability†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦26 4. preparation for delivery †¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 26 5. Note †¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â ‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦ 26 1SCOPE 1 1. 11. 1 Identification System Number : 01-02-022-R0-2006-03 System Name: UNISEL LIBRARY MEMBERSHIP SYSTEM System Abbreviation: 01-02-022-R0 Module Number: 01-02-022-R0-2006-03 Module Name: UNISEL LIBRARY MEMBERSHIP Module Abbreviation: 01-02-022-R0 2 1. 21. 2 Module Overview This paragraph describes the purpose of the system and the module to which this SRS applies. Purpose of the Unisel Library Membership System: The main purpose of the system is to make the registration process and book borrowing process easier. Purpose of the Unisel Library Membership System: 1. Online registration -Students can make registration from their place without going to the library. They can go to the online library page and key in their information and register themselves. 2. Information about the library -The main page of the system contains the information about the library and also the information about the system. It also contains the procedures for borrowing the book from the library. 3. Administrator login -This page is the login page for the Administrators. There is place to enter â€Å"username†, â€Å"password† and a â€Å"login† button. Once they enter the username and password correctly, the system will direct them to another page. 4. Student database -This is the database page that contains all the registered student’s information. This page contains student’s name, id, race, course, religion, password, email, address, membership type, and faculty. 3 1. 31. 3 Document Overview This document describes the interaction between the actors with the module Unisel Library Membership System. Analysis of the requirements applying to Unisel Library Membership System relies on an OOAD UML notation using the Rational Rose 2000 tool. Certain elements resulting from this analysis are presented in this document. Chapter 1:Scope Chapter 2:Referenced Documents Chapter 3:Engineering Requirements Chapter 4: Qualification Requirements Chapter 5: Preparation for Delivery Chapter 6:Notes 4 1. 41. 4 Relationship to other plans Not applicable. 2REFERENCE DOCUMENT The following documents, for which the exact is indicated, form part of the specification as far as everything specified hereafter is concerned. In the event of a discrepancy between the documents referred to here and the content of this specification, it is the content of the specification, which should be considered to be the background reference. Copies of specifications, standards, drawings and publications requested by suppliers in contact with the specified supplying functions may be obtained by contacting the contracting agency or directly through the contracting office. 1 2. 12. 1 Government Documents Not applicable. 2 2. 22. 2 Non-Government Documents |[1] |Sommerville Software Engineering | |[2] |System Requirement Study | | | | 3 2. 3 Contractual documents Not applicable. 4 2. 42. 4 Non-contractual document Not applicable. 3ENGINEERING REQUIREMENTS 1 3. 13. 1 System Context Diagram Figure 1: Context Diagram Figure 2: Use Case Diagram Figure 2 System Flow 3. 1. 1Unisel Library Membership System System Interface Identification: System Administrator Interface Type: Person 3. 1. 1. 1 Description The System Administrator is an actor who responsible for managing Unisel Library Membership System. He / She will manage the users and contents of Unisel Library Membership System. 3. 1. 1. 2 Association This actor communicates with all of the use cases. Interface Identification: Normal User Interface Type: Person (Student) 3. 1. 1. 3 Description Normal User are the students, they can only use â€Å"Main Page†, â€Å"Registration Page† and also the â€Å"Book Borrowing Page†. . 1. 1. 4 Association This actor communicates with the following use cases : 1. visit main page 2. register – normal user can register 3. using the system – normal user use the system only for borrowing 2 3. 2 3. 2General System Requirements 3. 2 HAHH STUDENT Figure 2: Use Case 3. 2. 3Use Case Name3 (SRS_REQ1_001) Eg: F igure 5: Use Case Registration diagram 1 3. 2. 3. 1Brief Description Student must complete the form and click submit if the form has been completed. We have fill in to register as a library member. 2 3. 2. 3. 2Characteristic of Activation Students must register first before using the system library, personal information should be stored in the system. 3 3. 2. 3. 3Pre-Condition 4 1. System displays registration button. (SRS_REQ1_003) 5 3. 2. 3. 4Basic Flow 1. This use case begins when the first register. 2. Registration display system that includes the following options: A-1: We have text box for name, id, race, course, religion, password, email and address. After insert detail click submit button to submit the form after completely fill in the form. 3. The use case ends. 7 3. 2. 3. 5Alternative Flow Not applicable. 3. 2. 1Use Case Name1 (SRS_REQ1_002) Eg: Figure 3: Use Case Main Screen diagram 1 3. 2. 1. 1Brief Description The main screen is a main page about the online registration for the library. The main page have a button home, about us and registration. 2 3. 2. 1. 2Characteristic of Activation User must register and enter the password and the email address or Id card. 3 3. 2. 1. 3Pre-Condition 1. System displays user or person menu. (SRS_REQ1_001) 2. User can’t access Administration page. (SRS_REQ1_001) 4 3. 2. 1. 4Basic Flow 1. This use case begins when the user has registered information on the first page. 2. System display home, about us and registration which including the following options: – Additional buttons are about us and registration to assist the customers. 3. The use case ends. 5 3. 2. 1. 5Alternative Flow A-1: Selects Add New library system button 1. Information such as the button for the contact information should be added in the future. (SRS_REQ1_001) 2. The use case continues. A-2: Selects contact information button 1. users can contact if there any problems. 3. 2. 2Use Case Name2 (SRS_REQ1_003) Eg: Figure 4: Use Case about us diagram 1 2 3. 2. 2. 1Brief Description These pages show the library system database. This database shows information about students who have registered to become library members. 3 3. 2. 2. 2Characteristic of Activation The name, id, race, course, religion, password, email, and address, membership type and faculty. 4 3. 2. 2. 3Pre-Condition 5 1. Admin allows to check the details of the information. Unisel library system shows the table that contains the record of all students that are member of the library. Present a form to the admin to allow him to search the record of the students. SRS_REQ1_102) 6 3. 2. 2. 4Basic Flow 1. This use case is begin when the admin click the database page [A-1: Actor select the search bar to view the student database] 2. System display the student information who have registered [A-1: Actor select to view according to name, id, race, course, religion, password, email, and address, membership type and faculty] 3 . The use case ends. A-1: Not applicable. 1. The use case ends. 7 3. 2. 2. 5Alternative Flow [A-1: Actor selects delete] 1. System displays the delete button [A-2: Actor selects menu box button] 2. The use case continues A-2: Actor selects home button 1. System goes back to previous screen. 3. 2. 4Use Case Name4 (SRS_REQ1_004) Eg: Figure 6: Use Case Admin diagram 1 3. 2. 4. 1Brief Description Only admin can check and updates the record information . 2 3. 2. 4. 2Characteristic of Activation Admin can open the data and check the information through the database. 3 3. 2. 4. 3Pre-Condition 1. System displays Administration menu. (SRS_REQ1_004) 2. User has privilege to access Administration page. (SRS_REQ1_004) 4 3. 2. 4. 4Basic Flow 1. This use case is begin when check the information through the database 2. System display admin which including the following options: A-1: Admin can login in admin panel and insert username and password to check the data. 3. The use case ends. 5 3. 2. 4. 5Alternative Flow Not applicable. 6 7 3. 3 Exception Flow †¢ Error massage will appear in registration information could not continue if the information is incomplete. †¢ Error massage will appear to enter the email and password information is wrong. †¢ Error massage will appear when the information is already used. 8 3. 3. 1Post Condition(s) †¢ The system are successful. 9 10 3. 3. Rules(s) †¢ Users not allowed to access the database system. †¢ The register form must be complete before proceed. †¢ Users can access the system anytime. †¢ System can use by all students at UNISEL. 11 3. 3. 3Constraint(s) 12 †¢ Users must knowledgeable about this system before use it. †¢ If form not completed, user cannot submit the form. †¢ User must have id number to lo g in this system. †¢ The information of all the users must be stored in a database that is accessible by the Online Library System. †¢ The university information security system must be compatible with the Internet applications. The users access the Online Library System from any computer that has Internet browsing capabilities and an Internet connection. †¢ The billing system is connected to the Online Library System and the database used by the billing system must be compatible with the interface of the Online Library System 13 3. 3. 4Note(s) 14 †¢ Users can browse to see the books existing currently in the library via online access. †¢ System can update all new information about the university. †¢ System can display the charge fines imposed for late return of books. 1 3. 4 GUI 1) Main Screen In the main page users are able to: I. Do Registration. II. Logging in. III. View information about the library. [pic] Figure 7 : Main Screen 2) Registration I. Click on the button Register. II. Registration page. [pic] Figure 8 : Registration page III. Fill in name, id, race, course, religion, password, Email, address and choose the membership type. IV. Click to submit button (to be complete the registration). 3) Logging in. I. User must type a user name and password to log in the system II. Click the button â€Å"login† to access the system [pic] Figure 9 : Logging in page III. About us page [pic] Figure 10 : about us page 1. On this page it tells the story of rooms available to fine reading materials and system. 2. It also a story about the library system IV. Database page [pic] Figure 11 : Database page I. This database show information of about student who have registered to become library members. II. Admin allow to check the details of information . III. They also can edit and delete it. 3. 5CSCI Internal Interfaces 3. 5. 1Main Class Diagram 1 1.. * 10.. * 10.. * 3. 6Module Data Element Requirements This paragraph identifies the interfaces between the capabilities identified above. In this case, this means that we give the main activity, the list of the classes, the received and sent messages of each class according to an object-oriented viewpoint. 3 3. 53. 7 Adaptation Requirements Not applicable. 4 3. 63. 8Sizing and Timing Requirements |ITEM |INPUT |DESCRIPTION |OUTPUT | | |Username and password |Session will expire if the |System logged out automatically | |20 seconds | |system is idle for 30 minutes | | Table 1: Time Requirements Description 5 3. 73. 9Safety Requirements |ITEM |INPUT |DESCRIPTION |OUTPUT | | | |Insert the wrong id all |System reset all information | |Error |Register |information will be deleted and |automatically | | | |can’t process. | | Table 2 : Safety Requirements 3. 9Requirements Traceability |No |Requirement No. |Description | |1. |SRS_REQ1_001 |System displays Registration | |2. |SRS_REQ1_002 |System displays Main Screen | |3. |SRS_REQ1_003 |System displays Database | |4. SRS_REQ1_004 |System displays Record Information | Table 3: Unisel Library Membership System Use Case Requirements Traceability 4PREPARATION FOR DELIVERY The delivery of documents will be delivered in the following formats: File format:MS Word (. doc) Submission formats:Hardcopy Quantity:1 each 5NOTES Abbreviation used: – CSCIComputer Software Configuration Item – CSCComputer Software Component – CSUComputer Software unit 3. 8 2 3. 10 [pic] ——â₠¬â€Ã¢â‚¬â€Ã¢â‚¬â€Ã¢â‚¬â€Ã¢â‚¬â€Ã¢â‚¬â€œ Admin e-Document Student Unisel Library Membership System Registration online and Web Information Main screen User Home Registration About us Complete Form Submit Form Database Login Login Page Admin Registration Main Screen STUDENT DATABASE RECORD INFORMATION ADMIN Registration Main Screen Database Record Information 1. The register button to access the registration form Logging button Home Button About us button 3. Submit button 2. Registration form . Logging in form. 2. Logging in button Admin Unisel Library Membership System Register Database Student ———————– †¦Ã¢â‚¬ ¦/†¦.. /SRS/120082009 UNISEL LIBRARY MEMBERSHIP SYSTEM V3 A4 00-01-022-0 ITEM NUMBER VERSION FORMAT CSCI NAME DOCUMENT IDENTIFICATION COVER PAGE V3 A4 01-02-022-R0 UNISEL LIBRARY MEMBERSHIP SYSTEM ITEM NUMBER VERSION FORMAT CSCI NAME DOCUMENT IDENTIFICATION V3 A4 01-02-022-R0 UNISEL LIBRARY MEMBERSHIP SYSTE M ITEM NUMBER VERSION FORMAT CSCI NAME DOCUMENT IDENTIFICATION How to cite Srs of Library Membership System, Essay examples