Anda di halaman 1dari 34

Micro Link Information Technology

Business College

Department of Software Engineering

Caravan ICET Solutions

Prepared: By

Name: ROBIEL TADDELLE

ID: Mde/2524/13

Advisor: Yoseph K
Acknowledgment

First of all we would like to thank God for his help in every aspects of our life. Our heartfelt
gratitude goes to my advisor Yoseph Kiros who had been always there to help and co-operate us
with his valuable ideas, views, suggestions, devotion and more than everything his friendly
approach. Similarly, we cannot remain without thanking our respective parents and siblings from
whose love, care and continuous toil, we are here to do this project work.

At last, not the least we too express our thanks to everyone inclusive of friends who had been
always there for preparing this project work.
Abstract:
A website is a place where people can leave any types of messages and notifications, for example,
to advertise things, announce events or provide any information.
A website it can be placed on digital devices such computers, tabs, mobile phones etc. This web
project is very helpful for all type of users like existing users and new users. So admin can leave
and erase notification for other people to read and see. The main aim of this free online notice
board project is make information dissemination much easier in a paperless community as the
world tends to interact with the online notice board facility as an project, admin can send the
notification to the particular users regarding any new activity happen in organization fest
participation, warnings and reminders etc for this work web project is make all work much easier
and understandable to all. This project work generally intends to act as a support system for the all
users. By the help of free online solution to users can access the notifications and articles quickly
not only in the particular premises, also wherever and whenever they need to know. This this web
usability is fully capable of passing relevant notices and announcements, and keeping the users
update from time to time. The users are kept updated each time with the online notice board for
Caravan is uploaded based on their preferences with respect to through a notice board online. This
web application involves almost all the features of online notice board. In the online notice board
project all the updates like, add, delete, view are done by admin, so that user will get the updated
current information through notice board online.
Table of Contents
Acknowledgment .......................................................................................................................... iiii

Abstract: ....................................................................................................................................... ivii

Table of Contents ......................................................................................................................... viii

List of Figures ............................................................................................................................ viiiv

Chapter One .................................................................................................................................... 1

1. Introduction ............................................................................................................................. 2

1.1. Introduction About the company...................................................................................... 3

1.2. Purpose, scope of the System ........................................................................................... 2

1.3. Scope of the System ......................................................................................................... 2

1.4. Objectives ..................................................................................................................... 3

1.5. Methodology .................................................................................................................... 4

1.5.1. Data Gathering Methodology ................................................................................... 4

Chapter Two.................................................................................................................................... 5

2. Requirement Analysis ............................................................................................................. 5

2.1. Overview of the existing System ..................................................................................... 5

2.2. Overview of the proposed system .................................................................................... 5

2.2.1. Problem of The Existing System .............................................................................. 6

2.3. Constraints and Assumptions ........................................................................................... 7

2.3.1. Constraint of the project............................................................................................ 7

2.3.2. Assumption of the project ......................................................................................... 7

2.4. Specific Requirements...................................................................................................... 7

2.4.1. Functional Requirement ............................................................................................ 7

2.4.2. Non-Functional Requirements .................................................................................. 8

2.5.1. Hardware requirements .................................................................................................... 9


2.5.2. Software requirement ................................................................................................ 9

2.6. System modeling ............................................................................................................ 10

2.6.1. Use case diagram .................................................................................................... 10

2.6.2. Sequence/ Collaboration diagrams ......................................................................... 11

2.6.3. Class diagrams ........................................................................................................ 13

CHAPTER THREE ...................................................................................................................... 15

3. SYSTEM DESIGN ............................................................................................................... 15

3.1 Design Goal ........................................................................................................................ 15

3.2 System Decomposition ....................................................................................................... 15

3.3 System Architecture ............................................................................................................ 15

3.4 Deployments Diagram ........................................................................................................ 17

3.5. User Interface Design ........................................................................................................ 17

CHAPTER FOUR ......................................................................................................................... 18

4.1. Implementation .................................................................................................................. 18

4.2. TOOLS ............................................................................................................................... 18

4.3. Sample code and out put .................................................................................................... 21

4.2.1. Sample code and out put of homepage ....................................................................... 21

