TISQAAD

COMPUTER SCIENCE COLLEGE

RESEARCH BOOK ON TAFEY

ELECTRONICS
Submitted for the partial fulfillment of the requirements for the award of
the Diploma Information Communication Technology (ICT)
Under the Guidance of Name: Mohamed Amin

RESEARCHER’S NAMES:

1. MUSE MOHAMED MOHAMOUD

2. SAALIM MUSTAFE ISMACIL

3. JAMILA MUXUMED QORANE

INSTRUCTOR : MOHAMED ABDIRAHMAN ABDULLAHI (AMIN )

 TABLE OF CONTENTS

Chapter One
1.0 Introduction...........................................................................................
1.1 Background...........................................................................................
1.1.1 Org Background ……........................................................................
1.1.2 Mission...............................................................................................
1.1.3 Vision.................................................................................................
1.1.4 Org Structure. ....................................................................................
1.2 Problem Statement ..............................................................................
1.3 Proposed Solution.................................................................................
1.4 The project goals and Objectives..........................................................
1.4.1 Project goals.......................................................................................
1.4.2 Project Objectives..............................................................................
1.5 Theoretical background........................................................................
1.6 Project management.............................................................................
1.6.1 Total cost...........................................................................................
1.6.2 Time management.............................................................................

Chapter two
2. Analysis..................................................................................................
2.0 Introduction...........................................................................................
2.1 Fact
finding……....................................................................................
2.1.1 Interviews...........................................................................................
2.2 Requirements.........................................................................................
2.2.1 Functional requirements.....................................................................
2.2.2 Non-functional requirements..............................................................
2.3 System DFDs.........................................................................................
2.3.1 Context
Diagram.................................................................................
2.3.2 Level zero diagram.............................................................................
2.3.3 Lower-level
diagram...........................................................................

Chapter thee
3. Project design.............................................................................................
3.0 Introduction...............................................................................................
3.1 Data
dictionary………...........................................................................
3.1.1 Data item
dictionary............................................................................

I
3.1.2 Data structure
dictionary.....................................................................
3.1.3 Datastore dictionary...........................................................................
3.1.4 Data flow
dictionary............................................................................
3.1.5 Function description dictionary..........................................................
3.2 Data design............................................................................................
3.2.1 Entities and
Attributes.........................................................................
3.2.2 Database design..................................................................................
3.2.2.1 Create an initial
ERD.......................................................................
3.2.2.2 Assign all data elements to
entities...................................................
3.2.2.3 Create 3NF designs for all tables, taking care to identify all
primary and foreign
keys..........................................................................................
3.2.2.4 Generate the final ERD that will include new entities identified
during
normalization....................................................................................
3.3 Interface & Screens
design.....................................................................
3.4 Input, Output, and report
design.............................................................
3.5 Control
design........................................................................................

Chapter four
4. Project
implementation............................................................................
4.0 Introduction...........................................................................................
4.1 Application
development.......................................................................
4.1.1 Modules..............................................................................................
4.1.2 Refer to DFDs, process descriptions,
ERDs.......................................
4.2 User manual...........................................................................................

Chapter five
5. Conclusion and Future
work...........................................................................
5.0 Introduction...........................................................................................
5.1 Future work……......…….....................................................................

II
5.2 Conclusion….........................................................................................

References

III
 Chapter One
Introduction
1.0 Introduction
Tafey electronics is a place where you can buy any electronics from
smartphones to televisions. It is a great location for getting your next
phone, laptop, or TV. They offer many different items, and the experts
are always available if you need help choosing anything. Tafey
electronics is located Cadaani area.
1.1 Background
1.1.1 Org background
Tafey electronics was invented on 3rd May 2003 by entrepreneur
Mustafe Ismail in Hargeisa, Somaliland. During these nineteen years in
business, Taffy performed well and developed in capacity, experience,
and size. It employs about six people with different skills and
specializations.
1.1.2 Mission
 To enhance our product’s quality.
 To expand branches of the business in the country.
 To upgrade Employee’s skills to increase their efficiency.
 To achieve a high level of client satisfaction through excellent
service.
1.1.3 Vision
 To be the first choice for customers by exceeding their
