FYP-Proposal

By

XYZ 2016-GCUF-071948
XYZ 2016-GCUF-071938
XYZ 2016-GCUF-071944

BACHELOR OF SCIENCE
IN
COMPUTER SCIENCE

DEPARTMENT OF COMPUTER SCIENCE

Government College University Faisalabad

2021
Table of Contents
Table Of Content........................................................................................................................ ii
Revision History ........................................................................................................................ iii
1. Introduction ............................................................................................................................. 1
1.1 General Information ....................................................................................................................... 1
1.2 Purpose ......................................................................................................................................... 1
1.3 Document Conventions .................................................................................................................. 1
1.4 Project Objective ............................................................................................................................ 1
1.5 Intended Audience and Reading Suggestions ................................................................................ 2
1.6 Project Scope ................................................................................................................................ 2
2. Overall Description ................................................................................................................. 2
2.1 Product Perspective ....................................................................................................................... 2
2.2 Product Features ........................................................................................................................... 3
2.3 User Classes and Characteristics................................................................................................... 3
2.4 Operating Environment .................................................................................................................. 3
2.5 Design and Implementation Constraints ......................................................................................... 3
2.6 User Documentation ...................................................................................................................... 3
2.7 Assumptions and Dependencies .................................................................................................... 3
3. System Features ..................................................................................................................... 4
3.1 System Feature 1 .......................................................................................................................... 4
3.2 System Feature 2 (and so on) ........................................................................................................ 5
4. External Interface Requirements ........................................................................................... 5
4.1 User Interfaces .............................................................................................................................. 5
4.2 Hardware Interfaces ....................................................................................................................... 5
4.3 Software Interfaces ........................................................................................................................ 5
4.4 Communications Interfaces ............................................................................................................ 5
5. Other Nonfunctional Requirements ....................................................................................... 6
5.1 Performance Requirements ........................................................................................................... 6
5.2 Safety Requirements ..................................................................................................................... 6
5.3 Security Requirements ................................................................................................................... 6
5.4 Software Quality Attributes ............................................................................................................. 6
6. WBS Project Management ...................................................................................................... 7
7. Analysis model........................................................................................................................ 7
7.1 Use Case Diagram......................................................................................................................... 7
7.2 Class Diagram ............................................................................................................................... 7
7.3 Object Diagram .............................................................................................................................. 7
7.4 Sequence Diagram ........................................................................................................................ 7
7.5 Activity Diagram ............................................................................................................................. 7
7.6 Collaboration Diagram ................................................................................................................... 7
7.7 State Transition Diagram................................................................................................................ 7
7.8 ERD ................................................................................................................................................ 7
8. Tools & Technologies ............................................................................................................. 7
8.1 Programming Languages ............................................................................................................... 7
8.2 Databases/Data storages............................................................................................................... 7
8.3 Operating System .......................................................................................................................... 7
Appendix A: Glossary ................................................................................................................ 8
Appendix B: Check List ............................................................................................................. 9
Appendix C: Supervisory Committee ..................................................................................... 10

Revision History
Name Date Reason For Changes Version
 Government College University Faisalabad Page 4

1. Introduction

1.1 General Information

Information to be provided in this section gives a specific name to the project as well as pertinent
information about the personal involved.

Project Name: Cybersecurity Website Starting Date: 7/29/2020

_

Controlling Agency: LGES Final Date: 8/29/2020

_ _
_
Prepared By: XYZ Authorized by: LGES management
_

1.2 Purpose

The purpose of this document is to specify the software requirements for the development of a
cybersecurity website. This project, intended as a final year project, aims to provide comprehensive
information and resources on various aspects of cybersecurity, including threat identification,
protection measures, and best practices for securing digital assets. The website will be developed
using HTML, CSS, and JavaScript to ensure a responsive and interactive user experience.

This Software Requirements Specification (SRS) document will cover the entire scope of the
cybersecurity website, detailing the features, functionalities, and user interactions expected in the
final product. It will encompass the following key components of the website:

• Home Page: An introduction to the website with an overview of cybersecurity, latest news,
and updates in the field.
• Threat Identification: A section dedicated to common cybersecurity threats, their
characteristics, and how they can be identified.
• Protection Measures: Guidelines and strategies for protecting against cybersecurity threats,
including tools and software recommendations.
• Best Practices: A comprehensive list of best practices for individuals and organizations to
follow to enhance their cybersecurity posture.
• Resources: Links to additional resources, such as articles, whitepapers, and tutorials, for
further learning.

1.3 Document Conventions

This Software Requirements Specification (SRS) document follows a set of standards and
typographical conventions to ensure clarity and consistency throughout. The conventions used in this
document are as follows:

1. Font and Text Formatting:

 Government College University Faisalabad Page 5
o Primary Text: The primary text of this document is written in a standard font (e.g.,
Times New Roman or Arial) with a font size of 12 points.
o Headings: Section and subsection headings are formatted in bold to distinguish them
from the body text. Major section headings (e.g., 1.0, 2.0) are in a larger font size (e.g.,
14 points), while subsection headings (e.g., 1.1, 1.2) are in the same font size as the
primary text but bolded.
o Emphasis: Italics are used to emphasize specific terms or phrases that require special
attention.
2. Numbering Conventions:
o Sections and subsections are numbered hierarchically to indicate their level of
importance and relation to other sections (e.g., 1.0, 1.1, 1.1.1).
3. Requirement Identification:
o Each requirement within this document is uniquely identified by a label (e.g., REQ-1,
REQ-2) to facilitate easy reference and tracking.
4. Prioritization:
o Requirements are prioritized to indicate their level of importance. Priorities are
categorized as follows:
▪ High Priority (H): Essential requirements that must be implemented in the initial
release.
▪ Medium Priority (M): Important requirements that should be implemented but
may be deferred to later releases if necessary.
▪ Low Priority (L): Desirable requirements that can be implemented if time and
resources permit.
5. Use of Tables and Lists:
o Tables and lists are used to organize information clearly and concisely. Tables are used
for presenting data in a structured format, while bullet points and numbered lists are
used to enumerate items or steps.
6. References:
o References to external documents or sections within this document are indicated by
hyperlinks or cross-references (e.g., "see Section 3.1").

By adhering to these conventions, this SRS aims to provide a clear, organized, and easily navigable
document for all stakeholders involved in the development of the cybersecurity website.

1.4 Project Objective

This section defines the objectives of the cybersecurity website project as they relate to the strategic
goals of the organization. Projects inherently involve uncertainty, so an initial risk assessment will be
conducted as part of this charter to identify, quantify, and establish mitigation responses to high-level
risk events that could adversely affect the project outcome.

The project will support the following organizational strategic goals. For each goal, specific project
objectives are identified. The project plan developed as a result of this project charter will:

• Develop a project performance measurement plan to measure performance against these

objectives.
• Provide a project performance report to document the results.

The external oversight committee must approve the project performance measurement plan.
 Government College University Faisalabad Page 6

Agency Goals Project Objectives

Simplify the processes involved in cybersecurity Develop the website as a centralized platform for
awareness and implementation to make the cybersecurity information, resources, and tools.
website user-friendly and accessible.
Showcase how a centralized website can
Ensure all cybersecurity measures, protocols, and
streamline the process of obtaining cybersecurity
best practices are well-documented to enhance
the quality of information provided. information and resources.
Ensure users are comfortable and proficient in using
Design the website to enhance user the website's features and functionalities.
experience, making it easier for users to find
and utilize the information, thus improving
their overall cybersecurity knowledge and
practices.
Encourage users to make the website an integral
part of their cybersecurity strategy. Support users
in incorporating the information and resources
from the website into their daily operational
processes.

