Student Information System EIS Document Quality Assurance Results

RISK MITIGATION, MONITORING

Requirements

Compliance

Correctness

Remarks

AND MANAGEMENT (RMMM)

1.0 INTRODUCTION

Passed or
Failed

Introduce the RMMM as a

PASSED

whole for the EIS/Module

1.1

1.2

Scope and intent of

Indicates the scope and

RMMM activities

purpose of RMMM activities.

Risk Management

States the organizational roles

Organization Role

in Risk Management.

2.0 RISK DESCRIPTION

Check the

FAILED

alignment

Use

FAILED

numbered list

Describes the risks in creating

the system.

2.1

Risk Table

Cites down the description and

probability of risks in tabular

It must be in

FAILED

tabular form

form.
2.1.1

Description of

Describes the specified risks.

Risk
2.1.2

Probability and

Check the

FAILED

Alignment
States the impact/effect of a

Payroll System with Attendance and Leave Monitoring

Have a good

FAILED

Page 1

Student Information System EIS Document Quality Assurance Results

Impact of Risk

risk as well as the probability of

look of table

it to happen.
3.0 RISK MITIGATION,

Includes the monitoring of risks

MONITORING AND

and the procedures in

MANAGEMENT

managing it.

3.1

Risk Mitigation for Risk

Describes the steps in

addressing the risk that was

Check

FAILED

Alignment

Check

FAILED

Alignment

stated.
3.1.1

Product Size

Indicates the scope of risk

definition.

Check

FAILED

Alignment
and the
order

3.1.2

Business Impact

States the impact of risk in

Check

businesses/systems that are

Alignment

currently being developed.

and the

FAILED

order
3.1.3

Customer(User)

Lists down the risk of the

Risk

system on its customer.

Payroll System with Attendance and Leave Monitoring

Check

FAILED

Alignment

Page 2

Student Information System EIS Document Quality Assurance Results

and the
order
3.1.4

Process Risks

States the effect of risk in the

process of the system.

Check

FAILED

Alignment
and the
order

3.1.5

Technology

Cites down the risk of the

Risks

system in technology.

Check

FAILED

Alignment
and the
order

3.1.6

Development

Lists down the risks that are

Check

Risks

present during the development

Alignment

stage.

and the

FAILED

order
3.1.7

Employee Risks

Describes the risk of the

Check

(Teammates)

system that is being developed

Alignment

to its developers.

and the

FAILED

order

Payroll System with Attendance and Leave Monitoring

Page 3

Student Information System EIS Document Quality Assurance Results

3.2

Risk Monitoring for Risk

Describes the process of

monitoring procedures for

No content

FAILED

Check

FAILED

determined risks.
3.2.1

Product Size

States the coverage/area of

monitoring risks.

Alignment
and the
order

3.2.2

Business Impact

Cites down the monitoring

procedures inside the business.

Check

FAILED

Alignment
and the
order

3.2.3

Customer(User)

Includes the risk monitoring for

Check

Risk

clients/customers of the

Alignment

system.

and the

FAILED

order
3.2.4

Process Risks

Checks the monitoring activity

for the systems processes.

Check

FAILED

Alignment
and the

Payroll System with Attendance and Leave Monitoring

Page 4

Student Information System EIS Document Quality Assurance Results

order

3.2.5

Technology

Monitors the risk that affects

Check

Risks

the technologies used in

Alignment

developing the system.

and the

FAILED

order
3.2.6

Development

Addresses the steps in

Check

Risks

monitoring the development

Alignment

risks

and the

FAILED

order
3.2.7

Employee Risks

Monitors the risk that affects

Check

(Teammates)

the employees or developers of

Alignment

the system.

and the

FAILED

order
3.3

Risk Management for

This part describes how the

Risk m

proponent will manage the

No content

FAILED

Check

FAILED

identified risks.
3.3.1

Product Size

Describes the steps on how will

the group handle the largeness

Payroll System with Attendance and Leave Monitoring

Alignment
Page 5

Student Information System EIS Document Quality Assurance Results

of the project.

and the
order

3.3.2

3.3.3

Business Impact Sites down the procedures on

Check

how will the proponents

Alignment

address the requests or needs

and the

of the client.

order

Customer(User)

Shows the management of

Risk

user related risks.