4.2.2. Sample code Admin and output .................................................................................. 23

4.3 Software Testing ................................................................................................................. 26

4.3.1. Unit tests................................................................................................................................... 26

4.3.2. Integration testing..................................................................................................................... 26

4.3.3. System testing .......................................................................................................................... 27

CHAPTER FIVE .......................................................................................................................... 28

5.1. Conclusion and Recommendation ................................................................................................... 28

5.2. Conclusion ....................................................................................................................................... 28

5.3. Recommendation ............................................................................................................................. 28


List of Figures
Figure 1. the existing and new systems .......................................................................................... 6
Figure 2: The use case diagram. ................................................................................................... 10
Figure 3: User diagram ................................................................................................................. 11
Figure 4: Admin diagram .............................................................................................................. 12
Figure 5: Class Diagram 1 ........................................................................................................... 13
Figure 6:: Class Diagram 2 .......................................................................................................... 14
Figure 7: User Database ................................................................................................................ 16

Figure 9: Deployment Diagram .................................................................................................... 17


Figure 10: Homepage .................................................................................................................... 22
Figure 11: Admin Homepage........................................................................................................ 25
Figure 12: Output of Registration Form ....................................................................................... 25
Chapter One

1. Introduction
1.1. Introduction About the company
Caravan ICET solutions provides a variety of sales register machnes to suit the range of
all your business need.

Caravan ICET provides you free support training, maintenance (with in warranty period),
item insertion and other services.

 And also has the following business partners:

 Guna Trading House PLC

 Mekelle Institute of Technology

 Daisy Technology LTD

 Ethiopian Revenue and Customs Authority

 Tigray Revenue Development Agency

VISION

To be a nationally competitive and exemplary solution provider in the Ethiopia.

MISSION

Creating vibrant private sector in the country by providing online solutions as well as provide
well trained man power in technologies. Introduction about the Project

In our project is to develop a web system for user using high level programming language PHP.

In the existing system, addressing of efficient data to the intended user was not comfortable. In
addition to lots of paper work, the beauty of the city was damaged, and user haven’t got the chance
to access the things they need to know about the occupation, and other stuffs.

1
 The project post notice website system is a web based application that used in worldwide
or local area to accessible of solutions to the user.
 Website works as the company announcer the company gives its notice to the developer.
The developer posts the company notice to the users.

 The software system is developed using PHP programming language and Wamp
server database to store and manage data.

1.2. Purpose, scope of the System


Currently the company uses manual base system, which is time consuming and space wastage. In order to
avoid this difficulty, developing an online solution system will replace the existing manual system and
also reduces time, energy wastage.

The purpose of this project is:

 Make an easy to use environment for users.


o In this case the system will be easy to access and friendly to access.
 Save money and time of the users
o The user will be able to save their time, which means that the users will have the
chance to check any troubleshooting and solutions online anywhere any time.
 Create clean environment.
 Searching a particular Notice.
o The user will have the chance to search any information from the database.

1.3. Scope of the System


The scope of the project is limited to the study, design and implementation of system. In this project we
will focus only on:
Caravan ICET Solution. Focuses on:

 Post online free supports to users


 Post training modules online for registered users
 Post register machines for sale
 Searching a particular Notice

2
1.4. Objectives
1.4.1. General Objective

The general objective of this project is to develop a web system. The primary aim of the Online
solution support project is to create a fully functional digital solution system which will
efficiently handle all assigned tasks. It may be able to, in due course, heavily minimize, if not
eradicate, the conventional. With the help of the supplementary applications, users will be able to
receive real-time notifications of any and all notices posted by another user with privileges as
such.

1.4.2. Specific Objective


For successful development of the software system, the project comprises the following specific
objectives: -

- To make effective communication with user of the web for adequate gathering of required
information
- To design the graphical user interface with hypertext markup language (html) and code the
web based software using PHP programming language.
- To design the database using the requirement analysis and gathered data.
- To develop supplementary web for the proposed solution.
- To create a user-friendly interface.
- To develop and manage a proper database system to ensure data safety and proper
management.
- To allocate various levels of users and have proper authentication.
- To assure the availability of the right information at the right time.
- Design and develop an integrated system to query the data model.
- To provide a system with a user-friendly interface which is simple to understand and
efficient to use.
- Reduce the time and energy consuming.
- Reduce unfairness service.

