Analysis of TCP/IP Model, Software Development Process and ITSM
VerifiedAdded on 2022/11/14
|8
|1316
|229
Homework Assignment
AI Summary
This assignment delves into the TCP/IP model, software development processes, and ITSM. It begins with calculations of protocol overhead for IPv4 and IPv6, followed by an explanation of the TCP/IP protocol stack. The assignment then analyzes the agile software development method, comparing it to evolutionary software development. It further examines the Apple design process and identifies factors contributing to project failures, including schedule delays, unmet client expectations, and project complexity. Finally, it outlines goals for software development, emphasizing quality, security, and cost-effectiveness. The provided solution uses credible sources to support its analysis.

Running head: NETWORK MODEL, SOFTWARE DEVELOPMENT PROCESS AND
ITSM
NETWORK MODEL, SOFTWARE DEVELOPMENT PROCESS AND ITSM
Name of the Student
Name of the University
Author Note
ITSM
NETWORK MODEL, SOFTWARE DEVELOPMENT PROCESS AND ITSM
Name of the Student
Name of the University
Author Note
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

1TCP/IP MODEL, SOFTWARE DEVELOPMENT PROCESS AND ITSM
1. Data size calculation
Given data:
File size = 1024 bytes
Payload size = 128 bytes.
TCP header = 20 bytes
IPv4 header = 20 bytes.
So total TCP/IP header = 40 (20 + 20) bytes.
1024 bytes in 8 segments, 128 bytes per segment
Then,
(40+128)*8= 1344 bytes
So total 1344 bytes will be sent along with TCP/IP overhead.
i) What is the protocol overhead (stated as a percentage)? [3 marks]
IPv4 percentage overhead:
Total overhead: 8*40= 320 bytes
Total data sent: 1024 bytes
Percentage overhead: (320/1024)*100= 31.25%
1. Data size calculation
Given data:
File size = 1024 bytes
Payload size = 128 bytes.
TCP header = 20 bytes
IPv4 header = 20 bytes.
So total TCP/IP header = 40 (20 + 20) bytes.
1024 bytes in 8 segments, 128 bytes per segment
Then,
(40+128)*8= 1344 bytes
So total 1344 bytes will be sent along with TCP/IP overhead.
i) What is the protocol overhead (stated as a percentage)? [3 marks]
IPv4 percentage overhead:
Total overhead: 8*40= 320 bytes
Total data sent: 1024 bytes
Percentage overhead: (320/1024)*100= 31.25%

2TCP/IP MODEL, SOFTWARE DEVELOPMENT PROCESS AND ITSM
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 = 30 bytes
IPv6 header = 30 bytes.
So total TCP/IP header = 60 (30 + 30) bytes.
1024 bytes in 8 segments, 128 bytes in each segment
Then,
(60+128)*8= 1504 bytes
So total 1504 bytes along with TCP/IP overhead as well.
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. protocol stack
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 = 30 bytes
IPv6 header = 30 bytes.
So total TCP/IP header = 60 (30 + 30) bytes.
1024 bytes in 8 segments, 128 bytes in each segment
Then,
(60+128)*8= 1504 bytes
So total 1504 bytes along with TCP/IP overhead as well.
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. protocol stack
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

