ACTIVITY NO.

4
REQUIREMENT DETERMINATION

Determine the requirements (functional and non-functional) of your proposed system:

1. Functional/Feature Requirements of The System.

FUNCTIONAL REQUIREMENTS

FUNCTIONS PROCESS ORIENTED INFORMATION ORIENTED

 The system should  The system must

guide users through a
1.USER step-by-step process
REGISTRATION to create an account.
store user
information securely
and ensure that it is
only accessible by
authorized personnel.

 The system should  The system must

prompt users to enter store user login
their login credentials credentials securely
and perform a and ensure that they
validation process to are not accessible to
authenticate their unauthorized
2.USER identity. personnel.
AUTHENTICATION
 The users can log in
using their username
and password or
through their
respective QR Code
provided by the admin.

 The system should  The system must

provide a user-friendly store user profile
3.USER PROFILE interface for cadet information securely
MANAGEMENT officers to view and and ensure that it is
edit their profile only accessible by
information. authorized personnel.

 The system should  The system must

have a responsive ensure that user data
4. MOBILE design that adapts to is encrypted and
ACCESSIBILITY different screen sizes securely transmitted
and device types. over mobile
networks.
  The system should
allow cadet officers to
 The system must
send and receive
store communication
messages to/from
and notification data
other cadet officers or
securely and ensure
administrators.
that it is only
5.COMMUNICATION accessible by
AND NOTIFICATION authorized personnel.
 The system should
also send notifications
to cadet officers for
upcoming events,
changes in training
schedules, and other
important information.

2. LIST THE NON-FUNCTIONAL REQUIREMENTS.

NON-FUNCTIONAL
SYSTEM REQUIREMENTS
REQUIREMENTS
Technical  The system can be used even when
2.1 Environment the network is unavailable or offline.
OPERATIONAL  The system must be able to
interface with other programs and
tools used by the Cadet Officers of
System
Integration the 1202nd CDC, including systems
for email and messaging, training
management, and other similar
programs.
 The system must be designed to be
easily portable to other
Portability environments, such as different
operating systems, hardware
configurations, or cloud platforms.
 The system must be designed to be
easily maintained, including making
updates and bug fixes, and adding
new features.
 The code should be well-
Maintainability
documented, easy to understand,
and follow industry best practices.
 The system should also be designed
to facilitate testing and debugging, to
make maintenance easier.
  The system must be designed to
2.2
provide fast response times to user
Performance
requests.
Speed  The system should also be
optimized for fast database queries
and efficient use of system
resources.
 The system must be designed to
handle a large number of concurrent
Capacity users.
 The system should also be able to
handle a large amount of data.
 The system must be available to
users at all times.
 The system should also be designed
to recover quickly from any failures
or disruptions.
 The system must be designed to be
Availability and
Reliability reliable, with a minimum of 99.9%
successful transactions per day.
 The system should also be designed
to handle errors and exceptions
gracefully, with appropriate error
messages and error handling
procedures.
 The system must be designed to
2.3 provide accurate and reliable value
Security estimates for user accounts and
System Value
Estimates data.
 The system should also be designed
to store and retrieve value estimates
quickly and efficiently.
 The system must be designed to
provide secure access control, to
ensure that only authorized users
have access to the system and user
Access Control data. This includes measures such
as password policies, multi-factor
authentication, and role-based
access control, with a minimum of
two-factor authentication for
privileged users.
Encryption and  The system must be designed with
Authentication encryption and authentication in
mind, to protect user data and
prevent unauthorized access. This
includes measures such as
encryption of sensitive data, secure
login and authentication procedures,
 and secure communication
protocols.
 The system must be designed to
protect against viruses, malware,
and other malicious software, with
appropriate virus control measures
Virus Control in place. This includes measures
such as regular virus scans, virus
definition updates, and firewalls, with
a maximum time of 24 hours for
virus definition updates.
 At least three languages must be
2.4
supported by the system, which
Cultural and
must be built to support multiple
Political
Multilingual languages. Additionally, the system
needs to be created with concise
and clear language translation tools
to make it simple to translate user
interface components.
 The system must be designed to
allow customization, to meet the
specific needs of different users and
organizations. This includes
Customization measures such as customizable
user interfaces, customizable
workflows, and customizable
reporting tools, with a maximum of
10 customization options.
 The system must be built to make
implicit norms explicit in order to
prevent misunderstandings and
misconceptions. A maximum of
Making Unstated
Norms Explicit three clicks are required to obtain
any help or documentation, and this
includes measures like clear and
simple user manuals, help and
documentation, and tooltips.
 The system must be designed to
comply with all legal requirements,
including data protection and privacy
laws. This includes measures such
Legal as secure data storage and
transmission, data retention policies,
and clear and concise privacy
policies, with a minimum of 90 days
of data retention.