3
1.5. Methodology
1.5.1. Data Gathering Methodology

The information discussed in this section includes the features of the study area where the research
was conducted, the methodology adopted, and instrument used for data collection and analysis.
About Data Collection

 Interview for the respective persons

 Document Observation of the existing system

 Direct Observation & Participation of the system

Approach (object-oriented program)


object oriented programming approach to any programming language. By using these features,
you can easily reuse your program or part of your program provides you a power to do
programming in a very effective manner.

Modeling Technique
 Logical Database Design

 Mapping

 Integrity Constraints

 Implementation Language

 My sql: (structure query language)

 Software: Wamp server

4
Chapter Two

2. Requirement Analysis
2.1. Overview of the existing System
Currently Caravan has manual system of providing solutions. It was found to be inefficient in
meeting the growing demands of population Proposed System will be able to eliminate wastage
of time and energy.

 Current System

o Manual Usage of record system


o Manual usage/providing solutions.

2.2. Overview of the proposed system


Our website is called Caravan ICET Solution. The user can sign up to make view and can
download; more information’s, solutions.

The existing system was a manual or paper-based system. But It was found to be inefficient in
meeting the growing demands of population Proposed System will be able to do the following:
- To eliminate wastage of time and energy.
- To avoid duplication and overlapping.
- Searching a particular Notice.
- Reduction of waiting lists through more efficient use of resources.
- The amount of time spend by both customers and service givers because of the slow
manual system will be reduced
<!DOCTYPE html>
<html>
<head>
<title> Services</title>
<style type="text/css">
<body>
<p>Copyright © 2016 - 2018 - Caravan Information and Communications Engineering and Technology Solutions Plc</p>
<p>Sales Register Machine Information Management System (SRM-IMS) </p>
<hr>
<p>
Designed and Developed by -Natna ICT Solutions Plc. - All Rights Reserved.</p>
<p>Mekelle, Ethiopia.

5
</p>
</div>
</body>
</html>

The following figures are the system that are.

Figure 1. the new systems

2.2.1. Problem of The Existing System

In the existing paper system, addressing of efficient data to the intended user was not comfortable.
In addition to lots of paper work. Other the online notice board website lacks addressing the
information to the user in able way.

Lack of prompt updating.

Manual notices stack is vulnerable to damage, destruction and theft in ways that digital
databases are not.
The web do not allow users to easily edit data or information.

Wastage of resources, time & man power

6
2.3. Constraints and Assumptions
2.3.1. Constraint of the project

These web systems have constraint with who has little knowledge and experience with computer
which can make it difficult for effective implementation. Internet network problem is also one
issue at the district which can result more challenge during implementation.

Constraints

 Unfortunate failure of system


 Connection problem
 Power problem and virus attack
he interfaces will be in English and Amharic only. The system is working for single server.

2.3.2. Assumption of the project

In our country, Ethiopia online solution not well known to the user because of shortage of
implementation and even if they are exist they are not comfortable to the user.

The website does require back-end database server wamp for storing the username and password
for different types of user of the system as well as various databases regarding various insurance
information. User must be trained for basic computer functionalities. User must have the basic
knowledge of English the system must be able to respond to database software
within reasonable time.
The website will require a computer with an application program or with any other application
program and a communication channel.

2.4. Specific Requirements


2.4.1. Functional Requirement

Are statements of services the system should provide, how the system should react to particular
inputs, and how the system should behave in particular situations? In some cases, the functional
requirements may also explicitly state what the system should not do.

 Workload of notice in chargers would be greatly reduced.


 Notices would be displayed in a more confined and sophisticated manner.

7
 To manage and store notices and files.
 To provide appropriate UI for notice and file upload and download.
 recognize and authenticate several levels of users.
 manage and maintain a proper database.
 work seamlessly with the web server.
 provide push messaging in real time, whenever available.

2.4.2. Non-Functional Requirements

Are constraints on the services or functions offered by the system? They include timing constraints,
constraints on the development process, and constraints imposed by standards. Non-functional
requirements often apply to the system as a whole, rather than individual system features or
services.

