Internship report: Computerized Corporate Communication System - Conception and Realization

Written by: MBOVING TEGUETIO Levan Fredy Student in level 3 Software Engineering
AICS-Cameroon, Paul Biya Technological Center of Excellence
INTERNSHIP REPORT
ACADEMIC SUPERVISOR:
MRS EBENYE VANESSA
LECTURER AT AICS-CAMEROON
PROFESSIONAL SUPERVISOR:
MR JUSLIN KUTCHE
SYSTEMS AND NETWORKS ENGINEER
ACADEMIC YEAR 2016-2017
CONCEPTION AND REALISATION OF A
COMPUTERIZED CORPORATE COMMUNICATION
SYSTEM: CASE OF NTFoods Ltd.
REPUBLIC OF CAMEROON
Peace – Work - Fatherland
AFRICAN INSTITUTE OF COMPUTER SCIENCES
CAMEROON OFFICE
PAUL BIYA TECHNOLOGICAL CENTER OF
EXCELLENCE
P.O Box: 13718 Yaounde
Tel: (+237) 242 72 99 57; Fax: 242 72 99 58
E-mail : contact@iaicameroun.com
Web Site : www.iaicameroun.com
REPUBLIQUE DU CAMEROUN
Paix – Travail - Patrie
NT Foods SARL
Tel: (+237) 690 79 62 40
Email: info@tanty.cm
Web Site : www.tanty.cm
Internship period: 10th July to 30th September 2017
In view of obtaining an Engineering Diploma in Computer
Sciences (Advanced Level +3)
Option: Software Engineering
Written by:
MBOVING TEGUETIO Levan Fredy

CONCEPTION AND REALISATION OF A COMPUTERIZED
CORPORATE COMMUNICATION SYSTEM: CASE OF NTFOODS SARL
ii
To my family.
DEDICATION

iii
In all success and pride, it is important to remember those who contributed. That is why
we thank all those through which this project is made a reality, among which are:
❖ The Resident Representative of AICS-Cameroun, M. Armand Claude ABANDA,
precious counselling and for being an inspiration for his students;
❖ The Director of NTfoods Ltd, Mr. NYAMEN Thierry for having welcome us and
validated our application in his structure;
❖ To all our teachers in AICS-Cameroun and particularly Mme. EBENYE Vanessa
for the time and energy she sacrificed for the supervision of this project;
❖ To my professional supervisor Mr. KUTCHE Juslin for his quality and available
support;
❖ To the administrative and teaching staff of AICS-Cameroon for the quality training
received at the institute;
❖ To my mother Mme TSOPGO Clarisse for her care and unceasing support during
my studies;
❖ To all the members of my family at Mendong, Biyem-assi and others for their
daily financial, moral and physical support;
❖ To all students of AICS-Cameroon because they are considered as part of this
project;
❖ All the people who were by our sides whether near or far during the realization of
this project and also those who left us because of one reason or the other;
❖ Special thanks you, readers who thought my book worth some of your time;
ACKNOWLEDGEMENTS

iv
SUMMARY
DEDICATION................................................................................................................................ ii
ACKNOWLEDGEMENTS...........................................................................................................iii
LIST OF FIGURES ................................................................................................................... vi
LIST OF TABLES...................................................................................................................viii
ABBREVIATIONS ................................................................................................................... ix
ABSTRACT............................................................................................................................... xi
RESUME ..................................................................................................................................xii
GENERAL INTRODUCTION................................................................................................xiii
PART I: INSERTION PHASE....................................................................................................... 1
INTRODUCTION ...................................................................................................................... 4
I. PRESENTATION OF NTfoods Ltd................................................................................... 4
II. RESOURCES ..................................................................................................................... 6
III. GEOGRAPHICAL LOCATION ..................................................................................... 9
CONCLUSION......................................................................................................................... 10
PART II: PRELIMINARY STUDY............................................................................................. 10
PART III: SPECIFICATION BOOK ........................................................................................... 11
INTRODUCTION .................................................................................................................... 13
I. CONTEXT........................................................................................................................ 14
II. PROBLEM DEFINITION................................................................................................ 16
III. OBJECTIVES ................................................................................................................ 18
IV. TECHNICAL CHOICES ............................................................................................... 19
V. FUNCTIONAL CHOICES............................................................................................... 20
VI. PROJECT PLAN ........................................................................................................... 20
CONCLUSION......................................................................................................................... 25
PART IV: ANALYSIS PHASE.................................................................................................... 26
INTRODUCTION .................................................................................................................... 28
I. DESCRIPTION OF THE EXISTING SYSTEM ............................................................. 29
II. PRESENTATION OF THE ANALYSIS METHOD....................................................... 30
III. CAPTURE OF THE FUNCTIONAL NEEDS .............................................................. 35
IV. CAPTURE OF THE TECHNICAL NEEDS ................................................................. 48

v
V. ANALYSIS....................................................................................................................... 53
CONCLUSION......................................................................................................................... 55
PART V: CONCEPTION PHASE ............................................................................................... 56
INTRODUCTION .................................................................................................................... 58
I. PRESENTATION OF THE CONCEPTION PHASE...................................................... 59
II. DETAILED CONCEPTION ............................................................................................ 59
CONCLUSION......................................................................................................................... 69
PART V: REALISATION PHASE .............................................................................................. 70
INTRODUCTION .................................................................................................................... 72
I. THE PHYSICAL DATA MODEL................................................................................... 73
II. NETWORKING PROTOCOLS USED............................................................................ 74
III. THE ARCHITECTURE OF THE APPLICATION ...................................................... 75
IV. PRESENTATION OF TOOLS USED........................................................................... 79
CONCLUSION......................................................................................................................... 80
PART VI: USER’S GUIDE.......................................................................................................... 81
I. DEPLOYING THE WEB SERVICES ............................................................................. 83
II. INSTALLING AND RUNNING THE CHAT SERVER................................................. 84
III. INSTALLING AND RUNNING THE DESKTOP CLIENT........................................ 87
CONCLUSION......................................................................................................................... 96
GENERAL CONCLUSION..................................................................................................... 97
BIBLIOGRAPHY.................................................................................................................... xiv
WEBOGRAPHY ...................................................................................................................... xv
ANNEXES............................................................................................................................... xvi

vi
LIST OF FIGURES
Figure 1: Organization Chart of NTfoods (source: NTfoods) ........................................................ 5
Figure 2: Project Plan (Gantt Chart) ............................................................................................. 23
Figure 3: Graphical representation of 2TUP (source: UML2 in action)....................................... 33
Figure 4: Diagrammatical representation of use case diagram..................................................... 36
Figure 5: Representation of actors ................................................................................................ 36
Figure 6: Representation of inheritance........................................................................................ 37
Figure 7: Representation of use case ............................................................................................ 37
Figure 8: Representation of an association relation...................................................................... 38
Figure 9: Representation of inclusion relation.............................................................................. 38
Figure 10: Representation of extension relation........................................................................... 38
Figure 11: Representation of specialization.................................................................................. 39
Figure 12: General Use case diagram of the entire communication system................................. 40
Figure 13: Activity diagram of “Send message” .......................................................................... 46
Figure 14: Activity diagram of “Broadcast message” .................................................................. 47
Figure 15: Generic Design............................................................................................................ 48
Figure 16: Component Diagram of the communication system ................................................... 50
Figure 17: Deployment diagram of the corporate communication system................................... 52
Figure 18: State machine diagram of “Instant Message”.............................................................. 54
Figure 19: Representation of sequence diagrams ......................................................................... 61
Figure 20: Sequence Diagram for messaging ............................................................................... 62
Figure 21: Sequence diagram of “authenticate” ........................................................................... 63
Figure 22: Sequence diagram of “configure sending rights”........................................................ 64
Figure 23: Class diagram of the Corporate communication system............................................. 68
Figure 24: Physical Data Model of the system ............................................................................. 73
Figure 25 Calculation of the database's size ................................................................................. 74
Figure 26: Physical architecture of the system ............................................................................. 76
Figure 27: Logical Architecture of the system ............................................................................. 78
Figure 28: Glassfish Server Admin Console ................................................................................ 83
Figure 29: Deploying the .war file................................................................................................ 84

