INTERNSHIP LOG-BOOK
Evidence Record
Intern’s Job Title: __Research Assistant________________________________
Department: ___Information Technology_______________________________
Employee Name and Surname: _______________________________ ,
1.INTRODUCTION :This logbook is to assist Interns to keep record of their Daily work. It will
show the work and periods of time spent in each.
2. WEEKLY PLANNING OF WEEK AHEAD
3. WEEKLY REPORT ON WEEK PAST
The Daily work carried out is to be recorded clearly.
4. MONTHLY REPORT : This is a summary of work done in a week and reports on the work
covered. Employee is required to present the logbook weekly to the Supervisor for progress.
Activities PLANNING: 25 TO 29 March 2024
Day of the week Planning
Monday 25 Mar  . Review and analyze the referral website
www.xplorio.com
 Understanding the flow of the website
 Getting full understanding of the website features
 Document initial findings
 Understanding the uniqueness
Tuesday 26 Mar  Overview of Big Data: Definition, characteristics, and
importance.
 Understanding the 3Vs of Big Data: Volume, Velocity,
and Variety.
 Examples of real-world applications of Big Data in
various industries.
 Introduction to popular Big Data frameworks and
technologies such as Hadoop, Spark, Kafka, and Flink.
 Comparison of different Big Data processing
paradigms: batch processing vs. real-time processing
Wednesday 27  Overview of data capture methods: Batch processing,
Mar real-time streaming, and micro-batching.
 Detailed discussion on streaming data capture using
tools like Apache Kafka and Apache Flume.
 Importance of data quality and strategies for data
cleansing and preprocessing.
Hands-on session with Apache Kafka for setting up
data streaming pipelines.
1
Actual work done logged below. Also record below
deviance from plan and reflect on work done
 Reviewed and analyzed the referral
website.
 Understood the flow of the website.
Getting fully understand the website.
features.
Understood the uniqueness of project
 Overview of Big Data: Definition,
characteristics, and importance.
 Understanding the 3Vs of Big Data:
Volume, Velocity, and Variety.
 Examples of real-world applications of Big
Data in various industries.
 Introduction to popular Big Data
frameworks and technologies such as
Hadoop, Spark, Kafka, and Flink.
 Comparison of different Big Data
processing paradigms: batch processing
vs. real-time processing
 Overview of data capture methods: Batch processing,
real-time streaming, and micro-batching.
 Detailed discussion on streaming data capture using
tools like Apache Kafka and Apache Flume.
 Importance of data quality and strategies for data
cleansing and preprocessing.
Hands-on session with Apache Kafka for setting up
data streaming pipelines.
Thursday 28 Mar  Introduction to relational databases and NoSQL
databases.
 Understanding the CAP theorem and its implications
on distributed databases.
 Discussion on key-value stores, document stores,
column-family stores, and graph databases.
 Introduction to relational databases and
NoSQL databases.
 Understanding the CAP theorem and its
implications on distributed databases.
 Discussion on key-value stores, document
stores, column-family stores, and graph
databases.

Friday 29 Mar  Introduction to distributed file systems: HDFS
(Hadoop Distributed File System) and Amazon S3.
 Overview of distributed computing frameworks:
Apache Hadoop and Apache Spark.
 Use cases and best practices for choosing between
different storage and processing frameworks.
 Introduction to distributed file systems:
HDFS (Hadoop Distributed File System)
and Amazon S3.
 Overview of distributed computing
frameworks: Apache Hadoop and Apache
Spark.
 Use cases and best practices for choosing
between different storage and processing
frameworks.

WEEK PROGRESS CHART WEEK ENDING…29/03/2024……………………

DAY DESCRIPTION OF WORK DONE TIME SPEND

Monday 25 Mar   . Review and analyze the referral website www.xplorio.com 5 Hours
 Understanding the flow of the website
 Getting full understanding of the website features
 Document initial findings
 Understanding the uniqueness

Tuesday 26 Mar   Overview of Big Data: Definition, characteristics, and importance. 5 Hours
 Understanding the 3Vs of Big Data: Volume, Velocity, and
