abija project

38
PROJECT TITLE: NETWORKING SYSTEM DEVELOPER: SCOPAS GORINWA SAMUEL CARD NUMBER: 22-329 SUBMITTED TO: MISS.CHEBET JOURNAL: FINAL FULFILLMENT COURSE UNIT DATE: 5 TH -DECEMBER-2010 COURSE: INFORMATION COMMUNCATION TECHNOLOGY LEVEL: ADVANCE DIPLOM Scopas Gorinwa Samuel Page 1

Upload: abija-samuel

Post on 06-Apr-2018

223 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 1/38

PROJECT TITLE: NETWORKING SYSTEM

DEVELOPER: SCOPAS GORINWA SAMUEL

CARD NUMBER: 22-329

SUBMITTED TO: MISS.CHEBET

JOURNAL: FINAL FULFILLMENT COURSE UNIT

DATE: 5TH-DECEMBER-2010

COURSE: INFORMATION COMMUNCATION TECHNOLOGY

LEVEL: ADVANCE DIPLOM

Scopas Gorinwa Samuel Page 1

Page 2: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 2/38

DECLARATIONThis project report is my original work and protected under copyright, it is cover final

completion of the course unit and Graffins college Examination body.

Scopas Gorinwa Samuel Page 2

Page 3: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 3/38

ABSTRACTThe purpose of this paper is to introduce a starting point for the sharing of information and

knowledge among Department within the organization. This will be accomplished by applying

 practice related to the concept of networking system, a widely acclaimed business practice that is being pursued in thousands of corporations across the world.

By applying the principles of networking system and, specifically-it will create better performance in both individual professionals and the entire organization as awhole.

-the aim to prove that the establishment of a knowledge-based system in which organization

 professionals throughout the Department can share knowledge and information will facilitatehow the professionals solve problems and challenges.

-it will automate the organization process.

Although this project only begins the study into the application of networking system principlesto the organization, it offers insight into what is needed to share, transfer, and create knowledge

in order to advance the organization field.

Scopas Gorinwa Samuel Page 3

Page 4: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 4/38

PREFACEAs the world turns to networking system, companies and organizations are changing to

accommodate the shift by implementing computer manipulated systems and internet services.

These systems are designed to:

Make-work easier for the company hence more workload can be done with less effort.Eradicate the manual system of carrying out operations.Increases an organization profits and minimize on the costs they incur.

Make the transaction of information across the organization easier.

Make the communication easier with other organization across the country.

This system is easy to learn, user friendly and time conserving hence efficient and effective

management of the networking system.

Scopas Gorinwa Samuel Page 4 

Page 5: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 5/38

ACKNOWLEDGEMENTSI would like to give my appreciation to the many people who have contributed to the successful

completion of this system. Most especially, I thank my lecturers at Graffins College, Miss.

Chebet for her invaluable assistance in developing the system and who greatly influenced thesystem and also this manuscript. I also acknowledge the material and moral support offered to

me by my friends throughout the system development period.I want to thank my reviewers, who have made many helpful suggestions:

Miss. Chebet

Lecturer Graffins College

Scopas Gorinwa Samuel Page 5

Page 6: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 6/38

Table of ContentsDECLARATION .............................................................................................................................2

ABSTRACT ..................................................................................................................................... 3PREFACE ........................................................................................................................................ 4

ACKNOWLEDGEMENTS ............................................................................................................. 5Table of Contents ............................................................................................................................. 6

CHAPTER 1 .................................................................................................................................... 8

1.1 INTRODUCTION .................................................................................................................8

1.2 OBJECTIVE .......................................................................................................................... 8

1.3 ACADEMIC ..................................................................................................................... 8

1.4 PERSONAL ........................................................................................................................... 8

1.5 BUSINESS PURPOSES ........................................................................................................8

1.6 AIM ........................................................................................................................................8

1.7 PROBLEM STATEMENT .................................................................................................... 9

1.8 JUSTIFICATION ..................................................................................................................9

1.9 CONSTRAINTS .................................................................................................................... 9

.................................................................................................................................................... 10

1.10 DELIVERABLES ..............................................................................................................10

1.11 MAJOR MILESTONES ................................................................................................10

1.12 Resources: Budget .............................................................................................................11

1.13 RISK PLAN .......................................................................................................................11

CHAPTER 2 ..................................................................................................................................12LITERATURE REVIEW .......................................................................................................... 12

CHAPTER 3 ..................................................................................................................................14

3.1 FEASIBILITY STUDY .......................................................................................................14

3.2 Terms of Reference ..............................................................................................................14

3.3 Technical feasibility .............................................................................................................14

3.4 Economic feasibility ............................................................................................................ 14

3.5 RESEARCH METHODOLOGY .........................................................................................15

3.6 INTRODUCATION ............................................................................................................ 15

CHAPTER 4 ..................................................................................................................................16

4.1 REQUIREMENTS ANALYSIS AND SPECIFICATIONS ...............................................16

4.2 HARDWARE REQUIREMENT .........................................................................................16

4.3 SOFTEWARE REQUIRMENT ..........................................................................................16

4.4 USER REQUIREMENT ......................................................................................................16

Scopas Gorinwa Samuel Page 6 

Page 7: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 7/38

CHAPTER 5 ..................................................................................................................................17