Check

FAILED

FAILED

Alignment
and the
order

3.3.4

Process Risks

Describes the management of

process risks.

Check

FAILED

Alignment
and the
order

3.3.5

Technology

Manages the risks in

Check

Risks

technologies while developing

Alignment

the system.

and the

FAILED

order

Payroll System with Attendance and Leave Monitoring

Page 6

Student Information System EIS Document Quality Assurance Results

3.3.6

Development

States the steps on how will the

Check

Risks

developers manage the

Alignment

development risks.

and the

FAILED

order
3.3.7

Employee Risks

Describes the management of

(Teammates)

employee risks.

Check

FAILED

Alignment
and the
order

4.0 SPECIAL CONDITIONS

States the special conditions

No content

FAILED

that the system encounters.

Payroll System with Attendance and Leave Monitoring

Page 7

Student Information System EIS Document Quality Assurance Results

SOFTWARE CONFIGURATION

Requirements

Compliance

Correctness

Remarks

MANAGEMENT (SCM)
1.0 INTRODUCTION

Passed or
Failed

Introduces the Software

Configuration Management as

Check

FAILED

Alignment

a whole.
1.1

Scope and Intent of

Describes the scope and

SCM activities

purpose of doing the SCM

Dont use

FAILED

bullets

activities.
Use
numbered
list
1.2

SCM Organizational

Cites down the responsible

There are no

Role

persons for the task given in

responsible

SCM Activities.

persons

FAILED

cited
2.0 SCM TASKS

Lists down the activities to be

done in SCM.
2.1

Identification

Identifies the task to be done

Payroll System with Attendance and Leave Monitoring

Check

FAILED

Alignment

There are no
tasks
identified

FAILED

Page 8

Student Information System EIS Document Quality Assurance Results

Dont use
bullets
Use
numbered
list

to ensure the proper

configurations of the system.

2.2

Configuration Control:

Describes on how the

proponents will control the

Missing

FAILED

content

changes in the system.

2.2.1

Description

Describes the procedures and

tools to be used in controlling

Dont use

FAILED

bullets

the changes.
2.3

Version Control

Cites down the way of the

proponents in numbering the

Missing

FAILED

content

versions of their documents

and system.
2.3.1

2.3.2

Description

Describes the versioning

No

technique in revised

versioning

documents and systems.

technique

Increasing

Describes the way of

Version

increasing the version number

Payroll System with Attendance and Leave Monitoring

FAILED

Page 9

Student Information System EIS Document Quality Assurance Results

2.3.3

Number

of systems.

Work Products

States the revision history of

and

the system and documentation

Does not

FAILED

state the

Documentation

revision
history

2.4

Configuration Status

Describes the recording and

Accounting

reporting of information

Check

FAILED

Alignment

required to effectively manage

the configuration of a system
or product.
2.4.1

Description

Describes on how the

Configuration Status

Dont use

FAILED

bullets

Accounting will be done.

Use
numbered
list
2.4.2

Work Products

States the revision history of

and

the system and documentation

Dont use

FAILED

bullets

Documentation
Payroll System with Attendance and Leave Monitoring

Page 10

Student Information System EIS Document Quality Assurance Results

Use
numbered
list

Payroll System with Attendance and Leave Monitoring

Page 11

Student Information System EIS Document Quality Assurance Results

SOFTWARE QUALITY

Requirements

Compliance

Correctness

Remarks

ASSURANCE

Passed or
Failed

1.0 INTRODUCTION:
1.1

Dont use

Scope and intent of

Must include quality

SQA activities

assurance intent of the

bullets. Use

Student Information System

numbered

EIS

list

FAILED

Quality Assurance
information is precise
1.2

SQA Organization Role

Description for every Role is

available

There are no

FAILED

descriptions
of roles

Must specify methodology

or diagrams providing
information about
organization roles of the
project.

Payroll System with Attendance and Leave Monitoring

Page 12

Student Information System EIS Document Quality Assurance Results

2.0 SQA Tasks

Specify task of software

Dont use

quality assurance in Payroll

bullets. Use

System with Attendance

numbered

and Leave Monitoring

list

FAILED

System

2.1

Task Overview

Must provide information

about task overview

Check the

FAILED

alignment

considering SQA Tasks

