|
Rajarata University of Sri Lanka
Faculty
of Applied Sciences - Department of Computing
Project– ICT 3411 &
COM 3405
Application
for EC04
|
|
Team Name:
|
Kid Glove
|
|
Project title:
|
Smart kid-glove for
a software framework with virtual reality concepts
|
Section 02
Functional Requirements to be deployed:
|
Number
|
01
|
|
Name of the
Function
|
Setting the Bluetooth
Connection
|
|
Objective of the
Function
|
Wireless
connection setup between hand glove and desktop framework
|
|
Input
|
Bluetooth
information of the Bluetooth module
|
|
Process in Brief
|
Checking for
compatibility with PC Bluetooth settings and memory and processing
requirements
|
|
Output
|
Pairing the hand
glove with PC
|
|
Business rules/
constraints/ Assumptions if available
|
Bluetooth module
will be paired with the user desktop Bluetooth settings.
|
|
Number
|
02
|
|
Name of the
Function
|
Tracking and
reading the user finger movement(hall sensors)
|
|
Objective of the
Function
|
For reading the
coordinates in numerically
|
|
Input
|
Tracking object
|
|
Process in Brief
|
The web cam of
the user desktop will track the tracking object followed by hall effect and
will display its moving as a single dot
|
|
Output
|
Single dotted
visual output
|
|
Business rules/
constraints/ Assumptions if available
|
Processing and
Arduino IDE, web cam will be
|
|
Number
|
03
|
|
Name of the
Function
|
Drawing a sketch
using the glove via a paint application
|
|
Objective of the
Function
|
Check whether
the glove is working properly
|
|
Input
|
Hall sensor
touch with each other via fingers
|
|
Process in Brief
|
When hall
sensors touch each other while fingers are moving a continuous line or a
curve will be drawn.
|
|
Output
|
Drawn visual
output
|
|
Business rules/
constraints/ Assumptions if available
|
Paint
application
|
|
Number
|
04
|
|
Name of the
Function
|
Displaying the
identified coordinates
|
|
Objective of the
Function
|
Checking whether
the glove is getting the coordinates
|
|
Input
|
Hall sensor movement
readings
|
|
Process in Brief
|
Identified
coordinates along the user drawn output will be displayed
|
|
Output
|
Set of
coordinates in command prompt
|
|
Business rules/
constraints/ Assumptions if available
|
Command prompt
will be used to display coordinates
|
|
Number
|
05
|
|
Name of the
Function
|
Storing the
identified coordinates
|
|
Objective of the
Function
|
For temporary
abstraction/library developing of hand glove coordinates
|
|
Input
|
Sensor
calibration and movement along the paint application
|
|
Process in Brief
|
The coordinates
read by the sensor, while moving will be stored via a MySQL query
|
|
Output
|
Data table of
(x,y values) coordinates
|
|
Business rules/
constraints/ Assumptions if available
|
MySQL database
along wamp server will be used to store data
|
|
Number
|
06
|
|
Name of the
Function
|
Straight line
drawing exercise and library development
|
|
Objective of the
Function
|
Practicing and
providing elementary level straight line drawing ability
|
|
Input
|
Finger movements
with sensors(readings)
|
|
Process in Brief
|
Predefined and
connected number of points will be given to match in order to develop a
complete straight line
|
|
Output
|
Straight line
|
|
Business rules/
constraints/ Assumptions if available
|
Straight line
will be vertical, horizontal and diagonal with predefined angles.
|
|
Number
|
07
|
|
Name of the
Function
|
Curve drawing
exercise and library development
|
|
Objective of the
Function
|
Practicing and
providing elementary level curve(circular) drawing ability
|
|
Input
|
Finger movements
with sensors(readings)
|
|
Process in Brief
|
Predefined and
connected number of points will be given to match in circular pathway in
order to develop a quarter of circle
|
|
Output
|
Quarter of
circle
|
|
Business rules/
constraints/ Assumptions if available
|
Quarter portion
of the circle will be facilitated for drawing
|
|
Number
|
08
|
|
Name of the
Function
|
Level Selection
|
|
Objective of the
Function
|
Identifying and
accessing the level
|
|
Input
|
Selection of
level
|
|
Process in Brief
|
User will be checked
and granted with access to the level in sequentially controlled order by the
system itself.
|
|
Output
|
Level access
granted/not granted
|
|
Business rules/
constraints/ Assumptions if available
|
Two levels for
line drawing and curve drawing
|
|
Number
|
09
|
|
Name of the
Function
|
Activity Selection
|
|
Objective of the
Function
|
Identifying and
accessing the activity within a particular level provided.
|
|
Input
|
Selection of
activity
|
|
Process in Brief
|
User will be
granted with access to the activity within a particular level in sequentially
controlled order by the system itself.
|
|
Output
|
Activity access
granted/not granted
|
|
Business rules/
constraints/ Assumptions if available
|
Line drawing
activities
|
|
Number
|
10
|
|
Name of the
Function
|
Evaluation
|
|
Objective of the
Function
|
Evaluating the performance
of a particular activity
|
|
Input
|
Submission of
the completed activity for evaluation.
|
|
Process in Brief
|
User performance
for a particular activity will be evaluated under a system predefined
criteria.
|
|
Output
|
Evaluation
Results as a percentage and a feedback
|
|
Business rules/
constraints/ Assumptions if available
|
|
|
Number
|
11
|
|
Name of the
Function
|
3D platform
development
|
|
Objective of the
Function
|
The system
environment to be emerged within a
three dimensional platform
|
|
Input
|
Visual representation
of the system of user desktop
|
|
Process in Brief
|
Visual screen of
the user desktop will create virtual images of three dimensions using the
hologram like structure
|
|
Output
|
3D system
visualization
|
|
Business rules/
constraints/ Assumptions if available
|
Hologram like
structure will be used along with a multimedia projector
|
|
Number
|
12
|
|
Name of the
Function
|
Database
development
|
|
Objective of the
Function
|
To store and
control user data and privacy constraints
|
|
Input
|
User data
required by the system
|
|
Process in Brief
|
User data will
be stored default for authenticating the user and managing their accounts
|
|
Output
|
User base with
their system authentication details
|
|
Business rules/
constraints/ Assumptions if available
|
|
|
Number
|
13
|
|
Name of the
Function
|
Registration
|
|
Objective of the
Function
|
Authenticating
new user to the system
|
|
Input
|
User
details(Username, password, age)
|
|
Process in Brief
|
Registering a
new user to the system
|
|
Output
|
Completion of
registration and allowing the user with the access to the very first
activity.
|
|
Business rules/
constraints/ Assumptions if available
|
|
|
Number
|
14
|
|
Name of the
Function
|
Login
|
|
Objective of the
Function
|
Identifying
existing user
|
|
Input
|
Username and
password
|
|
Process in Brief
|
Identifying and
allowing the access to the user profile intended
|
|
Output
|
Access to the
profile granted
|
|
Business rules/
constraints/ Assumptions if available
|
|
|
Number
|
15
|
|
Name of the
Function
|
Logout
|
|
Objective of the
Function
|
Terminating the
process temporarily
|
|
Input
|
Button Click
|
|
Process in Brief
|
When user issue
the command for logging out, the system will terminate its processing
happened that moment and will temporarily exit from account while saving the
completed workload.
|
|
Output
|
Termination of
processing and saving completed states of activities
|
|
Business rules/
constraints/ Assumptions if available
|
|
Section 03
Non-functional Requirements to be deployed:
|
Number
|
01
|
|
Non Functional Requirement
|
Usability
|
|
Objective/
Benefit to the project
|
Identify the
minimal requirements and constraints for addressing a function or a portion
of data.
|
|
Measurement
|
User categories
and their preliminary requirements, user perception
|
|
Data to be used
to evaluate
|
User ideas and
views as a percentage
|
|
Number
|
02
|
|
Non Functional
Requirement
|
Availability
|
|
Objective/
Benefit to the project
|
To guarantee the
continuous and even provision of services and resources
|
|
Measurement
|
Database in time
configuration and evaluator in time configuration throughout one complete
activity cycle.
|
|
Data to be used
to evaluate
|
Fault tolerance
value
|
|
Number
|
03
|
|
Non Functional
Requirement
|
Security
|
|
Objective/
Benefit to the project
|
Maximize the
system security
|
|
Measurement
|
Confidentiality,
Integrity, non-repudiation, authenticity, accountability
|
|
Data to be used
to evaluate
|
Database
accessibility specifications, user profile access, device access to the
system
|
|
Number
|
04
|
|
Non Functional
Requirement
|
Capacity
|
|
Objective/
Benefit to the project
|
Define the
maximum no of user profiles the system can facilitate.
|
|
Measurement
|
Maximum no of
users that can be facilitated by the system
|
|
Data to be used
to evaluate
|
Number of user
profiles in the database
|
|
Number
|
05
|
|
Non Functional
Requirement
|
Maintainability
|
|
Objective/
Benefit to the project
|
System features
and functions can be updated and advanced
|
|
Measurement
|
Analyzability,
changeability, testability
|
|
Data to be used
to evaluate
|
Database
entries, user profiles, activity history, and system services state.
|
No comments:
Post a Comment