User Experience (UX) Design is a design approach that focuses on how the end user perceives the product. Its aim is to provide the user with the most pleasing experience possible in terms of utility, emotional appeal, ease of use, and overall value. UX design can be applied to many different media, but for the sake of this review, I am referring to UX design in relation to digital media, such as applications and websites.
The CDC Integrated Surveillance Portal (CISP) prototype is a comprehensive, real-time, interactive resource for CDC, its partners, and the public to explore and discover information about the full inventory of CDC’s Surveillance Systems, Programs, Registries, Health Surveys, Tools, and Collaboratives. CISP contains not only descriptive information about these CDC resources — CISP also describes the relationships between resources.
One of the things that caused some mild consternation in our first Scrum sprint was Angular and IE9. For those unfamiliar with Scrum, it is a specific agile software development framework / methodology for managing product development. A sprint is a specific period of time to carry out work.
End-to-end testing is a methodology used to test whether the flow of an application is performing as designed from start to finish. This becomes essential as an application grows in scope and complexity and it becomes unfeasible to manually test for new features, catch bugs and notice regressions. These types of tests are also meant to capture bugs that come up during the integration between components that would not be caught during unit tests. For those unfamiliar with unit testing, it focuses on testing small individual “units” of source code.
Optimizing for performance can fall by the wayside when developing in a fast-paced environment such as the Informatics Innovation Unit (IIU). The IIU team strives to rapidly build out web application prototypes. Often, to get a prototype “into the hands” of our clients as quickly as possible, we are forced to adopt a “we’ll get to that later” philosophy. This issue came to the forefront when, out of curiosity, I tested our sites through Google’s PageSpeed Insights and was surprised to learn that, even though our sites ran well in our testing and production environments, our sites had page weights of more than 3mb and scored relatively poorly on their speed tests. This result was well over the average of 1.7mbs, which meant that for slower connections our sites would have a prolonged load time.
HL7 is the abbreviation for the term, Health Level-7. The organization, HL7, provides international standards for the structuring and transmission of clinical and administrative data in the healthcare domain. One HL7 interoperability specification used for many years has been version 2.x, otherwise known as V2. V2 has been a standard used to codify medical (led by billing) information and transmit it between computerized medical systems. The standard was developed and finalized during the 1980s, and thus was optimized for lower memory and storage usage in the very early stages of networked computing; thus it was an implicitly typed flat-file.
Overview The following is an outline of the branching, merging, and workflow conventions that can help development teams manage parallel feature development and release management. This workflow style is taken directly from http://nvie.com/posts/asuccessful-gitbranchingmodel/ Please visit that site to read the full length post on the details of this method.