expectations.
 To be the best electronic shop in Somaliland.
 To add new products to the business so that customers will able to
choose from a wide range of items at reasonable prices

1.1.4 Org Structure

CEO

Finance Manager Staff

Cashier

1
1.2 Problem Statement
The most common problems they tell us to include:
 This Electronic business has no database system to store the data
of the customers
 Our business data management was a manual system and was not
right to store in this modern time.
 Sometimes the data is lost due to manual system.
 Time-consuming to manage data because There was no
computerized system.

1.3 Proposed Solutions

As we have mentioned the problems that stumbled the company and we
will propose the solution that we found suitable they are listed
 This Desktop application solved the problem of registration,
manipulating, and storing the data in each customer.
 To make a quality management system to become secure data of
customers.
 after they get the application, they will be able to update their data
 To save time and effort to register or update data of the business
 To easily review all financial transaction activities.

1.4 Project goals and objectives

1.4.1 Project goals
This section will contain some of the goals that are willing to be
achieved in the coming up years with the help of this project here there
are some of them:
 to save the data in a simple way
 To make the data more secure
 To ensure that all information belongs to the right customers
 All system management is automated

1.4.1 Project Objectives

 To make easy data management
 To increase customer confidence
 To improve collaboration between coworkers
 To promote business profitability
1.5 Theoretical Background

2
C# is an elegant and type-safe object-oriented language that enables
developers to build a variety of secure and robust applications that run
on the .NET Framework. You can use C# to create Windows client
applications, XML Web services, distributed components, client-server
applications, database applications, and much, much more. Visual C#
provides an advanced code editor, convenient user interface designers,
an integrated debugger, and many other tools to make it easier to develop
applications based on the C# language and the .NET Framework. Such
as
1 Computer
2 Visual studio
3 SQL Database

1.6 Project management

1.6.1 Total cost Equipment Equipment cost

computer $400
Ram $70
mouse $25
printer $300
Total 795$

3
 1.6.2 Time management

Chapter Two
Data analysis
2.0 Introduction
System analysis is a logical process; the objective of this phase is not
actually to solve the problem but to determine what must be done to
solve the problem. The basic objective of the analysis stage is to develop
the logical model of the system.

Project duration
Buying tools 2

Application development 5

Editing book 1

Writing book 4
Tasks

Collecting data 1

Interview 2

Task 0

0 1 2 3 4 5 6
Days

This chapter will provide a full description of the system and its users
then it depicts the functional And non-functional requirements that have
been collected using several methods from Brainstorming interviews and
e-surveys, after determining the most important requirement,
Requirement analysis was adopted using several tools such as use –case

4
diagram, sequence diagram and activity diagram Before making the
project we must to make Analysis to try the solve problems that we
found our analysis. In this chapter, we deliberate to analyze the system
and easily understand how data is followed. The data Follow diagrams
(DFDs) or fact-finding they are helping to build an international system.
2.1 Fact Finding
2.1.1 Interview
Analyze manager
A: Do you use a computer? B: No, we use a book to store data.
A: what are the problems that your B: Sometimes data can lose due to the
Electronics need to help with? manual system we use.
A: How to see if we make you B: I need to find our program because
program your own? it will add more value to our business.
A: what do you think will make the B: The program should have a good
program easy to use for you? interface and user experience to be
easy to navigate.

2.2 Requirement
Before starting making any project the manager of the project must
determine what is functional, and nonfunctional requirements of the
project are because understanding the difference between the two helps
to ensure that developers will deliver a product that performs as
expected.
3.2.1

5
 3.2.2 Functional requirement
Functional requirements define a system or its component. It
describes the functions a software must perform. A function is
nothing but inputs, behavior, and outputs. It can be a calculation, data
manipulation, business process, user interaction, or any other specific
functionality which defines what function a system is likely to
perform. Simply is Something that system must do. If the system
does not meet a functional requirement it will fail. 
For example:
 The system sends an approval request after the user enters
personal information.
 A search feature allows a user to hunt among various invoices if
they want to credit an issued invoice.
 The system sends a confirmation email when a new user account
is created.
❖ Step one: how to enter the system

✓ Enter the password of the administrator will be able to create an

