IT Fundamental - TCP/IP Header, Agile Method, Apple Design Process

This document discusses TCP/IP header, Agile Method, and Apple Design Process. It also compares and contrasts Agile Method and Evolutionary Software Development Process. It also highlights the reasons for project failure and goals to be considered.

Running head: IT FUDAMENTAL
IT FUNDAMENTAL
Name of the Student
Name of the University

2
IT FUDAMENTAL
1. Given data:
File size = 1024 bytes
Payload size = 128 bytes.
TCP header is composed of 20 bytes
IPv4 header is composed of 20 bytes.
So total TCP/IP header is composed of 40 (20 + 20) bytes.
Distribute 1024 bytes into 8 segments, each segment has 128 bytes.
Then,
So total 1344 bytes will be sent including the entire TCP/IP overhead.
i)
Given data: IPv4 percentage overhead:
Total overhead in eight segments: 8*40= 320 bytes
Total data sent: 1024 bytes
Percentage overhead: (320/1024)*100= 31.25%
ii)
File size = 1024 bytes
File size = 1024 bytes

3
IT FUDAMENTAL
Payload size = 128 bytes.
TCP header is composed of 30 bytes
IPv4 header is composed of 30 bytes.
So total TCP/IP header is composed of 60 (30 + 30) bytes.
Distribute 1024 bytes into 8 segments, each segment has 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 and however, TCP has been connection oriented. These two
protocols have been coexisting in the same protocol stack. There are four layers in TCP/IP
protocol that are stacked together in two different protocols for working in the close
organizations and execute network communication. The first layer is application layer of the
TCP/IP protocol and send HTTP request. The TCP layer used to get HTTP request from the
application layer and helps in breaking the overall message into several packets that are called as
data packets. These packets have been sent to internet layer in which these packets have been

4
IT FUDAMENTAL
assigned proper IP address. Therefore, implementation of different layers with each other helps
in improving the speed and reliability of communication along with.
3. The advantage of agile method is that it helps in providing opportunity for giving their inputs
and feedbacks that helps designer to identify system characteristics as per the requirement of
client. This help in prioritizing project milestones that ensures about the success of the project
with high stakeholder satisfaction.
The limitation of agile method is that it does not have a clear idea about the final product. The
project gets out of scope that creates difficulty in completing a successful project.
4. Here both of these methods have been analysed. It discusses various features that Compare
and contrast the Agile method and Evolutionary software development process. In order to
provide a comprehensive overview about this discussion, an example has been considered to
discuss these two methods.
Prototype is an evolutionary software development process that help in agile development
process. Both of these methods have been considering the same project. AN initial prototype has
been provided in the prototyping and asked for review. This has been an important principle in
the agile method that helps stakeholders for getting involved into the project and provide their
input. Prototyping has been a rough presentation of project ideas and product features but might
not be consistent with actual product. There has been misconception related to product design in
agile method. It helps in providing feedback for reducing level of confusion in the project. This
help n allowing designing of product consistent with consumer requirements that helps in
ensuring project success.

5
IT FUDAMENTAL
5. Apple design process has been integrated with the product manufacturing. The product has
been produced, tested and reviewed properly. One important thing that makes the apple design
process different from other electronics manufacturing companies is their emphasis on design
iterations. Such support to the designers makes the design process lot easier, which also ensures
quality in the products along with the highest quality of design and engineering in manufacturing
of the products. The design team review helps in making an improvement to the original design
and production starts again. If there is an issue with the design prototype, the design process is
started again. This helps in double checking the quality of product. This has make Apple
synonymous with design and quality is not seen in products from another manufacturer. The
design process has been playing an important role in Apple that has helped in completing several
strategies from other customer electronics companies. Instead of finalizing a design, they test
each of the design prototypes developed by the designers.
6. There have been several reasons of failure of project:
Poor communication: Communication has been an important part for success of the project.
However, a poor communication among team members and manager create conflict among them
that led to failure of the project.
Poor budget planning: poor planning and estimating has been leading to failure of project, Due
to poor budget allocation, some raw materials and machines are not used in the projects. Due ti
which the quality and success factor of the project get low.
Poor coordination among teams: Coordination among team members have been a crucial point
in the project. Lack of coordination has been affecting the motivation of team members that led
to failure of project.

6
IT FUDAMENTAL
7. Following are the goals that need to be considered:
 Ensuring quality of each software
 Enhancing security of software
 Budget for maintenance need not to be exceeded than planned budget
 Security and testing of software needs to be proper within budget limitation
 Software quality needs to be according to needs of customer and requirements

7
IT FUDAMENTAL
References
Balaji, S., & Murugaiyan, M. S. (2012). Waterfall vs. V-Model vs. Agile: A comparative study
on SDLC. International Journal of Information Technology and Business
Management, 2(1), 26-30.
Duka, D. (2013, May). Adoption of agile methodology in software development. In 2013 36th
International Convention on Information and Communication Technology, Electronics
and Microelectronics (MIPRO) (pp. 426-430). IEEE.
Kumar, G., & Bhatia, P. K. (2012). Impact of agile methodology on software development
process. International Journal of Computer Technology and Electronics Engineering
(IJCTEE), 2(4), 46-50.
Losada, B., Urretavizcaya, M., López-Gil, J. M., & Fernández-Castro, I. (2012, October).
Combining InterMod agile methodology with usability engineering in a mobile
application development. In Proceedings of the 13th International Conference on
Interacción Persona-Ordenador (p. 39). ACM.
Mahalakshmi, M., & Sundararajan, M. (2013). Traditional SDLC Vs Scrum Methodology–A
Comparative Study. International Journal of Emerging Technology and Advanced
Engineering, 3(6), 192-196.
Patwardhan, A., Kidd, J., Urena, T., & Rajgopalan, A. (2016). Embracing Agile methodology
during DevOps Developer Internship Program. arXiv preprint arXiv:1607.01893.
Špundak, M. (2014). Mixed agile/traditional project management methodology–reality or
illusion?. Procedia-Social and Behavioral Sciences, 119, 939-948.