Following Non-functional requirements will be there in the Insurance on internet:

Secure access of confidential data.

 Better component design to get better performance at peak time.


 easily operable and user friendly.
 Error handling
 Graphical user Interface (GUI): The graphical user interface of the online notice board
website system is designed using hypertext markup (Html) and php language which is
primarily used to define structure of the software pages and design its elements.
 Input output validation (I/O)
 Security

Performance Requirements

The system in itself does not require anything specific for basic operation, but the complete
website with all its components running may have some performance requirements. an internet
connection is needed for the features of the system to become available.

8
Safety Requirements
Major attention should be given to the safety and security of the data and information that are
stored in the database. The database must be trustworthy and non-leakage to ensure no data loss
occurs.
Security Requirements
User authentication must be absolute and non-by-passable. No user should be able to access the
website without providing proper authentication. In case of guest users, only public notices and
events should be visible.

2.5. Systems Requirements:


2.5.1. Hardware requirements

There is no distinct interface for hardware upon which the on line notice board website system
needs to reside. It is accessible from any computer being connected to the internet. Even it is a
mobile friendly application which makes it very convenient for users.

Hardware requirements for Insurance on internet will be same for both the parties which are
follows:

computer

 Processor: - Pentium I or above.


 RAM: - 128 MB or above.
 HD: - 20 GB or above.
 NIC: - For each party

2.5.2. Software requirement

The website system uses Wamp server database to manage data. In addition, before deployment
to an actual server, the system is developed and executed on local personal computer using a Wamp
virtual server which allows using apache and database with a web browser. Notepad++ web
programming environment is used to develop the modules and interfaces that drive the website

Software required to make working of product is: -

9
 Operating System: Windows XP/vista/7 or later version, Linux OS which supports
networking
 Programing language: PHP, HTML, JS and CSS.
 Database: wamp server

An active internet connection will be required for the functioning of the website. In case of the
mobile apps, an internet connection will then allow the software to connect to the online
database. The system will use the Hyper Text Transfer Protocol (HTTP) to transmit data.

2.6. System modeling


System modeling is the process of developing abstract models of a system, with each model
presenting a different view or perspective of that system. System modeling as generally come
to mean representing the system using some kind of graphicalotation, which is now almost
always based on notations in the Unified Modeling Language (UML).

2.6.1. Use case diagram

Through use case diagram we are graphically representing how the user is interacting with the
proposed system by model the functionality of a system using actors and use cases.
Use case diagrams, which show the interactions between a system and its environment.

Use cases are requirements discovery techniques that were first introduced in the Objector
method. They have now become a fundamental feature of the unified modeling language.

Figure 2: The use case diagram.

10
In Figure. 3, Admin means: the system administrator whose duties is to post the allowed
announcements through uploading or typing on the text box provided, read the posted
announcements through downloading them first, delete outdated announcements and archive
where necessary, register guest, and user, view guest and user. user means: any registered user in
the system, this will be capable of after being given the right to do that by administrator, read
announcements posted by others through downloading them first and receiving notifications. User
means: any user who hasn’t registered for the system.

2.6.2. Sequence/ Collaboration diagrams

Sequence diagrams in the UML are primarily used to model the interactions between
The actors and the objects in a system and the interactions between the objects themselves.

User diagram

Figure 3: User diagram

11
Figure 4: Admin diagram

12
2.6.3. Class diagrams

Class diagrams, which show the object classes in the system and the associations between
these classes. An object class can be thought of as a general definition of one kind of system
object. An association is a link between classes that indicates that there is a relationship between
these classes. Consequently, each class may have to have some knowledge of it

System Items

ItemID

File
Notice

FileID
NoticeID
UploaderID
UploaderID
Uploadtimestamp
Uploadtimestamp
Filesize
Priority
FileType

Restricted Notice Class file


Public Notice

NoticID FileID
NoticeID
UploaderID UploaderID
UploaderID
Uploaderlocation Filesize
Priority
Priority Filetype

Class Notice

NoticID

UploaderID

Priority

Figure 5: Class Diagram 1

13
System Places

Notice List

Restricted Room
Public Room

RoomID
Notice List
RoomName

Notice List

Filelist

Room

