Network Protocols, SDLC & ITSM Assignment: A Comprehensive Overview

This assignment delves into key concepts of network protocols, SDLC, and ITSM. It begins with calculations involving TCP/IP overhead and IPv4/IPv6 protocols, analyzing file transfer scenarios. The assignment then explores the coexistence of TCP and IP, discussing their connection-oriented and connect...Read More

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. (i) IN this step, it is firstly assumed that both of the clients would be making use of
IPv4 Protocol that is based on transferring of file.
Provided data:
Size of file = 1024 bytes
Size of payload = 128 bytes
The TCP header would be comprised of 20 bytes
The IPv4 header would be comprised of 20 bytes
Hence, the entire TCP/IP header would be composed of 40*(20 + 20) bytes
The bytes would be divided into 1024 bytes that would consist of 8 segments each of 128
bytes.
Then, (40 + 128)*8 = 1344 bytes.
Hence, a total of 1344 bytes would be sent including of the TCP/IP overhead.
(ii) The size of file = 2048 bytes
Size of the payload = 512 bytes
The total number of datagrams required for transfer of entire file is:
Number of datagrams = (File size/Payload Size) = (2048/512) bytes = 4 bytes.
2. Whenever a user would issue a certain command, they would make use of the TCP/IP
application layer protocol that can be defined as a chain of events that would be highly set in
motion. The message or command of the user would mainly pass through the protocol stack that

2NETWORK PROTOCOLS, SDLC & ITSM
would be entirely be based on a local machine (Goralski, 2017). It would then pass across the
network media based on the protocols of the recipient. The TCP/IP protocol at each of the layer
would be present within the sending host and would thus add information to the original data. As
the command of the user would make their way through the entire protocol stack, the protocols
present at each of the layers would be able to interact with the sending hots. It would also
interact with the connected peers based on the side of the receiving host.
The packet can be considered as the basic unit of information that can be transferred
across the internet network. This would mostly consist of a header with the addresses of the
sending and receiving hosts (Mileva & Panajotov, 2014). A body with the data would be
transferred. As the entire set of packets would travel through the TCP/IP protocol stack, the
protocols present at each of the layers would either add or remove the fields from the basic
header. When a certain protocol present on the sending host would host the addition of data to
the packet header, the entire process could be called as the encapsulation of data. Moreover, each
of the layers that would consist of a common term based on the altered packet.
3. One of the major advantage of the agile method for the development of software
projects, it can be discussed that it would prove maximum benefits for the growth of the project.
Based on the implementation of the agile mode of software development, it would be highly easy
for collaborating with the entire team and thus bring in changes towards the project. The project
managers would thus be responsible for bringing in the features of adaptability to various
situations of changes (Domann et al., 2014). This can also be defined as the key advantages of
choosing the agile methodology. Based on the following over the agile methodology, the
software teams would be able to deliver the best kind of business results after the development of

3NETWORK PROTOCOLS, SDLC & ITSM
the project. The following of the agile methodology would also help the project managers to
keep the stakeholders happy based on the delivering of a high quality product.
On the other hand, the major form of disadvantage that can be faced by the agile based
teams is that the developers, testers and customers who are highly engaged with the development
of software based on this methodology would always need to interact with each other (Goevert et
al., 2018). All the team members who are involved within the project must have a good form of
communication amongst each other. Each of the engaged team members would need to be
available based on prompting towards testing and then signing off with the project (Špundak,
2014). The engagement of the stakeholders within the team for such long hours would also
ensure that the product meets up to the expectations of the customers. The engagement of such
kind of factors would incur a high factor of time consuming and consumption of energy for the
team members.
4. The comparison of the agile method of software development and the evolutionary
method of software development can be discussed as:
Agile Model Evolutionary Software Development Model
The agile model can be considered as to be an
incremental delivery process in which each of
the incremental modes would be mainly
delivered based on a certain level of iteration
(Abrahamsson et al., 2017). Each of the
iterations that would be made within the
software developmental process would help in
proving the agility of the software
development teams. During the process of
iteration, each of the unnecessary activities
that would waste a considerable effort and
time.
In this process, each of the requirements
based on development of the software would
be divided into several forms of modules that
could be further be developed and then
delivered (Ahimbisibwe, Cavana &
Daellenbach, 2015). Some of the core features
based on the development is that the whole
software would be developed based on the
additions of new kind of features in different
forms of successive versions.
With the development of a software based on In the evolutionary software development

4NETWORK PROTOCOLS, SDLC & ITSM
the agile model, the end date for an iteration
would be fixed. It cannot be changes (Turk,
France & Rumpe, 2014). Hence, the
development team might have to reduce the
form of delivered functionality in order to
complete the iteration within the possible
time.
model, there is no such fixed time based on
the completion of the next form of iteration.
5. The Product Development Process of Apple is considered as one of the most
successful processes of design that has been ever implemented. Apple owns an integrated team
of designers who produce their own design environments and thus help in the growth of the
organisation based on the vast number of delivered products. Whenever the design team at Apple
collaborates over a new product, they get separated from the rest of the team of the business.
They also implement different forms of physical controls that help the prevention of the team
from interacting with any other employees of Apple during the entire day (Chuang, Morgan &
Robson, 2015). At this point of time, the team also gets separated from the traditional workplace
hierarchy at Apple. They are also able to create their own forms of reporting structures and thus
report directly to the main executive team. This kind of unique thinking helps them in leaving
free of the design. The information about the Apple New Product Process (ANPP) is mainly
provided to the product development team. In this position, the primary work over the software
design begins their journey.
The product development team details out the entire set of processes in a phased wise
manner. The primary idea behind this is that the product creation team would go through the
entire details of the draft. This team would also be responsible for letting the other teams to gain
an idea about the working order over each of the members (Grudin, 2017). The different
resources at the company are helped in concentrating over a wide range of projects that would be

