Skip to content

Milestones

List view

  • (Legacy) Milestone towards Micro service 2.0.0

    The milestone comprises 1.2.x and 2.0.x series. General Goal: 1. Refract the project architecture to Micro-service to make the system easy to deploy. 2. Prototype design shall be done before the due, and set up additional development environment for **Admin** and **Doctor** Module. Criteria: 1. All of the CI/CD workflows should be passed, build&test&deploy, documentation generation, dependent update and SOC II Compliance should be passed. 2. The Unit Test coverage should be over 80%. 3. Guarantee the preliminary compliance of the newly-introduced APIs. 4. Conduct the UI/UX(i.e. Prototype) design. 5. Micro-service should be highly reliable Sub-Criteria: 1. Monitoring Components such as Proemtheus and Graphna should be integrated. 2. Cache via Redis helps the response time of APIs derease by 80%. 3. Configurations should be dynamic and confidential via Nacos. 4. The system can be deployed by Docker Compose. ## Disclaimer Only technical issue will be completed,the following terms are only used for our Campus Assignments.Redistribution,copy and other forms of use is not allowed!Any aftermath caused by the following terms has nothing to do with us(The Backend Team) and we won't give any supports to anyone outside the organization.

    Overdue by 2 year(s)
    •
    Due by May 1, 2024
    •4/4 issues closed
    100% complete0 open4 closed

  • Tangxiaozhi >=2.3.0

    The milestone marks the completion of all the functionailties of our ecosystem,congratulations! ## General Goal This milestone focuses on NoSQL like Redis and its module(Redis TimeSeries,Redis Bloom),the Redis will be more reliable! After Integration,the response time will increase by a huge a mount and user can make predictions of CGM! Chat function will be supported in this series too! ## Criteria 1. The response times of all APIs won't exceed 200ms,100ms on average. 2. The errors(RMSE) on prediction of glycemia via LSTM won't exceed 5. 3. Acceptance Test passed and availability is guaranteed by **Gray Release**. 4. Redis will be upgraded as Redis Enterprise Cloud,the system will be deployed by Kubernetes and Docker. 5. The design of front website meets the basic aesthetic requirements. 6. User Manuals shall be completed before the due. 7. License ,disclaimer and other legal notices shall be published. 8. All CI/CD Workflows passed and the system adhere to the SOC Compliance I,II and III. ## Disclaimer Only technical issue will be completed,the following terms are only used for our Campus Assignments.Redistribution,copy and other forms of use is not allowed!Any aftermath caused by the following terms has nothing to do with us(The Backend Team) and we won't give any supports to anyone outside the organization.

    Overdue by 2 year(s)
    •
    Due by July 1, 2024
    •2/2 issues closed
    100% complete0 open2 closed

  • Tangxiaozhi 2.0.x

    OA Service Introduced in this series. ## General Goal 1. Implement basic functionality of OA Service(i.e. the backend of Admin Platform). 2. The website of Admin shall be composed before due. ## Criteria 1. All of the CI/CD Workflows should be passed and all **patches**(i.e. the Pull Requests) has been approved by at least 2 maintainers. 2. DDos and hack from external networks of a specific hospital will always fail. 3. The system must adhere to the SOC II Compliance. 4. All **patches** and issues are tracked and the releases that adheres to the semantics versioning shall be published at the due time. ## Disclaimer Only technical issue will be completed,the following terms are only used for our Campus Assignments.Redistribution,copy and other forms of use is not allowed!Any aftermath caused by the following terms has nothing to do with us(The Backend Team) and we won't give any supports to anyone outside the organization.

    Overdue by 2 year(s)
    •
    Due by June 13, 2024
    •9/9 issues closed
    100% complete0 open9 closed

  • Tangxiaozhi >=2.1.0

    Interact Service introduced in this series ## Disclaimer Only technical issue will be completed,the following terms are only used for our Campus Assignments.Redistribution,copy and other forms of use is not allowed!Any aftermath caused by the following terms has nothing to do with us(The Backend Team) and we won't give any supports to anyone outside the organization.

    Overdue by 2 year(s)
    •
    Due by June 20, 2024
    •7/7 issues closed
    100% complete0 open7 closed