Client's Technical Specification:
Technical Specification for the Development of the Website of the Kyrgyz State Medical Institute of Retraining and Advanced Training named after S.B. Daniyarov
1. General Requirements
1.1. The website developed under this Technical Specification (TS) must be used by users to obtain any information of interest posted on the site.
1.2. The Customer has no right to demand from the Contractor, within the framework of the Contract, the performance of works or provision of services not explicitly described in this TS.
1.3. The Customer has no right to demand from the Contractor compliance with any formats or standards unless specified in this TS.
1.4. All ambiguities identified in this TS after its signing shall be subject to bilateral agreement between the Parties. During the agreement process, additional requirements may be developed, which shall be formalized by an additional agreement to the Contract and appropriately evaluated.
1.5. The site must be designed in such a way that it can be used on personal computers, tablets, and mobile phones.
1.6. The name of the organization, logo, and slogan are developed by the Customer and placed on the website.
1.7. The website must be implemented in the state and official languages.
2. Website Development
The initial development and layout of the content (information content) of the Website must be carried out by the Contractor with the direct participation of the Customer. The Customer provides the Contractor with all necessary textual and graphic materials, as well as comments regarding their content, volume, formatting, and placement.
3. Requirements for the Website
3.1. The website must contain the required volume of information, a mechanism for timely content updating, and a basic set of information handling services that ensure the required completeness of informational and other services provided to the user.
3.2. The website must display a news and events feed, information about the main activities of the Contractor, including in the form of a presentation about the activities and a photo gallery of events and news, a directory, and contact information.
3.3. The structure for presenting information resources and user interfaces for accessing resources and services must be intuitively understandable to a wide range of users.
3.4. The site navigation must provide a consistent way to move from page to page and from section to section, as well as return to the home page and access main hyperlinks, using main and auxiliary navigation mechanisms with consistent positioning on all pages, and a site map.
3.5. Provision must be made for placing banners, including dynamic ones (in the bottom, side, and top parts of the site). Banner management.
3.6. Access rights differentiation by site sections must be ensured. For this purpose, it is necessary to provide for the possibility of registering a site administrator, as well as editors with full or limited rights to individual site sections.
3.7. Logs of site activity must be maintained, recording login/logout details of the administrator and editors, as well as modified sections and pages of the site.
3.8. Display of the site and user interaction with it, regardless of authentication level, must not depend on the browser used among the most common ones: Microsoft Internet Explorer, Microsoft Edge, Mozilla Firefox, Google Chrome, Opera, Apple Safari, etc., including those used on mobile devices.
3.9. Maintain identical display when viewed in web browsers Internet Explorer 7.0+, Mozilla Firefox 3+, Safari 3.6+, Opera 9+, Google Chrome 3+.
3.10. Provide user feedback via web browser both with and without using email clients or other programs.
3.11. Ensure correct display of information on computers without pre-installed Flash modules, with script support disabled (exception: drop-down menu, animation of service type switching in Internet Explorer version 7.0), etc.
3.12. Contain a comprehensive set of metadata for effective indexing by search engines and correct automatic charset selection.
3.13. The site layout must be responsive. The site must display correctly on devices with image rotation in portrait and landscape modes.
3.14. Page layout must ensure automatic page scaling depending on the width of the user's browser workspace. The site must fully fit the screen width at horizontal monitor resolutions from 1024 to 1680 pixels. The preferred visual display is full-screen without margins. When the user's monitor resolution significantly exceeds the maximum value, the option to center the site with background-patterned margins. When using a lower-resolution monitor, horizontal scrolling is acceptable. When calculating resolution, consider the browser window resolution, not the monitor.
3.15. Users of the site should not require special technical skills, knowledge of technologies, or software products, except for general personal computer and standard web browser skills.
3.16. For display on mobile devices, separate design solutions affecting site display must be proposed.
3.17. The site must allow users to report a page error to the Site Administrator’s email address without using third-party grammar services, analogous to “select text, press CTRL+Enter”.
3.18. Ensure display of any site page’s content in a print-adapted view, including a simplified design.
3.19. Develop a design for the 404 error page.
3.20. Include a site search function. The function must provide simple and advanced search by information type, date or date range of publication, update date, keywords, tags (identifiers), and substring. The search subsystem may take into account Russian language morphology.
3.21. Hyperlinks must: be highlighted; be relative; contain information about any unexpected actions for the user; be accompanied by an icon indicating the type of file being downloaded, as well as the file size.
3.22. Cyclic hyperlinks leading to the same page on which they are placed are not allowed, except for in-page tag navigation.
4. Website Design (Styling)
4.1. The site must be simple in structure and easy to use.
4.2. The site must be modern in functionality and design.
4.3. The site design must use the official symbolism, corporate identity, and logo of the institute.
4.4. The stylistic design of the site must be selected by the designer; font size and color must be highly readable and match the overall site style.
4.5. Site design must be based primarily on the use of graphic images in control and decorative elements:
1) Be concise and intuitive.
2) Provide the user with convenient work with information on the site.
3) Contain static and dynamic graphic elements.
4.6. Main site sections must be accessible to the user from the first (home) page.
4.7. Text (fonts) and graphic elements used for design must not contradict the overall stylistic design of the site and corporate identity (fonts must be embedded in the site).
4.8. The site design must be unique.
4.10. The site must include a slider with several posters in the top part of the site.
4.11. News feed.
4.12. Adaptive tree menu.
5. Technical Specifications
5.1. All system software must be developed as web applications.
5.2. The system must operate under Windows or Linux family operating systems. The choice of operating system will be made after additional discussion with the developer.
5.2. The development of the site must use official and de facto open standards (such as XML, HTML, etc.) that are most common on the Internet and generally accepted in the practice of building organizational/enterprise information systems. Preference should be given to architectural solutions and software products that have already proven their suitability for solving similar tasks.
5.3. Procedures for installation on new hardware, setting up a backup site, support, and administration must be described in the technical documentation and worked out in detail during site implementation, taking into account simplicity and convenience. Requirements for the qualifications of personnel who will operate the site must also be formulated.
5.4. The site information must include the following pages: SOUTHERN BRANCH OF KSMI R&AT MAIN ABOUT US CONTINUOUS EDUCATION POSTGRADUATE TRAINING/RESIDENCY SCIENCE RESOURCES CONTACTS CTP (calendar)
5.5. The “About Us” section contains information about the institute (management, structural units).
5.6. The “News” section contains operational information. Latest news — News archive.
5.7. The “Contacts” section presents information about the site Customer organization in 3 languages.
5.8. The “Search” section must provide the ability to search for various information for the site user.
5.9. The developed site must be accessible and fully functional at the address https://…. Automatic redirection from http to https requests must be configured.
5.10. The site must be protected against DDoS attacks and other vulnerabilities, as well as against spam and other malicious programs, and protected against unauthorized file editing.
5.11. The site must be able to send emails about registration and password recovery, as well as other emails provided by site input forms.
5.12. In the “Feedback” section, the user must be able to send a message to the Customer by providing contact details, full name, subject, and message text.
5.13. Ability to place audio and video streaming materials, as well as embedded video from popular streaming video and audio services.
5.14. Page with the calendar-thematic plan displaying a list of active and upcoming courses by date, with filtering and search capabilities.
5.15. Convenient administrative panel interface.
5.16. The interface for creating and editing content must be intuitive for ordinary users without special computer skills.
5.17. Ability to create and edit galleries.
5.18. Trust box without authorization.
5.19. Calendar-thematic plan with filter and current courses for the next month.
7. Access Rights Management Requirements
7.1. The site must be protected against unauthorized distortion or destruction of the information presented on it, and against unauthorized placement of information.
7.2. The link to the administrative interface must not be visible from other site pages.
7.3. The function must provide registration and authorization for access to the administrative interface, read/write operations on page and file content, and use of functions within the administrative interface.
7.5. Access to managing editor accounts is available only to the site administrator.
7.6. The site management system must include a mechanism for backing up the structure and content of the database. The backup procedure must be performed by the employee responsible for site maintenance. Backup of graphic content must be done manually.
8. Documentation Requirements
8.1. Before starting preliminary site testing, the Contractor provides the Customer with:
1) Distribution of the installation version of the site and all developed subsystems.
2) User documentation: Site Administrator Guide (including instructions for deploying software on new hardware, creating backups, restoring backups); guide for preparing and publishing materials; technical documentation for the site containing a description of the structure, databases, requirements for technical and system software; documentation must include a list of all directories and files with their functional purpose.
8.2. The set of documentation is provided to the Customer in electronic and printed form (1 copy). All documentation is provided in Russian.
9. Procedure for Preliminary Site Testing
9.1. Preliminary site testing is carried out according to the testing program and methodology developed by the Contractor and agreed with the Customer. The Contractor delivers the site fully compliant with the technical specification, as well as a table of created and assigned logins-passwords required for site management.
9.2. Based on the results of preliminary testing for operability and compliance with the TS, in accordance with the program and methodology, an Act of Acceptance of the Site for Trial Operation is drawn up.
10. Trial Operation of the Site
10.1. Trial operation of the site is carried out for one month from the date of signing the Act of Acceptance of the Site. During trial operation, site availability on the Internet is not restricted. Based on the results of trial operation, the Contractor eliminates identified deficiencies of the site and, by agreement with the Customer, implements proposals to improve site performance (within one day upon request from the Customer).
11. Site Warranty
11.1. The warranty on the site is provided for 12 months from the date of signing the Act of Acceptance of the Site upon completion of trial operation. During the warranty period, the Contractor eliminates identified deficiencies of the site, restores site operability in case of loss, provides free support for the site management system and its updates (within three days upon request from the Customer).
12. Additional Requirements
12.1. The basic site software must be checked for the absence of known vulnerabilities to denial-of-service attacks and unauthorized access.
12.2. The Contractor guarantees that the site is free from third-party claims, including on technologies, software, and components developed by the Contractor that are part of the technical means complex (TMC), site design, images used on the site and design layouts. The Customer reserves the right to replicate the site. The Contractor provides free support for the site management system during the warranty period. Installation of all updates to the management system released during the warranty period is performed by the Contractor at the Contractor’s expense while preserving all functionality and site content.
12.3. At the same time, the Contractor guarantees site operability even after the warranty period ends.
12.4. Exclusive rights to the developed site in full belong to the Customer in accordance with the current legislation of the Kyrgyz Republic. The Contractor has no right to use, sell, demonstrate, or transfer the site program code to third parties.
12.5. All licensed software products necessary for site operation, purchased from third parties, are formalized by the Contractor for the Customer and transferred to his ownership, and must be accompanied by documentation confirming the right of these persons to supply such products, and license agreements.
12.6. The Contractor transfers to the Customer all exclusive rights to algorithms and software developed during the provision of services.
12.7. Installation of the system as a whole, as well as installation of individual parts of the system, must not impose additional requirements to purchase licenses for third-party software.
12.8. Design, layout, functionality, and design solutions of the site must be preliminarily agreed with the Customer.
12.9. The Contractor provides at least 5 (five) options for approval, including site design (layouts of the main page, section page layouts, mobile version page layouts, layouts of pages for persons with disabilities). The site design must be concise, memorable, and not overloaded with dynamic elements.
12.10. The site structure must provide for the possibility of its development by creating and adding new sections and changing the structure of sections.
12.11. Documentation is provided to the Customer for approval and signing in printed and bound form in two copies, as well as on flash drives.