Task must be precise and
appropriate in Payroll
System with Attendance
and Leave Monitoring
System.
2.2

Standards, Practices

Detailed information about

and Conventions SPC

the standards, considering

PASSED

Payroll System with

Attendance and Leave
Monitoring System. system

Payroll System with Attendance and Leave Monitoring

Page 13

Student Information System EIS Document Quality Assurance Results

task or transactions.

2.3

SQA Resources

Software Quality Assurance

must be listed.

Missing

FAILED

content

3.0 REVIEWS AND AUDITS

3.1

Generic Review

Conduction Review is

Guidelines

existing

Dont use

FAILED

bullets. Use
numbered

Roles and Responsibility is

list

precise
Check
alignment
Must have information
about Review Work Product
3.2

Formal Technical

Description of Review

Reviews

Walkthroughs

Dont use

FAILED

bullets. Use
numbered

Description of Review

list

Inspection
Check
Payroll System with Attendance and Leave Monitoring

Page 14

Student Information System EIS Document Quality Assurance Results

alignment.
System Specification
Review

Check the
numbering

Software Project Plan

Review
RMMM Review
Requirements Reviews
(Models, Specification)
Data Design Review
Architectural Design Review
Interface (GUI)
Component Design Review
Code Review
Test Specification Review
Change Control Reviews
and Audits
Payroll System with Attendance and Leave Monitoring

Page 15

Student Information System EIS Document Quality Assurance Results

3.3

SQA Audits

Specify team approach to

Quality Assurance

Dont use

FAILED

bullets. Use
numbered
list
Check
alignment

4.0 PROBLEM REPORTING AND

CORRECTIVE
ACTION/FOLLOW-UP
4.1

Reporting Mechanism

Mechanism of reporting in
Payroll System with

Check

FAILED

alignment

Attendance and Leave

Monitoring System is
specified

It shows information about

the procedure in producing
reports about quality
Payroll System with Attendance and Leave Monitoring

Page 16

Student Information System EIS Document Quality Assurance Results

assurance

4.2

Responsibilities

Specify roles and provide

Use

information about their

numbered

roles.

list

FAILED

Check
alignment
4.3

Data Collection and

Quality assurance for data

Valuation

collection and valuation is

Check

FAILED

alignment

clearly identified.
4.4

Statistical SQA

Quality assurance for

Dont use

statistical SQA is identified

bullets. Use

and appropriate to Payroll

numbered

System and Attendance and

list

FAILED

Leave Monitoring
Check
alignment
5.0 SOFTWARE PROCESS

PASSED

IMPROVEMENT ACTIVITIES
Payroll System with Attendance and Leave Monitoring

Page 17

Student Information System EIS Document Quality Assurance Results

5.1

Goal and Object of SPI

Goals and Objectives of SPI

Dont use

is clearly identified and

bullets. Use

appropriate to Payroll

numbered

System with Attendance

list

FAILED

and Leave Monitoring

Check

System

alignment
5.2

SPI Tasks and

SPI task of Payroll System

Responsibilities

and Attendance and Leave

FAILED
Check

Monitoring System is

alignment

specified and clearly

identified
6.0 SOFTWARE CONFIGURATION

Software configuration

MANAGEMENT AND OVERVIEW

management and overview

Check

FAILED

alignment

must be specified and

appropriate to Payroll
System and Attendance and
Leave Monitoring System

Payroll System with Attendance and Leave Monitoring

Page 18

Student Information System EIS Document Quality Assurance Results

7.0 SQA TOOLS, TECHNIQUES,

Tools and techniques must

METHODS

be clearly identified

Payroll System with Attendance and Leave Monitoring

Check

FAILED

alignment

Page 19

Student Information System EIS Document Quality Assurance Results

SYSTEM SPECIFICATIONS

Requirements

Compliance

Correctness

Remarks

Passed or
Failed

1.0 INTRODUCTION
1.1

Goals and Objectives

Detailed objectives of the

Dont use

system. Ex in GL. Must

bullets. Use

record all the transactions of

numbered

the Hospital regarding

list

FAILED

money.
Check
alignment
1.2

System Statement of

Detailed objectives of the

Scope

system. Ex in GL. Must

Check

FAILED

alignment

record all the transactions of

the Hospital regarding
money.
1.2.1 General
Requirements

