Eportfolio

 

CSI_4_PPR ePortfolio

Building evidence.
Building professional practice.

ePortfolio for CSI_4_PPR Professional Practice. This site documents my personal development, research evidence, teamwork learning, and weekly reflections as part of the Vision Builders team at LSBU.

Edgar Camara
Student ID 4434651
BSc Computer Science Cyber Security
LSBU 2025 2026
PDP
Research evidence
Teamwork
Weekly reflections
Submission ready

Start here for markers
Quick links to required sections.
About me
Academic profile and team context.

 

PDP skills and development
SMART goals and progress measures.

 

Evidence sections
Research, teamwork, agreement.

 

Maintenance and submission
Updates, access, and submission info.

 


Week timeline
1
2
3
4
5
6
7
8
9
10

Vision Builders

About me

Academic profile, career interests, and course context.

Profile

Edgar Camara (Student ID: 4434651), BSc Computer Science (Cyber Security) at London South Bank University.
I am developing practical skills in security operations, log analysis, and incident response while building professional habits for a career in cyber security.

Academic focus
  • Programme: BSc Computer Science (Cyber Security)
  • Current module: CSI_4_PPR Professional Practice
  • Key interests: SIEM fundamentals, log analysis, structured incident reporting
Career aspirations

I am working towards a placement or graduate role as a Junior SOC Analyst or Cyber Security Analyst.
I focus on evidence based skills employers value: SIEM platforms, alert triage, clear communication, and continuous learning.

My team: Vision Builders

I am part of the Vision Builders team for the CSI_4_PPR group project, designing a Feedback Application System (FAS).
Our team meets online via Microsoft Teams or on site at LSBU.

6

Team members
10

Weeks tracked
3

PDP skill areas

Team list
Alexandra Marcu 4420667
Edgar Camara 4434651
Shakshi Brijesh Patel 4428282
Mythely Ganeshankugan 4503250
Mahshid Mohammadi Zein Abadi 4401952
Alain De Jesus 4327230
Team principles
  • Respect
  • Communicate
  • Manage
Contact placeholders
LinkedIn: add your link. GitHub: add your link.

PDP

Skills and development plan

Three skill areas as required by the module brief: technical skill, project management and teamwork skill, and writing or communication skill.

PDP header
Student name: Edgar Camara
Student ID: 4434651
Tutorial time: add your tutorial slot
Date: February 2026

How I measure progress
  • Technical: TryHackMe rooms completed and Splunk queries logged
  • Teamwork: meeting minutes, actions completed, peer feedback
  • Communication: weekly reflections on time and tutor feedback
PDP update log
Add dated notes when you revise the PDP, for example Week 4 adjusted plan after completing the first SOC module.
PDP evidence checklist
Table completed with all columns. Three skill areas covered. Goals SMART. Each component linked to career aspirations. Progress tracked in reflections.
PDP table
Component Goal Purpose Priority Plan Time frame Resources Relevance
Technical skill Develop foundational SIEM and log analysis skills using Splunk and TryHackMe labs Direct relevance to SOC roles, stronger placement applications, improved coursework quality High Complete TryHackMe SOC Level 1 path, practise Splunk queries weekly, document findings in a research log By end of Semester 2, May 2026 TryHackMe, Splunk free tier, LSBU labs, 4 hours per week Essential for junior SOC roles, SIEM skills appear in most job specs
Project management and teamwork Improve structured task management and team collaboration through the FAS group project Effective team contribution, experience of project planning that mirrors workplace dynamics High Maintain action lists with owners and due dates, share meeting minutes by rota, use a Gantt chart to track milestones Weekly throughout the module Microsoft Teams, shared files, Gantt chart template, peer feedback All cyber roles require teamwork and delivery discipline
Writing or communication Improve clear written communication through weekly reflective writing and structured evidence logs Stronger coursework and professional documentation, preparation for incident reports Medium Write one reflective entry per week, use a consistent structure, seek tutor feedback on clarity Weekly throughout the module This ePortfolio, module guidance, tutor feedback, LSBU academic skills resources Clear documentation is a daily requirement in analyst roles

Evidence

Research, teamwork, and agreement

Dated entries that show what I did, what I learned, and what proof is available.

Evidence of research

Each entry records the topic, source, context, key findings, what it proves, and the evidence uploaded.
Entries are dated and linked to module lectures and tutorials.

Research log template
Date, topic, source, context, key findings, what it proves, evidence.
Research entry 1
Week 1
February 2026
Platform selection

Topic: ePortfolio platform research for academic and professional use.
Context: Tutorial 1 Task 1 required researching at least five platforms and comparing ease of use, cost, privacy, and upload capability.
Key findings: WordPress chosen for flexibility, free tier, custom domain support, and block editor. Compared against Wakelet, Notion, Google Sites, Wix, Mahara.
What it proves: ability to evaluate tools against requirements and justify a selection.