5.1 SYSTEM ANALYSIS AND DESIGN ................................................................................17

5.2 INTRODUCTION ............................................................................................................... 17

5.3 SYSTEM DESCCRIPTION ................................................................................................17

5.4 SYSTEM DESIGN ..............................................................................................................185.5 LOGICAL DEDIGN ............................................................................................................18

5.6 PHYSICAL DESIGN ..........................................................................................................19

5.7 OUTPUT DESIGN ..............................................................................................................19

5.8 INPUT DESIGN ..................................................................................................................19

5.9 Tasks to be tackled ...............................................................................................................20

5.10 WBS (Work Breakdown Structure) .......................................................................................215.11 PROPOSED SYSTEM FLOWCHART ................................................................................21

5.12 PROPOSED SYSTEM FLOWCHART ................................................................................22

5.13 Connection Flowchart ........................................................................................................235.14 Network topology Flowchart .............................................................................................24

5.15 Home page .............................................................................................................................25

CHAPTER 6 ..................................................................................................................................266.1 INTERFACE CODING PROGRAM ..................................................................................26

6.2 System connection ...............................................................................................................26

6.3 Network topology ................................................................................................................ 28

CHAPTER 7 ..................................................................................................................................30

7.1 TESTING AND IMPLEMENTATION .............................................................................. 30

7.2 Testing ..................................................................................................................................30

7.3 Implementation ....................................................................................................................31

7.4 Training ................................................................................................................................31

CHAPTER 8 ..................................................................................................................................33

MAINTENANCE .....................................................................................................................33

CHAPTER 9 ..................................................................................................................................36

USER MANUAL ......................................................................................................................36

CHAPTER 10 ................................................................................................................................37

10.1 GLOSSARY .................................................................................................................... 37

10.2 sBIBLIOGRAPHY ............................................................................................................37

Scopas Gorinwa Samuel Page 7 

Page 8: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 8/38

CHAPTER 1

1.1 INTRODUCTIONThis section provides basic introduction to networking system, what is networking system,

Ethernet overview, LAN/WAN technology, internet communication system and basic LAN

concepts. The term “networking system” in computing system means two or more computersconnected each other to form a network and networking means two or more computers

connected with each other and sharing data and resources. Today every business in the worldfrom banking to airlines offices, corporate organizations, postal services, universities and a even

a home where there are two or more computers, need a network to communicate with other 

 people. With the passage of time, the network technology has adopted many new standards and

many inventions in this industry are on their way to provide the maximum advantages accordingto the needs of every business.

1.2 OBJECTIVEThere are many objectives I hope to achieve by the completion of this project.

1.3 ACADEMICThis project will help a great way in achieving and increasing my knowledge in many topics that

I have been taught theortically.It will help me to learn how to use usability principle to create anetworking system as well as advance my knowledge in designing and developing.

1.4 PERSONAL

The Networking system will be a plate from for me to challenge myself to reach height level thatI may not have pursued before hope this project will enable me to learn my capabilities and

limitation with networking system in mind.

1.5 BUSINESS PURPOSESComputerize information processing and provision to be automatic can even work without

human intervention.

-To improve on record keeping procedures especially in data entry.

-To facilitate easier information retrieval e.g. student details and employee files.

1.6 AIMThe purpose of this project is to develop a networking management information system within

the organization or any institution, which brings into the existing environment, automatedoperations and hence realizes efficiency tabulating into more technology and works.

The project also sets out to incorporate a website that will be able to allow for online programs

hence increase convenience.

Scopas Gorinwa Samuel Page 8

Page 9: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 9/38

1.7 PROBLEM STATEMENTIn the organization industry there is a need to evolve the way data and information are handled

and manipulated. Old conventional methods are ineffective in many ways. Some of the

challenges posed by the use of these methods of record keeping at the organization include:Orders are processed slowly and therefore less orders are processed this in turn means reduced

revenue. Handling of orders manually is a tedious and slow process.Work of keeping employee records, organization report, and losses is currently done manually atorganization making it a slow tedious process.

Other problems are highlighted below:

The Manual system requires human control for information processing and output.

Large numbers of files and papers which consume valuable space.Difficulties in retrieving employee, suppliers and other queries concerning their pertinent details

Tedious and time consuming reports generation.

Sloppy data recorded on paper.When all these problems are considered, there Is therefore need to develop, install and maintain a

system that will decrease if not eliminate these problems therefore increasing productivity.

1.8 JUSTIFICATIONMost of the operations and activities in the organization are done using traditional methods

leading to lot of paper work, data redundancy, extra labor, slowed records retrieval and reports

generation and high possibilities of inaccurate information concerning the organization activities.Most of the records keeping activities are done on paper leading to a number of problems which

include.

Searching for records is tedious since there is no set procedure for finding data from the

voluminous files especially those concerning employee or stock details. This will be changed byuse of queries to retrieve information at the click of a button.

The whole record keeping process is time consuming. Time will be saved since creating,

updating, and retrieving records will be computerized.Misplacement of records as they move from one department to another will be a thing of the past

since there will be a centralized database and workstations from where information will be

accessed easily and readily. No backup for the files such that in cases of a natural disaster like fire all the records are lost.

Back up will be simplified with the use of only a CD or a DVD per session which will be twice a

week.The information kept is prone to errors. Human error will be eliminated since the system will be