3TCP/IP MODEL, SOFTWARE DEVELOPMENT PROCESS AND ITSM
Integrating connections protocol with the connection-oriented protocol is what makes
TCP/IP protocol stack. While TCP protocol requires a dedicated connection between two
devices communicating with each other, the IP protocol only requires the IP address of two
communicating devices, which are nothing but a logical address, defined by the network
configuration and assigned to those devices while transferring information and data (Kota et
al., 2016).
TCP layer after receiving server request from the application layer generates data
packets and then send it to the IP layer, which assigns an IP address to these data packets and
then sends the data packets according to the IP address.
While the TCP layer creates an end-to-end connection between two devices, IP
protocol guides this communication through IP address that is integrated with the data
packets.
3. Agile method
Advantage:
Agile method provides context to develop products in the project that is consistent
with stakeholder requirements and expectations, ensuring stakeholder satisfaction (Dingsøyr
et al., 2018).
Disadvantage:
Software developers find it difficult in quantifying effort that is required for executing
the project, which makes project execution less effective, and it lacks efficiency too
(Choudhary & Rakesh, 2016).
Integrating connections protocol with the connection-oriented protocol is what makes
TCP/IP protocol stack. While TCP protocol requires a dedicated connection between two
devices communicating with each other, the IP protocol only requires the IP address of two
communicating devices, which are nothing but a logical address, defined by the network
configuration and assigned to those devices while transferring information and data (Kota et
al., 2016).
TCP layer after receiving server request from the application layer generates data
packets and then send it to the IP layer, which assigns an IP address to these data packets and
then sends the data packets according to the IP address.
While the TCP layer creates an end-to-end connection between two devices, IP
protocol guides this communication through IP address that is integrated with the data
packets.
3. Agile method
Advantage:
Agile method provides context to develop products in the project that is consistent
with stakeholder requirements and expectations, ensuring stakeholder satisfaction (Dingsøyr
et al., 2018).
Disadvantage:
Software developers find it difficult in quantifying effort that is required for executing
the project, which makes project execution less effective, and it lacks efficiency too
(Choudhary & Rakesh, 2016).
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

4TCP/IP MODEL, SOFTWARE DEVELOPMENT PROCESS AND ITSM
4. Agile method comparison
Both agile method and evolutionary software development process execute project in
different iteration and in each iteration a specific part of the project is provided to the client
for review (Dingsøyr et al., 2018).
For example, if an software is designed, an specific part of the software like login
facility of the software is demonstrated to the client.
Now in agile method, even though it is for demonstration , this feature of the software
has to be working properly.
However, in evolutionary software design process, if the considered model is
prototyping only prototype of the software needs to be provided, it might not be working,
however, if it is spiral model, then it is similar to the approach described in the agile method
(Joslin & Müller, 2015).
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.
5. Apple design process
Some of the features that make apple design process so different and successful are
the following (Khan, Alam & Alam, 2015):
Designers are provided the requirement that Apple wants to design and after that what
to be designed and how to design that depends on the designer team and such
flexibility according to the designers makes it possible to design some revolutionary
product that apple has offered to the consumers over the years
4. Agile method comparison
Both agile method and evolutionary software development process execute project in
different iteration and in each iteration a specific part of the project is provided to the client
for review (Dingsøyr et al., 2018).
For example, if an software is designed, an specific part of the software like login
facility of the software is demonstrated to the client.
Now in agile method, even though it is for demonstration , this feature of the software
has to be working properly.
However, in evolutionary software design process, if the considered model is
prototyping only prototype of the software needs to be provided, it might not be working,
however, if it is spiral model, then it is similar to the approach described in the agile method
(Joslin & Müller, 2015).
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.
5. Apple design process
Some of the features that make apple design process so different and successful are
the following (Khan, Alam & Alam, 2015):
Designers are provided the requirement that Apple wants to design and after that what
to be designed and how to design that depends on the designer team and such
flexibility according to the designers makes it possible to design some revolutionary
product that apple has offered to the consumers over the years

