System Architecture
The main controller is the main engine of the entire
application. It receives input from the user interface and calls upon the
appropriate manager to handle the specific user input. It also sends the output
back to the user interface after a certain operation.
This is one of four managers responsible for handling
user tasks. It is responsible for handling requests about the calls like hiding
or encrypting call logs. This component works with the call logs application of
the android operating system.
The contacts manager is similar to the calls manager.
It also receives commands from the main controller and works with the contacts
application of the android operating system.
The messages manager also receives commands from the
main controller and works with the message logs of the android operating system
to complete the tasks.
The files manager also receives commands from the main
controller and works with the media gallery of the android operating system to
complete the tasks.
I.
Call
logs
This is the call log application of the android
operating system. It is responsible for logging incoming, missed and outgoing
calls with their durations and their respective numbers.
II.
Message
logs
This is the messages log application of the android
operating system. It is responsible for showing the incoming and outgoing
messages.
III.
Contacts
This is the contacts application responsible for
displaying all the contacts stored on the mobile phone or the simcard.
IV.
Media
Gallery
This is the media application of the android operating
system. It is responsible for all the media stored on the mobile phone like
music, videos and music.
Description of how components work
together
The user interface receives user input and
directs it to the main controller. The main controller is the main engine of
the application controlling all the other components of the application. On
receiving user input the main controller invokes the appropriate event handler,
hence calling one of the four managers according to user input. Incase the user
had chosen a task about calls, the main controller directs that command to the
calls manager. The calls manager then works with the call logs component and the
SQLite database of the android operating system to complete the task. The same
procedure is followed with files, contact and messages tasks.Sequence diagrams
Encryption and decryption sequence diagram on a call log
When
a user wants to encrypt a call, an encrypt call method is sent to the calls
manager. The calls manager then calls an encrypt method of its own to encrypt
the calls’ number and name. The same procedure is repeated for the calls,
messages and contacts tasks’.
Sequence
diagram for hiding and revealing a call log
When
a user wants to delete a call, a delete call method is sent to the calls
manager. The call manager looks up the call logs of android operating system
that correspond to the selected call. That specific call is then deleted and
stored in the applications’ database.
No comments:
Post a Comment