Software Design Specification - Advanced Software Engineering | CS 430, Study Guides, Projects, Research of Software Engineering

Download Software Design Specification - Advanced Software Engineering | CS 430 and more Study Guides, Projects, Research Software Engineering in PDF only on Docsity! Software Design Specification RFID Parking Garage Matt Nichols Tony Nichols Contact E-Mail: anichol9@gmail.com March 11, 2008 1.0 Introduction....................................................................................................................4 1.1 Goals and objectives..................................................................................................4 1.2 Statement of scope.....................................................................................................5 1.3 Software context........................................................................................................5 1.4 Major constraints.......................................................................................................6 2.0 Data design.....................................................................................................................8 2.1 Temporary data structure...........................................................................................8 2.2 Database description..................................................................................................8 3.0 Architectural and component-level design....................................................................9 3.1 Program Structure......................................................................................................9 3.1.1 Architecture diagram..........................................................................................9 3.1.2 Alternatives.........................................................................................................9 3.2 Description for Component Keypad Digit Entry.....................................................10 3.2.1 Processing narrative for component Keypad Digit Entry.................................10 3.2.2 Component Keypad Digit Entry interface description......................................10 3.2.3 Component Keypad Digit Entry processing detail...........................................10 3.3 Description for Component RFID Card Scan..........................................................12 3.3.1 Processing narrative for component RFID Card Scan......................................12 3.3.2 Component RFID Card Scan interface description..........................................12 3.3.3 Component Keypad Digit Entry processing detail...........................................12 3.4 Description for Component Admin/User Login/Logoff..........................................14 3.4.1 Processing narrative for component Admin/User Login/Logoff......................14 3.4.2 Component Admin/User Login/Logoff interface description...........................14 3.4.3 Component Admin/User Login/Logoff processing detail................................15 3.5 Description for Component Modify Account Information......................................16 3.5.1 Processing narrative for component Modify Account Information..................16 3.5.2 Component Modify Account Information interface description......................16 3.5.3 Component Modify Account Information processing detail............................17 3.6 Description for Component Process Funds..............................................................18 3.6.1 Processing narrative for component Process Funds..........................................18 3.6.2 Component Process Funds interface description..............................................19 3.6.3 Component Process Funds processing detail....................................................19 3.7 Software Interface Description................................................................................20 3.7.1 External machine interfaces..............................................................................20 3.7.2 External system interfaces................................................................................20 3.7.3 Human interface................................................................................................20 4.0 User interface design....................................................................................................21 4.1 Description of the user interface..............................................................................21 4.1.1 Screen images...................................................................................................21 4.1.2 Objects and actions...........................................................................................22 4.2 Interface design rules...............................................................................................23 4.3 Components available..............................................................................................24 4.4 UIDS description.....................................................................................................24 5.0 Restrictions, limitations, and constraints.....................................................................24 6.0 Testing Issues...............................................................................................................26  To determine the feasibility and cost effectiveness of an RFID parking system that provides efficiency and ease of use.  Improve security over conventional RFID parking systems by adding a keypad for user authentication. 1.2 Statement of scope The user will be provided an RFID card and an online account which they will use to gain access to the parking area and pay for each visit. When the user is ready to enter the parking area, they will place the card within a close proximity to the RFID reader. The proximity will vary depending on the model of the RFID implementation. A unique ID is transmitted from the card to the reader. The reader then transmits the unique ID to the database. In addition to scanning their card, the user will also enter his pin number into the keypad. The system will validate the user and record the time of entry. A signal is then sent to the entrance by the system to allow the user to enter the parking garage. Upon leaving, the user will repeat the same process that he used to entering the garage. The system will record that the user is exiting the parking area and record the time of exiting. The user is then charged the appropriate amount for the visit and the amount is made visible on his account. The user can then login to his account and make a payment on his balance. 1.3 Software context In order to resolve the issue, we must change both the way that customers access the parking garage and how money is transferred between the building owner and the customer. A simple and accessible technology like Radio Frequency Identification (RFID) cards and readers could be employed in order to streamline the entry and exit process. The cards would be tied to customer accounts, to which money could be transferred using a web interface. This new process would grant users virtual immediate entry and exit from the parking structure because the transaction is electronically automated. The garage owner would seamlessly receive correct payment. The process would begin with the user requesting an account through the web interface. This web interface will need to be easy to understand and navigate. After creating an account and receiving a unique RFID card in the mail, the user could deposit money into their account for payment in the parking garage(s) connected to the system. As a user vehicle passes the RFID reader at a garage entrance, the card would be read in order to retrieve account information. If the account balance was above the required minimum, the vehicle would be granted access. When leaving the garage, the RFID reader at the exit would read the user’s RFID card and deduct an appropriate amount of money from the user’s account. This process of entry and exit can be streamlined to avoid the lines associated with the current parking garage procedure. The system would be able to count the number of vehicles in the structure at any one time, and know the amount of free parking spaces, if any, present. 1.4 Major constraints  The system development cost for the initial prototype should not exceed $500.  The final sales cost should be competitive with other typing products and specialized numeric keypad devices that are on the market at the time of sale.  The system should withstand periodic cleaning with a damp cloth and mild detergent.  The system should maintain functionality when introduced to an outside environment.  The system should not contain hazardous materials.  The system should maintain functionality when used repetitively by elementary school aged children.  The system should not interfere with the operation of the personal computer to which it is attached.  The system must comply with Part 15, entitled "Radio Frequency Devices" of Title 47 of the Code of Federal Regulations.  The system keypad should be ergonomic in design so that the occurrence of repetitive stress injuries is minimized.  The system must not expose the user to electrical shock. parts of the architecture would be the user acting as the client, the broker acting as the RFID scanner, and the supplier as the parking garage. But this architecture would only fit for the parking garage aspect of the project and not encompass the website for the parking garage system. The user of the system would have direct access to the website and not have to go through a mediator for information regarding the parking garage systems because the information is provided from the database. 3.2 Description for Component Keypad Digit Entry 3.2.1 Processing narrative for component Keypad Digit Entry The keypad digit entry is done upon arrival at the parking garage gate following the RFID card scan. The digit entry is an added layer of security for access into the parking garage where the user will enter their 3-5 digit password. The information they enter is stored in a temporary file which is then compared to the database information. If the information is correct then the user is granted access into the parking garage. Otherwise they are denied access. 3.2.2 Component Keypad Digit Entry interface description. The input interface is the keypad device found at the entry gate of the garage. The user will enter their password and it is processed by the database for authorization. The output will come from the parking garage light which is represented by a green for access and red for denial. 3.2.3 Component Keypad Digit Entry processing detail 3.2.3.1 Interface description The interface will consist of the numbers 0 through 9 found on any keypad entry device. 3.2.3.2 Algorithmic model (e.g., PDL) Password Entry Grant Access to garage Correct Incorrect 3.2.3.3 Restrictions/limitations  The password is limited to a 3-5 digit password. This can be changed pending if the parking garage administrator wants a longer entry.  Access to the garage if the information is correct.  Denial to the garage if the information is incorrect. 3.2.3.4 Local data structures No data structure is needed for this device. 3.2.3.5 Performance issues  The database should provide the user with access/denial to the garage in a reasonable amount of time, no more then 5-10 seconds. 3.2.3.6 Design constraints  3-5 digit password  Individuals are allowed five attempts before they must contact the garage administrator for troubleshooting. 3.3 Description for Component RFID Card Scan 3.3.1 Processing narrative for component RFID Card Scan The RFID card scan is the first thing an individual does upon arrival at the parking garage. The individual will scan their card at the RFID reader and then enter their digit password (described in section 3.2). After the user is done at the garage, they will arrive at another RFID reader which they will scan their card again which will mark their departure from the garage. 3.3.2 Component RFID Card Scan interface description. The RFID card scan interface is simply the RFID readers found at the entrance and exit gates of the garage. 3.3.3 Component Keypad Digit Entry processing detail 3.3.3.1 Interface description The interface for this device is the RFID card reader. 3.4.3 Component Admin/User Login/Logoff processing detail 3.4.3.1 Interface description The interface will contain two fields, one for the username and one for the password. Once they are logged onto the system they will have a link on the left side of the screen from which to logout. 3.4.3.2 Algorithmic model (e.g., PDL) Enter Username and Password Grant Access to website Throw error message and prompt to reenter information 3.4.3.3 Restrictions/limitations  Users are allowed five attempts to login before they are locked out of the system and must contact an administrator.  Username will be the e-mail address they used to register.  Password must be between 8-30 characters. 3.4.3.4 Local data structures No data structure is needed for this device. 3.4.3.5 Performance issues  The database should provide the user with access/denial to the garage website in a reasonable amount of time, no more then 5-10 seconds.  Logging onto the system may be slow if many users are trying to gain access to the website. 3.4.3.6 Design constraints  8-30 character password  Individuals are allowed five attempts before they must contact the garage administrator for troubleshooting. 3.5 Description for Component Modify Account Information 3.5.1 Processing narrative for component Modify Account Information Users of the system are allowed to modify account information. This includes their e-mail address, password, home address, phone number, and name. This is to ensure that users of the system can change information if the need arises. If users wish to update this information, a link on the left side of the screen is provided labeled as “Update Account Information”. If users wish to update their password or e-mail address, then they must enter the information twice to ensure the e-mail address and password are identical. Administrators will also be allowed to update this information but only if the user calls and requests the information change. 3.5.2 Component Modify Account Information interface description. The interface to update the account information will be a series of boxes that will ask the user to input the required information. A series of checks is performed once the user clicks the “Update” button to ensure the information is in the right format, e.g. the password must be 8-30 characters, if the user does provides too few or too many characters an error message will display. 3.5.3 Component Modify Account Information processing detail 3.5.3.1 Interface description The interface will contain various boxes for the user to enter their information. As stated in 3.5.1, if a user wishes to change their e-mail address or password then they must verify them by entering the information twice. 3.5.3.2 Algorithmic model (e.g., PDL) Update Account Information Account Updated Error: Account Not Updated. (Erroneous information) 3.5.3.3 Restrictions/limitations  Users must provide correct information to update their account.  Faulty data is flagged by the administrator and they attempt to contact the individual to correct  Must provide a valid dollar amount. 3.6.3.4 Local data structures No data structure is needed for this device. 3.6.3.5 Performance issues  Adding funds to the users account may be slow if many users are trying to gain access to the website. 3.6.3.6 Design constraints  Must enter an amount as xxx.xx format. 3.7 Software Interface Description. 3.7.1 External machine interfaces At this time, this system will not need to interface to other machines. 3.7.2 External system interfaces Users and Administrators of the system may connect to the website via an Internet connection at any time. The RFID scanner will connect to the database via USB cables and process the information through the database interface. 3.7.3 Human interface The human interface is described in further detail in section 4.0. Overall the design of the interface that users and administrators will see will be a very simple and easy to use interface. It will allow users and administrators of the system a way to view account information or garage information. 4.0 User interface design 4.1 Description of the user interface 4.1.1 Screen images  Login – user will provide a username and password to gain access to the website. This page will also provide a means to new users to register.  User Home Page o View Account – provides their account information. o Financial Page – provides payment options, current balance, and payment history. o Modify Account – provides a means for the user to modify account information.  Admin Home Page o View Users – list all the users currently registered for the garage and allow them to view account information. o Modify User Information – provides the admin with a means to modify the user’s account with some restrictions. o Garage Statistics – provides the administrator with general statistics of the garage usage. o Garage Options – provides the administrator with a means to modify attributes with the garage i.e. name, price, open or closed, and parking times. At this time screenshots of these pages are unavailable but are currently in development and will be available for viewing later. 4.1.2 Objects and actions  Login o The login screen will provide users a box where they will input their user name and password. The information they enter is validated through the database.  User Home Page o This page will provide general information for the user and provide links to view financial information and to modify their account. The user will also have the ability to log out from this screen.  Financial Page (User Page) o User will be able to view their current balance and specify a payment method.  Modify Account (User Page) o User will be able to modify attributes with their account including address, e-mail address, password, phone number, and name.  Admin Home Page  The system should maintain functionality when used repetitively by elementary school aged children.  The system should not interfere with the operation of the personal computer to which it is attached.  The system must comply with Part 15, entitled "Radio Frequency Devices" of Title 47 of the Code of Federal Regulations.  The system keypad should be ergonomic in design so that the occurrence of repetitive stress injuries is minimized.  The system must not expose the user to electrical shock.  The system must not store the users’ credit card information.  Pin number must be 5 digits  System must be easily maintained and updated by parking garage employees.  The system must require minimal modification/updates once implementation is complete. 6.0 Testing Issues 6.1 Classes of tests  Sub-systems Testing o RFID Reader Test – an RFID card is placed near the RFID reader. The card is read and the data is sent to the server. o Add/Remove User - A user is created or removed on the admin webpage. o Gate Test – A signal is sent to the gate control circuit which activates the opening of the gate. The gate remains open until the user has entered the parking garage and begins the closing cycle. o User/Administrator Login – A user or administrator attempts to login to the website using their username and password. o Keypad Test – A pin number is entered into the keypad and transmitted to the server.  System Testing o General Test – User attempts to access the parking garage via an RFID card and keypad. This is a general test of the overall system response. The main purpose of the test is to determine the status of the RFID reader, the keypad, the database status, and the gate functionality. o Administrator Test – An Administrator attempts to login to the system and perform administrative actions. These actions include: add/remove users, modify user accounts, query the database, check the status of the system, and set parameters and constraints on the parking system. o Web Interface Test - A user attempts to login the web interface and modify their account. These modifications include: Changing email address, modifying address, modifying name, requesting an account, and changing payment options. 6.2 Expected software response  Sub-system Testing o RFID Reader Test – The RFID card’s unique ID is transmitted to the server. o Add/Remove User – User roster is updated accordingly in the database. If a user is added, all fields will be filled in and their status is set to “active”. If a user is removed, their status is set to “inactive” and their account information remains in the database. o Gate Test – When the “open” signal is received, the gate begins the opening cycle. Once the user has entered the garage or a present amount of time has passed, the gate will begin it closing cycle. o User/Administrator Login – The user will be validated by the system by their username and password. o Keypad Test – The user’s pin number is transmitted to the server  System Testing