General Requirement of GL
Module is specified

Dont use

FAILED

bullets. Use
numbered
list

Payroll System with Attendance and Leave Monitoring

Page 20

Student Information System EIS Document Quality Assurance Results

Requirement of GL module

Check

is specified

alignment

5 Analytical Reports
Free Format Query
Custom GUIs
Android Application
Import and Export Utility
1.3

System Context

Must include information

about the importance of

Provide

FAILED

more details

Payroll and Monitoring

system process inside SIS
Tertiary EIS
1.4

Major Constraints

Computing Environment

PASSED

Data Requirement

Payroll System with Attendance and Leave Monitoring

Page 21

Student Information System EIS Document Quality Assurance Results

Clearly Specified
2.0 FUNCTIONAL DATA
DESCRIPTION
2.1

System Architecture
2.1.1 Architecture

Appropriate Use of Figures

Model

Use single

FAILED

colour only
Appropriate Menus of
Payroll and Monitoring
System

Every attributes must have

description.
2.1.2 Current

Subsystem overview is

Provide

Subsystem

appropriate to Payroll and

more

Overview

Monitoring System

subsystems

FAILED

overview
Payroll System with Attendance and Leave Monitoring

Page 22

Student Information System EIS Document Quality Assurance Results

Information is clearly
defined
2.2

Data Description
2.2.1 Major Data
Objects

All attributes is appropriate

to GL System

Be

FAILED

consistent in
numbered

Every Attribute must have a

list one

description.

2.2.2 Relationships

Objects of Payroll and

format only

Provide the

Monitoring System are

relationships

existing

of each

FAILED

entity
Readable Diagrams and the
connection is correct
2.3

Human Interface

Description for human

Description

interface in Payroll and

Check

FAILED

alignment

Monitoring System is
clearly defined.

Payroll System with Attendance and Leave Monitoring

Page 23

Student Information System EIS Document Quality Assurance Results

3.0 SUBSYSTEM DESCRIPTION

3.1

Subsystem Flow

Objects are appropriate to

Diagrams

Payroll and Monitoring

Use single

FAILED

colour only.

System
Use
appropriate
objects
4.0 ENHANCED INTERFACE
PROTOTYPING
4.1

Prototyping

Screen for Login

PASSED

Requirements
Screens for the Payroll and
Monitoring System

Payroll System with Attendance and Leave Monitoring

Page 24

Student Information System EIS Document Quality Assurance Results

SOFTWARE REQUIREMENTS
SPECIFICATION
1.0 INTRODUCTION

1.1 Goals and Objectives

1.2 System Statement of

Scope

Requirements

Compliance

Correctness

Remarks

Passed or
Failed

Must introduce the

whole requirements of
the system.

Detailed objectives of
the system. Ex in GL.
Must record all the
transactions of the
Hospital regarding
money.

This includes the

importance of the
requirements in the
system and why are
they needed.

Check
alignment

FAILED

Dont use

FAILED

PASSED

Dont use

FAILED

bullets
Use
Numbered list

Must have a table that

includes the
requirements, priority,
references and
description
1.2.1 General
Requirements

Must be detailed
general requirements.

Payroll System with Attendance and Leave Monitoring

Page 25

Student Information System EIS Document Quality Assurance Results

Must include the 5
basic requirements with
the system functions.

bullets
Use
Numbered list

1.2.2 Extended
Requirements

These are the extended

requirements. For ex.
The interim systems

Dont use

FAILED

bullets
Use
Numbered list

1.3

1.4

System Context

Major Constraints

This contains the

importance of the
requirements of the
system.

These are the

constraint in the
requirements. It is not
about the time, funding.

Must contain all the

user roles and what
they are doing in the
system

Check

FAILED

Alignment

Check

FAILED

Alignment

2.0USAGE SCENARIO
2.1

User Profiles

Payroll System with Attendance and Leave Monitoring

Dont use

FAILED

bullets
Use
Page 26

Student Information System EIS Document Quality Assurance Results

Numbered list
2.2

Use-Cases
2.2.1

Use Case
Diagram

Must have a use-case

diagram including all
the users.

Dont use

FAILED

bullets
Use
Numbered list

2.2.2

Use Case
Description

Must have all the use

case including the
preconditions, trigger,
exceptions and goals.

