Response to Request No. 184388
SLAC
National Accelerator
Laboratory
Technical Proposal for Enterprise Drupal 7 Implementat...
Introduction
We are pleased to submit our proposal to provide design, development, data and content migration,
testing, tr...
Company Profile
About Propeople
Propeople is a full-service creative web agency that provides advanced web development, ele...
Team
Client management team
Michael Drejer
Title: Global CEO & Partner This project: Workshop
Michael is one of the foundi...
Chris Leppanen
Senior Architect, http://drupal.org/user/473738
Chris is a sharp Drupal mind with extensive knowledge and a...
Technical specifications: After the web strategy workshop we already know the project well enough to
start working on the t...
Creative process
A good user experience begins at the intersection of the business/concept, functionality and design.
Ther...
Responsiveness
You’re not just building a website for the desktop computer anymore. We must also target people on
tablets ...
Technical Solution
Overview
Propeople will assist SLAC in setting up the Drupal environments, both Intranet and Internet, ...
Setting up the centralized administration will follow, including all the site components and a site
provisioning tool that...
2 Architecture/Structure
2.1 Development/staging and production
environments for internet and intranet
should be built on ...
4.2 From a central location/console: Ability for
SLAC Web Team to push themes/
branding to targeted internet and intranet
...
4.8 From a central location/console: Ability for
SLAC Web Team to roll bach the version
of Drupal for a site to its previo...
7.4 "All Drupal environments. (Development/
Staging, Production Internet, Production
Intranet), to be secured against comm...
8 Site Provisioning
8.1 A web form that enables the SLAC Web
Team to quickly provision the following
kinds of sites at SLA...
8.7 Up to 100 MB of files, (attachments,
images, etc), can be uploaded by site-
owner to a provisioned site in a
production...
Table 2.1.3 Business Requirements - InternetTable 2.1.3 Business Requirements - InternetTable 2.1.3 Business Requirements ...
4.2 Internal Subtheme A:
A subtheme configured for internet
subsites with the following features:
- Responsive design
- Inh...
2.1.4 Business Requirements - Intranet2.1.4 Business Requirements - Intranet2.1.4 Business Requirements - Intranet2.1.4 Bu...
Upcoming SlideShare
Loading in …5
×

How to Configure CyberSource Secure Acceptance Web/Mobile in Drupal 7

3,294
-1

Published on

One of Propeople’s Drupal experts presents a short tutorial on how to add, manage and configure CyberSource Secure Acceptance Web/Mobile payment system for your Drupal website.

Published in: Internet
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
3,294
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