vii
Figure 30: Browsing the the Chat_Server.jar file ......................................................................... 85
Figure 31: Chat server started....................................................................................................... 85
Figure 32: Chat server - help ........................................................................................................ 86
Figure 33: Online clients............................................................................................................... 86
Figure 34: Kicking-off a client ..................................................................................................... 86
Figure 35: Login frame ................................................................................................................. 87
Figure 36: Network settings.......................................................................................................... 88
Figure 37: Messaging/Broadcasting Module................................................................................ 89
Figure 38: Private Discussion window ......................................................................................... 90
Figure 39: Profile Module............................................................................................................. 91
Figure 40: Creating/Editing a profile Wizard - Profile Information............................................. 92
Figure 41: Creating/Editing a profile Wizard - Profile details ..................................................... 93
Figure 42: Logs Module................................................................................................................ 94
Figure 43: Emptying Logs ............................................................................................................ 94
Figure 44: Printing Logs ............................................................................................................... 95

viii
LIST OF TABLES
Table 1: Hardware Resources ......................................................................................................... 6
Table 2: Software Resources .......................................................................................................... 7
Table 3: Human Resources of NTfoods.......................................................................................... 8
Table 4: Software Resources (Source: Mercurial 2017 and from official websites).................... 21
Table 5: Hardware Resources (prices from Mercurial 2017) ....................................................... 22
Table 6: Human Resources (Prices from Mercurial 2017)........................................................... 22
Table 7: Presentation of the left branch ........................................................................................ 33
Table 8: Presentation of the right branch...................................................................................... 34
Table 9: Presentation of the right middle branch.......................................................................... 34
Table 10: Textual Description of “Authenticate” ......................................................................... 41
Table 11: Textual description of “Broadcast Message” ............................................................... 42
Table 12: Textual description of “Create Profile” ........................................................................ 43
Table 13: Explanation of Activity Diagrams................................................................................ 45
Table 14: Explanatory table of Component Diagrams ................................................................. 49
Table 15: Description of Deployment Diagrams.......................................................................... 51
Table 16: Explanatory table of State Machine Diagrams ............................................................. 53
Table 17: Explanation of Class diagram....................................................................................... 65
Table 18: Classes and Attributes of the System............................................................................ 67
Table 19: Tools used during the project ....................................................................................... 79

ix
ABBREVIATIONS
2TUP Two Track Unified Process
AICS African Institute of Computer Science
API Application Programming Interface
CLI Command Line Interface
CRUD Create Read Update Delete
CSS Cascading Style Sheet
DB Database
DBMS Database Management System
EJB Enterprise Java Bean
GNU GNU Not Unix
ICT Information and Communication Technology
IM Instant Messaging
JEE Java Enterprise Edition
JRE Java Runtime Environment
JPA Java Persistence API
JPQL Java Persistence Query Language
MVC Model View Controller
OOP Object Oriented Programming
PC Personal Computer
RDBMS Relational Data Base Management System
RUP Relational Unified Process

x
SMS Short Message Service
SOAP Simple Object Access Protocol
SQL Structured Query Language
UML Unified Modelling Language
UP Unified Process
MVC Model View Controller
XUP Extreme Unified Process

xi
ABSTRACT
In order to provide an answer to the expansion of expansion of ICT in the world, AICS-
Cameroon permits its students to gain professional experience through an academic internship, at
the end of which they will make their expertise available to the economy. The business that hosted
us of our academic internship is called NTfoods Ltd and the project theme is “Conception and
Realization of a Computerized Corporate Communication System: Case of NTfoods SARL”.
To realize this project, an investigation in different departments of NTfoods was realized
and despite its excellent business process flow, communication was found to be improvable. We
then analysed the business, using 2TUP and UML and came out with a fully functional solution to
improve communication techniques of NTfoods. The application was developed in a 3-layer
architecture, it is multiplatform and ensures a secured private communication within a Local Area
Network (LAN) or even through the internet. This application will permit smooth and more
efficient communication at NTfoods. The application produced at the end is called “EnterComm”
for “Enterprise Communication” and will be able to offer its services to desktop, android mobile
and web clients. Also, the application is thought to provide room for an evolution into one that is
used for communication between different physical agencies of NTfoods across the country, over
a Virtual Private Network 1
(VPN).
Key Words:
- Communication,
- Instant Messaging Application,
- Corporate communication,
- Chat,
- Secure discussions,
1
A virtual private network (VPN) extends a private network across a public network, and enables users to send and
receive data across shared or public networks as if their computing devices were directly connected to the private
network.

xii
RESUME
Dans le but de répondre aux nouvelles tendances imposantes des Technologies de
l’Information et de la communication, l’IAI Cameroun permet à ses étudiants d’acquérir une
expérience professionnelle à travers un stage académique, une expérience qu’il mettrons à la
disposition de l’économie. NTfoods SARL est l’entreprise qui nous accueillit et nous y avons
travaillé sur le thème « Conception et Réalisation d’un Système d’un Système de
Communication d’Entreprise, cas de NTfoods SARL ».
Dans le but de réaliser ce projet, nous avons attentivement observés les processus métiers
de NTfoods et en avons tiré que le système de communication de NTfoods, bien qu’efficace,
pouvait être amélioré. Nous avons ensuite utilisé la méthode d’analyse « 2TUP » avec l’aide
d’UML, afin d’obtenir une solution complète, multiplateforme et implémentable sur le réseau local
de NTfoods. Cette solution devra permettre une communication souple et efficiente au sein de
NTfoods dans un premier temps, et plus tard la communication vers l’extérieur. L’application, qui
s’appellera « EnterComm » qui signifie « Communication d’Entreprise » en anglais, a été
développé dans une architecture 3-tiers, et offrira ses services via les clients desktop, Android, et
web. Aussi, l’application a été pensée pour permettre une évolution en une plateforme qui lui
permettra d’être utilisée pour la communication entre les agences de NTfoods à travers le pays,
via un Réseau Privé Virtuel 2
(VPN).
Mots Clés :
- Communication,
- Messagerie Instantanée,
- Communication d’entreprise,
- Chat,
- Conversations sécurisées.
2
Un réseau privé virtuel est un système permettant de créer un lien direct entre des ordinateurs distants. On utilise
notamment ce terme dans le travail à distance

