srm template

Name:

University:

Course:

Tutor:

Date:

Software Requirements Specifications

1. Introduction

1.1. Use of RFID technology to monitor the movements of pets in the house.

1.2. The software must locate the position of the pets at any instance.

1.3. The software either grant or deprive entry to a pet at the door.

1.4. Tracking the number of times a pet goes past the door.

2.0 Function requirements

2.1 The user requires a door fitted with a RFID reader.

2.2 The user requires pet tags fitted on the pets

2.3. User requires the system to deny access to pets that are not wearing tags.

2.4 users should be notified if the door doesn’t open in the right manner.

2.5 user require to determine the location of the pet is access at the door is granted

2.6 marketers need a user interface

2.6 marketers need access to change frequency settings and mode of notifications.

3.0 database requirements

3.1 should enable programming interface to execute pet’s information.

3.2 should store the names and information of the pet.

3.3 identify the pet by name and location

3.4 identify the condition of the door.

3.5 send notification to the user via emails and short sms.

3.6 store pet movement details.

3.7 databases must accept changes in settings.

4.0 Operation requirements

4.1.1 Doors detects the RFID signal on the pet’s

4.1.2 Must query the database.

4.1.3 Receive feedback from the database

4.1.4 Identify the name of the pet

4.1.5 Must query the database for permission for the pet.

4.1.6 Grants or deny permission to the pet.

4.1.6 Send a notification to the owner.

4.1.7 Must identify the condition of the door.

4.1.8 Must send notification to the user about the condition identified.

4.2. Must allow the marketer to change the frequency.

5.0 Interface requirements.

5.1. user interface requirements.

5.1.1the interface must allow display of the pets names

5.1.2. The interface must display the permissions status of the pet.

5.1.3 The interface must enable the marketer to change the frequency of the system.

5.1.4. The user interface must display the message sent to the owner.

5.1.5 The user interface must display the condition of the door.

5.2. Network interface requirements.

5.2.1 The user interface must integrate to the available internet connection

5.2.2. The user interface must connect to available GSM network

5.2.3 The user interface must offer option for selecting the network to connect to.

5.2.4. The user interface must link with an online database.

5.2.5. The user interface must connect to owner’s online account for reviews.

6.0 .User requirements.

6.1 The user must identify the pet by names.

6.2 The user must decide the permission status of the pet.

6.3. The user must set the condition of the door properly.

6.4 The user must send the feedback to the system marketers after a given period.

7.0. Non functional requirements.

7.1. The RFID tags must be embeddable on the pet attire.

7.2. the door RFID reader must be small

7.3. the RFID must have power back up mechanism.

7.4. the RFID system must be compact and light.

7.5 the system must always operate silently.

7.6. must match the user language.

7.7 the system must store errors encountered during operation.

7.8. the system must offer alternative means of sending report

7.9 the system must offer user settings alteration directly.

8.0. Assumption.

8.1 The system support is available

8.2. The backup team has the required tools to fix any bugs

8.3. The stakeholders shall cooperate as instructed by the support team.

9.0. Constraints

9.1. The developer must have a coding platform.

9.2. The developer must have the required knowledge in all areas

9.3 The developer must have reliable networking tools.

figure 1.0 shows the case flow diagram of the system.

RFID Reader

(Door)

90d

RFID tag

(pet)

9Pet)

Check door condition

Display/LED

Identify the name of pet

Approve entry

Decline entry

Store to database

Send notification

Database