Upload comparison table screenshot and selection notes.
Research entry 2
Add your next research entry.
Research entry 4
Add your next research entry.

Learning from teamwork

Evidence and reflection on group work, collaboration, roles, and communication for the Feedback Application System project.

Evidence types
  • Meeting minutes with actions
  • Teams communication screenshots
  • Contribution proof and deliverables
  • Reflection on what worked and what did not
Teamwork evidence: Week 1

Activity: team formation, name and logo selection, principles agreement, Week 1 presentation.
My contribution: joined team identity discussion, contributed to principles, presented with the group.
Learning: task allocation works best when based on strengths. Early principles set a professional tone.
Tutor feedback: add feedback here when available.

Upload Week 1 slides and at least one Teams screenshot.
Week 2 teamwork evidence
Add Week 2 entry: PDP presentation, Gantt chart, FAS brainstorm.
Week 3 teamwork evidence
Add Week 3 entry: creative thinking, features brainstorm, presentation.

Team project agreement

Upload the signed agreement as a PDF or image.

Upload signed team agreement here.
Agreement summary
  • Team: Vision Builders, six members
  • Communication: Microsoft Teams, respond within 24 hours
  • Meetings: Fridays preferred, online via Teams or on site at LSBU by booking
  • Task allocation: based on skills, decided together
  • Core principles: Respect, Communicate, Manage
  • Conflict resolution: raise with team first, escalate to tutor if needed

Reflections

Personal reflections

Weekly reflective entries linked to lectures, workshops, and project milestones.

1
2
3
4
5
6
7
8
9
10
Week 1 reflection
Week 1
February 2026

What I did: Formed the Vision Builders team. Agreed team name, logo, and core principles. Researched ePortfolio platforms and selected WordPress. Began building my ePortfolio. Participated in the Week 1 group presentation.

What went well: Team formation was smooth and everyone contributed. We agreed on Fridays and Microsoft Teams. Wakelet setup for the team was easy.

What did not go well and why: Task allocation is still informal, which can cause confusion as the project grows.

What I learned: Early agreement on team principles creates a strong foundation. Evaluating platforms taught me to select tools using clear criteria.

Next actions: Complete the PDP for Tutorial 2 and begin FAS research and brainstorm. For the team: assign roles and start a Gantt chart.

Weekly reflection template
Week number and date range. What I did. What went well. What did not go well and why. What I learned. Evidence added. Next actions for me. Next actions for the team.
Add Week 2 reflection: Tutorial 2 PDP, FAS brainstorm, Gantt chart, presentation.
Add Week 3 reflection: Tutorial 3 creative thinking, assumptions challenge, method selection.

Artefacts

Artefacts and evidence index

Documents, diagrams, slides, screenshots, and outputs that demonstrate learning and contribution.

ePortfolio platform comparison
ResearchWeek 1
  • Demonstrates tool evaluation against requirements
  • Shows justified selection of WordPress
Upload comparison notes or screenshot.
Week 1 group presentation slides
TeamworkWeek 1
  • Shows team identity, principles, and task allocation
  • Demonstrates collaboration and presentation
Upload Week 1 slides PDF.
Personal development plan
PDPWeek 2
  • Shows SMART goals for the three required skills
  • Demonstrates self assessment and planning
Upload completed PDP table file.
FAS brainstorm and features
ArtefactWeeks 2 to 3
  • Shows creative thinking and problem solving
  • Demonstrates ideation and assumptions challenge
Upload brainstorm notes or slides.
Gantt chart for FAS project plan
ArtefactWeek 2
  • Demonstrates project planning and timeline control
  • Shows task breakdown and milestones
Upload Gantt chart image or file.
Team agreement signed
TeamworkWeeks 1 to 2
  • Shows agreed working practices and accountability
  • Demonstrates professional team setup
Upload signed agreement file.

Maintenance

Maintenance and submission

Update schedule, dating convention, access permissions, and submission details.

Update schedule
  • One reflection each week, dated and linked to that week activities
  • New evidence added to the artefacts index
  • PDP updates if goals or priorities change
  • New entries in research and teamwork sections

Dating convention

Use DD Month YYYY, for example 16 February 2026. Include the week number in reflection titles.

Access and visibility
  • Site set to public so tutor can access without login
  • Submit URL via CW submission area by the deadline
  • Also submit URL via Microsoft form as required by Tutorial 2
  • Keep permissions active through the assessment period

Version history

16 Feb 2026: initial structure, About and PDP published.
Add your next dated entries here.

Professionalism statement

This ePortfolio is maintained as a professional document. All content is my work unless clearly attributed.
Evidence is presented honestly. Placeholders will be replaced with genuine evidence as the module progresses.

Submission reminder
Submit the link via the CW submission area by the stated deadline and ensure access remains active.