thoroughly tested and users will have error messages whenever a mistake is made.

Security of data will be enhanced with the use of password protection among other means.

This managements system aims to eliminate such problems and instead ensure accuracy,availability and security of all the information kept or processed. Above all, it helps all in the

organization from the manager, accountants, CEO and floor staff to develop relevant computing

skills vital in today’s worlds.

1.9 CONSTRAINTSIn any project there are mainly two major constraints .they affect fully the success of the projectthese constraints are:

Scopas Gorinwa Samuel Page 9

Page 10: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 10/38

Time and resources

Time-limited resource considerations

In this case emphasis will be placed on completing the project within a specified time. This timewill usually have been determined by analysis. Adjustments in the timing of any activity, and the

resources required at a given time, must be undertaken within the float (slack) available.

Obviously there can be no adjustment of activities which are on the critical path.The time constraint is critical in the successful completion of this project. The time allocated is

considerably limited (2 and ½ months) for me to complete this project successfully I must utilize

this resource carefully.Resource-limited resource considerations

In this case the project must be completed with the resources available even if this means

extending the project duration. If the total resource demand exceeds the resource availability at

any time then some of the activities must be delayed until there is sufficient resource availability

.

1.10 DELIVERABLES

The networking management system is suggested as a solution of the long experienced problems in record keeping and information provision at the business venture. It is a system that

will help in keeping track of all the records within the restaurants key departments. The key areas

of focus will be:

Accounts office – it will help them in calculating transactions, profits and losses and other key

financial records.

Management – managers will be able to manage employees and retrieve at will all the records

that they may need in making decisions useful to the restaurant.

Event managers- will be able to plan events and coordinate with other departments to make the

necessary arrangements.

1.11 MAJOR MILESTONES

There are milestones I plan to achieve in the development of this system, each will be considered

a success once completed within the stated time period.Some of major milestones and the time I will have achieved include:

Deliverable Approximate Time for  

Milestone

Delivery Date

Project Proposal 1 week 15

th

October, 2010Project Plan 1 week 20th October, 2010

Literature review 2 weeks 25th October,2010

Interim project report three weeks 17th November,2010

Scopas Gorinwa Samuel Page 10

Page 11: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 11/38

Final report and presentation Two weeks 8th December,2010

1.12 Resources: BudgetItem Amount

Cables 20.000Computers 500.000

Printers 100.000

Scanner 60.000

Hubs, Switches and Routers 60.000

RJ45 10.000

Network administrators 90.000

Tools 25.000

Total 865.000

1.13 RISK PLANRISK PROBABILITY ACTION

Power blackout during project

development

3 Work at home or at the

cyber cafe

Computer Virus attack 3 Install anti-virus and scan

all storage devices before being used on the

computer 

Time limited 1 Ask for an extension

Inaccurate information 3 Search on the web and

 perform backgroundchecks

Computer crash 4 Backup

Scopas Gorinwa Samuel Page 11

Page 12: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 12/38

CHAPTER 2

LITERATURE REVIEWLiterature review of networking system in the an organization

Organization practitioners and researchers have recently turned their attention to networkingsystem. As mechanisms for bringing organizations together to address met problems, network 

system offer benefits such as pooled resources, improved communications, development of competencies, and potential for innovation, as well as increased legitimacy and status within the

community. While network system offer promise, they have been little studied within the

organization field. Disciplines such as social ecology, computer science, management, and

 political science have paid some attention to network system. However, significant gaps in theliterature remain. The rationale for this review includes the need to identify gaps in existing

research, determine new directions for study, and primarily to assist network members in

understanding the network concept for effective development and evaluation of their networks.This review was developed for the organization management Network. It Provides practitioners,

researchers, and evaluators with an overview of networks addressing issues such as whynetworks exist, and how they operate. The vision, structure, functions and service deliveryaspects of networks are discussed. In addition, this review identifies several outcome measures

for evaluation of networks. Four levels of analysis for evaluation are suggested: Community,

 Network, Organization, and Individual. A summary of network concepts and issues is provided.

Technological Aspects networking system

Many organizations rely heavily on computers, intranets, and the internet for knowledge

 packaging. In fact, much of the credit for the widespread use of networking system theories and practices must go to the development of the worldwide web because the internet has made the

world increasingly smaller in its short history. The internet began in 1969 as a Pentagon-

sponsored program called the Advanced Research Projects Agency. It began as a looseconfederation of interconnected computer networks to help military contractors share large sets

of data. By the early 1980’s, universities and research laboratories were using it as well. With

the transition from mainframe computers to personal computers in the mid to late 1980’s, businesses began to use the internet too. By 1997, there were more than 35 million users. The

surge in information flow and connectivity has allowed individuals and organizations to share a

great volume of information and knowledge in a manner that had never been possible.

Information technology has become a key in the implementation of networking system. “IT’srole is emerging as an integrator of communications technology, rather than solely a keeper of 

information. The critical role for IT lies in its ability to support communication, collaboration,

and those searching for knowledge and information. Information technology and the advent of 

the personal computer have greatly enhanced organizational effectiveness, interorganizationaldeployment, and cognitive advance (Grover and Davenport, 2001, p. 6). Another area of 

communication that information technology has drastically impacted is social activity.Computer networks provide a means to break down stovepipes, or hierarchical barriers, that

