Software Development Project: Scope Creep and Fact-Finding

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

Table of Contents
Introduction .....................................................................................................................................2
Q 1...................................................................................................................................................3
TCP/IP network ..........................................................................................................................3
Q 2...................................................................................................................................................3
Rapid application development ..................................................................................................3
Advantages of RAD ....................................................................................................................4
Disadvantages of RAD ...............................................................................................................4
Q 3...................................................................................................................................................5
Agile methodology .....................................................................................................................5
Two advantages of the agile development model .......................................................................5
Two disadvantages of the agile development model ..................................................................5
Q 4...................................................................................................................................................6
Dealing with scope creep ............................................................................................................6
Q 5...............................................................................................................................................7
The fact-finding technique ..........................................................................................................7
Conclusion ......................................................................................................................................9
Reference ......................................................................................................................................10

Introduction –
This project is discussed the synchronous data link control and the network protocol. The TCP
protocol used three-ways handshake and it discussed the agile methods and scope creep in the
software development and rapid application development is also discussed in this project. The
fact-finding technique for the requirement of the development of real-time glucose monitoring
system is also described.

Q 1.
TCP/IP network -
To connect the server and a local host in a TCP/IP network a method is used, this method is
known as the three-way handshake. In this method, both the server and the client need to
exchange ACK and SYN packets and after the exchange of these packets, the data
communication begins.
In a three-way handshake, first, an SYN data packet is sent by the client or host node over an IP
network. By sending SYN packet a client knows that the server is ready for the new connection
or not. If the server is free and ready for the new connection, then receives the SYN packet and
send the SYN/ACK to a client. After the reception of SYN/Ack packet by the client node, it
sends back the acknowledgment packet that it is also ready for the connection. So, both the
parties in three-way handshake establish. After this process, a server and host can communicate.
In two-way handshake first, an SYN data is sent by the host node over a network. The SYN
packet is received by the server and it sends back the Ack package by sending the Ack package it
makes a connection with the client node and the communication between server and host will
start. So, ISN is established by only one party, which means the data is sent by only one party.
But the communication protocol in TCP/IP is bi-directional which means both server and client
can send and receives the data on TCP protocol. So, it needs to send the ACK package back to
the server and then the server sends the SYN/ACK package back to host and the communication
will start from both side in TCP protocol.
Q 2.
Rapid application development –
To speed up the development of software application the rapid application development is used.
To produce application of software the RAD use prototype technology that is predefined. It
allows to easily drop and drag the required application component of software by the end-user
and surrounded by the GUI development. To produce software application fast and to employ
various tools, rapid application development is used. To create structure, predefined component
and methods to develop a software model quickly. Full-scale functionality is a lack of RAD

software prototype. Primarily used for requirement gathering and demonstration. Organization
model, customized data and processes are containing in RAD. So, the object-oriented and model-
driven approach to develop a solution is employed by RAD. Project is delivered in small pieces
in RAD. It reuses the code, tools, templates, and processes.
The phase for the RAD model is data modeling, business modeling, process modeling, generate
the software, turnover, and testing. The product is design based on the information in the
business modeling, to construct the software the automated tools are used for generating the
application. And after the generation of the application, the application is tested but during
iteration, the prototype is tested so less time taken to test the application.
The RAD methodology is used when there is a minimum time to produce the application. And it
has all the requirements, And the risk to develop the application is less, and the system needs to
modularized in 3-4 months, this methodology is used when the automated tool cost is high for
the generation of the code and the budget to create the application is also high.
Advantages of RAD –
1. The changes are adaptable and flexible.
2. The project risk is also reduced by the RAD model.
3. In the RAD model intermediate code, high-level abstraction and scripts are used so the
deliverables are transferred easily.
4. The manual coding is also reduced because of the reuse of code and generation of code.
5. The defects in the RAD model are also less because of prototyping in nature.
6. The maximum priority functionality to the client is delivered by each phase of the model.
7. Increase in the productivity of the application with fewer people in a short time.
Disadvantages of RAD –
1. Smaller projects are not created by the RAD model.
2. RAD model is not compatible with all the application.
3. Not suitable for the high technical risk.
4. The RAD project fails when the software delivering by the developer is not on time.
5. Timeboxing can reduce the features of the application because to finish the project early
the features are done in the next update of the application.

