An Operational Framework showing the Development of Subdivision

Management System

The project's developers utilized Barry Boehm's 1986 description of the Spiral model for
project development, which they applied in the project's development.
research paper titled "A Spiral Model of Software Development and Improvement."
minimized planning and prioritized prototype iterations. Because the Spiral Model
enables developers to break a large project into smaller sections and focus on one
feature at a time, they can ensure that nothing is missing.

The spiral model, an SDLC strategy for risk management that combines the iterative
development process model with components of the Waterfall model, integrates the
iterative development process model with aspects of the Waterfall model. For large,
expensive, and complex projects, software engineers prefer the spiral model.
When viewed as a diagram, the spiral model looks like a coil with many loops. The
number of loops varies based on each project and is often designated by the project
manager. Each loop of the spiral is a phase in the software development process.

The first step is to identify the objectives and understand the requirements. the
phase where the developers began by gathering data. The project's developers
consider a project that can address a community problem and select the ideal
community partner. Interviewing the community partner's authorized representative
allows the developer to learn how the neighborhood is run and to ascertain what the
community expects, or requests be taken into consideration for the project. Along with
the community partner, the developers go over the project's objectives. Data is
gathered, processed, and then used to develop the project in a useful way. In case the
project is attempted but fails, an alternative option is also mentioned.

The second stage of developing a project is risk analysis. During this point, project-
related hazards are recognized and assessed. To identify potential risks, the project
developers conducted research and brainstorming meetings. Risk mitigation strategy is
developed and completed after risks are identified.

The project is developed and tested in the third phase. Actual development and testing
if the software takes place in this phase. The project includes knowledge, software, and
hardware requirements that are essential to the project's development. The project
developers must have an appropriate knowledge about the devices that will be used.
Also, software requirements are need in creating and developing the project. Then
hardware requirements in order to run the program. The project developer started with
an initial version of the project to know and test what the outcome should be. Then, the
project developer learned the adjustments to create the actual project. It transforms the
notion created in the two previous quadrants into a project that can be used.

The project development process's final stage is review and evaluation. The project
developers check, analyze, and determine whether the project was successful or not.
The community partner can start using the project right away. If the community partner
is not satisfied, the following iteration will be updated or revised in accordance with the
demands of the next community partner. The subsequent cycle repeats planning, risk
analysis, development, and evaluation (testing). Based on the final project's refinement
and the community partner's satisfaction, it is built.