文件列表:

.idea/ (0, 2015-07-07)
.idea/.name (8, 2015-07-07)
.idea/compiler.xml (709, 2015-07-07)
.idea/copyright/ (0, 2015-07-07)
.idea/copyright/profiles_settings.xml (74, 2015-07-07)
.idea/misc.xml (2312, 2015-07-07)
.idea/modules.xml (383, 2015-07-07)
.idea/uiDesigner.xml (8792, 2015-07-07)
.idea/vcs.xml (180, 2015-07-07)
FedMedCo-grailsPlugins.iml (10873, 2015-07-07)
FedMedCo.iml (9502, 2015-07-07)
application.properties (111, 2015-07-07)
docs/ (0, 2015-07-07)
docs/Architecture.md (70, 2015-07-07)
docs/ContinuousIntegration.md (1716, 2015-07-07)
docs/Monitoring.md (131, 2015-07-07)
docs/Personas_and_user_scenerios_for_18F.pdf (1080874, 2015-07-07)
docs/Personas_and_user_scenerios_for_18F.pptx (304559, 2015-07-07)
docs/UserGuide.md (2211, 2015-07-07)
docs/architecture.png (128513, 2015-07-07)
docs/aws1.png (107550, 2015-07-07)
docs/aws2.png (98297, 2015-07-07)
docs/aws3.png (95893, 2015-07-07)
docs/jenkins1.png (92978, 2015-07-07)
docs/jenkins2.png (62739, 2015-07-07)
docs/query0-input.png (83386, 2015-07-07)
docs/query0-output1.png (147302, 2015-07-07)
docs/query0-output2.png (160718, 2015-07-07)
docs/query1-input.png (45743, 2015-07-07)
docs/query1-output.png (37856, 2015-07-07)
docs/query2-input.png (45707, 2015-07-07)
docs/query2-output1.png (49983, 2015-07-07)
docs/query2-output2.png (34375, 2015-07-07)
docs/query3-input.png (45603, 2015-07-07)
docs/query3-output.png (89695, 2015-07-07)
docs/query4-input.png (49770, 2015-07-07)
docs/query4-output.png (46218, 2015-07-07)
docs/query5-input.png (35502, 2015-07-07)
... ...

# Agile Delivery Services (ADS 1) FedMedCo ## http://www.fedmedco.info/FedMedCo This prototype provides a responsive human centered design interface that enables both novice and experienced users to search the openFDA data to identify critical drug information and display results across multiple devices. Please login using the following information: * user id: john * password: password ## Overview Lockheed Martin has provided a Minimum Viable Product (MVP) directed at three main categories of users: patients, pharmaceutical manufacturers, and regulatory agencies. The drug reaction and food to drug interaction features are primarily for patients seeking information about medications they are using. The interesting facts about drugs feature and the open query are for both pharmaceutical manufacturers and regulatory agencies who have pharmaceutical domain knowledge and are performing a deep dive. ## Features * Adverse Events - Drug related patient deaths * Reported Drug Reactions * Drug to Food Interaction * Interesting facts about drugs * Open Query for search engine * Multi-Device compatibility ## Description Lockheed Martin, headquartered in Bethesda with over 113,000 employees and greater than 45B in sales, selected to put their best and brightest on the task for the 18F challenge. We are known for our engineering expertise in building complex systems, but not our agility in delivering rapid solutions. We see this challenge as a step in the right direction in changing both government as well as our own corporate culture ensuring we are agile in delivering needed capabilities to the field. Beginning with an analysis of the requirements set forth in the RFQ and with the user in mind, our team engaged an FDA subject matter expert (SME) to identify capabilities that would be valuable to the end users of FDA applications. Based on interviews with the SME, our team determined to focus on three main personas: patients, pharmaceutical manufacturers, and pharmaceutical regulators. Our understanding of the data led us to believe that 80% of the usage would be patients looking for information regarding their medications. We leveraged iterative user interface design by pairing our user interface developer with the FDA SME to develop prototype screen mockups. We also engaged the FDA SME in our task analysis, which included developing personas, scenarios, and use cases. Once we had these, we identified the appropriate architecture and technology stack needed to best deliver the use cases. We identified the appropriate business and architectural epics that would provide the capabilities identified and then developed conditions of acceptance for those capabilities. We made use of VersionOne to track the sprint and associated metrics. The team then decomposed the epics into user stories and aligned them to the appropriate personas and linked them to test cases. Our team then set a time box of one week to complete the user stories to be delivered. Our product owner worked with the team to prioritize the user stories against business value, ensuring we delivered in priority order. We selected to utilize scrum as our core Agile management practice due to its structure, predefined business rhythms and associated artifacts. At the start of our one week sprint the team decomposed the user stories into 2-8 hour tasks to maximize transparency into delivery. Each of the tasks was tracked within our Agile project management tool. At the start of each day the team had a virtual daily stand-up given the distributed nature of the team across multiple time zones. We leveraged the architecture design developed by our solutions architect and rapidly set up the environment. We made use of Apache Tomcat for our web server, Grails for a lightweight web framework, HTML5/CSS3 couple with bootstrap and JQuery to develop a presentation that would support responsive design; D3.js along with DataMaps for remixing openFDA data with SVG maps; Sitemesh to provide HTML templates; MongoDB as a NoSQL database; and RESTful webservice to pull out the needed data. Once our environment was set up we instantiated continuous integration with GIT, Jenkins, and SonarQube. Technical excellence is a key aspect of Agile architecture therefore we wanted to ensure we managed technical debt from the start. Upon the completion of each build in Jenkins the team could rapidly see if they had increased technical debt into the baseline and make decisions from a position of knowledge regarding its cleanup. With the knowledge that social coding is closely linked to the ease of being able to extend the baseline we focused on ensuring our code was the highest quality possible. In order to realize the benefits of DevOps our team mapped the value stream to delivery at the start, leveraging Amazon Web Services (AWS) as our target environment. The team was able to deploy multiple times to AWS enabling us to remove bottlenecks early that we may not have found until the end of our time box. Usability testing was critical to the success of our delivery and our FDA SME spent hours verifying the capabilities and ensuring they met the acceptance criteria. With the knowledge that the patient persona would utilize the site the most the team provided access to the site to a random number of employees at Lockheed Martin with various skillsets and backgrounds. These users were able to identify issues our SME had not considered such as if the end user typed something irrelevant such as "Dog" into the search. We updated the application to provide informative error messages to the user. In a digital society the team wanted to ensure the security of the application given the criticality of the data and the impact on the end user if the application was tampered with. The team had security scans done at multiple times during the course of the week to understand vulnerabilities being exposed and incorporating feedback to remove any security concerns. ## User Guide Learn how to use our application, including examples of sample queries to try, in our [user guide](https://github.com/williamjking/FedMedCo/blob/master/docs/UserGuide.md). ## Design Documents * [Architecture Diagrams](https://github.com/williamjking/FedMedCo/blob/master/docs/Architecture.md) * [Personas & Use Cases](https://github.com/williamjking/FedMedCo/blob/master/docs/Personas_and_user_scenerios_for_18F.pdf) ## Technologies | | **Technology** | **Description** | **License** | **Version** | **Date** | | --- | --- | --- | --- | --- | --- | | 1. | Grails | Web framework | Apache 2 | 2.5 | 2015 | | 2. | Groovy | Language | Apache 2 | 2.4 | 2015 | | 3. | HTML5/CSS3 using Bootstrap | Presentation / responsive design supporting multi-device | MIT | 3.3.4 | 2015 | | 4. | JQuery | JavaScript library | MIT | 1.11.1 | 2014 | | 5. | D3js | JavaScript library for manipulating documents based on data| BSD | 3.5.3 | 2014 | | 6. | Datamaps | Customizable SVG map visualization Javascript library.| MIT | 0.4.0 | 2015 | | 7. | Sitemesh | HTML template framework based on Decoration Model | OpenSymphony (Apache) | 2.1.5 | 2015 | | 8. | GORM | Object relationship mapping | Apache 2 | 2.5.0 | 2015 | | 9. | MongoDB | NoSQL database JSON-like documents | GNU AGPL v3 | 3.0.4 | 2015 | | 10. | Tomcat | Java servlet container | Apache 2 | 8.0.23 | 2015 | | 11. | Selenium | Web testing | Apache 2 | 2.46 | 2015 | | 12. | Spock | Integration test | Apache 2 | 0.7 | 2012 | | 13. | SonarQube | Code quality analysis | GNU GPL v3 | 5.1.1 | 2015 | | 14. | Jenkins | Continuous integration | MIT | 1.599 | 2015 | ## Installation instructions for Amazon Linux ### Install JDK 1. Run command `uname -a` to determine what Linux version is running on the box. i686 indicates a 32-bit OS and x86-64 indicates a 64-bit OS. 2. Download the correct distribution of the [Oracle JDK](https://github.com/williamjking/FedMedCo/blob/master/http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html) * jdk-8u45-linux-i586.tar.gz for 32-bit OS * jdk-8u45-linux-x64.tar.gz for 64-bit OS 3. Unzip and install the downloaded package in /opt ```Shell sudo mkdir /opt/java cd /opt/java tar xzf jdk-8u45-linux-x64.tar.gz cd /opt/java/jdk1.8.0_45/ sudo alternatives --install /usr/bin/java java /opt/java/jdk1.8.0_45/bin/java sudo alternatives --config java ``` 4. Modify your environment file (for example, for bash, modify .bashrc) ```Shell JAVA_HOME=/opt/java/jdk1.8.0_45 export JAVA_HOME ``` ### Install Grails 1. Download and install [Grails](https://github.com/williamjking/FedMedCo/blob/master/https://grails.org/download.html) - Select 2.5.0 from "Previous Versions" drop down menu ```Shell mkdir ~/grails cd ~/grails/ unzip grails-2.5.0.zip ``` 2. Set environment variables ```Shell GRAILS_HOME=/home/ec2-user/InstalledPrograms/grails-2.5.0 export GRAILS_HOME PATH=$PATH:$GRAILS_HOME/bin export PATH ``` ### Install git ```Shell sudo yum install git ``` ### Install MongoDB 1. Create a `/etc/yum.repos.d/mongodb-org-3.0.repo ` file so that you can install MongoDB directly, using `yum`. ```Shell sudo su cd /etc/yum.repos.d/ vi mongodb-org-3.0.repo ``` 2. Add the following to mongodb-org-3.0.repo ```Shell [mongodb-org-3.0] name=MongoDB Repository baseurl=https://repo.mongodb.org/yum/amazon/2013.03/mongodb-org/3.0/x86_64/ gpgcheck=0 enabled=1 ``` 3. Install Mongod ```Shell sudo yum install -y mongodb-org-3.0.4 mongodb-org-server-3.0.4 mongodb-org-shell-3.0.4 mongodb-org-mongos-3.0.4 mongodb-org-tools-3.0.4 ``` 4. Start MongoDB ```Shell sudo service mongod start ``` ### Install Tomcat 8 ```Shell yum install tomcat8 yum install tomcat8-webapps ``` ### Get the source code from git ```Shell git clone https://github.com/williamjking/Fedmedco.git ``` ### Deploy to Tomcat ```Shell cd FedMedCo git pull grails war sudo su mv target/FedMedCo.war /usr/share/tomcat8/webapps service tomcat8 restart tail -f /var/log/tomcat8/catalina.out ``` ## Continuous Integration Our app is compiled, tests are run, and a code analysis is performed automatically by our [Jenkins continuous integration server](https://github.com/williamjking/FedMedCo/blob/master/docs/ContinuousIntegration.md) every time updates are made to the git repository. ## Monitoring The application is monitored via the the Amazon Web Services (AWS) control panel. See screenshots of our [AWS Monitoring](https://github.com/williamjking/FedMedCo/blob/master/docs/Monitoring.md). ## API Reference [https://open.fda.gov/api/reference/](https://github.com/williamjking/FedMedCo/blob/master/https://open.fda.gov/api/reference/) ## Test [Latest Test Report](https://github.com/williamjking/FedMedCo/blob/master/docs/test-reports/TestReports.md) ## Contributors Lockheed Martin ## Contact Information ### Technical POC Robin Yeman 2345 Crystal Drive, Suite 300 Arlington VA 22202 Email: robin.yeman@lmco.com 571-535-5854 ### Management POC Phil Magrogan 2345 Crystal Drive, Suite 300 Arlington VA 22202 Email: phil.magrogan@lmco.com 703-336-2328 ## License All license agreements are Free and Open Source * [Apache 2.0](https://github.com/williamjking/FedMedCo/blob/master/http://www.apache.org/licenses/LICENSE-2.0) * [MIT](https://github.com/williamjking/FedMedCo/blob/master/http://opensource.org/licenses/MIT) * [GPL-3.0](https://github.com/williamjking/FedMedCo/blob/master/http://www.gnu.org/licenses/gpl-3.0.en.html) * [OpenSymphony 1.1](https://github.com/williamjking/FedMedCo/blob/master/https://svn.apache.org/repos/asf/tiles/framework/trunk/OGNL-LICENSE.txt) * [BSD License](https://github.com/williamjking/FedMedCo/blob/master/http://opensource.org/licenses/BSD-3-Clause)

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：