1.5 Intended Audience and Reading Suggestions

This document is intended for a variety of readers who have a vested interest in the development and
implementation of the cybersecurity website. The intended audience includes:

• Developers: Responsible for coding and implementing the website features. Developers
should focus on the detailed functional requirements, system architecture, and design
specifications.
• Project Managers: Oversee the project timeline, resources, and deliverables. Project
managers should start with the project overview, goals, objectives, and the project
performance measurement plan.
• Marketing Staff: Plan and execute the promotional strategies for the website. Marketing staff
should read the sections on user experience and interface design to understand how the
website will meet user needs.
• Users: The end-users who will utilize the website for cybersecurity information and resources.
Users can refer to the use case scenarios and user interface design sections to understand
how to navigate and benefit from the website.
• Testers: Ensure the website meets the specified requirements and functions correctly.
Testers should focus on the sections detailing functional and non-functional requirements, as
well as the testing plan and procedures.
• Documentation Writers: Create user manuals, help guides, and other supporting documents.
Documentation writers should read the entire SRS to fully understand the website's features
and how to document them effectively.

Organization of the SRS:

The document is organized as follows:

1. Introduction:
 Government College University Faisalabad Page 7
o Purpose
o Document Conventions
o Intended Audience and Reading Suggestions
o Project Scope
o References
2. Overall Description:
o Product Perspective
o Product Functions
o User Classes and Characteristics
o Operating Environment
o Design and Implementation Constraints
o Assumptions and Dependencies
3. System Features:
o Detailed descriptions of each feature
4. External Interface Requirements:
o User Interfaces
o Hardware Interfaces
o Software Interfaces
o Communication Interfaces
5. System Requirements:
o Functional Requirements
o Non-functional Requirements
o System Attributes
o Other Requirements
6. Appendices:
o Glossary
o Acronyms and Abbreviations

Reading Suggestions:

• Overview Sections: All readers should start with the Introduction to get a high-level
understanding of the project's purpose, scope, and objectives.
• Project Managers and Stakeholders: Proceed to the Overall Description and Project
Objectives sections to understand the strategic alignment and high-level requirements.
• Developers and Testers: Focus on the System Features and System Requirements sections
for detailed technical specifications and requirements.
• Marketing Staff and Documentation Writers: Read the User Interfaces and System
Features sections to understand the user experience and interface design.
• Users: Refer to the User Classes and Characteristics and User Interfaces sections for an
overview of how to navigate and utilize the website.

1.6 Project Scope

The cybersecurity website project aims to develop a comprehensive online platform that provides
vital information, resources, and tools related to cybersecurity. This project is intended as a final year
project for a student and will utilize HTML, CSS, and JavaScript to ensure a modern, responsive, and
user-friendly experience.

Purpose: The primary purpose of the cybersecurity website is to educate and inform users about
various aspects of cybersecurity, including threat identification, protection measures, and best
 Government College University Faisalabad Page 8
practices. The website will serve as a centralized hub for cybersecurity knowledge, making it
accessible to a wide audience ranging from beginners to advanced users.

Benefits:

• Educational Resource: Provide detailed information on cybersecurity threats, protective

measures, and best practices.
• User-Friendly Interface: Offer an intuitive and easy-to-navigate platform that enhances user
experience.
• Centralized Information Hub: Serve as a single point of reference for all cybersecurity-
related queries and resources.
• Awareness and Prevention: Help users stay informed about the latest cybersecurity trends
and preventive measures.

Objectives and Goals:

• Educate Users: Increase awareness and understanding of cybersecurity threats and best
practices.
• Provide Resources: Offer tools, guidelines, and links to additional resources for further
learning.
• Improve User Experience: Design an intuitive and engaging user interface to facilitate easy
access to information.
• Support Corporate Goals: Align with corporate strategies to enhance cybersecurity
awareness and promote best practices within the organization.

Relation to Corporate Goals: The development of this cybersecurity website aligns with broader
corporate goals by promoting cybersecurity awareness and education. By providing a centralized
resource for cybersecurity information, the website supports the organization's strategic objective of
enhancing digital security and protecting sensitive information. The project contributes to the
corporate mission of fostering a secure and informed digital environment.

2. Overall Description

2.1 Product Perspective

The cybersecurity website project is a new, self-contained product developed as part of a final year
project for a student. It aims to provide comprehensive information and resources on cybersecurity,
focusing on threat identification, protection measures, and best practices. The following sections
describe the context, origin, and relationship of this product to other systems.

Context and Origin:

• New Development: This cybersecurity website is being developed from the ground up, with
no predecessors. It is tailored specifically for educational and informational purposes within
the cybersecurity domain.
• Academic Project: The project is conceived as an academic exercise to showcase the
student's proficiency in web development using HTML, CSS, and JavaScript, while addressing
the critical topic of cybersecurity.

Product Classification:
 Government College University Faisalabad Page 9
• Standalone Product: The cybersecurity website is a standalone system and does not form
part of a larger product family. It is designed to operate independently, without dependencies
on other systems.
• No Replacement: This website is not intended to replace any existing platforms or tools.
Instead, it aims to create a unique and focused resource for cybersecurity education.

System Relationship and Interfaces:

• Self-Contained System: As a self-contained product, the cybersecurity website

encompasses all functionalities within its own framework. It does not integrate or interface with
external systems or components.
• Internal Components: The website will consist of various internal components such as the
homepage, threat identification section, protection measures section, best practices section,
and resources section. These components will be interconnected to provide a seamless user
experience.

Diagram of Major Components: Below is a simple diagram illustrating the major components of the
cybersecurity website and their interconnections:

Functional Relationships:

• Home Page: Acts as the entry point, providing an overview and navigation to other sections.
• Threat Identification: Describes various cybersecurity threats, linking to detailed information
pages.
• Protection Measures: Offers guidelines and strategies for mitigating cybersecurity risks, with
links to tools and resources.
• Best Practices: Lists recommended practices for enhancing cybersecurity, with detailed
explanations.
• Resources Section: Provides external links and references for further reading and learning.
 Government College University Faisalabad Page 10

2.2 Product Features

The cybersecurity website is designed to serve as an educational platform, providing users with
essential information and tools related to cybersecurity. Below is a summary of the major features
that the website will offer:

1. Home Page
• Overview and Introduction: The home page will provide an introduction to the website, highlighting its
purpose and the importance of cybersecurity.
• Navigation Menu: A user-friendly navigation menu will allow users to easily access different sections
of the website.

2. Threat Identification
• Threat Categories: This section will categorize and describe various cybersecurity threats such as
malware, phishing, ransomware, and more.
• Detailed Descriptions: Users will be able to access detailed descriptions of each threat, including
examples and potential impact.
• Recent Threats: A subsection dedicated to the latest cybersecurity threats, providing up-to-date
information on emerging risks.

3. Protection Measures
• Preventive Strategies: This section will outline strategies to prevent cybersecurity breaches, including
password management, encryption, and firewalls.
• Tools and Software: Information on various cybersecurity tools and software that users can
implement to protect themselves from threats.
• Step-by-Step Guides: Detailed guides on how to implement different protection measures, tailored for
users with varying levels of expertise.

4. Best Practices
• Security Guidelines: A comprehensive list of best practices for maintaining cybersecurity, both at an
individual and organizational level.
• Regular Updates: Advice on keeping software and systems up to date to prevent vulnerabilities.
• Case Studies: Real-world examples of successful cybersecurity implementations and lessons learned.

