Quality Assurance - Revision history

Dondi: /* Milestones */ Copy or write up remaining QA milestones.

2017-11-09T22:16:25Z

‎Milestones: Copy or write up remaining QA milestones.

Dondi: /* Milestones */ Write up QA milestone 4.

2017-11-09T22:05:28Z

‎Milestones: Write up QA milestone 4.

Kdahlquist: /* Guild Members */ added members

2017-11-07T22:05:38Z

‎Guild Members: added members

Kdahlquist: put back my edits

2017-11-07T18:58:56Z

put back my edits

Kdahlquist: Reverted edits by Kdahlquist (talk) to last revision by Dondi

2017-11-07T18:57:56Z

Reverted edits by Kdahlquist (talk) to last revision by Dondi

Kdahlquist: removed extra project links template

2017-11-07T18:57:08Z

removed extra project links template

Kdahlquist: clarified role of QA

2017-11-07T18:56:28Z

clarified role of QA

Dondi: Initial stub-out of quality assurance guild page.

2017-11-07T16:20:38Z

Initial stub-out of quality assurance guild page.

New page

{{GRNsight Gene Page Project Links}}

The Quality Assurance team member is the resident expert on species ID systems and formats. He or she should be proficient with Google Chrome Developer tools, code-savvy editors, '''curl''', and the command line in general (as applicable) to check his or her team’s deliverable for accuracy, bugs, or any other quality-related issues.

In many cases, the same person holds the role of Project Manager and Quality Assurance, as these two roles go together as the ones who ensure that their team’s deliverable meets the overall project’s requirements.

== Guild Members ==

* Page Design:
* Gene Database APIs:
* JASPAR API:
* Interaction and Integration:

== Milestones ==

(varies per team)

{{Under Construction}}

{{GRNsight Gene Page Project Links}}

[[Category:Group Projects]]

← Older revision		Revision as of 22:16, 9 November 2017
Line 13:		Line 13:

	== Milestones ==		== Milestones ==
		+
		+	The milestones do not necessarily correspond to particular weeks; instead they are sets of tasks grouped together.
		+
		+	=== Milestone 1: Annotated Bibliography ===
		+
		+	* For the [[Week 11]] assignment, the Data Analysts will work with the QAs to develop an annotated bibliography of papers that perform the global transcriptional analysis of DNA microarray data in yeast.
		+
		+	=== Milestone 2: Journal Club Presentation ===
		+
		+	* For the [[Week 12]] assignment, the Data Analysts will work with the QAs to prepare a PowerPoint presentation to be delivered in class on Tuesday, November 21.
		+
		+	=== Milestone 3: Requirements Analysis ===
		+
		+	As the Coders begin their development work and the Data Analysts start working with their assigned microarray data sets, the QA team members should familiarize themselves with and help specify the expected correct functionalities of their respective teams.
		+
		+	* The ''entire QA guild'' should become an expert on the information that can be retrieved for a gene, so that they know how IDs should look, how certain data types will be displayed, etc. This will help them detect flaws and areas of improvement as development work proceeds.
		+	* ''Page Design team'': QA should get to know the information that is expected to be displayed on the gene page.
		+	* ''Gene Database APIs team'': QA should get to know how the four web service APIs are to be used in order to retrieve gene data given a gene symbol. They should be able to perform these steps themselves using '''curl''' or a web browser, so that they can provide independent verification that the Coders’ work is functioning correctly.
		+	* ''JASPAR team'': QA should learn about transcription factors in general and what the JASPAR database provides in particular. They should coordinate with the Coders to learn the API initially (since this API has not been seen before in class) then work out how to retrieve relevant transcription factor information for a given gene symbol. Once the steps are learned/discovered, they should be able to perform these steps themselves using '''curl''' or a web browser, so that they can provide independent verification that the Coders’ work is functioning correctly.
		+	* ''Interaction and integration team'': QA should be familiar with the vision of the project’s overall goal so that when they are presented with progressive builds of the project, they can test the functionality from end to end in order to detect flaws or points of improvement.

	=== Milestone 4: On-going Testing of Respective Team Deliverables ===		=== Milestone 4: On-going Testing of Respective Team Deliverables ===

← Older revision		Revision as of 18:57, 7 November 2017
Line 17:		Line 17:

	{{Under Construction}}		{{Under Construction}}
−
−	~~{{GRNsight Gene Page Project Links}}~~

	[[Category:Group Projects]]		[[Category:Group Projects]]

@@ Line 14: / Line 14: @@
 == Milestones ==
-(varies per team)
+=== Milestone 4: On-going Testing of Respective Team Deliverables ===
-{{Under Construction}}
+The rest of the semester is expected to be an on-going process of verifying and validating the correctness of a QA member’s assigned team. Specific concerns include but are not limited to the following:
 {{GRNsight Gene Page Project Links}}
 [[Category:Group Projects]]

@@ Line 7: / Line 7: @@
 == Guild Members ==
-* Page Design:
+* Page Design: Hayden
-* Gene Database APIs:
+* Gene Database APIs: Corinne
-* JASPAR API:
+* JASPAR API: Quinn
-* Interaction and Integration:
+* Interaction and Integration: Katie
 == Milestones ==

@@ Line 1: / Line 1: @@
 {{GRNsight Gene Page Project Links}}
-The Quality Assurance team member is the resident expert on species ID systems and formats. He or she should be proficient with Google Chrome Developer tools, code-savvy editors, '''curl''', and the command line in general (as applicable) to check his or her team’s deliverable for accuracy, bugs, or any other quality-related issues.
+The Quality Assurance (QA) team member is the resident expert on the gene data, ID systems, and formats. He or she should be proficient with Google Chrome Developer tools, code-savvy editors, curl, and the command line in general (as applicable) to check his or her team’s deliverable for accuracy, bugs, or any other quality-related issues. The QA is the bridge between the coders and the Data Analyst, integrating information from both parts of the team.
 In many cases, the same person holds the role of Project Manager and Quality Assurance, as these two roles go together as the ones who ensure that their team’s deliverable meets the overall project’s requirements.