Networking Protocols and SDLC: A Comprehensive Report

Desklib provides solved assignments and past papers to help students succeed.

Networking Protocol and SDLC

Introduction
Networking protocols are defined for any network in order to maintain the integrity of any
network. The majorly used networking protocol in today’s scenarios is the Transfer Control
Protocol (TCP). In the following report the various aspects of networking protocols and SDLC
are discussed along with the dos and don’ts of them. After going through this whole report a
learner would be having the ability to be answering the questions such as the importance of 3way
handshaking, knowledge about RAD and agile methodology and an explanation of scope creep.

1. Explain why we need a 3-way handshake in TCP? Why not just 2-way?
A three way handshake in defined as a techniques or a technology that is used by the transfer
control protocol in order to establish a connection between the host server as well as the client
server. A three way handshake process consist of 3 steps, in which both the client as well as the
server are required to send SYN and ACK that means they both need to send the Synchronous bit
as well as the Acknowledgement bit. The client node firstly sends the SYN data packets over the
internet protocol network to the servers (Hsu, et. al., 2016). The aim of sending this SYN is just
to enquire if the server is allowing new connection to be established. The server to which this
was sent responds back if it is open to new connections and for this it sends ACK and SYN, after
this step, in the last step the client receives server’s receipt of ACK/SYN and then it sends back
the ACK for the completion of establishment of the connection.
Figure 1 Connection Establishment through 3 way handshake (Qin, et. al., 2016)
The 3 way handshake process is highly preferred over the 2 way handshake process that was
used earlier due to various reasons. This can be understood by an example, the basic meaning of
2 way hand shake process is would be that there would be no need of the ACK bit that is sent by
the client after receiving the SYN/ACK bit (Hsu, et. al., 2016). The basic question is over the
need of the last bit. As per the research of (Qin, t. al., 2016) the last bit is necessary for the server
to ensure whether the network is strong enough for the connection to be establish and hence the
host will be knowing that the messages are being received at both the ends. If there are only 2
handshakes done in the whole process of connection establishment, then in that case the client
would be knowing that the messages are being received by the server but the server would not be
having any idea if the client has received their acknowledgment as well as the synchronous bit

and to make sure that the client has received the both the client has to send a last ACK bit (Qin,
et. al., 2016).

2. What is RAD? List an advantage and a disadvantage of using RAD.
A Rapid Action Development or RAD is defined as a specific category of the agile methodology
that is used for the development of a software. The RAD methodology is very much different
from the Waterfall methods of software development as the key trait of the RAD is that it has a
very high emphasis over the proper creation of a working software as well as the feedback of the
user on the strict plans and the recording of the requirements (Satyawati et. al., 2017).
Following are the steps that are involved in the RAD
Figure 2 RAD Methodology (Satyawati et. al., 2017)
1. Knowing the requirements of the user: The requirements that are provided by the user
must be known and gone through thoroughly as it is very important to have every feature
in the software that has been required to the user. If the requirements of the user is
already known then in that case the analysis of the requirement gathering becomes easy
(Sasimito and Wiyono, 2017).
2. Creation of Prototypes: It is also necessary in every type of software development to
start the development of the software as soon as possible just after the factors such as user
requirements, budget of the software and the deadline for the deployment of the software
is known to the team (Satyawati et. al., 2017).
3. Getting the Feedback of the User: The user or the client who has ordered the team to be
working on the creation of the software must always be kept in loop in order to keep
them updated that what all process are being done in the whole project. At any stage of
the product the user must be having an update about the current condition of the software
and how much more it is left (Sasimito and Wiyono, 2017).

