Network Protocols and SDLC: A Comprehensive Report

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

NETWORK PROTOCOLS AND SDLC

Table of Contents
Introduction:...............................................................................................................................................3
Q.1)..........................................................................................................................................................4
Transmission control protocol.............................................................................................................4
Q.2)..........................................................................................................................................................5
RAD......................................................................................................................................................5
Advantages of RAD..............................................................................................................................6
Disadvantages of RAD..........................................................................................................................7
Q.3)..........................................................................................................................................................7
Agile method.......................................................................................................................................7
Advantages of agile methodology.......................................................................................................7
Disadvantages of Agile methodology..................................................................................................8
Q.4)..........................................................................................................................................................8
Scope Creep.........................................................................................................................................8
Q.5)........................................................................................................................................................10
Conclusion:................................................................................................................................................12
References:................................................................................................................................................13

Introduction:
In this report, the student will know about Network protocols and SDLC. And also know about
the different methods of network protocols and as well as their advantages and disadvantages. In
short, this report gives all the information about network protocols and how to communication
done between two or more devices.

Network protocols & SDLC: Network protocols can be defined as it is procedures and comprised of
rules which are used to communicate between more than two devices over the network. And it
gives all the security and managed data over the network. while SDLC(synchronous data link
control) is a communication protocol of computer. SDLC is a layer two protocol for
SNA(System Network Architecture). SDLC is used for linking multipoint and for error
correction.
Q.1)
Transmission control protocol: TCP is a protocol that is used to establish the network
connection and manage network communication via application program which can exchange
data. TCP is used with internet protocol(IP) which gives information about how the computer
sends data of packet to each other. The transmission control protocol(TCP) is a connection-
oriented protocol, which means the connection is maintained and established until the application
finished exchange data from both sides.
In TCP three-way handshake is needed instead of the two-way handshake because if TCP uses a
2-way handshake than it allows only one party to settled/established an initial sequence number
and another party only acknowledgment it. In short, in a two-way handshake, only one
device/party can send data while in a Three-way handshake, both parties can send the data to
each other without any restriction. And TCP is a two-way(bi-directional) communication
protocol which means both parties can establish an ISN(initial sequence number) and give
acknowledgment to other’s initial sequence numbers (ISN). In short, both parties can send the
data reliably.
The two-way handshakes works as a Client send the synchronization to the server for established
a connection so client can send the data to the server after getting the synchronization from
client, the server sends back acknowledgment that I’m free and then after getting the
acknowledgment from server, they established a connection and then client can easily send the
data to the server but the server cannot send back to the data packets. while in three-way
handshake a client sends the synchronization to the server and server accept its request and send
acknowledge back and also send a request to the client after getting the request from the server,

the client sends back an acknowledgment to the server to establish a connection. After
establishing a connection both parties(client and server) can easily send the data and receive the
data at both sides. The 3-way handshake is needed because both(client and server) parties needed
to synchronize their SSN(segment sequence number) which is used during the transmission.
Each party has to send the SYN segment consist of sequence numbers than it is acknowledged by
another party by the ACK segment. In order to work the connection, each party has to verify that
it can send data or packet to another party. The TCP uses two-segment, the first one is SYN and
another one is ACK. SYN means to request that a packet is sent and ACK means it is sent after
getting the SYN to prove that this packet is received. the three-way handshake works as
following:
First party----SYN---- Other party
First party-----<SYN/ACK----- Another party
First party-----ACK----- Other party
before establishing the connection, both parties need to confirm four points:
 Second-party(server) need to confirm that he can receive data or packet from first-
party(client).
 The first party needs to confirm that he can receive data from the second party.
 The first party has to confirm that, Second party can receive the packet from the first
party.
 Second-party has to confirm that, First party can receive the packet from the Second
party.
Q.2)
RAD: RAD stands for Rapid Application Development. RAD is an endorsement of the waterfall
model which is used to develop software at a minimum time or less time. RAD usually cling
Object-oriented programming technology.
SDLC RAD(rapid application development) model has many phases which are the following:

 Business: Business modeling is used on the basis of the flow of data or information and
