FPSWEN2

profilePONNI
RPGSWEN6452.docx

Software Requirements Specifications

Mahamadou Diallo

University of Maryland Global Campus

SWEN 645

RPG

Contents 1 Introduction 4 1.1 Purpose 4 1.2 Scope 4 1.3 Overview 5 2 Description 7 2.1 Project description 7 2.2 Product functions 7 2.3 The user interfaces 7 2.4 Features of the user 8 2.5 Constraints 8 2.6 Website interface 8 2.6.1 The user interfaces 9 2.6.2 System interface 9 2.6.3 Communication interface 9 2.7 Website memory constraints 9 2.8 Website function 9 2.9 Temperature detection 10 2.10 Creation of group location/asset 10 2.11 Virtual bidding 10 2.12 Camera control system 10 2.13 An auction system 11 2.14 Radio system 11 2.15 New system addition user characteristics 11 2.16 Dependencies and assumptions 12 2.17 Apportioning of system requirements 12 3 Specific system requirements 13 3.1 External interface needs 13 3.2 Website functional requirements 13 3.2.1 Use cases 13 3.3 Performance requirement 26

Introduction

This part of the document will cover the overall scope of the SRS and the overview. Also, the section covers the purpose of the document.

Purpose

The purpose of this SRS document is to detail the website requirements of the customer to add more features to the website such as addition of radio monitoring system, camera installations and monitoring, auctioning and bidding functions as well as temperature monitoring features. The document will show the declaration and the purpose for the modification of the website. it will expound on the constraints that will be encountered, the interface and system interactions and the users of the new functions in the website. This SRS documents is a proposal to the customer for the approval of the website requirements and will act as reference for the modification of the website.

Scope

Most of the modifications such as the camera monitoring, radio monitoring and auction modification will be GPS based for accurate location for monitoring purposes. The applications should be easily accessed freely on the website depending on the authority and level of the user.

The functions provide the customer with the required information using the web-portal. The data will be vital to the expansion of the store and offer security from the unprecedented scenarios such as from riots, protests and combat the spread of Covid-19. The new additional features will also lead to enhanced administration of the store and keep the information and processes in the store easy and accurate.

The new features are dependent on the usage of internet and GPS connection in order to access, fetch and display the information. All the data generated from the new functions is maintained in the database, that is located on the overall website server. The new features will also have an interaction with the GPS navigator which is presumed to be already installed in the website and has an integration capabilities with the mobile GPS navigators and the computer GPS navigator. By using the GPS navigators, the store owner and the website administrator will be able to view the store on the map and monitor the activities around and within the store. The website administrator will have the ability to pull out detailed data from the new functionalities about the store.

The system will cover such functionalities as temper detection, arsonist detection, detection of personal shapes with fevers and how to contain them using infrared, radio to monitor crowds and identify the person calling the shots, radio to monitor the location of law enforcers, an auction system, the camera control system and the virtual bidding section in the website.

Overview

The other parts of this SRS documents is made up of three main sections. The second part provides the functionalities of the new additions to the website and the overall interaction of the new features with the users. This section covers the major stakeholders and the application the new features to the overall operations of the store. Further, the constraints are covered in this section.

References

IEEE Software Engineering Standards Committee, “IEEE Std 830-1998, IEEE Recommended Practice for Software Requirements Specifications”, October 20, 1998

Van Vliet, H. (2008). Software engineering: Principles and practice (3rd ed.). Chichester, UK: John Wiley & Sons.

Description

Project description

Project #4 is a continuing project that do not require the creation of a new website. It is specifically designed to meet the additional customer requirements with the addition of several tabs to the website. The website additions are designed to be secure and can be easily accessed by the authenticated user. Nonetheless, the access of some of the additional features such as camera control, arsonist detection will have a restricted access for only the website administrator.

Product functions

With the new functionalities, the security of the store will be enhanced and the users will be able to view all the sections of the store and get access to the merchandise offered in the store. The camera installation will offer both virtual visits to the store as well as help in monitoring the security in the store. Radio monitoring will help in curbing the security and in the monitoring of crowds. The cameras and the radio will cover all the locations within the store and outside.

