Qa Document Rmmm-Ts HR Profiling System

(Name of ERP) 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 whole

for the EIS/Module
1.1
Scope and intent of
Indicates the scope and purpose
RMMM activities
of RMMM activities.
Risk Management
States the organizational roles in
Organization Role
Risk Management.
1.2
2.0 RISK DESCRIPTION
Passed
The
proponents fail
to name the
roles for Risk
Management
but
it
was
identified with
information
and
the
constraints
also is given.
Failed
No table
Failed
Describes the risks in creating the

system.
2.1
Risk Table
Cites down the description and
probability of risks in tabular form.

2.1.1
Description of Risk
HR Profiling System
Describes the specified risks.
Passed
Page 4
2.1.2
Probability and
States the impact/effect of a risk
Impact of Risk
as well as the probability of it to
Passed
Passed
Passed
Passed
Passed
Passed
happen.
3.0 RISK MITIGATION,
Includes the monitoring of risks
MONITORING AND MANAGEMENT
and the procedures in managing

it.
3.1
Risk Mitigation for Risk m
Describes the steps in addressing

the risk that was stated.
3.1.1
Product Size
Indicates
the
scope
of
risk
definition.
3.1.2
Business Impact
States
the impact
businesses/systems
of
risk
that
in
are
currently being developed.

3.1.3
3.1.4
Customer(User)
Lists down the risk of the system
Risk
on its customer.
Process Risks
States the effect of risk in the

process of the system.
3.1.5
Technology Risks
HR Profiling System
Cites down the risk of the system
Page 5

in technology.
3.1.6
Development
Lists down the risks that are
Risks
present during the development
Passed
Passed
Passed
Passed
Passed
Passed
stage.
3.1.7
Employee Risks
Describes the risk of the system
(Teammates)
that is being developed to its

developers.
3.2
Risk Monitoring for Risk m
Describes
the
monitoring
process
procedures
of
for
determined risks.
3.2.1
Product Size
States
the
coverage/area
of
monitoring risks.
3.2.2
Business Impact
Cites
down
the
monitoring
procedures inside the business.

3.2.3
3.2.4
Customer(User)
Includes the risk monitoring for
Risk
clients/customers of the system.
Process Risks
Checks the monitoring activity for

the systems processes.
HR Profiling System
Page 6
3.2.5
Technology Risks
Passed
Passed
Passed
Monitors the risk that affects the

technologies used in developing
the system.
3.2.6
3.2.7
Development
Addresses the steps in monitoring
Risks
the development risks
Employee Risks
Monitors the risk that affects the
(Teammates)
employees or developers of the

system.
3.3
Risk Management for Risk
This
part
proponent
describes
will
how
manage
the
the
No
Risk
Failed
Management
identified risks.
3.3.1
Product Size
Describes the steps on how will

the group handle the largeness of
the project.
3.3.2
Business Impact
Sites down the procedures on how

will the proponents address the
requests or needs of the client.
3.3.3
Customer(User)
Shows the management of user
Risk
related risks.
HR Profiling System
Page 7
3.3.4
Process Risks
Describes the management of

process risks.
3.3.5
Technology Risks
Manages the risks in technologies

while developing the system.
3.3.6
Development
States the steps on how will the
Risks
developers
manage
the
development risks.
3.3.7
Employee Risks
Describes the management of
(Teammates)
employee risks.
4.0 SPECIAL CONDITIONS
States the special conditions that

the system encounters.
HR Profiling System
No
Special
Failed
Conditions
Page 8
SOFTWARE CONFIGURATION
Requirements
Compliance
Correctness
Remarks
MANAGEMENT (SCM)
1.0 INTRODUCTION
Passed or
Failed
Introduces
the
Software
Configuration Management as a
whole.
1.1
Scope and Intent of SCM
Describes the scope and purpose
activities
of doing the SCM activities.
1.2
SCM Organizational Role Cites
down
the
responsible
persons for the task given in

SCM Activities.
2.0 SCM TASKS
Passed
The
proponents fail
to
state
specific
person for a
specific role
Failed
Lists down the activities to be