circulation between different-different business channels where the product designed.
 Data: Data modeling is used to delicate the information which is collected from
BM(business modeling) into a set of object data that are useful for the business.
 Process: The data object which is initialized into the data modeling is now transformed
to get the necessary information flow to implement the business function.
 Application Generation: computerized tools are used for making the software, to convert
data models and process into prototypes.
 Turnover and testing: These prototypes are individually tested at every iteration. The
total time of testing is reduced in RAD.
Fig: RAD model
It is mostly focused on output-input sources and harbor of the information. It delivering the
project in a small category means the bigger project divided into smaller-smaller projects. this all
small piece of the project is delivered and planed individually. The main moto of the RAD model
is to reuse the templates, processes, and tools.
RAD methodology is used:
 RAD methodology is used when a product/system needs to be developed in a minimum
or less time(around 2-3 months).
 RAD methodology is used when users involved in the whole life cycle.

 RAD methodology is used when the risk of technology is less.
 RAD methodology is used when there is needed to be software developed at a span of
time.
 When all the requirements are known than RAD methodology can be used.
Advantages of RAD: There are many advantages of RAD, which are the following:
o It is very flexible and versatile to change.
o It is useful and helpful when the team has to reduce project risk.
o Every phase of the RAD methodology delivers the best functionality to the user/client.
o With minimum people, productivity can be high in less time.
o It has fewer chances of defects.
Disadvantages of RAD: it has disadvantages also, which are the following:
o It cannot be used for lower/small projects.
o Not all software is good or best with RAD.
o When the technical risk is higher than RAD is not able or suitable.
o RAD project can fail if the developer did not commit to the delivery of software or
system on time.
o It requires or needed highly skilled developers and designers.
Q.3)
Agile method: The agile model is a type of incremental model. Agile methodology promotes
continuous iteration of testing and development throughout the SDLC(software development life
cycle) of the project. The agile model is created with the increment and iterative model. The
main moto of the agile model is to take care of customer satisfaction and process adaptability.
some year ago, the iterative model is used for to develop the software but today developers have
to face many troubles or issues at the time of development of software, one of the main problems
is that in between the software development any customer wants to change in the software then it

can be a issue for the developer and it takes much time and cost which is not good sign of the
software development life cycle(SDLC). For solving these issues, in the mid-1990’s the AGILE
model is launched. The main moto of launched the agile model is that it can be used whenever
the changes are needed in between the software development so that the project could be
developed very fastly.
Advantages of agile methodology:
o In this, two coders or programmer works togetherly so from which it will be resultant as
less mistake during the software development.
o It is a realistic approach to software development.
o It has less rule and the documentation is also less.
o It does not need any planning.
o Agile methodology believes in teamwork.
o Agile methodology can be managed easily.
o It was firstly developed for the software industry.
o It has fast turnaround times.
o In this, no worry about premature optimization.
o The main advantage is that the developer can test and experiment with the project
because it has a low cost.
Disadvantages of Agile methodology:
o It can not handle the complex dependencies.
o Lack of formal documentation, there may be little bit confusion in the documentation.
o It depends on the customer if the customer gives the wrong information than software
will become useless.
o The main disadvantage is that in this only experienced programmer or coder take the
decision.
o In this, the developer can not measure the cost and effort and time before the software
development.

o It demands more energy and time from every man because customers and developers
should interact with each other constantly.
o It is not used for small projects.
o The cost of agile methodology is high as compare to other methodologies.
o The project can terminate from the track if the project manager is not sure and clear about
what outcomes and requirements the user wants.
Q.4)
Scope Creep: Scope creep refers to a project which is used to see its goals which have to be
achieved while in between the progress. As the name suggests, creep of scope is a process that
starts with small alteration and ends with resultant as it takes long term to complete or fails
before the project finished. Scope creep is also called creeps of scope, requirement creep, and
kitchen sink syndrome. If the project was successfully completed then it can be resultant as in
last deliverable. The scope creep refers to project management as to changes, uncontrolled, or
continuous growth in project scope. In between the project development, the scope creeps occurs
when the scope of project is not clearly defined, controlled or documented. It is considered
harmful. It is a little bit same as feature creep because feature creeps are referred to features
while scope creeps refer to the whole project.
Creep of scope can be achieved for many reasons which are the following:
1) Poor knowledge and understanding of the project.
2) If the market condition is changed.
3) Compete force within a company.
4) Poor or least communication between both parties.
5) Lack of project object, this can result in scope creep.
6) It occurs when changes are done to the scope of the project without any power or control.
There are many ways to deal with the scope creep, they are the following:
 Documentation of the requirement: The most important way to avoid the creep of