The new features will enable the store owner with functionalities in managing the store and in conducting sales virtually. In both bidding and auction processes will be managed through the website.

The user interfaces

The user interface adopted will be easy to manipulate with minimum to no training required. Both the website admin and the guests will be able to interact with the website in any of the languages that is included in the language menu. The website will use the ZUI graphical environment which will assume the existing sense of contrast and color, and all the pages are printable using the functional keys. The additional website features will be made accessible from any of the pages opened.

Features of the user

The new features that will be added in the website will be accessed by four types of users; mobile application users, store owner and the website administrators as well as the customers. Each group of these users have the different use of the functionalities as per their individual requirements.

The mobile application and customer users will utilize the functionalities in finding the store. this gives the user the ability tox search for the store, choose it from the search engine them navigate through it using the virtual visits enabled by the installed cameras. In order to access the section, the user is interested in, he or she needs to clarify the section and the type of books they need.

The store owner will access the new functionalities using the web portal. He will be able to manage the data about the store.

Website administrators will also access the new functionalities through the web portal. They are the overall managers of the website to ensure that there are no discrepancies within it. The administrators manage all the information about the bookstore and manage the interaction of both the customers and the mobile application users.

Constraints

The UUIS system used in the website is implemented in JAVA. In order to add new additions to the site, JVM system is required. In addition, the website will require phpMyAdmin and Tomcat. The website will be maintained to support up to 1000 users at the same time.

Website interface

From the previous website specifications are available in a CSV format. The installation of new features to Project #4 will need an API in order to obtain data from the files.

The user interfaces

The user interface adopted will be easy to manipulate with minimum to no training required. Both the website admin and the guests will be able to interact with the website in any of the languages that is included in the language menu. The website will use the ZUI graphical environment which will assume the existing sense of contrast and color, and all the pages are printable using the functional keys. The additional website features will be made accessible from any of the pages opened.

System interface

The website was previously developed in a CSV format. UUIS will thus require an API to help in the importation of the data and the needed files.

Communication interface

The website contains an UI that is easily manageable and can be manipulated easily. The new customer requirements will be added in a format that could be accessed from any of the available ports. It will form the basis of communication between the new features and the user. The new features will be able through all the browsers where HTML papers interact.

Website memory constraints

The additional website features require 512 MB minimum memory on the primary disc and 3.5 GB on the secondary memory for efficient installation and execution.

Website function

The website will perform the following functions. The functions will however depend on the user’s level and the permission level as put by the features of the user.

Temperature detection

The new installation will help in system monitoring of the temperatures and help in the detection of arsonist in the current unprecedented time where most of the business have been looted and torched down during protests. The temperature detection will also help in the monitoring of the customer personal shapes to identify those with fevers which is vital in containing the Covid-19 virus. The feature will be available on the system menu functions on the administrator’s side.

Add, edit, view, delete records

This function will allow the website administrator with the ability and permission to add, edit, view, delete records in the most appropriate categories on Project #4. The four main databases that will affect the new additions include the ‘location’, ‘assets’, ‘persons’, and ‘licenses. The website administrator has also the authority to make bulk entry. The deleted information will mean the change of status.

Creation of group location/asset

The function will allow the grouping of all the inventory into various subgroups and combining the list of assets present in the store and help in monitoring the rare comic items in the store.

Virtual bidding

The functions will allow customers to place bids on various items through the website and the method of payment is reconfigured in the site.

Camera control system

This function will allow the administrator to have appropriate ability to control the cameras that will be installed in the store and monitor all the activities in the store. Th control will follow the user maps that will be preinstalled to control the movement of the cameras on the areas that needs covering. In case of the overlapping maps, the system will create the problem file which will allow the administrator to check it manually.

An auction system

The function will allow for the auction of various merchandise in the store and will be done live and streamed from the website. It allows the users to create merchandise subgroups and group them according to their price, rarity and according to the types. The auction function will have various packages within the system.

Radio system

This tab will have two subsections; monitoring the location of law enforcers and monitoring the groups to identify the ring leader and the person calling the shots. This is a security feature that will connected to both the computer system and the phone system for easy monitoring and ready access.

New system addition user characteristics

The users of these new features will be assigned various levels. the levels are as follows;