4. Testing: After the whole project has been completed by the tem it must be properly
tested by the help of various test cases that are created by the testing team. The test cases
of a software are created on the bases of the requirement of a user that they have provide.
IT is basically done in order to check whether there is an error in the project or any bug
and if all the requirement provided by the user are fulfilled or not.
5. Deployment: This is the part where the project must not be having any error or bugs and
it has be successfully tested by the testing team and no more additions are needed to be
done and the software is deployed to the client and presented to them for use.
6. Maintenance: In case if there is any problem that is faced by the user of the software
such as the client of the customer of the client, then in that case the repairmen or the
maintenance is also done in this model only. The regular maintenance of the software is a
part of this methodology which allows to make updates in the software in the backend
without effecting the performance of the software (Sasimito and Wiyono, 2017).
Advantages of RAD
1. RAD is very much flexible to new changes.
2. It is found to be highly efficient if the overall project risk is to be reduced
3. It can be highly productive even if the people involved are less in number
Disadvantages of RAD
1. It cannot be used for small scale projects.
2. Not all the software that are to be made, compatible to RAD.
3. When the risk of technicalities are high, it must not be used.
4. It requires very high skilled designers.

3. Discuss two advantages and two disadvantages of agile methods.
Advantages of Agile Methodology
1. One of the most advantageous feature of the agile methodology is that it has the
requirements that are provided by the user as well as the varying nature of the
development phase of the software always into consideration which makes it easy for this
methodology to be scaling in a proper manner for the project that are based upon real life
without even taking the size of the of the project into consideration. This basically means
that the agile method follows the policy of properly analyzing the requirements that are
provided by the user before the starting of the development of the user that then it does
not matter what is the size of the project, it would be created in the same method as all
the others are created (Kumar et. al., 2019).
2. Another one of an organizational advantage of the agile methodology being used of the
software development is that it is a heavy promoter of team work in an organization. As it
is already known that there are various teams involved in the creation of a software if the
required software is being created by the help of the agile methodology. As per the
features of the agile model, each and every team has to be kept in loop that is, they must
be knowing that what has till now happened in all the departments of the project. Due to
this all the departments that are involved in the methodology of agile have to work
together and hence the teams work is promoted through it (Kumar et. al., 2019).
Disadvantages of Agile Methodology
1. The agile methodology has consistently known to be failed in the projects of software
development that includes the handling of any king of complex or confusing
dependencies in the software. If the software that has to be created also needs to be extra
sustainable, maintainable as well as extensible, then is that case agile methodology is not
a correct option to choose as the risk gets increased in the agile methodology if any of the
three is required in the software that is being prepared. Also apart prom that, if some
cases it has been found to be highly difficult for the agile methodology to provide
assistance to the efforts that are to be made at the initial stage of the project or the
software (Kana, et. al., 2014).

2. The agile methodology is known to be very informal and hence no formal documentation
is done even if the project is correctly and successfully made already. The main impact of
this lack of documentation is seen at the time when there is any new person who has
joined the team or if the project has been reallocated to any other team for any reason. In
this case the new people would be finding it very difficult to get adjusted along with the
basic functionalities of the software. Even if there is no new member, there are some
cases when the older team member require a bit of guidance from the documents such as
the Software Requirement Specification (SRS) and without it the project might go into a
wrong direction (Kana, et. al., 2014).

4. What is scope creep in software development? Explain three ways to deal with scope
creep
A scope creep is defined as the tendency of a project or a software development process by the
virtue of which the requirements of the project get increased as the development of the software
moves forward in the software development life cycle. There are various negative impact of the
scope creep in any software development life cycle be it any methodology that is being user
(Madhuri, et. al., 2014). The whole planning of the project is done on the basis of the
requirement that are provided to the developer in the initial stage of the project. The deadline and
the budget of the project is also decided at the same time. If the requirements are increased in the
project in the midway of the project development life cycle, then it will have immediate impacts
on the deadline as well as the budget of the project (Amaotey and Anson, 2017).
Following are some methods by the help of which the problem of scope creep can be dealt with.
1. One of the main causes of the problem of the scope creep is the lack of updates that are
provided to the client. This means that if the client is not having the regular information
about the ongoing phases of the project then in that case it is very likely that they might
change their mind and want some more functionalities to be added in the project. Hence
in order to minimize this problem of the scope creep, the proper methodologies must be
used that involved regular updating to the client regarding the status of the project. This
will keep the client aware of the statues of project regularly and due to that they would be
having the confidence that everything is still under their control.
2. Another one of the major causes of the issue of scope creep is that the developer’s lack of
raising of issues in a proactive manner. If there is any addition made by the client that is
not possible after a particular stage of the software development and that phase have been
passed. The developer must always make sure to provide this information immediately to
the client just after they have given the requirement that this respective modification
cannot be done in the project as the project has already passes the phase where the
mentioned features could have been added and adding the feature now might increase the
timeline of the project at an exponential level. In this way the scope creep can be avoided
in this case.