scope on project to make the document of all the requirement which is needed in

between the development of project. To document all the requirements, the
communication should stand between the project stakeholder and users to make a
decision that what exactly they want in the project. This means clear the objective and
goals of the project. Suppose if one stakeholder wants the website to be blue and another
stakeholder wants the website to be green than they should make a last and final
decision. This is time-consuming for record and document all the requirement but if it
once did then it can be very helpful for the project stakeholder to create better software.
 Create a clear project schedules: use the requirement gives the better software. The
project schedule is used for knowing that what the project will deliver and it should
display all the requirements and how can this achieved also should be done in the project
schedule.
 Setup changes control processes: if the documentation of requirement is ready but what
would happen if any changes made in between the project development. A change
control process is used when someone made changes. Then it should be reviewed,
approved, or reject. These changes should be discussed with the project sponsor and
team member of the development team.
Q.5)
Real-Time Glucose Monitoring (RTGM): Real-Time Glucose Monitoring has potential to add
the details of patients and providers in the management of blood glucose patterns. If any
organization wants a device that is wrist-based and gives all the information from the body heat
and gives the senses of glucose levels from body’s perspiration. The RTGM system used this
device because this device all the information about the body like temperature, sugar level,
blood, weight, and etc. this can be very helpful all over the world. To make or develop this
device the system analyst has to collect or documentation of the all requirement which could be
used by device. This system should be easy going in the smartphone with Bluetooth facility.
The system analyst uses a fact-finding technique to collect the information of requirement from
which the device can be easily developed without any causes. Fact-finding is a process that
collects the data and information based on techniques which consist documentation, observation,
interviews, questionnaires and research planning. The system analyst chooses those fact-finding
technique which is suitable for those devices. Collect the information of requirements is the most

powerful tool to implement in the software development life cycle(SDLC). There are many fact-
finding techniques but the system analyst chosen three fact-finding technique which is suitable
for that device development.
1) Sampling of existing documents, databases and forms: The best method to analysis
the existing software or system is collect from the document of requirement of the
existing software instead of human sources. There can be different-different types of
documents which is to collect from existing systems, such as Email, notes, suggestion
box, customer complaints, customer feedback, different types of diagram and flowcharts,
samples of completed user form. These all the documents can be helpful for the new
system which is to develop with the help of the existing system.
2) Site visit and Research: this is the second technique that is chosen by the system analyst
which is suitable for that device and system. It is a process which is used for examining
the problem which is occurred previously and solved by other resources and sources they
are either document or human. To solve the requirement problem, the system analysist
visits the another organization that follows the same problem. Although the system
analyst can also collect the information from reference books, databases, internet and
case studies. This technique saves time if any other person already solves this problem.
3) Observation of the work environment: another fact-finding technique is observation of
the work environment which is chosen by the system analysis which is suitable for that
device. In this technique, the system analysist goes to the organization, studies the flow
of charts and documents, interact with the different-different user. The main technique is
to collect the information of requirement is observation because observation can be
helpful and useful when the analysis has user point of view. With the use of technique the
system analysist can easily know how the employee spends their days.

Conclusion:
In this report, the network protocols and SDLC are discussed. The network protocols are used to
communicate between two or more systems over the internet. The main conclusion which comes
from this report is that three-way handshake is needed in TCP instead of two-way handshake.
The agile methodology is also launched for better software development. This report also tell
that the system analyst can choose any fact-finding technique as their requirement.