Analysis of Network Protocols and Software Development Methodologies

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

ITC544
Assignment 2: Network protocols and
SDLC
Assessment Item - 4
Student name –
Student ID –

Contents
Question 1........................................................................................................................................3
Question 2........................................................................................................................................3
Question 3........................................................................................................................................7
Question 4........................................................................................................................................8
Question 5......................................................................................................................................10

Question 1
This task will help in giving various reasons for using 3- way handshake rather than 2-way in
TCP. The 3-way handshake is the procedure to establish connectivity such that server and Client
can communicate with each other. During communication, both server and client keeps tracking
the sequence number to verify what they have sent. Technically, it counts the byte which is sent.
The acknowledgement by the receiving party can be done by using the sender’s sequence no.
Sequence Number doesn’t always start from zero, it begins with ISN (Initial Sequence Number)
considered as the randomly generated value. The importance of sequence number is that it helps
in identifying which message is lost and also help in finding how many duplicates of the single
message is sent. It is known that TCP helps in conducting both ways communication and hence it
allows both the side of the system to generate its ISN randomly. It implies that when they
generate ISN it must send a notification to the other party about its sequence number.
The following diagram shows the communication process which occurs in 3 way handshake.
Here we can notice four main events to occur which are as follows:
1. The client generates sequence no. and synchronizes its ISN with the server.
2. Server Acknowledge the ISN of the client.
3. Then Server generates its own ISN and synchronizes with the client.
4. Client Acknowledge the ISN of the server.
The two events (2 and 3) occur in the same packet. The occurrence of ACK and SYN is due to
on and off of binary flag in TCP headers. And if in this place, 2 – way communication is enabled
then it will only allow one of the parties out of client and server to send data and generate ISN
but as TCP supports two-way communication which 2 – way handshake does not allow it. The
procedure which occurs in 2 – way is shown below
Client
Client
Client
Server
Server
Server
SYN
ACK/SYN
ACK
Client Server
SYN
Client Server
ACK

Question 2
RAD is the type of incremental methodology used for developing software based on iterative
prototyping. It does not require any specific planning. The requirements in this model are
collected with the help of the focus group. It aims at quick delivery by integrating functional
modules and Prototypes which are developed simultaneously. The whole project is divided into
small chunks which are incorporated to conduct the whole project.
The different phases of the RAD are as follows:
Business Modelling – It involves the information flow to a different channel. This phase helps in
accomplishing the requirements of analysis and planning. It helps to gives the overview of whole
project functionality. The deliverables which are achieved during this phase are project scope,
applications requirements, work plan, sequential procedures, business case and needs and system
requirements.
Data Modelling – It is the phase which involves modelling of data collected in the previous
phase so that thorough analysis and evaluation can be conducted. It also contributes to building
the prototypes by determining the architecture of the RAD framework and taking feedback from
the user.
Process Modelling - The phase is involved with the actual working which involves integration,
testing and coding. Any changes which occur in the project are defined here to maintain the flow
of information. This process keeps on repeating until all the necessary requirements are
achieved.
Application Generation – This implies the completion of coding part and development of the
application. It generally takes use of automated tools for building the software. This phase helps
in the creation of prototypes by converting the processes into models. The coding elements
which are developed are test cases with the help of a live environment. Application Generation
also helps in saving time by independently testing each phase.
Turnover and Testing – When the whole system is built, it is tested independently and
handover to the final end-user.

Figure 1: Phases of RAD
Advantage of RAD
 It helps in developing the product rapidly and quickly.
 It also helps in reusing the various components of the software which help in saving time.
 It helps in achieving constructive feedback.
 It also helps in measuring the progress of the project.
 It also helps in reducing the iteration time.
 It also helps in increasing the productivity of the whole project by taking a small team of
people.
 It also helps in accommodating and maintaining changes which occur during the project
progress.
 It also helps in giving repetitive reviews and feedback during every phase.
 It also helps in evaluating the budgets and schedule of the project.
 It helps in developing various prototypes which are independent of each other.
 It also provides advantages of extensibility, portability and interoperability
