Skip to content

Commit 175e7d3

Browse files
hasithhasith
committed
initial structure commit
0 parents  commit 175e7d3

11 files changed

+315
-0
lines changed

‎.gitignore

+76
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
#
2+
# Jekyll Ignores
3+
# https://github.com/github/gitignore/blob/master/Jekyll.gitignore
4+
#
5+
6+
_site/
7+
.sass-cache/
8+
.jekyll-cache/
9+
.jekyll-metadata
10+
11+
#
12+
# macOS Ignores
13+
# https://github.com/github/gitignore/blob/master/Global/macOS.gitignore
14+
#
15+
16+
# General
17+
.DS_Store
18+
.AppleDouble
19+
.LSOverride
20+
21+
# Icon must end with two \r
22+
Icon
23+
24+
25+
# Thumbnails
26+
._*
27+
28+
# Files that might appear in the root of a volume
29+
.DocumentRevisions-V100
30+
.fseventsd
31+
.Spotlight-V100
32+
.TemporaryItems
33+
.Trashes
34+
.VolumeIcon.icns
35+
.com.apple.timemachine.donotpresent
36+
37+
# Directories potentially created on remote AFP share
38+
.AppleDB
39+
.AppleDesktop
40+
Network Trash Folder
41+
Temporary Items
42+
.apdisk
43+
44+
#
45+
# Windows Ignores
46+
# https://github.com/github/gitignore/blob/master/Global/Windows.gitignore
47+
#
48+
49+
# Windows thumbnail cache files
50+
Thumbs.db
51+
Thumbs.db:encryptable
52+
ehthumbs.db
53+
ehthumbs_vista.db
54+
55+
# Dump file
56+
*.stackdump
57+
58+
# Folder config file
59+
[Dd]esktop.ini
60+
61+
# Recycle Bin used on file shares
62+
$RECYCLE.BIN/
63+
64+
# Windows Installer files
65+
*.cab
66+
*.msi
67+
*.msix
68+
*.msm
69+
*.msp
70+
71+
# Windows shortcuts
72+
*.lnk
73+
74+
# IDE project files
75+
.idea
76+
.vscode

‎CONTRIBUTE.md