RoomID

RoomName

NoticeList

Filelist

Figure 6:: Class Diagram 2

14
CHAPTER THREE

3. SYSTEM DESIGN
3.1 Design Goal
On designing of the web we had considered the Availability, Manageability, Scalability, and
Securablity of the web.

 Availability: The web page has designed with an easy use understandable for all type of
users.
 Manageability: The web page has also designed to be managed by the admin to post the
advertising products and news, and for uploading entertainment to user.
 Scalability: The web page has also designed to be to fully satisfy the demand of the user
by increasing resources.
 Securablity: The web page has designed to be safely protecting the resources by the admin.

3.2 System Decomposition


The webpage system has decomposed to a lot of field, home, about, news, at the home page
advertised materials will frequently addressed for the user, and at the about page general
information about the organization will be displayed, and also at the news page the latest news
will frequently displayed, at last we have the vacancy page that contains different Vacancies from
different organization and we also have a Bid local and international that contains different bids
from local companies and international companies.

3.3 System Architecture


Architectural design is a creative process where you design a system organization that will
satisfy the functional and non-functional requirements of a system. Because it is a creative process,
the activities within the process depend on the type of system being developed, the background
and experience of the system architect, and the specific requirements for the system.
It is therefore useful to think of architectural design as a series of decisions to be made rather than
a sequence of activities.
=> The following are the details of some of the web system architecture:

15
A. Home

Name: Home page


Type: Web page
Description: This is the initial page presented to users who access the webpage system. It displays
about the organization general information.
B. Login

Name: Login page


Type: Web page form
Description: This is the initial page presented to users who logged in to system. It displays a form
to accept username and password.
Attributes: Text

User Database

Figure 7: User Database

16
3.4 Deployments Diagram
The webpage uses MySQL database. All of the pages for the web based software system
will reside on webhost server and users use web browser installed on local computers to access the
system.

Figure 8: Deployment Diagram

3.5. User Interface Design


The graphical user interface of the advertising website system is designed using hypertext
markup (Html) and php language which is primarily used to define structure of the software pages
and design its elements.
Java script and Cascade style sheet (css) are also used to add styling to the pages. The main
intention of the interface design is to make it usable for non-technical users.

17
CHAPTER FOUR
4.1. Implementation
The proposed system will implement parallel with the existing system until the awareness
of the employer and customers towards the proposed system improved

4.2. TOOLS
 SOFTWARE

Font-End Tool : PHP, html, JavaScript

Back-End : MySQL Server

 BACK END
 MySQL SERVER
Microsoft MySQL Server is an application used to create computer databases
for the Microsoft Windows family of server operating systems.
It provides an environment used to generate databases that can be accessed from
workstations, the web, or other media such as a personal digital assistant (PDA).
Microsoft MySQL Server is probably the most accessible and the most
documented enterprise database environment right now. This also means that you
can learn it a little quicker than most other database environments on the market.

 PHP
PHP is a programming language designed to generate web pages interactively
on the computer serving them, which is called a web server. PHP code
runs between the requested page and the web server, adding to and changing the
basic HTML output.
While PHP is great for web application development, it doesn’t store information by
itself. For that, you need a database.
The database of choice for PHP developers is MySQL, which acts like a filing
clerk for PHP-processed user information. MySQL automates the most common

18
tasks related to storing and retrieving specific user information based on your
supplied criteria.
MySQL is easily accessed from PHP, and they work well together. An added
benefit is that PHP and MySQL run on various computer types and operating
systems, including Mac OS X, Windows-based PCs, and Linux.

 Apache
Apache is a web server that turns browser requests into resulting web pages and
knows how to process PHP code. PHP is only a programming language, so without
the power of a web server like Apache behind it, there would be no way for web
users to reach your pages containing the PHP language code.

 SQL and Relational Databases


Structured Query Language (SQL) is the most popular language used to create,
retrieve, update, and delete data from relational database management systems. A
relational database conforms to the relational model and refers to a database’s data
and schema.
The schema is the database’s structure of how data is arranged. Common usage of
the term “Relational Database Management System” technically refers to the
software used to create a relational database, such as Oracle or Microsoft SQL
Server.
A relational database is a collection of tables, but other items are frequently
considered part of the database, as they help organize and structure the data in
addition to forcing the database to conform to a set of requirements.

 MySQL