Disadvantage of RAD
 During its initial stage, a gathering of resources takes a lot of time and effort.
 It is not suitable for small scale and projects having no project.
 It requires high skills in the modelling process and is highly dependent on it and failure in
this fails the overall project.
 The complexity of the management is very higher.
Business
modelling
Data
Modelling
Process
Modeling
Application
Generation
Testing and
Turnover

 It involves high involvement of the user in each phase of the life cycle.
 Modularized system can only build with the help of this modelling.
 Code generation of automation is very high.
 It also helps in reducing the scalability of the project.

Question 3
Agile is the methodology of software development prototyping, incremental and iterative
building process. It works by building the whole project into small chunks which are presented in
iterations. These small segments are shown to stakeholders to take valuable feedback so that
appropriate improvements can be made. This unstructured methodology helps in conducting the
testing from the initial stage so that errors and flaws can be reduced. Example of most used agile
methodology is Scrum, Kanban, Extreme programming, Lean Software and Crystal Clear. The
four main core focus area of the agile methodology is as follows.
1. Focuses more on interaction and teamwork rather than on tools and processes.
2. Believes in working and functional software rather than documentation.
3. Give more emphasis on collaboration with the customer.
4. Helps in following the plan by simultaneously managing the changes.
Advantages Disadvantage
 As the whole project is divided into a
small group, the product quality is highly
achieved.
 It provides more flexibility as it helps in
delivering quick deliverable to the end-
user.
 It gives more emphasis on face to face
interactions.
 Changes are incorporated from the initial
phase of the project.
 It helps in improving customer
satisfaction.
 It embraces changes which are made at
the last moment.
 It gives significance to the design and
technicality of the project.
 It helps in providing turnaround time very
quickly.
 Helps in providing transparency in the
business process.
 It also helps in saving time as risk and
errors can be detected earlier.
 Highly based on the customers, hence it can
possess issues if the customer has no clue of
objective and the processes involved.
 As it does not focus on documentation, it
can lead to dependency on the skilled
person for the training process.
 Estimation of resources becomes very hard
for the project having complex nature.
 As changes and features keep on evolving
there is no consistency provided in the
project.
 Decisions are always taken by the senior
developers and hence not pay attention to
the new programmers.
 Progress cannot be measured easily in this
methodology.
 It faces the problem of scope creep.
 There is a lack of product cohesion because
designs and outputs are fragmented.

Question 4
Scope Creep is defined as the event which occurs when the project goes beyond its scope. The
budget, deliverables, feature, deadlines exceed from the initial planning of the project. It is very
necessary to deal with the problem of scope creep because it can result in the overall failure of
the project. The result of scope creep can lead to wastage of resources and money; it decreases
the satisfaction of the customer and cannot complete all the required deliverables.
In simple word, it is defined as the additional features which have been added in the project
without considering its adverse effect on the cost, time and resources. The various reasons which
can cause scope creep to occur are listed below:
 When the objectives and clarity of the project are not mentioned.
 Change management and control are poorly maintained and implemented.
 Unnecessary involvement of the stakeholders.
 Not getting proper support from the managers, owners and sponsor.
 Not taking approval of the client and taking the wrong decision.
 Quality Assurance is not conducted properly.
 Initial Requirements are poorly defined.
 Poor communication and Documentation is also one of the reasons.
Scope Creep is of two forms: technical as well as business which is explained below:
Business Creep – It occurs because of the external driving forces which are not controlled by the
managers. For example, changes which occur in the trends of the market are out of anyone’s
control.
Technical Creep - It generally occurs when the team agrees upon every request from the
customer, without taking into the account the scope, budget and other things in the project. Gold
– Plating means amendments of additional features which are initially not included in the project
plan also cause the issue of technical creep.
To manage the scope creep following steps should be kept in mind:
 Scope Creep is a little difficult to control due to changing nature, hence it becomes very
necessary to prioritize the features involved in the project.
 Requirements should be analyzed critically in the initial stages to avoid any afterwards glitch
