In this application, consumers who are authorized will be able to view OE results, filter by fields and optionally explore/analyze the result.
Administrator is a special actor in web application who will manage all the users as initiators, observers and consumers.
3.2Mobile Android application
In mobile Android application, observer is able to make an observation as prescribed by initiator, such as answering questions (posed by the Initiator), making notes, taking pictures, providing audio commentary. Observation data with a unique user ID will be time and location stamped. And the data will be transmitted to web server by instant transfer with cellular connection, delayed transfer when Wi-Fi is available, or transfer to desktop computer with cable connection.
3.3Mobile web application
With mobile web application, observer can make an observation without Android mobile. The application is adapted with Opera Mini. Any mobile devices connecting with network is able to make observation and send data. The functionality of mobile web application is the replacement of mobile Android application to enable end users with non-Android platform with this application.
In the end-to-end scenario, initiator enters a study question as an OE in web application and makes it available to mobile observers. Then observers make an observation on mobile application by answering questions, making notes, taking pictures or recording audio. After that, the observation data will be sent to web application. And web application will collect the result and make them available for consumers to analysis and view.
3.5Non-functional Scenario
For privacy/security and authentication, system will generate a key for the observer selected, and the key will be used to relay back the information when OE demands a signature. Only observation data with the key matched will be valid.
For accessibility, Android platform is used for mobile application device to ensure that data can be encrypted to make the transmission secure.
For affordability, mobile application will provide means to capture observations even if it hasn’t got access to the Internet.
Identity
|
Sta
tus
|
Prio
rity
|
Description
|
Source
|
|
|
|
System Administration
|
|
ADM-1
|
I
|
1
|
Ability to create a user.
|
SYS
|
|
Administrator is able to create the user and assign a role to him. The role can be of initiator or observer or consumer or a combination of the above roles.
|
|
ADM-2
|
I
|
2
|
Ability to edit a user.
|
SYS
|
|
Administrator is able to edit properties of a user including his role.
|
|
ADM-3
|
I
|
2
|
Ability to view a user.
|
SYS
|
|
Administrator is able to view the properties of a user.
|
|
ADM-4
|
I
|
1
|
Ability to delete a user.
|
SYS
|
|
Administrator is able to delete a user.
Case 1: Initiator can be deleted only after the OE created by him is deleted.
Case 2: Observer is deleted.
Case 3: Consumer is deleted.
Case 4: Guest User (Inactive User) is deleted.
|
|
|
|
|
Initiator
|
|
INI-1
|
I
|
1
|
Ability to create an observation event.
|
CTM
|
|
The initiator will be able to create observation events based on certain predetermined parameters. The observation event will be identified by its own unique id, type, etc.
|
|
INI-2
|
I
|
1
|
Ability to start an observation event.
|
CTM
|
|
The initiator will be able to start a created OE by him. To start an OE, it should have at least one observer tagged to it and medium of observation identified.
|
|
INI-3
|
I
|
1
|
Ability to terminate an observation event.
|
CTM
|
|
The initiator will be able to terminate an OE created by him. When the OE is terminated by the initiator, the observers tagged to the particular OE are notified. When the observer logs in, the OE list is refreshed.
|
|
INI-4
|
I
|
2
|
Ability to edit an observation event.
|
CTM/SYS
|
|
The initiator will be able to edit the observation event. The editable parameters are limited. Once the OE is edited, the tagged observers will be notified about the changes if the changes are related to the recording of the OE event such as change in deadline.
|
|
INI-5
|
I
|
1
|
Ability to view an observation event.
|
CTM/SYS
|
|
The initiator will be able to view his created OEs. He can view his OE at any time after creation. The view should be able to show him tagged observers, their observations till now which have been relayed back and any data if it has been presented to the consumer.
|
|
INI-6
|
I
|
2
|
Ability to delete an observation event.
|
CTM/SYS
|
|
The initiator has an ability to delete an OE. Before deleting an OE, the OE needs to be terminated.
|
|
INI-7
|
I
|
1
|
Ability to select observers for an observation event.
|
CTM
|
|
The initiator will have the option of selecting observers for a particular OE. The observers can be selected anytime before or after starting the OE. The notification of OE is sent only after start of the OE.
|
|
INI-8
|
I
|
1
|
Ability to select the medium for the observation data.
|
CTM
|
|
The initiator has the option to select the medium for an OE. The medium can be text, picture, video or audio or a combination of the above.
|
|
|
|
|
Observer
|
|
OBS-1
|
I
|
1
|
Ability to view observation events assigned.
|
SYS
|
|
Once an OE is started, the tagged observer gets a notification of it. He has the option to view all the OEs assigned to him.
|
|
OBS-2
|
I
|
1
|
Ability to accept/reject observation event.
|
CTM
|
|
If the observer accepts the OE, it is added to its OE list. If the observer rejects the OE, it is not added to its OE list.
|
|
OBS-3
|
I
|
1
|
Ability to make observations using Mobile Application Device.
|
CTM
|
|
The observer has the option to make/record observations using his Mobile Application device for a particular OE. The OE data can be stored in memory in case the observation is distributed in time.
|
|
OBS-4
|
I
|
1
|
Ability to send an observation data using Mobile Application Device to a web-server.
|
CTM
|
|
The observer has the option to send a final saved data for a particular OE to a web-server. The data can be sent before deadline of that particular OE.
|
|
OBS-5
|
I
|
2
|
Ability to access the information via Mobile Application Device even though there is no internet access.
|
DEV
|
|
The observer has the option to access his OE information without internet access.
|
|
OBS-6
|
D
|
1
|
Ability to view observation events assigned through a web-interface.
|
|
|
|
|
Consumer
|
|
CSM-1
|
I
|
1
|
Ability to view observed data.
|
CTM
|
|
The consumer is able to view information related to a particular OE for which he is selected by the initiator or which is made public to all the consumers.
|
|
CSM-2
|
I
|
1
|
Ability to analyze the observed data.
|
CTM
|
|
The consumer has the option to analyze OE information and represent it in form which is accessible to him.
|
|
|
|
|
Others
|
|
OTH-1
|
I
|
1
|
Ability to register a user on website.
|
SYS
|
|
A new user (called as guest user) has to register in the MOb application before becoming a part of it. He will be presented a form for registration where he will put in his desired role for approval.
|
|
|
|
|
NFR
|
|
NFR-1
|
H
|
2
|
The identity of the observer if desired should be kept secret.
|
CTM
|
|
|
|
If the observer while sending back the OE information wants to hide his identity, he should be able to do it.
|
|
NFR-2
|
I
|
2
|
Observer authentication should be possible if desired.
|
CTM
|
|
|
|
|
|
NFR-3
|
I
|
2
|
Encryption techniques should be used for security for mobile applications
|
CTM
|
|
|
|
|
|
NFR-4
|
I
|
2
|
Web-Application must be compatible with latest web browsers.
|
DEV
|
|
|
|
The Web-Application should be supported across IE, Firefox, Safari, Chrome and all other standard browsers.
|
|
NFR-5
|
I
|
2
|
The web interface should be user-friendly.
|
DEV
|
NFR-6
|
I
|
1
|
The system response should be quick.
|
DEV
|
NFR-7
|
I
|
1
|
The system should be stable.
|
DEV
|