often inhibit the flow of free thinking, knowledge, and innovation, or the creation of knowledge.

There are, however, some difficulties caused by the use of information technology in knowledge

management practices. First of all, information technology leads to misconceptions about thedifferences between information and knowledge. Organizations often store heavy loads of 

Scopas Gorinwa Samuel Page 12

Page 13: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 13/38

information or data and mistakenly think they are fostering the flow of knowledge. “Quite a few

of these projects include work focused on data warehousing, installation of Lotus Notes, building

intranets and developing document and intellectual capital applications—all of which bear adefinite but somewhat distant relationship to knowledge”. A second challenge occurs when

organizations view knowledge work as done once the information technology application

 becomes technologically operational. In reality, this is just the beginning of the knowledge project. Constructing an information technology infrastructure for knowledge does not, in itself,

guarantee that organization members will use the system. Finally, some organizations rely too

heavily on information technology and not enough on the social aspects of sharing knowledge.

Scopas Gorinwa Samuel Page 13

Page 14: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 14/38

CHAPTER 3

3.1 FEASIBILITY STUDY 

is an evaluation of a proposal designed to determine the difficulty in carrying out a designated

task of the project overview or analysis of the potential impact of a proposed project.

3.2 Terms of Reference

To investigate and report on the existing system, its procedures and costs.

To define the system requirements.

To establish whether these requirements are being met by the existing system.

To establish whether they could be met by an alternative system.To recommend the most suitable system to met the systems’ objectives.

The feasibility study concentrated on three major areas of the project i.e. technically,economically and operationally.

3.3 Technical feasibilityThe assessment is based on an outline design of system requirements in terms of Input,Processes, Output, Fields, Programs, and Procedures. This can be quantified in terms of volumes

of data, trends, frequency of updating, etc. in order to estimate whether the new system will

 perform adequately or not. Technical feasibility is carried out to determine whether the companyhas the capability, in terms of software, hardware, personnel and expertise, to handle the

completion of the project.

3.4 Economic feasibilityEconomic analysis is the most frequently used method for evaluating the effectiveness of a newsystem. More commonly known as cost/benefit analysis, the procedure is to determine the

 benefits and savings that are expected from a candidate system and compare them with costs. If 

 benefits outweigh costs, then the decision is made to design and implement the system. Anentrepreneur must accurately weigh the cost versus benefits before taking an action.

Cost-based study: It is important to identify cost and benefit factors, which can be categorized as

follows:Development costs

Operating costs.This is an analysis of the costs to be incurred in the system and the benefits derivable out of the

system.Time-based study: This is an analysis of the time required to achieve a return on investments.

The future value of a project is also a factor.

Operational feasibility

Scopas Gorinwa Samuel Page 14 

Page 15: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 15/38

Operational feasibility is a measure of how well a proposed system solves the problems, and

takes advantage of the opportunities identified during scope definition and how it satisfies the

requirements identified in the requirements analysis phase of system development.

3.5 RESEARCH METHODOLOGY 

3.6 INTRODUCATION

Research can be defined as the search for knowledge, or as any systematic investigation, with anopen mind, to establish novel facts, usually using a scientific method. The primary purpose for 

applied research (as opposed to basic research) is discovering, interpreting, and the development

of methods and systems for the advancement of human knowledge on a wide variety of scientificmatters of our world and the universe.

Research Methodology

- is the analysis of the principles of methods, rules, and postulates employed by adiscipline.

-the systematic study of methods that are, can be, or have been applied within a discipline.-is the study or description of methods-Research Methodology can be defined as a systematic and orderly procedure or process for 

attaining some objective.

METHODOLOGY

Some of the methods that will be used in the development of this system include:

Data collection methods

System development methods

DATA COLLECTION METHODS

Many methods will be used to collect data relevant to the development of the system, successfulimplementation and completion of this project, they include;

Use of questionnaires to gather information from proposed users of this system Observation of 

the staff to see how information is handled at the organization. These among others will be usedto gather information that will be needed in the new system.

Scopas Gorinwa Samuel Page 15

Page 16: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 16/38

CHAPTER 4

4.1 REQUIREMENTS ANALYSIS AND SPECIFICATIONSRequirements Analysis is the process of understanding the customer needs and expectations from

a proposed system or application and is a well-defined stage in the Software and hardware

Development Life Cycle model. Requirements are a description of how a system should behaveor a description of system properties or attributes. It can alternatively be a statement of ‘what’ an

application is expected to do.

4.2 HARDWARE REQUIREMENT

• Main Frame PC• At least 4 GB of Memory (RAM)

• At least 4 GB Processor 

• 350 GB of Hard disk space•

Backing storage facility•  Network cables

•  Network card• Switch, Hub and Router 

• Printer 

• Scanner 

4.3 SOFTEWARE REQUIRMENT

• Application Package server software• Database Management package such as MySql• A graphical user interface such as Windows 97,7, 2000, XP.

•  Network drivers

• Anti virus• Firewall

4.4 USER REQUIREMENT

Use cases are strongly recommended to be used in documenting user requirements. The

following sections are typically included in use case descriptions:

•  Name: Unique name of the use case (the same as the name in the use case diagram)• Summary: Short description of the use case• Actors: List of users and the other systems that interacts directly with a system

• Preconditions: Description of "start situation" and goals of the users• Basic sequence: Description of main actions• Exceptions: Descriptions of special situations, violations of organization rules etc.

