tailieunhanh - Bài giảng Kiến trúc phần mềm: Tài liệu kiến trúc phần mềm - PGS.TS. Trần Minh Triết

Bài giảng Kiến trúc phần mềm - Tài liệu kiến trúc phần mềm cung cấp cho người học các kiến thức: Architecture documentation, documenting an architecture is good, component diagram, deployment diagram, component interfaces, component decomposition, . Mời các bạn cùng tham khảo. | Trường Đại học Khoa Học Tự Nhiên Khoa Công Nghệ Thông Tin Bộ môn Công Nghệ Phần Mềm CTT526 - Kiến trúc phần mềm Tài liệu kiến trúc phần mềm . Trần Minh Triết tmtriet@ Version https tailieudientucntt Nội dung của bài giảng sử dụng Session 6 Documenting a Software Architecture trong bộ slide Software Architecture Essential của GS. Ian Gorton Software Engineering Institute Carnegie Mellon University 2 https tailieudientucntt Architecture Documentation Architecture documentation is a thorny issue Commonly there is no documentation covering the architecture. If it is it s out-of-date inappropriate and basically not very useful. Also projects that have masses of architecture related information Sometimes invaluable but often it s out-of-date inappropriate and not very useful 3 https tailieudientucntt Documenting an Architecture is good Others can understand evaluate the design. We can understand the design after a period of time. Others in the project team and development organization can learn from the architecture. We can do analysis on the design perhaps to assess its likely performance or to generate standard metrics. 4 https tailieudientucntt But it s difficult No universally accepted architecture documentation standard. An architecture can be complex and documenting it in a comprehensible manner is time consuming and non-trivial. An architecture has many possible views. Documenting all the potentially useful ones is time consuming and expensive. An architecture design often evolves Keeping the architecture documents current is often forgotten especially with time and schedule pressures in a project. 5 https tailieudientucntt Think carefully about what to document Project complexity A small project may only need a marketecture Project longevity One-off stop gap software Strategic long-term will evolve