User:Kchahal
(4 intermediate revisions by one user not shown) | |||
Line 3: | Line 3: | ||
Some of the research publications related to this work are as follows: | Some of the research publications related to this work are as follows: | ||
− | Open Source Software Evolution: A Systematic Literature Review (Part 1), International Journal of Open Source Software and Processes (IJOSSP), Vol 7, issue 1, January-March 2016, IGI Global. | + | 1. Open Source Software Evolution: A Systematic Literature Review (Part 1), International Journal of Open Source Software and Processes (IJOSSP), Vol 7, issue 1, January-March 2016, IGI Global. |
− | Open Source Software Evolution: A Systematic Literature Review (Part 2), International Journal of Open Source Software and Processes (IJOSSP), Vol 7, issue 1, January-March 2016, IGI Global. | + | 2. Open Source Software Evolution: A Systematic Literature Review (Part 2), International Journal of Open Source Software and Processes (IJOSSP), Vol 7, issue 1, January-March 2016, IGI Global. |
3. Fuzzy Analysis and Prediction of Commit Activity in Open Source Software Projects, IET Software, 2016. | 3. Fuzzy Analysis and Prediction of Commit Activity in Open Source Software Projects, IET Software, 2016. | ||
4. Analysing Change Profiles of Open Source Software Projects using Burst Detection, IET Software,2016. | 4. Analysing Change Profiles of Open Source Software Projects using Burst Detection, IET Software,2016. | ||
Line 14: | Line 14: | ||
− | == Activity Stage 1C: FOSS in Courses - II == | + | == POSSE 07-17 Activity Stage 1C: FOSS in Courses - II == |
Line 37: | Line 37: | ||
^ plan a role play for each issue by assigning different tasks to different groups e.g. one group may be the user, and another may be responsible for requirement analysis. | ^ plan a role play for each issue by assigning different tasks to different groups e.g. one group may be the user, and another may be responsible for requirement analysis. | ||
^ remember to reverse the roles for different issues so that every group gets opportunity to play different roles. | ^ remember to reverse the roles for different issues so that every group gets opportunity to play different roles. | ||
− | + | ^ towards the end of the semester, choose one issue and ask different groups to work simultaneously on the same issue to judge their progress. | |
− | + | *** Advanced Software Engineering | |
+ | ^ FOSS is the best example to learn development of distributed systems by global teams. | ||
+ | ^ Introduce FOSS to learn human aspects of software engineering - developer demography. | ||
+ | ^ Understand different project requirements in different contexts - political, social, economic constraints. | ||
+ | ^ Students can be asked to compare different projects using product/process/project metrics. | ||
+ | ^ Take case studies of failed projects/ successful FOSS projects. Is there any recipe of a successful project? | ||
+ | == POSSE 07-17 Activity to evaluate OpenMRS == | ||
− | |||
{| class="wikitable" style="width:100%;" | {| class="wikitable" style="width:100%;" |
Latest revision as of 19:45, 29 June 2017
Dr. Kuljit Kaur Chahal is a senior lecturer in department of Computer Science, Guru Nanak Dev University, Amritsar, Punjab, India. Her teaching interest lies in the following subjects - data structures, programming languages, object oriented analysis and design, software engineering, operating systems, and distributed systems. As a researcher, she is particularly interested in the Open Source development paradigm. Recently, she completed a major research project on "Tracking Open Source Software Evolution for Characterization of its Evolutionary Behaviour" with research grant (worth 9,35,000 INR) from the UGC, India. Some of the research publications related to this work are as follows:
1. Open Source Software Evolution: A Systematic Literature Review (Part 1), International Journal of Open Source Software and Processes (IJOSSP), Vol 7, issue 1, January-March 2016, IGI Global. 2. Open Source Software Evolution: A Systematic Literature Review (Part 2), International Journal of Open Source Software and Processes (IJOSSP), Vol 7, issue 1, January-March 2016, IGI Global. 3. Fuzzy Analysis and Prediction of Commit Activity in Open Source Software Projects, IET Software, 2016. 4. Analysing Change Profiles of Open Source Software Projects using Burst Detection, IET Software,2016. 5. Tracking Open Source Software Evolution for the Characterization of Its Evolutionary Behavior, 17th International Conference on Product-Focused Software Process Improvement (PROFES16). Editors: Abrahamsson, P., Jedlitschka, A., Nguyen Duc, A., Felderer, M., Amasaki, S., Mikkonen, T. (Eds.), 22-24 November 2016, Trondheim, Norway, Springer.
faculty web page: [1]
Currently she is exploring how to encourage students to participate in open source software projects for humanitarian needs.
POSSE 07-17 Activity Stage 1C: FOSS in Courses - II
- Introductory Programming Language Course
>include an activity on program documentation - ^ first identify modules that students can understand easily e.g. sorting/searching lists. ^ make the students read the code - suggest comments. ^ add fun by asking them to compete - for awarding the best comment for a piece of code. >a senior group can be assigned tasks to introduce FOSS projects to their juniors >learn coding styles, naming conventions.
- Data Structures
> Learn use of different data types/structures in a FOSS project. > Appreciate the different ways of doing the same thing > Analyze the existing implementation and suggest improvements. ^ again best suggestions can be awarded suitably
- Software Engineering
> Learn different roles/activities involved in a software project e.g. analysis, design, coding, testing, deployment, operations ^ Start with a FOSS project such as OpenMRS. Ask them to go through the open issues in the project. ^ encourage them to brain storm (make it a group activity) and suggest more issues related to the domain of the project. ^ involve students to short list a few of the issues that the class wants to work on in the semester course. ^ plan a role play for each issue by assigning different tasks to different groups e.g. one group may be the user, and another may be responsible for requirement analysis. ^ remember to reverse the roles for different issues so that every group gets opportunity to play different roles. ^ towards the end of the semester, choose one issue and ask different groups to work simultaneously on the same issue to judge their progress.
- Advanced Software Engineering
^ FOSS is the best example to learn development of distributed systems by global teams. ^ Introduce FOSS to learn human aspects of software engineering - developer demography. ^ Understand different project requirements in different contexts - political, social, economic constraints. ^ Students can be asked to compare different projects using product/process/project metrics. ^ Take case studies of failed projects/ successful FOSS projects. Is there any recipe of a successful project?
POSSE 07-17 Activity to evaluate OpenMRS
Evaluation Factor | Level (0-2) |
Evaluation Data |
---|---|---|
Licensing | 2 | the Mozilla Public License, v. 2.0 with Healthcare Disclaimer . |
Language | 2 | top three languages-> Java 95.4% SQLPL 3.0% GAP 0.7% |
Level of Activity | 2 | Commit activity is quite regular. A lot of activity is seen in 2011-12. Most of the activity occurs on week days |
Number of Contributors | 2 | total 263 contributors. very large network. |
Product Size | 2 | 219.87 MB |
Issue Tracker | 2 | |
New Contributor | 2 | project is very inviting |
Community Norms | 2 | well documented rules |
User Base | 2 | large user base spread in six continents as the atlas shows |
Total Score | 18 | great project for students to contribute. there are a number of unassigned modules which students can start working on as per their skill set. |