• Post conditions: Description of "end situation"

• Priority

Scopas Gorinwa Samuel Page 16 

Page 17: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 17/38

CHAPTER 5

5.1 SYSTEM ANALYSIS AND DESIGN

5.2 INTRODUCTIONSystems are created to solve problems. One can think of the systems approach as an organized

way of dealing with a problem. In this dynamic world, The subject System Analysis and Design,

mainly deals with the software development activities.

After going through this, you should be able to:

• understand a system• understand the different phases of system developments life cycle• know the components of system analysis

• know the components of system designing.

5.3 SYSTEM DESCCRIPTION Manual System

This is the current system in the organization, which tends to be loaded with disadvantages rather than advantages. These demerits are:

•  Slow: The manual system is very slow since humans do every work manually. The

workload involved in the company system is quite a lot especially at peak times hence the

need for more manpower, which is costly. The time consumed while dealing with thecustomer is a lot since to cater for every customer one would need to write all the

information supplied by the customer.•  Expensive: Since with the manual system everything has to be done manually, it requires

a lot of people and you have to pay for it. Also long hours at work are required and the

company will have to pay the workers for overtime they have worked and overtime is

 paid at a higher rate than normal working hours.•  Insecurity: With the manual system, it’s very hard to secure the company’ documents.

Since you can’t have passwords on paper to safeguard your documents, everything that

contains sensitive information has always to be under lock and key.•  Resources: To keep all the records of the company, extra space will be required and so

there is need to increase storage area, which is an incurred resource.

• Computerized system

• In the day today activities, most of the organizations are finding it more useful for themto networking their systems. This is because if they don’t networking or computerizetheir systems, they will end up losing a lot of business to other companies that have

networking or computerized their systems. The merits are:

•  Improved Productivity: Work done on computers is much higher quality than work donemanually.

Scopas Gorinwa Samuel Page 17 

Page 18: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 18/38

• Fast: Working on a computer is much faster than working manually. A computer can

handle a lot of work compared to human being capacity to handle the workload. A lot of 

errors are also reduced when it comes to a networking or computerized system.•  Security: With a networking or computerized system, information is more secure since

 passwords can be set on certain documents that are not to be viewed by every individual

in the company. Access rights can also be granted so that certain people are restrictedfrom accessing certain files.

•  Effective and efficient : Networking or Computerization of an organization affects

 business in a positive manner since the services are improved hence gaining an advantageover other businesses. Also an organization attracts more customers since the system

 being used is efficient enough to provide the required services.

 Networking system Web-based Management software describes the tools to design and manageall facets of an

 Networking system, providing the workers with simple and rewarding purchasing experience,

software ranges from affordable, designed for small business owners, to fully customizable

solutions for high volume businesses. Networking system Web-based Management software typically offers design tools that were put

into practice.Mysql, c++, java, Firewall, used to model and generates the system due to its efficiency that

allows information within the database to be retrieved and manipulated with ease.

Also designed will be the user interface and various forms used to get input data from the user 

and to display them.The Networking or computerized system is a similar in operation to the manual system although

more efficient. To be able to use it, the user must have basic computer skills for example on data

entry, backup methods, network repair, and computer fault handling and troubleshooting.

5.4 SYSTEM DESIGN

Based on the user requirements and the detailed analysis of a new system, the new system must be designed. This is the phase of system designing. It is a most crucial phase in the development

of a system. Normally, the design proceeds in two stages. Logical design and physical design

5.5 LOGICAL DEDIGNThis design describes what the system will do and not how it will do it. It utilizes the following:

Flowcharts

Data Flow diagramsEntity Relationship Diagrams

In this case the following will be designed:Flowcharts: -

Home System Flowchart

Connection FlowchartNetwork topology Flowchart

Scopas Gorinwa Samuel Page 18

Page 19: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 19/38

Data Flow diagram: -

Home Data Flow Diagram

5.6 PHYSICAL DESIGN

This design describes the actual construction of interface, which will form the basis of input andoutput. It also entails the creation of a database that will link up with the interfaces.

The interfaces to be used are:

Home SystemConnection

 Network topology

5.7 OUTPUT DESIGN

Each organization shall establish and maintain procedures for defining and documenting outputdesign in terms that allow an adequate evaluation of conformance to design input requirements.

Output design shall be documented, reviewed, and approved before release. The approval,including the date and signature of the individuals approving the output, shall be documented.

The output is categorized into three groups: 

External results- these results are sent to people outside the organization.

Internal results- they are distributed within the organization.

Internal system results- this is the information relating to the operations relating to the system

itself.The design of the output should cover the following:

What output is to be produced?The speed at which output is produced. In some cases the output is urgently needed.The conditions given for the production of the output.

The amount of the output needed. The system designer should know whether the system could

handle the output needed by the organization.

5.8 INPUT DESIGN

Is the physical and performance requirements of a device that are used as a basis for device

design.The following points are considered when designing the input.

Volume of input to be handled by the new system.

Kind of input expected.The frequency of the input. Is the input daily, monthly, or annually?

Where data will be captured for input.

The input medium.Control Design

Scopas Gorinwa Samuel Page 19

Page 20: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 20/38

After the input design, a system analyst should take precaution so that the wrong information