+62
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
[Home](./README.md) > How to Contribute
2+
3+
# How to Contribute
4+
5+
**Before stepping-in, please ensure you have read and understood the [Underline Principles](./README.md#underline-principles) of this curriculum**
6+
7+
What to contribute:
8+
9+
- Content reviews and improvements (technical)
10+
- Content reviews and improvements (English, presentation)
11+
- Add/propose missing/latest content
12+
- Develop more assignments for students
13+
- Add further descriptions to Modules, Topics, and Lessons
14+
- Add self study material in to Lessons
15+
16+
## For basic GitHub users (Edit on web UI)
17+
18+
Below is the community practice for you to follow in contributing to develop this curriculum via GitHub web UI.
19+
20+
- Create a GitHub account if you don't have one already:
21+
[https://github.com/](https://github.com/)
22+
23+
- Fork the below repository into your GiHub account.
24+
[https://github.com/SLASSCOM/{{repo name}}](https://github.com/SLASSCOM/{{repo name}})
25+
![Github Fork](./assets/img/github_fork.png)
26+
27+
- On the forked repository, goto the file you wish to edit, and click on the edit button.
28+
![Github Edit](./assets/img/github_edit.png)
29+
30+
- After editing a file, you should commit the changes (this is similar to saving).
31+
![Github Commit](./assets/img/github_commit.png)
32+
33+
- Edit all the files you need. Once the editing session is done you should submit your changes to the SLASSCOM repository. This is called creating a 'Pull Request'. Go to the root of your local repository and click the button as shown below to submit a pull request.
34+
![Github PR](./assets/img/github_pr.png)
35+
36+
- You may similarly perform other file operations such as create new files, delete files, upload files, etc.
37+
38+
## For advanced Git/GitHub users (Edit via cloning)
39+
40+
Below is the community practice for you to follow in contributing to develop this curriculum via cloning the files to your local machine.
41+
42+
- Create a GitHub account if you don't have one already:
43+
[https://github.com/](https://github.com/)
44+
45+
- Fork the below repository into your GiHub account.
46+
[https://github.com/SLASSCOM/{{repo name}}](https://github.com/SLASSCOM/{{repo name}})
47+
48+
- Install Git and clone the repository to your local machine
49+
50+
`git clone https://github.com/<your_username></your_username>/{{repo name}}`
51+
52+
- Add 'upstream' repo to your local cloned git repository so that you are able to obtain the latest directly from the 'upstream'.
53+
54+
`git remote add upstream https://github.com/SLASSCOM/{{repo name}}.git`
55+
56+
- Do edits to .md files by cloning your fork to the local machine using an IDE.
57+
- Always take a pull from 'upstream' before sending a pull request with following command. This will help reduce merge conflicts and increase the chance of your pull requests getting accepted.
58+
59+
`git pull upstream master`
60+
61+
- Submit a pull request to the [upstream repo](https://github.com/SLASSCOM/{{repo name}}) via GitHub web UI of your fork.
62+
- A moderator will attend to your pull request and accept, reject or request for changes.

‎README.md

+68
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
# Introduction
2+
3+
This model curriculum is to be used as guidance by educational institutes in teaching ICT.
4+
5+
<dl>
6+
<dt>Which career qualification?</dt>
7+
<dd>This is for students passionate about a Software Tester and Trainee Business Analysts related career. Depth of the lessons are intended for diploma level qualifications in pursuing an entry-level job.</dd>
8+
<dt>Recommended duration?</dt>
9+
<dd>Through a short (one year or less) intensive course.</dd>
10+
<dt>Is this free to use?</dt>
11+
<dd>This is an open-source curriculum under Creative Commons license - https://creativecommons.org/licenses/by/4.0/. You are free to use this for commercial, non-commercial use under the terms of the license. </dd>
12+
<dt>Who are behind this?</dt>
13+
<dd>SLASSCOM (together with the industry professionals) expects to maintain this and keep relevant to reflect the industry's entry-level skill demands. </dd>
14+
</dl>
15+
16+
## Modules of the curriculum
17+
18+
| Module | Details |
19+
| ------------------------------ | --------------------------------------------------------- |
20+
| Module A | [View Topics](./module-a/README.md) |
21+
| Module B | [View Topics](./module-a/README.md) |
22+
| Module C | [View Topics](./module-a/README.md) |
23+
24+
## Problem overview
25+
26+
Skills development and capacity building are vital in achieving the [SLASSCOM](https://slasscom.lk) Vision 2022 of USD 5 billion in revenue, 200,000 jobs, and 1000 startups.
27+
28+
The National IT-BPM workforce survey 2019, conducted by the ICT Agency of Sri Lanka (ICTA), reveals that the IT-BPM workforce's annual shortage is 12,140. The local universities produce only 9,076 graduates a year, and the annual demand stands at 21,216. This supply-demand gap is shown to keep growing with the industry's expansion and has become a significant bottleneck impacting the sector's growth.
29+
30+
Although there are tens of thousands of students learning ICT related subjects at various courses, their employability in the software export industry is notably low. Unemployability is mainly due to the non-relevant curriculums and low quality teaching methods.
31+
32+
## How this curriculum helps you
33+
34+
As per the industry observations, most of the ICT related curriculums in use are outdated and do not reflect the skills required by the industry. SLASSCOM expects to keep this curriculum up-to-date through volunteers and keep freely available for any institute to use as guidance for their curriculums.
35+
36+
Please note that this curriculum is not a comprehensive lesson plan to cover all the skills required. Instead, it is a limited scoped, minimal content for a student to find an entry-level job opportunity. The content of the modules, topics, and lessons are developed independently by different contributors from the industry.
37+
38+
## Underline principles
39+
40+
This curriculum is built based on the following ground principles in mind. To contribute, it is essential to understand and adhere to these principles.
41+
42+
<dl>
43+
<dt>Applicability before theory</dt>
44+
<dd>A common mistake of most curriculums is that they teach a lot of theory to students before understanding how and when to apply the same. This curriculum is built in a way students experience and understand the usage first so that they appreciate the theory when learned later. For example, students should use 'sorting' practically before writing a 'bubble sort' algorithm.</dd>
45+
<dt>Hands-on teaching</dt>
46+
<dd>Rather than long presentation slides and descriptions, the lecturer should show/write 'real code', 'real work' and explain the concepts to students in teaching.</dd>
47+
<dt>Continuous evaluations</dt>
48+
<dd>Student evaluation should be continuous and shouldn't happen just at a final examination. Use interactive, gamified tools to do quick and frequent assessments.
49+
</dd>
50+
<dt>Focus on essentials</dt>
51+
<dd>If the curriculum is shallow and broad, students may learn many things but won't master any. Since this curriculum is for a short period and is for entry levels, we propose focusing on a few things and teach them well.
52+
</dd>
53+
<dt>Pair lecturing</dt>
54+
<dd>Pair a professional from the industry with the academic lecturer when delivering the lessons. The lesson should take a discussion format between the lecturer and professional, allowing students to participate by asking questions. Industry professionals can show practical examples and some hands-on demonstrations.
55+
</dd>
56+
</dl>
57+
58+
## How to contribute
59+
60+
This repository is maintained as a community effort in the industry. If you like to contribute, please go through the following link:
61+
62+
[Guide for contributors](./CONTRIBUTE.md)
63+
64+
## Related links
65+
66+
- [Curriculum Website](https://slasscom.github.io/slasscom-qa-and-ba-curriculum)
67+
- [Git Repository](https://github.com/SLASSCOM/slasscom-qa-and-ba-curriculum)
68+
- [SLASSCOM Website](https://slasscom.lk)

‎_config.yml

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
theme: jekyll-theme-dinky
2+
title: SLASSCOM Bootcamp BA and QA Curriculum
3+
description: Contributed by the IT industry as a guidance to educational institutes.

‎assets/css/style.scss

+22
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
---
3+
4+
@import "{{ site.theme }}";
5+
6+
body {
7+
background-color: #fff;
8+
font-size: 15px;
9+
}
10+
11+
td {
12+
background: #eeeeee;
13+
}
14+
15+
a {
16+
font-weight: 400;
17+
}
18+
19+
header li {
20+
font-size: 13px;
21+
width: 150px;
22+
}

‎assets/img/github_commit.png

129 KB
Loading

‎assets/img/github_edit.png

234 KB
Loading

‎assets/img/github_fork.png

103 KB
Loading

‎assets/img/github_pr.png

255 KB
Loading

‎module-a/01-topic-a.md

+55
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
[Home](../README.md) > [{{Module Name}}](./README.md) > {{Topic Name}}
2+
3+
# Topic: {{Topic Name}}
4+
5+
* Lesson 1: [{{Lesson name}}](#lesson-1)
6+
* Lesson 2: [{{Lesson name}}](#lesson-1)
7+
* Lesson 3: [{{Lesson name}}](#lesson-1)
8+
* Assignment 1: [{{Assignment name}}](#assignment-1)
9+
10+
---
11+
---
12+
13+
## Lesson 1: {{Lesson name}}
14+
15+
<dl>
16+
<dt>Self learning Duration</dt>
17+
<dd>xx mins</dd>
18+
<dt>Lecture/Lab Duration</dt>
19+
<dd>xx mins</dd>
20+
</dl>
21+
22+
### Self learning content
23+
24+
Before Lecture:
25+
26+
* [link description](./#)
27+
* [link description](./#)
28+
29+
After Lecture:
30+
31+
* [link description](./#)
32+
33+
### Lecture/Lab description
34+
35+
Description to lecture content (50 - 100 words)
36+
37+
* teaching point 1
38+
* teaching point 2
39+
* teaching point 3
40+
41+
---
42+
---
43+
44+
## Assignment 1: {{Assignment name}}
45+
46+
<dl>
47+
<dt>Assignment Duration</dt>
48+
<dd>xx mins</dd>
49+
</dl>
50+
51+
### Assignment description
52+
53+
Description to assignment to complete
54+
55+
---

‎module-a/README.md

+29
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
[Home](../README.md) > {{Module Name}}
2+
3+
# Module: {{Module Name}}
4+
5+
> Short module description (~10 words)
6+
7+
<dl>
8+
<dt>Total Duration</dt>
9+
<dd>~ xx hours</dd>
10+
<dt>Number of Topics</dt>
11+
<dd>x</dd>
12+
</dl>
13+
14+
## Introduction
15+
16+
Module description and why the content is important in the industry (~ 50 words).
17+
18+
## Topics
19+
20+
1. [Topic A](./01-topic-a.md)
21+
2. [Topic B](./01-topic-a.md)
22+
3. [Topic C](./01-topic-a.md)
23+
24+
## Learning Outcomes
25+
26+
- learning outcome 1
27+
- learning outcome 2
28+
- learning outcome 3
29+
- learning outcome 4

0 commit comments

Comments
 (0)