5. Resources
• External Links: A curated list of external resources, such as articles, whitepapers, tutorials, and
cybersecurity organizations.
• Downloadable Materials: Users can download guides, checklists, and other educational materials.
• Glossary: A glossary of common cybersecurity terms and acronyms to help users understand
technical language.

6. User Interface and Experience

• Responsive Design: The website will be fully responsive, ensuring it is accessible on a wide range of
devices, including desktops, tablets, and smartphones.
• Interactive Elements: Features such as quizzes, videos, and infographics will enhance user
engagement and learning.
 Government College University Faisalabad Page 11
7. Search Functionality
• Keyword Search: Users will be able to search for specific topics or terms using a keyword-based
search feature.
• Filtered Search: Advanced search options will allow users to filter results by category, date, or
relevance.

Diagram of Major Features:

Below is a simplified diagram illustrating the relationship between the major features of the
cybersecurity website:

2.3 User Classes and Characteristics

User Classes and Characteristics
In this section, we identify the different user classes that are anticipated to interact with the cybersecurity
website. Each user class is defined by its distinct characteristics, including frequency of use, level of technical
expertise, security or privilege levels, educational background, and experience. Understanding these user
classes helps tailor the website’s features and functionalities to meet the specific needs of each group.
2.3.1 Cybersecurity Enthusiasts
• Description: Individuals with a keen interest in cybersecurity but with varying levels of technical
expertise.
• Frequency of Use: Regular
• Subset of Product Functions Used: Primarily interested in educational content, threat identification,
and best practices.
• Technical Expertise: Low to Medium
• Security or Privilege Levels: General access
• Educational Level: High school to college level
 Government College University Faisalabad Page 12
• Experience: Limited hands-on experience, seeking to expand knowledge.

• Pertinent Characteristics: This group values clear explanations, visual aids, and practical examples.
Content should be accessible and educational, focusing on building foundational knowledge.
2.3.2 IT Professionals
• Description: Individuals working in IT or related fields who require up-to-date information on
cybersecurity threats and protection measures.
• Frequency of Use: Frequent
• Subset of Product Functions Used: Detailed threat identification, protection measures, and
resources sections.
• Technical Expertise: High
• Security or Privilege Levels: May require higher access for advanced resources or tools.
• Educational Level: College degree in IT or a related field
• Experience: Experienced professionals with significant hands-on experience in cybersecurity.
• Pertinent Characteristics: This group demands in-depth, technical content and up-to-date
information. They may also require access to advanced tools and resources to implement protection
measures effectively.
2.3.3 Educators and Trainers
• Description: Teachers, professors, and trainers who incorporate cybersecurity topics into their
curriculum or training programs.
• Frequency of Use: Regular to Frequent
• Subset of Product Functions Used: Educational content, best practices, and resources for
instructional purposes.
• Technical Expertise: Medium to High
• Security or Privilege Levels: General access with potential for higher access for educational
resources.
• Educational Level: College degree or higher, often in education or IT-related fields
• Experience: Varied experience, but generally knowledgeable about cybersecurity basics.
• Pertinent Characteristics: This group requires structured and credible content that can be easily
integrated into teaching materials. They value downloadable resources, case studies, and clear
explanations of concepts.
2.3.4 Business Executives
• Description: Decision-makers in organizations who need to understand cybersecurity risks and
implement strategies to mitigate them.
• Frequency of Use: Occasional
• Subset of Product Functions Used: Overview sections, best practices, and protection measures with
a focus on strategic implementation.
• Technical Expertise: Low to Medium
• Security or Privilege Levels: May require access to strategic content and decision-making tools.
• Educational Level: College degree, often in business or management
• Experience: Experienced in management but may have limited technical cybersecurity knowledge.
 Government College University Faisalabad Page 13
• Pertinent Characteristics: This group prioritizes high-level content that links cybersecurity to business
strategy. They value executive summaries, risk assessment tools, and case studies demonstrating ROI
on cybersecurity investments.
2.3.5 Students
• Description: High school or college students studying cybersecurity or related fields.
• Frequency of Use: Regular
• Subset of Product Functions Used: Educational content, best practices, and resources for
assignments or projects.
• Technical Expertise: Low to Medium
• Security or Privilege Levels: General access
• Educational Level: High school to college level
• Experience: Limited, primarily theoretical knowledge with some practical exposure through
coursework.
• Pertinent Characteristics: This group needs accessible, educational content that supports their
studies. Interactive elements like quizzes and simulations can enhance their learning experience.
2.3.6 General Public
• Description: Individuals with a general interest in cybersecurity, often concerned with personal online
safety.
• Frequency of Use: Occasional
• Subset of Product Functions Used: Home page, basic threat identification, and protection measures.
• Technical Expertise: Low
• Security or Privilege Levels: General access
• Educational Level: Varied, typically high school or lower
• Experience: Minimal technical experience; basic understanding of online safety.
• Pertinent Characteristics: This group requires simple, non-technical explanations and easy-to-follow
guidelines. Visual aids and step-by-step instructions are essential for ensuring comprehension.

2.4 Operating Environment

This section describes the operating environment in which the cybersecurity website, built using
HTML, CSS, and JavaScript, will operate. It outlines the hardware, software, and relevant system
components necessary for the website's proper functioning.

2.4.1 Hardware Platform

• Client-Side:
o Minimum Requirements:
▪ Processor: Dual-core CPU with 2 GHz or higher
▪ RAM: 2 GB
▪ Storage: 50 MB of available disk space
▪ Display: 1280 x 720 resolution or higher
o Recommended Requirements:
▪ Processor: Quad-core CPU with 2.5 GHz or higher
▪ RAM: 4 GB or more
 Government College University Faisalabad Page 14
▪ Storage: 100 MB of available disk space
▪ Display: 1920 x 1080 resolution or higher

2.4.2 Operating System

• Client-Side:
o Windows 7 or later
o macOS 10.10 (Yosemite) or later
o Linux distributions such as Ubuntu 16.04 or later
o Mobile: Android 7.0 (Nougat) or later, iOS 10.0 or later

2.4.3 Web Browsers

• Supported Browsers:
o Google Chrome (latest version)
o Mozilla Firefox (latest version)
o Microsoft Edge (latest version)
o Safari (latest version)
o Mobile Browsers: Chrome for Android, Safari for iOS

2.4.4 Software Dependencies

• Front-End Technologies:
o HTML5 for structuring content
o CSS3 for styling and layout
o JavaScript (ES6+) for interactivity and dynamic content

2.4.5 Development Tools

• IDE/Editors:
o Visual Studio Code (latest version)
o Sublime Text (latest version)
o Atom (latest version)
• Version Control:
o Git (optional, for version tracking)

2.4.6 Other Requirements

• Security: The website should be hosted on a secure server with SSL/TLS enabled for secure
communication.
• Network: A stable internet connection is required for users to access the website.

2.5 Design and Implementation Constraints

This section outlines the constraints that will affect the design and implementation of the
cybersecurity website. These constraints define the boundaries within which the development
process must occur, limiting the options available to the developers.

2.5.1 Technology Constraints

• Frontend Technologies Only: The website will be developed exclusively using HTML, CSS, and
JavaScript. No backend technologies, databases, or server-side scripting will be utilized.
 Government College University Faisalabad Page 15
• Browser Compatibility: The website must be compatible with modern web browsers (e.g., Chrome,
Firefox, Edge, Safari) and maintain a consistent user experience across different platforms and
devices, including mobile.

2.5.2 Security Considerations

