ICT 544 Solution

Read this document to learn about TCP, RAD, Agile, Scope Creep, and Data Collection Techniques. Get solved assignments, essays, and dissertations on Desklib.

Running head: ICT 544 SOLUTION 1
ICT SOLUTION
Author’s Name
Institutional Affiliation
Date

ICT 544 SOLUTION 2
ICT 544 SOLUTION
Q1
The two-way handshake in TCP has some limitations as only one party can establish an
ISN (initial sequence number) for connection while the second party forced to acknowledge the
connection which is a limitation because more connections are expected to be established. This is
the strongest part of the three-way handshake in TCP. TCP being a bilateral in nature in its
communication, both parties can speak, therefore, it is a requirement that they both generate an
ISN to act the starting Sequence Number (Lopez, Sun, Blair & Mukhtar, 2015). Because of all
these reasons, three-way handshake in TCP is mostly recommended because one party can
establish an ISN and then the other two parties acknowledges it and both parties can send data
because TCP is bidirectional. Always for a full TCP connection, the three-way handshake is
highly recommended in the initiation process for better communication in any connection.
Q2
RAD is an abbreviation of rapid development model which is used in project
development (Moreno-Lizaranzu & Cuesta, 2014). RAD is a development model that was
adopted from the famous waterfall model and mostly focus on projects that are on a short term
basis as per the description is given by the user. Some projects may be demanded by the
customer to be completed as soon as possible and in a case like this RAD is the best option for
the project managers to adapt to meet the short deadline set by the customer.

ICT 544 SOLUTION 3
Advantage of RAD
Flexible to any change that is suggested by the customer. The project manager and the
developers are always very keen on the updates the customer issues until the last day of the
project presentation.
Disadvantage of RAD
Not all projects can be done by the RAD model as some are very complicated and if
rushed using this model can lead to a big failure or the developers fail to deliver on time.
Q3
Advantages of Agile
Agile development model has big advantage to the side of the customer as the project is
delivered exactly at the stipulated time or just before the set deadline and this helps the customer
to plan him or herself enough (Gray & Rumpe, 2018). The customers, developers and the project
managers constantly interact worth the project daily like if the project is developing a certain
software, the user can monitor daily progress via the updates from the project managers and the
developers are able to acknowledge any change suggested by the customers and the final product
is always great.
With the Agile development model, face to face communication is most used and this
helps the developers and the project manager get clarification from the customers so nicely such
that no requirement that can be left behind. Because the customer is involved constantly and the

ICT 544 SOLUTION 4
possibility of him or her being satisfied are very high because of the constant updates and the
room given for suggestions and changes as the development continues up to the last requirement.
Disadvantages ofthe Agile model
For large projects, Agile model faces a challenge as the project manager may fail to
exactly estimate the deliverables or the labor required before the project starts and this can lead
to confusion when the project has already kicked off which may lead to a loss for the company.
This is because they may be forced to hire more skilled personnel in a case where they under-
estimated the required personnel.
This model limits the junior developers from contributing much to the project
requirements as only senior developers contribute a lot and mostly their final view is the one
followed. This can lead to them not contributing their important views which can make the
success of the project and be a disadvantage to the customer and the company as well because
they will lose a customer.
Q4.
Scope creep in software development refers to the way the requirements of the project
tend to go high over the lifecycle of the project (Mahmoud, 2018)The development of a new
software is usually as a result of the users identifying a need and then identifying how a new
software will meet that need, which now becomes the scope of the project. All the plans and
estimates are drawn based on that scope. However, as the time progresses, the user may identify
other additional requirements that they did not mention during the initial stage of the software
development causing changes to be made to the original plan, more time spent as well as
increased costs. This is what is referred to as scope creep.

ICT 544 SOLUTION 5
The following are the various ways to deal with scope creep;
 Make sure that the functional requirements during onset of the project are
written down in a simple language well understood by the user. For example, you can
give the customer a walkthrough of the things that the new software will do, screenshots
and understand the point of view of the user.
 Ensure that the customers agree and signs on list of the functional
requirements which should include a clear scope statement. This serves as the legal
binding that the functionality of the software is only what is covered in the statement and
anything else not included is outside the scope.
 In the case where the user requests for a new functionality to be added,
evaluation is done on how it will affect the overall project duration and cost. The new
revised specification should then be put into writing indicating why it was amended and
also to include a new scope statement.
 If the new addition of the function greatly impacts the project and
duration, the customer should be made aware of the new budget and changes in the
timeline through writing for reference purposes.
 It is then up to the customer to make a decision if they are willing to pay
more and comfortable with the new timeline.
 If they are in agreement then they should sign the new specification as
before.

ICT 544 SOLUTION 6
Q5.
The following are some of the techniques that can be use to collect data from the
potential users of the system;
 Interviews
This is one of the most efficient ways of fact finding. It is very helpful to find out
the state of the current system and what the users expect to benefit from the newly
developed system. They are very effective because mostly they involve face to face
communication where the users open up about any areas of misunderstanding and
problems that they want to be solved (Lloyd & Hopkins, 2015). As an analyst, this is
usually the best method to clear out any unrealistic expectations about the new system
and provide some more information about it to the users as well as deal with possible
resistance to the new system. However, interviews have a major drawback of being very
time consuming especially if a large number of people is involved.
 Questionnaires
Questionnaires are quite effective than collecting information from a large group
of people (Parajuli, 2008). One can either used open-ended or closed questionnaire. Open
ended are whereby the respondent is not limited to choose answer from a list of provided
options. They are free to give answers in their own words and are suitable to find out
about people’s opinions, feelings and their general view about the system. Closed
questionnaires have a predetermined set of options that respondents will choose as the
answers. Suitable if the analyst wants to find out specific information.

ICT 544 SOLUTION 7
 Record Inspection/ Reviews
This involves the inspection of the available records such as bills, regulations,
reports, policy manuals or the standard operation procedures. This gives the analyst an
opportunity to draw conclusions without relying on information from other people.
 Observation
This is another method that an analyst uses to get information without asking
questions from other people. He/she just chooses a strategic place, person or a group of
people to observe. Just by looking on how the work is done, the general conduct and the
interactions between people the analyst is able to gather information about the current
system and the issues that the new system should focus on.

ICT 544 SOLUTION 8
References
Gray, J., & Rumpe, B. (2018). Agile model-based system development. Software & Syste
ms Modeling, 17(4), 1053-1054. doi: 10.1007/s10270-018-0694-1
Lloyd, J., & Hopkins, P. (2015). Using interviews to research body size: methodological
and ethical considerations. Area, 47(3), 305-310. doi: 10.1111/area.12199
Lopez, J., Sun, Y., Blair, P., & Mukhtar, M. (2015). TCP three-way handshake: linking d
evelopmental processes with plant immunity. Trends In Plant Science, 20(4), 238-
245. doi: 10.1016/j.tplants.2015.01.005
Mahmoud, M. (2018). The Role Software Project Scope Verification in Software Develo
pment. International Journal Of Computer Applications, 182(7), 26-29. doi: 10.51
20/ijca2018917647
Moreno-Lizaranzu, M., & Cuesta, F. (2014). A framework and architecture for rapid soft
ware development: a success story. Empirical Software Engineering, 20(6), 1456-
1485. doi: 10.1007/s10664-014-9320-1
Parajuli, B. (2008). Questionnaire: A Tool of Primary Data Collection. Himalayan Journ
al Of Sociology And Anthropology, 1, 51-63. doi: 10.3126/hjsa.v1i0.1553