Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
12 views6 pages

Ch3 Update

The document discusses the methodology for a project using Rapid Application Development. It describes the RAD approach, its 4 steps of defining requirements, prototyping, construction, and deployment. It also outlines techniques for collecting data like observations, interviews, surveys. The document discusses tools, a time schedule and budget for the project.

Uploaded by

sylviamunyambu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
12 views6 pages

Ch3 Update

The document discusses the methodology for a project using Rapid Application Development. It describes the RAD approach, its 4 steps of defining requirements, prototyping, construction, and deployment. It also outlines techniques for collecting data like observations, interviews, surveys. The document discusses tools, a time schedule and budget for the project.

Uploaded by

sylviamunyambu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

CHAPTER 3: METHODOLOGY

3.1 APPROACH TO BE USED

Rapid Application Development (RAD) –It is an adaptive software development model based on
prototyping and quick feedback with less emphasis on specific planning. It builds a functional
working model of the application in the fastest way possible. It is the best approach to develop
prototypes swiftly for testing software functionalities without worrying about any effects on the
end product. Developers can quickly make multiple iterations and updates to the software
without starting from scratch. This helps ensure that the final outcome is more quality-focused
and aligns with the end-user’s requirements. Unlike traditional development models with initial
planning and further execution RAD implies more flexibility (Andrey Glaschenko, 2023). It is a
continuous evolution of development philosophies according to the requirement at that particular
time.

-It has 4 basic steps;

1. Define the requirements

At the very beginning, rapid application development sets itself apart from traditional software
development models (Kissflow, 2023). It doesn’t require you to sit with end users and get a detailed
list of specifications; instead, it asks for a broad requirement. The broad nature of the requirements
helps you take the time to segment specific requirements at different points of the development
cycle.

2. Prototype

This is where the actual development takes place. Instead of following a rigid set of requirements,
developers create prototypes with different features and functions as fast as they can. These
prototypes are then shown to the clients who decide what they like and what they don’t.

More often than not, these prototypes are quickly made to work to showcase just the key features.
This is normal, and the final product is only created during the finalization stage where the client
and developer are in alignment with the final product.
3. Construction

The construction stage is a crucial stage of development. Engineers and developers work tirelessly
to flesh out a working system from a working model. Feedback and reviews are crucial at this stage
and most bugs, issues, and alterations are addressed during this stage. This stage can be particularly
long, especially in cases where clients change directions or feedback is intensive.

4. Deployment

The final stage of RAD involves deploying the built system into a live production environment. The
deployment phase involves intensive scale testing, technical documentation, issue tracking, final
customizations, and system simulation. Teams also spend time debugging the app and running final
updates and maintenance tasks before going live.
3.2 TECHNIQUES USED TO COLLECT DATA

3.1.1 Observations- The easiest and most direct data collection technique is observation.
The most common form of observation in the context of data collection involves simply
watching the behaviors or actions of a subject in a specific setting to understand them and record
what was observed. In today’s online world, an example of the act of observation can include
watching people interact with products, websites, and services in real-time.

3.1. 2 Interviews- In this method, the interviewer asks the respondents face-to-face or by
telephone. In face-to-face interviews, the interviewer asks a series of questions to the
interviewee in person and notes down responses. If it is not feasible to meet the person, the
interviewer can go for a telephone interview. This form of data collection is suitable for only
a few respondents. It is too time-consuming and tedious to repeat the same process if there
are many participants.

3.1.3 Surveys-they are one of the most well-known methods of data collection. They are done
with questionnaires and can be conducted physically and digitally to collect both quantitative
and qualitative data. These questionnaires are often inexpensive to create and answer, thus
making surveys a very accessible option for both researchers and their correspondents.

Commonly, surveys are used to collect responses about an event or item. The responses
collected can then be used as a basis for product improvement, decision-making matrices, or
further studies.

. (Roselin Manawis, 2023)

3.3. TOOLS FOR IMPLEMENTING AND TESTING THE SYSTEM

Java as my programming language as it is code comprehensive, dynamic and flexible.

Netbeans is a free and open source integrated development environment for application
development. It simplifies the development of web, enterprise, desktop, and mobile applications
that use the Java and HTML5 platforms.

MySQL to store data in tables that maps to objects


3.4. TIME SCHEDULE AND PROJECT COST

3.4.1. TIME SCHEDULE

Table of activities

Task Name Duration Calendar


Project Proposal 1 week 4th October - 11th October 2023
Software Requirement 2 weeks 12th October - 26th October2023
Specification
System design, 5 weeks 27th October – 23rd November
construction and coding 2023
begins
System design, 4 weeks 24th November- 24th December
construction and coding 2023
completed
System design, document 5 weeks 24th December- 31st January 2024
and Test plan
System Test plan 5 weeks 1st February- 8th March 2024
implemented
Complete Software 2 weeks 9th March- 23rd March 2024
Development
Develop user guide 1 weeks 23rd March- 30th March 2024
Project submission 1 day 30th March 2024

3.4.2. PROJECT ACTIVITY PRESENTATION


Activity October November December 2023 January 2024 February 2024 March 2024
2023 2023

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

1. Define the
requirements

2. Prototype

3. Construction

4 Deployment

3.4.3. PROJECT BUDGET

NO Item Cost (KES)


1. Laptop 30,000
2. Mouse 2500
3. Internet Connectivity 4,500
4. Stationery 250
5. Transport 1,500
6.
Total 38,750
3.5. REFERENCES

Andrey Glaschenko, (2023) What is Rapid Application Development?

https://www.jmix.io/rapid-application-development/

Kissflow, (2023). Is RAD SDLC Killing Traditional Application Development?

https://kissflow.com/application-development/rad/rad-sdlc-slowly-replacing-traditional-sdlc/

Roselin Manawis, (2023) Data collection techniques.

https://safetyculture.com/topics/data-collection/data-collection-techniques/

You might also like