The website administrator level, the customer and the new user.

System usage leveling is mostly used for these features as an area of visibility so as to show data for the store, various store segments and on individual merchandise. For example, the system administrator is able to manage all the store assets while the employees take care of merchandise in the store.

Moreover, the system usage leveling is used for approval or rejection of requests. Once one system user of some level submits his or her request, it is seen, approved or rejected by the main administrator. An exception of this is the requests submitted by the level three system user which does not need approval from anyone. These requests are approved automatically and directly after submission.

Same roles from the different user levels have different approval permissions. From the general point of view, the following are some of the groups in which the users are grouped into:

i. Store owner

ii. Store employees

iii. Users

Dependencies and assumptions

The personal data information- title, ID, username, communication information, user’s level in the website and the user role is previously determined for all the users utilizing the newly added features. The access to the new features have some restrictions in relation to the information required and the level of the user in the system will determine the level of restrictions imposed. The system administrator- store owner, verifies and can access the users’ account in the system. the action that will be conducted on the new features need to be recorded and saved on a separate database for auditing and future reference purposes.

Apportioning of system requirements

The features will be available in all the existing site languages. While the whole websites might wait for future upgrades and versions, the new features will be available for all future upgrades and versions. The SDD of the website can be referred for a detailed list of the new functions.

Specific system requirements

External interface needs

The new features will take input from the external equipment such as the cameras, keyboards, scanners and the files stored in the memory. Various segments of the newly added features will develop printable output both on the screen and peripherals. They will utilize JDBC and MySQL system connectors to aid in communication with the database.

Website functional requirements

Use cases

This will describe the required exemptions and procedures foreach of the function added. The required permissions of each of the website user are listed in the table described in section 2.

Addition of new merchandise for bidding and auctioning

Website actors: users with the required permissions

Pre-requirements:

i. No such merchandise or addition to the existing subgroup

ii. Authentication of the session

iii. Submission and approval of appropriate request

Trigger: click bidding/auction menu, ‘add new.’

Procedure:

a. User on the main page ‘click either bidding or auction menu’ merchandise and system transfers it to page ‘merchandise – add new’

b. The system will open the store ‘merchandise’

c. User selects the merchandise to be added from the available list displayed and the system indicates the appropriate features of each merchandise

d. The system creates the date added

e. The user provides the following information concerning the merchandise; name, subgroup, serial number, purchase number, barcode, color, rarity, request number, publisher and author of the book.

f. The user assigns the location on the shelf

g. The user terminates the process

· User clicks create to save the changes made to the ‘bidding or auction page.’

· System checks the uniqueness of the barcode

· The system updates the actions on the relevant tabs

· The changes can be aborted by clicking cancel

Post conditions: the new merchandise is added to the subsequent shelf

Exceptions:

a. Error from the database

b. Error message from the system

c. Empty required field

d. Error message with a request for the user to repeat the process again

e. Barcode not unique

f. Error message with user requested to change the barcode

Camera operation and store view

Actors: users with the require permissions

Preconditions:

1. Authenticated session

2. Cameras are running in the store

Trigger: click menu’ monitoring- camera (choose camera number) – choose location to view

Procedure:

1. Administrator user on the main page

· Administrator user on the ‘main page’ click on ‘menu’ click on ‘monitor’ transfer to ‘camera’ click on ‘store section’ click on ‘camera number’

· Administrator user on the page ‘main’ click on menu ‘licenses’ transfer to store location

· User on the page ‘main’ click on ‘location’ view area

2. System display

· The system displays DB ‘camera’ in the list. The display depends on the section the user is in and the role of the user

· System displays DB ‘location’. display depends on the role of the user

· System displays ‘camera’. Depends on the role of the user

· The user clicks on the display/virtual tab to see the camera details and to access the required section of the store

· The system updates the action on the records for audits

Post conditions:

1. Records on the appropriate camera is reviewed

Exceptions:

1. Error message displayed by the system

2. Database error

Radio system for monitoring

Actors: the users with the required permissions

Preconditions:

h. Required activity present in the UUIS

i. Authenticated session

j. Submitted and approved appropriate request

Trigger: click link ‘monitor’- click ‘radio monitors’ (choose between crowd radio monitor or law enforcement radio locator)