• SSL/TLS Requirement: The website must be hosted on a server with SSL/TLS enabled to ensure
secure communication between users and the site.
• Client-Side Security: Since the website relies entirely on frontend technologies, care must be taken to
avoid common client-side security vulnerabilities such as cross-site scripting (XSS) and man-in-the-
middle (MITM) attacks.

2.5.3 Performance Constraints

• Page Load Time: The website must be optimized for fast load times, particularly on mobile devices
with slower internet connections. This includes minimizing the use of large images, scripts, and other
resources.
• Memory Usage: The website should be designed to minimize memory usage, ensuring smooth
performance even on devices with limited hardware resources.

2.5.4 Design Conventions

• Responsive Design: The website must be fully responsive, adapting seamlessly to various screen
sizes and orientations.
• Accessibility Standards: The design should adhere to accessibility guidelines (e.g., WCAG 2.1) to
ensure the website is usable by people with disabilities.

2.5.5 Development Tools and Standards

• Code Standards: Developers must follow best practices for writing clean, maintainable, and well-
documented HTML, CSS, and JavaScript code.
• Development Environment: The development should be carried out using text editors or IDEs that
support HTML, CSS, and JavaScript, such as Visual Studio Code or Sublime Text.

2.5.6 Regulatory and Compliance Constraints

• Data Privacy: The website must comply with relevant data privacy regulations, ensuring that any user
data handled by the website is protected and not exposed to unauthorized parties.

2.6 User Documentation

This section outlines the user documentation that will accompany the cybersecurity website. The
documentation will be designed to assist users in understanding and effectively using the website's
features.

2.6.1 User Manuals

• Website User Guide:
o Description: A comprehensive manual that provides detailed instructions on how to navigate
and use the various features of the cybersecurity website. It will include sections on basic
website navigation, understanding security features, and how to report security issues.
o Format: PDF document, accessible from the website’s help section.
 Government College University Faisalabad Page 16
2.6.2 Online Help

• Interactive Help Tooltips:

o Description: Context-sensitive help tooltips will be integrated into the website, offering brief
explanations of features and functions as users interact with the website.
o Format: Inline help displayed in response to user actions (hover or click).
• Help Center:
o Description: An online help center hosted on the website, containing articles, FAQs, and
troubleshooting guides to assist users in resolving common issues.
o Format: HTML pages accessible via the website's navigation menu.

2.6.3 Tutorials

• Getting Started Tutorial:

o Description: A step-by-step tutorial designed to introduce new users to the cybersecurity
website’s basic features, including how to navigate the site, access resources, and perform key
tasks.
o Format: Interactive web-based tutorial available on the website.
• Video Tutorials:
o Description: A series of short video tutorials that visually demonstrate how to use various
features of the website, including security best practices and navigating the site.
o Format: Video files embedded in the website and accessible through the help center.

2.6.4 Documentation Delivery Formats

• All user documentation will be delivered in digital formats, primarily as web-based content or
downloadable PDFs.
• Documentation will be accessible across devices (desktop, tablet, and mobile) to ensure users can
access help resources from any platform.

2.7 Assumptions and Dependencies

This section identifies the assumptions made during the development of the cybersecurity website
and the dependencies that could impact the project if they change or prove incorrect.

2.7.1 Assumptions
• Stable Operating Environment: It is assumed that the users will access the website in a stable
operating environment with modern web browsers and up-to-date operating systems. This includes the
assumption that users have a reliable internet connection.
• Browser Compatibility: It is assumed that the website will be compatible with all major web browsers
that adhere to standard web technologies (HTML5, CSS3, JavaScript ES6+).
• User Technical Expertise: The primary users are assumed to have a basic understanding of
navigating websites, and minimal training will be required to use the website effectively.
• Security Protocols: It is assumed that the web hosting environment will have proper security
protocols (e.g., SSL/TLS) already in place to ensure secure communication between the client and
server.

2.7.2 Dependencies
• Third-Party Libraries and Frameworks: The project may depend on third-party JavaScript libraries
(e.g., jQuery, Bootstrap) to enhance functionality and design. Any updates or deprecations of these
libraries could impact the website's performance or compatibility.
 Government College University Faisalabad Page 17
• Hosting Service: The availability and performance of the website are dependent on the selected web
hosting service. Any changes or disruptions to the hosting service could affect website accessibility.
• Compliance with Web Standards: The website's development is dependent on adherence to current
web standards. Any significant changes to these standards could require adjustments to the website's
codebase.
• Security Updates: The project depends on timely updates to address any security vulnerabilities in the
technologies used (HTML, CSS, JavaScript). Failure to apply these updates could expose the website
to security risks.
• User Devices and Browsers: The website's performance and appearance may vary based on the
user's device, browser, and screen resolution. It is assumed that users will not be using outdated or
unsupported browsers or devices.

3. System Features
This section details the functional requirements of the cybersecurity website by organizing them
according to key system features. Each feature includes a description, priority level, user interaction
sequences, and the associated functional requirements necessary to achieve the desired
functionality.

3.1 Home Page

3.1.1 Description and Priority

The Home Page is the primary entry point to the cybersecurity website. It introduces users to the
site's purpose and provides easy navigation to other sections. The priority of this feature is High due
to its critical role in user engagement and navigation.

• Benefit: 9
• Penalty: 8
• Cost: 5
• Risk: 4

3.1.2 Stimulus/Response Sequences

• User Action: The user enters the website's URL in a browser.
o System Response: The system loads the Home Page, displaying the website title, tagline,
navigation menu, and featured content.
• User Action: The user clicks on a menu item (e.g., "Threat Identification").
o System Response: The system redirects the user to the selected section.

3.1.3 Functional Requirements

• REQ-1: The Home Page must load within 3 seconds on a standard broadband connection.
• REQ-2: The navigation menu on the Home Page must provide links to all primary sections, including
Threat Identification, Protection Measures, Best Practices, and Resources.
• REQ-3: The Home Page must include a search bar to allow users to search content across the site.
• REQ-4: The Home Page must be fully responsive, ensuring optimal display on various devices
(desktop, tablet, mobile).
• REQ-5: The system must display featured content, such as recent articles or alerts, prominently on the
Home Page.

3.2 Threat Identification

 Government College University Faisalabad Page 18
3.2.1 Description and Priority

The Threat Identification section categorizes and provides detailed information about various
cybersecurity threats. The priority is High because it is a core component of the educational purpose
of the website.

• Benefit: 9
• Penalty: 8
• Cost: 6
• Risk: 3

3.2.2 Stimulus/Response Sequences

• User Action: The user selects a specific threat category (e.g., Phishing) from the list.
o System Response: The system displays detailed information about the selected threat,
including its definition, impact, and examples.
• User Action: The user clicks on "Learn More" to access a detailed analysis of the threat.
o System Response: The system navigates to a page with in-depth information and related
resources.

3.2.3 Functional Requirements

• REQ-6: The system must categorize threats by type (e.g., Malware, Phishing, Ransomware).
• REQ-7: Each threat category must include a description and a link to a dedicated page with more
details.
• REQ-8: The Threat Identification section must allow filtering by threat type and severity.
• REQ-9: The system must include a "Recent Threats" feature highlighting emerging cybersecurity
threats.

3.3 Protection Measures

3.3.1 Description and Priority

The Protection Measures section offers guidelines and tools for preventing cybersecurity threats.
This feature is of Medium priority, as it provides practical resources for users to implement security
measures.

• Benefit: 8
• Penalty: 7
• Cost: 5
• Risk: 4

3.3.2 Stimulus/Response Sequences

• User Action: The user selects a protection measure (e.g., Password Management).
o System Response: The system provides a step-by-step guide on how to implement the
selected protection measure.
• User Action: The user downloads a recommended tool from the section.
o System Response: The system initiates the download and displays a confirmation message.

