User Interface Subsystem - 1. 1 The Motivation

|
1. 1 The Motivation
|
bet | 31/32 | Sana | 22.07.2021 | Hajmi | 0,89 Mb. | | #15652 |
6.5 User Interface Subsystem
The User Interface of the VoIPv6 application was implemented successfully; however it is relatively simple in cosmetic appearance, but fully functional. There are three windows within the User interface and they are identical to the windows within section 5.1 Diagram X, X and X.
The User Interface subsystem has a number of internal functions which deal with processing user commands and displaying the displayed window. The following is a list of internal functions, that standard windowing and application setup functions such as, InitInstance and InitApplication are not shown since there standard to all Windows CE application which implement a User Interface;
ui_startlisening() calls the setup function of the communications subsystem and also passes the “start listening” message to communications. This function is called when the application is initialised.
ui_stoplistening() sends the “stop listening” message to the communications sub system, which tells the subsystem to close down and stop listening for new connections.
ui_acceptcall() sends the “accept” call signal to the communication subsystem when the user decides to accept an incoming call.
ui_rejectcall() sends the “reject” call signal to the communication subsystem when the user decides to reject an incoming call.
ui_hang_up() sends the “hang up” signal to the communication subsystem when the user decides to terminate either an incoming or outgoing call.
ui_makecall() sends the “makecall” signal to the communications subsystem to initiate a call.
There are also external functions which are called by the communications subsystem these are;
ui_noanswer() notifies the user interface that there was either no answer or a reject signal to an outgoing call, this would display a message to the user and then close the in-call window returning to the dialler window..
ui_ringing() notifies the user interface that there is an incoming caller trying to initiate a call, this would open the incoming caller window until the user either presses accept or reject, or the other machine cancels the call.
ui_callcancelled() notifies the user interface that the incoming caller cancelled the call before the call was initiated, this would close the incoming caller window and then display the dialler window.
ui_setincallstatus(char *message) sets the in-call status label to the messages parameter allowing the communications subsystem to keep the user informed.
ui_getip() allow the communications subsystem to retrieve the IP address entered into the system by the user.
7 Testing
The following section addresses the testing of the system mainly in terms of acceptance testing. It describes the out come of the tests performed by a number of subjects to look at how they feel the system performs and how easy to use and informative the user interface is.
What will be in my testing plan????
8 Evaluation
After some shallow testing the VoIP system seem to work. But how well does the system work? Does it work well enough for user of the university/corporate user to adopt to use within there institutions?? This section tries to address some of these questions, first by comparing the system to its original aims, and using the test data from the subject who tested the system tries to look at whether the system addresses the non functional aims. Then finally summary section which in summaries what the system does and what it fails to do.
|
| |