done in SCM.
2.1
Identification
Passed
Identifies the task to be done to

ensure the proper configurations
of the system.
2.2
Configuration Control:
Describes on how the proponents

will control the changes in the
system.
HR Profiling System
Page 9
2.2.1
Description
Passed
Passed
Describes the procedures and

tools to be used in controlling the
changes.
2.3
Version Control
Cites down the way of the

proponents
in
numbering
the
versions of their documents and

system.
2.3.1
Description
Describes
the
versioning
technique in revised documents

and systems.
2.3.2
2.3.3
Increasing
Describes the way of increasing
Version Number
the version number of systems.
Work Products
States the revision history of the
and
system and documentation
Documentation
2.4
Configuration Status
Describes
Accounting
reporting of information required

to
the
effectively
recording
manage
Minor
and
Major update
not included
Failed
Versioning
and
the
validation for
auditing
the
documents are
not specified
Failed
and
the
configuration of a system or
HR Profiling System
Page 10

product.
2.4.1
Description
Describes
on
how
Passed
Passed
the
Configuration Status Accounting

will be done.
2.4.2
Work Products
States the revision history of the
and
system and documentation
Documentation
HR Profiling System
Page 11

SOFTWARE QUALITY ASSURANCE
Requirements
Compliance
Correctness
Remarks
Passed or
Failed
1.0 INTRODUCTION:
1.1
Scope and intent of SQA
Must include quality assurance
activities
intent of the ( ___ ) EIS
Passed
Passed
Passed
Quality Assurance information

is precise
1.2
SQA Organization Role
Description for every Role is

available
Must specify methodology or
diagrams providing information
about organization roles of the
project.
2.0 SQA Tasks
Specify task of software quality

assurance in (____) System
2.1
Task Overview
Must provide information about

task
overview
considering
SQA Tasks
HR Profiling System
Page 12
Task must be precise and

appropriate in (_____) System.
2.2
Standards, Practices and
Detailed information about the
Conventions SPC
standards,
(_____)
Passed
considering
system
task
or
transactions.
X
2.3
SQA Resources
Software Quality Assurance
No list of SQA
Failed
Resources
must be listed.
3.0 REVIEWS AND AUDITS
3.1
Generic Review
Passed
Conduction Review is existing
Guidelines
Roles and Responsibility is
precise
Must have information about

Review Work Product
3.2
Formal Technical
Description
Reviews
Walkthroughs
HR Profiling System
of
Review
No
Test
Failed
Specs
included
Page 13
Description
of
Review
Inspection
System Specification Review
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
HR Profiling System
Page 14
3.3
SQA Audits
Specify
team
approach
Some
requirement
are not met
to
Quality Assurance
Failed
4.0 PROBLEM REPORTING AND

CORRECTIVE
ACTION/FOLLOW-UP
4.1
Reporting Mechanism
Mechanism
of
reporting
Passed
in
(____) System is specified
It shows information about the

procedure in producing reports
about quality assurance
4.2
Responsibilities
Specify
roles
and
provide
Quality assurance for data
Valuation
collection
valuation
Failed
roles
Data Collection and
and
the
name of each
information about their roles.
4.3
Specify
Passed
is
clearly identified.
HR Profiling System
Page 15
4.4
Statistical SQA
Quality
assurance
Passed
Passed
Passed
Passed
Passed
for
statistical SQA is identified and

appropriate
to
(________)
System
5.0 SOFTWARE PROCESS
IMPROVEMENT ACTIVITIES
5.1
Goal and Object of SPI
Goals and Objectives of SPI is

clearly
identified
and
appropriate to (____) System

5.2
SPI Tasks and
SPI task of (_____) System is
Responsibilities
specified and clearly identified
6.0 SOFTWARE CONFIGURATION
Software
MANAGEMENT AND OVERVIEW
management
must
be
appropriate
configuration
and
overview
specified
to
and
(_________)
System
7.0 SQA TOOLS, TECHNIQUES,
Tools and techniques must be
METHODS
clearly identified
HR Profiling System
Page 16
HR Profiling System
Page 17