3.3.3 Functional Requirements

 Government College University Faisalabad Page 19
• REQ-10: The Protection Measures section must include a list of common security practices (e.g.,
encryption, firewalls).
• REQ-11: Each practice must have a detailed guide and links to relevant tools or software.
• REQ-12: The section must support downloadable resources in commonly used formats (e.g., PDF).
• REQ-13: The system must provide interactive elements, such as quizzes, to help users assess their
understanding of security measures.

3.4 Best Practices

3.4.1 Description and Priority

The Best Practices section outlines recommended actions to maintain cybersecurity. This feature is
of Medium priority, focusing on reinforcing good habits and protocols.

• Benefit: 7
• Penalty: 6
• Cost: 4
• Risk: 3

3.4.2 Stimulus/Response Sequences

• User Action: The user clicks on a best practice item (e.g., "Regular Software Updates").
o System Response: The system displays information on the importance of the practice and tips
for implementation.

3.4.3 Functional Requirements

• REQ-14: The system must list best practices for both individual users and organizations.
• REQ-15: Each practice must include an explanation of its importance and a guide on implementation.
• REQ-16: The section must feature case studies that demonstrate successful implementation of best
practices.
• REQ-17: The Best Practices section must be regularly updated with new recommendations based on
emerging trends.

3.5 Resources
3.5.1 Description and Priority

The Resources section offers external links, downloadable materials, and a glossary of terms. This
feature is of Low priority but adds value by expanding the scope of the site's educational content.

• Benefit: 5
• Penalty: 4
• Cost: 3
• Risk: 2

3.5.2 Stimulus/Response Sequences

• User Action: The user clicks on an external link in the Resources section.
• System Response: The system opens the link in a new browser tab.
• User Action: The user searches for a term in the glossary.
o System Response: The system displays the term's definition and related resources.
 Government College University Faisalabad Page 20
3.5.3 Functional Requirements
• REQ-18: The Resources section must include a list of external links to authoritative cybersecurity
resources.
• REQ-19: The section must support downloadable content, such as whitepapers and study guides.
• REQ-20: The system must feature a glossary of common cybersecurity terms with search functionality.
• REQ-21: External links must open in a new browser tab to ensure users remain on the website.

4. External Interface Requirements

4.1 User Interfaces

This section outlines the logical characteristics of the user interfaces for the cybersecurity website. It
includes descriptions of the interface elements, layout guidelines, and standards that will be followed
to ensure a consistent and user-friendly experience.

4.1.1 General User Interface Characteristics

• Consistency: The user interface (UI) will maintain a consistent look and feel across all pages,
adhering to a unified style guide that includes font choices, color schemes, button styles, and
iconography.
• Responsiveness: The UI will be fully responsive, adapting seamlessly to different screen sizes and
orientations, including desktop, tablet, and mobile devices.
• Accessibility: The UI will follow accessibility guidelines (e.g., WCAG 2.1) to ensure that all users,
including those with disabilities, can easily navigate and interact with the website.

4.1.2 Screen Layout and Navigation

• Header: The website will have a fixed header that includes the logo, main navigation menu, and a
search bar. The header will remain consistent across all pages and will shrink or expand based on the
screen size.
• Navigation Menu: The main navigation menu will be positioned at the top of the screen and will use a
dropdown format for sub-menu items. On mobile devices, the menu will collapse into a hamburger icon
that expands into a vertical menu when clicked.
• Footer: The footer will contain links to important pages (e.g., Privacy Policy, Contact Us) and social
media icons. It will also include a newsletter signup form and site credits.

4.1.3 Standard Elements

• Buttons: Standard buttons will have a consistent style, with primary action buttons highlighted using a
distinct color. Buttons will have hover effects and appropriate padding to enhance usability.
• Forms: Input fields, such as text boxes and dropdowns, will follow a consistent design, with clear
labels, placeholders, and error messages. Required fields will be marked with an asterisk (*).
• Error Messages: Error messages will be displayed near the relevant form field or at the top of the
page. They will use a red color to draw attention and will be phrased in clear, concise language to
guide the user in correcting the issue.
• Modals: Pop-up modals will be used sparingly for important actions, such as confirmations or alerts.
They will include a close button and a clear call-to-action.
 Government College University Faisalabad Page 21
• Tooltips: Tooltips will be used to provide additional information or clarification on specific UI elements.
They will appear on hover or focus and will disappear when the user moves away from the element.

4.1.4 Sample User Interfaces

• Homepage: The homepage will feature a hero section with a large background image or video,
overlaid with a brief introduction and a call-to-action button. Below this, key sections will be displayed,
such as recent articles, featured services, and testimonials.
• Dashboard: For logged-in users, the dashboard will present a summary of their activities, notifications,
and quick links to common actions. It will include a sidebar menu for easy navigation to different
sections of the user account.
• Article Page: The article pages will be designed with a clean layout, featuring a prominent title, author
information, publication date, and the content itself. The right sidebar may contain related articles,
social sharing buttons, and a comment section.

4.1.5 Keyboard Shortcuts

• Global Shortcuts: Users will be able to navigate the website using keyboard shortcuts. For example,
pressing "Ctrl + F" will focus the search bar, and "Esc" will close any open modal.
• Form Navigation: In forms, users will be able to navigate between fields using the "Tab" key, and
submit the form using the "Enter" key when focused on a submit button.

4.1.6 User Interface Specification

• Documentation: Detailed designs and specifications for each user interface component will be
documented in a separate User Interface Specification document. This will include wireframes,
mockups, and descriptions of interaction patterns.

4.2 Hardware Interfaces

This section describes the logical and physical characteristics of the interfaces between the
cybersecurity website and the hardware components of the system. Since the website is built with
HTML, CSS, and JavaScript and does not involve backend systems or specialized hardware, this
section will focus on the interaction with standard user devices.

4.2.1 Supported Device Types

• Desktops and Laptops:

o Characteristics: Devices with various screen sizes, ranging from 1366 x 768 pixels to 3840 x
2160 pixels or higher. These devices typically use a mouse and keyboard for input.
o Interaction: The website will adapt its layout based on the screen resolution and aspect ratio to
ensure a consistent user experience across different devices.
• Tablets:
o Characteristics: Devices with screen sizes ranging from 7 inches to 12.9 inches, with
resolutions from 800 x 1280 pixels to 2732 x 2048 pixels. Tablets may use touch input as well
as a virtual keyboard.
o Interaction: The website will support touch gestures and provide a responsive layout to
accommodate the varying screen sizes.
• Mobile Phones:
o Characteristics: Devices with screen sizes ranging from 4.7 inches to 6.7 inches and
resolutions from 750 x 1334 pixels to 1440 x 3200 pixels. Mobile phones primarily use touch
input.
 Government College University Faisalabad Page 22
o Interaction: The website will include touch-friendly elements, such as larger buttons and
swipeable content, and will adapt its layout for smaller screens.

4.2.2 Nature of Data and Control Interactions

• Data Input:
o Interaction: Users will interact with the website through standard input devices such as
keyboards, mice, and touchscreens. Form inputs, search queries, and navigation actions will be
handled through standard HTML form elements and JavaScript event handlers.
o Data Handling: All user inputs will be processed on the client side. Data validation and user
feedback will be managed using JavaScript.
• Display Output:
o Interaction: The website will render content to the user’s screen using standard web
technologies (HTML, CSS). Display output will include text, images, videos, and interactive
elements.
o Rendering: CSS media queries and responsive design techniques will ensure that the website
displays correctly across various device sizes and orientations.

