1.

0 Objective

As generally, the main objective of the respective paperwork is to support the business
operation in order to get the loan from the commercial bank. The detail in the report will
be able to persuade the officer to approve the business startup loan. It is because the
statistic, planning and explanation in this paperwork will shows the sincere and efforts in
order to run the new business. It certainly will boost up the confident of the bank officer
in approving the loan for the company.

At the mean time, the respective paperwork also will become a useful guideline for the
business operator to run the business accordingly in the future. Without a proper
planning in company network, it can become a serious problem in the future especially
during upgrading the whole networking infrastructure and system.

The ineffective of network implementation will also seriously affect the smoothness of
the whole business operation. Therefore, the respective paperwork will play a crucial
role in determine the smoothness of the daily operation of the company.

Lastly, the respective paperwork will also be able to give the business runner the
projected income as well as the expenses. Then, the business runner can plan its
financial expenses wisely.
2.0 The Importance of Network Application
(A) Business Strategies

As for the business strategies, there are:

 Team building, modeling, and consensus
o It will more focus on the process of building up the whole teamwork as
well as the business model which will be used in running the whole
business operation. Communication is the key to establish the whole
teamwork and the implemented network within the company will definitely
provide a effective channel for the staffs to communicate with each other.

 Evaluating what an organization has accomplished and the resources they

have acquired
o It is always important to ensure the company management to fully utilize
the available resources so that a waste is not happen. By implement the
new network application, the management can easily shares the data and
human resource in perform daily business operation.

 Analyzing business, economic, political, and societal environment

o In order to get competitor advantages, the management must be able to
analyze the macro factors such as economic, political and societal
environment. By using an appropriate network application, the analyzing
tasks will become easier to be performed.

 Anticipating and evaluating the impact of future developments

o In this business strategy, the company will evaluate and estimate the
impact on the future development especially in network infrastructure.
As well know, today business moving faster and faster. A business
entity needs an infrastructure which can deliver and share the data
faster to relevant department in the company. The respective
implemented network infrastructure fulfills the requirement.
(B) Information Technology (IT) Strategies

Technology Platform

The Internet, intranets, extranets, and other networks, computer systems, system
software, and integrated enterprise application software provide a computing and
communications infrastructure, or platform that supports the strategic use of information
technology for e-business and e-commerce.

Data Resources

Many types of operational and specialized databases, including data warehouses and
Internet/intranet databases store and provide data and information for business
processes and decision support

Application Portfolio

 Business applications of information technology are designed as an integrated

portfolio of information systems that support strategic e-business initiatives, as well as
cross-functional business processes.

IT Organization
The organizational structure of the IS function within a company and the distribution of
IS specialists is designed to meet the changing strategies of a business. The form of the
IT organization depends on the managerial philosophy, e-business vision, and
business/IT strategies formulated during the strategies planning process.
(C) Information System (IS) Strategies

The Network is designed as a strategic, collaborative approach to addressing the

following powerful trends in environmental information management:

 As the scale and complexity of environmental challenges (and their associated

data) grow, environmental managers must collect, assess, and securely
exchange more data.

 The devolution of environmental management from central and local levels, and
the attempts to use more “integrative” or “adaptive” management approaches,
has dramatically broadened the universe of data and data exchange.

 Integrated environmental management requires integrated environmental

information and nearly always requires information integrated across media,
program areas, and geographic, political, and organizational boundaries.

 The Internet and its associated technologies are transforming information

management approaches. They are also increasing public expectations for data
access and presenting information security issues of a new magnitude.
3.0 Requirement in the Implementation of Network Application
(I) Functional
 Provides a workable performance abstraction for various network types which
accommodate a parameterized delay based on distance between notes for
speed of-light based LAN, MAN and WAN delays

 Provides a capability to model multi-packet transfer size buffers and an

abstraction of multi-packet windowing flow control in the network delay model.

 model protocols applicable to legacy applications (peer to peer and messaging

protocols)

 Retry and sanity check operations for long-lived RPC’s.

Figure 1.0: The Functional Requirement Diagram

(II) Performance

Every application user will have some expectations with respect to application
performance. Often they can be numerically quantified. The server administrator must
understand these expectations clearly, and use them in capacity planning to ensure that
the deployment will meet customer needs, when completed.

With regard to performance, there are certain criteria need to be concerned:

 What are the required average response times expected by the end users for
various interactions with the application? What are the most frequent
interactions? Are there any extremely time critical interactions? What is the
length of each transaction, including think time? In many cases, empirical user
studies may need to be performed to come up with good estimates.
 What is the anticipated steady state and peak user loads? Are there are any
particular times of the day, week or year when load peaks are observed? While
there may be several million registered customers for an online business,
typically only a fraction of them are logged in and performing business
transactions, at any point in time. A common mistake during capacity planning is
to use the total size of customer population as the basis and not the average and
peak numbers for concurrent users. The number of concurrent users, also may
exhibit interesting time based patterns.
 What is the average and peak amount of data transferred per request? This is
