Skip to main content

Chapter 2: Requirement Analysis

Chapter 2: Requirement Analysis


2.1 Functional Requirements

Functional requirements define the core functionality of a system. They describe what the application is supposed to accomplish, including data and functional process requirements. A function is described as a set of inputs, behavior, and outputs. These requirements may include calculations, technical details, data processing, and other specific operations. Behavioral requirements, describing all the cases where the system uses these functions, are captured in use cases.

Stakeholders

Online users are the main stakeholders.

Actors and Goals

1) Actor: User ðŸ‘¤

  • Description: A person who visits the website.

  • Goals: Create an account, add friends, post texts, comment on posts, send messages, and search for friends.



2) Actor: Admin ðŸ‘¤

  • Description: The website administrator who manages the platform.

  • Goals: Add, update, and make changes to the website.

2.2 Use Case Diagram

The Use Case Diagram (Figure 2.1) shows the set of use cases, actors, and their relationships. Use case diagrams illustrate the static view of a system and are especially important for modeling its behavior.


Figure 2.1 Use Case Diagram
Figure 2.1 Use Case Diagram

2.3 Operational and Non-Functional Requirements

The system is designed to be highly scalable and manageable. From user creation to posting, commenting, liking, groups, and pages, the platform provides sufficient rights for users to interact freely. The system is deployable on government-purchased servers, allowing easy upgrades and maintenance.

2.3.1 Security Requirements

Security is a primary focus. Features like signup, sign-in, and email verification are designed to prevent:

  • Account hijacking

  • SQL injections

  • Identity theft

  • Session hijacking

Separate databases are used for sensitive groups of features, and hosting on a dedicated governmental server ensures maximum security.

2.3.2 Installation/Setup Requirements

The deployment team will work directly with server administrators. Databases will be installed first, domain names and disk space allocated, and the solution hosted to communicate with the underlying databases.

2.3.3 Legal Requirements

Legal compliance will be ensured through privacy policies, terms and conditions, and copyright documentation.

2.3.4 Scalability for Business Needs

Professional Hub provides organizations with a pool of professionals from KPK, saving time in recruitment and advertising. It also offers potential advertising revenue. Future versions will maintain backward compatibility for a smooth user experience.

2.4 System Requirements Specification

This section outlines the system requirements, dependencies, and infrastructure for Professional Hub.

2.4.1 Systems and Services Dependencies

  • The platform will be hosted on external servers for 24/7 availability, with the ability to increase the number of servers as needed.

  • Hardware: Windows Server 2008 R2 with IIS services, 64-bit Intel Nehalem processors (4 or 8 cores), and 256GB–512GB RAM, linked in clusters.

  • Network: Force10 Network E-Series switches capable of handling up to 5 TBps backplane with multiple gigabit and 10-gigabit connections.

  • Storage: Data, including notes, photos, and videos, will be stored on multiple vendor storage servers, measured in terabytes and petabytes.

  • Database: MS SQL Server R2.

  • Other Requirements: Unlimited bandwidth and FTP utility.

By meeting these functional and system requirements, Professional Hub ensures a secure, scalable, and efficient platform for professionals in KPK to connect and grow their network.

Comments