Network Protocols, SDLC & ITSM: Detailed Analysis and Solutions Report

This assignment solution delves into the intricacies of network protocols, Software Development Life Cycle (SDLC), and IT Service Management (ITSM). It begins with calculations of data transmission overhead using TCP/IP, IPv4, and IPv6, analyzing protocol efficiency. The assignment then explores the coexistence of connection-oriented and connection-less protocols within the same stack, followed by a discussion on the Agile methodology, comparing and contrasting it with Evolutionary software development. The analysis extends to the Apple design process, highlighting its unique features. Furthermore, the solution identifies and describes critical reasons for project failures, offering insights into project management. Finally, the assignment addresses the goals of managing software products within budgetary constraints. The solution includes references to relevant academic sources.

Running head: Network Protocols, SDLC & ITSM
Network Protocols, SDLC & ITSM
Name of the Student
Name of the University
Author Note

1Network Protocols, SDLC & ITSM
1. 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.)
Given data:
File size = 1024 bytes
Payload size = 128 bytes.
TCP header contains 20 bytes
IPv4 header contains 20 bytes.
So total TCP/IP header contains 40 (20 + 20) bytes.
Divide 1024 bytes into 8 segments, each 128 bytes.
Then,
So total 1344 bytes will be sent that also includes the entire TCP/IP overhead.
i) what is the protocol overhead (stated as a percentage)? [3 marks]
Given data: IPv4 percentage overhead:
Total overhead in eight segments: 8*40= 320 bytes

2Network Protocols, SDLC & ITSM
Total data sent: 1024 bytes
Percentage overhead: (320/1024)*100= 31.25%
ii) perform the same calculation, this time assuming that both clients are using IPv6. [2
marks]
File size = 1024 bytes
Payload size = 128 bytes.
TCP header contains 30 bytes
IPv6 header contains 30 bytes.
So total TCP/IP header contains 60 (30 + 30) bytes.
Divide 1024 bytes into 8 segments, every 128 bytes.
Then,
(60+128)*8= 1504 bytes
So total 1504 bytes will be sent including the entire TCP/IP overhead.
Protocol overhead:
IPv6 percentage overhead:
Total overhead in eight segments: 8*60= 480 bytes
Total data sent: 1024 bytes
Percentage overhead: (480/1024)*100= 46.87%
2. IP is a connection-less protocol, whereas TCP is connection-oriented. How can these
two protocols coexist in the same protocol stack? [4 marks]

3Network Protocols, SDLC & ITSM
However, they coexist in the same protocol stack because they work in close association with
the application layer. The application layer is responsible for sending an HTTP request and
once this request is received, the TCP layer defines some IP address and provide it to the IP
layer which according to the IP address provided by the TCP layer sends the data packet to
the destination device. The packet is not only sent to the destination, but it is also ensured that
it is received by the targeted device because the TCP protocol creates a dedicated end to end
connection between two communicating device. Therefore, even though these two protocols
work on two different techniques, they are integrated into the same protocol stack, which
increases reliability and efficiency in communication.
3. Mention one advantage and one disadvantage of Agile method. [4 marks]
The agile method divides project execution in to smaller modules and these modules are then
managed in proper sequence as per the project plan and schedule. As the project is divided
into the module it is easier to manage those modules which ensures that overall project
manager is simple yet effective that ensures the project success.
One disadvantage of the agile method is that as the project modules are managed and
executed in sequence, execution of any new module is not started once the previous module
is not completely executed. This means that the issue in one module will affect the execution
of other modules as well and hence affecting the overall project execution.
4. Compare and contrast the Agile method and Evolutionary software development
process. Explain with an example. [4 marks]
When a product is developed in agile method it is done in incremental approach which means
that instead of the whole products, some part of the products is only developed and it then
provided to the consumers. However, it is ensured that functionality that is offered with the