MySQL is a free yet full-featured relational database. MySQL was developed in
the 1990s to fill the ever-growing need for computers to manage information
intelligently.
MySQL supports several different database engines. Database engines determine
how MySQL handles the actual storage and querying of the data. Because of that,

19
each storage engine has its own set of abilities and strengths. Over time, the database
engines available are becoming more advanced and faster.
 Database design
Certain principles guide the database design process. The first principle is that
duplicate information (also called redundant data) is bad, because it wastes space
and increases the likelihood of errors and inconsistencies. The second principle is
that the correctness and completeness of information is important. If your database
contains incorrect information, any reports that pull information from the database
will also contain incorrect information. As a result, any decisions you make that are
based on those reports will then be misinformed.
A properly designed database provides you with access to up-to-date, accurate
information. Because a correct design is essential to achieving your goals in working
with a database, investing time required to learn the principles of good design makes
sense. A good database design is, therefore, one that:
 Divides your information into subject-based tables to reduce
redundant data.
 Provides Access with the information it requires to join the
information in the tables together as needed.

 Helps support and ensure the accuracy and integrity of your


information.

20
4.3. Sample code and out put

4.2.1. Sample code and out put of homepage


<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="">
</head>
<body>
<div id="head">
<div id="logo">
<img src="logg.jpg" width="806" height="88">
</div>
<ol>
<li><a href="Home.php"> Home </a></li>
<li> <a href="Products.php"> Product</a> </li>
<li> <a href="Services.php"> Services</a> </li>
<li> <a href="About.php"> About Us</a> </li>
<li><a href="Contact.php"> Contact Us</a> </li>
<li> <a href="Login.php"> Login</a> </li>
</ol>
</div>
<div id="main">
<img src="Banner.png" width="77%" height="86%">
<h1> ቴቴቴቴቴ ቴቴቴቴቴቴቴ ቴቴቴቴቴቴ!</h1>

</div>
<div class="right">
<h2>Business partners </h2>
<ul>
<div id="link">
<li> <a href="http://www.effortinvestments.com/cgi-sys/suspendedpage.cgi"> Guna Trading House
PLC</a> </li>
<li> <a href="http://www.mitethiopia.edu.et/"> Mekelle Institute of Technology </a></li>
<li> <a href="http://en.daisy.bg/"> Daisy Technology LTD </a></li>
<li> <a href="http://www.erca.gov.et/"> Ethiopian Revenue and Customs Authority </a></li>
<li><a href="http://www.trda.gov.et/"> Tigray Revenue Development Agency </a></li>

21
<li><a href="http://www.p-eds.com/index.php?lang=en"> Professional Electronic Data Systems PLC
</a></li>
<li> <a href="http://caravanethio.com/"> Akless Paper Products PLC </a></li>
<li> <a href="http://caravanethio.com/">Abacus Accounting Management Consulting & Commercial
Firm </a></li>
<li> <a href="http://caravanethio.com/"> Natna ICT Solutions PLC </a></li>
<li> <a href="http://caravanethio.com/"> Mekelle University </a></li>
<li> <a href="http://caravanethio.com/">Wass Electronics </a></li>
</div>
</ul>

</div>
<div id="footer">
<p>Copyright © 2016 - 2018 - Caravan Information and Communications Engineering and Technology
Solutions Plc</p>
<p>Sales Register Machine Information Management System (SRM-IMS) </p>
<hr>
<p>
Designed and Developed by -Natna ICT Solutions Plc. - All Rights Reserved.</p>
<p>Mekelle, Ethiopia.
</p>
</div>
</body>
</html>
Then the output will be as follows:-

Figure 9: Homepage

22
4.2.2. Sample code for Admin and Registration Form

<html> <head>
</head>
<body>

<div id="head">
<div id="logo">
<img src="cg.jpg" width="806" height="88">

</div>
<ol>
<li><a href="Home.php"> Home </a></li>
<li> <a href="Products.php"> Product</a> </li>
<li> <a href="Services.php"> Services</a> </li>
<li> <a href="About.php"> About Us</a> </li>
<li><a href="Contact.php"> Contact Us</a> </li>
<li> <a href="Login.php"> Login</a> </li>
</ol>
</div>