xiii
GENERAL INTRODUCTION
ICT is a key tool for efficiency and is basically the art of efficiently and automatically
managing information using a computer to ease or even replace human effort. Haven mentioned
that, what better sector than communication to apply ICT principles. NTfoods, a food producing
Cameroonian SME needs to control its communication process. NTfoods being our host center,
we took the challenge and developed the theme “Conception and Realization of a Computerized
Corporate Communication System” during the 3 months of internship. Even though
transmission of information is ideal for optimization through ICT, what brought us to choose this
theme is the importance of a good communication in a business. The communication system
actually ensures the transmission of information within the business. The need for amelioration in
this domain is that an ineffective communication system may lead to data inconsistency, conflicts,
disorder and wrong and slow decision making. That is why we will build and deploy a software
through which NTfoods will perform operations based on chatting, emailing, and messaging
through SMS.
In this book, we will cover the entire internship session, passing through the presentation
of our host business NTfoods, analysis and implementation of the software solution. We divided
this report into five parts which are as follows:
1. Insertion document: In this part we will present the company in which we spent
our internship period and the way we were welcomed in the company.;
2. Specification Book: In the specification book, we specify the needs of the
customer taking into consideration the time and cost of the project;
3. Analysis Document: It presents the analysis method chosen (2TUP) together with
the presentation of the associated UML diagrams used for the analysis of the
project;
4. The Realization Phase: It will permit the visualization of the implementation
process of the solution;
5. The User’s Guide: Which presents the condition necessary to use the application
and how to use it.

1
PART I: INSERTION PHASE

2
Preamble
This document is the first document produced for this internship. It presents the events that
happened at the beginning of the internship and also, presents the host company: NTfoods TANTY,
specifying its structure, composition, location and history.
Content
INTRODUCTION
Reception at NTfoods Ltd
I. Presentation of NTfoods Ltd
II. Resources
III. Geographical Location
CONCLUSION

3
RECEPTION AT NTFOODS
Upon arrival at NTfoods on Monday, 17th
July 2017 at 7:30 AM, we were welcomed by the
human resource department. The workers of the department presented to us, in the form of slide
shows, the structure and activities of NTfoods. The slide show contained a detailed presentation of
the history of NTfoods, its growth and the products it supplies. There-after, we discussed on details
of our internship session and concluded with the signature of internship contracts. The following
day, we had a complete guided tour of the departments of NTfoods and were presented to our
respective departments. After integrating departments, we were then assigned professional
supervisors.

4
INTRODUCTION
The insertion report presents the process of integration and adaptation in the host business.
It basically describes the composition of NTfoods and also its organization structure. This is in fact
the first of a series of documents that will be the result of our presence in this business. Here, we
are going to present the history, mission, organization and finally the theme of our internship.
I. PRESENTATION OF NTfoods Ltd
NTfoods is a Cameroonian food-producing company whose goal is to process/transform
agricultural products such as maize, soya bean and groundnut into finished and semi-finished
products. NTfoods aims at ensuring a permanent distribution of its products in the whole country.
Categorized in small- and medium-sized enterprises (SMEs), it is a limited liability company
located in Yaounde and has as vision to produce high quality “Made-in-Cameroon” products for
the whole of central Africa. NTfoods was created by Mr. Thierry NYAMEN, Doctor in processing
of agricultural products.
The idea of creating a business came from the fact that during his studies at KHARKOV
(EX-USRSS) university of agricultural techniques, he was not able to receive ground groundnuts
from his mother. His mother actually lacked electricity to grind and send the groundnut.
Disappointed about this situation he then got the idea to build a complex machine that could
process large amounts of groundnuts to produces powdered groundnuts, groundnut oil, for the first
time on the African continent. In 1999, the first product was presented and approved and in the
year 2000 this business was actually born and by then was called “TANTY”. From then, TANTY
grew larger in size and quality of its products and won many prizes.

5
Organization Chart of NTfoods
Figure 1: Organization Chart of NTfoods (source: NTfoods)

6
II. RESOURCES
A. Hardware Resources
Each office of NTfoods has a desktop computer and those computers are interconnected in a
network. Other equipment present are:
Table 1: Hardware Resources
No Equipment Qtty3
Characteristics Use
1 • Server PC; 1 IBM
Used as FTP Server for file
transfers,
2 • Routers 1 TP LINK Used as gateway
3 • Switches; 4 TP LINK
Used to interconnect the
networking equipment
together
4 • Modems 2 D-LINK
Converts analog signals to
digital signals and vice versa
5 • Printer 1 HP
Used to convert softcopies to
hardcopies (paper)
6 • Security camera 3 DVR
Used to monitor the different
rooms and offices of
NTfoods for security
purposes.
3
Qtty: Quantity

7
B. Software Resources
Computers are equipped with windows operating systems such as windows seven software
tools such as:
Table 2: Software Resources
Software Use
• SAGE SARE;
For recording, managing the company’s stock
and accounts. (Accounting)
• Microsoft Office suite (Word, Excel,
PowerPoint, etc.);
Edition of Word documents, spreadsheets and
presentations)
• Web browsers such as Internet
explorer and Mozilla Firefox;
Edition of mails, communication through
social networks, fetching contents and
resources available.
• Skype Videoconferencing

8
C. Human Resources
Table 3: Human Resources of NTfoods
Resource Role
CEO4
- Owns the control of the business,
- Defines the broad goals to follow for the success of the business,
- Makes strategic decisions that will affect the business in long-term,
- Manages the production services,
- Defines the prices of products,
- Defines the objectives of the commercial agents,
- Encourages and motivates the commercial forces,
- Follows up the activities of all the services and orders expenditures.
The manager
- Manages procurements of raw material,
- Is in charge of managing stocks in the production department and in
the commercial department,
- Manages the company’s accounts,
- Calculates salaries,
- Manages administrative matters and workers’ profiles,
- Is in charge of the payment of all bills, taxes and raw material,
- Helps the CEO in decision making and collaborates with him.
SECRETARY /
FINANCIAL
MANAGER
- Monitors sales,
- Manages the archives,
- Manages administrative matters,
- Helps in taking important decisions for the business.
HEAD OF THE
PRODUCTION
DEPARTMENT
- Organizes and monitors the works in the factory,
- Makes sure the defined objectives are met and reports to the manager.
COMMERCIAL
MANAGER
- Manages the commercial forces and ensures that the CEO’s
predefined objectives are met,
- Organise and plans meetings,
- Organizes commands,
- Follows up the important clients of the business (supermarkets,
wholesalers),
- Negotiates sales in big stores
COMMERCIAL
AGENTS
- Are in charge of distributing the products to the selling points,
- Are in charge of promoting the products,
4
CEO: Chief Executive officer

9
HOSTESSES
- They are in charge of presenting the products in supermarkets and
convincing customers to buy them.
III. GEOGRAPHICAL LOCATION
Localization Chart
The company, NTfoods, is located at ODZA in Yaounde precisely at the highway through the entrance
of “Cité de la Paix”. The following figure provided by NTfoods better illustrates its geographical location.
Figure 2: Geographical location of NTfoods (source: NTfoods)
Usine NT Food
école primaire
st pierre
apotre de
messamedon
go
Commissariat
odza Complexe
scolaire bilingue
l’excellence
École maternelle
sante anne
College
eloungoou
amougou
Station service Tradex
Rond point
messamedongoVenant
de mvan
Venant de nsam
efoulan
Venant de
nsimalen
Venant du deuxième
échangeur
ACCD

10
CONCLUSION
The end of the first two weeks of internship has helped us to take contact with our
environment in NTfoods, which is the company in which we will work during our three months of
internship. We could enter into contact with the business, condition in which we find ourselves in
this company together with the understanding of the business, its personnel, its mission, and its
rules and regulations. As mentioned before, we as students studying computer science had to
observe the business processes and come out with an aspect of it that we would then optimize
through a computerized solution. Concerning the aspect to be optimized, communication within
NTfoods drew our attention and after some analysis, the theme: “Conception and Realization of
a computerized corporate communication system, case of NTfoods was held as internship
project. The next step in this book will be to elaborate the preliminary study which would in line
with the academic and professional needs.

11
PART III: SPECIFICATION
BOOK

