200 likes | 301 Views
Design definition. Den proces, som med forskellige teknik- ker definerer en enhed, en proces, eller et system i tilstrækkelige detaljer, således at det kan kodes/realiseres. Taylor Begyndelsen til visdom for en program- designer er at erkende forskellen mellem
E N D
Designdefinition • Den proces, som med forskellige teknik- ker definerer en enhed, en proces, eller et system i tilstrækkelige detaljer, således at det kan kodes/realiseres.Taylor • Begyndelsen til visdom for en program- designer er at erkende forskellen mellem at få et programtil at virke og få det gjort rigtigt. Jackson
Procesdesign Designretningslinier Kravspecifikation Programdesign Moduldesign • T1 - T6 Designtrin • D1 - D6 Designregler • A1 - A7 Design dokumentation/ arbejdsformer • Godt design: • Let at forstå • Let at implementere • Let at teste • Let at vedligeholde
PM-System delvist level 1 DFD: Local Monito- ring Vital signs Patient Patient bounds Patient data Vital signs bounds Central Monito- ring Warning message Nurse Update log Formatted patient data Report Report generator Log data Log data Request for report Patient log Nurse
PM-System, alle forbindelser: Local Monito- ring Vital signs Patient Patient bounds Get vital data Vital signs bounds Patient info Patient Patient data Alarm Actuel data Patient entities Central Monito- ring Warning message Nurse Insert patient data Nurse Formatted patient data Update log New data Report Nurse Report generator Time Time Log data Log data Request for report Real time clock Patient log Nurse
PM-System m. krav: Local Monito- ring Vital signs 3.2.1 Patient Patient bounds Get vital data Vital signs bounds Patient info Patient 3.2.2 3.2.3 3.2.4 3.2.8 Patient data Alarm Actuel data Patient entities Central Monito- ring Warning message Nurse Insert patient data Nurse Formatted patient data Update log New data 3.2.5 Report Nurse 3.2.9 Report generator 3.2.6 3.2.7 Time Time Log data Log data Request for report Reel time clock Patient log Nurse
PM-System m. 2 processer: Local Monito- ring Vital signs Overvågning Patient Patient bounds Get vital data Vital signs bounds Patient info Patient Patient data Alarm Actuel data Patient entities Central Monito- ring Warning message Nurse Insert patient data Nurse Formatted patient data Update log New data Report Nurse Report generator Time Time Log data Log data Request for report Reel time clock Operatør Patient log Nurse
PM-System m. yderligere P: Alarm tabel Opdater alarmtabel Behand. alarm Local Monito- ring Vital signs Patient Patient bounds Alarm proces Get vital data Patient info Patient Patient data Vital signs bounds Actuel data Patient entities Central Monito- ring Driver to hardware Nurse Insert patient data Nurse Formatted patient data Update log New data Report Nurse Report generator Print Proces Time Time Log data Log data Request for report Reel time clock Print buffer Patient log Nurse
Procesdesign Procesdesign • Hovedformåler med procesdesign er modul specifikation • T1 - T6 Procesdesigntrin • D1 - D6 Procesdesignregler • A1 - A7 Procesdesign dokumentation/ arbejdsformer • Procesdesign-checkliste • Godt design: • Let at forstå • Let at implementere • Let at teste • Let at vedligeholde
Processen opdelt i moduler Test Modul 1 Kodning Modul integration Proces Modul i Kodning Test • Struktur-diagram • Funktions-diagram • Top down, Button up, Mest kritisk først
Procesdesign metoder(T1) • Funktions- orienteret • Objekt-orienteret • Datastruktur- orienteret • Funktioner med fælles egenskaber samles i moduler • Kvalitativ vurdering af opdelingerne • Hierarkisk struktur ønskelig • Grafik til at give overblik
Eksterne grænseflader(T2) Patient Tabel Real Time clock Alarm proces Skærm Alarm Tabel Patient Printer Buffer
Moduldesign:AlarmProces Alarm ? Print buffer Patient tabel Alarm Tabel Patient stue Real time clock Skærm
Funktioner i AlarmProces Eksempel 13 i SPU side 149 Moduler i AlarmProces Eksempel 14 i SPU side 150
Moduldesign Moduldesign • T1 - T6 Moduldesigntrin • D1 - D6 Moduldesignregler • A1 - A7 Moduldesign dokumentation/ arbejdsformer • Moduldesign-checkliste • Godt design: • Let at forstå • Let at implementere • Let at teste • Let at vedligeholde
Moduldesign • Formål: - At få lagt sig fast på datastrukturer - At få bekrevet modulets funktioner så de bliver til at implementere Metoder T1: • Pseudokode • Tilstandsdiagram • Rutediagram • Warnier-Orr-, Jackson-, Nassi_Scneiderman-diagrammer
End Program Struktureret Flowchart Program Algorit Not Algorit Begin kunde Not g.a.bev Grp. Af bev. 1 bevægelse Kredet Debet End 1 bev End g.bevæg End kunde End Algorit
Diverse metoderi modul design Eksemplerne i SPU siderne 160 - 161
VisdomsordGrady Boch • ”A complex system that works is invariably evolved from a simple system that worked.. A complex system designed from scratch never works and cannot be patched up (lapped sammen) to work. You have to start over again, beginning with a working simple system” • ”Object-oriented decomposition greatly redu- ces the risk of building complex software systems, because they are designed to evolve incrementally from smaller systems in which we already have confidence”
Lidt flere visdomsordJohn F. Palmer • With bad specifikation, a bad software system is the best that can be expected • The ones who works as they thing, produce understandable and complite specification in much less time. These high quality specifications lead to high quality software