Variety.
 Examples of real-world applications of Big Data in various
industries.
 Introduction to popular Big Data frameworks and technologies
such as Hadoop, Spark, Kafka, and Flink.
 Comparison of different Big Data processing paradigms: batch
processing vs. real-time processing

Wednesday 27 Mar   Overview of data capture methods: Batch processing, real-time 5 Hours
streaming, and micro-batching.
 Detailed discussion on streaming data capture using tools like
Apache Kafka and Apache Flume.
 Importance of data quality and strategies for data cleansing and
preprocessing.
Hands-on session with Apache Kafka for setting up data
streaming pipelines.

Thursday 28 Mar   Introduction to relational databases and NoSQL databases. 5 Hours

 Understanding the CAP theorem and its implications on
distributed databases.
 Discussion on key-value stores, document stores, column-family
stores, and graph databases.

Friday 29 Mar   Introduction to distributed file systems: HDFS (Hadoop 5 Hours

2
 Distributed File System) and Amazon S3.
 Overview of distributed computing frameworks: Apache Hadoop
and Apache Spark.
 Use cases and best practices for choosing between different
storage and processing frameworks.

Total Hours Covered: 25 HOURS

Comments: Learned about the importance of carefully evaluating use case requirements when choosing between
storage and processing frameworks, considering factors like scalability, latency, fault tolerance, and integration.
Additionally, understanding the strengths and trade-offs of each framework enables informed decision-making for
building efficient and effective data processing pipelines.

Activities: Planning 1 to 5 April 2024

Day of the week Planning Actual work done logged above Also record below
deviance from plan
Monday 1 April  Importance of data modeling in  Importance of data modeling in
database design. database design.
 Understanding different data modeling  Understanding different data
techniques: Entity-Relationship (ER) modeling techniques: Entity-
diagrams, UML diagrams, etc. Relationship (ER) diagrams,
 Hands-on exercise on designing UML diagrams, etc.
database schemas for specific use cases.  Hands-on exercise on designing
database schemas for specific
use cases.

Tuesday 2 April  Implementation of database schemas  Implementation of database

using a relational database management schemas using a relational
system (e.g., MySQL, PostgreSQL). database management system
 Exercise on designing optimized queries (e.g., MySQL, PostgreSQL).
for data retrieval and manipulation.  Exercise on designing optimized
 Troubleshooting common database queries for data retrieval and
performance issues and optimization manipulation.
techniques.  Troubleshooting common
database performance issues
and optimization techniques
Wednesday 3 April  Importance of stakeholder interviews  Importance of stakeholder
and requirements gathering in system interviews and requirements
design. gathering in system design.
 Techniques for eliciting and  Techniques for eliciting and
documenting user requirements: documenting user
interviews, surveys, and use cases. requirements: interviews,
 Case study analysis of successful surveys, and use cases.
requirement analysis processes in Big  Case study analysis of
Data projects. successful requirement analysis

3
 processes in Big Data projects.

Thursday 4 April  Group activity: Brainstorming and  Group activity: Brainstorming

defining use cases for the data capture
and management system.
 Review and feedback session to ensure
clarity and completeness of use case
documentation.
and defining use cases for the
data capture and management
system.
 Review and feedback session to
ensure clarity and completeness
of use case documentation.

Friday 5 April  Deep dive into the domain relevant to
the data capture and management
system.
 Analysis of industry-specific challenges
and opportunities related to data
handling.
 Case studies of successful
implementations in similar domains.
 Deep dive into the domain
relevant to the data capture and
management system.
 Analysis of industry-specific
challenges and opportunities
related to data handling.
 Case studies of successful
implementations in similar
domains

WEEK PROGRESS CHART WEEK ENDING…5/04/2024……………………

DAY DESCRIPTION OF WORK DONE HOURS

 Importance of data modeling in database 4 hours

Monday
design.
01/04/2024  Understanding different data modeling
techniques: Entity-Relationship (ER) diagrams,
UML diagrams, etc.
 Hands-on exercise on designing database
schemas for specific use cases.

 Implementation of database schemas using a 4 hours