12
Preamble
The specification book is the part of the document that describes with precision the needs
of the user and the conditions necessary for a successful completion of the project. This part is
considered as the part of communication and the description of the project in order to avoid results.
Content
INTRODUCTION
I. Context
II. Study of the Existing
a.Shortcomings
b.Proposed Solution
III. Project Plan
CONCLUSION
CONCLUSION

13
INTRODUCTION
The specification book gives us the directives on the product to be delivered, the
conditions of their delivery and the technical specifications of the deliverables. We will establish
this book as the executors of the project on one hand, and the close agreement with the project’s
owner or client. In this project, we are the executors of the project and NTfoods makes up the
project owner. This specification book will enable us to realize and also specify the needs of the
user (clients) geared towards the new information system, details to respect as well as the
constraints on the tools to be used.

14
I. CONTEXT
Communication is a process of information transfer from a sender to a receiver via a
medium, the process starting from an inner state of the sender which produces the transfer of the
signal and ending with an inner state of the receiver when the signal is delivered (Shannon &
Weaver, 1949). Robbins et al (2000:633) defined communication as a participative, two-way
sharing of understanding, commitment and purpose, leading to appropriate action").
Corporate communication is a management function that offers a framework for the effective
coordination of all internal and external communication with the overall purpose of establishing
and maintaining favorable reputations with stakeholder groups upon which the organization is
dependent.
Characteristics of communication
Two-way process: It refers to a communication where the participants take turns in being speaker-
listener, writer-reader, and the process being complete only if there is a feedback from the receiver
to the sender on how well the message is understood.
Verbal and nonverbal: Verbal communication uses sounds and language to express ideas and
concepts while non-verbal communication uses gestures, touch and body language to send and
receive wordless cues between people.
Language familiarity: Effective communication means that the sender must use a language the
receiver is familiar with, otherwise the communication will be a failure.
Interest in the message: The receiver has to be interested in the subject the sender has to convey,
so that the communication process is successful.
Perception: There should be a consensus between the message that is sent and the one that is
received. The intended meaning has to be the same for an effective communication.
Continuity: Communication is continuous because in everything we do, we have to convey or
receive information, the exchange of information being a continuous process.
Components of communication
Communication becomes effective when it achieves the desired response from the receiver.
These are the components by means of which communication can be effective:
Context

15
- Every communication starts with a context and is affected by the context in which it occurs.
The context could be cultural, social, physical, etc. and it is the sender who chooses the
message to communicate within such a context.
Sender/encoder
- This is the person who conveys the message. He/she uses words, visual aids or body
language to send the message and produced the desires response, the verbal or nonverbal
symbols chosen being essential for a correct interpretation of the message by the receiver.
Message
- The message is the essence of what the sender wants to communicate and it is the starting
point of the communication process because the sender starts by planning the message
he/she wants to transmit.
Medium
- It is the channel which is used to conduct the communicative act. It is essential to choose
the right medium in order to have an effective communication.
Receiver/decoder
- This is the person to whom the message is addressed, the understanding of the message
depending also on the relationship between the sender and the receiver, but also on the
reliance that the encoder has on the decoder.
Feedback
- Feedback is very important for the communication process as the sender has the possibility
of analyzing the efficacy of the message and to understand if the message has been
interpreted correctly
• THE IMPORTANCE OF INTERNAL COMMUNICATION
o What is employee communication?
Effective internal communication is at the heart of achieving business outcomes and it’s
something the whole organization is responsible for. It supports the organization’s smooth running,
successful change programs and good leadership on vision, strategy and values. Despite the need
for communication to be high up the agenda in all organizations, not many employees feel fully or
fairly well informed about what’s happening in their organization, some even saying they receive
limited or very little information.

16
The communication media
As mentioned earlier, an important aspect of communication is the medium and those used by
NTfoods are mainly based on the following:
1. Direct
Direct communication here refers to direct mouth-to-ear communication.
2. Fixed phone calls
NTfoods, just as many other businesses rely on national mobile telephone network providers
for most of their distant voice communication practices.
3. Short Message Services (SMS)
Short Message Services also serve for distant communications and are used generally in the
case the mobile phone calls are not available.
4. Electronic messaging (e-mails)
E-mails are also used by NTfoods and permit communication with any stakeholder, no matter
his location on the earth surface through internet access.
II. PROBLEM DEFINITION
NTfoods does not have problems using this system. All the above tools were adopted in
order to target every stakeholder no matter his/her geographical location. Having all this in mind,
it is not easy to understand why this should change. That is where technology and innovation comes
in to optimize and create value. As mentioned before communication is crucial for a business and
the case of NTfoods will serve as an illustration

17
If we have a closer look at the existing communication system, we will notice the following:
1. Direct communication
Direct communication should not be canceled but is not appropriate when the sender and the
receiver are in different offices, departments. This is usually materialized by a worker shouting
loud for a worker in another office to get his/her message. This is very insecure and will always
disturb other workers, who will take some time to come back to what they were working on. This
does not mean that the information should not be transmitted but should be in another way that is
as instantaneous as direct communication is.
2. Mobile phone calls
This medium is excellent but again, there is a problem. This solution was thought to be a
standalone system and in our case, is not integrated to their system. To be clearer, the problem is
simply the fact that voice calls are made on a dedicated terminal equipment and not on the device
workers in their office spend their days on, their computer. In addition to that, any increase in the
number of offices will mean the purchase of a new terminal equipment which will cost some money
and as mentioned earlier, NTfoods is an SME whose aim is to minimize cost and maximize profit.
Mobile phone services used by NTfoods are thought for the general public, not for NTfoods in
particular. Mobile phone communication here is peer-to-peer. That is a one-to-one communication
which does not allow for the implementation for grouped discussions unless implemented by a
specialized technician. A dedicated software solution would make creation of grouped discussions,
broadcasting5
and conferencing to be available in just some few clicks.
3. SMS
The current implementation of SMS within NTfoods is through the use of mobile phones with
basic phone numbers. This is perfect for the general public but for NTfoods, certain messages
should be unidirectional and company’s name should be seen as the sender instead of a plane series
of digits representing the company. Also in the current system, using a mobile phone for corporate
communication is not appropriate, for mobile phones are personal and are meant to be used and
5
Broadcasting: By broadcasting, we refer here to the act of creating one message and sending it to a group of
numerous users.

18
managed by a single user at a time. The small size of the screen, keyboard and the input method
confirms that. Having to compose a message for customers daily and sending them manually on a
small phone with all the edition limits that it signifies is expensive in time, energy and money. And
as if this was not enough, only the current owner of the phone can send a message at a time.
4. Electronic messaging
The problem with the currently implemented electronic messaging solution resides in the fact
the does not permit a custom email using animations and images. It does not permit NTfoods to
use customers’ email addresses to send them dynamic and rich contents for advertisement of their
products, which limits their communication possibilities.
III. OBJECTIVES
A. Global Objective
The main objective of this project is to conceive and implement a computerized solution that
will improve the communication system of NTfoods and make it more efficient.
B. Specific Objectives
We want to build a software that will use the Local Area Network currently installed at NTfoods,
its internet access and its computers to exchange messages instantly, thus permitting broadcasting,
conferencing, mailing and sending of SMS. The system will be able to:
❖ Interconnect the offices of NTfoods and permit distant conferencing or chatting (be it
grouped or private);
❖ Provide a unique interface through which NTfoods will perform all text-based digital
communication. That is: mailing, SMS and chatting be it to its internal or external
stakeholders (of course, only the internal stakeholders will benefit from instantaneous
chatting);
❖ Provide a private and secured communication medium to workers of NTfoods;
❖ Allow for timed messaging;
❖ Allow for broadcasting;
❖ Allow controlled access to communication media and profiles;

19
❖ Allow for unidirectional SMS, named messages (SMS whose sender name is always the
same text).
❖ Allow for usage of the same SMS profile for all messages sent by the company
❖ Permit messages to be composed once, media chose, profiles chosen and used to send the
messages at once.
❖ Secure messages that are exchanged through the system.
IV. TECHNICAL CHOICES
NTfoods being a food producing company, is not willing to allocate huge budgets on new
equipment dedicated to communication such as VOIP6
servers for voice video conferencing
through the local network. Hence any solution should be able to use the existing equipment to meet
its objectives. Because of this, a support for most devices and platforms is necessary to make sure
all the stakeholders are targeted. In addition to that, all these devices need to be interconnected to
consume the same services from a central server. This explains the choice of the following
technologies:
JEE for Web services and web clients and JPA for communication with the
database. Web clients will also be created in order to ensure universal portability
with the condition of the installation of a web browser.
PostgreSQL as DBMS for its security and functionalities (schemas, user groups,
etc.)
JSE for desktop clients and rapid access to system low-level services such as
multithreading, system notifications, automatic execution of programs.
JavaFX for its stability, regular updates and cool UI7
capabilities.
6
VOIP: Voice Over IP (Internet Protocol). It is a methodology and group of technologies for the delivery of voice
communications and multimedia sessions over (IP) networks, such as the Internet.
7
UI: User Interface

20
V. FUNCTIONAL CHOICES
❖ Security
Once the user launches a connection request, his/her security level is determined by the
communication system and a custom interface is presented. Profiles available for communication
are those are predefined because everybody should not be able to communicate to any profile, for
security purposes.
Also, messages that are exchanged should be encrypted, so as to prevent middle listeners from
obtaining sensible information about the business.
❖ Availability
Since NTfoods is supposed to rely on this system for most communication processes, the
system should be made accessible from the time the user starts the working time (assuming the
user starts the computer at the beginning of everyday) to the time he/she ends the working session
for that day (shutting down the computer).
❖ Usability
The system should be fast and easy to use since communication is best when instantaneous.
We have now gathered all the expectations we have for the communication solution
and the next step is to set a plan on how to accomplish that. We will have to gather what will be
needed, derive its monetary value, schedule the analysis and development process and sort out the
end products.
VI. PROJECT PLAN
This section describes scheduling of the project realization, its costs and products. This
project will have to pass through a series of feasibility studies, field studies and analysis, to ensure
a perfect definition of the context, expectations and boundaries. The project will then pass through
the implementation, testing and maintenance phases to ensure its realization. This section will also
define the time schedule.

21
A. Time Scheduling
The time management being an important factor in project management, it is important to
define exactly when and for how long each phase of the project will be realized. Our internship
period is 3 months which leads us to the below scheduling of time:
The time being completely allocated, we need to allocate resources to the project according to
its requirements.
B. Estimation of Resources Needed
1. Software resources
Table 4: Software Resources (Source: Mercurial 2017 and from official websites)
Resource Software Usage Qtty8 Cost
(FCFA)
Database
Management
System
PostgreSQL Communicating with the
database
1 Free
Operating
System
Microsoft®
Windows® 10
Operating system of the
computer used for testing
1 17 500
Ubuntu 16.04 LTS Operating system of the
computer used for software
development
1 0
Development
Software
NetBeans IDE Integrated development
environment for editing of
HTML, CSS and PHP codes.
1 Free
Project
Planning Tool
GANTT Project Project planning tool 1 Free
Word
Processor
Microsoft Office Used for the realization of
the internship report
1 10 000
8
Qtty: Quantity

22
Modelling tool Visual Paradigm + 3
months’ license
Modelling the system in
UML
1 52 500
Server
Package
Glassfish Server Server suite that hosts web
container and Enterprise
Java Beans
1 Free
Total 1 - - 80 000
2. Hardware resources
Table 5: Hardware Resources (prices from Mercurial 2017)
Resource Hardware Usage Qtty
9
Cost (FCFA)
Computer HP EliteBook 8640p Analysis, coding,
document building
1 250,000
Installation
Media
CD-ROM Installation media 1,000
Removable disk 16GB USB key For file transfers
between computers
1 8000
Total 2 - - 259 000
3. Human resources
Table 6: Human Resources (Prices from Mercurial 2017)
Resource Number Cost per day Number of days Cost (FCFA)
Project Head 1 20 000 50 1 000 000
Analyst 2 12 500 21 252 000
Designer 2 10 000 5 200 000
9
Qtty: Quantity

23
Programmer 2 5750 25 287 500
Consultant 1 10 000 7 70 000
Total 3 - - 1 809 500
Total1 + Total2 + Total3 = 2 148 500FCFA
Unexpected: 20% of Total = 429 700 FCFA
Overall total = 3,028,623 + 605,724 = 3,634,347 FCFA
Hence the total cost is evaluated at 2 578 200 FCFA
The resources and their cost allocated to the project, we have to define what will be the
output of these resources.
C. Global Planning of the Project
For the realization of this project, our application will pass through several stages which
depend on each other. The duration of this project is 3 months. Each stage must be carried out in
the strict respect of the time which is assigned to it as indicated in the following diagram:
Figure 2: Project Plan (Gantt Chart)

24
D. Items Produced
At the end of the internship period, we are supposed the produce:
✓ An insertion report;
✓ A specifications book;
✓ An analysis document;
✓ A conception document;
✓ An implementation document;
✓ A user manual;
✓ The software in a CD-ROM.

25
CONCLUSION
NTfoods received us as students in Software Engineering and expected from us a net
amelioration of their system through a software solution. After observation of their system,
limitations were identified in the communication sector. We had to gather ideas and tools that could
meet the stated requirements and solve the problem. Doing all of this is already great because
everything seemed to be functioning well, but our studies revealed that this was not the case.
Through this solution, NTfoods expects us to have its productivity considerably increased, its
expenditures reduced and the quality of its communication practices greatly improved. All is now
left to develop and implement this system which will be the main topic of the next sections.
Particularly, the next section will describe an important phase of the software development
lifecycle, the Analysis Phase. With the use of 2TUP and UML, we will organize the building blocks
of the future system for a smooth and organized implementation phase.

26
PART IV: ANALYSIS PHASE

27
Preamble
The analysis put in place in this book present a modelling of the solution proposed, presents
in details the functionalities to take into consideration and with the aid of UML diagrams, the
details on how information and resources are put together to fulfill use cases.
Content
INTRODUCTION
I. Description of the Existing System
II. Presentation of the analysis method
III. Capture of the functional needs
IV. Capture of the technical needs
V. Analysis
CONCLUSION

28
INTRODUCTION
All computer projects need to be well analyzed to provide an answer to the problems faced.
Before programming, we have to be sure that we will consider all the specifications of the project.
This part will permit us to define all the boundaries of the system, its component and how they
interact together to accomplish a task. This way of analyzing a system is known as 2TUP and gives
us the methodology to follow in order to ensure the usability and reliability of the future system.
2TUP makes use of graphical representations in order to illustrate the various steps of the
development of a software. The diagrams used by 2TUP follow a language called the Unified
Modelling Language (UML). Before going into the analysis, it is important to understand these
tools first, and this will be our entry point to this section.

