Coder - Revision history

Dondi: /* Milestone 4: Development, Implementation, and Unit Testing */ Add link to QA.

2017-11-09T21:56:47Z

‎Milestone 4: Development, Implementation, and Unit Testing: Add link to QA.

Dondi: /* Milestones */ Write up milestone 5.

2017-11-09T21:40:52Z

‎Milestones: Write up milestone 5.

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

2017-11-09T21:22:16Z

‎Milestones: Write up milestone 4.

Dondi: /* Milestones */ Write up milestone 3.

2017-11-09T21:03:20Z

‎Milestones: Write up milestone 3.

Dondi: /* Milestones */ A word on timing.

2017-11-09T20:57:23Z

‎Milestones: A word on timing.

Dondi: /* Milestones */ Write up Milestone 2.

2017-11-09T20:54:52Z

‎Milestones: Write up Milestone 2.

Dondi: /* Milestones */ Wrong markup language heh.

2017-11-09T20:37:45Z

‎Milestones: Wrong markup language heh.

Dondi: Write up milestone 1.

2017-11-09T20:37:04Z

Write up milestone 1.

Dondi: Add journal club as a milestone.

2017-11-09T20:32:23Z

Add journal club as a milestone.

Kdahlquist: /* Guild Members */ added guild members

2017-11-07T22:04:48Z

‎Guild Members: added guild members

@@ Line 63: / Line 63: @@
 If anyone runs into problems with this procedure, please consult with your fellow guild members or notify Dr. Dionisio.
-=== Milestone 4: Development, Implementation, and Unit Testing ===
+=== Milestone 4: Development, Implementation, and Localized Testing ===
 At this point, each team proceeds with their own development work. In general, each team will do most of their work (and place most of their files) in the following locations within the GRNsight repository. Some files may need to go elsewhere; check in with Dr. Dionisio if there are any file organization/location issues:
@@ Line 74: / Line 74: @@
 For the Gene Database APIs and JASPAR teams, your work will not be visible to end-users until the first overall integration is done, so use ''unit tests'' as your initial approach for verifying that your code is working well. You will probably need to mock up your API calls so that you don’t bombard the web services with requests while unit testing. However, these sites are generally open access so you can probably write your ''initial'' set of tests using real requests and responses.
 The Interaction and Integration team should initially get to know the files being created and worked on by the other teams prior to the first integration milestone.

@@ Line 43: / Line 43: @@
 #* ''After'' the ''gene-database-apis'' branch is created, the JASPAR API team creates a branch '''from ''gene-database-apis''''' called ''jaspar-api''.
-The teams will then do their work on their respective branches. The protocol for integrating your work is described in the ''Integration'' milestone below.
+The teams will then do their work on their respective branches. The protocol for integrating your work is described in the ''Integration and Integration Testing'' milestone below.
 The structure described in this milestone is a typical GitHub fork-and-branch approach which some Coders are already familiar with. If any Coder needs help with this methodology, please consult your fellow guild members or ask Dr. Dionisio.
@@ Line 63: / Line 63: @@
 If anyone runs into problems with this procedure, please consult with your fellow guild members or notify Dr. Dionisio.
-=== Milestone 4: Development, Implementation, and Testing ===
+=== Milestone 4: Development, Implementation, and Unit Testing ===
 At this point, each team proceeds with their own development work. In general, each team will do most of their work (and place most of their files) in the following locations within the GRNsight repository. Some files may need to go elsewhere; check in with Dr. Dionisio if there are any file organization/location issues:
@@ Line 79: / Line 79: @@
 Teams should perform their own internal testing (both manual and automated) on their respective files throughout development. Commit and push your work to your designated branch at appropriate intervals. Coders who are not familiar with this style of working should consult with fellow guild members or talk to Dr. Dionisio.
-=== Milestone 5: Integration and Testing ===
+=== Milestone 5: Integration and Integration Testing ===
-{{Under Construction}}
+Integration and integration testing should take place periodically to make sure that the overall gene page project is coming together well. Most of the Coders’ work for the remainder of the semester will be a cycle of the development and integration milestones. The Interaction and Integration team is in charge of coordinating when these integrations take place. The first integration will likely be the most difficult one to perform, but it is hoped that later iterations will proceed more smoothly.
 {{GRNsight Gene Page Project Links}}
 [[Category:Group Projects]]

@@ Line 43: / Line 43: @@
 #* ''After'' the ''gene-database-apis'' branch is created, the JASPAR API team creates a branch '''from ''gene-database-apis''''' called ''jaspar-api''.
