RUBRICS FOR IS PROPOSALS

Criteria

Beginning

Developing

Accomplished

INTRODUCTION
Provides a glimpse of the system being
proposed; Description and benefits of
the proposed system are clearly stated

Does not give any

information about what
to expect in the proposal

Gives very little /

incomplete information

Gives too much

information - more like a
summary

Failed to identify the

problem to be addressed
by the proposed system

Gives an incomplete
information about the
problem to be solved

Lacks proper focus in

presenting the nature of
the problem and the
scope and limitations of
the problem to be
addressed

The objectives are too

general to serve as basis
for evaluation

Poor statement of
context supporting
rationale for the
proposed project

Provides clear context

supporting rationale for
the proposed project

STATEMENT OF THE PROBLEM

A concise desription of the issues that
need to be addressed by the researcher.
The following must at leased be
addressed: 1. What is the problem? 2.
Whose problem is being solved? 3.
What is the scope and limitations of the
problem?

SOFTWARE PROJECT OBJECTIVES

Objectives are concrete statements
describing what the project is trying to
achieve. The objective should be written
at a lower level, so that it can be
evaluated at the conclusion of a project
to see whether it was achieved or not.

STAKEHOLDER'S REQUIREMENTS
provides a complete description of the
functional behavior and non-functional
characteristics of a system to be
developed. It includes a set of use cases
that describe all the interactions the
users will have with the software.

The specification does not

reflect the actual
requirements of the
stakeholders

Clearly identified and meets

most of the requirement
specifications.

CONTEXT AND DATAFLOW

DIAGRAMS
graphical representation of the "flow" of
data through an information system,
modeling its process aspects

Process is not clearly

stated

Some directions are

given, but there are
missing information.

Process is easily
understood

ENTITY RELATIONSHIP DIAGRAM

a graphical representation showing how
entities in a database and relationships
between tables within that database are
connected

Diagram does not represent

a clear logical relationship
among entities and
attributes

All entities are represented Diagram shows

in the diagram, but their
consequently the process of
relationships not clearly
the business entity
defined

USER INTERFACE / SAMPLE SCREEN

SHOTS
shows the design and theme of screen Visual structure is not
shots in mobile communication devices, appealing
software applications, and websites with
the focus on the user's experience and
interaction.

Visual structure is appealing Visual look and content

but needs improvement
identified are attractive and
appealing

PROTOTYPING AND SPECIFICATION

CORRECTNESS
Shows a working model of a system built The program does not meet The program produces
The program works and
to test/ demonstrate a concept or
the requirements
correct results but does not meets most of the
process.
specification
display them correctly
specification

REUSABILITY
The ability to use all or the greater part
of the same code or system design in
another application or area.

The system is not organized Some parts of the system

for reusability
could be reused in other
programs

Most of the codes can be

used in other programs

PRELIMINARY IT INFRASTRUCTURE
The design of computing, storage and
Disorganized IT network
communications systems, which
infrastructure
includes the backbones, routers,
switches, wireless access points, access
methods and protocols used.

IT Network Infrastructure
needs to be organized

IT Network infrastructure is
organized and have visual
clear content look

Exemplary

10
Presents a concise lead-in
to the proposal

Presents a concise,
complete and researchworthy problem;
Accurately describes an
active challenge that does
not have adequate
solutions available
including the
argumentation for its
viability/in ISSP

Well-worded objectives:
Specific, Measurable,
Attainable/Achievable,
Realistic and Time-bound
(SMART).

SCORE

All functional and nonfunctional requirements were

clearly and accurately
identified

There are clear

representations of the
diagram for all processes
involved

There is accurate and clear

representation of the diagram

Visual look and content have

a consistent professional look
and feel

The program works and meets

all the specification

The system could be reused

as a whole or each routine
could be reused.

IT Network infrastructure is
very organized and represent
a clear and convincing
capability that the proposed
system can be supported