29
I. DESCRIPTION OF THE EXISTING SYSTEM
NTfoods SARL needs to communicate within their infrastructure. This is already achieved
through a set of communication tools. But why this project? We will better understand from these
results obtained after a study of the existing communication system.
Limitations Consequences Technical Solution(s)
Direct conversations
within the company
are usually verbal
- Workers are being distracted by
loud conversations.
- Private conversations are
insecure since any nearby
person can get it.
- Implementation of a text-
based instant communication
system.
Digital conversations
at NTfoods use public
and internet-based
solutions
- There is always the dangerous
risk of having sensible
information being stolen by
outsiders.
- Implementation of a secured
communication system that
will keep all conversation data
within the infrastructures of
NTfoods
A limited number of
offices at NTfoods
have a fixed phone
- Only those offices that have
phones can be contacted
through a call. Others will have
to either shout or go to whom
they want to discuss with
- Implementation of a software
that will make the computers
and mobile phones of the
workers communicate
The usage of
traditional phone
numbers for SMS to
stakeholders of
NTfoods
- The sender identifier of
NTfoods’ messages is a plain
phone number and usually
varies.
- Messages that serve for simple
information purposes can be
replied to, by customers. This is
not always the desired
functioning.
- Implementation of an SMS
management system that uses
the company’s name as sender
ID for customer care, and
which is unidirectional10
.
The usage of
traditional email
services for email
communication
- Limited possibilities when it
comes to advertisement of
products.
- Wastage of time in building up
and sending messages that
could be send in bulk and
automatically.
- Implementation of a dynamic
rich email managing tool that
can send programed
advertisements to customers.
10
This means that the NTfoods alone can send a text message to customers.

30
II. PRESENTATION OF THE ANALYSIS METHOD
A. Presentation of UML
UML stands for Unified Modelling Language. It is a graphical language used for visualizing,
specifying and documenting blueprints of an object-oriented software system.
As its name suggests, UML defines software system and is just a language. There is no
development method or procedure in UML and is thus incomplete for software development.
UML proposes two main ways in which a system can be looked at:
- Structural View
- Behavioral View
1. Structural View
The structural view shows elements that make-up the system and their relationships. In
fact, the class diagram is a perfect example. Other diagrams just follow the principle of class
diagrams. The other diagrams that constitute this view are: object diagram, composite structure
diagram, component diagram, deployment diagram and finally package diagrams.
The following describes diagrams of the structural view.
Package diagrams are used to divide the model into logical containers or “packages” and
describe the interactions between them at a high level
Class or Structural diagrams define the basic building blocks of a model: the types, classes
and general materials that are used to construct a full model
Object diagrams show how instances of structural elements are related and used at run-
time.
Composite Structure diagrams provide a means of layering an element's structure and
focusing on inner detail, construction and relationships
Component diagrams are used to model higher level or more complex structures, usually
built up from one or more classes, and providing a well-defined interface
Deployment diagrams show the physical disposition of significant artefacts within a real-
world setting.

31
2. Behavioral View
Behavioral diagrams capture the variety of interaction and instantaneous state within a
model as it ‘execute’ over time.
Use Case diagrams are used to model user/system interactions. They define behavior,
requirements and constraints in the form of scripts or scenarios.
Activity diagrams have a wide number of uses, from defining basic program flow, to
capturing the decision points and actions within any generalized process.
State Machine diagrams are essential to understanding the instant to instant condition
or "run state" of a model when it executes.
Communication diagrams show the network and sequence of messages or
communications between objects at run-time during a collaboration instance.
Sequence diagrams are closely related to Communication diagrams and. show the
sequence of messages passed between objects using a vertical timeline
Timing diagrams fuse Sequence and State diagrams to provide a view of an object's
state over time and messages which modify that state.
Interaction Overview diagrams fuse Activity and Sequence diagrams to provide allow
interaction fragments to be easily combined with decision points and flows.
B. The Process of Development of Software
A process is defined as a sequence of steps, partly ordered which permits to obtain software
system or the evolution of an existing software. The objective of software development is the
production of quality software which answer the needs of users during a particular time and at a
particular cost.
C. A Unified Process
A unified process is a process of development of software constructed on UML; it is
iterative, incremental, centered on the architecture, driven by the use cases and driven by
requirements.
- Iterative and incremental

32
Iterations are distinct sequences of activities with a basic plan and evaluation criteria which
produce an output (internal or external). Either the content of an iteration is ameliorated or the
evolution of the system is evaluated by the users.
An increment is the difference between two release produce at the end of two iterations. Each
iteration ensures that the group is capable of integrating the technical environment in order to
develop a final product and give the possibility to users to have tangible results of their
specifications.
- Risk-driven: Here, the major causes of the failure of software project must be avoided in
priority. We identify the first cause coming from the incapacity of the technical architecture
to answer to operational constrains and the second cause is due to inadequacy of the
development of the needs of users.
- It is constructed around the creation and the maintenance of a model instead of the
production of mountain of documents. The volume of information of this model needs a
strict organization which represents the different viewpoints of the software at different
level of abstraction.
- It is component oriented: Whether at the level of modelling and/or production, it is the
guarantee of flexibility for the model itself and the software it is representing. This type of
practice constitutes the necessary support for the re-usability of software and offers a
perspective of gain that is not negligible.
- It is user oriented: since the specification and the conceptions are constructed from the mode
of utilization of the user of the systems.
- Examples of unified process are 2TUP, RUP, XUP, EUP, …
D. Two Track Unified Process
2TUP is a Unified process. The 2TUP brings an answer to the constraint of continual changes
imposed by the information system of the business. In this sense, it enforces the control on the
capacity of evolution and correction of the system. “2 Tracks” signifies literally that the system
follows two branches. These branches are “functional” and “technical” branches which answer to
the two level of changes imposed by the information system. After the evolution of the functional
branch and the technical branch, the realization merges the results of the two branches. The

33
merging permits to obtain a process of development in the form of Y as illustrated in the figure
below.
Figure 3: Graphical representation of 2TUP (source: UML2 in action)
i. The left branch (functional)
It captures the functional needs which help preventing the production of software that does
not fit the need of the user. The analysis here consists of studying precisely the functional
specification in order to obtain an idea of what the system is going to realize and its result does
not depend on any technology. The table below shows the different diagrams which constitute
this branch.
Table 7: Presentation of the left branch
Capture of the functional needs
▪ Use case diagram
▪ Collaboration diagram
▪ Activity diagram

34
Analysis
▪ State machine diagram
▪ Package Diagram
▪ Interaction overview diagram
ii. The right branch (Technical branch)
It captures all the constraints and choices related to the conception of the system,
the tools and equipment’s as well as the integration constraint with the existing system
condition. The different diagrams are shown in the table below:
Table 8: Presentation of the right branch
Capture of the technical needs
▪ Component diagram
▪ Use case diagram
Generic conception ▪ Deployment diagram
iii. The middle Branch
The preliminary conception, the detailed conception and the documentation of the system
are studied here. The diagrams are shown in the table below:
Table 9: Presentation of the right middle branch
Preliminary conception ▪ Component diagram
▪ Deployment diagram
Detailed conception
▪ Class diagram
▪ Sequence diagram
▪ Collaboration diagram
▪ State machine diagram
▪ Activity diagram
▪ Component diagram

35
III. CAPTURE OF THE FUNCTIONAL NEEDS
The capture of the functional needs is the first step in the left branch of 2TUP’s Y structure.
It formalizes and explains in details what have been presented in the preliminary study. Here, we
will gather all the functional elements of the future system such as actors of the system and
functionalities that we want the system to be able to offer. From the above preliminary studies, the
system should offer the following use cases:
A. Identification of Use Cases
The different use cases of our system are as follows:
✓ Authenticate
✓ Configure senders and receivers
✓ Schedule a meeting
✓ Create a message template
✓ Schedule a message
✓ Broadcast a message
o Through Instant Message (IM)
o Through SMS
o Through Email
o To all employees
o To a department
o To suppliers/clients
o To a third-party profile
✓ Disconnect