Missing
content

FAILED

2.3

Special Usage
Considerations

Must contain the

considerations for
special users of the
system.

Missing
content

FAILED

2.4

Activity Diagram

Must have diagrams of

the main activities in
the system.

Missing
content

FAILED

3.0 DATA MODEL AND

DESCRIPTION
3.1

Data Description

Payroll System with Attendance and Leave Monitoring

Page 27

Student Information System EIS Document Quality Assurance Results

3.1.1 Data Objects

and Dictionary

Must contain the

descriptions of the
attributes in the table.

3.1.2 Relationships

Must have a diagram

and description for
relationships.

Indicate the
relationship
of every
entity

FAILED

It contains the
subsystem of the
module.

Use single

FAILED

Check

FAILED

Alignment

4.0 FUNCTIONAL MODEL AND

DESCRIPTION
4.1

Subsystem Flow
Diagrams

colour only.
Use
appropriate
objects

4.2

Human Interface

5.0 RESTRICTIONS, LIMITATIONS

AND CONSTRAINTS

It is the human
interface requirements
of the system.

It includes things that

the system cannot do.

Payroll System with Attendance and Leave Monitoring

Include only

FAILED

the main
points

Include only

FAILED

the main

Page 28

Student Information System EIS Document Quality Assurance Results

points
6.0 VALIDATION CRITERIA

The Functional and

Non Functional
Requirements of the
system.

Must include

FAILED

the
Functional
and NonFunctional
requirements

Payroll System with Attendance and Leave Monitoring

Page 29

Student Information System EIS Document Quality Assurance Results

SOFTWARE DESIGN SPECIFICATION

Requirements

Compliance

Correctness

Remarks

Passed or
Failed

1.0 INTRODUCTION
1.1

Goals and Objectives

Focuses on the

PASSED

goals of the
system in the
design
1.2

System Statement of Scope

The scope of the

system in the

Missing

FAILED

content

design.
1.2.1 General Requirements

The general
requirements in

Dont use

FAILED

bullets

the design that

comprises the 5
basic
requirements

Use
Numbered
list

together with the

module features.

Payroll System with Attendance and Leave Monitoring

Page 30

Student Information System EIS Document Quality Assurance Results

1.3

System Context

Significance of

the design in the

Focus on

FAILED

design

development of
the system
1.4

Major Constraints

The design

constraints that

Focus on

FAILED

design

the system can

have.
2.0DATA DESIGN
2.1

Database Description

Contains the

tables together

Missing

FAILED

content

with the attributes

and table
description.
3.0 ARCHITECTURAL AND

Must have UML

COMPONENT-LEVEL DESIGN

diagram.

Use single

FAILED

colour only.
Use
appropriate

Payroll System with Attendance and Leave Monitoring

Page 31

Student Information System EIS Document Quality Assurance Results

objects
3.1

Program Structure

Comprises of the

System

Use single

FAILED

colour only.

Composition
Use
appropriate
objects
3.2

Description for Components

The components
of the system are

Check the

FAILED

format

the users that

have the
narrative,
interface and
algorithmic
description and
design class
hierarchy and
restrictions and
limitations of
each.

Payroll System with Attendance and Leave Monitoring

Page 32

Student Information System EIS Document Quality Assurance Results

4.0 USER INTERFACE DESIGN

4.1

Description of the User

Interface

Describes the

importance of the

Missing

FAILED

content

UI design.
4.1.1

Screen Images

Sample Images.

4.1.2

Objects and Actions

All of the objects

that will be used

PASSED

Missing

FAILED

content

by the system
(ex. Login button)
and what will be
the main actions
afterwards.
4.2

Interface Design Rules

The Eight Golden

Check format

PASSED

Components

FAILED

Rules of Design
Interface
4.3

Components Available

All of the
components

Payroll System with Attendance and Leave Monitoring

not properly

Page 33

Student Information System EIS Document Quality Assurance Results

available in the

described

template / design
are described
here.
4.3.1

Intrinsic Controls

The basic

No images

controls must be

and

detailed with

description

FAILED

images.
4.3.2

ActiveX Controls

The advanced

No images

components must

and

be detailed with

description

FAILED

image.

5.0 RESTRICTIONS, LIMITATIONS AND

It includes things

Focus on