account and delete updated data in this Dental management system.
How to create new data: You can enter new records via visual basic
studio and SQL server
1. Click the new button then the Customer ID
2. Write the Customer’s name
3. Customer’s Address
4. Customer’s Phone number
5. And then click the save button
❖ Step Two:
How to update: Is the change data already exist into another new data if
you made a mistake
1. click the Customer’s table you want to update
2. click the Address or phone you went to update, then
3. Click the update button your data will be updated.

3.2.3 Nonfunctional requirements

Nonfunctional requirements describe how the system works. it
focused on how the system goes about delivering a specific function.

6
 At first glance, they might be seen as less important than functional
requirements but both have a part to play in a good system.
Nonfunctional requirements do not have an impact on the
functionality of the system but they do impact how it will perform. In
short, nonfunctional requirements are all about system usability. If
nonfunctional requirements are not met, users may become frustrated
with how the system works and go elsewhere. Meeting at least some
nonfunctional requirements is important in a well-performing system.
Some nonfunctional requirements are:
 Usability: the system should be easy to use for Staff.
 Maintainability: the system must be easy to modify and
maintain.
 Effectiveness: This means that system should perform well in
the effort.
 Interoperability: the system should be able to work with any
operating system easily.
 Efficiency: the system must give good results within an
amount of time.
 Security: the system should be secured from unauthorized
access.
 Accessibility: we must make sure that the system is accessible
to all authorized staff and not accessible to anyone else.
 Extensibility: the system must be customizable.
2.3 System DFDs
Data-Flow Diagram (DFD) is a graphical visualization of the movement
of data through an Information system.
DFDs are one of the three essential components of the structured-
systems analysis and Design Method (SSADM).

7
 2.3.1 Context Diagrams
Context diagram diagrams and data follow Context Diagrams and Data-
Flow Diagrams were created for systems analysis and design.