How to Configure CyberSource Secure Acceptance Web/Mobile in Drupal 7

  1. 1. Response to Request No. 184388 SLAC National Accelerator Laboratory Technical Proposal for Enterprise Drupal 7 Implementation Services March 01, 2013 Version 1.0 Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com
  2. 2. Introduction We are pleased to submit our proposal to provide design, development, data and content migration, testing, training and deployment for SLAC National Accelerator Laboratory. Propeople is looking forward to provide the best value in order to benefit SLAC National Accelerator Laboratory with reasonable pricing and according to the stated design and development requirements in order to create a digital resource that is easy to use, with clean and creative user interface, complex functionality, efficient data management, and high performance. Propeople is a leading Drupal partner with a rich portfolio and extensive experience delivering well thought trough strategy, elegant design and advanced development for some of the leading institutions and organizations in their field such as Stanford Graduate School of Business, Stanford Student Affairs, InfoBlox, Apigee, Maersk, Egmont and others. We have formed a highly experienced team of professionals in their field to meet your expectations and secure the highest quality. We have briefly described each team member, so you may be assured of our strong commitment for your project. We consider SLAC National Accelerator Laboratory a key client and will do the utmost to meet your expectations. Please contact us in case you have any questions about the offer. Sincerely, Michael Drejer Global CEO Propeople Group drejer@wearepropeople.com 650-384-9655 Propeople is a proud supporter and contributor to the Drupal community. Learn more at www.drupal.org Propeople is an Acquia Enterprise Select Partner. Learn more at www.acquia.com ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 2
  3. 3. Company Profile About Propeople Propeople is a full-service creative web agency that provides advanced web development, elegant design, and business-savvy strategy. Founded in 2000, Propeople is now a leader in leveraging cutting- edge trends and technologies. Our team includes over 175+ experienced web specialists from all over the world. We are located in 7 countries: USA, Denmark, Sweden, Austria, Bulgaria, Moldova and Ukraine. We are recognized professionals with key industry awards and speakers at international conferences. Our experience and track record ensures a high quality solution for every project. We love what we do, and we’re enthusiastic about our many client partnerships. We strive for simplicity and elegance in our design, and relentlessly work to build efficient sites that connect with and engage the end user. We can proudly state that “Propeople never lost a client” while developing more than 800 advanced web solutions over the past 12 years. Our specialty Propeople combines the best of strategy, user interface and technology to ensure your success. Whether we’re delivering bold new ideas or simply offering creative guidance, we align with your goals and budget while helping you advance in new directions. We strive to create the best possible experience for the end user, and to ensure that every site we create fulfills its purpose. To achieve this, we deliver a unique visual style that balances the elements of color, contrast ratios, usability, readability, and media compatibility. We’re always up-to-date with the latest trends and best practices in web development in order to create outstanding online experiences. Technology is about understanding the end user and making their visit to your site personal, relevant, and creating the best online experience possible. Leader in Drupal Propeople is an Acquia Enterprise Select Partner and offers exceptional Drupal expertise and unique vertical application experience to design and implement advanced Drupal-based solutions that leverage Acquia's products and services. Over the last six years, Propeople have delivered more than 400 complex Drupal solutions. By selecting Propeople, an Acquia Enterprise Select Partner, you can be assured that you are working with a team committed to the highest standards of quality, innovation and success in Drupal. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 3
  4. 4. Team Client management team Michael Drejer Title: Global CEO & Partner This project: Workshop Michael is one of the founding partners in Propeople, his main role in this project will be during the kick start of the project where he will participate in workshops related to site concept, content strategy and UX. Mihai Moscovici Title: COO This project: Client Manager Mihai has been with Propeople for more than four years. Mihai has been handling most of our high-end clients. Mihai will be in charge of Arcade as a client in Propeople and he will participate in all relevant meetings to ensure a hight client satisfactory! Creative team Michel Testmann Samucha Title: Creative Director & Partner This project: IA, UX, Design Michel is one of the founding partners and has been with Propeople for more than 12 years. Michel is an expert when it comes to out-think online concepts based on client strategy and then implement them into a user friendly, easy to understand, self-explaining and simple solution. Michel oversee all design projects across the Propeople offices. Technical team Oleg Ciubotaru Title: CTO & Partner This project: Project Manager Oleg has been with Propeople for more than three years. During this time Oleg has established himself as a high-end technical architect among our clients. At Stanford GSB, Student Affairs Oleg is also appreciated as a very skillful Project Manager. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 4
  5. 5. Chris Leppanen Senior Architect, http://drupal.org/user/473738 Chris is a sharp Drupal mind with extensive knowledge and a phenomenal Drupal architect. Chris is the mastermind behind one of the most demanding specifications developed by Propeople for Stanford, particularly for Stanford GSB. His role is to architect the system, code review all sources to be within Drupal standards and ensure the high performance of the website. Chris maintains one of the most important data migration modules on drupal.org “feeds”. Yuriy Gerasimov Senior Architect, http://drupal.org/user/257311 Yuriy is a Senior Drupal Architect that recently joined Propeople. Previously Yuriy was a Senior Dev. Lead at Trellon. He is one of the main developers and maintainers of the “Service” module on Drupal.org He has been involved in various Drupal projects at Stanford related to performance, architecture and more. Web development process It is important to Propeople to collaborate with their clients and it is better that we create a transparent environment right from the beginning of our collaboration. We will present a general overview of the milestones that we usually apply on our projects and that we intend on using with SLAC, further on gathering information from sprint plans and creating a full and detailed time plan for you. However, we are quite flexible and are able to agree upon the development plan and milestones along with SLAC before the development workflow begins. We usually split up the process of implementing our projects in several stages, but we can still work on this according to your needs. We will present an overall description of each one of them in this section: Discovery and Strategy: Discovery Meeting: Propeople will be onsite with the client to have a number of discovery meetings. The purpose of the discovery meetings  is to meet the key persons responsible for the project, understand the clients organization and further evolve our understanding of the business drivers and the decision making and approval processes.   Discovery workshop: We will then meet again to run the Strategic Discovery Workshop and get a better understanding about the organizational purpose and goals, target audiences and success metrics. Planning Scope run: Propeople will facilitate a meeting/workshop in order to gather detailed and in-depth information about the new solution. Based on the workshops, talks, interviews and the client’s internal requirements, we will outline key priorities and will create a high level project scope. Web strategy: Propeople will run a full day web strategy workshop in order to gather information and create the client's web strategy. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 5
  6. 6. Technical specifications: After the web strategy workshop we already know the project well enough to start working on the technical specifications that should be implemented that describe the scope of the project in a technical language, broken down to small details. Development cycle Technical documentation is prepared and tasks are assigned to the lead developer. After this all the tasks are divided between specific developers (depending on the project size, we could assign multiple development teams). You can find more information in the Implementation Approach section. Each phase will be documented and knowledge sharing sessions will be done throughout the development cycle, ensuring the SLAC technical team stays up to date with the steps implemented during the workflow. Internal QA Propeople tests the consistency of the new website internally and makes sure the UX lives up to the standards. In addition to that the QA department makes a full cross-browser testing in order to make sure everything works properly. Deployment and release We deliver the final solution, set it up on your server and launch online. We’ll assist you to maintain the system and further extend the functionality according to your needs. More detailed information can be found in the Deployment section of this document and specific solutions will be delivered during the project workflow. Implementation Approach The development of a project demands finding the best solution, both from the development and the front end point of view. Propeople ensures that projects are finished within the agreed deadline, budget, scope and quality. The specific purpose of the pre-phase discussions is intended to facilitate an expectation- tuning to ensure a clear common goal. Working closely with the client is the best way for us to understand the clients’ mission, vision and goals. We go through several phases, in order to ensure an organizational path so that both our team and the client get a better understanding of how we can present a good development solution. Propeople will use the methodology preferred by SLAC team. We can work agile and with SCRUM. We suggest that we mutually agree on a detailed methodology in order to achieve the best possible fit. We suggest using partly Scrum with sprints divided for different tasks compilation – this would ensure a logical workflow, as well as successfully meeting deadlines. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 6
  7. 7. Creative process A good user experience begins at the intersection of the business/concept, functionality and design. Therefore, it is important to always facilitate the development process where both the client as well as the technicians and creative persons, have the opportunity to be heard and to participate actively. The specific purpose of pre-phase discussions is intended to facilitate an expectation-tuning, to ensure a clear common understanding of SLAC’s goals. Iterations within the hub The creative process for redesigning the SLAC website will be split into several iterations. This means that for every iteration we will get closer to the final result. We believe that easy communication and also being able to iterate fast is a part of creating something great. The project hub will allow us to do just that. Each iteration ends with a direct meeting with the SLAC team. In between iterations, we would suggest having as many meetings/meet ups needed in order to end up with the best outcome possible. Please note that if the desired result is not reached at the final iteration, further iterations will be estimated. Each iteration will be estimated based on what improvements and requirements are found on the way. Concept Clarification workshop To assist you best - both now and in the future - it is essential that we have a common understanding of your product objectives and strategic priorities.We propose that meeting at a workshop where we could review the solution's objectives and gain the necessary insight into your thoughts about the purpose, challenges and opportunities in the solution. That way, we can build on the knowledge you already have instead of starting from zero. The purpose is to identify and prioritize content elements from the strategic objectives. The ultimate goal is to obtain the necessary business insight so that we’re able to visualize the user behavior.This workshop is also about having fun! We’ll brainstorm, draw, and come up with all kind of cool UX ideas that we can sort from later on in the design process. Conceptual site-map Based on the accumulated knowledge from the Conceptual Clarification Workshop, we will begin to work on a conceptual site-map. This will include general thoughts and ideas, and how these are implemented in a potential user-flow. Sketches - Mobile first The number one rule for designing a responsive website is that we start with mobile first. What it means is that we should start prioritizing for that viewport (screen) first. The reason for starting with mobile is that it forces us to prioritise and think simple. Simplicity in both content and design is a very important factor when building a responsive website. Before starting building the actual prototype, it is important that we have a really good understanding of what page types and elements we would need to build. This is when sketches come up into the picture. During the workshop we will draw low fidelity sketches as a part of a brainstorming process. The sketches will later be improved and iterated upon so that it meets your intended goals. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 7
  8. 8. Responsiveness You’re not just building a website for the desktop computer anymore. We must also target people on tablets and smartphones. The smartphone and tablet market is huge and still growing. It is very important to make a platform that communicates to all users, most devices and viewports. This way we will ensure that your new website will be somewhat of a future proof. High Fidelity Responsive prototype Building high fidelity Responsive prototypes is really useful for understanding how your new website will act in real time. The prototypes are built in html5 and css3.The real beauty is that the prototypes will be viewable from any newer browser and you will be able to test how they work, instantly, on all viewports (desktop, tablet, smartphone). What’s important to be able to understand quickly is - behavior and user- experience. User-experience means everything and that’s also why we came up with this method of building prototypes. So that we’re able to understand what really happens when a user interacts with a website. The prototypes allow us to see the behavior and experience of any change that we make, almost instantly. That makes it very easy for us and you to communicate what we want to accomplish with a certain feature or page. Visual design workshops and graphic implementation according to the brand guidelines During the initial visual design workshop, we will collect information from you about your design preferences. What’s really important to us before we start designing anything is that we understand you. We are aware of the fact that you have a pre-made mood-board and a full set of design guidelines. That said, we still need to get “under your skin” to really understand what your wishes are for a visually stunning website. We need you to inspire us to come up with some great ideas. The most important thing to remember at this stage though, is to focus on a "design" that will enhance the intended communication, strategy, business goals, usability and user experience. Principle Design Based on the information gathered at the design workshop, we will prepare an overall design concept. We will prepare 2 different versions of 2 different pages. Our main goal is to focus on improving usability and communication according to your primary purpose. The design will be presented in a direct meeting with you. Usage of the principle design on all page types Based on the approved principle design, we will design the other approved pages and page types. We can talk through the option of going with the described creative process, and you can see a version of proposed estimates (Design - Version 1) along with this proposal. However our creative department has also come up with a second estimations version (Design - Version 2) of estimates that includes only the design and wireframes delivery to SLAC, created according to the specifications described in the RFP.   ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 8
  9. 9. Technical Solution Overview Propeople will assist SLAC in setting up the Drupal environments, both Intranet and Internet,  as well as through the developing and design process, offer trainings and documentation upon agreement, ending up with offering maintenance and support possibilities if needed. A thorough research is needed in order to come up with details on improved information architecture as well as improved navigation solutions for the SLAC website, along with offering the best solution for the secure Intranet and other functionalities needed by SLAC (like “reducing confusion for users requesting for a new website” as stated in the RFP for instance). Propeople has a vast experience in working out and offering feasible solutions for complex projects regarding both: visual design and web development. We also have a broad experience in assisting complex projects in the deployment process, as well as offering the needed detailed documentation and trainings on that. We follow a transparent workflow during the development, testing and deployment process, hence any changes on the environments: Development, Staging and Production (only agreed with the SLAC team) can be overviewed and approved by the client or the responsible technical team for the project, coming up with questions or corrections during the workflow. We tried to answer to all of your concerns stated in the RFP, following the steps you have mentioned in the charts and asked to be followed in the technical proposal. Of course there is much research to be done yet in order to ensure the best possible solution that would suit your needs and the needs of your visitors and users, but this can be implemented in the discovery phase of our collaboration further on. Propeople is looking forward to working on a project as complex as SLAC promises to be. We would be glad to assist you in developing the long-term Web Road Map that you have in mind, offering our expertise in the design, web development process and especially in working with Drupal. Phase I - Implementation of Enterprise Drupal 7 for SLAC Is the most complex envisioned phase and will include most of the implemented functionality. It will include the discovery workshop and the design process, setting project milestones to a final decision with the SLAC responsible team members and proceeding to the whole design and development process itself. The system architecture will be set up at this point, along with setting up the system access, needed accounts and the version control and deployment workflow. This will also include the project setup ( i.e. the two environments - Intranet, Internet and the Dev environment) and setting up firewall rules where each subnet will be separated for these environments. This step will be finalized with the implementation of the design/architectural document that will be iterated if needed with the SLAC team and delivered upon approval. A test plan document will also be delivered, detailing the so far implemented functionality. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 9
  10. 10. Setting up the centralized administration will follow, including all the site components and a site provisioning tool that will also be attached to the new Drupal instance. This will include the implementation of automation scripts and web service API’s. Each development sub-phase will be accompanied by knowledge sharing from the Propeople team working closely with SLAC. It will be provided in written form or any other preferred training method. After the installation and configuration of both environments, we will proceed with adding up the functionality stated in the technical specifications and the approved estimates. Our developers would suggest using a shell script called by Drupal/Drush to add a new apache Virtual Host to an existing host, so that new websites within the intranet for instance could be created. The process of adding up an additional host to the pool will be quite intuitive, but will however support the needed knowledge sharing from Propeople. We will come up with more precise solutions for the most important functionalities after the discovery phase of the development process. You can find a more detailed technical solution for the functionalities stated in the RFP in the comments provided below for entire development phase.! Phase I.a – Configuration of SLAC Internet and Intranet Environments Table 2.1.2 Business Requirements - Common to Internet AND IntranetTable 2.1.2 Business Requirements - Common to Internet AND IntranetTable 2.1.2 Business Requirements - Common to Internet AND IntranetTable 2.1.2 Business Requirements - Common to Internet AND Intranet Key Requirements WorksheetKey Requirements WorksheetKey Requirements WorksheetKey Requirements Worksheet # Criteria Complies (yes/no) Comments 1 Access 1.1 Authentication required to manage websites (e.g. content authors, system administrators, developers) yes Single sign-on authentication based on CROWD and WebAuth modules. 1.2 Authentication performed against WebAuth or CROWD to authenticate SLAC Unix or CROWD user accounts yes Use CROWD Drupal module and WMD (WebAuth module: http:// drupalfeatures.stanford.edu/project/ webauth) 1.3 Federal Section 508 Accessibility Compliance: The current rules and standards of the Federal Government for handicapped accessibility will be complied with troughout all sites, specifically Section 508 yes Propeople will comply with the Accessibility Compliance 508 both in the development and design process, respecting the needed regulations on different functionalities where it will be possible to apply ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 10
  11. 11. 2 Architecture/Structure 2.1 Development/staging and production environments for internet and intranet should be built on a scalable arhitecture with respect to content storage, system capabilities and performance. It should be easy to add additional hosts to the pool(s). yes A shell script called by Drupal/ Drush to add a new apache VirtualHost or an alias to an existing one. Add apache user to sudoers for this script. 2.2 Production environments for internet and intranet configured with Drupal web-front- end running on dedicated server, connecting to centralized MySQL service for content database yes Drupal front-end configuration environment will manage site configurations, database connections, deployment workflows and backup strategy. 2.3 Development/staging environments for internet and intranet configured with Drupal web-front-end running on dedicated server, connecting to centralized MySQL service for content database. yes Drupal front-end configuration environment will manage site configurations, database connections, deployment workflows and backup strategy. 3 System Administration 3.1 Configuration management tools and practices required to maintain the production and development environment servers should integrate with or directly utilize SLAC's existing configuration management tools and practices. New tools and practices may be introduced by the vendor if verified and approved by the SLAC Systems Administration teams impacted yes Common best practices and server administration tools will be used to manage and maintain production and development environment servers. Drupal front-end configuration environment will use standard and custom Drush commands and custom shell scripts to perform various administrative tasks. These commands will also be availlabe from command line terminal. 3.2 Backup and recovery procedures configured and documented for the SLAC Application and Database Administration team. yes Backup/recovery scripts accessible as a Drush command and/or from a Web wizard on Drupal configuration environment. 4 Centralized Site Administration 4.1 From a central location/console: Ability for SLAC Web Team to track and audit the different versions of Drupal being used by the sites across the internet and intranet, as well as the associated modules for each site, and their versions. yes A central administrative console will use Drush commands to pull information about modules versions and status across all environments/ sites. Modules versions information will be also available from the make file from each site. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 11
  12. 12. 4.2 From a central location/console: Ability for SLAC Web Team to push themes/ branding to targeted internet and intranet sites. yes Available themes for each site will be included in installation profile for current site. Additional themes/modules will be added to make file and a set of commands will be run to refresh the code on target environment/site and run the database updates. 4.3 From a central location/console: Ability for SLAC Web Team to configure Drupal core updates and deploy to targeted internet and intranet sites. yes Each site will have a separate make file which includes Drupal core version. The make file will be editable and there will be the option to switch to a different core version. Drupal front-end configuration environment will have a wizard tool to create/update make files. 4.4 From a central location/console: Ability for SLAC Web Team to manage the set of Drupal modules/ apps available to site- owners for configuring sites yes "The main modules repository will be managed from a central location/console via command line/ graphical version control tools. Repository managing options will also be available from Drupal front- end configuration environment. 4.5 Site-owners cannot install Drupal modules/apps that are not in the approved set of modules provided by the SLAC Web Team yes Site-owners will be limited to chose modules and features from the ones defined and built by make file. 4.6 From a central/location/console: Ability for SLAC Web Team to add Drupal modules/ apps and push updates to modules/apps in the set available for new intranet and internet yes All new modules and updates to existing ones will be pushed to the file repository. The repository will consist of separate git repositories for each module/feature and will be branched/tagged based on versions. In the site provisioning/update wizard, SLAC Web Team will have the option to chose between different module versions. 4.7 From a central location/console: Ability for SLAC Web Team to push modules/apps and updates to modules/apps to targeted existing intranet and internet sites yes Installed profile (make file) will be editable from Drupal front-end configuration environment and will have an option to re-deploy the build to targeted site. Additional commands as backing up the database and applying database updates will be triggered on deploying a new build. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 12
  13. 13. 4.8 From a central location/console: Ability for SLAC Web Team to roll bach the version of Drupal for a site to its previous version, if necessary (e.g. site is corrupted or loses functionality due to the version upgrade/update) yes The list of previous builds will be available on the administrative dashboard with the option to revert the site to a previous build and database. 5 Themes and Design 5.1 "Responsive Design used for design/ layout of site elements in all configured internet and intranet themes to ensure appropriate appearance maintained across platforms and different display configurations, including but not limited to: - Desktop monitor - Laptop - Tablet - Mobile yes We agree on using responsive design and will contribute with our knowledge sharing further on in the discovery phase 6 Customizations/Development 6.1 Customizations to be developed and delivered as Drupal Features (for easy re- use and sharing) yes "All configurations will be wrapped in features grouped by functionalities. These features will be selectable on creating a new site install profile. 7 Security 7.1 The production internet Drupal environment should be installed in its own subnet, secured from other subnets at SLAC yes Create a separate VLAN for production environment. Configure port forwarding rules. SLAC network administrators will set up the network with technical assistance from Propeople. 7.2 The production intranet and development/ staging Drupal environments should be installed a separate subnet, secured from other subnets at SLAC yes Create a separate VLAN for development/staging environment. Configure port forwarding rules. SLAC network administrators will set up the network with technical assistance from Propeople. 7.3 Firewall rules are configured for each Drupal subnet to permit the minimal set of port connections to/from the rest SLAC's network for Drupal environments and configured sites to function correctly yes Configure the minimal set of ports to enable normal working environment for web servers. SLAC network administrators will set up the firewall rules with technical assistance from Propeople. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 13
  14. 14. 7.4 "All Drupal environments. (Development/ Staging, Production Internet, Production Intranet), to be secured against common remote code execution attacks, including but not limited to the following types: - Exploiting register_blogals in PHP - XMLRPC for PHP vulnerabilities yes register_globals will be off. Update Drupal core and contrib modules to the latest stable versions. 7.5 All Drupal environments, (Development/ Staging, Production Internet, Production Intranet), to be secured against common SQL- injection attacks yes All SQL queries will be run using Drupal database API abstraction layer. 7.6 All Drupal environments, (Development/ Staging, Production Internet, Production Intranet), to be secured against common cross-site scripting attacks yes All user submitted data will be sanitized when displaying in browser according Drupal best practices. 7.7 All web forms in the internet and intranet to have their inputs automatically sanitized/scrubbed for dubious or malicious content yes All form data will be checked/ validated. All forms will be created using Drupal form API to prevent CSRF attacks. 7.8 Captcha widget automatically included for all web forms to prevent automated form submissions. yes Use reCaptcha to comply with the Federal Section 508 Accessibility Compliance. 7.9 All test accounts, code and content removed from all Drupal environments before environments go live yes A general content and user cleanup script will be run before going live. 7.10. All Drupal environments, (Development/ Staging, Production Internet, Production Intranet), to be secured against common username enumeration attacks (e.g. apply consistent login-error messages that don't disclose if a valid username has been submitted)) yes Default Drupal login behavior have the same error message both for invalid login or password. 7.11 Drupal Core, and all installed Drupal modules/apps need to be in compliance with SLAC's security protocols and standards in all configured Drupal environments (SLAC Cyber-Security team will perform scans to validate solution compliance) yes We will make sure to choose the modules and functionality solutions with the highest security level. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 14
  15. 15. 8 Site Provisioning 8.1 A web form that enables the SLAC Web Team to quickly provision the following kinds of sites at SLAC: - Internet: * User Site * Group Site * Departmental/Directorate sites - Intranet: *Institutional Site - Extranet: * Joint Institute/collaboration Sites yes A site provisioning wizard on Drupal configuration environment with a set of options to select the site type, available features and site details and general settings. 8.2 The Site Provisioning web form requests the following information for a new site: - Site Type (see 8.1 above) - Site Name - Site Description (brief) - Site Owner - Site Theme: * 2 subthemes available for internet sites * 1 subtheme available for intranet sites yes The Site Provisioning web form will include requested fields and additional ones that will be more precise after discovery phase. 8.3 Site Provisioning functionality/component should be available in production and development environments for both internet and intranet yes We can build one site provisioning tool for all environments in order to make it easy transferring data from one environment to the other. 8.4 Authentication required to access the Site provisioning tool yes General authentication module based on CROWD and WebAuth will be used. 8.5 Only the SLAC Web Team has permission to provision a new site using the Site Provisioning tool at this time, with flexibility built-in to allow more users to use the Site Provisioning tool at a later date. (Permissions can be granted to groups) yes Roles will be assigned on user creation. New users will be created on first login from WebAuth or CROWD according to their group membership. A special permission will be created for accessing site provisioning wizard. This permission can be granted to one or many roles (user groups). 8.6 Site Provisioning component/functionality to be provided as a web service, with flexible API design to allow for future growth with respect to types of sites allowed, new themes, and other potential parameters, (Web form makes calls to the web service) yes Services module will be used as a framework to build custom resources and methods for site provisioning tool. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 15
  16. 16. 8.7 Up to 100 MB of files, (attachments, images, etc), can be uploaded by site- owner to a provisioned site in a production or development environment. yes A custom module will validate and limit file upload forms according to site quota. 9 System Performance 9.1 Low Bandwidth Accessibility (1-2 Mbps): All internet and intranet websites should be available to locations with low bandwidth internet access, including mobile. The technical footprint should be light enough that users can view pages and documents without excessively long downloads. yes Site frontend will be optimized and compressed. CSS Sprites technique will be used to group images in order to decrease the total image size and the number of http requests. 9.2 Normal- High Bandwidth Accessibility (>2Mbps): Production and development environments should be configured such that 99+% od all sire pages take <= 2 seconds to load. yes Various performance improvement techniques will be used to improve site response time such as: - full page cache for anonymous users with Varnish; - caching blocks, views and panes with Memcached; - cache all content for longer time and invalidate the cache on content update; - aggregate frontend elements (js, css, images) 9.3 Production and development environments have automatic failover and redundancy to minimize site down-time during patch cycles or system issues. yes RAID1 for data mirroring and hot- swap hardware capability for replacement of failed units (HDD and power supply). Master/Slave architecture for database servers. Scalable web server architecture with support of multiple web servers behind a load balancer. 10 Roles and Permissions 10.1 Ability for the Web Team to map users' groups to roles, so the user automatically has the appropriate permissions on login to a site(e.g. Web Team staff member is automatically assigned the role of Administrator for any site, on login) yes New users will be created on first login from WebAuth or CROWD. Roles will be assigned on user creation. A configuration form for admins to map user groups to Drupal roles. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 16
  17. 17. Table 2.1.3 Business Requirements - InternetTable 2.1.3 Business Requirements - InternetTable 2.1.3 Business Requirements - InternetTable 2.1.3 Business Requirements - Internet Key Requirements WorksheetKey Requirements WorksheetKey Requirements WorksheetKey Requirements Worksheet # Criteria Complies (yes/no) Comments 1 Access 1.1 All published content is anonymously accessible. Yes Standard Drupal Behavior 2 Modules 2.1 Modules for internet and intranet need to support: - Events - Calendars - News Articles + RSS Feed - Form Building - Blogs - Wikis Yes Each of the modules will be implemented as Drupal feature which will contain related contrib modules, custom implementation modules, content types, views, blocks and other settings. 3 Site Provisioning 3.1 Naming conventions should be applied/ standardized to differentiate between and avoid naming clashes with user site home directories, and group site home directories (e.g., prepending the same prefix in front of each user site, and prepending a different prefix in front of all group sites). Yes A special naming convention pattern will be used to avoid naming clashes. 4 Themes 4.1 Internet Base theme configured for SLAC's top-level internet website, using responsive design. Theme branding to be based on SLAC's internet branding (see SLAC Design Guide for branding details), but with top navigation drop-down menus extended to allow for third tier of navigation, and left navigation extended to allow for fly-out menus. Yes We might suggest installing an extension of Open Framework as a base theme. This is a responsive Drupal theme based on Twitter Bootstrap ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 17
  18. 18. 4.2 Internal Subtheme A: A subtheme configured for internet subsites with the following features: - Responsive design - Inherits from internet Base theme - Same core-branding as Internet Base theme, but allows for co-branding of site by site-owner - Has left-navigation and top navigation Yes We will use an extension of the base theme suggested above 4.3 Internet Subtheme B: A subtheme configured for internet subsites with the following features: - Responsive design - Inherits from Internet Base theme - Same core-branding as Internet Base theme, but allows for co-branding of site by site-owner - Has no left navigation, only top navigation. Yes We will use an extension of the base theme suggested above 4.4 Central repository for storing web assets employed by all internet themes, and which are shared by other public-facing sites (global headers/footers, JS, CSS, etc.). yes We can share headers and footers in .inc files. This will update all the themes on all sites if we include them. Shared CSS and JS that are served remotely will not be aggregated and can impact performance. No problem serving assets. Varnish can cache files for performance. The solution can be changed after the discovery phase - when we'll have more information. 5 Roles & Permissions 5.1 The following roles should be configured by default for all internet sites: - Author - Editor - Site Owner/Manager - Administrator - SLAC Collaborator (extranet)" yes Roles will be created as part of installation process. 5.2 Roles should automatically be mapped/ applied to users, based on their group membership (e.g., a Web Team staff member is automatically assigned the role of Administrator for any site, on login). yes Roles will be assigned on user creation. New users will be created on first login from WebAuth or CROWD according to their group membership. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 18
  19. 19. 2.1.4 Business Requirements - Intranet2.1.4 Business Requirements - Intranet2.1.4 Business Requirements - Intranet2.1.4 Business Requirements - Intranet Key Requirements WorksheetKey Requirements WorksheetKey Requirements WorksheetKey Requirements Worksheet # Criteria Complies (yes/no) Comments 1 Access 1.1 Authentication required to view SLAC intranet sites/pages when accessed from off-side and not VPN'ed in. Yes SLAC Drupal authentication custom module (WebAuth + CROWD). Additionally we can enable Apache http authentication for users accessing the site from a non SLAC network. 1.2 No login required when viewing SLAC intranet sites/pages on SLAC's network (on-site at SLAC or via SLAC's VPN) Yes "Requests from SLAC network will bypass Apache http authentication. Additionally authentication module can check the visitors IP address and can automatically log them in as a generic user." 1.3 Single-sign-on: Following the initial login for accessing an intranet site, all other intranet sites are available without further logins being required by the client, until the session expires. Yes CROWD and WebAuth implementing single-sign-on. When a visitor open a page and he has no active session, the custom authentication module will provide a custom login page with the options to chose the type of authentication (WebAuth or CROWD). A cookie can be set to hold the authentication method in order to skip that page in future. 2 Modules 2.1 The core set of modules for the intranet needs to include the following: - Panels - Events - Calendars - News Articles + RSS feeds - FAQ's (integration of the FAQ and FAQ ASK modules) - Service Catalog (use Stanford's?) - Collaboration (Drupal Commons?) - Blogs - Wikis Yes Listed modules will be added and custom modules/features will be created. We can implement collaboration features needed from Drupal Commons in Drupal without using the distribution. 4 Themes ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 19
  20. 20. 4.1 Intranet Base theme configured for top- level intranet website, using responsive design. Theme branding to be based on SLAC's intranet branding, but with top navigation drop-down extend to allow third tier of navigation, and left navigation extended to allow for fly-out menus." Yes We might suggest installing an extension of Open Framework as a base theme. This is a responsive Drupal theme based on Twitter Bootstrap. The theme will then be customized according to the branding needs or any other specifications 4.2 Intranet subtheme configured for intranet subsites, using responsive design, and which inherits core aspects from the Intranet Base theme. Similar branding to Intranet Base theme, but allows for co-branding of the site by site-owner. Yes We will use an extension of the base theme suggested above, along with the needed customizations 4.3 Central repository for storing web assets employed by all intranet themes, and which are shared by other internal-facing sites (global headers/footers, JS, CSS). Yes We can share headers and footers in .inc files. This will update all the themes on all sites if we include them. Shared CSS and JS that are served remotely will not be aggregated and can impact performance. No problem serving assets. Varnish can cache files for performance. The solution can be changed after the discovery phase - when we'll have more information. 5 Roles & Permissions 5.1 The following roles should be configured by default for all intranet sites: - Author - Editor - Site Owner/Manager - Administrator - SLAC Staff - SLAC User - SLAC Collaborator" Yes Roles will be created as part of installation process. 5.2 Roles should automatically be mapped/ applied to users, based on their group membership (e.g., a SLAC staff member is automatically assigned the role of SLAC Staff on login). Yes Roles will be assigned on user creation. New users will be created on first login from WebAuth or CROWD according to their group membership. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 20
  21. 21. Phase I.b – Implementation of SLAC Intranet Gateway Page 2.2.22.2.22.2.22.2.2 Key Requirements WorksheetKey Requirements WorksheetKey Requirements WorksheetKey Requirements Worksheet # Criteria Complies (yes/no) Comments 1 Access 1.1 Site to be hosted on SLAC's intranet, so authentication required to access all published content on the website. Yes General authentication module based on CROWD and WebAuth will be used. 2 Architecture/Structure 2.1 Site will consist of one (1) landing page, with up to five (5) supporting pages (e.g., custom error messages). Yes Architecture to be implemented according to the designs and technical specifications 3 Themes and Design 3.1 Base intranet theme is set as the theme for this site - all pages in the site use this theme. Yes Intranet site will be generated/built with intranet base theme enabled by default. 3.2 Apply SLAC's responsive design content hierarchy rules througout the SLAC intranet website. (See SLAC Design Guide document for details). Yes Intranet theme will provide responsive behaviour which will be configured to match SLAC Design Guide requirements. 4 Key Site Features 4.1 Home Page: - Top 5-7 news articles from the SLAC Today auto populated - Top 3-5 Science/Mission news articles (manually generated) - Links link to event Calendar - Option to subscribe to a daily email that contains the content of the home page - Interactive search box with separate search fields for people and web - Top Employee Resource links" Yes Different searches can be done with different filter criteria. Cron will be used to send daily updates of homepage articles. 4.2 Staff Resources Page: migrate the staff resources page from the SLAC main site (http://www6.slac.stanford.edu/general/ staff-resources.aspx) to the intranet portal and apply the new theme to it. Yes Manually migrated as a panel page with custom content blocks and JS menus. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 21
  22. 22. 4.3 A-Z site index page Yes We will use Views to accomplish this. 4.4 Lightbox functionality: *Ability to download full resolution images from the lightbox display. *Lightbox image sizes standardized." Yes Views & Image Styles will allow that. Phase II – Migration of SLAC Home Website to Drupal 7 The second phase will continue with the migration of the content from the actual platform(TeamSite/.Net) of the SLAC website to the Drupal 7 instance.  Starting with content types and menus, we will continue with the pages and all the content blocks. We will implement the News content migration automatically, most probably with the Feeds module. We will also implement manual migration for the rest of the content on the website, meaning more time has been estimated for this processes in the development process. Documentation will be provided as stated in RFP for the sections needed by SLAC and knowledge sessions will be done accordingly. Phase II.a – Migration of SLAC Home Website from TeamSite/.NET 3.1.2! Business Requirements3.1.2! Business Requirements3.1.2! Business Requirements3.1.2! Business Requirements Key Requirements WorksheetKey Requirements WorksheetKey Requirements WorksheetKey Requirements Worksheet # Criteria Complies (yes/no) Comments 1 Access 1.1 Site to be hosted on SLAC's internet, so all published content is anonymously accessible. Yes Standard Drupal behavior. 2 Architecture/Structure 2.1 Site structure/map should match the current SLAC home website. Yes A panel page with all region blocks placed according current design. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 22
  23. 23. 3 Theme and Design 3.1 Base Internet theme is set as the theme for this site - all pages in the site use this theme. Yes Internet site will be generated/built with intranet base theme enabled by default. 3.2 Apply SLAC's responsive design contect hierarchy rules throught SLAC Home website. (See SLAC Design Guide document for details) Yes Internet theme will provide responsive behaviour which will be configured to match SLAC Design Guide requirements. 4 Page Templates 4.1 Home Page: A one-off template for the home page of the site. Page is highly graphical, with text, links, and videos interspersed. Main feature is a large banner carousel displaying several graphics that link to news stories, and which cycle periodically (slideshow). 1 pages based on this template: -slac.stanford.edu Home page Yes Panel page with content views and slideshow views. 4.2 1-Coulumn Page: A page containing a wide body content column in the middle ,with no left or right navigation columns. Main body content can contain text, graphics, videos, quote highlights, links, graphic-gallery, and/or buttons 1 pages based on this template: - Footer > Privacy Notice Yes One column node view panel page template. 4.3 2-Column-Left-Nav Page: A page containing a narrow left- navigation column, and a wide body content column to the right. Main body content can contain text, graphics, videos, quote highlights, links, graphic- gallery, and/or buttons 3 pages based on this template: - About > Contact SLAC - Research > Scientific Programs - Visiting SLAC > Lodging Information" Yes Panel page variant for node view with left-nav menu block. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 23
  24. 24. 4.4 2-Column-Right-Nav Page: A page containing a narrow right- navigation column, and a wide body content column to the left. Main body content can contain text, graphics, videos, quote highlights, links, graphic- gallery, and/or buttons 3 pages based on this template: - Footer > Careers - Footer > Safety - Global header > Research Resources" Yes Panel page variant for node view with right-nav menu block. 4.5 3-Column Page: A page containing a narrow left- navigation column, a narrow right- navigation column, a narrow right- navigation column, and a wide body content column in the middle. Main body content can contain text, graphics, videos, quote highlights, links, graphic- gallery, and/or buttons 35 pages based on this template: - 6: All landing pages - 6: Top six About pages - 8: Top eight Research pages - 3: Top three Facilities pages - 2: Top two News pages - 3: All Community pages - 2: Top two Visiting SLAC pages - 2: News Archive pages - 2: Press Release Archive pages - 1: Staff Resources page (classic look) Yes Panel page variant for node view with right-nav and left-nav menu blocks. 4.6 News Article Page: A page containing a wide body content column on the left, with a narrow right- hand-side column listing graphics/medis related to the article. Main body content can contain text, graphics, videos, quote highlights, links, and/or buttons - 200 pages based on this template" Yes Panel page variant for news nodes view with a right column containing various informative blocks related to the article. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 24
  25. 25. 4.7 Site Index Page: A one-off page template containing a full site index, database-driven, which can be navigated alphabetically. Page body contains only text and links. 1 pages based on this template: - Footer > Site Index" Yes We will use Views to accomplish this. 4.8 Staff Index Page: A one-off page template containing sets of links useful to SLAC staff. Page body contains graphics, text, links, and a navigation carousel. 1 pages based on this template: - Global Header > Staff Resources" Yes Panel page using 3 columns stacked layout with custom content blocks and JS menus. 4.9 Site Feedback Form: A one-off page template of a web form that allows users to provide feedback to SLAC. Form contains several text fields, a drop-down menu, and a submit button. 1 pages based on this template: - Footer > Site Feedback" Yes Standard page with a Feedback Form block attached. 4.10 Contact Form: A one-off page template of a web form that allows users to contact the Communications office at SLAC. Form contains several text fields, a drop-won menu for query topics, and a submit button. 1 pages based on this template: - About > contact SLAC Yes Standard page with a Contact Form block attached. 5 Current Key Site Features 5.1 Home Page Carousel/Slideshow: A carousel banner that switches graphics each time the page loads, and also contains navigation controls for user to select from the available slides. Yes Views slideshow module ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 25
  26. 26. 5.2 Home Page News Highlights: The three latest headline news articles should be automatically updated on the home page when new articles are created (dynamic update). Yes Views module. View sorted by date. 5.3 Maps & Directions: In the Maps & Directions page (under the Visiting SLAC section), user can get directions to SLAC, embedded into the page (powered by Google gadgets). Yes Use Get Directions module or just embed HTML provided by Google gadgets, depending on requirements. 5.4 News Archive and Press Release Archive: News and press release articles should be automatically added to the appropriate archives pages on creation. Yes We can use Views filtered by date to display archived News/Releases, or have a flag on them to make them archived. 5.5 Media Lightbox: Graphics and videos on select pages in the website should appear in a lightbox when clicked. Yes Media Gallery module provides this functionaliity. 5.6 Media Gallery: A gallery feature for presenting sets of graphics/videos or other media types. User should be able to download the media asset. Yes Media Gallery module 5.7 "Social Media: A collection of standard social media icons that quickly and easily allow for sharing of content from the site with popular social platforms, including but not limited to: - Twitter - Facebook - Flickr - YouTube - Digg - Slashdot - Delicious - Reddit - RSS Yes Social Share module or similar will be used. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 26
  27. 27. 5.8 Public Lectures: Content and functionality of the SLAC Public Lectures website will be folded into the SLAC home website, including but not limited to the following features: - A Poster gallery presented with a Cover Flow control for navigation the collection of posters, and the ability to zoom in on a poster - A list of Past Lectures showing the date, title, and presenter for each lecture, as well as a link to the video for each lecture - Storage for all public lectures, as well as the ability to stream them on the website - A form enabling the public to join SLAC Connections, which allows them to stay up-to-date with public events and happenings at SLAC Yes Views Slideshow: ImageFlow will be used for Cover Flow. 5.9 Contact SLAC Form: A web form that allows users to contact the Communications office at SLAC. Form contains several text fields, a drop- down menu for query topics, and a submit button. Form submission results in an email being sent to the Communications office. Yes We'll use Webform module for the form if it needs to be configured on back-end, or define it in code otherwise. 5.10 Site Feedback Form: A web form that allows users to provide feedback to SLAC. Form contains several text fields, a drop-down menu, and a submit button. Form submission results in an email being sent to the Communications office, and to the Web team. Yes Feedback form can be also a Webform as mentioned in 5.9 ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 27
  28. 28. 6 Search 6.1 SLAC Global Search Box: Appears at the top of every page (in global header), and provides user the option to search SLAC's entire web or the SLAC directory for people. Last selected option for Web or People search is remembered for each user. Web search targets SLAC's enterprise search engine, IDOL. Directory search for people targets SLAC's enterprise phone-book application. Yes IDOL and phone-book application will be queried for results and returned results will be displayed in Drupal and themed. 7 New Site Features 7.1 RSS /Metadata enable the news articles and press releases so they can be injected in other sites/pages Yes RSS feeds will be created with Views module. 7.2 Add SLAC Blog * Blog 'block' on the home page listing most recent blogs * blog entries can include multiple images/video slots that are displayed in lightbox (similar to news article pages) *archive/chronological listing of past entries listed in right column * RSS /Metadata enabled Yes Blog content type will be created and blog listings will be done with Views, as well as RSS feed. 7.3 Lightbox functionality: * Ability to download full resolution images from the lightbox display. * Lightbox image sizes standardized Yes Views Lightbox2 and Image Styles will be used. 7.4 Ability to easily add social media icons block to any page consistently Yes Standard drupal functionality to add block to specific pages or other conditions. 7.5 Ability to password protectc certain news articlepages that are intended for private audience. Yes We will implement password protect according to requirements based on Protected node module 7.6 Ability to extract pull quotes from news articles/press realeses and control the size of the quote text easily. Yes Quotes can be created and quotes will be referenced with Entity Reference module. This way updating a quote will change all the pages where it was used. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 28
  29. 29. Phase III – Migration of SLAC Tours Website to Drupal 7 Will finalize the development process proposed by SLAC and will imply the migration of the Tours section from the public SLAC website. The phase will include the migration of data like tours registration forms, private tours, tours wait list, etc. All the existing pages and functionalities will be developed in the new Drupal environment as stated in the RFP. The migration of tours will be implemented manually for all the pages mentioned in the RFP and the enclosed estimations. Phase III.a – Migration of SLAC Tours Website from Oracle APEX 4.1.2! Business Requirements4.1.2! Business Requirements4.1.2! Business Requirements4.1.2! Business Requirements Key Requirements WorksheetKey Requirements WorksheetKey Requirements WorksheetKey Requirements Worksheet # Criteria Complies (yes/no) Comments 1 Access 1.1 Site to be hosted on SLAC's internet, so all published content is anonymously accessible. Yes Standard Drupal behavior. 2 Architecture/Structure 2.1 Site structure/map should match the current SLAC Tours website. Yes The new site will be built according current site structure. 3 Theme and Design 3.1 Internet subtheme B selected as the theme for this site - all pages in the use this theme. Yes Subtheme B will be generated/built with intranet base theme enabled by default. 3.2 Apply SLAC's responsive design content hierarchy rules throughout SLAC Tours website. (See SLAC Design Guide document for details) Yes Internet subthemes will provide responsive behaviour which will be configured to match SLAC Design Guide requirements. 4 Key Site Features 4.1 Bimonthly tour registration form Yes Webform module will be used to register attendees. 4.2 Ability for schools/institutions to request private tours Yes Webform module will be used to register private tours attendees ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 29
  30. 30. 4.3 Ability to create one-off "special tour" pages with registration component Yes Webform module will allow you to create those tours in back-end. 4.4 Administration interface for tour organizers Yes Dashboard with Views and Webform administration interface. 4.5 Wait list for tour registration, and the ability to check on our status, without logging in Yes Webform results will be stored in database and will be used as a waitlist, unless we'll need to store some other data in the wait list. A form will be created for users to check their status. 4.6 Email notifications for all registrations. Yes Rules module will be used to notify by email. Testing We will perform testing during each phase of the project: data migration, user permissions, performance, functionality and code review. During data migration, we will check all content and user permissions to work properly. We will start doing performance analysis early in the process in order to promptly catch any regressions. Our team of QA assistants will carefully test all implemented functionality to make sure everything works according to the technical requirements. We use a number of automated testing tools as well as some manual procedures throughout the entire testing process in order to fully prepare the website for a successful deployment. Training Propeople has the advanced experience to build Drupal projects and make extensive manuals describing all its modules and functionalities. In Addition, we are able to organize a full training session for dedicated employees at SLAC where we explain in details all the developed functionality, along with test cases and other technical documentation needed after a milestone is achieved. Training plan Propeople will hold/provide extensive training sessions where we will guide, teach and train the SLAC staff into all aspect of using their Drupal system. Trainings can be provided by text documentation, online screen sharing sessions or in person training sessions - when the client is trained on how to add/edit/ delete content or to modify different elements and website sections. We will further on find an approach that is best for your needs and preferred by the SLAC responsible team. Deployment We recommend using the three-level hosting setup: development, staging and production/live servers. The core repository will be on git or github, and we may automate the process to push code and ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 30
  31. 31. databases from the Development to the Stage server, and then from the Stage to the Production/Live server. This approach will ensure a easy and straightforward deployment process. We will come up with more precise solutions, after the discovery phase mentioned in this offer. Support Propeople offers enterprise-class Drupal support for your website. We can offer 24/5 support coverage, or in cases of emergencies 24/7 coverage. The price is negotiable and may vary per the individual Service Level Agreement. Our Service Level Agreements includes a specific amount of development hours each month, emergency coverage via e-mail or phone to answer all your questions, share the best practice and help in order to solve issues as quick as possible. ! Propeople, Inc. - 467 S First street, San Jose, CA 95136 - www.wearepropeople.com! 31

×