5TCP/IP MODEL, SOFTWARE DEVELOPMENT PROCESS AND ITSM
Design process is integrated throughout the manufacturing process and improvement
is made along the way manufacturing is done. If design has any issue, manufacturing
is not continued and the design is started again to ensure that design is perfect and has
no issue. This dedication for perfection is what makes apple design great and different
from other products offered by other manufactures
6. Analysis of project failure.
Project execution is not according to schedule: This not only increases overall time to
complete the project, it increases the overall project budget as well leading to budget
overflow. This is another significant reason that affects project success (Milosevic &
Martinelli, 2016).
Clients expectations for the project is not properly identified: When a client does not
agree to the quality and the features of the product delivered, the project is not
considered as successful (Kerzner, 2017).
Project is too complex: Sometimes even after proper project planning, a project is not
successful due to the complex nature of the project. Sometimes project requirements
are so complex that project team are not successful in implementing the project
according to the stakeholder requirements (Nicholas & Steyn, 2017).
Design process is integrated throughout the manufacturing process and improvement
is made along the way manufacturing is done. If design has any issue, manufacturing
is not continued and the design is started again to ensure that design is perfect and has
no issue. This dedication for perfection is what makes apple design great and different
from other products offered by other manufactures
6. Analysis of project failure.
Project execution is not according to schedule: This not only increases overall time to
complete the project, it increases the overall project budget as well leading to budget
overflow. This is another significant reason that affects project success (Milosevic &
Martinelli, 2016).
Clients expectations for the project is not properly identified: When a client does not
agree to the quality and the features of the product delivered, the project is not
considered as successful (Kerzner, 2017).
Project is too complex: Sometimes even after proper project planning, a project is not
successful due to the complex nature of the project. Sometimes project requirements
are so complex that project team are not successful in implementing the project
according to the stakeholder requirements (Nicholas & Steyn, 2017).
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

6TCP/IP MODEL, SOFTWARE DEVELOPMENT PROCESS AND ITSM
7. Analysis of goal
All the software have superior quality and performance
Software are secured
Low maintenance cost
7. Analysis of goal
All the software have superior quality and performance
Software are secured
Low maintenance cost
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

7TCP/IP MODEL, SOFTWARE DEVELOPMENT PROCESS AND ITSM
References:
Choudhary, B., & Rakesh, S. K. (2016, February). An approach using agile method for
software development. In 2016 International Conference on Innovation and
Challenges in Cyber Security (ICICCS-INBUSH) (pp. 155-158). IEEE.
Dingsøyr, T., Moe, N. B., Fægri, T. E., & Seim, E. A. (2018). Exploring software
development at the very large-scale: a revelatory case study and research agenda for
agile method adaptation. Empirical Software Engineering, 23(1), 490-520.
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.
Kerzner, H. (2017). Project management metrics, KPIs, and dashboards: a guide to measuring
and monitoring project performance. John Wiley & Sons.
Khan, U. A., Alam, M. N., & Alam, S. (2015). A critical analysis of internal and external
environment of Apple Inc. International Journal of Economics, Commerce and
Management, 3(6), 955-961.
Kota, S., Goyal, M., Goyal, R., & Jain, R. (2016). Multimedia satellite networks and TCP/IP
traffic transport. arXiv preprint arXiv:1603.08020.
Milosevic, D. Z., & Martinelli, R. J. (2016). Project management toolbox: tools and
techniques for the practicing project manager. John Wiley & Sons.
Nicholas, J. M., & Steyn, H. (2017). Project management for engineering, business and
technology. Routledge.
References:
Choudhary, B., & Rakesh, S. K. (2016, February). An approach using agile method for
software development. In 2016 International Conference on Innovation and
Challenges in Cyber Security (ICICCS-INBUSH) (pp. 155-158). IEEE.
Dingsøyr, T., Moe, N. B., Fægri, T. E., & Seim, E. A. (2018). Exploring software
development at the very large-scale: a revelatory case study and research agenda for
agile method adaptation. Empirical Software Engineering, 23(1), 490-520.
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.
Kerzner, H. (2017). Project management metrics, KPIs, and dashboards: a guide to measuring
and monitoring project performance. John Wiley & Sons.
Khan, U. A., Alam, M. N., & Alam, S. (2015). A critical analysis of internal and external
environment of Apple Inc. International Journal of Economics, Commerce and
Management, 3(6), 955-961.
Kota, S., Goyal, M., Goyal, R., & Jain, R. (2016). Multimedia satellite networks and TCP/IP
traffic transport. arXiv preprint arXiv:1603.08020.
Milosevic, D. Z., & Martinelli, R. J. (2016). Project management toolbox: tools and
techniques for the practicing project manager. John Wiley & Sons.
Nicholas, J. M., & Steyn, H. (2017). Project management for engineering, business and
technology. Routledge.
1 out of 8
Related Documents

Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
Copyright © 2020–2025 A2Z Services. All Rights Reserved. Developed and managed by ZUCOL.