Procedure

i. User on the ‘main’ page

· Click on the menu ‘monitors’ and system transfers to ‘monitors’

· Click on the radio monitor dropdown and system takes to ‘radio monitor’ display depends on the level and role of the user

ii. System display

· System displays the two types of radio installed in the store- crowd monitoring radio and law enforcement locator radio

· System displays the type of radio identified and sends records to the memory for auditing and future use

iii. User clicks view to view ‘crowds’ or identify the exact location of the law enforcers

iv. System opens a sub window that shows activity of the party observed

v. User makes decision on the same

Post conditions:

The records are modified and stored

Exceptions:

i. Error from the database

ii. Error message displayed by the system

iii. No crowd or law enforcement activity in the area

iv. Error system display by the system and user requested to repeat again

v. Radio monitor not selected

vi. The system identifies an error in the selection of the radio monitor and requests the user to change the selection

Editing data in the system

Actors: website user with appropriate permissions

Preconditions:

i. Appropriated request submitted to the system

ii. Authenticated session

iii. Appropriate merchandise exists on the list to be selected

Trigger:

Click link ‘merchandise’ click the ‘edit’ button- select item location, click ‘edit’ click ‘add’ to add to the list of items on auction or for bidding

Procedure:

1. User in the main page:

· On the main page, click on the tab merchandise and the system transfers to the list of the available merchandise on the shelfs

· On the main page, click on the page persons, systems redirects to the page persons

· On the main page click location, the system redirects to the page location

2. System display

· The merchandise available in the store is displayed in a table. The user is able to show the hidden columns and also be able to change the number of lines in any given page. However, the display is dependent on the level and the role of the user as well as the authority.

· The system displays the location in a tabular form. The user is able to show or hide columns, as well as change the number of lines per page within the display.

· System displays person in a tabular form. The user is able to show and hide columns, and as well as be able to change the number of liner per page. The display largely depends on the level, role and the authority of the user.

3. The user, system administrator, clicks edit next to the place that require addition of the item

4. The system leads to a new window which shows the lists of merchandise already in line

5. User initiates the edits

6. The user clicks on the submission button to save the changes made and back to discard the changes initiated

· The system checks on all the required data from the book such as the price, the author, the type, the barcode, the Dui number and the author

· The list of the items available is updated

Post conditions:

Records in the store database are modified and updated.

Exceptions:

i. System error message and user asked to rectify

ii. Database error

iii. Information not matching any of the items

iv. Error message and barcode change required

v. Empty compulsory empty

Deleting records from the bidding and auction section

Actors: users with the required permission

Preconditions:

i. Session authentication

ii. Existence of nonempty DB in the UUIS

Trigger:

Click on the menu asset then delete/ location- delete/ license- delete/ person- delete

Procedure:

i. On the main page, the user:

· On the main page, the user clicks on the page assets- delete and the system will transfer the user to the new page ‘asset- delete’

· User on the main page clicks on the menu location- delete and the system transfers the user to the location- delete window

· On the main page, the user clicks on the license- delete tab and the system opens the license- delete tab

· On the main page, the user clicks on the tab person- delete and the system displays the person- delete window.

2. System display

· The system will display the merchandise in a tabular form. The user has the permission to show or hide columns and change the number of the lines in any given page. The information displayed in this page is based on the level and the authority of the user

· The display on the information on the location is on a tabular form. The user is able to change the number of lines per page. Information displayed is dependent on the level and the authority of the user

· The information displayed regarding license is done in a tabular form. The users has the ability to show or hide the number of the line’s user page. The information displayed is dependent on the level and the authority of the user

3. The users are able to scroll through the list of the merchandise to see the different records in a tabular form

4. The user identifies and selects the items that are to be deleted by checking on the appropriate boxes on the right-hand side of the list

5. The user then clicks on the ‘delete selected items’

6. The system shows, ‘are you sure you want to delete the selected items?’ click ‘ok’ to confirm.

7. System automatically updates the database and audit the files

Post conditions

1. Records in the database are deleted

Exceptions:

i. Error message displayed by the system

ii. Database error

iii. No selection made by the user

iv. Error message but user required to do the selection afresh