will not be accidentally entered. This can be done under the data preparation control.Data preparation is practiced to make sure that:

Incorrect data is not entered.

Location of errors is simplified.A system is user friendly and easy to use.

Processing of the output is easy.

User Interface Design

This can also be referred to as Screen design since it mainly elaborates on the type of interface

required for a good system, its qualities and how it should look like.Screen designs should be made very user friendly and should not be poorly made. They should

 be easy to work with, straight to the point all the information needed must be catered for.

This includes:

Identification of the documentPurpose of the document

Organization of the documentContents of the document

Sequence of the data.

Work Breakdown Structure (WBS)

5.9 Tasks to be tackled

Feasibility Study

Is basically the test of the proposed system in the light of its workability, meeting user’srequirements, effective use of resources and .of course, the cost effectiveness.

Analysis

Assuming that a new system is to be developed, the next phase is system analysis. Analysis

involved a detailed study of the current system, leading to specifications of a new system.

 

System Design

Based on the user requirements and the detailed analysis of a new system, the new system must

 be designed.

Coding of systemAfter designing the new system, the whole system is required to be converted into computer 

understanding language.

Testing

Before actually implementing the new system into operations, a test run of the system is doneremoving all the bugs, to check whether the new system is working accurately.

Scopas Gorinwa Samuel Page 20

Page 21: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 21/38

Implementation

Is the stage of a project during which theory is turned into practice. During this phase, all the

 programs of the system are loaded onto the user's networking.

Maintenance

Is necessary to eliminate errors in the system during its working life and to tune the system to

any variations in its working environment.

Documentation

Provide a user manual for the users.

5.10 WBS (Work Breakdown Structure)

5.11 PROPOSED SYSTEM FLOWCHARTThis flowchart tries to explain the logical design of the whole system comprising of all the files

i.e.

Home System fileConnection

 Network topology

It helps one to understand the system requirements after the files have been encompassedtogether.

Scopas Gorinwa Samuel Page 21

NETWORKING SYSTEM WEB BASED

Feasibilitystudy/Anal

System

designSystemcoding

Input and

outputData based

and file

Implement

ationMaintenance

Documention

System

Testing

Interface

design

Page 22: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 22/38

5.12 PROPOSED SYSTEM FLOWCHART

Scopas Gorinwa Samuel Page 22

START

Home Page

Choice

SystemConnection

 Network topology

END

Page 23: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 23/38

5.13 Connection Flowchart

Pseudocode

Begin the sub-routineUser name

User password

Wire connection

Scopas Gorinwa Samuel Page 23

Choi

ce

Start

Home

 page

Cabling

connection

System

connection

End

Page 24: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 24/38

5.14 Network topology Flowchart

Pseudo code

Begin the sub-routine

User name

User password Network topology

Mark a connection type

Scopas Gorinwa Samuel Page 24 

Choi

ce

Home

 page

Star 

topology

 Network 

topology

End

Start

Page 25: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 25/38

5.15 Home page

Scopas Gorinwa Samuel Page 25

Page 26: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 26/38

CHAPTER 6

6.1 INTERFACE CODING PROGRAM

6.2 System connection

Scopas Gorinwa Samuel Page 26 

ssssssanner 

Page 27: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 27/38

Server 

A server computer is a computer , or series of computers, that link other computers or electronic

devices together. They often provide essential services across a network, either to private usersinside a large organization or to public users via the internet. For example, when you enter a

query in a search engine, the query is sent from your computer over the internet to the servers

that store all the relevant web pages. The results are sent back by the server to your computer.Hub 

Is a common connection point for devices in a network . Hubs are commonly used to connect

segments of a LAN. A hub contains multiple ports. When a packet arrives at one port, it iscopied to the other ports so that all segments of the LAN can see all packets.

Cable

is the medium through which information usually moves from one network device to another. In

this network connection unshielded twisted pair cable.

Unshielded Twisted Pair Connector

The standard connector for unshielded twisted pair cabling is an RJ-45 connector. This is a

 plastic connector that looks like a large telephone-style connector.

Printerit is for printing file and document within an organization. Printer is connecting in networking

environment to link one or more computer in the network so that to make the work easier withthe company.

Modern

A modem links organization network to the Internet through your Internet Service Provider 

(ISP). The high speed types of data outside of your home aren't suitable for your direct use, somodems convert the data into digital Ethernet, which all the network equipment in organization

can use.

Scopas Gorinwa Samuel Page 27 

Page 28: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 28/38

6.3 Network topology

Star topology

In local area networks with a star topology, each network host is connected to a central hub. Incontrast to the bus topology, the star topology connects each node to the hub with a point-to-

 point connection. All traffic that traverses the network passes through the central hub. The hub

acts as a signal booster or repeater. The star topology is considered the easiest topology to designand implement. An advantage of the star topology is the simplicity of adding additional nodes.

Scopas Gorinwa Samuel Page 28

Page 29: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 29/38

A point-to-point link (described above) is sometimes categorized as a special instance of the

 physical star topology – therefore, the simplest type of network that is based upon the physical

star topology would consist of one node with a single point-to-point link to a second node, thechoice of which node is the 'hub' and which node is the 'spoke' being arbitrary.

After the special case of the point-to-point link, as in note 1.) above, the next simplest type of 

network that is based upon the physical star topology would consist of one central node – the'hub' – with two separate point-to-point links to two peripheral nodes – the 'spokes'.

