rwanda mining rights management system
TRANSCRIPT
i
DEDICATION
This dissertation is dedicated to:
My Mather and Father,
My lovely Brothers and sisters,
All my community members,
All my family members,
ii
DECLARATION
I, RUBAMBURA August hereby declare that the project report entitled
“RWANDA MINING RIGHTS MANAGEMENT SYSTEM” submitted in
partial fulfillment of the requirement for the award of Bachelor’s degree in
Information Systems and Management is a record of bonafide project work carried
out by myself under the guidance of Mr. Sampson KAGORORA.
I further declare that the work reported in this project has not been submitted,
either in part or in full, for the award of any other degree or diploma in this
institute or any other institute or university.
Kigali………………. ……………………
Date: ………/………/……… RUBAMBURA August
iii
INDEPENDENT INSTITUTE OF LAY ADVENTIST OF KIGALI
(INILAK)
B.P. 6392 KIGALI, Tél : 55107311/55104697
E-mail : [email protected] Website: www.inilak.ac.rw
BONAFIDE CERTIFICATE
This is to certify that the project report entitled “RWANDA MINING RIGHTS
MANAGEMENT SYSTEM” submitted by RUBAMBURA August(Reg. Num.
Kgl 01035/2010) to INDEPENDENT INSTITUTE OF LAY ADVENTISTS OF
KIGALI in partial fulfillment of the requirements for the award of Bachelor’s
degree in Information Systems and Management is a record bonafide work carried
out by him under my supervision.
SUPERVISOR HEAD OF DEPARTMENT
Mr. Sampson KAGORORA Mr. Pierre Célestin ZIRARUSHYA
On October 31, 2013 on October 31, 2013
Accredited by Ministerial Order No 002/09 of 01/04/2009 granting the definitive operating license
iv
ACKNOWLEDGEMENT
I am most grateful to my supervisor, Mr. Sampson KAGORORA for his guidance, advice,
criticism and efforts in guiding me to produce this work.
My gratitude also goes to my beloved parents, RUHIGANA Augustin and NIYIRORA
Petronilla, for their education, patient, affection, and moral support all along my education
period.
My gratitude also goes to the staff of MINIRENA for having co-operated with me and provided
me the needed information helpful to the achievement of this project.
I wish to extend my appreciation particularly to NTEZIRYAYO Florien for his material
support when I was writing this dissertation.
I also express my sincere gratitude to my nearest friends and classmates for their cooperation,
help and encouragements specially my friend INGABIRE Jacqueline for patient, affection, and
moral support.
Finally, let my thanks be extended to all teachers who participated in my education since my
childhood up to now.
May Almighty God bless you all.
Place Kigali
Date…/………/………
RUBAMBURA Augustin
……...….…………..
v
Table of Contents DEDICATION ................................................................................................................................. i
DECLARATION ............................................................................................................................ ii
BONAFIDE CERTIFICATE ......................................................................................................... iii
ACKNOWLEDGEMENT ............................................................................................................. iv
Table of Contents ............................................................................................................................ v
LIST OF FIGURE.......................................................................................................................... ix
LIST OF TABLE ............................................................................................................................ x
LIST OF ABREVIATIONS .......................................................................................................... xi
ABSTRACT ................................................................................................................................. xiii
CHAPTER 1: GENERAL INTRODUCTION ............................................................................... 1
1.1. Introduction ........................................................................................................................................ 1
1.2. Problem statement .............................................................................................................................. 1
1.3. Motivation .......................................................................................................................................... 2
1.4. Objectives .......................................................................................................................................... 2
1.5. Interest of the study ............................................................................................................................ 3
1.6. Methods and techniques ..................................................................................................................... 3
1.6.1. Techniques .................................................................................................................................. 3
1.6.2. Methodology ............................................................................................................................... 4
1.7. Scope of the study .............................................................................................................................. 5
1.8. Expected results ................................................................................................................................. 5
1.10. Organization of the study ................................................................................................................. 5
CHAPTER II: LITERATURE REVIEW ....................................................................................... 7
2.1 Introduction ......................................................................................................................................... 7
2.2 Definition of Key Terms ..................................................................................................................... 7
vi
2.3 Database concepts ............................................................................................................................. 11
CHAPTER III: ANALYSIS OF THE EXISTING SYSTEM ...................................................... 15
3.0. INTRODUCTION ........................................................................................................................... 15
3.1. Historical background of Mining activities in Rwanda ................................................................... 15
3.2. Mission and Vision .......................................................................................................................... 16
3.2.1 Mission ....................................................................................................................................... 17
3.2.2 Vision ......................................................................................................................................... 17
3.3 The organization of Existing system ................................................................................................. 18
3.4. Variation of different report for mining licenses ............................................................................. 19
3.5. Problems of existing system ............................................................................................................ 20
3.6. Proposed solution ............................................................................................................................. 21
CHAPTER 4: ANALYSIS AND DESIGN OF THE PROPOSED SYSTEM ............................ 22
4.1. Introduction ...................................................................................................................................... 22
4.2 Structured System Analysis and Design Method .............................................................................. 22
4.3 Functional Diagram .......................................................................................................................... 25
4.3.1 System main functions ............................................................................................................... 25
4.4 Context diagram ................................................................................................................................ 26
4.5 Data flow Diagram ............................................................................................................................ 27
4.5.1 Data Flow Diagrams symbols .................................................................................................... 27
4.5.2 Data flow diagram – Level 0 ...................................................................................................... 29
4.5.3 Data Flow Diagrams Level 1: Process of miner management ................................................... 29
4.5.4 Data Flow Diagrams Level 1: Process of Request management ............................................... 30
4.5.4 Data Flow Diagrams Level 1: Process of Licenses management .............................................. 30
4.6 Entity-Relationship diagram (ERD) .................................................................................................. 32
4.6.1 Entity .......................................................................................................................................... 32
vii
4.6.2 Relationship ............................................................................................................................... 32
4.6.3 Cardinality .................................................................................................................................. 33
4.6.4 Entity Relationship Diagram Chart ............................................................................................ 33
4.7. Data dictionary ................................................................................................................................. 33
4.7.1. Data dictionary: Table of company ........................................................................................... 34
4.7.2. Data dictionary: Table of Request............................................................................................. 34
4.7.3. Data dictionary: Table Mining Site ........................................................................................... 35
4.7.4. Data dictionary: Table District .................................................................................................. 35
4.7.5. Data dictionary: Table Mine ..................................................................................................... 36
4.7.6. Data dictionary: Table Mine type ............................................................................................. 36
4.7.7. Data dictionary: Table License ................................................................................................. 36
4.7.8. Data dictionary: Table License type ......................................................................................... 37
4.8 Logical Data Model .......................................................................................................................... 37
4.9 Physical Data Model ......................................................................................................................... 38
CHAPTER 5: IMPLEMENTATION OF SYSTEM..................................................................... 40
5.1 Introduction ....................................................................................................................................... 40
5.2. Development of the project .............................................................................................................. 40
5.3. Technology and tools used ............................................................................................................... 40
5.3.1. Apache ...................................................................................................................................... 40
5.3.2. PHP ........................................................................................................................................... 40
5.3.3 HTML ........................................................................................................................................ 42
5.3.4. Cascading Style Sheets (CSS) ................................................................................................... 42
5.3.5. JavaScript .................................................................................................................................. 42
5.3.6. Xampp ....................................................................................................................................... 43
5.4. Software testing ............................................................................................................................... 43
viii
5.4.1. Functional vs. Non functional testing ....................................................................................... 43
5.4.2. Testing methods ........................................................................................................................ 43
5.5. System interfaces ............................................................................................................................. 45
5.5.1. Home page ................................................................................................................................ 45
5.5.2. LOGIN PAGE ........................................................................................................................... 46
5.5.3. COMPANY REGISTRATION PAGE ..................................................................................... 46
5.5.4. Company license Request page ................................................................................................. 47
5.5.5. LICENSE DELIVERY PAGE .................................................................................................. 47
CHAPTER VI: CONCLUSION AND RECOMMENDATIONS ................................................ 49
6.0. Introduction ...................................................................................................................................... 49
6.1. The conclusion ................................................................................................................................. 49
6.2. Recommendations and suggestions for further researchers ............................................................. 49
6.2.1. Recommendations ..................................................................................................................... 49
6.2.2. Suggestions for further researchers ........................................................................................... 49
REFERENCES AND BIBLIOGRAPHY ..................................................................................... 51
APENDICE ................................................................................................................................... 53
ix
LIST OF FIGURE
Figure 1: System Development Life Cycle (SDLC) ..................................................................................... 5
Figure 2: ERD of ONLINE MINERAL ACTIVITE MONITORING SYSTEM in study of UWIMPUHWE
Clarisse/2011............................................................................................................................................... 14
Figure 3: outline of posts requested in the geology and mines section in Rwanda natural resource
development ................................................................................................................................................ 18
Figure 4: the current permit application process ......................................................................................... 19
Figure 5: The waterfall model ..................................................................................................................... 23
Figure 6: the waterfall model ...................................................................................................................... 23
Figure 7: function diagram .......................................................................................................................... 25
Figure 8: Context diagram .......................................................................................................................... 27
Figure 9 : Data flow diagram ...................................................................................................................... 29
Figure 10: Data Flow Diagrams Level 1: Process of Miner management .................................................. 30
Figure 11: Process of Request Management ............................................................................................... 30
Figure 12: Process of Licenses management ............................................................................................. 31
Figure 13: Entity Relationship Diagram chart ............................................................................................ 33
Figure 14: Physical Data Model.................................................................................................................. 39
Figure 15: Common Gateway Interface (CGI) ........................................................................................... 41
Figure 16: Home page ................................................................................................................................. 46
Figure 17: Login page ................................................................................................................................. 46
Figure 18: Company registration page ........................................................................................................ 47
Figure 19: Requesting form page ................................................................................................................ 47
Figure 20: page of license deliverance ........................................................................................................ 48
Figure 21: list of Request in process ........................................................................................................... 53
Figure 22: licences status ............................................................................................................................ 53
x
Figure 23: Sample of mining license .......................................................................................................... 54
LIST OF TABLE
Table 1: large Scale miners Licenses .......................................................................................................... 19
Table 2: Large Scale Miners Licenses2 ...................................................................................................... 20
xi
LIST OF ABREVIATIONS
CGI: Common Gateway Interface
COPIMAR: Coopérative de Promotion de l‘Industrie Minière Artisanale au Rwanda
CSS: cascading style sheet
DBMS: database management system
DF: Data flow
DFDs: Data flow diagrams
EIA: Environmental Impact Assessment
ERD: Entity-Relationship diagram
HTML: Hypertext Markup Language
HTTP: Hypertext Transfer Protocol
IBM: International Business Machines
INILAK: independent institute of lay Adventist of Kigali
IT: information Technology
MINIRENA: MINISTRY OF NATURAL RESOURCES
MySQL: structured Query Language
OGMR: RWANDA GEOLOGY AND MINES AUTHORITY
OS: Operating systems
R.M .R .M .S: Rwanda mining rights management system
RDBMS: Relational database management Systems
REDEMI: Régie d'Exploitation et de Développement des Mines
SOMIRWA: Sociéte minière au Rwanda
xii
SQL Server: structured Query Language sever
SRO-EA: sub-regional office for Eastern Africa
SSADM: Structured System Analysis and Design Method
xiii
ABSTRACT
This research was conducted in order to solve the problems covering Rwandan mining industry
in its management system.
The purpose of this project is to implement Rwanda mining Right Management System
(R.M.R.M.S) for Mining sector in Rwanda which include in the Rwandan Geology and Mines
Department, the mining sector regulatory body within the Ministry of Natural Resources
(MINIRENA).
The main objective of this project is to implement a web based application that provides the
online request for mining licenses to the mining companies (miner) who have register to the
system from different location of Rwanda.
This system will efficiently and effectively help all company make their business in mining
sector to request for mining licenses provided by MINIREMA through different department of
Rwandan government which are local government and central government. The achievement of
this objective is described in the current project within its phases such as requirement gathering,
analysis, design, and implementation and testing.
This project gives definition and theoretical concept of a web based application; provides both
theoretical and practical conception of Rwanda Mining Right Management System
(R.M.R.M.S).
In the analysis and design of the software, we used the Structured System Analysis and design
(SSADM). To implementing the software, PHP technology was used, and MYSQL served us as
RDBMS. The software developed was found that it meets all mentioned problems. Hence we
found that our objectives were successful achieved.
1
CHAPTER 1: GENERAL INTRODUCTION
1.1. Introduction
Nowadays, Information Technology plays major roles in the development of both developed and
developing countries. It had a great impact in all aspect of life and the global economy is
currently undergoing fundamental transformation.
Many countries, include Rwanda, IT is one of the factors contributing to the overall economy of
the nation. It helps organizations and institutions to control their activities easily when they are
computerized. Among the facilities of the information technology include the ability to share
resources, information, files, etc.
These facilities could not be easily achieved in the 19th
century, where IT was not developed, and
many organizations and institutions were still using manual system to control their activities.
This manual system led to many problems as the difficulty in sharing resources among
organization’s members and therefore time consuming to search important information.
Rwandans are rightly proud of their cultural roots and the government will ensure that it takes
advantage of this heritage in all facets of the development process. However, for this
development process to be a success, Rwanda must embrace the future and exploit innovations in
Science and technology to complement its cultural strengths.
In Rwanda, the rate of adoption and integration of science and technology in socio-economic life
is very low and the shortage of technically qualified professionals is visible at all levels. From
now until 2020, Rwanda projects to have adequate, highly skilled scientists and technicians to
satisfy the needs of the national economy. There is a need to generate, disseminate and acquire
1
Scientific skills as well as technological innovations, in addition to integrating them into the
social and economic development drive, detailed above
Now to days with evolution of Information Technology, many sectors can benefit from this
technology as it allows different activities done manually to be automated which reduces the
gaps of manual system.
1.2. Problem statement
The mining industry is currently in a state of transition across two axes: moving from a publicly-
run to a private industry; and moving from a regional trading industry to a local extraction and
exporting industry. The focus of this policy is on cementing and hastening this transition,
building on recent progress. Recent progress includes the updating of the regulatory framework
to keep pace with the rapid privatization of mining sector since 2004, through the publication of
the new Mining Law. This Law forms a solid basis for the regulation of the mining industry and
will be effectuated by a number of Ministerial Orders currently being formulated. However,
many challenges to extraction remain, including difficulties accessing finance, dealing with taxes
and coping with price risks. Further still, there is a general dearth of skilled mine engineers,
geologists and metallurgists in Rwanda, meaning that companies have to import skilled staff.
These gaps are being addressed with efforts to train young mining scientists, but this will take
time. The knowledge of reserves also remains a major challenge, but one that can be addressed
by effective clarification and then implementation of the mining license requirements contained
in the new mining law together with an effort to gather all existing information on Rwanda’s
mining sector from international sources. In order to make satiability of activity improved by
change of new mining Low, the company or cooperative can have the same licenses on different
site mining make disorder in control of license. Those make the license duplication and make
long time in waiting for new license request. Post-extraction value addition to minerals also
suffers from a number of challenges, but especially the relative high cost of energy. Efforts to
develop processed quarry products will face the same issue, but do have the potential to be
competitive against existing imports. The problems like request of the mining license, reduction
of waiting time, complication of knowing delivery date and expired date of those licenses and
managing site mining are difficult to manage its.
2
Due to those problems, how can design and implement software that will manage those problems
mentioned above.
1.3. Motivation
The choice of this project is not done by default. It results from the interest we have in the
development of our country. Especially when considering the importance of mining excavation
for exploiter mining and when finding that the current management of exploitation of mining site
and getting license certificate is manual, which presents many problems, we engage to contribute
in developing the adequate system capable of serving the corporate clients quickly and
effectively in order to resolve problem of additional information, granting, Notice of renewal,
quarterly returns.
1.4. Objectives
The objectives of this project are categorized into two main categories: General objectives and
Specific objectives.
1.4.1. Specific objectives
Here, the aim is to analyze the current system used to facilitate the company or cooperative
(Miners) request for mining licenses, to make easy for checking expiration(checking remanding
days) of their licenses and to come up with a dynamic web based application system that will
assist administrator to save information for long time. There are numerous organizations actively
involved in processing, managing and monitoring mining licenses.
1.4.2. General objectives
This is aimed at the following objectives:
To facilitate people who have intention of apply for mining licenses.
To create the spirit of online activities.
To create user-friendly web interface to allow the users to interact with the system.
To create a centralized database.
To generate various reports.
3
1.5. Interest of the study
1.5.1. Personal interest
After this project will be finished, it will be submitted to the academic administration and it will
be considered as a partial fulfillment of the requirements for the award of Bachelor’s Degree in
Information Systems and Management at Independent Institute of Lay Adventists of Kigali
(INILAK).
1.5.2. Academic interest
At the end of academic formation, every student who is about to end his academic studies must
prepare a Scientific research work that complete the theoretical formation received during his/her
studies. My work will be used as a tool to help the ulterior students who want to thrive in the
same sense of my project.
1.5.3. Public interest
After the software is completed, the public, especially the miners will benefit from it as:
It will serve them effectively and timely.
The time taken by making manual computations of operations which are numerous and
too complex will be reduced.
Overcharging or less of public funds will be avoided
Transport fees for miner will be reduced.
1.6. Methods and techniques
1.6.1. Techniques
1.6.1.1. Observation
This technique will be used to observe how the current system is. It means how miners apply for
licenses, how company register and fill form for mining licenses and what they will be received.
1.6.1.2. Documentation
This technique helped us to go through all the data in several works relating to our topic in order
to pull the necessary information. Several books, booklets, dissertation, government report,
4
gazette, websites and notes of courses learned from class and newspaper were consulted as well
as web graphic which helped us to make the research on the internet and to consult different sites
related to this dissertation.
1.6.1.3. Interview
This technique helped us to interact with both the agencies’ staff who provide the good life
condition for miners and the miners who are the beneficiary of the system, in order to interview
them.
1.6.2. Methodology
General software engineering methodology is used to accomplish this research project, it is
divided into following:
Observing how process of providing mining license delivery in the current system. Discussion
with the agencies which provide the mining licenses, and some miners who had those mining
licenses while collecting information on the current system. Find out and analyze the current
format which is used in those agencies, identify the problems faced in the process of finding the
institution to help Miners. Waterfall model approach is applied for this project development
following its fives phases in System Development Life Cycle (SDLC).
System Development Life Cycle (SDLC)
5
Figure 1: System Development Life Cycle (SDLC)
1.7. Scope of the study
This system will be limited to:
The Miner requests for mining licenses
The storing of Miners data storing
Regulation for expiration time of mining licenses
The miners contribution management
This piece of research will not talk about the tools used in mining licenses payment and
Geographic Information Systems (GIS) for mining site map.
1.8. Expected results
At the end of this work, the manual system will replaced by computerized information system,
the project will minimize the time used by old system which and the information will be secure.
This project will provide the reporting features about mining licenses activities in Rwanda and
the services delivered to Miners will be good.
1.10. Organization of the study
The plan of this project is divided into six chapters, and it is outlined as follows:
CHAPTER 1: GENERAL INTRODUCTION
This chapter especially presents the dissertation, the problem statement, the objectives and the
motivation.
CHAPTER 2: LITERATURE REVIEW
In this Chapter some key concepts related to the dissertation will be explained, and it will be
focused on some relevant theories and concepts upon which the development process of this
dissertation is based.
CHAPTER 3: ANALYSIS OF EXISTING SYSTEM
6
It is an interested part. The existing system will be analyzed
CHAPTER 4: ANALYSIS AND DESIGN OF A NEW SYSTEM
This chapter will be concentrated on the analysis and designing of the new system
CHAPTER 5: IMPLEMENTATION OF A NEW SYSTEM.
Here, the new system will be tested and implemented
CHAPTER 6: CONCLUSION AND RECOMMENDATIONS
In this chapter, the project will be concluded and some recommendations related to this project
will be given.
7
CHAPTER II: LITERATURE REVIEW
2.1 Introduction
In order to facilitate readers to understand the rest of the project’s content, the present chapter
clearly defines some important key terms used to develop this project. It describes also this
Project compare to others done by other researchers in the same field. The purpose is to present
the similarities as well as the differences among both projects compared. Finally, it shows the
personal contribution to the research conducted.
2.2 Definition of Key Terms
2.2.1 Rwanda
A landlocked country in central Africa, to the north of Burundi and the south of Uganda;
population 10,746,300 (est. 2009); official languages, Rwanda (a Bantu language), English and
French. Capital is Kigali. Official name Rwandese Republic
2.2.2 Mining
Excavation of materials from the Earth's crust, including those of organic origin, such as coal and
petroleum. Modern mining is costly and complicated. First, a mineral vein that can likely
produce enough of the desired substance to justify the cost of extraction must be located
[www.merriam-webster.com/dictionary/mining]. Then the size of the vein or deposit is determined, and mining
engineers decide the best way to mine it. Most of the world's yearly mineral production is
extracted by surface mining, which includes open-pit mining, strip mining, and quarrying. For
ore bodies that lie a considerable distance below the surface, underground mining must be
considered. In both techniques, excavating and extracting mineral substances involve costly
combinations of drilling, blasting, hoisting, and hauling, as well as measures for health and
safety and reduction of environmental impact.
2.2.3 Rights
Justified, recognized, and protected (violation of which is unlawful) claim on, or interest in,
specific tangible or intangible property [www.businessdictionary.com/definition/right.html].
A security giving stockholders entitlement to purchase new shares issued by the corporation at a
predetermined price (normally at a discount to the current market price) in proportion to the
8
number of shares already owned. Rights are issued only for a short period of time, after which
they expire.
2.2.4. Mining Rights
A right to enter upon and occupy a specific piece of ground for the purpose of working it, either
by underground excavations or open workings, to obtain the mineral ores which may be
deposited therein [www.answers.com/topic/mining-right]
also known as mineral right.
A landowner's right to receive a portion of the profits of any minerals that are extracted from the
land. Mineral rights apply to all types of resources, such as oil and gas, ores and metals or other
raw materials. The term mineral rights describe the numerous beneficial ways the owner can
profit from the resources in the ground.
2.2.5 Management
Management is an individual or a group of individuals that accept responsibilities to run an
organization. They can Plan, Organize, Direct and Control all the essential activities of the
organization. Management does not do the work themselves. They motivate others to do the
work and co-ordinate (i.e. bring together) all the work for achieving the objectives of the
organization (Peter Drucker in his book "The Principles of Management"(2011)),
2.2.6. Miner
Miner is a person who extracts ore, coal, or other minerals from the earth through mining. There
are two conceptions as to what this includes. In its narrowest understanding, "miners" are solely
those persons who work at the face cutting, blasting, or otherwise working and removing the
rock. In the broader understanding, a "miner" also includes any other laborer working within a
mine, not just working the rock itself [http://en.wikipedia.org/wiki/Miner]
.
2.2.7. Licenses
The verb license or grant license means to give permission. The noun license (American English)
refers to that permission as well as to the document recording that permission.
9
A license may be granted by a party ("licensor") to another party ("licensee") as an element of an
agreement between those parties. A shorthand definition of a license is "an authorization (by the
licensor) to use the licensed material (by the licensee)."[https://en.wikipedia.org/wiki/License]
In particular, a license may be issued by authorities, to allow an activity that would otherwise be
forbidden. It may require paying a fee and/or proving a capability. The requirement may also
serve to keep the authorities informed on a type of activity, and to give them the opportunity to
set conditions and limitations.
A licensor may grant a license under intellectual property laws to authorize a use (such as
copying software or using a patented invention to a licensee, sparing the licensee from a claim of
infringement brought by the licensor. A license under intellectual property commonly has several
components beyond the grant itself, including a term, territory, renewal provisions, and other
limitations deemed vital to the licensor.
2.2.8. System
A set of connected things or parts forming a complex whole, in particular.
A set of things working together as parts of a mechanism or an interconnecting network
E.g.1. a computer system refers to the hardware and software components that run a computer or
computers.
2.2.9 Information System
Information system is a set of people, data, and procedures that work together to achieve the
common goal of information management [http://en.wikipedia.org/wiki/Information_system]
. People, data and
procedures are the minimum components required in the information system, but most today
information systems include computer hardware and software.
Information system allows information to be generated, processed and distributed efficiently and
timely. Because of accurate and timely information allows problem solving and better decision
making, this enable successful goal attainment to an organization.
2.2.10. Information Technology
10
(Martin Wainrght E et al. 1993,p.91), define information technology as a broad one
encompassing all forms of technologies involved in capturing, manipulating, communicating,
presenting and using data i.e data transformed into information.
But (Henry C Lucas 2001, p.11) stated that information technology refers to all form of
technology applied to processing, storing, and transmitting information in electronic form.
2.2.11. Management information system (MIS)
Management Information System (MIS) is a computer system, usually based on mainframe or
microcomputer designed to provide management personnel with up-to-date information on
organization’s performance[en.wikipedia.org/wiki/Management_information_system]
; ex: inventor and sales .These
systems output information in a form that is useable by managers at all levels of the organization
:strategic , tactical and operational.
2.2.12. Website
A website is a set of interconnected web pages, usually including a homepage, generally located
on the same server, and prepared and maintained as a collection of information by a Person,
group, or organization.
a) Static web site
A static web site is a web page that is delivered to the user exactly as stored, in contrast to
dynamic web pages which are generated by a web application. A static web page displays the
same information for all users, from all contexts, subject to modern capabilities of a web server
to negotiate content-type or language of the document where such versions are available and the
server is configured to do so. Static web pages are often HTML documents stored as files in the
file system and made available by the web server over HTTP.
b) Dynamic web site
A dynamic website is one that changes or customizes itself frequently and automatically, based
on certain criteria. Dynamic websites can have two types of dynamic activity: Code and Content.
Dynamic code is invisible or behind the scenes and dynamic content is visible or fully displayed.
11
2.2.13. Information
Information can be defined as data converted into something valuable and usable for certain user.
2.2.14. Software
Computer software, or just software, is a collection of computer programs and related data that
provide the instructions for telling a computer what to do and how to do it. In other words,
software is a conceptual entity which is a set of computer programs, procedures, and associated
documentation concerned with the operation of a data processing system. We can also say
software refers to one or more computer programs and data held in the storage of the computer
for some purposes. In other words software is a set of programs, procedures, algorithms and its
documentation.
2.3 Database concepts
2.3.1 Introduction
To keep records, is the most important part of every business. We need to keep records of
customers, orders, reports, etc for future reference. To keep all the data separately is quite hard
[en.wikipedia.org/wiki/Database_management_system]. In case records are needed on particular customers for
example, the manual search is applied which is not reliable process. So, these data needed to be
kept in the safety place for faster access. And one of the most important storage of data is the
database.
2.3.2 Definition
A database is a collection of related tables. It can also include other objects, such as queries,
forms, and reports. The structure of a database is the relationships between its tables.
2.3.3 Description
We need three things to design a database:
Table,
Rows
12
Columns
2.3.4 Database Management System (DBMS)
A database management system (DBMS) is the software that allows a computer to perform
database functions of storing, retrieving, adding, deleting and modifying data.
Relational database management systems (RDBMS) implement the relational model of tables
and relationships.
Examples:
Microsoft Access, MySQL, Microsoft SQL Server, and Oracle are all examples of database
management systems.
2.3.5 Table
A table is one of the most important ingredients to design the database. A table is a collection of
related records. For example Site_minig table, location table, miner table, etc.
A record is the collection of values for all the fields pertaining to one entity: i.e. miner,
Site_minig, location.
2.3.6 Rows
A table contains rows: Rows is a collection of instance of one thing, such as the information of
one student. Example: miner_id, first name, last_name, address, telephone, e-mail, etc.
2.3.7 Columns
A table contains the columns: Columns contains all the information of a single type. Each
column in a table is a category of information referred to as a field.
2.3.8 Field
A field is an area (within a record) reserved for a specific piece of data. Examples: miner_id,
miner name, and miner_lastname in the miner table.
2.3.9 Comparative Study on Reviews
13
Under this section, we describe the relevant project consulted done by other researcher in the
same field. Here we focus on showing the similarities as well as the differences among both
projects compared. In designing and implementing our project, we used to consult the project
done by “UWIMPUHWE Clarisse” ONLINE MINERAL ACTIVITE MONITORING
SYSTEM. Case study RWANDA GEOLOGY AND MINES AUTHORITY (OGMR)” which is
realized in 2011 supervised by Mr. MASABO Emmanuel.
2.3.10 Similarities between both projects compared
Our project and the project compared have many similarities:
Both projects focus on the management of Rwanda mining sector. They used PHP as technology,
MYSQL as RDBMS (Relational Database Management System). PhpMyAdmin was used for
both projects as an interface for the administration of MYSQL database.
2.3.11 Difference between both projects compared.
Although both projects have many similarities, they have also many differences as follows:
Both projects are developed with different scope. The scope of the project consulted is limited to
the movement of mineral from cooperatives that are licensed in buying and selling mineral in
Rwanda whereas our project’s scope is limited to mining licenses management, The requests for
mining licenses, the storing of Miners data storing, regulation for expiration time of mining
licenses and miners contribution management, the mining monitoring and our project also allow
the system manager to rapport with database system. Our project also categorized the mining
licenses into categories based on times of licenses.
14
ProvinceId
ProvinceNa
me
MineralId
MineralNa
me
DistrictId
DistrictNa
me
SectorId
SectorNam
e
PotId
PotNam
e
Telepho
ne
Exportatio
nID
Date
Quality
Tag
Productin
Id
Date
Quality
Tag
UserId
Fname
Lname
Password
Sex
Telephone
Processing
Id
Date
Quality
Tag
Coperativeid
CoperativeNa
me
Telephone
Has
get
HasHas
get
get
Getget
Province
District
Mineral
Processing
Production
Sector
Exportation
OGMRUSERCoperative
Pot Has
n
1n
n
1
1
1
n
1
1
nn
1
n
1
1
n
n
Figure 2: ERD of ONLINE MINERAL ACTIVITE MONITORING SYSTEM in study of UWIMPUHWE Clarisse/2011
15
CHAPTER III: ANALYSIS OF THE EXISTING SYSTEM
3.0. INTRODUCTION
This chapter describes the history and the background of Mining activities in Rwanda, the Vision
and the Missions for distribution of mining licenses, the functioning of the existing system, the
disadvantages of the existing system and the solutions proposed in the new system.
3.1. Historical background of Mining activities in Rwanda
Since 1930, Rwanda invested in Mining Industry. The main concern was to address the growth
of country economy and to increase the income among Rwandan population.
The underground part of Rwanda contains important minerals such as cassiterite, coltan, wolfram
and gold. Additionally, Rwanda has other construction materials such as amphibilite, granites
and quartzite, volcanic rocks, clay, sand and gravel. Minerals are among activities that contribute
to the country development.
For the past seven years, the Rwandan economy has benefited enormously from the mining
industry. Revenues have increased from $10 million USD in 2003 to $96.4 USD in 2010 and the
year 2011 is projected to generate up to $ 100 USD. Since 2006, mineral productivity has been
increasing due to the fact that the Government of Rwanda privatized the mining concessions and
encourages the use of modern techniques as a way to increase productivity.
Today a growing number of people are joining Mining Sector and many jobs have been created
locally. On one side, Mining contributes a lot in the Economic growth and on another side it can
also contributes to the Environment destruction. In order to define ways of adding values to our
environment and protection of people ,before starting activities that would result in
environmental degradation such as Mining investors should work under a basic EIA
(Environmental Impact Assessment). A procedure that ensures that environmental consequences
of project are identified and assessed before Authorization is given.
16
3.2. Mission and Vision
The Rwandan mining industry is currently in a state of transition. It has recently transformed
from a publicly-run to a private industry and at the same time is moving from a regional trading
industry to a local extraction and exporting industry.
Recent progress includes the updating of the regulatory framework to keep pace with the rapid
privatization of mining sector since 2004, through the publication of the new Mining Law. This
Law forms a solid basis for the regulation of the mining industry and will be made effective by a
number of Ministerial Orders currently being formulated.
Nevertheless, for the minerals sector, many challenges to extraction remain, including difficulties
accessing finance, dealing with taxes and coping with price risks. Further still, there is a general
dearth of skilled mine engineers, geologists and metallurgists in Rwanda, meaning that
companies have to import skilled staff.
These gaps are being addressed with efforts to train young mining scientists, but this will take
time. The knowledge of reserves also remains a major challenge, but one that can be addressed
by effective clarification and then implementation of the license requirements contained in the
new mining law together with an effort to gather all existing information on Rwanda's mining
sector from international sources. Post-extraction value addition to minerals also suffers from a
number of challenges, but especially the relative high cost of energy.
Efforts to develop processed quarry products will face the same issue, but do have the potential
to be competitive against existing imports
The Mining Sector has a range of Objectives among others are:
Strengthen and enabling the legal, regulatory and institutional environment
Develop competitive investment and fiscal policies for mining
Improving mining sector knowledge, skills and use of best practices
Raise productivity and discover new mines
17
Diversify into new products and increase value addition
3.2.1 Mission
The overall mission of OGMR is “to develop geology and mines sector to contribute optimally to
an increase in national revenue through proper management of mineral resources and with the
capacity to monitor natural hazards”.
To implement its mission, the OGMR has adopted a strategic plan covering the period 2010 –
2013, articulated around three specific objectives. For each objective, strategies (11 in total) and
expected results were elaborated. An action plan quantified and detailed every year, implications
in terms of human resources, and co-ordination with other players in the sector, cross sector
issues, and a monitoring/evaluation system form an integral part of this Strategic Plan.
3.2.2 Vision
The vision for OGMR envisages ‘a modern, dynamic and a competitive institution providing
very high quality services for promotion of sustainable mining for economic growth and
development.
18
OUTLINE OF POSTS REQUIRED IN THE GEOLOGY AND MINES SECTION IN RWANDA NATURAL RESOURCE DEVELOPMENT
- Legal Officer - Administrative
assistant/Public relations - Planning officer
Support Services in Mining Business
development
Regulation and
inspection
Research and Data
1 Geology Division 2 Cartography
(Geologic map making and publication)
3 Geophysics Division
4 Petrography and mineralogy Division
1. Supervision of large-scale mines
2. Supervision of small-scale mines and quarries
3. Inspection of mining activities
1 Development of Small and Medium Mining
And quarry Enterprises
2 Contracting in mineral Investment and trading 3 Mining analyst
Figure 3: outline of posts requested in the geology and mines section in Rwanda natural resource development
3.3 The organization of Existing system
The newly published Mining law form a solid basis for the regulation of the mining industry.
This final Green Paper will be transformed to a White paper for Cabinet approval and will
inform the Ministerial Orders and hence will provide the detailed framework for the
implementation of the law.
One area that the Ministerial Orders will seek to change is the permit application process. The
current permit application process is complicated and bureaucratic, see the figure below
19
Figure 4: the current permit application process
3.4. Variation of different report for mining licenses
Large Scale Miners Licenses
S/N Name OF INVESTOR
Name of the
Representative Address Location of site Name of mineral (s) Type of the permit No. Issued date Expiry date
1 BAY VIEW GROUP Anthony Ehlers
P.O BOX 7391, Tel:
+250
788300952/0788303314 Bisesero /Karongi Cassiterite,Wolfram special permit 84/16.03/05 15/06/2007 14/06/2011
2
B.C.K ( Bocca Costa
Kanyandekwe )SARL Luigi Costa
P.O Box 6415 Kigali,
Tel:+250788302462
Burera, gakenke & Rulindo
District (Nyamugari)
Gold, Cassetilite,
Wolfram & Colombo-
Tentalite Prospection permit 0026/16.03/04.05 1/9/2009 31/08/2011
3
CARACAL Gold Rwanda
Rwanda Marcel F. DeGuire B.P 980 Kigali
South west & North Rwanda
/Rusizi, Gicumbi
Gold research &
exploration Research license 0021/16.03/04.05 1/9/2009 31/08/2013
4
China Xiamen Tungsten
Corporation Zhuang Zhigang
tel:0783593889/0086-
592-6081228
Gahengerri Mineral
Concession/Rwamagana Tungsten
EXPLOITATION
Permit 0035/16.03/04.05 21/10/2009 20/10/2013
Table 1: large Scale miners Licenses
special permits of large miners
prospecting permits of large miners
20
research permits of large miners
exploitation permits of large miners
Large Scale Miners LicensesS/N Name OF INVESTOR
Name of the
Representative Address
Location of
site District
Name of mineral
(s)
Type of the
permit No. Issued date Expiry date
1
BAY VIEW
GROUP Anthony Ehlers
P.O BOX 7391, Tel:
+250
788300952/0788303
314
Bisesero
/Karongi Karongi
Exploration &
Research special permit 84/16.03/05 15/06/2007 14/06/2011
2
B.C.K ( Bocca
Costa
Kanyandekwe
)SARL Luigi Costa
P.O Box 6415 Kigali,
Tel:+250788302462 Nyaruguru Nyaruguru
Gold, Cassetilite,
Wolfram &
Colombo-Tentalite Prospection permit0026/16.03/04.05 1/9/2009 31/08/2011
3
CARACAL Gold
Rwanda Rwanda
Marcel F.
DeGuire B.P 980 Kigali
South west &
North Rwanda
/Rusizi,
Gicumbi Gold
Research
license 0021/16.03/04.05 1/9/2009 31/08/2013
Table 2: Large Scale Miners Licenses2
3.5. Problems of existing system
Having analyzed the Rwanda's mining industry and seeing the activities of the existing system,
we found problems with the entire system management especially in license management in
Rwanda's mining industry.
These problems are:
Inefficient security of data
Report generation very difficult because data comes from different files which stored in
different places consuming.
Taking long time, high cost and lengthy for getting mining license
Difficult to control the mining company and their licenses.
21
3.6. Proposed solution
After analyzing the above problems, the decision is to design a computerized management
Rwanda's mining industry, which will help to: Store company mining (miners)’s data online and
easy to find but hard to change without permission from the program administrator, from online
system it will be easy to generate the required reports on time, Ensure data security with
permission to access the program menus. The miner will be able to request for mining licenses
on line and they will get response online and company activities for licenses will be done online.
It will also reduce lose of time and cost of circulation for requesting licenses.
22
CHAPTER 4: ANALYSIS AND DESIGN OF THE PROPOSED SYSTEM
4.1. Introduction
After analyzing the existing system in the previous chapter, it is the time now to design the
proposed system which overcomes most of the problems encountered in the existing one.
The present chapter is dedicated to the design of the proposed system. We shall explain the
SSADM (Structured System Analysis and Design Method) which is a systems approach to the
analysis and design of information systems. We shall also describe various diagrams as well as
various models which were constructed in order to achieve the overall objectives. These include:
functional diagrams, Context diagram, data flow diagrams, entity relationship diagram, data
dictionary, logical data model, and physical data model.
4.2 Structured System Analysis and Design Method
4.2.0 Introduction
SSADM concentrates on the analysis and design phase of the Waterfall Model of the Systems
Development lifecycle, as shown in the following diagram:
23
Figure 5: The waterfall model
SSADM stands for Structured Systems Analysis and Design Method and it is the method of
designing and examining information systems that was developed in the early 80’s in the United
Kingdom. SSADM specifies exactly the flows and tasks of a development project and produces a
detailed documentation of the project. SSADM sticks to the traditional waterfall model, which
allows review of each stage but requires its accomplishment before the next one can begin.
4.2.1 Waterfall model
Figure 6: the waterfall model
4.2.2. Definition of waterfall model
24
The waterfall model is the most common and classical of life cycle models. It is also referred to
as linear- sequential life cycle model.
4.2.3 Requirement Analysis
This is the first stage which is the most important because it involves gathering information
about the customer needs and defining, in the clearest possible terms, the problem that the
product is expected to solve.
4.2.4 Design
This stage consists of defining the hardware and software architecture, components, modules,
interfaces, and data to satisfy specified requirements.
4.2.5 Implementation
This stage consists of actually constructing the product as per the design specification(s)
developed in the previous stage.
4.2.6 Verification
In this stage, both individual components and the integrated whole are methodically verified to
ensure that they are error-free and fully meet the requirements outlined in the first stage.
4.2.7 Maintenance
This stage occurs after installation, and involves making modification to the system or an
individual component to alter attributes or improve performance.
4.2.8 Advantages of waterfall model
It is simple and easy to use
It is easy to manage due to the rigidity of the model. Each phase has specific deliverables
and review process.
Phases are processed and completed one at a time
It works well for small projects where requirements are very well understood Functional
Diagram.
25
4.3 Functional Diagram
The functional diagram is used to show the system’s functions that will be constructed and the
implementation process of data diagram. This function diagram only shows what to do not how
to do.
RWANDA MINING RIGHT MANAGEMENT
SYSTEM(RMRMS)
MINER
MANAGEMENTREQUEST
MANAGEMENT
LICENSE
MANAGEMENTREPPORT
Search
Request
Update
Reque
Add request
Search miner
Record
Update
License
Search
license
Record
License
Update miner Update Miner
Figure 7: function diagram
4.3.1 System main functions
As seen above, the main functions of the proposed system are: Users management, miner
management, Licenses management, Delivering management and reports. The description of
each one is explained below:
4.3.1.1. Miner management
This function deals with the management of Miner. Its main sub functions are: Record as new
Miner in the system; search Miner which searches for Miner details, and update miner which
saved in database.
4.3.1.2. Request management
This function is about the management of request. Its main sub functions are: add new request,
Search request, and update request.
26
4.3.1.3. License management
This function is about the response for management of licenses. Under this function, the system
has the following operations: Record licenses, search and update licenses also search miner.
4.3.1.4. Reports
This function shows the main reports of the system. These include the following:
All request for mining licenses
Rejected requests for mining licenses
Accepted requests for mining licenses.
Request for district
Request for variation of data
Periodic mining request.
Periodic approved licenses.
4.4 Context diagram
The context diagram is a diagram that represents the actors outside a system that could interact
with that system. This diagram is the highest level view of a system. The diagram consists of
rectangle representing the system boundary, the external entities interacting with the system and
the data which flows into and out of the system. The objective of a system context diagram is to
focus attention on external factors and events that should be considered in developing a complete
set of system requirements and constraints.
27
RWANDA MINING RIGHT MANAGEMENT
SYSTEM
ADMINISTRATIONDISTRICT
Check request
Approve /disapprove
request
Approve/disapprove
request
MINISTER
MINER
View Request
Register
Accept/refuse
Login
Send Request
View Request
Approve/disapprove
License delivery
Licenses update
Request Report
Report Delivery
Figure 8: Context diagram
4.5 Data flow Diagram
Data flow diagrams (DFDs) are categorized as either logical or physical. A logical DFD focuses
on the business and how the business operates. It describes the business events that take place
and the data required and produced by each event. On the other hand, a physical DFD shows
how the system will be implemented as we mentioned before.
Is also an important technique for modeling a system’s high-level detail by showing how input
data is transformed to output results through a sequence of functional transformations. DFDs
reveal relationships among and between the various components in a program or system. DFDs
consist of four major components: entities, processes, data stores and data flow.
4.5.1 Data Flow Diagrams symbols
There are four basic symbols used in data flow diagram: External entity, process, data flow, and
data store.
28
4.5.1.1 Entity
The external entity represents the actors outside the system that interacts with the system.
It is represented by the rectangle
4.5.1.2 Process
Processes are work or actions performed on incoming data flows to produce outgoing data flows.
These show data transformation or change. Data coming into a process must be "worked on" or
transformed in some way. Thus, all processes must have inputs and outputs. It is represented by
the round corner square.
4.5.1.3 Data Flow
Data flow represents the input (or output) of data to (or from) a process ("data in motion").
A DF is represented by a line, with arrowheads showing the direction of flow.
4.5.1.4 Data Stores
Data Stores are repository for data that are temporarily or permanently recorded within the
system. It is an "inventory" of data. These are common link between data and process models.
Only processes may connect with data stores. Data store are represented by Narrow opened
rectangle as follows.
29
4.5.2 Data flow diagram – Level 0
the Level 0 DFD shows how the system is divided into sub-systems (processes), each of which
deals with one or more of the data flows to or from an external agent, and which together provide
all of the functionality of the system as a whole. It also identifies internal data stores that must be
present in order for the system to perform its job, and shows the flow of data between the various
parts of the system.
Miner filesD1
Adminisatrator1
Manage user
Request fileD2
ADMIN2
Request Mangenent
Licenses filesD3
3
Management of
license
4
Report
Send Request
User detailMINER
MINISTER
Requesting for repport
Report delivery
Miner information
Request information
Store license info
Checking mine information
Checking request
information
License report
Request report
Miner report
Figure 9 : Data flow diagram
4.5.3 Data Flow Diagrams Level 1: Process of miner management
The diagram below is a child diagram of the process 1 shown in DFD level 0
30
1.1
Record new miner
1.2
Search miner
1.3
Update miner
Miner filesD2
Miner
Minister
Miner informationMiner information
Retrieve information
Store information
Figure 10: Data Flow Diagrams Level 1: Process of Miner management
4.5.4 Data Flow Diagrams Level 1: Process of Request management
The diagram below is a child diagram of process 2 shown in DFD level 0
2.1
Add request
2.2
Search request
2.3
Update request
Request filesD2
Miner
Minister
Send requestRequest information
Retrieve information
Store information
District
Admin
Figure 11: Process of Request Management
4.5.4 Data Flow Diagrams Level 1: Process of Licenses management
The diagram below is a child diagram of process 3 shown in DFD level 0
31
3.1
Add license
3.2
Search licenses
3.3
Update License
vLicense filesD2
Miner Send requestRequest information
Retrieve information
Store information
Search miner
3.3
Miner filesD1Retrieve info
Figure 12: Process of Licenses management
32
4.6 Entity-Relationship diagram (ERD)
An entity-relationship diagram is a data modeling technique that creates a graphical
representation of the entities, and the relationships between entities, within an information
system.
There are three main components of an ERD: Entity, Relationship, and cardinality
4.6.1 Entity
An entity is a person, object, place or event for which data is collected. The entity is represented
by a rectangle and labeled with a singular noun.
4.6.2 Relationship
The relationship is an interaction between the entities. A relationship may be represented by a
diamond shape, or more simply, by the line connecting the entities. In either case, verbs are used
to label the relationships.
There are three types of relationships between entities:
One-to-one (1, 1): one instance of an entity (A) is associated with one other instance of another
entity (B).
One-to-many (1, N):
One instance of an entity (A) is associated with zero, one or many instances of another entity
(B), but for one instance of entity B there is only one instance of entity A.
Many-to-many (N, N):
33
One instance of an entity (A) is associated with one, zero or many instances of another entity
(B), and one instance of entity B is associated with one, zero or many instances of entity A.
4.6.3 Cardinality
The cardinality defines the relationship between the entities in terms of numbers.
The following diagram shows an entity relationship diagram
4.6.4 Entity Relationship Diagram Chart
Figure 13: Entity Relationship Diagram chart
4.7. Data dictionary
A data dictionary, or metadata repository, as defined in the IBM (International Business
Machines) Dictionary of Computing, is a "centralized repository of information about data such
as meaning, relationships to other data, origin, usage, and format.
34
The term "data dictionary" is used by many, including myself, to denote a separate set of tables
that describes the application tables. The Data Dictionary contains such information as column
names, types, and sizes, but also descriptive information such as titles, captions, primary keys,
foreign keys, and hints to the user interface about how to display the field.
4.7.1. Data dictionary: Table of company
Attributes Types Size Constraints Description
Companyid Int 11 Primary key User
identification
CompanyName Varchar 30 Not null Company
username
E-mail Varchar 30 Not null Company E-
Telephone Varchar 10 Not null company
telephone
Name Varchar 30 Not null Company name
Address Varchar 30 Not null Company
address
Owner Varchar 30 Not null Name of the
Representative
4.7.2. Data dictionary: Table of Request
Attributes Types Size Constraints Description
Requestid Int 11 Primary key Request
identification
Letter Varchar 30 Not null Application
letter
Maps Varchar 30
requestDate Varchar 10
Adminrequest Varchar 1 Not null
35
DistrictReception Varchar 30 Foreign key
ministerReceptioin Varchar 30 Not null
Request Decision varChar 30 Not null
Minerid Int 11 Foreign Key Miner
identification
MingSite_Id Int 11 Foreign Key Mining site
identification
DistrictComment Varchar 100 Not null Comment for
District
AdminComment Varchar 100 Not null Comment for
Admin
MinisterComment Varchar 100 Not null Comment for
Minister
4.7.3. Data dictionary: Table Mining Site
Attributes Types Size Constraints Description
MiningSite_id Int 11 Primary key Site
miningidentification
Name Varchar 30 Not null Site name
District_id Int 11 Foreign key District
identification
4.7.4. Data dictionary: Table District
Attributes Types Size Constraints Description
Districtid Int 11 Primary key District
identification
Districtname Varchar 30 Not null District name
36
E-mail Varchar 30 District E-
Telephone Varchar 10 District
contact
UserName Varchar 30 Not null District
username
Password Varchar 30 Not null District
password
4.7.5. Data dictionary: Table Mine
Attributes Types Size Constraints Description
Mine_id Int 11 Primary key Site mine
identification
Name Varchar 30 Not null Mine name
4.7.6. Data dictionary: Table Mine type
Attributes Types Size Constraints Description
MineType_id Int 11 Primary key Mine type
identification
Typename Varchar 30 Not null Mine Type name
Mine_id Int 11 Foreign key Mine identification
4.7.7. Data dictionary: Table License
Attributes Types Size Constraints Description
Licenseid Int 11 Primary key License
identification
RequestId Int 11 Not null Request
identification
37
LicenseType Int 11 Not null License Type
identification
MineType_id Int 11 Not null Mine type
identification
StartDate Date Starting date of
license
EndDate Date Ending date of
licenses
4.7.8. Data dictionary: Table License type
Attributes Types Size Constraints Description
LicenseType_id Int 11 Primary key License type
identification
TypeName Varchar 30 Not null License Type name
4.8 Logical Data Model
During the design phase of the project, the logical data model is created for the scope of the
complete project. The logical data model reflects the technology to be used.
The logical data model reflects a logical data design that can be used by the developers on the
project. For an RDBMS, that means logical tables (views) and columns. Reasons for building a
logical data model
Helps common understanding of project data elements and requirements
Provides foundation for designing a database
Facilitates avoidance of data redundancy and thus prevent data & project transaction
inconsistency
Facilitates data re-use and sharing
Decreases development and maintenance time
Confirms a logical process model and helps impact analysis.
38
Below is the logical data model of the system.
REQUEST(request_id,#company_id,letter,map,#miningsite_id,#mine_id,requestDate,
adminReception,districtReception,RequestDecision,AdminComment,DistrictComment,Minister
Comment);
COMPANY(company_id,company_name,address,owner,address,telephone,email,username,pass
word);
LICENSE(license_id,#request_id,#licenseType_id,#mineType_id,startDate,endDate);
DISTRICT(district_id,districtName,telephone,email,username,password);
MININGSITE(miningSite_id,name,#district_id);
MINETYPE(mineType_id,mineTypeName,#mine_id);
LICENSETYPE(licenceType_id,typeName),
MINE(mine_id,type)
4.9 Physical Data Model
A physical data model (or database design) is a representation of a data design which takes into
account the facilities and constraints of a given database management system.
Like the logical data model, the physical data model is created during the design phase. This
modeling activity should reflect the scope of the specific release of the project. The model’s final
design will be highly dependent on the technical solution for the data warehouse.
The purpose of this model is to capture all the technical details required to produce the final
tables, and physical constructs such as indexes and table partitions.
All the functionality reflected in the logical data model should be preserved while creating the
physical data model.
39
Figure 14: Physical Data Model
40
CHAPTER 5: IMPLEMENTATION OF SYSTEM
5.1 Introduction
This chapter aims to show the interfaces with its interpretations that are used in the new system.
We also talk about experimentation, optimization, and evaluation. Before all let’s see what are
the technologies used to build this software program.
5.2. Development of the project
The project is developed from identification of problem. After that we started to try solving the
problem through the waterfall model as methodology used. In implementation and
experimentation we used the technology tools like PHP language, cascading style sheet (CSS),
java script, Hypertext Markup Language HTML and xammp sever. We optimized the systems,
then we written down the instructions code to implement new system but it was not easy because
of time. So for support of my supervisor the project is done.
5.3. Technology and tools used
The technology tools used in this new system are described in the following step:
5.3.1. Apache
Apache is the web server that is primarily used to serve both static content and dynamic Web
pages on the World Wide Web. Many web applications are designed expecting the environment
and features that APACHE provides.
5.3.2. PHP
PHP stands for Hypertext Preprocessor and is a server-side language. This means that when a
visitor opens the page, the server processes the PHP commands and then sends the results to the
visitor's browser, just as with ASP. A typical PHP files will content commands to be executed in
the server in addition to the usual mixture of text and HTML (Hypertext Markup Language) tags.
However, PHP is Open Source and cross-platform. PHP runs on Windows NT and many Unix
versions, and it can be built as an Apache module and as a binary that can run as a CGI.
41
Figure 15: Common Gateway Interface (CGI)
5.3.2.1 Advantages of PHP
The popularity of PHP is growing rapidly because of its advantages:
It’s faster. Because it is embedded in HTML code, the response time is shortest.
It’s inexpensive-free, in fact. PHP is proof those free lunches do exist and that you can get more
than what you paid for.
It’s easy to use. PHP contains many special features and functions needed to create dynamic web
pages. It can run on many operation systems. It runs on a wide variety of operating systems:
Windows, Linux, Mac OS, and most varieties of UNIX. Technical support is widely available. A
large base of users provides free support via email discussion lists. It’s designed to support
databases.PHP includes functionality designed to interact with specific databases. It relieves you
of the need to know the technical details required to communicate with a database.
It’s customizable. The open source license allows programmers to modify the PHP software,
adding or modifying features as needed to fit their own specific environments.
5.3.2.2 How does PHP work?
PHP is embedded scripting language when used in web pages. This means that PHP code is
embedded in HTML code. You use HTML tags to enclose the PHP language that you embed in
your HTML file, the same way that you would use other HTML tags. You create and edit wed
pages containing PHP the same way that you create and edit regular HTML pages.
The PHP software works in the conjunction with the web server. The web server is the software
that delivers web pages the world. When you type a URL into your web browser, you are
42
sending a message to the web server at the URL, Asking it to send you an HTML file and display
the web page. You also request the web server to send you a file when click a link in a web page.
In addition, the web server processes a file when you click a web page button that submits a
form.
5.3.3 HTML
Hypertext Markup Language, language for creating Web pages, it uses a structure formed with
tags allowing the formatting of text. It requires a web browser for viewing.
The purpose of a web browser is to read HTML documents and compose them into visible or
audible web pages. The browser does not display the HTML tags, but uses the tags to interpret
the content of the page.
HTML elements form the building blocks of all websites. HTML allows objects to be embedded
and can be used to create interactive forms. It provides a means to create structured by denoting
structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. It
can embed scripts written in languages such as JavaScript which affect the behavior of HTML
web pages.
Web browsers can also refer to Cascading Style Sheets (CSS) to define the appearance and
layout of text and other material. The W3C, maintainer of both the HTML and the CSS
standards, encourages the use of CSS over explicit presentational HTML markup
5.3.4. Cascading Style Sheets (CSS)
CSS, or Cascading Style Sheets, is a W3Copen standards programming language for specifying
how a web page is presented. It allows web site designers to create formatting and layout for a
web site independently of its content.
5.3.5. JavaScript
A scripting language developed by Netscape to enable Web authors to design interactive sites.
JAVASCRIPT can also interact with HTML source code, enabling Web authors to spice up their
sites with dynamic content.
43
5.3.6. Xampp
Xampp is a free and open source cross-platform web server package, consisting mainly of the
apache HTTP server, MSQL database and interpreters for scripts written in the PHP and Perl
programming languages. The program is released under the terms of the GNU General Public
License and acts as free web server capable of serving dynamic pages. Xampp is available for
Microsoft Windows, Linux, Solaris or Mac OS, and is mainly used for web development
projects.
5.4. Software testing
Software is an investigation conducted to provide Rwandan mining industry with information
about the quality of the product or service under test. Software testing also provides an objective,
independent view of the software to allow the business to appreciate and understand the risks of
software implementation. Test techniques include, but are not limited to, the process of executing
a program or application with the intent of finding software bugs.
5.4.1. Functional vs. Non functional testing
Functional testing refers to activities that verify a specific action or function of the code. These
are usually found in the code requirements documentation, although some development
methodologies work from use cases or use stories. Functional tests tend to answer the question of
“Can the user do this?” or “does this particular feature work?”
Non-functional testing refers to aspects of the software that may not be related to a specific
function or user action, such as scalability or security. Non-testing tend to answer the question
like “How many people can log in at once?”
5.4.2. Testing methods
There are different methods which can be use for Software testing. This briefly describes those
methods.
5.4.2.1. Black-box testing
Black-box testing is a method of software testing that examines the functionality of an
application (e.g. what the software does) without peering into its internal structures or workings.
44
This method of test can be applied to virtually every level of software
testing: unit, integration, system and acceptance.
5.4.2.2. Lack Box Testing
The technique of testing without having any knowledge of the interior workings of the
application is Black Box testing. The tester is oblivious to the system architecture and does not
have access to the source code. Typically, when performing a black box test, a tester will interact
with the system's user interface by providing inputs and examining outputs without knowing how
and where the inputs are worked upon.
5.4.2.3. White Box Testing
White box testing is the detailed investigation of internal logic and structure of the code. White
box testing is also called glass testing or open box testing. In order to perform white box testing
on an application, the tester needs to possess knowledge of the internal working of the code.
The tester needs to have a look inside the source code and find out which unit/chunk of the code
is behaving inappropriately.
5.4.2.4. Grey Box Testing
Grey Box testing is a technique to test the application with limited knowledge of the internal
workings of an application. In software testing, the term the more you know the better carries a
lot of weight when testing an application.
Mastering the domain of a system always gives the tester an edge over someone with limited
domain knowledge. Unlike black box testing, where the tester only tests the application's user
interface, in grey box testing, the tester has access to design documents and the database. Having
this knowledge, the tester is able to better prepare test data and test scenarios when making the
test plan.
5.4.2.5. Testing levels
Tests are frequently grouped where they are added in the software development process, or by
the level of specificity of the test. Unit testing refers to tests that verify the functionality of a
45
specific section or code, usually at the function level. In an object-oriented environment, this is
usually at the class level, and minimal unit tests include the constructors.
These types of tests are usually written by developers as they work on code (white box style), to
ensure that the specific function is working as expected. One function might have multiple tests,
to catch corner cases or other branches in the code. Unit testing alone cannot verify the
functionality of a piece of software, but rather is used to assure that the building blocks the
software uses work independently of each other. Unit testing is also called component testing.
Integration testing Integration testing is any type of software testing that seeks to verify the
interfaces between components against a software design. Software components may be
integrated in an iterative way or altogether (“big bang”). Normally the farmer is considered a
better practice since it allows interface issues to be localized more quickly and fixed.
Integration testing works to expose defects in the interfaces and interaction between integrated
components (Modules). Progressively larger groups of tested software components
corresponding to elements of the architectural design are integrated and tested until the software
works as a system, Software verification and validation, Software testing is used in association
with verification and validation; Verification is the process of evaluating a system or component
to determine whether the products or a given development phase satisfy the conditions imposed
at the start of that phase. Validation is the process of evaluating a system or component during or
at the end of the development process to determine whether it satisfies specified requirements.
5.5. System interfaces
This section contains some of the interfaces (GUI) which captured by print screens to present
how Rwanda mining Right management System (R.M.R.M.S) will look like.
5.5.1. Home page
Home page of Rwanda Mining Right Management System(R.M.R.M.S). Here the user will be
informed about the system that he is going to use, and then he/she will be given the option of
logging in.
46
Figure 16: Home page
5.5.2. LOGIN PAGE
After the user had clicked on login, the next page will be displayed. It is a login page. Here, you
can use a system as; a mining company, district, administrator and minister.
Figure 17: Login page
5.5.3. COMPANY REGISTRATION PAGE
The new company on the system must be registered on system, this facilitate the registration.
Each company fills all information shown on this page.
47
Figure 18: Company registration page
5.5.4. Company license Request page
The company licenses request page is the page of company use in the moment of requesting the
licenses. The request of licenses, it is necessary fill and submits all information in using this page
Figure 19: Requesting form page
5.5.5. LICENSE DELIVERY PAGE
This page facilitates the minister the delivery of licenses. After process all information on request
of company to the license, the minister keeps the delivery of the licenses using form of this
48
interface
Figure 20: page of license deliverance
49
CHAPTER VI: CONCLUSION AND RECOMMENDATIONS
6.0. Introduction
In this chapter, the conclusion, recommendations as well as suggestions for further researchers
are going to be given.
6.1. The conclusion
The main objective of this project entitled “RWANDA MINING RIGHTS MANAGEMENT
SYSTEM(R .M .R .M .S)” was to provide a web based application, which will be used by
Rwanda mining sector in management of mining license distribute. We analyzed the existing
mining license management system offered by MINIREMA to the company and cooperative do
business in mining sectors, and we clearly showed how the system can migrate from paper-based
to a web application system.
This objective has been successfully achieved with a practical solution which shows that using
PHP as a programming language technology, MYSQL to make the database, and Software
Development Life Cycle as a methodology, has successfully solved the issues of the company
and cooperative that used for requesting the mining licenses.
This new system allows the company and cooperative to request for mining licenses, allows
company and cooperative that gates licenses to check their remainder of their licenses days,
allows the local government and central government to control mining license movement and to
generate the necessary reports.
6.2. Recommendations and suggestions for further researchers
6.2.1. Recommendations
Based on experiences, investigation carried out and some constraints accoutered to finish this
research the following recommendations are mentioned, for the great success of the present
system. We recommend MINIRENA to implement this software and deal with the researcher if
some features can be added or changed according to their will.
6.2.2. Suggestions for further researchers
More features would have been added to this system but the issue of the time was very strict for
us. As the wisdom of software engineering teaches that software is never completed, the
50
following is suggested to the future researchers; to add the feature of licenses payment, the
connecting R .M .R .M .S to the bank system and Geographic Information Systems (GIS) for
mining site map. To consider this software as a product in progress.
51
REFERENCES AND BIBLIOGRAPHY
1. BOOKS
Official Gazette the Republic of Rwanda, No49/2010 of 11 October 2010
Official Gazette the Republic of Rwanda, No48/2009 of 06 April 2009
Elizabeth Castro, HTML for the World Wide Web, 5th Edition, 2003, P 60-70, 74-80,263-279,282-292
Romain BOUCQ, PHP5, 1ère
Edition, Juillet 2005, P. 57-66
2. HANDOUTS
1. KAGORORA Sampson, INTERNET &WEB PROGRAMMING, unpublished, INILAK,
2013.
2. KAGARAMA Jean Baptiste, SYSTEM ANALYSIS AND DESIGN,
unpublished,INILAK,2012
3. DISSERTATIONS
1. UWIMPUHWE Clarisse ,’ONLINE MINERAL ACTIVITE MONITORING
SYSTEM’.INILAK, Kigali, December 2012
2. BIZIMANA J.BOSCO, ONLINE MANAGEMENT INFORMATION SYSTEM FOR
XTRA MILE MINISTRIES SCHOLARSHIPS.INILAK, Kigali, December 2013
3. MUHIRE NDAYAMBAJE, ‘Online management system for solar energy system
installation’. INILAK, Kigali, December 2012.
4. TWAGIRIMANA Jean Claude, ‘ONLINE MANAGEMENT SYSTEM FOR FAUD
RECORDING IN RWANDA’, INILAK, Kigali, December, 2011.
3. WEB REFERENCES
http://www.blog37.com/blog/2010/07/system-development-life-cycle/
www.merriam-webster.com/dictionary/mining
www.businessdictionary.com/definition/right.html
52
www.investopedia.com/terms/r/right.asp
kalyan-city.blogspot.com/2011/04/what-is-management-definitions-meaning.html
en.wikipedia.org/wiki/Miner on 23/7/2013
en.wikipedia.org/wiki/License on 23/7/2013
www.access-programmers.com/normalizing-the-table-design.aspx, 30/09/2013
en.wikipedia.org/wiki/Database_management_system, 30/09/2013
http://en.wikipedia.org/wiki/Information_system ,0/09/2013
en.wikipedia.org/wiki/Management_information_system 15/09/2013,
www.theeastafrican.co.ke/news/Rwanda+to+renegotiate+21+expired+mining+licences/-
/2558/1287152/-/w8nltl/-/index.html 0n 24/6/2013
en.wikipedia.org/wiki/Structured_systems_analysis_and_design_method on 24/6/2013
www.sqa.org.uk/e-learning/SDM01CD/page_02.htm on 24/6/2013
en.wikipedia.org/wiki/Data_dictionary on 28/7/2013
database-programmer.blogspot.com/2008/06/using-data-dictionary.html on 28/7/2013
en.wikipedia.org/wiki/Logical_data_model on 28/7/2013
en.wikipedia.org/wiki/Physical_data_model on 28/7/2013
webcheatsheet.com/php/what_is_php.php 0n 30/7/2013
www.answers.com/topic/mining-right on 28/8/2013
www.investopedia.com/terms/m/mineral-rights.asp on 28/8/2013[3]
minirena.gov.rw/index.php?id=177 on 10/9/2013
minirena.gov.rw/index.php?id=178 on 10/9/2013
en.wikipedia.org/wiki/HTML on 12/9/2013
53
APENDICE
List of Request in process
Figure 21: list of Request in process
Licenses status
Figure 22: licences status
Sample of existing mining license
54
Figure 23: Sample of mining license
LOGIN CODE
<html><head>
<link rel="stylesheet" type="text/css" href="Css/styleWebsite.css">
</head><body>
<div class="wrapper">
<div id="header" style="background-image:url(images/header.jpg);"></div>
<div id="menu">
<ul>
<li><a href="home.html">Home</a></li>
<li><a href="contact.html">Contact Us</a></li>
55
<li><a href="Logout.php">Logout</a></li>
</ul></div>
<div id="leftDiv">
<center><img src="images/augu.jpg"></center>
</div>
<div id="centerDiv"><br>
<html><head><body><center><b>LOGIN </b><center><body></head></html><br><br>
<center><table>
<form action="VerifyLogin.php" method="POST">
<tr><td>User name :</td><td><input type="text" name="username" /></td> </tr>
<tr><td>password :</td><td><input type="password" name="password" /> </td> </tr>
<tr><td></td><td><input type="submit" value="Submit"></td></tr>
<tr><td></td><td><?php if(isset($_SESSION['verification'])) echo "<font color='red'>User name or Password incorrect.Try again</font>";?></td></tr>
</form></table></center><br>
<center><img src="images/loginpage.jpg"></center><br>
<center><font color= "red ">MAP OF MINING SITE IN RWANDA</font></center></div>
<div id="rightDiv">
<li><a href="LoginForm.php">Home</a></li><br>
<li><a href="contact.html">Contact Us</a></li><br>
<li><a href="Logout.php">Logout</a></li>
<br><br>
<center><b><img src="images/login.jpg"></center></b>
</div>
<div id="footerDiv"><?php include('footerPage.html');?></div></body></html>