6. The scalability is also reduced because to finish the application early the RAD developer
develops the prototype application.
7. To develop the application in RAD model developer or designer needs to be highly
skilled.
Q 3.
Agile methodology -
Type of incremental model is agile development model. The software is developed in this model
in a rapid and incremental cycle. To ensure that the quality of the software is maintained, each
incremental release is tested. The best agile development model is extreme programming. By the
agile development model, the software is delivered on time so, a customer is satisfied. And if a
developer is wanting to change anything in the software after the development then it is also
possible.
Two advantages of the agile development model –
1. When a developer is wanting to alter the application, he can change it easily because the
agile gives the freedom to change any part of the application if needed. and the cost
required for change any part in the application is not that much because in the agile
development model the new increment frequency is produced. And in any other model,
the late change is not possible in an application. And if a developer wants to implement
any change then the cost to implement the change is high because the developer needs to
recreate the application to implement any change.
2. In the agile development model, the development of software is in a rigid sequential way,
so they got more option and time freedom than any other model. To start the project in
the agile model very limited planning is required because agile assume that in the IT
world and dynamic business the change in the application is needed time to time. And the
important decision is made when a developer has better data or when the hosting program
is available because of this option in the agile model. Without any fear of the failure, the
developer can continue the project to move forward.

Two disadvantages of the agile development model –
1. Predictability is less –
In the agile model, the efforts that are required to make an application cannot quantify by
the developers. And on the larger product, it is impossible to calculate effort in
development life cycle by the developer. So, the fear of the failure of the project is
always on the team in the agile methodology. A developer is frustrated and makes a poor
decision because of the fear. So, there is no idea how much time is taken to make a
product and what is the cost of the product if the product is large.
2. The project falls off the track –
Planning required in this method is very little and agile assume that in the IT world and
dynamic business the change in the application is needed time to time. Because of this
assumption, the agile model is stuck in a limit. And the developer might focus on wrong
areas if the customer’s instruction or feedback is not clear. And more energy and time is
required in this method. When the budget of the client is not high then this method it
can’t be used because in this method high budget is required.
Q 4.
The software is developed on the information of the need of the customer. And when the
information of the project is not properly given by the customer then scope creep occurs. The
results of scope creep are the software change control is poor, the executive sponsor or project
manager is also weak, and the requirements of the project are not proper, and communication
between the parties is also poor. The operational efficiency of the company is affected by the
scope creep and long-term relationship can be broken between the customer and the company.
there are two types of scope creep one is business scope creep and other is technical scope creep.
When a team is not able to reject the request for the scope change in the project then the
technical scope creep is shown. The additional features are adding by the team that is not part of
the main project just to maintain good relations with the customer.
If the customer forces the project manager to change the scope and manager can’t do anything
then the business scope creeps to occur.
Dealing with scope creep –
The specification of the function is produced at outset and written a way that it is understood by
the customer easily. The customer agreed and sign the specification of the function and the scope
statement is also included in the specification of the function.
1. Understand the requirement of the project – before start making the project a developer
must know the requirement of the project. The complexity of the project is must know to

balance the resources and timeline of the work. Deliverable is broken into tasks, so the
project is fast to create. Put the minor and major milestones on the timeline. To keep the
project on track review milestones whenever there is a request for the changes.
2. Online project management software must use – to manage scope creep the online PM
software is a very important tool. Always use that software that gives visibility to clients
and software team, so work done is faster and easier. Once the developer establishes the
rule then the project management tool is used for the request handling for changing the
scope. If the scope changes then the work tasks and schedule also change.
3. Say no to the unreasonable request – if there is an unreasonable request to changing the
scope then a developer must say no to that request because all changing scope is not
equally created. And the project delivery is delayed because of the scope change request.
And if a developer can’t say no then he must use the following alternatives-
If a developer something adds into the scope, then he must take out something from the
scope to maintain the zero-sum game. And start the second project as the backup for
denied the request in the current project.
Q 5.
The fact-finding technique -
To construct the required system the system analyst detains the necessary facts. The facts are by
using the current system how to encounter the problems, what are the requirements for the new
system, necessary constraints on user and data of the new system, and the set priority for the new
system requirements. By the fact-finding technique, these facts are capture. The system analyst
needs to confine the current system facts.
1. Documentation examining – it is a very helpful fact-finding technique to find the
requirement for the real-time glucose monitoring system. By making the document of
what the system needs to be perfectly used to monitor the glucose by the heat of the body.
And not any problem occurs to wearing it. And if any problem occurs that it is also
written in the document to solve that problem. By examining files, reports, forms and
documents associated with the real-time glucose monitoring system. A system analyst can
get good concept for the system. In the documentation, there are data of the system that
have advantages and disadvantages of the system. Means what are system advantages and
in how many ways it is helpful for the people. And what service may the system will
provide to the customers.
2. Interview – very useful and frequently used fact-finding technique is to interview the
person and get the information what they need in the glucose monitoring system. By
interviewing the people all facts and needs of the system are in front of the system analyst
then he must analyze those fact, generating enthusiasm, clarify the fact are helpful or not
helpful for the system, identify the requirements for the system. And he has ideas for the