Although most networks that are based upon the physical star topology are commonly

implemented using a special device such as a hub or switch as the central node (i.e., the 'hub' of the star), it is also possible to implement a network.

Star networks may also be described as either  broadcast multi-access or no broadcast multi-

access (NBMA), depending on whether the technology of the network either automatically

 propagates a signal at the hub to all spokes, or only addresses individual spokes with eachcommunication.

Scopas Gorinwa Samuel Page 29

Page 30: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 30/38

CHAPTER 7

7.1 TESTING AND IMPLEMENTATION

7.2 TestingTesting attempts to detect possible errors, that are in the completed system. Therefore, the

 purpose of testing is to identify all possible errors in the system and there by correct and prevent

future system malfunction. Testing is classified under different categories.This system was tested using both unit and system testing.

Unit testing is testing of functional units within a system as the main building blocks.

System testing is done after all the functional units are operating as expected hence

incorporating the hardware, software environment or operating system and the database.

This is concerned with proving the business functionality, usability and robustness of its software before it’s released to the user.

 

Correct Functionality

The software’s provides the functionalities specified by the user in the requirement

specifications, a failure to provide such functionalities may mean that key business processes can

not be carried out without appropriate system design changes has been made.User Friendliness

Although the networking may provide the required business functionality it must do so in such a

way that the user finds it easy to use. If the system is difficult or cumbersome to use, then theuser cannot utilize the business functionality.

 RobustnessThe software maybe functionally correct and user friendly but its quality is undermined if it

regularly crashes and so it’s unavailable for the user for significant amount of time.

Such failures will mean that the key functionality cannot be carried out and may casually affect

viability of the business.

User Acceptance Testing

It’s carried out to determine whether poor not the system meets the previously definedacceptance criteria. The aim is of/or the customer to determine whether or not to accept the

system.

The users usually carry out acceptance testing. However the purpose for this test is to;Find networking errors

Find out exactly what the demands of the new system are for users.

Find out whether the operating procedures are anticipated.

Scopas Gorinwa Samuel Page 30

Page 31: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 31/38

7.3 Implementation

The purpose of implementation is to translate the design documents into networking system that

can be used to carry out the intended processing tasks using the designated networking hardwareand software environments. The activities undertaken during system implementation are:

Testing• Coding

• Hardware Installation

• File conversion

• Documentation

• Changeover

• Staff Training

File Conversion

This refers to converting existing files into a suitable format for the new system. There are

various conversion strategies: Phased running- This is implementing the system in different phases i.e. after the completion of 

a certain phase; it is implemented for evaluation purposes.

 Direct Changeover - This is completely doing away with the old system and commencing the useof the new system.

 Parallel running - This is using the old system at the same time implementing the new system.

7.4 Training

Staff training in the use of networking technology is an important as the technology itself as

without effective operations at all levels computer systems. Training is not simply an issue that

affects the staff as people are used more and more as management tools

Training Strategy

Training strategies are determined by who is being trained and who will train them. The analystwill want to ensure that the appropriate trainer properly trains anyone whose work is affected by

the new information system.

Who to train: All people who will have secondary or primary use of the networking systemmust be trained. The amount of training a system requires thus depends on how much someone’s

 job will change because of the new system. You must ensure that users of different skill levels

and job interests are separated. It is certain trouble to include novices in the same training

sessions as experts, because novices are quickly lost and experts are rapidly bored with basics.

Training sources include:

• Lectures

• Discussion meetings• internal company magazine

• Handbooks

User Training

Users need a number of different ways of computer networking system training as outlined

 below.

Scopas Gorinwa Samuel Page 31

Page 32: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 32/38

Basic literacy in computers such as the concept of a file, use of packages and networking system,

what computers can do and what they cannot do. This can help users to know how to use the

system.Users need to know how the various applications with its departments operate. If the system is

complex such training gives users an overall view of the system, commands and procedures.

Users might sometimes need a refresher course especially if they don’t use particular applications.

Users need training while they operate certain applications on the training. This type of training

is usually very vigorous to ensure that users can interact very well with the system or thoseapplications.

Attending courses on the leading networking system provided by third party training

establishment.

Scopas Gorinwa Samuel Page 32

Page 33: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 33/38

CHAPTER 8

MAINTENANCE

The basic routine maintenance tasks are:Data backup 

Malware managementDaily maintenance

Weekly maintenance

Monthly maintenance

User data is unique to the installation and cannot be replaced 'off the peg', and for that reason it is

the central concern of system management. 

Data Backup

To data backup is to create a redundant copy, so that if anything should happen to the originalfile, you have recourse to the backup. The process can be as simple as copying files to diskettes, but this soon becomes a problem where files are too big for hard disk, where there are too many

files, or where too many hard disk are required.

A better solution is to use an archive (such as WinZip) or a backup utility to create a singlecompressed file from a collection of data files, and to split this over as many hard disk as

required.

Malware management

is a specialized network antivirus solution that allows you to protect from viruses not only a

 particular PC, but all computers in your network.

There's more on safe computing and malware. Malware includes viruses, worms, Trojans, andincreasingly invasive commercial applications, and management has several parts:

Risk avoidance and evaluation - choice of applications and system setup Risk avoidance and evaluation - user education and safe computing practice 