SYSTEM SPECIFICATIONS
Requirements
Compliance
Correctness
Remarks
Passed or
Failed
1.0 INTRODUCTION
1.1
Goals and Objectives
Detailed
objectives
of
Passed
the
system. Ex in GL. Must record

all the transactions of the
Hospital regarding money.
1.2
System Statement of
Detailed
objectives
of
Scope
system. Ex in GL. Must record
the
More detailed
Failed
objectives.
all the transactions of the

Hospital regarding money.
1.2.1
General
General Requirement of GL
Requirements
Module is specified
Include
EIS
the
Failed
basic
requirements
Requirement of GL module is
specified
HR Profiling System
Page 18
5 Analytical Reports
Free Format Query
Custom GUIs
Android Application
Import and Export Utility
X
1.3
System Context
Must include information about
Give
the
Failed
importance/
the importance of GL system
benefits of the
process inside Hotel EIS
HR
Profiling
System
X
1.4
Major Constraints
Computing Environment
Data Requirement
This
should
Failed
not be a selfserving.
Clearly Specified
2.0 FUNCTIONAL DATA
DESCRIPTION
HR Profiling System
Page 19
2.1
System Architecture
2.1.1
Architecture Model
Focus on the
main
menu/navigati
on for this
section
Failed
No subsystem
overview
Failed
No major data
objects
Failed
No
relationship
Failed
Appropriate Use of Figures

Appropriate Menus of Hotel
System
Every attributes must have

description.
2.1.2
Current
Subsystem
overview
Subsystem
appropriate to Hotel System
is
Overview
Information is clearly defined
2.2
Data Description
2.2.1
Major Data
All attributes is appropriate to
Objects
GL System
Every Attribute must have a
description.
2.2.2
Relationships
HR Profiling System
Objects of GL System are
Page 20

existing
Readable Diagrams and the
connection is correct
2.3
Human Interface
Description
for
Description
interface in GL system is
No
human
description
Failed
No subsystem
flow diagrams
Failed
No
prototyping
requirements
Failed
human
clearly defined.
3.0 SUBSYSTEM DESCRIPTION
3.1
Subsystem Flow
Objects are appropriate to GL
Diagrams
System
4.0 ENHANCED INTERFACE

PROTOTYPING
4.1
Prototyping Requirements
Screen for Login

Screens for the GL System
HR Profiling System
Page 21
HR Profiling System
Page 22
SOFTWARE REQUIREMENTS
SPECIFICATION
Requirements
Compliance
Correctness
Passed or
Failed
X
1.0 INTRODUCTION
Remarks
Must introduce the whole

requirements
of
the
system.
No
introduction
Failed
1.1
Detailed objectives of the

system. Ex in GL. Must
record
all
the
transactions
of
the
Hospital
regarding
money.
No goals and
objectives
Failed
1.2
System Statement of
Scope
This
includes
importance
of
requirements
in
system and why are
needed.
No
system
statement of
scope
specified
Failed
No
general
requirements
specified
Failed
the
the
the
they
Must have a table that

includes
the
requirements,
priority,
references
and
description
1.2.1
General
Requirements
HR Profiling System
Must be detailed general

requirements.
Must
include the 5 basic
requirements with the
Page 23

system functions.
1.2.2
Extended
Requirements
These are the extended

requirements. For ex.
The interim systems
No extended
requirements
specified
Failed
1.3
System Context
This
contains
importance
of
requirements
of
system.
the
the
the
No
system
context
specified
Failed
1.4
Major Constraints
These are the constraint

in the requirements. It is
not about the time,
funding.
No
major
constraints
specified
Failed
Must contain all the user

roles and what they are
doing in the system
No
user
profiles
specified
Failed
2.0USAGE SCENARIO
2.1
User Profiles
2.2
Use-Cases
2.2.1
Use Case
Diagram
Must have a use-case

diagram including all the
users.
No use case
diagram
created
Failed
2.2.2
Use Case
Description
Must have all the use