5NETWORK PROTOCOLS, SDLC & ITSM
expected to bear a certain result as compares to many kind of lesser projects. Unlike other
companies the design process does not get over during the process of manufacturing. In Apple,
the design team mainly iterates the design throughout the phase of manufacturing. The entire
product is then built, tested and finally reviewed. The design team further works over the design
in order to create some form of improvements.
6. The three primary reasons that can also be defined as the main cause of failure of
project are:
a. Inadequate form of scheduling and documentation – This aspect is the sole
responsibility of the project manager. With the tracking of milestones, it would be highly easy
for the entire team to keep up to the expectation of the clients. On the contrary, a poor form of
documentation would prove fatal for the entire project (Todorović et al., 2015). Lack of defining
of scheduling and incomplete documentation could lead towards the failure of the project.
b. Failure in defining of parameters – The most important quality of a project manager
or project leader is to bring in efficiency of the work processes. Each of tasks that would need to
be performed within the project should be done in accordance to the proper standards (Kendrick,
2015). Without a proper definition provided to the standards, the entire team would not be able to
get guided by the project manager. This would in turn lead to the aspect of failure for the project.
c. Inaccurate estimations on cost – The structure of cost that need to be incurred for the
project should be handled within the proper time. This should be defined prior to the start of the
project. Without a proper definition to the structure of costs, there might arise situations of
project failure (Trendowicz & Jeffery, 2014). This might lead to problematic situations where the
resources might run out of cost. This might also lead to the stoppage of product services.

6NETWORK PROTOCOLS, SDLC & ITSM
7. Based on the needs of the company to maintain the several procured software, it could
be discussed that there should be a form of balance based on the view of the number of products
owned and the remaining cost after procuring these items. The budgetary plan could be helpful
for the planning of the future prospects of the project. It would also be needed for continuing
over the investments made over the project (Fleming & Koppelman, 2016). During the procuring
of software required for the company, it would be highly necessary to maintain a budget
schedule of each of the aspects that are maintained all over the project. This kind of forecast
would be described as the prediction about the future of the project.
During the planning of the budget of the project, the main goal would be based on
estimating the projected sales structure of the budget period. The direct cost of sales such as the
cost of materials, subcontractors and components would be made. Based on the budgetary
planning, the fixed costs and overheads would also be needed to be maintained (Ahmadi et al.,
2015). After defining this budgetary plan, it would be needed to be cleared from the project
manager of the organisation. This would help in ensuring that the management of software
would be maintained within the constraints of budget of the company.

7NETWORK PROTOCOLS, SDLC & ITSM
References
Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Ahimbisibwe, A., Cavana, R. Y., & Daellenbach, U. (2015). A contingency fit model of critical
success factors for software development projects: A comparison of agile and traditional
plan-based methodologies. Journal of Enterprise Information Management, 28(1), 7-33.
Ahmadi, S., Yeh, C. H., Martin, R., & Papageorgiou, E. (2015). Optimizing ERP readiness
improvements under budgetary constraints. International Journal of Production
Economics, 161, 105-115.
Chuang, F. M., Morgan, R. E., & Robson, M. J. (2015). Customer and competitor insights, new
product development competence, and new product creativity: differential, integrative,
and substitution effects. Journal of product innovation management, 32(2), 175-182.
Domann, J., Hartmann, S., Burkhardt, M., Barge, A., & Albayrak, S. (2014). An agile method for
multiagent software engineering. Procedia Computer Science, 32, 928-934.
Fleming, Q. W., & Koppelman, J. M. (2016, December). Earned value project management.
Project Management Institute.
Goevert, K., Lindner, M., & Lindemann, U. (2018, March). Survey on agile methods and
processes in physical product development. In ISPIM Innovation Symposium (pp. 1-13).
The International Society for Professional Innovation Management (ISPIM).
Goralski, W. (2017). The illustrated network: how TCP/IP works in a modern network. Morgan
Kaufmann.

8NETWORK PROTOCOLS, SDLC & ITSM
Grudin, J. (2017). Obstacles to participatory design in large product development organizations.
In Participatory Design(pp. 99-119). CRC Press.
Kendrick, T. (2015). Identifying and managing project risk: essential tools for failure-proofing
your project. Amacom.
Mileva, A., & Panajotov, B. (2014). Covert channels in TCP/IP protocol stack-extended
version. Open Computer Science, 4(2), 45-66.
Špundak, M. (2014). Mixed agile/traditional project management methodology–reality or
illusion?. Procedia-Social and Behavioral Sciences, 119, 939-948.
Todorović, M. L., Petrović, D. Č., Mihić, M. M., Obradović, V. L., & Bushuyev, S. D. (2015).
Project success analysis framework: A knowledge-based approach in project
management. International Journal of Project Management, 33(4), 772-783.
Trendowicz, A., & Jeffery, R. (2014). Software project effort estimation. Foundations and Best
Practice Guidelines for Success, Constructive Cost Model–COCOMO pags, 277-293.
Turk, D., France, R., & Rumpe, B. (2014). Limitations of agile software processes. arXiv
preprint arXiv:1409.6600.