3. It must always be planned during the initial stages of the project that what are the various
methods in which the project can adapt to changes if any kind of modification has to be
done in the project in the future as per the requirements of the client. The client must
always be having the ability to give some small scale changes to the project if they are
not agreeing with the work of the developer and it is the responsibility of the developer to
make the project ready for changes of these kind form the starting as well as the earlier
stages if the project.

AAA Medical Devices
As it is known that the organization has already started to develop the device and the main
functionality of the device is to monitor the glucose level of a person and the software must be
embedded to wrist band or a wristwatch which can be controlled by the smartphone of the
individual by the help of Bluetooth.
There are various fact finding techniques that can be used in this case in order to gather the
requirements that are needed in order to develop the system. Following are some of the methods
that can be used.
1. Interview: The researches or the professors who have done their studies and also have
researched or even created similar systems in the past can be interviewed which might
help in the proper analysis of the older system. Another advantage of interviewing such
people is that they can also tell about the potential risks and challenges that the developer
might have ignored while analyzing the requirements of the system.
2. Questionnaire: A random mass of the people can be taken and a particular setoff
questions can be asked to them all, this might help the developers to know the some more
of the non- functional requirements that the maximum amount of people want. This will
also be helping the whole organization of AAA medical devices to know the market
value of the product which might help to know the feasibility of the product.
3. Journals: This can be termed as one of the most effective fact finding techniques that can
be used in order to gather requirements of the systems that is being created. The journals
and researches that are done in the past on the same topic of medical devices or any topic
that is a bit associated to that can help the developer to have a proper idea and a direction
to work in order to make the system.

References
Amoatey, C. and Anson, B., A., 2017, Investigating the major causes of scope creep in real estate
construction projects in Ghana. Journal of Facilities Management. 15(4). Pp. 393-407
Hsu, F., H., Hwang, Y., L., Tsai, C., Y., Kai, W.,T., Lee, C., H. and Chang, K., W., 2016, TRAP:
A three-way handshake server for tcp. Connection Establishment. Journal of Applied Sciences.
2016(6). Pp. 1-14
Kanan, V., Jhajharia, S. and Verma, S., 2014. Agile vs waterfall: A comparative analysis.
International Journal of Science, Engineering and Technology Research. 3(10). Pp. 2680-2686
Kumar, R., Gupta, A. and Singh, H., 2014. Agile methodologies: working mechanism with pros
and cons. GIAN JYOTI E-JOURNAL. 4(2). Pp. 18-27
Madhuri, L., K., Rao, J., J. and Suma, V., 2014, Effect of scope creep in software projects – its
bearing on critical success factors. International Journal of Computer Applications. 106(2). Pp.
9-13
Qin, M., M., Liu, S., Y. and Wen, X., J., 2016, TCP three-way handshake protocol based on
quantum entanglement. Journal of Computers. 27(3). Pp. 33-40
Sasmito, G., W. and Wiyono, S., 2017, Implementation of rapid application development method
on academic staff system of harapan bersama polytechnic. International Journal of Computer
Trends and Technology (IJCTT). 50(1). Pp. 11-13
Satyawati, E., Lyna and Cahjono, M., P., 2017, Development of accounting information system
with rapid application development (rad) method for micro, small, and medium scale enterprises.
Review of Integrative Business and Economics Research. 6(1). Pp. 166-175