Tuesday
relational database management system (e.g.,
02/04/2024 MySQL, PostgreSQL).
 Exercise on designing optimized queries for
data retrieval and manipulation.
 Troubleshooting common database
performance issues and optimization
techniques.

4
  Importance of stakeholder interviews and 4 hours
Wednesday
requirements gathering in system design.
 Techniques for eliciting and documenting user
03/04/2024 requirements: interviews, surveys, and use
cases.
 Case study analysis of successful requirement
analysis processes in Big Data projects.

 Group activity: Brainstorming and defining use 4 hours

Thursday
cases for the data capture and management
system.
04/04/2024  Review and feedback session to ensure clarity
and completeness of use case documentation.

 Deep dive into the domain relevant to the data 4 hours

Friday
capture and management system.
 Analysis of industry-specific challenges and
05/04/2024 opportunities related to data handling.
 Case studies of successful implementations in
similar domains
Total Hours Covered: 20 Hours

Activities: Planning 8 to 12 April 2024

Day of the week Planning
Monday 8 April  Conduct stakeholder interviews to
gather additional requirements and
insights.
 Refinement of previously defined use
cases based on stakeholder feedback.
 Prioritization of features and
functionalities based on business value
and feasibility.
Actual work done logged above Also record below
deviance from plan
In practical research efforts, stakeholder
interviews were conducted to gather
additional requirements, refine existing use
cases based on feedback, and prioritize
features and functionalities according to
business value and feasibility.

5
Tuesday 9 April  Validation of documented requirements
with stakeholders to ensure alignment.
 Addressing any discrepancies or
ambiguities in the requirement
documentation.
 Formal sign-off on the requirement
document to proceed to the design phase.
the following tasks were accomplished:
validating documented requirements with
stakeholders to ensure alignment, resolving
any discrepancies or ambiguities in the
requirement documentation, and obtaining
formal sign-off on the requirement document
to proceed to the design phase.

Wednesday 10 April  Introduction to architectural design  the following tasks were

patterns and principles (e.g., MVC,
Microservices).
 Analysis of scalability, reliability, and
security considerations in system
architecture.
 Identifying architectural trade-offs and
making informed design decisions.
completed: introducing
architectural design patterns and
principles, analyzing scalability,
reliability, and security
considerations, and identifying
architectural trade-offs to make
informed design decisions.
 Revised Project Perposal

Thursday 11 April  Creation of high-level architectural  Do research in practical execution,

diagrams depicting system components high-level architectural diagrams
depicting system components and
and interactions.
interactions were created, followed by
 Discussion on component interfaces, data
discussions on component interfaces
flows, and integration points.
 Review session to gather feedback and
refine the high-level design.

Friday 12 April  Breakdown of high-level components into  breaking down high-level components
detailed design specifications. into detailed design specifications,
designing data ingestion pipelines
 Designing data ingestion pipelines, storage
layers, processing modules, and interfaces.
Update the lockbook
 Consideration of fault tolerance, data
consistency, and performance
optimizations.

DAY DESCRIPTION OF WORK DONE HOURS

In practical research efforts, stakeholder interviews were 4 Hours

Monday conducted to gather additional requirements, refine
existing use cases based on feedback, and prioritize
8/04/2024
features and functionalities according to business value
and feasibility.
the following tasks were accomplished: validating 4 Hours
Tuesday documented requirements with stakeholders to ensure
alignment, resolving any discrepancies or ambiguities in
the requirement documentation, and obtaining formal
9/04/2024
sign-off on the requirement document to proceed to the

6
 design phase.
 the following tasks were completed: 4 Hours
Wednesday introducing architectural design patterns and
principles, analyzing scalability, reliability,
10/04/2024
and security considerations, and identifying
architectural trade-offs to make informed
design decisions.
Revised Project Perposal
Do research in practical execution, high-level architectural 4 Hours
Thursday diagrams depicting system components and interactions
were created, followed by discussions on component
interfaces
11/04/2024
breaking down high-level components into detailed design 4 Hours
Friday specifications, designing data ingestion pipelines

Update the lockbook

