Nội dung training chính

Sơ đồ tổng quan quy trình hoạt động

ID Mã quy trình Tên quy trình Mô tả chi tiết
1 SAPLU-230 Phát triển tính năng mới x
2 SAPL-906 Fix Bug của tính năng x
3 SAPL-123 Fix Bug có tính value
4 SAPL-345 Bug Production after Release
5 SAPL-432 Bug Fix Support
6 SAPL-432 Support Technical Issues trên Shopify Community

Quy trình dựa trên ý hiểu của SAPLU-230. Phát triển tính năng mới

Process Flow of BSS Group (2).pdf

Waterflall work flow:

The Waterfall model is a sequential (non-iterative) design process, often used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through several phases. Typically, these phases include:

  1. Requirements: This initial stage involves gathering and documenting what the system must do and what it needs to avoid. It's about understanding the client's needs and the problem that needs to be solved.
  2. Design: In this phase, the system's architecture and design are developed. The software's high-level structure and its low-level components are defined, often using design tools or programming frameworks.
  3. Implementation: Here, the actual development of the software takes place. The design is translated into source code by developers.
  4. Verification: This phase involves testing the software to ensure it meets all requirements and is free of bugs. Testing can be performed in various stages and can include unit testing, integration testing, system testing, and acceptance testing.
  5. Maintenance: After the software is deployed, it enters the maintenance phase. This includes updating the software to meet evolving client needs, fixing any bugs that weren't identified in earlier stages, and improving performance.

The Waterfall model is characterized by its rigid, linear structure. Each phase must be completed before the next begins, and there is typically no going back to a previous phase. This can make the Waterfall model less adaptable to changes compared to more iterative models like Agile.