Ensure software is usable by Suzanne Pierce - Revision history

Suzanne at 18:22, 10 March 2015

2015-03-10T18:22:35Z

Suzanne: Set PropertyValue: Progress = 100

2015-03-06T17:36:21Z

Set PropertyValue: Progress = 100

Suzanne: Set PropertyValue: TargetDate = 2015-02-23

2015-02-21T14:12:44Z

Set PropertyValue: TargetDate = 2015-02-23

Suzanne at 14:12, 21 February 2015

2015-02-21T14:12:19Z

Suzanne at 19:23, 20 February 2015

2015-02-20T19:23:12Z

Suzanne at 19:20, 20 February 2015

2015-02-20T19:20:35Z

Suzanne at 19:15, 20 February 2015

2015-02-20T19:15:01Z

Suzanne: Deleted PropertyValue: Participants = John Gentle

2015-02-20T16:51:37Z

Deleted PropertyValue: Participants = John Gentle

Suzanne: Added PropertyValue: Participants = John Gentle

2015-02-20T16:51:34Z

Added PropertyValue: Participants = John Gentle

Admin: Added PropertyValue: Expertise = geosciences

2015-02-12T01:36:56Z

Added PropertyValue: Expertise = geosciences

@@ Line 12: / Line 12: @@
 	Type=Low}}
-'''Heatseeker workflows, data, and required packages or resources for a build'''
+'''MCSDSS workflows, data, and required packages or resources for a build'''
 An initial User Manual and Set-up Guide is available as a word document
-NEED TO DO - select case example datasets and gather together
+Selected case example datasets and gather together (see next section)
 == Technology Goals ==
-The Heatseeker is a prototype system intended to demonstrate the potential capabilities of a single page application (SPA) running atop a web and cloud based architecture utilizing open source technologies.  The application is implemented on current web standards while supporting human interface design that targets both traditional mouse/keyboard interactions and modern touch/gesture enabled interactions.
+The MCSDSS is a prototype system intended to demonstrate the potential capabilities of a single page application (SPA) running atop a web and cloud based architecture utilizing open source technologies.  The application is implemented on current web standards while supporting human interface design that targets both traditional mouse/keyboard interactions and modern touch/gesture enabled interactions.
 The technology stack for the Heatseeker was selected with the goal of creating a robust and dynamic modular codebase that can be adjusted to fit many use cases and scale to support usage loads that range between simple data display to complex scientific simulation-based modelling and analytics.  The application integrates current frameworks for highly performant agile development with unit testing, statistical analysis, data visualization, mapping technologies, geographic data manipulation, and cloud infrastructure while retaining support for traditional HTML5/CSS3 web standards.
 == Server Stack ==
-The Heatseeker capitalizes on a recent evolution in the ECMA6 standard (the JavaScript language) and its comprehensive adoption rate across all web-enabled devices as the de facto language of the internet. The current approach is based on the traditional web stack (Apache Server, MySQL DB, Linux OS) technologies. The entirety of the Heatseeker application prototype runs on the Amazon Web Services (AWS) cloud on a single Elastic Compute Cloud (EC2) medium server instance running an Amazon Linux AMI and leveraging the AWS Route53 DNS service with Elastic Storage Blocks (EBS) for dynamic real-time data persistence and Simple Storage Service (S3) for read-only and archived data persistence.
+The MCSDSS capitalizes on a recent evolution in the ECMA6 standard (the JavaScript language) and its comprehensive adoption rate across all web-enabled devices as the de facto language of the internet. The current approach is based on the traditional web stack (Apache Server, MySQL DB, Linux OS) technologies. The entirety of the MCSDSS application prototype runs on the Amazon Web Services (AWS) cloud on a single Elastic Compute Cloud (EC2) medium server instance running an Amazon Linux AMI and leveraging the AWS Route53 DNS service with Elastic Storage Blocks (EBS) for dynamic real-time data persistence and Simple Storage Service (S3) for read-only and archived data persistence.
 [[Server Side Technology Stack]]

@@ Line 7: / Line 7: @@
 	Expertise=Geosciences|
 	Owner=Suzanne_Pierce|
-	Progress=85|
+	Progress=100|
 	StartDate=2015-02-07|
 	TargetDate=2015-02-23|

@@ Line 9: / Line 9: @@
 	Progress=85|
 	StartDate=2015-02-07|
-	TargetDate=2015-02-20|
+	TargetDate=2015-02-23|
 	Type=Low}}

@@ Line 7: / Line 7: @@
 	Expertise=Geosciences|
 	Owner=Suzanne_Pierce|
-	Progress=0|
+	Progress=85|
 	StartDate=2015-02-07|
 	TargetDate=2015-02-20|

← Older revision		Revision as of 19:23, 20 February 2015
Line 15:		Line 15:

	An initial User Manual and Set-up Guide is available as a word document		An initial User Manual and Set-up Guide is available as a word document
		+
	NEED TO DO - select case example datasets and gather together		NEED TO DO - select case example datasets and gather together

@@ Line 13: / Line 13: @@
 '''Heatseeker workflows, data, and required packages or resources for a build'''
 == Technology Goals ==