case
including
the
preconditions,
trigger,
exceptions and goals.
No use case
description
specified
Failed
HR Profiling System
Page 24
2.3
Special Usage
Considerations
Must
contain
considerations
special users of
system.
the
for
the
No
special
usage
consideration
specified
Failed
2.4
Activity Diagram
Must have diagrams of

the main activities in the
system.
No
activity
diagram
specified
No data model
and
description
Failed
3.0 DATA MODEL AND

DESCRIPTION
3.1
Failed
Data Description
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.
No data object
and dictionary
specified
Failed
4.0 FUNCTIONAL MODEL AND

DESCRIPTION
4.1
Subsystem Flow
Diagrams
It
contains
subsystem
of
module.
the
the
No subsystem
flow diagrams
created
Failed
4.2
Human Interface
It is the human interface

requirements
of
the
system.
No
human
interface
specified
Failed
HR Profiling System
Page 25
5.0 RESTRICTIONS, LIMITATIONS

AND CONSTRAINTS
It includes things that the

system cannot do.
6.0 VALIDATION CRITERIA
The Functional and Non

Functional Requirements
of the system.
HR Profiling System
No
restrictions,
limitations
and
constraints
included
No validation
criteria
Failed
Failed
Page 26
SOFTWARE DESIGN SPECIFICATION
Requirements
Compliance
Correctness
Remarks
Passed or
Failed
1.0 INTRODUCTION
X
1.1
Focuses on the
No goals and
Failed
objectives
goals of the system

in the design
X
1.2
System Statement of Scope
The scope of the
No system
Failed
statement of
system in the
goals
design.
1.2.1
General Requirements
The general
No general
requirements in the
requirements
design that
specified
Failed
comprises the 5
basic requirements
together with the
module features.
1.3
System Context
Significance of the
design in the
HR Profiling System
No system
Failed
context
Page 27

development of the
specified
system
1.4
Major Constraints
The design
No major
constraints that the
constraints
system can have.
specified
Failed
2.0DATA DESIGN
2.1
Database Description
Contains the tables
No database
together with the
description
attributes and table
specified
Failed
description.
3.0 ARCHITECTURAL AND COMPONENT-
Must have UML
LEVEL DESIGN
diagram.
3.1
3.2
Program Structure
Description for Components
HR Profiling System
Comprises of the
No program
System
structure
Composition
specified
The components of
No
the system are the
description for
users that have the
components
narrative, interface
specified
Failed
Failed
Page 28

and algorithmic
description and
design class
hierarchy and
restrictions and
limitations of each.
4.0 USER INTERFACE DESIGN
4.1
Description of the User

Interface
Describes the
No
importance of the
description of
UI design.
the user
Failed
interface
provided
4.1.1
Screen Images
Sample Images.
No screen
Failed
images
specified
4.1.2
Objects and Actions
All of the objects
No objects
that will be used by
and actions
the system (ex.
specified
Failed
Login button) and

what will be the
main actions
HR Profiling System
Page 29

afterwards.
4.2
4.3
Interface Design Rules
Components Available
The Eight Golden
No interface
Rules of Design
design rules
Interface
specified
All of the
No
components
component
available in the
available
template / design
specified
Failed
Failed
are described here.

4.3.1
4.3.2
Intrinsic Controls
ActiveX Controls
The basic controls
No intrinsic
must be detailed
constraints
with images.
specified
The advanced
No activeX
components must
controls
be detailed with
specified
Failed
Failed
image.
5.0 RESTRICTIONS, LIMITATIONS AND
It includes things
COSNTRAINTS
that the system
restrictions,
cannot do.
limitations,
No
Failed
and
HR Profiling System
Page 30

constraints
specified
6.0 TESTING ISSUES
6.1
Classes of Test
Must have the
classes of test for
No classes of
Failed
test specified
system interface,
login, system
setup, transactions
and other important
parts of the
system.
6.2
Performance Bounds
Contains how long
No
the system will
performance
respond. It includes
bounds
the best and worst
specified
Failed
case scenario.
6.3
Identification of Critical
Components
HR Profiling System
Describes the
No
detailed critical
identification
components of the
of critical
system. For
components
example in General
specified
Failed
Page 31

