Network Protocols Assignment: TCP/IP and IPv6 Overhead

Desklib provides solved assignments and past papers to help students understand complex networking concepts.

ASSESSMENT 4 - ASSIGNMENT 2
NETWORK PROTOCOLS, SDLC & ITSM

A station running TCP/IP needs to transfer a file to a host. The file contains 1024 bytes. How
many bytes, including all of the TCP/IP overhead, would be sent, assuming a payload size of 128
bytes and both systems are running IPv4? (Also assume that the three-way handshake and
window size negotiation have been completed and that no errors occur during transmission.)
What is the protocol overhead (stated as a percentage)?
The IPv4 protocol is used at the station to transfer the file to a host. The size of the given file is 1024
bytes. And the given payload size is 128 bytes. 20 bytes are used for the TCP header that is being
composed for the file. 20 bytes is used by IPv4 header. The total bytes used for the TCP/IP protocol is
40 bytes. 1024 bytes is divided into the 8 segments. Therefore,
128 bytes is used by each segment that is;
(40+128)*8= 1344 bytes
TCP/IP is used to transmit the file, and the total bytes used is 1344 bytes
Therefore, the given file size= 1024 bytes
Data sent= 1344 bytes
Hence,
1344*100/1024= 131.25%
The protocol overhead (in %) =131.25-100
= 31.25%
Perform the same calculation, this time assuming that both clients are using IPv6.
The given size of the file to be transmitted is 1024 bytes, and the given payload size is 128 bytes. The
bytes used for composing TCP header is 60(20+40) bytes. This is divided such as 20 bytes is used for
IPv4 header and a total of 40 bytes for the TCP/IP header. 1024 bytes are divided into 8 segments
making 128 bytes for each segment, therefore,
(60+128)*8= 1504 bytes
TCP/IP overhead is included of total 1504 bytes to transmit the file.
Therefore, the given file size= 1024 bytes
Data sent= 1504 bytes
Hence,
1504*100/1024= 146.87%
The protocol overhead (in %) =146.87-100
= 46.87%

IP is a connection-less protocol, whereas TCP is connection-oriented. How can these two
protocols coexist in the same protocol stack?
IPX is connectionless and in this manner appreciates the benefits of connectionless transports, which
includes expanded speed. SPX, then again, utilizes affiliation situated administrations. SPX
dependably utilizes the community layer administrations of IPX. IPX, however, can paintings freely
of SPX, as although it were both a network and delivery layer detail. Notice the manner IPX folds
over SPX, occupying room in each the network and delivery layers, ready to associate with better-
layer conventions and administrations, without the utilization of SPX. Alongside those lines, IPX
without SPX is like the blend of UDP and IP, instead of TCP with IP, that ‘an increasing number of
much likes the mixture of SPX and IPX. whilst IP will dependably reply to TCP or UDP, in no way
taking over delivery layer usefulness all by myself, IPX is prepared to do virtually such an
accomplishment.
IPX/SPX has no call goals framework as a be counted of course. That usefulness is utilized whilst a
NetWare server is jogging Novell directory offerings (NDS) and the NDS index requester (which
keeps running at the consultation, Presentation, and alertness layers) can make solicitations of an NDS
database.

Mention one advantage and one disadvantage of Agile method.
The Agile methodology is an SDLC model, which is a combination of the repetitive and increasing
process model that focuses on the adaptiveness and customer satisfaction through the rapid delivery of
the working product of the software. The model doesn’t follow the large incremental model but
divides the product in small incremental models. The main advantage of the use of this model is the
reviewing methods used to interact with the customer to determine feedbacks and the review of the
customer on the software product. The model uses the process and tools but emphasises on the
customers and their interaction with the developer. The software is delivered within very less period.
Due to the regular implementation of the customer feedback, the regular adaption of the
circumstances takes place on the software development cycle. The late changes in the software
through feedback are also introduced to the software as an up-gradation.
The major disadvantage of the Agile model is when large software deliverables are assigned for the
system as it is difficult to decide the effort which will be needed for the software development cycle
model — also, the lack of designing and documentation effects on the production of the development
process. The projects sometimes take a longer time to complete when the customer is not accurate
about the details of the software the organisation or individual needs. The decisions are taken only by
the senior designers and also determine the tools for the development process. The model also gets
affective due to unrealistic expectations of the customer when the processes are too complex, and the
deadline is also unrealistic to the software developers to work through the development cycle. The
changes that are implemented very less cost and have to be updated in a very short period. This
disadvantage also affects the developers and the stakeholders alike and the methodology when the
project is a rigid sequential way in the SDLC model.