Risk detection and destruction - choice and use of antivirus software

Keeping abreast of malware - antivirus updates and ongoing user education

Simply running an antivirus utility is not enough, even if it is kept up to date!

For best performance, you can use on-demand rather than on-access antivirus scanners - but this

requires the user to know when to use this, and act accordingly.

Updating an antivirus generally involves these steps:Go to antivirus vendor's web site via (say) Internet Explorer 

 Navigate to the download section of the siteDownload any updates that are relevant, noting where these are saved

Extract files from downloaded archive to the antivirus program directory

Scopas Gorinwa Samuel Page 33

Page 34: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 34/38

Some Windows-based antivirus utilities may automate this process to some extent, by accessing

the Internet directly from within the program. You should check for updates at least once a week,

and make sure your antivirus data files do not become more than a month out of date.

Advantage of malware management.

Remote virus scanning. Save your time to visit each PC and check it for viruses. Insteadcheck all PCs at once by one mouse click.

• Silent remote virus cleaning. Cleanup remote PCs from found malware in a silent mode

without interruption of remote user work.• Regular network virus scan. Enable regular checks by spending only few minutes to scan

network for viruses with a fast scan engine.

• Weak shields detection. Get notification about remote PCs where antivirus protection is

disabled or virus databases are out-of-date.

Daily maintenance

These are routine tasks that should be performed on a daily basis. For the most part they amount

to simple monitoring, but this monitoring keeps you on top of your environment.

Verify that you can connect to each server in your Terminal Server cluster. This ensures that theservers are up and responding to client requests.

Check the server event logs. Checking the event logs on a daily basis lets you determine if thereare system or application problems on a server prior to it being reported by the user logging into

each server or selecting the servers in Event Viewer.

Check the help desk tickets for the day to see if any new problems are arising. If you have a large

help desk using help desk management software, see if they are able to denote any problems withthe Terminal Servers and send a report to you. This way you can identify problems with your 

server prior to them affecting everyone in the organization.

Clear out any hung or disconnected sessions to keep them from eating up valuable CPU andMemory on your server. If you have short timeouts on these settings, this could be changed to a

weekly task.

Weekly maintenance

The following tasks should be completed on a weekly basis. These tasks generally fall into the"monitoring and trend analysis" set of tasks, but should be done to ensure that the servers are

running properly and not seeing a huge increase in utilization.

Based on the monitoring tools you've set up (see the previous section on Server Monitoring),

gather a weekly report that shows the utilization for the week.If you don't have an automated system for it, update your antivirus definitions. Most companies

offer new updates once a week unless a severe virus is detected that requires an immediate

update to the definitions. Your best bet is to ensure that your Terminal Servers are updated atleast once a week. As always, remember that you should test new updates to be sure there is no

ill effect on the Terminal Servers.

Like it or not, you'll still need to reboot your Terminal Servers about once a week. Remember that these are not servers at all, but really workstations. Can you imagine not rebooting a user 

workstation for months on end?

Ensure that no users will be affected.

Scopas Gorinwa Samuel Page 34 

Page 35: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 35/38

Immediately after a reboot is a perfect time to "clean up" the server. Generally what is done to

the server at this point will depend on the applications you're running.

Monthly maintenance

Check for any new hot fixes, security updates, print driver changes or other system updates that

are required once a month.If you're still not using third-party printer software, install any new print drivers into the cluster.

Check the current hot fixes and service packs that are available from Microsoft. Finding the new

security fixes and "critical updates" can be done using Windows UpdateSchedule applications updates or changes.

Scopas Gorinwa Samuel Page 35

Page 36: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 36/38

CHAPTER 9

USER MANUALThis provides a guide on how to use computerized networking system and will train the user on

the routine operations and maintenance of the system. 

Overview

The system has been created for increased ease of use through additional of menus for thevarious functions required. There are various buttons for running commands that have been

given relevant names to the functions they perform for increased ease of use. The error messages

when a wrong action is performed are friendly and easy to understand.

System Requirements

• Software

• Window based operating system• Server 8

 Network driver • Hardware• Personal computer or desktop computer 

• DVD or CD and USB storage device in which you can store your data

Installing the network program

• Open the compact disk 

• Insert the CD or DVD program• Click right click on the CD• Click open

• Choose setup program

Double click on the setup program• Click install program

Running the network system

Go to start and click network systemEnter the password to login to the server networking, and then executing

Scopas Gorinwa Samuel Page 36 

Page 37: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 37/38

CHAPTER 10

10.1 GLOSSARY  Flowchart Modeling Symbols

Conclusion

With all these works it proves that the installation or development of a networking system thathandles the flow of information in the organization is critical to the success of this business

venture.

IT systems transform the way processes are handled ensuring data integrity, speed, small physical space, versatility as well as maintaining low costs of maintaining the system as

compared to manual systems that have numerous disadvantages. The system development

methodology that will be used has been stated as the system development life cycle which is arobust and an efficient way of creating a system. It is also the method that is used widely in the

development of such systems.

10.2 sBIBLIOGRAPHY www.networkingsystem.orgwww.learningnetwork.net Learning networking and related studies by  John's Closet 

 End 

Scopas Gorinwa Samuel Page 37 

Page 38: Abija Project

8/3/2019 Abija Project

http://slidepdf.com/reader/full/abija-project 38/38