<form name="login">
<h3> Enter Your User Name and Password to Register Customers Information </h3>
<table>
<tr>
<div id="lef"><td> User Name:</td> <td> <input type="text" name="un"></tphpd> </tr>
<tr> <td> Password: </td> <td><input type="Password"
name="ps"></td></div></tr></table>
<input type="button" onclick="check(this.form)" value="Login" id="submit">
</form>
<script type="text/javascript">
function check(form){

if (form.un.value=="Robel" && form.ps.value=="12345") {

23
window.location=("Registration.php");
//header("location:DaisyPerfectS.html");
}
else{
alert("Incorrect Password or User name")
}
}
</script>
<h1> ቴቴቴቴቴ ቴቴቴቴቴቴቴ ቴቴቴቴቴቴ!</h1>
<div class="right">
</div>
<div id="footer">
<div id="p1">Copyright © 2016 - 2018 - Caravan Information and Communications Engineering and
Technology Solutions Plc</div>
<div id="p1">Sales Register Machine Information Management System (SRM-IMS) </div>
<hr>
<div id="p1">
Designed and Developed by -Natna ICT Solutions Plc. - All Rights Reserved.</div>
<div id="p1">Mekelle, Ethiopia.
</div>
</div>
</body>
</html>

Output will be as follows

24
Figure 10: Admin Homepage
Output of Registration Form

Figure 11: Output of Registration Form

25
4.3 Software Testing

Software testing is an investigation conducted to provide stakeholders with information about


the quality of the product or service under test. Software testing can also provide an objective,
independent view of the software to allow the business to appreciate and understand the risks of
software implementation. Test techniques include the process of executing a program or
application with the intent of finding software bugs (errors or other defects).

It involves the execution of a software component or system component to evaluate one or


more properties of interest. In general, these properties indicate the extent to which the
component or system under test:

 meets the requirements that guided its design and development,


 responds correctly to all kinds of inputs,
 performs its functions within an acceptable time,
 is sufficiently usable,
 can be installed and run in its intended environments, and
 achieves the general result its stakeholders desire

4.3.1. Unit tests

Unit tests is test only a single "unit" of the code (say a module or a class), to see if it behaves
as expected. They generally make sure that the behavior of the module is sane and desirable, while
not trying to see if it works as part of the larger scheme.

4.3.2. Integration testing

Integration testing is executed to establish whether the components interact with each other
consort to the specification or not. Integration testing in large refers to joining all the components
resulting in the complete system. It is further performed by the developer or the software Tester or
by both.

26
4.3.3. System testing

The process of testing an integrated system is to verify that it meets specified requirements.
The objective of System Testing is to verify that the integrated information system as a whole is
functionally complete and satisfies both functional and non-functional design requirements.
Functional testing is concerned with what the system does whereas Non-Functional testing is
concerned with how the system does what it does. Defect/error detection is a primary goal. Some
of the testing operations within the E-Invoicing software system are:

- To check correct price calculation for different numerical values.


- To check accurate report generation.
- To inject fault values and inspect MySQL injection in the system.
- To assure accurate information retrieval and modification.
- To check for bugs and errors with in the code.

27
CHAPTER FIVE
5.1. Conclusion and Recommendation
5.2. Conclusion
This research paper suggests the software development process of web based system using
PHP programming language. Its functionality is basically to advertise different products, to share
updated news and to entertain to our users.

In addition to being user friendly graphical user interface (GUI) based web system; the
website is developed to be very usable by any users. So it is in the best interest of the user to use
such website in which they can handle easily. With the power of advancing web applications, the
researcher concludes that this web system is very advantageous for our society by simplifying a
lot of manual operations and creating a better work environment.

5.3. Recommendation

This project was developed to fulfill user and business requirement; however there are lots of
scopes to improve the performance of the website software system in the area of user interface,
functionality, database performance, and query processing time. Some of the future improvements
and additions that are possible in the project are:

 Developing front-end system where customers can view the company products, make order
and pay online.
 Integrating with billing machine.
 Adding user has their own profile.

28