Inventory
Sellers Inventory detail
Receives product
Enters Product info Inventory report
report `

Electronic shop
Management
System
Order

Bill Inventory order

Payment

Customers Supplier

2.3.2 Level zero diagrams

In this part we will study diagrams in the project that how can easily
understand Diagrams can Help us to understand main concept of the
project many people can understands easily understand What diagrams
tells us

8
 1. Shows all the major processes that comprise the overall system the
internal components of process zero.

2. On the other side:

3. Shows how the major processes are interrelated by data flows
4. Shows external entities and the major processes with which they
interact
5. Adds data stores
Data flow diagrams (DFDs) reveal relationships among and between the
various components in a Program or system. DFDs are 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 consist of four major components:
entities, processes, data stores, and data flows. In below pictures tells us
the process of the programming is working

Order
Order
Order
Customers Inventory Store
Items
Bill
Order

Inventory
Detail

Inventory Order

Supplier Orders
Inventory Order Inventory Detail

Reports
Generate Sales Manager
Reports

Order Inventory Order

Inventory
9
 2.3.3 Lower-level diagram
A lower-level diagram is a component-level design process that follows
a step-by-step refinement Process. This process can be used for
designing data structures, and required software architecture The goal of
LLD or a low-level design document (LLDD) is to give the internal
logical design of the actual program code. High-level design is created
based on the low-level design. LLD describes the class diagrams with
the methods and relations between classes and program specs. It
describes the modules so that the programmer can directly code the
program from the document.

Manage products details

Manage sales details

Manage
modules
Manage payments details

Manage discounts details

Manage stock details

Manage inventory profiles

Manage user
Manage system Manage roles of
user permission
admins Manage login report

10
 Chapter Three
Project Design
3.0 Introduction
In this chapter, we deliberate and express the system and easy-to-see
graphical design project. Here, we shape the system, and always users
shall see the design to evaluate it.
3.1: Data Dictionary
A data dictionary is a collection of descriptions of the data objects or
items in a data model for the benefit of programmers and others who
need to refer to them. The first step in analyzing a system of objects with
which users interact is to identify each object and its relationship to other
objects. This process is called data modeling and results in a picture of
object relationships. After each data object or item is given a descriptive
name, its relationship is described (or it becomes part of some structure
that implicitly describes the relationship), the type of data (such as text
or image or binary value) is described, possible predefined values are
listed, and a brief textual description is provided. This collection can be
organized for reference into a book called a data dictionary. When
developing programs that use the data model, a data dictionary can be
consulted to understand where a data item fits in the structure, what
values it may contain, and basically what the data item means in real-
world terms. For example, a bank or group of banks could model the
Data objects involved in consumer banking. They could then provide a
data dictionary for a bank's programmers.
Entity Attribute Type/Size Primary key
Customer ID INT
Customer Full name Varchar (40)
Customer Age INT
Customer Gender Varchar (40)
Customer Tell INT

Customer Registration data Varchar (40)

Entity Attribute Type/Size Primary key
Customer Id No INT
Seller Name Name Varchar (40)
Date of Order Date Date & Time
Date of Delivery Time Date & Time

3.1.2 Data structure dictionary

11
A dictionary is a general-purpose data structure for storing a group of
objects. A dictionary has a set of keys and each key has a single
associated value. When presented with a key, the dictionary will return
the associated value. Which data structure can be used for efficiently
building a word dictionary and Spell Checker?

The answer depends upon the functionalists required in Spell Checker

and the availability of memory. For example, the following are a few
possibilities.
1. Hashing is one simple option for this. We can put all words in a hash
table. Refer to this paper which compares hashing with self-balancing
Binary Search Trees and Skip List, and shows that hashing performs
better.
2. Hashing doesn’t support operations like prefix search. Prefix search is
something where a user types a prefix and your dictionary shows all
words starting with that prefix. Hashing also doesn’t support efficient
printing of all words in the dictionary in alphabetical order and nearest
neighbor search.

Electronic
Management Admin
Customer
System

3.1.3 Data store dictionary

A data store is a repository for persistently storing and managing
collections of data which include not just repositories like databases, but
also simpler store types such as simple files, emails etc. A database is a
series of bytes that is managed by a database management system
(DBMS). A file is a series of bytes that is managed by a file system.
Thus, any database or file is a series of bytes that, once stored, is called a
data store.
3.1.4 Data flow dictionary
In computers, the path of data from source document to data entry to
processing to final reports. Data changes format and sequence (within a

12
 file) as it moves from program to program. In communications, the path
taken by a message from origination to destination that includes all
nodes through which the data travels.

Customers Administrator

Processor

Sellers

Electronic
Management System

Data source
3.2 Data design
3.2.1 Entities and Attributes
An entity relationship diagram is a means of visualizing how the
information a system produces is related. There are five main
components of an ERD:
Entities which are represented by rectangles. An entity is an object or
concept about which you want to store information

Entity
A weak entity is an entity that must defined by a foreign key
relationship with another entity as
it cannot be uniquely identified by its own attributes alone.

Entity

Actions, which are represented by diamond shapes, show how two

entities share information in the database

Entity

13
3.2.2 Database design
A database is a collection of information that is organized so that it can
easily be accessed, managed, and updated. In one view, databases can be
classified according to types of content bibliographic, full-text, numeric,
and images. a database is a list or group of objects organized to make the
list(s) and their values easy to create and manage. In the computer world,
this suggests, rightly, that the list(s) and (their) values are stored in a
machine. As information becomes highly important, almost every
company keeps some type of database, including its employees,
customers, or the products it sells.
Database design is the process of producing a detailed data model of
database. This data model contains all the needed logical and physical
design choices and physical storage parameters needed to generate a
design in a data definition language, which can then be used to create a
database. A fully attributed data model contains detailed attributes for
each entity.
The term database design can be used to describe many different parts of
the design of an overall database system. Principally, and most correctly,
it can be thought of as the logical design of the base data structures used
to store the data. In the relational model these are the tables and views.
In an object database the entities and relationships map directly to object
classes and named relationships. However, the term database design
could also be used to apply to the overall process of designing, not just
the base data structures, but also the forms and queries used as part of the
overall database application within the database management system
(DBMS).
The database design process generally consists of a number of steps
which will be carried out by the database designer. Usually, the designer
must:
1) Determine the data to be stored in the database.
2) Determine the relationships between the different data elements.
3) Superimpose a logical structure upon the data on the basis of these
relationships

14
3.2.2.3 create an initial ERD

3.2.2.4 assign all data elements to entities

3.2.2.5 create 3NF designs for all tables, taking care to identify all
primary and foreign keys
Normalization is the process of organizing a database to reduce redundancy
and improve data integrity.
Normalization also simplifies the database design so that it achieves the
optimal structure composed of atomic elements (i.e. elements that cannot
be broken down into smaller parts).
Also referred to as database normalization or data normalization,
normalization is an important part of relational database design, as it
helps with the speed, accuracy, and efficiency of the database.
By normalizing a database, you arrange the data into tables and columns. 
You ensure that each table contains only related data. If data is not
directly related, you create a new table for that data.

15
For example, if you have a “Customers” table, you’d normally create a
separate table for the products they can order (you could call this table
“Products”). You’d create another table for customers’ orders (perhaps
called “Orders”). And if each order could contain multiple items, you’d
typically create yet another table to store each order item (perhaps called
“Order Items”). All these tables would be linked by their primary key,
which allows you to find related data across all these tables (such as all
orders by a given customer).

Benefits of Normalization

There are many benefits of normalizing a database. Here are some of the
key benefits:

 Minimizes data redundancy (duplicate data).

 Minimizes null values.
 Results in a more compact database (due to less data
redundancy/null values).
 Minimizes/avoids data modification issues.

First normal form (1NF) is a property of a relation in a relational database. A

relation is in first normal form if and only if no attribute domain has
relations as elements. Or more informally, that no table column can have
tables as values (or no repeating groups). Database normalization is the
process of representing a database in terms of relations in standard
normal forms, where first normal is a minimal requirement. SQL-92 does
not support creating or using table-valued columns, which means that
using only the "traditional relational database features" (excluding
extensions even if they were later standardized) most relational databases
will be in first normal form by necessity. Database systems which do not
require first normal form are often called no sql systems. Newer SQL
standards like SQL:1999 have started to allow so called non-atomic types,
which include composite types. Even newer versions
like SQL:2016 allow json.
This table over customers' credit card transactions does not conform to
first normal form.
Second normal form (2NF) is a normal form used in database
normalization. A relation is in the second normal form if it fulfills the
following two requirements: It is in first normal form. It does not have
any non-prime attribute that is functionally dependent on any proper
subset of any candidate key of the relation.

16
 third normal form (3NF) is a normal form used in database normalization.
3NF was originally defined by E. F. Cod in 1971.[2]
Cod’s definition states that a table is in 3NF if and only if both of the
following conditions hold:

 The relation R (table) is in second normal form (2NF).

 Every non-prime attribute of R is non-transitively dependent on every
key of R.

3.2.2.4 generate the final ERD that will include new entities
identified during normalization

17
3.3 Interface & Screens Design

3.4 Input, Output & report Design.

New Clear Button

Save Save Button

Update
Update Button

Delete
Delete Button

18
 Chapter Four
Project Implementation
4.0 Introduction:
Project implementation (or project execution) is the phase where visions
and plans become reality. This is the logical conclusion, after evaluating,
deciding, visioning, planning, applying for funds and finding the
financial resources of a project. Technical implementation is one part of
executing a project.
4.1 Application Development
4.1.1 modules
Login from:
This form allows you to enter the project and needs you to enter
username and password to enter the project, if you type incorrect
username or password you can enter the project so its security form.

login Form code

When you passed the login form you will come and show main Form.
Main form consists of all form in our system, such as register customer,
orders, items and etc.
SqlConnection cn = new SqlConnection("Data Source=DESKTOP-1IH0L1E;Initial
Catalog=Project;Integrated Security=True");
string str = "Select * from Users where UserName='" + TXTUsername .Text.Trim() + "' and
Password='" + TXTPassword .Text.Trim() + "'";
SqlDataAdapter da = new SqlDataAdapter(str, cn);
DataTable dt = new DataTable();
da.Fill(dt);
if (dt.Rows.Count == 1)

19
Main from:

Main Form code:

private void Home_Load(object sender, EventArgs e)

{
}
private void pictureBox2_Click(object sender, EventArgs e)
{
Application.Exit();
}
private void metroLabel1_Click(object sender, EventArgs e)
{
Dashboard cc = new Home();
cc.Show();
this.Hide();
}
private void metroLabel2_Click(object sender, EventArgs e)
{
Customers f2 = new Customers ();
f2.Show();
this.Hide();
}
private void metroLabel3_Click(object sender, EventArgs e)
{
Orders f1 = new Orders ();
f1.Show();
this.Hide();
}

20
Screen Loading:

namespace TAFEY2022
{
public partial class ScreanLoading : Form
{
public ScreanLoading()
{
InitializeComponent();
}

private void ScreanLoading_Load(object sender, EventArgs e)

{

private void timer1_Tick(object sender, EventArgs e)

{
panel2.Width += 3;
if (panel2.Width >= 599)
{
timer1.Stop();
LoginForm Fm2 = new LoginForm();
Fm2.Show();
this.Hide();
}
}
}
}

Screen Loading code

21
 4.1.2Refer to DFDs, process description, ERDs
• DFD, or Data Flow Diagram, is a graphical representation of the
flow of data through an information system. DFDs show the movement
of data between different processes and components in a system and can
be used to provide a high-level view of how a system works. DFDs are
typically used during the design phase of a project, to help communicate
how data will flow through the system.
• However, they can also be useful for troubleshooting and
understanding how information flows within an existing system. DFDs
can be drawn using a variety of methods, including diagrams, charts, and
tables. Regardless of the method used, all DFDs should include four
basic elements: process nodes, data stores, data flows, and external
entities. These four elements will be further discussed below.
• Process nodes: Process nodes are symbols that represent the
various processes in a system. In most DFDs, process nodes are
represented by rectangles. Data stores: Data stores are symbols that
represent places where data is stored within a system. Data stores can be
physical (e.g., a database) or logical (e.g., an in-memory cache).
• ERD is a database modeling technique that is used to generate a
conceptual data model for a system. ERD diagrams represent the
relationships between entities in a system. These relationships can be
one-to-one, one-to-many, or many-to-many. ERD diagrams are typically
used in conjunction with other techniques, such as data flow diagrams
(DFDs) and entity relationship diagrams (ERDs), to create a complete
picture of a system. ERD diagrams are also sometimes referred to as ER
models.

Customers Payment Customers

Goods

Sales Order Sales invoice

Inquiry

Quotation

Order Management
System

22
4.2 User manual
The system will have user accounts for its users. The passwords will be
encrypted. To protected and will be kept for access to the system.
There is no such functionality in the system by which the user can
register himself to the system.
This is because there are only five users in the system apart from the
system administrator, so the user accounts are created by the system
administrator.
The system administrator can activate, deactivate, create, edit and delete
user accounts, because
every once in a number of years the user 1 or the user 2 may be changed,
but the user names for them will be constant. The new user will have to
do is to change the passwords for Him/herself.

23
 Chapter Five
Project Conclusion
5.1 Future work:
We will be upgrading with new visions and design that better than this
part Now we can’t able to upgrading due to time and our techniques
when we reach our hope We will produce new versions that is the best
this one this software will make more update in reality for all that
reasons it made to make an update placed and make advanced this
software works only offline It may have not attractiveness graphical
interface that attractive with the user, for the future will update it and we
will add more additional interfaces that make the software more
attractive.
The interfaces that will update is:
 Graphic interface
 Labels and their interfaces
 Controls and their interface structure
 Colors and user interfaces
The system of design it will be need to edit, remove and save more
extra thing like:
 Camera
5.2 Conclusions:
The system has been developed using C# and SQL Server, the system
was able to process and update the database with more ease. It helped in
developing a total integrated system.
This the project “Canadian Dental Management System” can be altered
in accordance with the future requirements of the organization. After we
have completed the project we are sure the problems in the existing
system would Overcome. The “Canadian Dental Management System”
process made computerized to reduce human errors and to increase the
efficiency. The main focus of this project is to lessen human efforts. The
maintenance of the records is made efficient, as all the records are stored
in the SQL SERVER database, through which data can be retrieved
easily. The navigation control is provided in all the forms to navigate
through the large amount-of records. If the numbers of records are very
large then user has to just type in the search string and user gets the
results immediately. The editing is also made simpler. The user has to
just type in the required field and press the update button to update the
desired field.

5.3 Reference
Online collecting information
http://www.google.com
http://www.youtube.com

24