User:Stefan.christov

Stefan Christov

Stefan Christov is an Associate Professor of Software Engineering at Quinnipiac University. He currently teaches courses on software quality assurance, software engineering in health care, software project management, and a software engineering module in an introductory engineering course.

Stefan Christov's current research interests include improving the quality of human-intensive processes (HIPs), such as medical processes, with a focus on detecting human errors before harm is done and preventing such errors. He has used software engineering techniques to formally express and analyze models of complex HIPs and industrial engineering techniques to elicit and validate models of such processes. He is also interested in human-computer interaction techniques for presenting information to assist process performers during an ongoing process.

Stefan enjoys outdoor activities, such as running, hiking, and skiing. Other hobbies include traveling and salsa dancing.

---

Part A: Answers to "Intro to IRC Activity" questions:

• How do people interact? By entering comments in the IRC channel, using a combination of free text and IRC commands.
• What is the pattern of communication? A meeting chair initiates the meeting and sets a topic. Other meeting participants discuss the topic (e.g., issues they have encountered, proposed solutions).
• Are there any terms that seem to have special meaning? 'IRC meeting chair', 'MeetBot', the IRC commands.
• Can you make any other observations? Occasionally, the meeting chair issues IRC commands to summarize discussion points and log action items.
• Join an HFOSS project's channel, observe for 24 hours, summarize observations. I joined the #foss2serve channel. For the period that I observed, someone changed their nick and there was an announcement about a conference.

Part A: Answers to "Project Anatomy Activity" questions:

• The Sugar Labs Project
  • Summarize the information under 'Contacts' for several teams of Sugar Labs. It is typical for a team to provide information about team coordinator(s), team members, and an IRC channel. Some teams also provide a mailing list.
  • Indicate the types/categories of tickets listed on this page as well as the information available for each ticket. Types: defect, enhancement, and task. Info for each ticket: ticket number, summary, status, owner, type, priority, milestone.
  • Does the project use a web-based common repository or a local repo? It uses a web-based repo.
  • Describe how the release cycle and roadmap update are related. A roadmap update is performed at the beginning of each release cycle.
• The Sahana Eden Project
  • Summarize the information found under each group. Most groups contain information about the activities of the group, guidelines for performing these activities, and information about tools to support these activities. The structure of the page for each team in the Sugar Labs project seems a bit more rigorous than the structure of the teams' pages in the Sahana Eden Project--for example, for the Sugar Labs project, each team's page starts with a mission, the contacts page has a standard set of sections, etc.
  • Tracker
    • How is the information here different than the information found on the Sugar Labs tracker page? The info here is organized by queries related to the existing tickets, such as tickets that are currently active and recently fixed bugs.
    • Click the Active Tickets link. Indicate the types/categories of tickets listed on this page as well as the information available for each ticket. Types: defect/bug, enhancement, task, documentation. Info for each ticket: Ticket number, Summary, Component, Version, Priority, Type, Owner, Status, Date Ticket Created.
  • Does the project use a web-based common repository or a local repo? The code resides on GitHub, so there is a web-based common repository. Users/developers can clone the code into a local git repository on their machine.
  • Describe the information found on the project's roadmap. The roadmap contains different releases and the key features each release must contain, along with other information, such as how much of each release is completed and when the release is due.