vault backup: 2025-01-08 16:44:38

.obsidian/plugins/text-extractor/cache/2f0141b61eb6fb93b6a8cf93ef1bb0ba.json

@@ -0,0 +1 @@
+{"path":"Attachments/Pasted image 20250108160308.png","text":"Requirements Release 15.0% _ — Development 12.0% Stage3 (80 DY 27% (0 A o Stage 1 | 217% Ç É> Stage 2 ‘ Each stage includes detailed . 21.7% design, construction, and äâæm _ testing, which overlap as shown in Figure 5-3. FIGURE 55 Activity distribution by percent of schedule consumed, assuming a project is divided into three stages. (Numbers do not add to WO percent due to rounding error.) Compare thisfigure to Figure 5-4: schedule and effort on a software project are not dis- tributed in exactly the same way.","libVersion":"0.3.2","langs":"deu+eng+fra"}

.obsidian/plugins/text-extractor/cache/f0a5703ebb4c7e867960770d865d7c3b.json

@@ -0,0 +1 @@
+{"path":"Attachments/Pasted image 20250108155841.png","text":"SN NN NN U O NNN NN NN NNN : SS —— NI NN } N E “ \\ S EN TS ESL ANNANNN Planning Checkpoint Time — Review FIGURE 53 Typical activity overlap. Early activities of requirements development and architecture do not overlap as much as later activities ofdetailed design, coding, integration, and testing. Bar thickness indicates the relative staffing levels throughout the phases of a project.","libVersion":"0.3.2","langs":"deu+eng+fra"}

.obsidian/plugins/text-extractor/cache/fb932d807609b861da2a23233f286554.json

@@ -0,0 +1 @@
+{"path":"Attachments/Pasted image 20250108160138.png","text":"Requirements Release 10% Development 6% chiteclm‘eß% sysem Tesing @ DS \\ pusin 0% YL ; 21100 Consirùcfion 40% FIGURE 5-4 Activity distribution by percent of effort consumed.","libVersion":"0.3.2","langs":"deu+eng+fra"}