-The teams will then do their work on their respective branches. The protocol for integrating your work is described in the ''Integration and Testing'' milestone below.
+The teams will then do their work on their respective branches. The protocol for integrating your work is described in the ''Integration'' milestone below.
 The structure described in this milestone is a typical GitHub fork-and-branch approach which some Coders are already familiar with. If any Coder needs help with this methodology, please consult your fellow guild members or ask Dr. Dionisio.
@@ Line 63: / Line 63: @@
 If anyone runs into problems with this procedure, please consult with your fellow guild members or notify Dr. Dionisio.
-=== Milestone 4: Development and Implementation ===
+=== Milestone 4: Development, Implementation, and Testing ===
-(varies per team)
+At this point, each team proceeds with their own development work. In general, each team will do most of their work (and place most of their files) in the following locations within the GRNsight repository. Some files may need to go elsewhere; check in with Dr. Dionisio if there are any file organization/location issues:
 === Milestone 5: Integration and Testing ===

← Older revision		Revision as of 21:03, 9 November 2017
Line 48:		Line 48:

	=== Milestone 3: “Developer Rig” Setup and Initial As-Is Build ===		=== Milestone 3: “Developer Rig” Setup and Initial As-Is Build ===
		+
		+	Before development can begin in earnest, the following initial setup steps must be performed ''per Coder'' after version control setup is complete:
		+	# '''git clone''' the GitHub fork created in the version control setup milestone on where you plan to work on the project.
		+	# '''cd''' into the folder that contains the cloned repository
		+	# '''git checkout''' the branch that is assigned to you:
		+	#* Interaction and Integration: ''master'' (no need for an explicit checkout because the clone defaults to this branch)
		+	#* Page Design: ''page-design''
		+	#* Gene Database APIs: ''gene-database-apis''
		+	#* JASPAR: ''jasper-api'' (note that as instructed above, '''this should be a branch of the ''gene-database-apis'' branch''')
		+	# Follow the [https://github.com/dondi/GRNsight/wiki/Running-the-Applications instructions in the GRNsight wiki] to perform the following:
		+	## Installation of necessary third-party libraries
		+	## Initial startup of the GRNsight application ''on your computer''
		+
		+	If anyone runs into problems with this procedure, please consult with your fellow guild members or notify Dr. Dionisio.

	=== Milestone 4: Development and Implementation ===		=== Milestone 4: Development and Implementation ===

@@ Line 12: / Line 12: @@
 == Milestones ==
-The milestones do not necessarily correspond to particular weeks; instead they are sets of tasks grouped together.
+The milestones do not necessarily correspond to particular weeks; instead they are sets of tasks grouped together. However, Milestones 1-3 are hard prerequisites for proceeding to Milestone 4, so ideally the Coder guild should finish these milestones (they require some coordination; see below) as soon as possible. The Coder guild should be working within the Milestone 4-5 cycle by Week 12 ''at the latest''.
 === Milestone 0: Journal Club Presentation ===

@@ Line 20: / Line 20: @@
 === Milestone 1: Working Environment Setup ===
-Coder work will require the following software. The Seaver 120 lab computers are already set up for this; this list is provided for coders who need to work on a different computer or outside of the lab.
+Coder work will require the following software. The Seaver 120 lab computers are already set up for this; this list is provided for Coders who need to work on a different computer or outside of the lab.
 * Node.js 8.4.0 or newer
 * Code-savvy editor such as Atom or Microsoft Visual Studio Code
@@ Line 30: / Line 30: @@
 === Milestone 2: Version Control Setup ===
 === Milestone 3: “Developer Rig” Setup and Initial As-Is Build ===
@@ Line 36: / Line 52: @@
 (varies per team)
 {{Under Construction}}

@@ Line 24: / Line 24: @@
 * Code-savvy editor such as Atom or Microsoft Visual Studio Code
 * Web browser with developer tools (Seaver 120 uses Google Chrome)
-* ***git*** version control software
+* '''git''' version control software
-* (depends on team) ***curl*** command
+* (depends on team) '''curl''' command
 Make sure that this software is installed and operational before beginning. If any Coder needs help with any of these packages, please consult your fellow guild members or ask Dr. Dionisio.

@@ Line 5: / Line 5: @@
 == Guild Members ==
-* Page Design:
+* Page Design: Arash (Coder), Nicole (Designer)
-* Gene Database APIs:
+* Gene Database APIs: Eddie A. and John
-* JASPAR API:
+* JASPAR API: Eddie B. and Simon
-* Interaction and Integration:
+* Interaction and Integration: Blair and Zach
 == Milestones ==