Software engineering rfid system
Download as PPTX, PDF3 likes2,952 views
This document outlines an RFID system project for a university car parking area. It includes sections on the group members, introduction to RFID technology and how it will work in the parking area, features of the system like user registration and record keeping, operating environment and hardware/software requirements, design constraints around power supply and budget, assumptions that include backup power and a shelter for equipment, non-functional requirements such as performance, safety, security and quality attributes, and use cases and sequence diagrams for how the system will function.
Software engineering rfid system
- 1. RFID SYSTEM
- 2. GROUP MEMBERS Fazeel Ashraf Ali Haider
- 3. CONTENTS Introduction to RFID Product features Operating Environment Design And Implementation constraints assumptions and dependencies Non-functional requirements Use cases Sequence diagram
- 4. INTRODUCTION Radio frequency identification SEECS car parking area RFID tags
- 5. INTRODUCTION… Working Scanning Antenna Transponder – RFID tag Power?
- 6. FEATURES Register a new user Remove user / update a user information Less use of man power keep records of the incoming and outgoing traffic Also used for the security purpose
- 7. OPERATING ENVIRONMENT As the integrated system Hardware shelter Software Clean environment to protect data
- 8. DESIGN AND IMPLEMENTATION CONSTRAINT Power supply Budget problem Back up of the user data in case of system crashs
- 9. ASSUMPTIONS & DEPENDENCIES Need a power supply back up Need a shelter for the Reading device / scanning antenna For the motor Bar should remain open while the car is passing
- 10. NON-FUNCTIONAL REQUIREMENTS Performance requirements Perform under any condition Database should be online 42 x 7 Safety requirements Bar should remain open while the car is passing Data back up in case of system crash
- 11. NON-FUNCTIONAL . . . . Security requirements No unregistered person should have access System should not be easily breakable Quality attributes Is actually hardware dependent More expensive is the hardware, more are the features supported by it
- 12. USE CASES
- 13. USE CASE…
- 14. SEQUENCE DIAGRAM