Compare and contrast the Agile method and Evolutionary software development process.
Explain with an example.
The Agile model is a very effective methodology for the improvement and development of the
software and delivering of a software project. This model consists of the repetition and iteration of the
batches in which the whole software project is divided and distributed. The software project is
completed and upgraded based on the feedbacks and methods of the client. These updations and
changes are taken in considerations even when the software developed are submitted to the client. For
example, if a company, say Google, has a project that is divided into various segments and each
segment has to be researched and analysed to its best, this model in the research will be used to make
that software efficient. The system modules in the Agile method are compatible with the changes that
are included in the software after completion. These updations include even the minor factors which
affect the software project of the organisation or an individual.
On the other side, the evolution software development process is a rigid process as compared to the
Agile method of software development life cycle. It is a technique defined methodology which works
according to a refined technique. The changes in the system don’t support the technique, then, the
changes are taken into account and converted to the modifications which are supportable by the
technique of the system. The feedback and the limitations are also taken account of only they can be
implemented through the technique according to which the system software is developed. The Agile
method can perform the changes in the software according to the feedback of the client and also the
modifications can be upgraded through various techniques. Also, with the use of the same technique,
it takes plenty of time to perform the changes for the system. The Agile method SDLC model uses
very less time to update and modify the working system of the software used.

Analyse the uniqueness of Apple design process.
Apple is one of the most renowned organisations which is famous for the design and working of its
world-class projects. The interface of the devices made by Apple is different and very user-friendly
other than many other companies in the same field. Not only creates a product, but they also upgrade
the existing model of their products, and this is done through the use of unique design methods.
Apple’s product design and development process are one of the largest successful design and project
processes that are ever implemented in any organisation which makes user-friendly electronic devices.
Apple design usually focuses on the choices and the requirement of the customer. The requirement
analysis step of the Apple design process is given a priority over every step in the development and
design cycle. The designs and the model of the device or software are completed before it is shown to
the client or needs to be upgraded in the already running systems or operating systems. Other than the
requirement analysis, the organisation focuses on providing the customer what they need and an easy
interface for the consumer to interact with the system through the device.
After all the solution is discussed, the project is taken into account by the senior authorities and is
analysed. The compatibility of the software project is checked through various techniques by the
authorities of the design process. The reviewing of the system is a regular process in the designing of
a unique Apple product. The system is analysed throughout the process of building the software,
running the software and reviewing the methodology of the software in the software development
cycle. The iteration model in the design process also helps the software developer to enhance the
integrity of the system. The approach taken by Apple is very costly, but the outcome of the approach
and the product delivered is unique in its feature as well as in the design.
At the end of the design process, the cost of the software or the product is established by Apple and
launch in the market for the consumer. This process is a costly process bur due to the efficiency of the
proposed system and process; the design model is considered to be one of the best models for Apple.

