User:Relkharboutly

Revision as of 18:10, 5 November 2014

Ruby ElKharboutly is an Assistant Professor of Software Engineering at Quinnipiac University. The Software Engineering Program is offered in the newly established School of Engineering. Dr. Ruby's research interests include software design and architecture, reliability and performance and software data analysis. Prior to joining Quinnipiac, Dr. Ruby was a full-time Professor at University of Connecticut. She has four years of industrial experience working as a software engineering and IT consultant. In her spare time, Dr. Ruby is mostly spending time with her kids, in the kitchen or at the gym.

Introduction to IRC

• How to people interact? By sending instant messages to all meeting participants.
• What is the pattern of communication? No specific pattern. It seems to be a long meeting where each participant sends a message whenever they have something to say.
• Are there any terms that seem to have special meanings? Yes, all the hash tags such as #info, #action, #topic,
• Can you make other observations? The time stamp, text after hash tags is bold.

Intro to Project Anatomy

Sugar Labs Project

Teams: Each team has a mission and specific set of responsibilities. Team pages are structured differently for each team.

Bugs: Each ticket has a number, summary, status, owner, type priority and release milestone. Bugs belong to components and are categorized according to priority, severity and bug status.

Repository: Web-based or local? web-based

Release cycle: The roadmap is updated at the beginning of each release cycle

Sahana Eden Project

Teams

Developers: Developers can review the BluePrints of the project including requirements and design. They can create User Story/Use Case as well. Complete instructions are included in the "Developer Guidelines" to introduce new developers to the project

Testers : Testers can assist as non-technical users by following the QA process documented on the wiki. They can report issues using Bug Reporting Guidelines. Developers can test their code as well by following Developer/Testing Guidelines. Finally, SysAdmins can set up a server by following the Continuous Integration process.

Designers: Designers can help make the application and the web site more usable. Guidelines for themes and usability are available on the website.

Bugs: Tickets are in the form or reports. Each ticket is structured in the same way as in the Sugar Lab Project

Repository: Web-based or local? local

Release cycle: The roadmap includes key features, modules and supported material

Project Evaluation Activity

Evaluation : File:Mifos-Eval-ElKharboutly.xlsx

FOSS In Courses Activity

I am interesting in the design and architecture of the FOSS projects in general. To be able to reverse engineer a project and model the design. To evaluate the design and suggest improvements. My students are using FreeMind this semester to map the design and architecture. I could have benefited form the project evaluation activity to help students understand the project.

Bug Reports

Part 1-Bug Reports:

1. Define what each of the column names below indicate. Include the range of possible values for 2-7 below. Feel free to explore beyond the page to find more information.
   1. ID
   2. Sev
   3. Pri
   4. OS
   5. Product
   6. Status
   7. Resolution
   8. Summary
2. Describe how you discovered the definitions and how did you find the information from above (hint: the advanced search shows the options or the Reports link has a link)?
3. Identify the order in which the bugs are initially displayed?
4. What is the meaning of the shading of some bug reports?
5. What is the meaning of the colors used when describing a bug (red, gray, black)?
6. Select a bug that you think that you might be able to fix and look at it more closely (click on the bug number).
   1. Identify when the bug was submitted.
   2. Identify if there has been recent discussion about the bug?
   3. Is the bug current?
   4. Is the bug assigned? To whom?
   5. Describe what you would need to do to fix the bug.
7. Repeat the previous step with a different kind of bug.

Part 2 - Collective Reports

1. Click on the “Reports” link on the top of the page.
2. How many bug reports were opened in the last week? How many were closed?
3. What was the general trend last week? Were more bugs opened than closed or vice versa?
4. Who were the top three bug closers? Why is this important to know?
5. Who were the top three bug reporters? Are these the same as the top three bug closes? What is the overlap in these two lists?
6. Who are the top three contributors of patches?
7. Who are the top three reviewers of patches? What is the overlap between these lists and the bug closers and bug reporters? What is the overlap between patch contributors and patch reviewers?
8. Click on the “Generic Reports” link.
9. Plot the Severity of each Version of the Accessibility features of Empathy.
10. What other reports can you generate?