project by interviewing the people. For interviewing the people, a system analyst must
have good communication skills because all people have different personalities, opinions,
values, motivations, and priorities. By the feedback of the people a system analyst can
make a good and helpful system and a developer can create the real-time glucose
monitoring system easily and reduce the time to build the system. By asking large number
of people about the system a system analyst gathered information very much. This fact-
finding technique is the best because every people gives the right information about the
system. Two types of question to be asked in this fact-finding technique that is fixed
format and free format. In the fixed format the answer given by the people must be fixed
and specific. And in free format the people have full freedom to answer the question. By
the answer to the question, a system analyst gathers the required information and by the
help of that information, a developer can easily make the real-time glucose monitoring
system.
3. Research - it is also a very useful and important fact-finding technique. A system analyst
must research the problems occur in the making the system or the application and
information can be gathered by any source such as, internet, reference books, trade
generals of computer these sources have good quality and quantity of the information
which is very useful for the system. By the research system analyst can know what
programming needs to be done to create a real-time glucose monitoring system by the heat
of the human body. And which items are needed to make this system and the cost of the
items is also known by the research. And the overall cost of the system is also found by
the research done by the system analyst. On the internet a system analyst can find any
information about the real-time glucose monitoring system.

Conclusion –
The TCP/IP protocol used the three-ways handshake because of TCP/IP is bidirectional and to
speed up the development of software application the rapid application development is used. The
advantage of an agile method is that the change can be possible at the time of creation any time.
The disadvantage is that the project falls off the track. Scope creep occurs when the information
of the project is not properly given by the customer. Research, interview and documentation
examine are the three fact-finding technique to collect the requirement of the system.

Reference –
Lopez, J. A., Sun, Y., Blair, P. B., & Mukhtar, M. S. (2015). TCP three-way handshake: linking
developmental processes with plant immunity. Trends in plant science, 20(4), 238-245.
Kothmayr, T., Schmitt, C., Hu, W., Brünig, M., & Carle, G. (2013). DTLS based security and two-way
authentication for the Internet of Things. Ad Hoc Networks, 11(8), 2710-2723.
Beynon-Davies, P., Carne, C., Mackay, H., & Tudhope, D. (1999). Rapid application development (RAD):
an empirical review. European Journal of Information Systems, 8(3), 211-223.
Coleman, G., & Verbruggen, R. (1998). A quality software process for rapid application
development. Software Quality Journal, 7(2), 107-122.
Conforto, E. C., & Amaral, D. C. (2010). Evaluating an agile method for planning and controlling
innovative projects. Project Management Journal, 41(2), 73-80.
Kuprenas, J. A., & Nasr, E. B. (2003). Controlling design-phase scope creep. AACE International
Transactions, CS11.
Davidson, J. E., Bloomberg, D., & Burnell, L. (2007). Scope Creep: When Nursing Practice Moves
Beyond Traditional BoundariesAn Evidence-Based Example Using Procedural Sedation. Critical care
nursing quarterly, 30(3), 219-232.
Maiden, N., Jones, S., Karlsen, K., Neill, R., Zachos, K., & Milne, A. (2010, September). Requirements
engineering as creative problem solving: A research agenda for idea finding. In 2010 18th IEEE
International Requirements Engineering Conference (pp. 57-66). IEEE.
Eva, M. (2001). Requirements acquisition for rapid applications development. Information &
Management, 39(2), 101-107.