Agile Prototyping

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 6

Agile prototyping is a good choice if you have an idea or plan for your project, but you’re

wondering whether it will be feasible. It can also provide you and your team with clarity if
you’re not entirely sure about the direction or requirements of your project. You may also find
that you’re ready to get started on a project, but investors or stakeholders are unable to see the
value. In this case, you can provide decision-makers with an interactive wireframe so you can
communicate key ideas. Prototyping is also a solid choice if you have a small budget. The more
time spent in development cycle, the more your project is likely to cost. Instead, working with
increasingly functional prototypes will mean that developers can spot issues and bugs early on.
That way, large problems can be solved well before development phase has begun- when issues
are much more time-consuming and expensive to fix.

This is can be similar with Agile- Agile is a development methodology. Basically, the agile
developers will develop and test in different stages (iterations) instead of waiting until the whole
product has been completed. Agile software development methodologies are popular due to its
detailed, accurate, consistent, and simple nature. The software is delivered in small parts, which
are considered to be miniature projects themselves. Just as the director of a play will work on
each scene individually before putting it all together, the agile model is about breaking a large
project down into multiple iterations. These iterative models are called sprints, and they can help
minimize risk. That’s because the agile development methodology involves a cycle of strict
planning, testing, integration, and risk evaluation. This reduces the chances that your project will
fail.

Prototyping begins before development is underway. Prototypes can range from a quick sketch
on a whiteboard to a fully interactive mockup.
1. Requirements Analysis

In this section, as the first step of SDLC, the proponents identify the requirements,
especially the system functional requirements, which will be emphasized and discussed
under the data gathering procedure.

1.2 Data Gathering Procedure

The researchers will collect certain tools or instruments that will be utilized as the
primary basis for creating interference. In developing the Web-based Barangay
Information and Management System for the Barangays in the City of Iligan,
techniques are applied in gathering the important data that serves as the basis in
developing this system, which includes interviews, library research, and internet
research.
1.3 Interview

The proponents conducted an on-site visit to the target community to


conduct meetings for interviews, and the sample barangay is Barangay Pala-o, to
gather the needed requirements. The Proponents interviewed the barangay
administrative staff, the barangay secretary, and the barangay chairman. For the
conducted interview, the proponents provided a formal letter to the respondents,
along with a letter of informed consent for the interview, which is attached in the
appendix part of this study. The proponents also conducted meetings for
interviews with some of the residents to gather more information for the proposed
study. Interview research is also a source of information, which often cannot be
found in the library or internet. It is a personal knowledge or experience. The
instrument serves as one of the proponents knowing the current conditions and
manual processes practiced by Barangays in the City of Iligan.

1.4 Use Case Diagram

With the interview conducted by the proponents of the proposed


system with their respondents, necessary data and functions, or
requirements, were successfully gathered. By those data, we can derive
our use case diagram to visually explain it, which can be seen below.
3.4.2.3 Observation

While the barangay utilizes a manual technique to retain separate records


of different clearances and other papers pertinent to the transaction inside their
barangay, the researchers noticed that records are stored in folders and document
cabinets. As a result of the expanding population, barangay staff are having
problems finding, looking, and discovering records. As a result, the researchers
determined that the barangays require a computerized system to assist them in
resolving the concerns and problems that they are experiencing.

3.4.2.4 Library Research

For this study, the researchers will visit various educational libraries. The
primary sources allow the researchers to get as close to the facts as possible.
Sources of relevant literature and research are gathered to contribute in the
development of the proposed system. Books, journals, and these are used to
acquire common functionality and data about the research.

3.4.2.5 Internet Research

Using online research, the researchers will obtain immediate information


on the most recent issues, literature, and project development systems for project
references related to and project background support for the intended study, such
as the barangay information system, the barangay management system.
Furthermore, the proponents used the World Wide Web to establish operational
definitions of phrases that the readers could readily comprehend.

3.4.2.6 Survey

The proponents conducted online questionnaire surveys using Google


Forms and posted them on the Facebook platform as a convenient survey for the
Barangay Pala-o residents to gather requirements information in line with the
residents' experiences of the existing system and to highlight what IT solutions for
the project development can be provided and developed by the proponents.

2. Quick Design- The second phase could consist of a preliminary design or a quick design.
During this stage, the system’s basic design is formed. However, it is not a complete
design. It provides the user with a quick overview of the system. The rapid design aids in
the development of the prototype.

3. Build a Prototype - During this stage, an actual prototype is intended to support the
knowledge gained from quick design. It is a small low-level working model of the
desired system.

4. Initial user evaluation- The proposed system is presented to the client for preliminary
testing at this stage. It is beneficial to investigate the performance model’s strengths and
weaknesses. Customer feedback and suggestions are gathered and forwarded to the
developer.

5. Refining prototype - If the user is dissatisfied with the current model, you may want to
improve the type that responds to user feedback and suggestions. When the user is
satisfied with the upgraded model, a final system based on the approved final type is
created.

6. Implement Product and Maintain - The final system was fully tested and distributed to
production after it was developed to support the original version. To reduce downtime
and prevent major failures, the programmer is run on a regular basis.
User - Case Evaluation

Barangay- The design is there but need more improvement for the rest of the system. Workout
more on the system design rather than the visual design. So that I would be easier to access the
website.

Secretary- Minimal design but I will rather go to the functions. The functions is there but needs
more improvement and then I will follow it up with suggesting a feature where we can see the
calendar events for upcoming events each in every month, is editable by me.

Residents- The design is good and it can successfully pass the information to the barangay and
we cannot see other resident’s information as well as any barangay member’s information. We
can see that our information will not leak easily. Secure our information at all cost.

Credits: https://www.intergy.com.au/agile-development-and-prototyping/

Credits: https://www.geeksforgeeks.org/software-prototyping-model-and-phases/?
fbclid=IwAR2IYbOwIJhWnfHS-tXtsYyFGh4D3Nt4ZRfVzB8KZGmqldLhHCHA2Qs1bYc

You might also like