You are on page 1of 7

Chapter 3

OPERATIONAL FRAMEWORK

The waterfall model was chosen by the project developers to build the wayfinding
system application software since this provides an easy overview of the program based
on the required specifications and a visual representation of the overall flow of the
software application development. For improved services and crime management,
project developers updated the current system .  These are the stages of the Crime
Management and Reporting System development.

Brainstorming and Planning


In this phase, the project developers had the opportunity to contribute ideas
spontaneously, as well as the process of developing each innovative concept and
solution through a freewheeling debate.

Requirements Analysis
This phase includes gathering needs from former and present users of the system while
doing research, reading journals and articles, and consulting related literature and
studies obtained online by the project developers.

System Analysis and Design


During this phase, the required specifications are examined, and system design is
carried out. For the best outcomes of their proposed project, the researchers examined
and assessed several prior and current systems. The suggested system's whole scope
and limits are examined and improved upon. Different design tools are being used for
this project, including Visual Studio Code 2010 and XAMPP (MySQL). The data
structure was created based on the system specifications.

Implementation and Testing


In this step, the proponents will start coding using VB.NET for the graphical user
interface. XAMPP is used for MySQL database and for the application logic which
enables communication between the front-end and the backend of the system. And the
coding and synchronizing of the software and hardware to make sure that these two
components are working together. All the units developed in the implementation phase,
the entire system and the hardware used by the proponents is being tested for any
errors and failures.

Deployment
The system is ready to deploy to the recipient after the functional and non-functional
testing is completed. This step entails educating the authorities who will be granted the
authority to operate the system, as well as filling the database with current records and
converting the data.
Maintenance
Assures that the system will continue to do the task that was given. This involves
looking for bugs and errors, as well as verifying that the system as a whole is
functioning effectively.

Systems Development Life Cycle is a systematic approach which explicitly breaks down
the work into phases that are required to implement either new or modified Information
System.

FIGURE 1. The Modified Waterfall Methodology


Requirements Specification

The Programming Language that project developer use is vb.net originally called Visual
Basic .Net it is a multi-paradigm, object-oriented programming language and The
Project Developer use the software called XAMPP for the localhost (SQL Server) and
the system has a Short Messaging Services Notification (SMS Notification) feature
using the GSM Module. The GSM module is responsible for sending and receiving text
from the user to police department or online system. The system can provide reports
such as the list of crimes/complaints for a specific date range.

Conceptual Framework

Inputs

Individual-level factors are what group members bring to the group, such as motivation,
personality, abilities, experiences, and demographic attributes. Software Requirements
The following are the software used for the development and for the implementation of
the system. Operating System: Windows 7 to Windows 10, Software Development:
Visual Studio 2010, Browser: Google Chrome/Mozilla Firefox and other browser,
Documentation: Microsoft Word 2010 up to latest version and lastly the internet.
Examples of group-level factors are work structure, team norms, and group size.
Environmental factors capture the broader context in which groups operate, such as
reward structure, stress level, task characteristics, and organizational culture.

Processes

Processes are the mediating mechanisms that convert inputs to outputs. A key
aspect of the definition is that processes represent interactions that take place among
team members. Many different taxonomies of teamwork behaviors have been proposed,
but common examples include coordination, communication, conflict management, and
motivation.

In comparison with inputs and outputs, group processes are often more difficult to
measure, because a thorough understanding of what groups are doing and how they
complete their work may require observing members while they actually perform a task.
This may lead to a more accurate reflection of the true group processes, as opposed to
relying on members to self-report their processes retrospectively. In addition, group
processes evolve over time, which means that they cannot be adequately represented
through a single observation. These difficult methodological issues have caused many
studies to ignore processes and focus only on inputs and outputs. Empirical group
research has therefore been criticized as treating processes as a “black box” (loosely
specified and unmeasured), despite how prominently featured they are in the IPO
model. Recently, however, a number of researchers have given renewed emphasis to
the importance of capturing team member interactions, emphasizing the need to
measure processes longitudinally and with more sophisticated measures.

Outputs
Indicators of team effectiveness have generally been clustered into two general
categories: group performance and member reactions. Group performance refers to the
degree to which the group achieves the standard set by the users of its output.
Examples include quality, quantity, timeliness, efficiency, and costs. In contrast, member
reactions involve perceptions of satisfaction with group functioning, team viability, and
personal development. For example, although the group may have been able to
produce a high-quality product, mutual antagonism may be so high that members would
prefer not to work with one another on future projects. In addition, some groups
contribute to member wellbeing and growth, whereas others block individual
development and hinder personal needs from being met. Hardware Requirements: The
following are the specifications as shown below for the visual studio for better coding:
Processor: Intel Dual Core 2.0 GHz or higher, Memory: 4GB DDR3 (Recommended),
Disk Storage: 500 GB (Recommended), Video Card: 512 MB GeForce VC (Optional),
USB Slot: USB Port 2.0 or up (Recommended for GSM Module), Router or Modem
(Recommended for Internet connection).
FEEDBACK MECHANISM

IDRAWING NG KAGAYA NG GANYAN AT LAGYAN KUNG ANO ANG INYONG


INPUT, PROCESS AND OUTPUT.

Figure 2

A Conceptual Framework showing the development of (title)………………………….


REMINDERS:
1. WAIT SA DEADLINE KUNG KELAN IPAPASA. NO CHAPTER 1 BAWAL
GUMAWA NG CHAPTER 2.
2. SUNDIN ANG PROPER FORMAT. PWEDE HAND WRITTEN AT PEDE ITYPE
SA MS WORD SIGURADUHIN NAKA JUSTIFY, ARIAL, 12, DOUBLE SPACING.
MARGIN 1 SA UP, DOWN AND RIGHT AND 2 SA LEFT.
3. IPASA THRU PM O GMAIL SA RESPECTIVE AND AUTHORIZED PERSON.
4. SHORT BONDPAPER KAHIT HANDWRITTEN O PATYPE.
5. PALAGING GAGAMITIN PAG TINUTUKOY AY IKAW PROJECT DEVELOPER.
HUWAG MAG LALAGAY NG DEVELOPER, RESEARCHER, PROPONENT.
6. HUWAG NA HUWAG GAGAMITIN NG THIRD PERSON KAGAYA NG WE, THIS
AND OUR ETC. PAG WE GAMITIN AY PROJECT DEVELOPER, AT PAG OUR
GAMITIN AY THE SYSTEM.
7. KADA ISANG PARAGRAPH/SENTENCE AY NAKA PAPASOK O INDENT.
8. ENGLISH PO ANG EXPLANATION
9. PAG MAY MAKAPAREHAS KAYO SA IBANG SECTION AUTOMATIC 5.00.
10. KAHIT HINDI MAGANDA SULAT OKEY LANG BASTA HANGGANG DULO
SAME PENMANSHIP.
11. BAWAL KUMUHA SA NET WORD BY WORD
12. INGAT KAYONG LAHAT SANA MATAPOS NA TO. PRAY LANG PO.

You might also like