also very application specific. Good estimates for content size, combined with
other usage patterns, will help the administrator anticipate network capacity
needs.
 What is the expected growth in user load over the next 12 months? Planning
ahead for the future, will help avoid crisis situations and system downtimes for
upgrades.
(III) Connectivity

It is the ease by which a deployed system can be maintained, including monitoring the
system, repairing problems that arise, and upgrading hardware and software
components. 
When planning requirements for serviceability, consider the topics listed in the following
table.

Topic  Description 

Downtime Identify maintenance tasks that require specific services to be

planning  unavailable or partially unavailable. Some maintenance and
upgrades can occur seamlessly to users, while others require
interruption of service. When possible, schedule with users those
maintenance activities that require downtime, allowing the users to
plan for the downtime. 

Usage Identify the usage patterns to determine the best time to schedule
patterns  maintenance. For example, on systems where peak usage is during
normal business hours, schedule maintenance in the evening or
weekends. For geographically distributed systems, identifying these
times can be more challenging. 

Availability  It is often a reflection of your availability design. Strategies for

minimizing downtime for maintenance and upgrades revolve around
your availability strategy. Systems that require a high degree of
availability have limited opportunities for maintenance, upgrades,
and repair. Strategies for handling availability requirements affect
how you handle maintenance and upgrades. For example, on
systems that are distributed geographically, servicing can depend
on the ability to route workloads to remote servers during
maintenance periods. Also, systems requiring a high degree of
availability might require more sophisticated solutions that automate
restarting of systems with little human intervention. 
Topic  Description 

Diagnostics It can improve the stability of a system by regularly running

and diagnostic and monitoring tools to identify problem areas. Regular
monitoring  monitoring of a system can avoid problems before they occur, help
balance workloads according to availability strategies, and improve
planning for maintenance and downtime. 

Figure 3.0: Connectivity Requirements

(IV) Availability
It is a measure of how often a system’s resources and services are accessible to end
users, often expressed as the uptime of a system. Availability is a way to specify the
uptime of a system and is typically measured as the percentage of time that the system
is accessible to users. The time that the system is not accessible (downtime) can be due
to the failure of hardware, software, the network, or any other factor (such as loss of
power) that causes the system to be down. Scheduled downtime for service
(maintenance and upgrades) is not considered downtime. A basic equation to calculate
system availability in terms of percentage of uptime is:

Availability = uptime / (uptime + downtime) * 100%

Typically you measure availability by the number of “nines” you can achieve. For
example, 99% availability is two nines. Specifying additional nines significantly affects
the deployment design. The following table quantifies the unscheduled downtime for
additional nines of availability to a system that is running 24x7 year-round (a total of
8,760 hours).

Number of Nines  Percentage Available  Unscheduled Downtime 

2  99%  88 hours 

3  99.9%  9 hours 

4  99.99%  45 minutes 

5  99.999%  5 minutes 

Figure 2.0 Unscheduled Downtime for a System Running Year-Round (8,760 hours)
Fault-Tolerant Systems
Availability requirements of four or five nines typically require a system that is fault-
tolerant. A fault-tolerant system must be able to continue service even during a hardware
or software failure. Typically, fault tolerance is achieved by redundancy in both hardware
(such as CPUs, memory, and network devices) and in software providing key services.

A single point of failure is a hardware or software component that is part of a critical path
but is not backed up by redundant components. The failure of this component results in
the loss of service for the system. When designing a fault-tolerant system, you must
identify and eliminate potential single points of failure.

Fault-tolerant systems can be expensive to implement and maintain. Make sure you
understand the nature of the business requirements for availability and consider the
strategies and costs of availability solutions that meet those requirements.

Prioritizing Service Availability

From a user perspective, availability often applies more on a service-by-service basis
rather than on the availability of the entire system. For example, the unavailability of
instant messaging services usually has little or no impact on the availability of other
services. However, the unavailability of services upon which many other services
depend (such as Directory Server) has a much wider impact. Higher availability
specifications should clearly reference specific use cases and usage analysis that
require the increased availability.

It is helpful to list availability needs according to an ordered set of priorities. The

following table prioritizes the availability of different types of services.

Priority  Service Description 

Type 

1  Mission Services that must be available at all times. For example,

critical  database services (such as LDAP directories) to
applications. 
Priority  Service Description 
Type 

2  Must be Services that must be available, but can be available at

available  reduced performance. For example, messaging service
availability might not be critical in some business
environments. 

3  Can be Services that must be available within a given time

postponed  period. For example, calendar services availability might
not be essential in some business environments. 

4  Optional  Services that can be postponed indefinitely. For example,

in some environments instant messaging services can be
considered useful but not necessary. 

Figure 3.0 Availability of Services by Priority

Loss of Services
Availability design includes consideration for what happens when availability is
compromised or when a component is lost. This includes considering whether users
connected must restart sessions and how a failure in one area affects other areas of a
system. QoS requirements should consider these scenarios and specify how the
deployment reacts to these situations.
(V) Security
It is a complex combination of factors that describe the integrity of a system and its
users. Security includes authentication and authorization of users, security of data, and
secure access to a deployed system.  Most business applications require security. The
various security considerations and available choices are discussed in this section.