4.2.3 Communication Protocols

• HTTP/HTTPS:
o Protocol: The website will use HTTP or HTTPS protocols for communication between the
user's browser and the web server. HTTPS is required to ensure secure data transmission.
o Function: These protocols handle the requests and responses between the client and server,
ensuring that content is delivered securely and efficiently.

4.2.4 Interaction with Peripheral Devices

• Printers:
o Characteristics: Users may need to print content from the website.
o Interaction: The website will include standard print-friendly styles and functionality to ensure
that printed content is formatted correctly.
• Scanners:
o Characteristics: While not directly interfacing with the website, users might scan documents or
images for use with the website.
o Interaction: Users will need to upload scanned documents or images through standard file
input fields on the website.

4.3 Software Interfaces

This section describes the connections between the cybersecurity website and other software
components, considering that the project only involves HTML, CSS, and JavaScript without any
external libraries or frameworks.

4.3.1 External Libraries and Frameworks

• None:
o Purpose: The project does not use any external libraries or frameworks. All functionality and
design are implemented using plain HTML, CSS, and JavaScript.

4.3.2 Integrated Commercial Components

 Government College University Faisalabad Page 23
• None:
o Purpose: No commercial components are integrated into the project. All styling and
functionality are handled within the scope of HTML, CSS, and JavaScript.

4.3.3 Data Items and Messages

• Input Data:
o Purpose: Includes user inputs from forms, search fields, and other interactive elements.
o Data Flow: Data is handled entirely on the client side. JavaScript processes user inputs to
provide feedback or update the interface without server-side communication.
• Output Data:
o Purpose: Includes content dynamically generated or updated based on user interactions.
o Data Flow: Content is rendered and updated in the browser using JavaScript to manipulate the
DOM directly.

4.3.4 Services and Communications

• Form Handling:
o Purpose: Manages user input from forms, including validation and feedback.
o Data Flow: Handled with plain JavaScript. Validation and user feedback occur on the client
side without server-side interactions.
• Error Handling:
o Purpose: Manages and displays error messages related to user inputs or interactions.
o Data Flow: Errors are captured and displayed using JavaScript directly in the user interface.

4.3.5 Data Sharing Mechanisms

• Client-Side Storage:
o Purpose: Stores user preferences or temporary data in the browser.
o Data Flow: Uses browser storage mechanisms such as localStorage or sessionStorage to
maintain state across page reloads or sessions.
• Global Variables:
o Purpose: Shares data or maintains state across different scripts or components within the
page.
o Data Flow: Variables are defined in the global scope and accessed by JavaScript functions to
ensure consistent data availability.

4.3.6 API Protocols and Documentation

• No External APIs:
o Reference: Since the project does not utilize external APIs or AJAX requests, no API
documentation is required.

4.4 Communications Interfaces

This section outlines the communication requirements for the cybersecurity website, given that it is
developed using only HTML, CSS, and JavaScript. This will focus on the web-based interactions and
protocols used in the absence of backend services.

4.4.1 Communication Functions

• Web Browser Interaction:

 Government College University Faisalabad Page 24
o Purpose: The website will be accessed through standard web browsers. All communication
between the user and the website occurs through HTTP/HTTPS protocols.
o Standards: The website must adhere to web standards such as HTML5 and CSS3 for proper
rendering and functionality across different browsers.
• Form Submissions:
o Purpose: Handles user input via forms, including data entry and submission.
o Standards: Forms will use HTML form elements. Any data validation and handling will be
managed on the client side using JavaScript.

4.4.2 Communication Protocols

• HTTP/HTTPS:
o Purpose: The website communicates using standard HTTP or HTTPS protocols for secure
data transfer. HTTPS is recommended to ensure data security and privacy.
o Details: Ensures secure communication between the user's browser and the website.

4.4.3 Message Formatting

• Form Data:
o Format: Data entered into forms will be collected and formatted in a manner that is consistent
with HTML form submission standards.
o Details: When submitting forms, data is formatted according to standard URL-encoded or
multipart form-data formats.
• Error Messages:
o Format: Errors and validation messages will be displayed directly on the web page using
JavaScript. They will be formatted in plain text or styled using CSS.

4.4.4 Communication Standards

• HTTP/HTTPS Protocols:
o Standards: Conforms to standard HTTP/HTTPS communication protocols for data transfer and
secure transactions.
• Data Transfer Rates:
o Considerations: Since the website operates in a browser environment, performance should be
optimized for minimal data transfer rates and fast load times. Efficient use of JavaScript and
CSS will help maintain performance.
• Encryption and Security:
o Purpose: To ensure the security of data transmitted between the user’s browser and the
website.
o Standards: HTTPS should be used to encrypt data during transmission, protecting it from
interception and tampering.
• Synchronization Mechanisms:
o Considerations: For static websites without backend interaction, synchronization is not
applicable. However, JavaScript can be used to manage client-side state and interactions
dynamically.
 Government College University Faisalabad Page 25

5. Other Nonfunctional Requirements

5.1 Performance Requirements

This section outlines the performance requirements for the cybersecurity website, focusing on the efficiency
and responsiveness of the site when using HTML, CSS, and JavaScript.
5.1.1 General Performance Requirements
• Page Load Time:
o Requirement: The website should load within 3 seconds on a standard broadband connection.
o Rationale: Ensures a good user experience by minimizing wait times and reducing bounce
rates.
• Responsiveness:
o Requirement: The website should be fully responsive and functional across all modern devices
and screen sizes, including desktops, tablets, and smartphones.
o Rationale: Provides a seamless experience for users accessing the website from various
devices.
5.1.2 JavaScript Execution
• Interactivity:
o Requirement: JavaScript functions should execute within 100 milliseconds for user
interactions, such as button clicks or form submissions.
o Rationale: Ensures that interactive elements respond quickly, maintaining a smooth user
experience.
• DOM Manipulation:
o Requirement: Changes to the Document Object Model (DOM) should be performed efficiently
to avoid slowdowns, especially for pages with complex layouts or large amounts of data.
o Rationale: Efficient DOM manipulation ensures that the page remains responsive even with
frequent updates.
5.1.3 Form Handling
• Validation:
o Requirement: Client-side form validation should be completed within 200 milliseconds to
provide immediate feedback to users.
o Rationale: Quick validation improves user experience by promptly identifying errors and
reducing the need for server-side validation.
5.1.4 User Interface Rendering
• CSS Rendering:
o Requirement: CSS styles should be applied and rendered without noticeable delay, with style
changes appearing instantaneously.
o Rationale: Ensures that visual updates and animations are smooth and do not impact the user
experience.
 Government College University Faisalabad Page 26
• Animation and Transitions:

o Requirement: Animations and transitions should run at 60 frames per second (FPS) to appear
smooth and fluid.
o Rationale: Maintains high visual quality and user satisfaction by providing smooth visual
effects.
5.1.5 Error Handling and Feedback
• Error Display:
o Requirement: Error messages should be displayed within 200 milliseconds of an error
occurring.
o Rationale: Provides users with prompt feedback to correct issues without significant delay.
• Loading Indicators:
o Requirement: Loading indicators should appear immediately when an operation is in progress
and disappear once the operation completes.
o Rationale: Informs users that an action is being processed, improving overall user experience
and reducing uncertainty.
5.1.6 Data Handling
• Client-Side Storage Access:
o Requirement: Access and manipulation of client-side storage (e.g., localStorage or
sessionStorage) should occur without noticeable delay.
o Rationale: Ensures that data operations do not impact user interactions or performance.

5.2 Safety Requirements