Creation of group of merchandise for auction

Actors: users with the required permission

Preconditions:

1. Session authentication

2. There is need for such subgroup of merchandise in the auction process

Trigger:

Click on the asset ‘menu- create a group’ or click on ‘location – create group’

Procedure:

i. On the main page, click on the tab ‘assets- create a group’ or ‘location- create a group and the system will transfer the user to the ‘asset-create a group’ or ‘location- create a group’

ii. The system displays ‘asset’ or ‘location’ in a table. The user is able to hide or show columns, be able to change the number of lines in a page. The information that will be displayed depends on the level and the authority of the user.

iii. A scroll bar will help the user to see the existing records in the table

iv. The user will be required to select the ‘asset master’ which translates to the name of the group

v. The user selects the asset master

vi. The user is required to select the next step

· User select on the ‘add master’ button so as to confirm the operation

· In order to cancel the whole operation, the user clicks on ‘cancel button’

vii. The user is prompted by the system to select the ‘add children’ so as to confirm operation. The user can repeat this process as many as possible

viii. User terminates the operations

· the group is created in the store website location is created after the user clicks ‘create group’

1. the process is updated on the audit file

· the process can be aborted by the user by clucking ‘cancel

post conditions:

i. The new group of merchandise is created in the websites DB location

Exceptions:

i. the database error

ii. error message from the system

iii. more than one selection of the asset master

iv. error message requiring the user to select only one asset master

importation of camera graphics and images

Actors: the users with the appropriate permission

Preconditions:

i. Session authentication

ii. Need to integrate the old data and the UUIS

Triggers:

On the main page: click asset- import’ or ‘location- import’ or ‘person- import’

Procedure:

1. On the main page, the user;

· The user clicks on the merchandise- import and the system will automictically transfers to the merchandise- import page

· User clicks on the location- import and the system transfers to the page location

· From the main page, the user clicks on the ‘person- import’ and the system redirects to the page

2. The user to select the type of import:

· From the file location

· User opens the camera file storage section

· The copy of the videos or images is made

3. From the available list, the required media is selected

4. From the drop-down menu, the section where the items are to be imported to is selected

5. The user terminates the operation:

· The user clicks to ‘insert data’ to add the selected files to be imported

· The system will insert the imported assets into the identified database

· The system generates the importation date

· The audit file updates is automatically updated

· ‘cancel’ button negates the process

6. The user fills the empty fields manually and he inserts in the appropriate databases

Post conditions:

i. The file is imported to the UUIS

Exceptions:

1. The data imported is converted to the incorrect format

2. System error displays to indicate need to save in the right format

3. The user did not select the selection to import the data to

4. Database error

5. Error message from the system

6. System error requiring user to select location

Auction and bids approval

Actors: users with the appropriate permission

Preconditions:

1. Session authentication

2. There is a request in the system which needs to be approved or rejected

Trigger:

The user clicks on the given request

Procedure:

1. In the main page, click on ‘request- approve reject’ and the system displays information on the ‘request- approve/reject’ page

2. The user views all the auction and bidding requests that needs approval

3. The requests are selected from the given list

4. The user is able to view the request and analyze the details that come with it

5. The reaction button is chosen based on the decision of the user:

· Click ‘approve’ if the bid is accepted. The changes are automatically updated on the system.

· Click ‘reject’ if the request is rejected.

6. The website will update and save the changes on the audit file

7. The next level request is mapped by the system

8. An email is sent to the customer to notify on the status of their bid

Post conditions:

i. The bid is approved or rejected

Exceptions:

i. The user did not provide the reason for the rejection of the bid

ii. The system shows an error message and requires the user to provide the reason for the rejection.

View of all the system requests

Actors: user with an appropriate permission

Preconditions:

Session authentication

Trigger:

Click on ‘requests- view all requests.

Procedure:

i. On the main page, the user clicks on ‘requests- view list of all the requests and the website will display the page.

ii. All the requests are displayed on the screen

iii. The user chooses their request of choice

Post conditions:

1. All the requests are reviewed

Exceptions:

No exceptions

Performance requirement

The new features are required to provide support to the store activities simultaneously. The functions should support the number of site visitors as the existing one.

2