Ledger, the
identification of
subsidiary ledgers.
HR Profiling System
Page 32
TEST SPECIFICATION
Requirements
Compliance
Correctness
Remarks
Passed or
Failed
1.0 INTRODUCTION
X
1.1
1.2
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.
Passed
Passed
[Insert Module Name]

1.3
Major Constraints
List down the constraints that will

affect the testing of [Insert
Module Name]
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.
2.2
Testing Strategy
HR Profiling System
Page 33
2.2.1
2.2.2
Unit
Describes the strategies/ways in
Testing
testing individual modules
Integration
Testing
testing the integration of EIS
Passed
Passed
systems.
X
2.2.3
Validation
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
No Testing
Failed
Resources
and Staffing
the system.
X
2.4
Test Record
HR Profiling System
No Test
Failed
Describes the ways of archiving
Page 34

Keeping
test results.
Record
Keeping
X
2.5
Testing Tools and
Indicates the list of
Environment
tools/software needed to test the
No Testing
Failed
Tools and
Environment
system.
X
2.6
Test Schedule
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
No unit
Failed
testing
individual modules.
3.2.2
Integration
Testing
how will the QA test the EIS
No integration
Failed
Testing
Modules
3.2.3
Validation
HR Profiling System
No validation
Failed
Page 35

Testing
how will the QA test the
testing
integration of EIS systems.

3.2.4
High-Order
Testing
how will the QA test if the
No high order
Failed
testing
system meets the requirements.

3.3
3.4
Testing Resources
Indicates the personnel and
and Staffing
resources involved in testing the
resources and
system
staffing
X
No testing
Test Record
Describes the way of archiving
Keeping and Log
the results and log files of each
keeping and
test.
log
HR Profiling System
No test record
Failed
Failed
Page 36

Qa Document Rmmm-Ts HR Profiling System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Qa Document Rmmm-Ts HR Profiling System

Uploaded by

Copyright:

Available Formats

(Name of ERP) Document Quality Assurance Results

RISK MITIGATION, MONITORING

AND MANAGEMENT (RMMM)

Introduce the RMMM as a whole

Scope and intent of

Indicates the scope and purpose

States the organizational roles in

2.0 RISK DESCRIPTION

Describes the risks in creating the

Cites down the description and

probability of risks in tabular form.

Describes the specified risks.

(Name of ERP) Document Quality Assurance Results

States the impact/effect of a risk

as well as the probability of it to

Includes the monitoring of risks

MONITORING AND MANAGEMENT

and the procedures in managing

Risk Mitigation for Risk m

Describes the steps in addressing

currently being developed.

Lists down the risk of the system

States the effect of risk in the

Cites down the risk of the system

(Name of ERP) Document Quality Assurance Results

Lists down the risks that are

present during the development

Describes the risk of the system

that is being developed to its

Risk Monitoring for Risk m

procedures inside the business.

Includes the risk monitoring for

clients/customers of the system.

Checks the monitoring activity for

(Name of ERP) Document Quality Assurance Results

Monitors the risk that affects the

Addresses the steps in monitoring

the development risks

Monitors the risk that affects the

employees or developers of the

Risk Management for Risk

Describes the steps on how will

Sites down the procedures on how

Shows the management of user

(Name of ERP) Document Quality Assurance Results

Describes the management of

Manages the risks in technologies

States the steps on how will the

Describes the management of

4.0 SPECIAL CONDITIONS

States the special conditions that

(Name of ERP) Document Quality Assurance Results

Scope and Intent of SCM

Describes the scope and purpose

of doing the SCM activities.

SCM Organizational Role Cites

persons for the task given in

2.0 SCM TASKS

Lists down the activities to be

Identifies the task to be done to

Describes on how the proponents

(Name of ERP) Document Quality Assurance Results

Describes the procedures and