<Specify those requirements that are concerned with possible loss, damage, or harm that could
result from the use of the product. Define any safeguards or actions that must be taken, as well as
actions that must be prevented. Refer to any external policies or regulations that state safety
issues that affect the product’s design or use. Define any safety certifications that must be
satisfied.>

5.3 Security Requirements

This section details the security and privacy requirements for the cybersecurity website, focusing on the
protection of data, user identity, and adherence to relevant policies and regulations, given the use of HTML,
CSS, and JavaScript.
5.3.1 Data Protection
• Data Encryption:
o Requirement: Ensure that all data transmitted between the user’s browser and the website is
encrypted using HTTPS.
o Rationale: Encryption protects data in transit from eavesdropping and tampering, maintaining
user confidentiality and integrity.
• Client-Side Storage Security:
o Requirement: Implement secure practices for handling client-side storage (e.g., localStorage
and sessionStorage), ensuring sensitive data is not stored in an insecure manner.
 Government College University Faisalabad Page 27
o Rationale: Prevents unauthorized access to stored data and mitigates the risk of data leakage.

• Data Handling:
o Requirement: Avoid storing sensitive user information directly in client-side storage. Use
secure tokens or identifiers for session management if needed.
o Rationale: Reduces the risk of exposing sensitive data through browser storage mechanisms.
5.3.2 User Authentication
• Authentication:
o Requirement: If user authentication is required, implement secure client-side mechanisms for
user login and session management, such as using secure tokens or cookies with the HttpOnly
and Secure flags.
o Rationale: Ensures that user authentication processes are handled securely and reduces the
risk of session hijacking.
• User Privacy:
o Requirement: Do not collect or store unnecessary personal data from users. Provide clear
information on data collection and usage practices in a privacy policy.
o Rationale: Protects user privacy and complies with data protection regulations by minimizing
the amount of personal data collected and stored.
5.3.3 External Policies and Regulations
• Compliance:
o Requirement: Adhere to relevant data protection regulations, such as the General Data
Protection Regulation (GDPR) or the California Consumer Privacy Act (CCPA), where
applicable.
o Rationale: Ensures that the website complies with legal requirements for data protection and
privacy, reducing the risk of legal issues.
• Security Standards:
o Requirement: Follow industry best practices for web security, including OWASP
recommendations for securing web applications.
o Rationale: Aligns with established security standards to safeguard against common web
vulnerabilities and threats.
5.3.4 Security and Privacy Certifications
• Certification:
o Requirement: If applicable, obtain relevant security or privacy certifications, such as ISO/IEC
27001 for information security management.
o Rationale: Demonstrates a commitment to security and privacy best practices and enhances
trust with users and stakeholders.
5.3.5 Incident Response
• Incident Handling:
o Requirement: Establish procedures for responding to security incidents, including detecting,
reporting, and mitigating breaches.
o Rationale: Ensures prompt and effective action in case of a security incident, minimizing
potential damage and maintaining user trust.
 Government College University Faisalabad Page 28

5.4 Software Quality Attributes

This section specifies the quality attributes for the cybersecurity website, focusing on characteristics that are
important for both customers and developers. These attributes help ensure that the product meets user
expectations and remains maintainable and effective over time.
5.4.1 Usability
• Ease of Use:
o Requirement: The website should be intuitive and easy to navigate, with a user satisfaction
rating of at least 85% based on user surveys.
o Rationale: Ensures a positive user experience, making it easier for users to interact with the
website effectively.
• Accessibility:
o Requirement: The website should comply with Web Content Accessibility Guidelines (WCAG)
2.1 Level AA to ensure accessibility for users with disabilities.
o Rationale: Ensures that the website is usable by a broad range of people, including those with
disabilities, enhancing inclusivity.
5.4.2 Reliability
• Availability:
o Requirement: The website should achieve 99.9% uptime, excluding scheduled maintenance
periods.
o Rationale: Ensures that the website is consistently available for users, minimizing downtime
and disruptions.
• Error Handling:
o Requirement: The website should gracefully handle errors, providing meaningful error
messages and recovery options without crashing.
o Rationale: Maintains a smooth user experience even when errors occur, preventing frustration
and improving overall reliability.
5.4.3 Performance
• Load Time:
o Requirement: The website should load within 3 seconds under standard conditions and
maintain responsiveness during peak usage.
o Rationale: Ensures a fast and efficient user experience, which is critical for user satisfaction
and retention.
• JavaScript Execution:
o Requirement: JavaScript functions should execute within 100 milliseconds to provide
immediate feedback to user interactions.
o Rationale: Ensures that interactive elements respond quickly, maintaining a smooth and
engaging user experience.
5.4.4 Maintainability
• Code Readability:
o Requirement: Code should be well-documented and follow consistent coding conventions,
making it easy for developers to understand and modify.
o Rationale: Facilitates future maintenance and updates by ensuring that the codebase is clear
and manageable.
• Modularity:
o Requirement: The website should be designed with modular components, allowing for easy
updates and changes to individual parts without affecting the entire system.
o Rationale: Enhances the ability to make modifications and improvements without extensive
rework.
5.4.5 Flexibility
• Adaptability:
o Requirement: The website should be adaptable to different screen sizes and orientations, with
a responsive design that adjusts layout and content appropriately.
o Rationale: Ensures that the website remains functional and visually appealing across various
devices and screen sizes.
• Customizability:
o Requirement: Allow for basic customization of visual elements (e.g., themes, colors) without
requiring code changes.
o Rationale: Provides users or administrators with the ability to tailor the website’s appearance to
their preferences or organizational branding.
 Government College University Faisalabad Page 29
5.4.6 Testability
• Automated Testing:
o Requirement: Implement automated tests for key functionalities, such as form validation and
user interactions, to ensure consistent performance and catch regressions.
o Rationale: Enhances the reliability of the website by catching issues early and ensuring that
changes do not introduce new bugs.
• Manual Testing:
o Requirement: Conduct thorough manual testing across different browsers and devices to verify
that the website functions as expected in various environments.
o Rationale: Ensures comprehensive coverage of different use cases and configurations,
validating the overall quality of the website.
5.4.7 Security
• Robustness:
o Requirement: Implement security best practices to protect against common vulnerabilities,
such as cross-site scripting (XSS) and cross-site request forgery (CSRF).
o Rationale: Enhances the security and robustness of the website, protecting user data and
maintaining trust.
• Compliance:
o Requirement: Adhere to relevant security standards and regulations, such as GDPR or CCPA,
as applicable.
o Rationale: Ensures that the website complies with legal requirements for data protection and
privacy.

6. WBS Project Management

 Government College University Faisalabad Page 30

7. Analysis model

7.1 Use Case Diagram

7.2 Class Diagram

 Government College University Faisalabad Page 31
7.3 Object Diagram

7.4 Sequence Diagram

 Government College University Faisalabad Page 32

7.4 Activity Diagram

7.5 Collaboration Diagram

 Government College University Faisalabad Page 33

7.5 State Transition Diagram

7.7 ERD
 Government College University Faisalabad Page 34
8. Tools & Technologies

8.1 Programming Languages

Overview: For the cybersecurity website project, the primary programming languages used are
HTML, CSS, and JavaScript. Each of these languages plays a crucial role in the development of the
front-end of the website.

HTML (HyperText Markup Language)

• Purpose:
o Structure: HTML provides the fundamental structure of the website. It defines the content and
layout of web pages using elements and tags.
o Content: It includes text, images, links, forms, and other content that users interact with.
• Key Features:
o Elements and Tags: Defines the building blocks of the web page (e.g., <header>, <nav>,
<section>, <footer>).
o Attributes: Provides additional information about elements (e.g., id, class, src, href).
o Semantic HTML: Uses elements that convey meaning (e.g., <article>, <aside>, <main>).