12/04/2024
Total Hours Covered: 20 hours

Comments
All these steps
represent the
crucial transition
from
conceptualization
to practical
implementation,
ensuring a robust
and efficient
system design
that meets both
technical
requirements
and stakeholder
expectations.

Activities: Planning 15 to 19 April 2024

Day of the week Planning Actual work done logged above Also record below
deviance from plan
Monday 15 April  Evaluation of technology options for  Take a call with supervisor
each component based on  revised project plan
requirements and design constraints.

7
  Prototyping critical components to
validate technology choices and design
assumptions.
 Finalization of the technology stack for
the data capture and management
system.

Tuesday 16 April  Setup development environments and  Work on documentation

version control systems for collaborative  revised project plan
development.
 Allocation of tasks and responsibilities
to team members for prototype
implementation.
 Initial coding sprints to start building
key components of the system
prototype.

Wednesday 17 April  Hands-on coding sessions to implement  Work on documentation

prototype functionalities according to  Make table of content
the design.
 Integration of prototype components to
establish basic end-to-end functionality.
 Continuous integration and testing
practices to ensure code quality and
early bug detection.

Thursday 18 April  Iterative development cycles focusing  Work on documentation

on incremental implementation of  Make giant chart
system features.
 Code reviews and pair programming
sessions to foster collaboration and
ensure code quality.

Friday 19 April  Development of unit tests, integration  Work on documentation

tests, and acceptance tests for each  Proof read the documentation
system component.  Update lock book
 Test-driven development (TDD)
practices to maintain code integrity and
facilitate refactoring.

WEEK PROGRESS CHART WEEK ENDING…19/04/2024……………………

8
 DAY DESCRIPTION OF WORK DONE HOURS

 Take a call with supervisor 4 hours

Monday
 revised project plan
15/04/2024
 Work on documentation 4 hours
Tuesday
 revised project plan

16/04/2024
 Work on documentation 4 hours
Wednesday
 Make table of content

17/04/2024
 Work on documentation 4 hours
Thursday
 Make giant chart

18/04/2024
 Work on documentation 4 hours
Friday
 Proof read the documentation
 Update lock book
19/04/2024
Total Hours Covered: 20 hours

Comments Revised older things and lead them to betterment

Activities: Planning 22 to 26 April 2024

Day of the week Planning Actual work done logged above Also record below
deviance from plan
Monday 22 April  Evaluation of technology options for
each component based on
requirements and design constraints.
 Prototyping critical components to
validate technology choices and design
assumptions.
 Finalization of the technology stack for

9
 the data capture and management
system.

Tuesday 23 April  Setup development environments and

version control systems for collaborative
development.
 Allocation of tasks and responsibilities
to team members for prototype
implementation.
 Initial coding sprints to start building
key components of the system
prototype.

Wednesday 24 April  Hands-on coding sessions to implement

prototype functionalities according to
the design.
 Integration of prototype components to
establish basic end-to-end functionality.
 Continuous integration and testing
practices to ensure code quality and
early bug detection.

Thursday 25 April  Iterative development cycles focusing

on incremental implementation of
system features.
 Code reviews and pair programming
sessions to foster collaboration and
ensure code quality.

Friday 26 April  Development of unit tests, integration

tests, and acceptance tests for each
system component.
 Test-driven development (TDD)
practices to maintain code integrity and
facilitate refactoring.

DAY DESCRIPTION OF WORK DONE Week Ending 26 April HOURS

Monday

22/04/2024

Tuesday

23/04/2024

10
Wednesday

24/04/2024

Thursday

25/04/2024

Friday

26/04/2024
Total Hours Covered:
Comments

11
EMPLOYEE’S SUMMARY REPORT: The report should contain a summary of work done this
month. This concludes the highlights of the project the EMPLOYEE was involved in. The
EMPLOYEE is expected to point out the weak and strong points of this document.

SUPERVISOR’S COMMENT: The Supervisor

will check the logbook to ensure that work was
done, reported and record his/her comment
below.

12
……………………………………………………………………………………………………………….

………………………… …………………………

Employee signature Supervisor signature

Date: Date:

13