[Budget amount is not correct]
[Section "3 Functional Requirements" is updated]
Please provide your best reasonable quote for this custom portlet development for Liferay 6.2 Portal also provide estimated total time with breakdowns.
We would need a timeline in terms of :
1. Technical Specification Document
2. New Application to Test Site
3. New Application to Live Site
4. Review Final Application and Documentation
5. Post-Deployment Support policy and period
Project Specification and Requirements:
1 Architecture: The DRPA shall utilize the following platform and integration:
1.1 Platform: Liferay Portal 6.2 Enterprise and Community Edition, Tomcat, MySQL, running on RedHat Enterprise Linux
1.2 Provide integration with Liferay’s search index and Application Program Interfaces (API)
1.3 Section 508 and Accessibility Standards
2 Web Application Security
2.1 The DRPA and development shall follow best practices (OWASP & SWAT) for web application security and user security.
3 Functional Requirements
3.1 User Functionality: the DRPA shall provide users with the following:
3.1.1 Listview of publications with sortable columns for Title, Authors, and Date. (Screenshot attached from existing php application), would need an option to add/remove columns from Listview.
184.108.40.206 Listview should allow Search by publication number, author, series (dropdown), category (dropdown) and keywords on all columns (existing and new custom columns). (Screenshot attached from existing php application)
220.127.116.11 Search functionality need to be within Lucene search index and search result should be shown with Portlet name as Category to choose from on search result page. (Screenshot attached from example Liferay portlet)
3.1.3 View publication record, print and download full report file in pdf (Screenshot attached from existing php application)
3.1.4 One publication entry can have multiple pdf files associated with it from 3.2.2 (below).
3.1.5 Audit Trail Log DB Table or Activity History Table should be maintained to record each action (view, edit, delete, disable) taken with Liferay userid (when updating old data must be saved in the log table)
3.2 Administrator Functionality: the DRPA shall allow administrators to:
18.104.22.168 Add/update/delete/disable publication records, including adding custom new fields/column (single or multi-value with dropdown) to the records.
22.214.171.124 Manage (Add/update/delete/disable) values for existing or new custom multi-value fields/columns (existing fields: series and category).
3.2.2 Attach full-text PDF files to publication record.
3.2.3 Export publication records to Excel with link to pdf on portal
3.2.4 Import publication records from Excel.
3.2.5 Option to Upload and store publication PDFs to Liferay individually or multiple PDFs at a time. Once uploaded, the individual PDFs (named same as Report_Number_#1 in the screenshot) shall be linked to the publication record and the link shall be maintained.
3.2.6 Specify the Liferay site specific to each Publication: Portlet must be usable for multiple Liferay sites by keeping the data separate for each site.
3.2.7 Uploaded PDFs are stored within data/document_library folder of Liferay and all handling should be done thru Liferay API. But files should not be visible via Document and Media Portlet. Separate Folders should be maintained by GroupId within Liferay to store files for that groupid.
4.1 Prepare a detailed and precise technical specification (application blueprint) document
4.2 Technical documentation shall include:
4.2.1 List of areas where passwords are used.
4.2.2 List of each source code file, functionality and how it relates to other files
4.2.3 List of libraries used and where and their source site URL's
4.2.4 Build files (How to build and compile the project)
4.3 Database documentation: List of Data structures and tables. Minimum meta and configuration data required for the site to run.
4.4 Inline code documentation: Each class, function should have documentation of what the function is used for and some basic pseudo code steps describing what the function does
4.5 User Documentation with screenshots to walk them thru.
4.6 Provide status updates to and align goals with us weekly.
5 Acceptance Testing:
The DRPA should be fit for purpose and mistakes shall be eliminated. DRPA must be populated with the existing report and repository data, users and other data during and all areas should be validated and tested, without bugs.
5.1 Quality Assurance Plan.
5.1.1 100% Performance Expected.
5.1.2 Commit new application code to a test site.
5.1.3 Complete testing, evaluations, troubleshoot and correct errors.
5.1.4 Test Application on the Test Server
5.1.5 Test Application on the Live Server
5.1.6 Errors/bugs resolved within 24 hours.
5.1.7 Review Liferay Repository Plug-in Application Code and Documentation with us.
5.1.8 Support and Maintain application, troubleshoot and correct errors / bugs for a minimum 2 years period.