Internship – Low Level Design

On

EMPLOYEE TRAINING EFFECTIVENESS

Team members:

SUNIL KUMAR SHARMA (220025)

ASHISH MEHLAWAT (220026)

PARAMJEET (220027)

GUIDED BY:

Mr. STEPHEN SMITH

Industry Mentor:

Mr. STEPHEN SMITH

1.1 Scope of the Document

The scope of this document is to provide a detailed understanding of the low-level design aspects of the
employee training effectiveness project. It focuses on various components including system architecture,
data design, validation mechanisms, and integration with external components. Specifically, it delves into
the intricate details of how each aspect of the system is designed to function at a granular level. By outlining
the low-level design, this document aims to offer developers, architects, and stakeholders a comprehensive
view of the internal workings of the system. This understanding is crucial for ensuring that the system is
developed and implemented effectively, meeting the intended requirements and objectives of the project.

1.2 Intended Audience

This document is intended for a specific audience comprising developers, architects, and stakeholders
directly involved in the implementation and evaluation of the employee training effectiveness project.
Developers will use this document as a reference to understand the detailed design specifications and
requirements for building the system. Architects will rely on it to ensure that the proposed design aligns with
the overall project goals and follows best practices. Stakeholders, including project managers and decision-
makers, will use this document to gain insights into the technical aspects of the project and make informed
decisions regarding resource allocation and project direction. Overall, the intended audience of this
document is individuals who require a deep understanding of the technical intricacies of the system.

1.3 System Overview

The system overview section provides a high-level description of the employee training effectiveness
project. It outlines the objectives of the project, which may include enhancing organizational performance,
improving employee skills, and fostering a culture of continuous learning. Additionally, this section
highlights the key features of the system, such as training delivery, data collection, analysis, and reporting.
Moreover, it introduces the technologies and tools utilized in the development of the system, providing an
overview of the technical stack. By offering this high-level perspective, the system overview sets the stage
for understanding the detailed design considerations discussed in subsequent sections of the document.
2. Low Level System Design

1.1 Sequence Diagram

Sequence diagrams serve as visual representations of the interactions between different system components
and actors during various scenarios. For instance, during user registration, the sequence diagram would
illustrate the steps involved, such as user input, validation, database update, and confirmation message
display. Similarly, sequence diagrams for training content delivery and feedback submission would depict
the flow of events from user interaction to system response.

1.2 Navigation Flow/UI Implementation

The navigation flow and UI implementation section outline the design of the user interface and the sequence
of screens, menus, and actions available to users. It details the layout of screens, placement of buttons and
menus, and the flow of navigation between different sections of the application. This ensures a user-friendly
and intuitive experience for users interacting with the system.

1.3 Screen Validations, Defaults, and Attributes

This section describes the rules and constraints applied to user inputs on different screens to ensure data
integrity and consistency. It specifies the validation criteria for each input field, default values set for certain
fields, and attributes associated with screen elements such as data types, field lengths, and visibility settings.

1.4 Client-Side Validation Implementation

Client-side validation is implemented using JavaScript or similar technologies to validate user inputs before
sending them to the server. This helps in enhancing user experience by providing immediate feedback to
users and reducing unnecessary server requests. The implementation details of client-side validation
mechanisms are discussed in this section.

1.5 Server-Side Validation Implementation

Server-side validation mechanisms are employed to validate user inputs and ensure data consistency and
security before processing requests. This section discusses the implementation details of server-side
validation, including the use of server-side scripting languages such as PHP, Python, or Java, and the
validation rules applied at the server-side.
1.6 Components Design Implementation

This section provides a breakdown of the system components and their interactions. It includes modules for
data management, user authentication, training delivery, and reporting. The design and implementation
details of each component, including their interfaces and dependencies, are discussed in this section.

1.7 Configurations/Settings

System configurations and settings required for optimal performance are specified in this section. This
includes database connection settings, security configurations, and system parameters such as cache size,
session timeout, etc. Proper configuration ensures the smooth functioning of the system.

1.8 Interfaces to Other Components

Integration points with external components such as Learning Management Systems (LMS), database
systems, analytics tools, and reporting frameworks are described in this section. It outlines the interfaces,
protocols, and data exchange mechanisms used for communication with external components, ensuring
seamless integration and interoperability.
3. Data Design

1.1 List of Key Schemas/Tables in Database

This section provides a detailed list of database schemas and tables utilized within the system. For example:
User Information Table, Training Data Table, Feedback Table. Each table's structure, relationships, and
attributes are defined to ensure effective data storage and retrieval.

1.2 Details of Access Levels on Key Tables in Scope

Access control mechanisms are crucial for maintaining data security. This section outlines access levels
defined for key database tables to prevent unauthorized access. For example: User Information Table
Access, Training Data Table Access. Access control is implemented using database roles, permissions, or
application-level logic to ensure data security and privacy.

1.3 Key Design Considerations in Data Design

Several design considerations are discussed to optimize database performance and scalability:

Data Normalization: Ensuring that the database schema is normalized to minimize redundancy and maintain
data integrity.

Indexing Strategies: Implementing appropriate indexes on frequently queried columns to enhance query
performance.

Data Partitioning: Partitioning large tables into smaller segments to distribute data across multiple storage
devices and improve scalability.

Data Archiving and Retention Policies: Establishing policies for archiving historical data and defining
retention periods to manage database size and performance.

Disaster Recovery Strategies: Implementing backup and recovery mechanisms to ensure data availability in
case of system failures.

These considerations are essential for optimizing database performance, ensuring data reliability, and
facilitating future scalability.
4. Details of Other Frameworks Being Used

1.1 Session Management

This section explains the mechanism employed for session management to maintain user sessions and
manage authentication and authorization. It may involve techniques such as using session tokens, cookies, or
JWT (JSON Web Tokens) to authenticate and authorize users throughout their interaction with the system.

1.2 Caching

The caching strategy employed to improve system performance by caching frequently accessed data and
resources is described in this section. Techniques such as in-memory caching, database query caching, and
HTTP caching may be utilized to reduce latency and improve response times.

5. Unit Testing

This section outlines the approach adopted for unit testing to validate the functionality of individual system
components. It may include techniques such as test-driven development (TDD), unit test frameworks, and
test automation tools to ensure code quality and reliability.

6. Key Notes

A summary of the key points and considerations highlighted throughout the document is provided in this
section for quick reference. It serves as a handy guide for developers, architects, and stakeholders to grasp
the essential aspects of the low-level system design.

7. Reference

The Reference section includes a comprehensive list of sources and references used during the creation of
the low-level system design document. By providing citations to relevant literature, articles, and
documentation, it enhances the credibility of the document and enables readers to delve deeper into the
topics discussed if desired.