in the project.
 Involvement or user, stakeholders, end-users should be done in the early stage of the project.
 Don’t always say yes to changes, critically evaluate the whole scenario and take a decision
considering all the other requirements.

 Implement the change management and mitigation process, which will help in deeply
evaluating the changes and take decision according to it.
 Clearly outline the project scope, schedule and deliverable before starting the project.
 Involvement and proper communication plan are very necessary to communicate the
information to every team member for the successful completion of the project.
 Proper Documentation of everything involved in the project should be done to avoid any
conflict.
 Scope management process should be involved for modelling, traceability, analysis and
prioritizing
 It is very necessary to discuss the impact of the scope creeps with stakeholder to maintain
transparency in the business processes.
 Divide projects into small chunks to avoid any errors in the project and follow a proper
methodology for project completion.


Question 5
Given Scenario: AAA is the medical devices manufacturing company which aims at
manufacturing the wearable and portable devices. Recently they developed a glucose monitoring
device which is embedded in the wristband. Now the AAA Company is planning to develop
RTGM (Real-Time Glucose Monitoring System) which will utilize the wristband.
The various advantage of this RTGM is that it will help patients, doctors and healthcare
providers to monitor the dangers including both short as well as long term impact. It will help in
maintaining the glucose level in the patient’s body. It will also help in taking necessary steps to
the encounter danger. Figure 2, shows how the system is going to work and how the movement
of data occurs between devices and the intended users.
Figure 2: System working of RTGM
The different requirements of the new system are as follows:
Functional requirements
 Connectivity of application with the wristband – This two application will be connected
and integrated with each other with the help of APIs.
 Displaying correct reading – These requirements help in showing the right readings of
glucose from Bluetooth device to the intended application.
 Bluetooth Communication – It will help in maintaining the flow of information i.e. sending
and receiving of data.
 Back-Up – the application provides the feature to save data both on online as well as local
storage.
 Tracking of Users – These requirements help in tracking the minute quantities of
perspiration and body heat.

 Alarm – With the help of a GUI interface, it will allow the user to set alarms.
 Authentication – This functionality will help in successfully log in and sign – up in the
application.
Data Requirements – It is the requirement which is essential for storing the data.
 Firebase – It is the software which is used to back up the data and help the user to perform
the operation of sign in and sign out.
 SQLite – It is the database application which is utilized for data storage.
User Requirements – It is the requirements which the user should possess when using this
system.
 API
 Internet Access
 Device
 Bluetooth connectivity.
Usability requirement – It is the non – functional requirement which is used in the new system
are as follows:
 Easy Understandable – The system must be that it is easily understood by the users and have
a consistent layout and design.
 Learnability – It must provide the user with the functionality so that they can learn from the
buttons they navigate and perform all the functionalities easily.
 Attractiveness – It must-have the feature of attractiveness so that user has easy navigation
and can easily help in using the button.
 Operation ease – This means all the functionality of the system should be performed with
efficiency and display correct results.
Security Requirements – This requirement is related to the security and privacy of the new
system developed. It can be done with the help of Password encryption and authentication.
The potential use of this system will be the patients who need to calculate their glucose level,
healthcare providers like hospitals can use this system to manage changes and precisely calculate
the glucose level of the patient. Doctors can use this system to calculate the values and reduce
human errors in the process.
The three techniques which are used to collect the fact-finding of the requirements of RTGM
process are as follows:
1. Interviews – It helps in gaining good information. It takes in-depth detail about the
requirements and provides one to one communication.

2. Brainstorming – It can be done either in a group or individually. It helps in collecting very
creative and innovate ideas regarding the requirements of the system.
3. Questionnaires – It is very advantageous one on one way of calculating the requirements
form the different stakeholders, sponsor, user involved in the project. It gives the real
perspective of why the people and stakeholder are interested in the project.
4. WorkShops – It is the process in which group of people sit together to find the requirements
and discuss all the necessary actions and activity need to take in the development of the
project.
5. Use cases – It involves the stories which will help in describing the working and main
functionality required in the system. It helps in describing the whole system from the point of
view of different people mainly users.