CSS (Cascading Style Sheets)

• Purpose:
o Styling: CSS is used to control the visual appearance of the HTML elements. It allows for
customization of colors, fonts, layouts, and overall design.
o Layout and Design: Manages layout techniques like flexbox and grid, positioning, and
responsive design.
• Key Features:
o Selectors: Targets specific HTML elements to apply styles (e.g., class selectors .classname, ID
selectors #idname).
o Properties and Values: Defines styles such as color, font-size, margin, padding, and border.
o Responsive Design: Uses media queries to adapt the layout to different screen sizes and
devices.

JavaScript

• Purpose:
o Interactivity: JavaScript adds interactivity and dynamic functionality to the website. It enables
user interactions, animations, and data manipulation.
o Client-Side Scripting: Runs in the user's browser to provide a responsive and interactive
experience.
• Key Features:
o DOM Manipulation: Allows for dynamic changes to the content and structure of the web page
(e.g., adding, removing, or updating elements).
o Event Handling: Responds to user actions such as clicks, form submissions, and keyboard
inputs.
o AJAX: Facilitates asynchronous data loading and interaction with server-side resources without
refreshing the page.

Integration:

• HTML: Defines the structure and content of the website.

• CSS: Styles the content and layout defined by HTML.
 Government College University Faisalabad Page 35
• JavaScript: Adds interactivity and dynamic functionality to the styled content.

8.2 Operating System

Overview: The operating system used for developing and hosting the cybersecurity website will
influence the development environment, tools, and deployment process. Since the project is focused
on front-end development with HTML, CSS, and JavaScript, the operating system choice will impact
the development workflow, compatibility with development tools, and hosting options.

Commonly Used Operating Systems:

1. Windows
o Development:
▪ Supports a wide range of development tools and IDEs (e.g., Visual Studio Code,
Sublime Text, and Adobe Creative Suite).
▪ Compatible with local server environments (e.g., XAMPP, WAMP) for testing
web pages.
o Deployment:
▪ Websites can be hosted on IIS (Internet Information Services) or third-party
hosting services.
o Advantages:
▪ Broad support for various software and tools.
▪ User-friendly interface with extensive community and technical support.
2. macOS
o Development:
▪ Preferred by many developers for its Unix-based environment, which is
conducive to web development.
▪ Tools such as Visual Studio Code, Atom, and Sketch are popular.
▪ Local server environments like MAMP are available for testing.
o Deployment:
▪ Websites can be hosted on macOS servers or third-party hosting services.
o Advantages:
▪ Unix-based system provides a robust development environment.
▪ Good compatibility with modern web development tools.
3. Linux
o Development:
▪ Popular among developers for its open-source nature and powerful command-
line tools.
▪ Tools like Visual Studio Code, Atom, and GIMP are widely used.
▪ Local server environments (e.g., LAMP stack) are commonly used for
development and testing.
o Deployment:
▪ Ideal for hosting on various Linux-based web servers (e.g., Apache, Nginx).
o Advantages:
▪ High level of customization and control.
▪ Strong support for web technologies and server-side scripting.

Choosing the Operating System:

• Development Environment:
o The choice of OS may depend on the developer’s familiarity and comfort level with the
operating system.
 Government College University Faisalabad Page 36
o Each OS provides tools and environments suitable for front-end development with
HTML, CSS, and JavaScript.
• Testing and Deployment:
o The OS used for development should be compatible with the chosen hosting
environment for a smooth transition from local development to production.
• Recommendations:
o Windows: Ideal for developers who prefer a GUI-based environment with a broad
range of tools.
o macOS: Suitable for developers who prefer a Unix-based system with modern
development tools.
o Linux: Best for developers who want a high degree of control and customization,
particularly for server-side testing and deployment.

Appendix A: Glossary
This glossary defines key terms, acronyms, and abbreviations used in the Software Requirements
Specification (SRS) for the cybersecurity website project. It aims to ensure clarity and consistency in
the interpretation of the document.

Terms:

1. Cybersecurity:
o Definition: The practice of protecting systems, networks, and data from digital attacks,
unauthorized access, and damage.
2. HTML (HyperText Markup Language):
o Definition: A standard markup language used to create and structure content on the web. It
defines elements such as headings, paragraphs, links, and images.
3. CSS (Cascading Style Sheets):
o Definition: A style sheet language used to describe the presentation of a document written in
HTML or XML. It controls the layout, colors, fonts, and other visual aspects of web pages.
4. JavaScript:
o Definition: A high-level, interpreted programming language used to create interactive and
dynamic content on web pages. It allows for manipulation of HTML and CSS, handling events,
and performing asynchronous operations.
5. Front-End Development:
o Definition: The part of web development focused on the user interface and user experience of
a website. It involves the use of HTML, CSS, and JavaScript to build the visual and interactive
aspects of a website.
6. User Interface (UI):
o Definition: The visual part of a website or application that users interact with. It includes
elements such as buttons, forms, and navigation menus.
7. User Experience (UX):
o Definition: The overall experience and satisfaction a user has when interacting with a website
or application. It encompasses usability, accessibility, and the design of the user interface.
8. Responsive Design:
o Definition: An approach to web design that ensures a website's layout and content adapt to
different screen sizes and devices, providing an optimal viewing experience.
9. DOM (Document Object Model):
o Definition: A programming interface for web documents that represents the structure of a
document as a tree of objects. JavaScript can interact with and manipulate the DOM to change
the content and structure of a web page.
10. Web Application:
 Government College University Faisalabad Page 37
o Definition: A software application that runs on a web server and can be accessed through a
web browser. It typically involves client-side (front-end) and server-side (back-end)
components.
11. Security Threat:
o Definition: An occurrence or potential occurrence that could exploit vulnerabilities to
compromise the integrity, confidentiality, or availability of information or systems.
12. Protection Measure:
o Definition: Strategies and tools implemented to mitigate security risks and protect systems and
data from potential threats.
13. Best Practices:
o Definition: Recommended guidelines and methods that are widely accepted as effective in
improving security, performance, and overall quality.
14. Resources Section:
o Definition: A section of the website that provides additional tools, references, and links related
to cybersecurity for further learning and exploration.

Acronyms and Abbreviations:

• HTML: HyperText Markup Language

• CSS: Cascading Style Sheets
• JavaScript: JavaScript (No acronym)
• AJAX: Asynchronous JavaScript and XML
• DOM: Document Object Model
• UI: User Interface
• UX: User Experience

Appendix B: Check List

Check List Yes No
I. Starting/Ending Dates ✅

II. Project Scope ✅

III. Product modules (covering all aspects of scope) ✅

IV. System Features (covering scope) ✅

V. Interface Requirements ✅

VI. Non-Functional Requirements ✅

VII. WBS ✅

VIII. Tools and Technologies Detail (for implementation) ✅

IX. Plagiarism Report ✅

Government College University Faisalabad Page 38

Appendix C: Supervisory Committee

For Approval of any two Consultant Teachers

Teacher Consulted Teacher Consulted

Name: _ _. Name: _ _.

Designation: _ . Designation: _ .

Comments:_ Comments:_

_ _

_ _

_ _

_ _

Signature: _ Signature: _

---------------------------------------------------------------------
Government College University Faisalabad Page 39

(For office use only)

Date:

□ Approved Group ID:

□ Meeting Required: Date: Time: Place:

□ Rejected

Remarks:

Project Title (if Revised):

Project Coordinator