36
USE CASE DIAGRAM
The use case diagram simply shows the functionalities of the system, their
interdependency and how they are linked with actors of the system. It also clearly defines the
boundaries of the system. The following is a use case diagram:
Figure 4: Diagrammatical representation of use case diagram
▪ An Actor
Figure 5: Representation of actors
An actor represents an entity that directly interacts with the system. The actor is what performs
the different possible actions of the system. The following is a representation of an actor as
specified by UML:

37
Note that an actor does not necessarily represents specific physical entity but merely a
particular facet of some entity that is relevant to the specification of its association use case.
Actors can have relations between them. The only possible relation between actors is
inheritance and is represented by an empty arrow-headed line from the child to the parent actor.
For example:
Figure 6: Representation of inheritance
Use case
A use case represents a functionality of the system. It is an action that can be performed by an
actor. It is represented as follows:
Figure 7: Representation of use case
The notation for using a use case is a connecting line with an optional arrowhead showing the
direction of control. The following diagram shows the relation between an actor and a use case:

38
Figure 8: Representation of an association relation
Use cases can have relationships between them. The relationships can be
specialization/generalization, inclusion or extension.
1. Inclusion:
An inclusion relation denotes that an included action must be performed before another
action can be performed. It is represented by a broken arrow with the stereotype “<< include >>”
as follows:
Figure 9: Representation of inclusion relation
2. Extension:
An extension relation denotes that an action may be performed while another one is being
performed. It is represented by a broken arrow with the stereotype “<< extend >>” as follows:
Figure 10: Representation of extension relation
Specialization:
A generalization relation between use cases denotes different ways of performing a
particular action or use case. For example,

39
Figure 11: Representation of specialization

40
The use case diagram of communication system is as follows:
Figure 12: General Use case diagram of the entire communication system
In NTfoods, there is a communicator and there is a secretary in charge of
communication. But, for tasks like configuring the communication system, creating and using
message templates, it is the communicator’s task. The employee on his side can of course perform
basic communication practices as shown in the diagram.

41
B. The Description of Use Cases
As we mentioned earlier, a use case represents a functionality. Here, is a question of
breaking down the use cases, making a textual and graphical description emphasizing on the
different detailed scenario. This will be done using diagrams known as the sequence diagram, the
collaboration diagram and activity diagram.
The various textual description will be represented as follows:
➢ Identification of content: here we are going to give the title, the goal and actors
concerned in the user cases.
➢ The description of scenario of uses cases.
The description will be presented in the form of a table, where we will find the elements mentioned
above.
1.The use case “Authenticate”
Table 10: Textual Description of “Authenticate”
Identification of content
Title: Authenticate
Goal: To permit all the workers of NTfoods to connect to the communication system.
Actors: Employee.
Description of scenario
Pre-conditions:
1. The computer is just switched on;
2. The JEE server is running;
3. The chat server is running;
4. The client is connected to the local network
Nominal Scenario:
1. The system sends a connection form;
2. The user enters the login and password and submits;
3. The system verifies the information in the database;

42
4. A home page is presented to the user in case a matching account was found in the
database;
Alternative Scenario
5a. An error message is displayed to the user;
5b. The system returns to step 2.
Post-conditions:
1. The client is the home window is displayed;
2. The use case “Broadcast a Message”
Table 11: Textual description of “Broadcast Message”
Title: Broadcast Message
Objective: Allows the user to compose a single message and send it to one or more profiles
and through one or many media at once.
Principal actor: Employee
Description of scenarios
Pre-condition: Authenticate
Nominal Scenario:
1. In the “Home” menu, the user chooses “Broadcast Message”;
2. The system presents a window with two options: “Internal” and “External”;
3. The actor chooses the scope of his/her message by clicking on an option;
4. The system displays a message configuration wizard.
5. The user chooses the concerned groups and clicks on “next”;
6. The system displays a list of profiles in the selected groups;
7. The user choses the concerned profiles and clicks on finish;
8. The system disposes the window and shows a message form;
9. The user fills the form with the message and clicks on send;
10. The system sends the message to the destination profiles through the selected media
and describes the progression to the user.
11. System completes and displays a success message

43
3.The use case “Create Profile”
Table 12: Textual description of “Create Profile”
Alternative scenario
11a. System fails to send some or all of the sending operations;
11b. The system displays an error message with the details of the error.
Title: Create Profile
Objective: Create a profile entry in the communication system.
Principal actor: The Communicator
Pre-condition: Authenticate
Description of scenarios
Nominal Scenario:
1. In the “Profiles” tab, the communicator clicks on the “New” button;
2. The system displays a new profile-wizard;
3. The communicator fills in the profile’s information and clicks on “Next”;
4. The system saves displays fields concerning the account details;
5. The communicator fills the matricule and password of the new profile and clicks on
“Next”;
6. The System saves and display groups;
7. The communicator selects the groups to be attributed to the new profile and clicks
“Finish”;
8. The System saves the new profile in the database;
9. The System displays and success message to the communicator.
Alternative scenario
3.
3a. The Communicator fills in the profile’s information but clicks on “Finish”;
3b. The System goes to step 8.
8.
8a. The System fails to save the message in the database;

44
8b. The System displays an error message to the communicator.
Post Condition: A new entry representing the new profile appears in the profiles table.

45
C. Activity Diagram
The activity diagram is used to represent the sequence of activities and actions of the system
or its functionality. It shows details from a start point to end point through all decisions and actions
that can possibly be performed. It permits to consolidate the specification of a use case. It may be
used to detail situations where parallel processing may occur in the execution of some activities.
Table 13: Explanation of Activity Diagrams
Name Diagrammatical Representation Description
Activities An activity is a round
cornered rectangle enclosing
all actions, control flows and
other elements that make up
an activity.
actions It represents single step
within an activity.
Control flow It shows the flow of control
from one action to the next.
Initial node An initial node is a control
node that splits a flow into
multiple concurrent flows.
Final node Denotes the end of a single
control flow.
Flow final node It denotes the end of a single
control flow.
Decision and merge
nodes
It is used either for decision
or merge.

46
The following diagram are activity diagrams of our system:
Activity diagram of Send message
Figure 13: Activity diagram of “Send message”

47
Activity diagram of Broadcast message (IM and SMS)
Figure 14: Activity diagram of “Broadcast message”

48
IV. CAPTURE OF THE TECHNICAL NEEDS
The capture of the technical needs is a specification of the right branch and it is important
for the architecture. Here, we need to design a mock-up of the future system, know the materials
that are going to be used; that is the machines needed, the network and tools need for the
development of the software.
A. GENERIC CONCEPTION
Figure 15: Generic Design
Tool Bar
Menu
Content
Main Content
Login form

49
B. PRELIMINARY CONCEPTION
1. Component Diagram
A component diagram shows pieces of software or embedded controllers that will
make up the system. A component diagram has a higher abstraction level compared to a class
or composite structure diagram. This is because it is usually implemented by one or more
classes at runtime and can thus encompass a large portion of the whole system.
Table 14: Explanatory table of Component Diagrams
Name Diagrammatic
representation
Description
Component It represents a modular part of a system
that encapsulate it content and whose
manifestation is replaceable within it
environment.
Interfaces An interface is a kind of classifier that
represents a declaration of a set of
coherent public features and
obligations. An interface specifies a
contract; any instance of a classifier
that realizes the interface must fulfil
that contract.
Port A port is a property of a classifier that
specifies a distinct interaction point
between that classifier and its
environment or between the (behavior
of the) classifier and its internal parts.