4Network Protocols, SDLC & ITSM
partially completed product is fully functional and it is verified with extensive testing process
before it is provided to the consumers and this is where the agile method has significant
difference with the prototyping model. However, the actual principle has similarity as both of
the model provides a prototype of the model before the final product is developed and
delivered to the clients.
However, in prototyping method, although functionalities is provided with the product
prototype, the functionalities might be completed or not and this is an important difference
with an agile method where functionalities have to be complete before it is provided to the
consumers.
5. Analyse the uniqueness of Apple design process. [4 marks]
One of the best things of the apple design process is that it provides complete freedom to its
designers, allow them to experiment with ideas and prototypes even though it is extremely
difficult to implement. This allows designers to think freely and implant their ideas the way
they like while the company provides full support, which includes financial resources
required for the experiment with the design.
Once a design team is formed, it is then excluded from the standard organizational hierarchy,
which allows them to work without any interference of higher authorities. This is something
that is not often seen in large companies. However, the meeting is held regularly every week
on Monday where design review is done to ensure that there is no issue with the design
process.
Apple emphasis on iteration to ensure that along with design their products also of the highest
quality as design without quality is not accepted by consumers.

5Network Protocols, SDLC & ITSM

6Network Protocols, SDLC & ITSM
6. Describe three reasons for project failure. [5 marks]
Although there are various reasons for project failure and it depends on the nature and
context of the projects, three of the most important reasons for which the project is not often
successful are the followings:
 Scope variance: It is one of the most important things of any project, however, it is
often not successfully considered in the project planning. It is seen that often project
plan does not describe the scope of the project which makes it difficult for the project
team to identify what they are supposed to do and what exactly needs to be done for
completing the project. This often leads to project execution that is not according to
the project objective and goal which makes it difficult to ensure success in the project
execution.
 Schedule variance: Sometimes due to lack of planning and project leadership, project
execution is not according to the defined project schedule developed during the
project planning. This lead to a delay in the project which required additional project
resources and funding as well. However, it is not that easy to acquire additional
funding from sponsors and stakeholders leading to stakeholder conflict which has the
potential to make the project a failure. Hence schedule variance is one of the main
reasons for a project not being that successful as planned.
 Lack of quality control: Often project does not integrate enhanced quality
management which is required for having control over the quality of the product
being delivered through the project. When a product does not meet the quality
expectations of the client the project is not regarded as a success.

7Network Protocols, SDLC & ITSM
7. Your company owns several software products and asks you to manage them within
company budget constraints. What will be your goals? [4 marks]
My company owns several software and it requires to manage that software within the
approved budget. Hence my goals will be the following:
 To ensure that each and every software provides specific functionalities as decided
during limits design
 The security aspect of each software is checked through the standard testing process
and this is done within the approved budget
 Even though the budget is not flexible, the quality of the software is not compromised
for a limited budget as this is important for the company to ensure that the business
process is not affected for ensuring a profit

8Network Protocols, SDLC & ITSM
References:
Arcaini, P., Gargantini, A., & Radavelli, M. (2018, February). An evolutionary process for product-
driven updates of feature models. In Proceedings of the 12th International Workshop on
Variability Modelling of Software-Intensive Systems (pp. 67-74). ACM.
Aksoy, A., & Gunes, M. H. (2016, November). Operating system classification performance of tcp/ip
protocol headers. In 2016 IEEE 41st Conference on Local Computer Networks Workshops
(LCN Workshops) (pp. 112-120). IEEE.
Elamin, R., & Osman, R. (2017, July). Towards Requirements Reuse by Implementing Traceability in
Agile Development. In 2017 IEEE 41st Annual Computer Software and Applications
Conference (COMPSAC) (Vol. 2, pp. 431-436). IEEE.
Goralski, W. (2017). The illustrated network: how TCP/IP works in a modern network. Morgan
Kaufmann.
Joslin, R., & Müller, R. (2015). Relationships between a project management methodology and
project success in different project governance contexts. International Journal of Project
Management, 33(6), 1377-1392.
Peng, Y. S., & Liang, I. C. (2016). A dynamic framework for competitor identification: A neglecting
role of dominant design. Journal of Business Research, 69(5), 1898-1903.
Shylesh, S. (2017). A Study of Software Development Life Cycle Process Models. In National
Conference on Reinventing Opportunities in Management, IT, and Social Sciences (pp. 534-
541).
Vasilakos, A. V., Zhang, Y., & Spyropoulos, T. (2016). Delay tolerant networks: Protocols and
applications. CRC press.