Sei sulla pagina 1di 6

Figure 3.

1 Waterfall Model

Requirements Phase. Requirements phase involves gathering a considerable amount of


information. It is very important to understand the customer requirements and expectations so that the end
product meets his specifications. The developers obtain information from the interview conducted with
Mrs. Loreta Diongco, the manager of the store. With this information that was elicited, the developers
studied carefully the existing process of the company.

System Design. This phase focused on the data requirements, the software construction and the interface
of the system. The developers will follow the requirements specified by the company and made use of the
different tools such as database schema, entity-relationship diagram (ERD), and data flow diagram in the
developing the design of the system.

System Development. This phase involves converting design specification into executable programs.
Requirement Analysis System Design Coding Testing Implementation 18 After approving the design of
the proposed system, the developers will create the source code for the system wherein researchers will
use Visual Basic 6.0 as the front-end and MYSQL as the back-end of the development of the system.
System Testing. This phase requires organizations to complete various tests to ensure the accuracy of the
programmed code, the inclusion of expected functionality and interoperability of application. Erroneous
codes are rewritten and tested again until desired output is achieved. At this phase, the developers will
conduct system testing method such as user acceptance test or acceptability test to ensure all the features
of the system is functioning as expected as well as the reliability of the system.

System Implementation. The implementation phase involves installing the approved application into the
company. Primary tasks include announcing the implementation schedule, training end-users who will
use the system and installing the product.
DEVELOPMENT METHODOLOGY

Figure 2. Agile Scrum Methodology

Agile Scrum

The researchers used the Agile Scrum Methodology in software Development. The researchers
chose this methodology to adapt easily to changes, to be able to work side by side with end users
and to make necessary corrections and adjustments quickly when certain requirements are
altered. As Schwaber (2004) pointed out, the Scrum Agile methodology excels on urgent
projects that are critical to an organization. He added that the scrum shortens the feedback loop
between customer and developer, and between wish list and implementation. The process starts
with the researchers interviewing the client for the requirements needed for the design of the
System. This was followed by the release planning fits nicely into the planning frameworks that
are often offered for scrum and identify the user’s story that they want to put in the release or
sprint backlog. After that, the amount of work has been estimated and several sprints were
created.

Planning

At the first stage of planning the session, the researchers have undergone a brainstorming session
to identify the target locale and discussed the needs and arising problem within. The researchers
discovered that the Aj Trading Motorparts is still using manual based system in making a sale
and managing their inventory.

The researchers listed down the problems that the locale encountered and discussed them with
the locale. After gathering the necessary data and requirements, the researchers created a Project
Backlog to serve as a guide on creating the system. Then after that, the researchers initiated an
estimation and prioritization planning session together with manager and loan officer. After that
meeting, the researchers evaluated all the items that have been selected and then initiated the first
Scrum Planning meeting.

Product Backlog

Product backlog is a part of Scrum terminology representing the prioritized list of requirements
for the project being developed. The product backlog is the list of work the researchers must
address during the next sprint. The list is derived by selecting the backlog items from the top of
the backlog until the researchers feel it has enough work to fill the sprint. The backlog items are
broken down into tasks by the researchers. Tasks on the sprint backlog are never assigned;

Rather, tasks are signed up by the researcher as needed according to the set priority and the
researchers’ skills. This promotes self-organization of the researchers.

In listing the project backlog, the researchers had a meeting to talk over and analyzed the module
that should be prioritized and included in every sprint. After a sprint has been done, the
researchers got the feedback of their locale, and if there were some suggestions that were
possible and can be included to the system, then these were included to the project backlog and
subjected for the next sprint.
Phases in the James Martin approach to Rapid Application Development

Having users interact with evolving prototypes leads to much higher business functionality. Our
software is more usable and has a better chance to focus on business problems that are critical
to end users rather than technical problems of interest to developers. Additionally, a RAD
approach can focus in early on the key risk factors and adjust to them based on empirical
evidence collected in the early part of the process. Finally, it helps our projects to be completed
on time and within budget.

Additionally the structure of our foundation software is built to be customized and is always
integrated with our Business Intelligence software for reporting that can be customized by the
end user. We believe not only in quality software that facilitates our clients’ goals. We also
want to develop quickly and cost effectively.

Reference: https://www.enhancedretailsolutions.com/2015/12/09/customization-and-rapid-
development/

Potrebbero piacerti anche