50
Component Diagram of “Messaging”
Messaging involves instant messaging and SMS. In order to accomplish this, the client
application needs to have access to the chat server for instantaneous messaging, to the core server
(where the enterprise beans are located) for information about profiles from the database, and
finally to the SMS service provider for short message services through mobile telephone networks.
Figure 16: Component Diagram of the communication system

51
2. Deployment Diagram
A deployment diagram shows the run-time structure/architecture of the system. It shows
the structure of the computer network that will host the software, and how they are mapped to the
software elements. It has the highest level of abstraction. The table below presents and explain the
different notations of a deployment diagram.
Table 15: Description of Deployment Diagrams
Name
Diagrammatical
representation
Description
Node
A node is either a hardware or
software component
Artifact
An artifact is a product of
software development process.
Example: source file, text report
etc.
Association
In this context, an association
represents a communication path
between nodes.
Component
It represents a modular part of a
system that encapsulate it content
and whose manifestation is
replaceable within it
environment.

52
Deployment Diagram of the Corporate Communication System
Figure 17: Deployment diagram of the corporate communication system

53
V. ANALYSIS
State Machine Diagram
A state machine diagram models the behavior of a single object, specifying the sequence
of events that an object goes through during it life time in respond to an event.
Table 16: Explanatory table of State Machine Diagrams
Name Description Representation
States A sate models a situation during which
certain invariant conditions hold.
Initial State It represents a default vertex that is a
source for a single transition to the default
state of a composite state.
Final state A special kind of state specifying that the
enclosing region is complete.
Transition A transition is a direct relation between a
source vertex and a target vertex.
Join It permits to merge several transitions
emanating from source vertices from
different orthogonal region.

54
Life cycle of an instant message
An instant message goes through different states as it is being manipulated by users and by
the server. There are as follows
Figure 18: State machine diagram of “Instant Message”

55
CONCLUSION
At the end of the analysis where we had to do a detail analysis and bring out the boundaries
of our project, the description of the use case helps us to specify in details the needs of the customer.
It also permitted us to understand the mechanism of our system. This is the information necessary
to elaborate the conception document of our project.

56
PART V: CONCEPTION PHASE

57
Preamble
In this section, we are going to study in details our project, it is necessary to engage our
self in this phase because it is very crucial for the realization of a project. Our future software
will depend on this phase and it will also permit us to develop an application that will be fast and
ergonomic.
Contents
INTRODUCTION
I. Presentation of The Conception Phase
II. Generic Conception
III. Preliminary Conception
IV. Detailed Conception
CONCLUSION

58
INTRODUCTION
The conception of a software is an art that necessitate experience, and it consist in
translating the needs required, by specifying how the software can satisfy them before going to the
realization. This is why 2TUP provides a conception phase before the realization phase simply
because it is not easy to implement without realizing. Here, it will be necessary for us to present
the technical diagrams that will permit us to understand how the software is going to react.

59
I. PRESENTATION OF THE CONCEPTION PHASE
The conception has many objectives. It is important to say here that it will help us to present the
structure of the future software. At the second hand, it will help us to:
Bring out the functionalities of the system;
Specify in details, each module in order to facilitated the realization at the same time
observing how the application will function during it manipulation;
Prepare our self to move to the technical document.
In this phase, we are going to present the:
deployment diagram;
Class diagram.
II. DETAILED CONCEPTION
A. Sequence Diagram
A sequence diagram in UML is a diagram that represents objects as lifelines running down
through the page and messages that they exchange as arrows. A message sent from an object to
another causes an action by that object either on itself or on another object on or out of the diagram.
The following are some basic components of a sequence diagram:
➢ Life lines
A life line represents an individual participant in a sequence diagram. A sequence diagram
usually has a rectangle containing the user name as shown in the diagram below.
➢ Message
A message defines a particular communication between life lines of an interaction.
Message are displayed as arrows. Message can be complete, lost or found, synchronous and
asynchronous, call or signal.
• A synchronous message is a kind of message that represents an invocation
of target life line. It is denoted by the solid arrowhead.
• An asynchronous message denoted by the line arrow head.

60
• Self-message represents a recursive call of operation or one method
calling another method belonging to the same object
➢ Combined fragment
A combined fragment is one or more processing sequence enclosed in a frame and executed
under specific named circumstances. The fragments available are:
• Alternative fragment denoted as “Alt”;
• The optional fragment denoted as “Opt”;
• Break fragment models an alternative sequence of events that is processed
instead of the whole of the rest of the diagram.
• Parallel fragment (denoted “par”) models concurrent processing.
• Weak sequencing fragment (denoted “Seq”) encloses a number of
sequences for which all the messages must be processed in a preceding
segment before the following segment can start, but which does not
impose any sequencing within a segment on messages that don’t share a
lifeline.
• Strict sequencing fragment (denoted “strict”) encloses a series of
messages which must be processed in the given order.
The following diagram represents a sequence diagram:

61
Figure 19: Representation of sequence diagrams
The following are sequence diagrams of the Corporate Communication System.

62
1. Sequence Diagram for messaging
Figure 20: Sequence Diagram for messaging

63
2. Sequence diagram of authenticate
Figure 21: Sequence diagram of “authenticate”

64
3. Sequence diagram of configure sending rights
Figure 22: Sequence diagram of “configure sending rights”

65
B. Class Diagram
A class diagram is the diagram that shows the building blocks of any object-oriented
system. They show a static view of the system describing what attributes and actions each element
can respectively possess and perform in the form of attributes and methods in classes. It also shows
the relations that can exist between elements in the form of associations, generalizations,
aggregations and compositions.
Class
A class in UML is represented by a rectangle divided into:
✓The name of the class starting with a capital letter. Ex: Person
✓A list of attributes of the class
➢ Public attributes are represented by “+” before the attribute name.
➢ Private attributes are represented by “-” before the attribute name.
➢ Protected attributes are represented by “#” before the attribute name.
✓A list of methods of the class.
The table below represents the different notations of a class:
Table 17: Explanation of Class diagram
Name Description Representation
Association
An association implies two models have a
relationship. These connectors may include
named roles, cardinality, direction and
constraint.
Generalization It is used to indicate inheritance.

66
Aggregation
They are used to depict elements which are
made up of smaller components.
Composition
A composition is a stronger form of
aggregation is used when components can
be added in maximum one composition at a
time. If the parent of the aggregation is
deleted, usually all of its part is deleted.
Enumeration class
A type of class that acts as a container of
enumeration literals.
Interface
An interface in UML is similar to a class
except that instead it does not have
attributes and the stereotype “<< interface
>>” on top of the name of the interface.

67
Table 18: Classes and Attributes of the System

68
Below is the class diagram of the Corporate communication system.
Figure 23: Class diagram of the Corporate communication system

69
CONCLUSION
The above diagrams clearly define and describe how the system is supposed to be built, the
different building blocks of the system and its boundaries. This information can be used developers
to build the software and deploy it in the specified physical architecture. Having done with the
analysis phase, we can now move to the realization phase

70
PART V: REALISATION PHASE

Internship report: Computerized Corporate Communication System - Conception and Realization

Internship report: Computerized Corporate Communication System - Conception and Realization

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Internship report: Computerized Corporate Communication System - Conception and Realization

Similar to Internship report: Computerized Corporate Communication System - Conception and Realization (20)

Recently uploaded

Recently uploaded (20)

Internship report: Computerized Corporate Communication System - Conception and Realization