100% found this document useful (1 vote)
644 views

Rubrics For Systems Analysis and Design Proposals

This document outlines rubrics for evaluating a proposal for a contract management system called CONTRATA. The proposal is being made by three proponents and will be evaluated based on criteria including a clear introduction and description of the proposed system, a concise statement of the problem being addressed and scope, concrete objectives for what the project aims to achieve, a complete description of stakeholder requirements and use cases, dataflow and entity relationship diagrams, and sample user interface designs.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
644 views

Rubrics For Systems Analysis and Design Proposals

This document outlines rubrics for evaluating a proposal for a contract management system called CONTRATA. The proposal is being made by three proponents and will be evaluated based on criteria including a clear introduction and description of the proposed system, a concise statement of the problem being addressed and scope, concrete objectives for what the project aims to achieve, a complete description of stakeholder requirements and use cases, dataflow and entity relationship diagrams, and sample user interface designs.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

RUBRICS FOR SYSTEMS ANALYSIS AND DESIGN PROPOSALS

Title : CONTRATA: A CONTRACT MANAGEMENT SYSTEM FOR


FRAMESPERSECOND USING WEB-BASED APP AND A MOBILE APP
Proponents
1. Almayda, Carl Joshua R.
2. Cabradilla, Richard Mark P.
3. Villaresco, Artchie N.
CRITERIA
INTRODUCTION
Provides a glimpse of the system being proposed;
Description and benefits of the proposed system are clearly
stated
STATEMENT OF THE PROBLEM
A concise description 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.
CONTEXT AND DATAFLOW DIAGRAMS
graphical representation of the "flow" of data through an
information system, modeling its process aspects
ENTITY RELATIONSHIP DIAGRAM
a graphical representation showing how entities in a
database and relationships between tables within that
database are connected
USER INTERFACE / SAMPLE SCREEN SHOTS
shows the design and theme of screen shots in mobile
communication devices, software applications, and websites
with the focus on the user's experience and interaction.

10

You might also like