Describe three reasons for project failure.
There are many reasons which can cause project failure in the system. The aspects and the features of
every factor should be taken into account to measure its effect on the system. The applications of the
factors on the system play a major role in project success and failures. The following are the three
major reasons described for project failure:
1. Inadequate risk management
This is considered as a major component that is taken into account for the reason for system
failure. This factor leads a software project in the direction of the failure of the project. It
includes the risk factors which effects the project when it is published and out in the market
for the consumers. This techniques or factor plays a very major role in the software
development cycle. The framework of the project is dependent on the risks, and the solutions
for that risk are needed to be found out as soon as possible.
2. Failure to track requirements
It is very important to keep track of all the requirements of the project as the making and
upgradations of the project are based on it. Sometimes, due to the size of the project, it is very
difficult to maintain all the files and improvements of the project and the project is delivered
to the client without the asked configuration is a major drawback for the project. It is very
important as the changes in the project system and the advancement of the project depends in
these requirements by the client. Therefore, loss of track of requirements possesses the system
or the project in the direction of failure.
3. Cultural differences in global projects
A project can be configured from anywhere in the world and are much time outsourced by the
organisation. Sometimes, when the project has to deliver to other countries, cultural
differences also plays a major role in the requirements of the project. Culture is a very
important factor for any individual, and if cultural differences are caused between the user
and the provider, then the project may found a drawback without having been published. This
kind of factors restricts the work on a global scale. An individual cannot consider the
requirement of the project before the cultural requirements.

Your company owns several software and asked you to manage them within company budget
constraints. What will be your goals?
For managing a settled and established company, it is important to make decisions which are in favour
of the employees as well as the company. The main focus of any company is to run itself and establish
their name in the field which they work. The budget is a major constraint that needs to be taken care
of if an individual is running a company on its own. The quality work is the main aim of the
individual to maintain the name of the company in the network. These goals should be considered for
managing a software company.
The individual should aim to keep the expenses of the software development procedure under control.
The upgradations in the software can take plenty of money as it is completely dependent on the
technology used and the quality of work done. Also, while running a company, the owner has to keep
the employee's point of view in mind. It is also very important to think about the profit the employees
will make.
It is very important for the organisation to hire the right and talented employees to handle the
upgradations of the software, which is run by the companies. The employees are part of the
organisation which completes the work and help the organisation to grow. Therefore, the choices
made in the hiring processes make a lot of differences in the status if the organisation or a company
and hence, the budget should be carefully divided in this section.
All these challenges and goals play an important role in determining the best way to distribute the
budget into segments for the benefit of the company. This helps the company to deliver the project on
time and with an efficient product.

References
 Zhang, Q. Y., Wang, X. W., Huang, M., Li, K. Q., & Das, S. K. (2018). Software defined
networking meets information centric networking: A survey. IEEE Access, 6, 39547-39563.
 Sadek, R. A. (2018). An Agile Internet of Things (IoT) based Software Defined Network
(SDN) Architecture. Egyptian Computer Science Journal, 42(2).
 Li, Y., Piao, X., Zhang, H., & Lei, K. (2018, December). NDN Producer Mobility
Management based on Echo State Network: a Lightweight Machine Learning Approach.
In 2018 IEEE 24th International Conference on Parallel and Distributed Systems
(ICPADS) (pp. 275-282). IEEE.
 Krishnan, P., & Achuthan, K. (2018, September). Managing Network Functions in Stateful
Application Aware SDN. In International Symposium on Security in Computing and
Communication (pp. 88-103). Springer, Singapore.
 Qiao, L., Liu, B., Liu, H., Yang, H., Xu, J., & Liu, S. (2018, November). Design and
Performance Evaluation of On-Board Computer Network Protocol Stack Based on Spacecraft
Operating System. In International Conference On Signal And Information Processing,
Networking And Computers (pp. 13-21). Springer, Singapore.
 Burleigh, S. C., De Cola, T., Morosi, S., Jayousi, S., Cianca, E., & Fuchs, C. (2019). From
Connectivity to Advanced Internet Services: A Comprehensive Review of Small Satellites
Communications and Networks. Wireless Communications and Mobile Computing, 2019.
 Kusek, M. (2018, May). Internet of things: Today and tomorrow. In 2018 41st International
Convention on Information and Communication Technology, Electronics and
Microelectronics (MIPRO) (pp. 0335-0338). IEEE.