User Authentication and Authorization

Application users must be authenticated. The network server must provide three
different choices for user authentication. The default file based security realm is suitable
for developer environments, where new applications are being developed and tested.

At deployment time, the server administrator can choose between the LDAP or Unix
security realms. LDAP stands for Lighweight Directory Access Protocol. Many large
enterprises use LDAP based directory servers to maintain employee and customer
profiles.

The type of authentication mechanism chosen may require additional hardware for the
deployment. Typically a Directory server executes on a separate server, and may also
require, a backup for replication and high availability. An authenticated user’s access to
various application functions may also need authorization checks. If the application uses
the role based J2EE authorization checks, some additional checking is performed by the
application server. This places additional overheads, which need to be accounted for
while doing capacity planning.

Encryption
For security reasons, sensitive user inputs and application output must be transmitted in
an encrypted form. Most business oriented web applications encrypt all or some of the
communication flow between the browser and Application server, if required. Online
shopping applications typically do not encrypt traffic, except when the user is completing
a purchase or supplying private data. Portal applications such as news and media
typically do not employ encryption. SSL is the most common security framework on
internet, and is supported by many browsers and application servers.
The implemented network server should be able to supports SSL 2.0 and 3.0 and
contains software support for various cipher suites. It also supports integration of
hardware encryption cards for even higher performance. Security considerations,
particularly when using the integrated software encryption, will impact hardware sizing
and capacity planning.
4.0 Opportunities and Threats in the Implementation of Network Application

(A) Opportunities

File Sharing
The major advantage of a computer network is that is allows file sharing and remote file
access. A person sitting at one workstation of a network can easily see the files present
on the other workstation, provided he is authorized to do so. It saves the time which is
wasted in copying a file from one system to another, by using a storage device. In
addition to that, many people can access or update the information stored in a database,
making it up-to-date and accurate.

Resource Sharing
Resource sharing is also an important benefit of a computer network. For example, if
there are four people in a family, each having their own computer, they will require
four modems (for the Internet connection) and four printers, if they want to use the
resources at the same time. A computer network, on the other hand, provides a cheaper
alternative by the provision of resource sharing. In this way, all the four computers can
be interconnected; using a network, and just one modem and printer can efficiently
provide the services to all four members. The facility of shared folders can also be
availed by family members.

(B) Threats

Security Issues
One of the major drawbacks of computer networks is the security issues involved. If a
computer is a standalone, physical access becomes necessary for any kind of data theft.
However, if a computer is on a network, a computer hacker can get unauthorized access
by using different tools. In case of big organizations, various network security software
are used to prevent the theft of any confidential and classified data.
Rapid Spread of Computer Viruses
If any computer system in a network gets affected by computer virus, there is a possible
threat of other systems getting affected too. Viruses get spread on a network easily
because of the interconnectivity of workstations. Such spread can be dangerous if the
computers have important database which can get corrupted by the virus

5.0 Conclusion

Unquestionable, a good implementation of network infrastructure and application will

bring a great impact to the whole organization. Networks allow computers, and hence
their users, to be connected together. They also allow for the easy sharing of information
and resources, and cooperation between the devices in other ways. Since modern
business depends so much on the intelligent flow and management of information, this
tells you a lot about why networking is so valuable.

Thus, it will increase the effectiveness and sufficiency of the whole business operation
and production.
6.0 Reference

A. CHILD, J. 1988. Information technology and organization. In Innovatzon and

Management: Internatzonal Comparzsons, K. Urabe et al., Eds Waiter de
Gruyter, Berlin

B. CRAIG SMITH, N. 1989. The case study: A vital yet misunderstood method for
management. In Frontwrs of Management, R. Mansfield, Ed. Routledge and
Kegan Paul, London.

C. FELDMAN, M., AND MARCH, J. 1981 Information in organizations as signal and

symbol. Admm. Sci Q. 26, 2, 171-186.

D. HIRSCHHEIM, R., AND NEWMAN, M. 1991. Symbolism and information

systems development: Myth, metaphor and magic Inf. Syst. Res. 2, 1, 29-62.

E. MINTZBERG, H. 1979. The Structurzng of Organizatzons: A Synthesis of

Research. Prentice-Hall, Englewood Cliffs, N.J.

F. Francalanci, C. (2001). Predicting the implementation effort of ERP projects:

empirical evidence on SAP/R3. Journal of information technology, Vol. 16,
Issue 1, pp33–48.

G. Hirt, S. G., Swanson, E. B. (1999). Adopting SAP at Siemens Power

Corporation. Journal of Information Technology, Vol. 14, Issue 3, pp243–251.

H. Krumbholz, M., Maiden, N. (2001). The implementation of enterprise resource

planning packages in different organisational and national cultures.
Information systems, Vol. 26, Issue 3, pp185–204.