@@ Line 22: / Line 25: @@
 The Heatseeker capitalizes on a recent evolution in the ECMA6 standard (the JavaScript language) and its comprehensive adoption rate across all web-enabled devices as the de facto language of the internet. The current approach is based on the traditional web stack (Apache Server, MySQL DB, Linux OS) technologies. The entirety of the Heatseeker application prototype runs on the Amazon Web Services (AWS) cloud on a single Elastic Compute Cloud (EC2) medium server instance running an Amazon Linux AMI and leveraging the AWS Route53 DNS service with Elastic Storage Blocks (EBS) for dynamic real-time data persistence and Simple Storage Service (S3) for read-only and archived data persistence.
 == Client Stack ==
@@ Line 28: / Line 48: @@
 The Yeoman workflow adds additional fluidity to the development process. For example, through integration with the Node Package Manager (for using modular third party node based libraries), Bower (for using modular third party JavaScript-based libraries), GruntJS (for automated error and code checking, unit testing, code minification, code obfuscation, and any other automated task), and providing various scaffolding systems for erecting complex application structures in very short periods of time. The online repository and project management services of BitBucket (from Atlassian) and a Git based code repository were used for the codebase management (version control) and issue tracking.
 Several third party libraries are used to provide extended capabilities.  Specifically D3 for data visualization and DOM manipulation, JQuery for DOM manipulation, SkrollrJS for parallax display effects (a visual display technique pioneered by Disney and in vogue on the modern web), WaypointsJS for linking to embedded content, GSAP for additional animations and transitions, KineticJS for additional touch and gesture support, LeafletJS for map technology integration, Bootstrap for responsive web design and user interface components, SASS & Compass for CSS styling and animations, HTML5 Boilerplate for consistent UI development, and ModernizrJS for feature detection and adaptive client capabilities.

← Older revision		Revision as of 19:15, 20 February 2015
Line 11:		Line 11:
	TargetDate=2015-02-20\|		TargetDate=2015-02-20\|
	Type=Low}}		Type=Low}}
		+
		+	'''Heatseeker workflows, data, and required packages or resources for a build'''
		+
		+	== Technology Goals ==
		+
		+	The Heatseeker is a prototype system intended to demonstrate the potential capabilities of a single page application (SPA) running atop a web and cloud based architecture utilizing open source technologies. The application is implemented on current web standards while supporting human interface design that targets both traditional mouse/keyboard interactions and modern touch/gesture enabled interactions.
		+	The technology stack for the Heatseeker was selected with the goal of creating a robust and dynamic modular codebase that can be adjusted to fit many use cases and scale to support usage loads that range between simple data display to complex scientific simulation-based modelling and analytics. The application integrates current frameworks for highly performant agile development with unit testing, statistical analysis, data visualization, mapping technologies, geographic data manipulation, and cloud infrastructure while retaining support for traditional HTML5/CSS3 web standards.
		+
		+	== Server Stack ==
		+
		+	The Heatseeker capitalizes on a recent evolution in the ECMA6 standard (the JavaScript language) and its comprehensive adoption rate across all web-enabled devices as the de facto language of the internet. The current approach is based on the traditional web stack (Apache Server, MySQL DB, Linux OS) technologies. The entirety of the Heatseeker application prototype runs on the Amazon Web Services (AWS) cloud on a single Elastic Compute Cloud (EC2) medium server instance running an Amazon Linux AMI and leveraging the AWS Route53 DNS service with Elastic Storage Blocks (EBS) for dynamic real-time data persistence and Simple Storage Service (S3) for read-only and archived data persistence.
		+
		+	== Client Stack ==
		+
		+	The client-side framework implements Google’s AngularJS, one of the predominant modern web libraries which enables modular code development in a decoupled Model-View-Controller-Service structure. The decoupled structure allows for robust unit testing (via the Karma test runner coupled with the Jasmine behavior-driven development framework for testing JavaScript code), end-to-end testing (using the Protractor test framework), automated application builds, and separation of responsibilities within the application design and within the development team roles. Additionally the AngularJS framework provides support for 1) templating systems (such as Jade, Handlebars, MustacheJS, Underscore, etc.), 2) routing, state machines, 3) data binding, 4) AJAX requests, animations and transitions (both JavaScript and CSS based), and 5) the use of modern web-development workflows based on Yeoman IO.
		+	The Yeoman workflow adds additional fluidity to the development process. For example, through integration with the Node Package Manager (for using modular third party node based libraries), Bower (for using modular third party JavaScript-based libraries), GruntJS (for automated error and code checking, unit testing, code minification, code obfuscation, and any other automated task), and providing various scaffolding systems for erecting complex application structures in very short periods of time. The online repository and project management services of BitBucket (from Atlassian) and a Git based code repository were used for the codebase management (version control) and issue tracking.
		+	Several third party libraries are used to provide extended capabilities. Specifically D3 for data visualization and DOM manipulation, JQuery for DOM manipulation, SkrollrJS for parallax display effects (a visual display technique pioneered by Disney and in vogue on the modern web), WaypointsJS for linking to embedded content, GSAP for additional animations and transitions, KineticJS for additional touch and gesture support, LeafletJS for map technology integration, Bootstrap for responsive web design and user interface components, SASS & Compass for CSS styling and animations, HTML5 Boilerplate for consistent UI development, and ModernizrJS for feature detection and adaptive client capabilities.