COSNTRAINTS

that the system

software

cannot do.

design

FAILED

6.0 TESTING ISSUES

6.1

Classes of Test

Must have the

classes of test for

Payroll System with Attendance and Leave Monitoring

Include the

FAILED

Classes of

Page 34

Student Information System EIS Document Quality Assurance Results

system interface,

test

login, system
setup,
transactions and
other important
parts of the
system.
6.2

Performance Bounds

Contains how

long the system

Check

FAILED

Alignment

will respond. It
includes the best
and worst case
scenario.
6.3

Identification of Critical
Components

Describes the
detailed critical

Check

FAILED

Alignment

components of
the system. For
example in
General Ledger,
the identification

Payroll System with Attendance and Leave Monitoring

Page 35

Student Information System EIS Document Quality Assurance Results

of subsidiary
ledgers.

Payroll System with Attendance and Leave Monitoring

Page 36

Student Information System EIS Document Quality Assurance Results

TEST SPECIFICATION

Requirements

Compliance

Correctness

Remarks

Passed or
Failed

1.0 INTRODUCTION
X
1.1

Goals and

States the goals and objectives

Objectives

in doing the test.

Statement of Scope

Indicate the range of test in

The goals and

Failed

objectives are
not specified.

1.2

Dont use

FAILED

bullets

Payroll System with Attendance

and Leave Monitoring
1.3

Major Constraints

Passed

Passed

List down the constraints that will

affect the testing of Payroll
System with Attendance and
Leave Monitoring

2.0 TESTING PLAN

2.1

Software (SCIs) to

Indicates the software (modules)

be tested

to be tested.

2.1.1

Insert the screenshots of the

X
Interfaces

No

Failed

screenshots

modules to be tested.

Payroll System with Attendance and Leave Monitoring

Page 37

Student Information System EIS Document Quality Assurance Results

2.2

Testing Strategy
2.2.1

2.2.2

Unit

Describes the strategies/ways in

Testing

testing individual modules

Integration

Describes the strategies/ways in

Testing

testing the integration of EIS

Passed

Passed

systems.
X
2.2.3

Validation

Describes the strategies/ways in

Testing

testing the validations/trapping

inside the
system.
X

High-Order

Checks if the software meets the

Testing

requirements stated on the SRS

Failed

trapping

inside the system.

2.2.4

Validation or

This checks if

Failed

the software
meets the

of the systems document

requirements
stated on the
SRS of the
systems
document.
X

2.3

Testing Resources

Indicate the responsible persons

and Staffing

and resources needed in testing

Dont Use

Failed

bullets

the system.
Payroll System with Attendance and Leave Monitoring

Page 38

Student Information System EIS Document Quality Assurance Results

X
2.4

Test Record

Describes the ways of archiving

Keeping

test results.

Testing Tools and

Indicates the list of

Environment

tools/software needed to test the

No list of

Failed

tools/software
needed to test
the system
X

Test Schedule

Failed

Keeping

system.

2.6

No Test
Record

X
2.5

Maps out the schedule of testing

No Test

Failed

Schedule

for each module

X

3.0 TEST PROCEDURE

3.1

3.2

No Test

Failed

Procedure

Software (SCIs) to

List down the software/modules

be tested

that will be tested

No SCIs to be

Failed

tested

Testing Procedures
3.2.1

Unit

Lists down the procedures on

Testing

how will the QA test the

List down the

Failed

main points

individual modules.
3.2.2

Integration

Lists down the procedures on

Testing

how will the QA test the EIS

List down the

Failed

main points

Modules
Payroll System with Attendance and Leave Monitoring

Page 39

Student Information System EIS Document Quality Assurance Results

3.2.3

Validation

Lists down the procedures on

Testing

how will the QA test the

List down the

Failed

main points

integration of EIS systems.

3.2.4

High-Order

Lists down the procedures on

Testing

how will the QA test if the

List down the

Failed

main points

system meets the requirements.

Dont use
bullets

3.3

Testing Resources

Indicates the personnel and

and Staffing

resources involved in testing the

Dont use

Failed

bullets

system
3.4

Test Record

Describes the way of archiving

Keeping and Log

the results and log files of each

Dont use

Failed

bullets

test.

Payroll System with Attendance and Leave Monitoring

Page 40