Professional Documents
Culture Documents
The Problem
Introduction
“Don’t wait until everything is just right. It will never be perfect. There
will always be challenges and less perfect conditions. So what. Get started now.
With each step you take you will grow stronger and stronger , more and more
skilled, more and more self-confident, more and more successful.”
- Mark Victor Hansen
The Office of the Registrar integrates thee major functions in our School
Community: Promoting the school through her degree program offerings;
recruiting and processing student admissions to Maryknoll College of Panabo,
Inc.; Receiving, evaluating, consolidating, systemizing, controlling, preserving
student records and enrolling students and issuing transfer credentials.
In addition, she does public relations and monitors events that are
taking place outside Maryknoll College of Panabo. The latter function involves
thinking and planning about what the outside environment think and does. This
is to help the University administration manage the environment and to help the
Office “think globally” for the future and to “Act locally”, now.
Incorrect Data Edits - This is when the software does not apply existing data
edits correctly. For example, a data edit may be coded to prohibit the entry of
the day of the month greater than "31", but does not allow for the month. This
would allow the entry of February 30 and other invalid dates.
Ineffective Data Edits - This is when data edits are in place and working
correctly, yet still fail to prevent incorrect data from being entered into the
system. An example of this is an alphanumeric address field that allows spaces
to be entered before any numbers or letters in the address. Therefore, when
searches or sorts are performed on the address field, the search or sort may not
find the intended address.
Incorrect Coding/Implementation Of Business Rules - This refers to the one
of the most common sources of software problems - the mistakes that occur
between what is intended to be developed or implemented and what is actually
delivered. These defects can be traced back to incorrect, missing, or vague
system requirements specifications, or to the misinterpretation of requirements
specifications. If you are asking, "What specifications? What requirements?",
the incorrect coding or implementation of business rules is probably a common
problem for you.
Confusing or Misleading Data - This means that the data shown to users may
be correct, but the users might not fully understand how to interpret the data.
This is not a trivial problem. Lives have been lost because of someone's failure
to take the correct actions based on the data delivered to them from a computer
system.
Unreliable results or performance - This means that the software does not
deliver consistently correct results or cannot be depended to work correctly
each time it is used.
Inadequate support of business needs or objectives - This refers to software
that is inflexible to meeting business needs. For example, a system may be
difficult to modify to meet and organization's needs or may lack features to
allow the users to customize business rules.
Incorrect or inadequate interfaces with other systems - This means that the
software does not correctly accept input (data, control, parameters, etc.) from
other systems or sends incorrect output (data, control, parameters, print, etc.) to
other systems. An example of this is when a system has an electronic data
interfaces (EDI) with external systems, but does not correctly receive or format
the information.
Data searches that yield incorrect results - This means that a search retrieves
incorrect data as the result of a search. In the worst case situation, the data
retrieved appears to be correct in format, but only by tracing back to source
documents and other original data can it be determined that the data is incorrect
for the search criteria. An example of this would be searching for the time
worked by a particular employee in a payroll system. The employee's name at
the top of the information may be displayed correctly, but the detailed time data
may belong to another employee. The only ways to verify the information
would be to compare the time worked back to time sheets or to tables that
indicate the employee ID.
Incorrect file and data handling - This refers to the software incorrectly
retrieving data from files or tables. This could include retrieving the wrong data
from the right source or the right type of data from the wrong data source. An
example of this would be retrieving data from an old version of a file or table,
thinking the data is being retrieved from the most current version. Another
example is the inability of the software to process empty or full files correctly.
A secondary problem could relate to the software's inability to pass data
correctly through the system. An example of this would be the incorrect
processing of transactions, where data is inadvertently dropped during
processing.
Tedious - It's implied that the manual way is exceptionally tedious, even the
most effortless errand, for example, scanning for a particular information can
take up a lot of time, seeing as the individual still needs to look it out of
alternate various information that is likewise recorded. In the manual way
regardless you have to look the class for the information though in the
programmed way, you just need watchwords or particular letters to limit the
hunt or to get the information you require.
Inerasable Errors - In the manual way once somebody commits an error it is
very difficult to delete it, depending if the client was utilizing a ballpoint pen as
opposed to pencils. Utilizing a white ink eradication may just prompt making
to a greater degree a wreck not at all like an electronic framework where you
just need to delete to erase the undesirable markings.
The researchers of this software project aims to help their recipient by doing
the following: