SWPG Frequently Asked Questions (FAQ)
What is mission of the Scientific Web Programming Group?
The Advanced Biomedical Computing Center?s (ABCC?s) Scientific Web Programming Group (SWPG) provides scientific web application development supporting Leidos Biomedical Research, Inc., the National Cancer Institute (NCI) and National Institutes of Health (NIH) scientists and staff.
How do I obtain SWPG web services?
To obtain services from SWPG, please contact the team at firstname.lastname@example.org to discuss basic requirements and to determine the best path to a completed project.
Where are SWPG?s websites hosted?
Currently, all websites built and supported by the SWPG are hosted and administrated by Information Technology Operations Group (ITOG). All files and databases are housed in one of two data centers: Building 430 at the NCI at Frederick Campus at Ft. Detrick and the other data center is located at the Advance Technology Research Facility in Frederick.
Do websites meet all NIH compliance standards?
All websites developed by the SWPG meet all NIH compliance standards. Some of these standards include, but are not limited to, HHS Web Standards, the use of persistent cookies, Privacy Act – 5 U.S.C. 552a – Sec. 508 of the Workforce Investment Act of 1998, NIH Web Guidance, and Quality of Information Dissemination. For information on NIH compliance standards, please see: Developing Web Sites at NIH
What is the turnaround time for support requests?
Support Requests are answered on a best effort basis. On average, you can expect roughly 1 hour for support responses. Support request resolution varies depending on the complexity of the request. There is a critical option in case of an actual emergency, such as services down. However, we have our own internal monitoring tools that report emergencies and those are treated immediately.
What is your web application development cycle?
We practice an iterative, phased approach to developing web applications. After gathering requirements from all involved parties, each requested feature is prioritized and milestones are created pertaining to each release. A development plan is then established, outlined, and tracked within an internal project management tool. Once development begins, a continuous feedback loop is used to ensure stakeholder satisfaction. From a technical perspective, all code and database constructs are implemented on a development server and versioned with Git. After a particular feature has completed testing, it is elevated to the production environment accessible to the target audience.
For questions or additional information , please contact the Information Systems Program at TalktoISP@mail.nih.gov