{"id":61294,"date":"2023-12-08T20:24:59","date_gmt":"2023-12-08T11:24:59","guid":{"rendered":"https:\/\/monolith.law\/cs\/?p=61294"},"modified":"2024-03-26T06:05:23","modified_gmt":"2024-03-25T21:05:23","slug":"system-development-specs-function","status":"publish","type":"post","link":"https:\/\/monolith.law\/cs\/it\/system-development-specs-function","title":{"rendered":"Do jak\u00e9 m\u00edry by m\u011bla b\u00fdt funkce, kter\u00e1 nen\u00ed uvedena ve specifikac\u00edch v\u00fdvoje syst\u00e9mu, implementov\u00e1na z pr\u00e1vn\u00edho hlediska?"},"content":{"rendered":"\n<p>Projekty na v\u00fdvoj IT syst\u00e9m\u016f pou\u017e\u00edvan\u00fdch v podnic\u00edch jsou v z\u00e1sad\u011b vytv\u00e1\u0159eny v souladu s p\u0159edem definovan\u00fdmi specifikacemi. Nicm\u00e9n\u011b, pokud zv\u00e1\u017e\u00edme v\u00fdznam toho, \u017ee dodavatel je jako odborn\u00edk na v\u00fdvoj syst\u00e9m\u016f pov\u011b\u0159en cel\u00fdm v\u00fdvojem, o\u010dek\u00e1v\u00e1n\u00ed u\u017eivatel\u016f nemus\u00ed b\u00fdt tak n\u00edzk\u00e1, \u017ee by sta\u010dilo pouze mechanicky implementovat to, co je naps\u00e1no ve specifikac\u00edch. V tomto \u010dl\u00e1nku se budeme zab\u00fdvat ot\u00e1zkou, do jak\u00e9 m\u00edry by m\u011bli n\u00e9st povinnost implementovat programy, kter\u00e9 nejsou uvedeny ve specifikac\u00edch, ale jsou pot\u0159ebn\u00e9 vzhledem k c\u00edl\u016fm v\u00fdvoje.<br><\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_53 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/monolith.law\/cs\/it\/system-development-specs-function\/#Pravni_problemy_spojene_s_implementaci_nezahrnutych_v_specifikacich\" title=\"Pr\u00e1vn\u00ed probl\u00e9my spojen\u00e9 s implementac\u00ed nezahrnut\u00fdch v specifikac\u00edch\">Pr\u00e1vn\u00ed probl\u00e9my spojen\u00e9 s implementac\u00ed nezahrnut\u00fdch v specifikac\u00edch<\/a><ul class='ez-toc-list-level-3'><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/monolith.law\/cs\/it\/system-development-specs-function\/#Od_dodavatelu_se_vyzaduje_diskrece\" title=\"Od dodavatel\u016f se vy\u017eaduje diskrece\">Od dodavatel\u016f se vy\u017eaduje diskrece<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/monolith.law\/cs\/it\/system-development-specs-function\/#Diskrece_by_mela_byt_uplatnovana_i_v_ramci_prisnych_vyvojovych_procesu\" title=\"Diskrece by m\u011bla b\u00fdt uplat\u0148ov\u00e1na i v r\u00e1mci p\u0159\u00edsn\u00fdch v\u00fdvojov\u00fdch proces\u016f\">Diskrece by m\u011bla b\u00fdt uplat\u0148ov\u00e1na i v r\u00e1mci p\u0159\u00edsn\u00fdch v\u00fdvojov\u00fdch proces\u016f<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/monolith.law\/cs\/it\/system-development-specs-function\/#Co_by_meli_odbornici_delat_aniz_by_byli_omezeni_specifikacemi\" title=\"Co by m\u011bli odborn\u00edci d\u011blat, ani\u017e by byli omezeni specifikacemi?\">Co by m\u011bli odborn\u00edci d\u011blat, ani\u017e by byli omezeni specifikacemi?<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/monolith.law\/cs\/it\/system-development-specs-function\/#Pravni_povinnosti_jsou_stanoveny_v_souladu_s_%E2%80%9Cucelem%E2%80%9D_specifikaci_a_smluv\" title=\"Pr\u00e1vn\u00ed povinnosti jsou stanoveny v souladu s &#8220;\u00fa\u010delem&#8221; specifikac\u00ed a smluv\">Pr\u00e1vn\u00ed povinnosti jsou stanoveny v souladu s &#8220;\u00fa\u010delem&#8221; specifikac\u00ed a smluv<\/a><ul class='ez-toc-list-level-3'><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/monolith.law\/cs\/it\/system-development-specs-function\/#Pripad_kde_povinnost_implementace_byla_poprena_kvuli_absenci_zaznamu\" title=\"P\u0159\u00edpad, kde povinnost implementace byla pop\u0159ena kv\u016fli absenci z\u00e1znamu\">P\u0159\u00edpad, kde povinnost implementace byla pop\u0159ena kv\u016fli absenci z\u00e1znamu<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/monolith.law\/cs\/it\/system-development-specs-function\/#Pripad_kde_byla_potvrzena_povinnost_implementace_i_bez_zapisu\" title=\"P\u0159\u00edpad, kde byla potvrzena povinnost implementace i bez z\u00e1pisu\">P\u0159\u00edpad, kde byla potvrzena povinnost implementace i bez z\u00e1pisu<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/monolith.law\/cs\/it\/system-development-specs-function\/#Co_lze_vycist_z_obou_rozsudku\" title=\"Co lze vy\u010d\u00edst z obou rozsudk\u016f\">Co lze vy\u010d\u00edst z obou rozsudk\u016f<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/monolith.law\/cs\/it\/system-development-specs-function\/#Jak_bychom_meli_uvazovat_o_odmene_za_vyvoj_ktery_neni_uveden_v_specifikacich\" title=\"Jak bychom m\u011bli uva\u017eovat o odm\u011bn\u011b za v\u00fdvoj, kter\u00fd nen\u00ed uveden v specifikac\u00edch?\">Jak bychom m\u011bli uva\u017eovat o odm\u011bn\u011b za v\u00fdvoj, kter\u00fd nen\u00ed uveden v specifikac\u00edch?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/monolith.law\/cs\/it\/system-development-specs-function\/#Shrnuti\" title=\"Shrnut\u00ed\">Shrnut\u00ed<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Pravni_problemy_spojene_s_implementaci_nezahrnutych_v_specifikacich\"><\/span>Pr\u00e1vn\u00ed probl\u00e9my spojen\u00e9 s implementac\u00ed nezahrnut\u00fdch v specifikac\u00edch<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/monolith.law\/wp-content\/uploads\/2019\/10\/shutterstock_164703428-1024x614.jpg\" alt=\"\" class=\"wp-image-5431\" \/><figcaption class=\"wp-element-caption\">Vysv\u011btl\u00edme d\u016fle\u017eit\u00e9 body t\u00fdkaj\u00edc\u00ed se &#8220;diskrece&#8221; v syst\u00e9mov\u00e9m v\u00fdvoji.<\/figcaption><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Od_dodavatelu_se_vyzaduje_diskrece\"><\/span>Od dodavatel\u016f se vy\u017eaduje diskrece<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>Jednou z hlavn\u00edch charakteristik smluv a r\u016fzn\u00fdch pr\u00e1vn\u00edch probl\u00e9m\u016f spojen\u00fdch s projekty syst\u00e9mov\u00e9ho v\u00fdvoje je, \u017ee dodavatel, kter\u00fd p\u0159ij\u00edm\u00e1 pr\u00e1ci, m\u00e1 velkou diskreci.<\/p>\n\n\n\n<p>Souvisej\u00edc\u00ed \u010dl\u00e1nek: <a href=\"https:\/\/monolith.law\/corporate\/project-management-duties\" target=\"_blank\" rel=\"noreferrer noopener\">Co je povinnost\u00ed projektov\u00e9ho managementu v syst\u00e9mov\u00e9m v\u00fdvoji[ja]<\/a><\/p>\n\n\n\n<p>Av\u0161ak &#8220;diskrece&#8221;, o kter\u00e9 zde hovo\u0159\u00edme, neplat\u00ed nutn\u011b pro v\u0161echny f\u00e1ze v\u00fdvoje syst\u00e9mu. Po identifikaci jednotliv\u00fdch f\u00e1z\u00ed a pokro\u010dil\u00e9m rozd\u011blen\u00ed na detailn\u00ed \u00fakoly se m\u016f\u017ee pr\u00e1ce \u010dasto st\u00e1t bl\u00edzkou jednoduch\u00fdm operac\u00edm. Nicm\u00e9n\u011b, obecn\u011b plat\u00ed, \u017ee \u010d\u00edm v\u00edce se st\u00e1v\u00e1me sou\u010d\u00e1st\u00ed proces\u016f v\u00fd\u0161e, tedy v r\u00e1mci upstream proces\u016f, t\u00edm v\u00edce se st\u00e1v\u00e1 obt\u00ed\u017en\u00fdm prov\u00e1d\u011bn\u00ed pr\u00e1ce bez velk\u00e9 diskrece. Toto je tak\u00e9 d\u016fvod, pro\u010d se smluvn\u00ed typy \u010dasto l\u00e9pe hod\u00ed pro quasi-mand\u00e1ty, zejm\u00e9na v p\u0159\u00edpad\u011b upstream proces\u016f.<\/p>\n\n\n\n<p>Souvisej\u00edc\u00ed \u010dl\u00e1nek: <a href=\"https:\/\/monolith.law\/corporate\/contract-and-timeandmaterialcontract\" target=\"_blank\" rel=\"noreferrer noopener\">Rozd\u00edl a rozli\u0161en\u00ed mezi smlouvou o d\u00edlo a quasi-mand\u00e1tn\u00ed smlouvou v syst\u00e9mov\u00e9m v\u00fdvoji[ja]<\/a><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Diskrece_by_mela_byt_uplatnovana_i_v_ramci_prisnych_vyvojovych_procesu\"><\/span>Diskrece by m\u011bla b\u00fdt uplat\u0148ov\u00e1na i v r\u00e1mci p\u0159\u00edsn\u00fdch v\u00fdvojov\u00fdch proces\u016f<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>Av\u0161ak, i kdy\u017e dodavatel v\u00fdvoje syst\u00e9mu m\u00e1 velkou diskreci, p\u0159ij\u00edm\u00e1n\u00ed po\u017eadavk\u016f klienta &#8220;na posledn\u00ed chv\u00edli&#8221; m\u016f\u017ee zp\u016fsobit zna\u010dn\u00e9 \u0161kody v pozd\u011bj\u0161\u00edch f\u00e1z\u00edch. Jeden IT syst\u00e9m se skl\u00e1d\u00e1 z mnoha mal\u00fdch komponent, a proto i mal\u00e9 zm\u011bny na povrchu mohou vy\u017eadovat zna\u010dn\u00e9 zm\u011bny v pracovn\u00ed dob\u011b z pohledu v\u00fdvoj\u00e1\u0159\u016f. K t\u00e9matu zm\u011bn specifikac\u00ed v\u00fdvoje syst\u00e9m\u016f existuje n\u00e1sleduj\u00edc\u00ed \u010dl\u00e1nek, kter\u00fd vysv\u011btluje, jak spravovat zm\u011bny z pr\u00e1vn\u00edho hlediska. Tento \u010dl\u00e1nek vysv\u011btluje, jak spravovat zm\u011bny, ale tak\u00e9 diskutuje o tom, jak velk\u00fd dopad mohou m\u00edt zm\u011bny specifikac\u00ed na pr\u00e1ci z pohledu technik\u016f.<\/p>\n\n\n\n<p>Souvisej\u00edc\u00ed \u010dl\u00e1nek: <a href=\"https:\/\/monolith.law\/corporate\/howto-manage-change-in-system-development\" target=\"_blank\" rel=\"noreferrer noopener\">Jak spravovat zm\u011bny v syst\u00e9mov\u00e9m v\u00fdvoji z pr\u00e1vn\u00edho hlediska[ja]<\/a><br><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Co_by_meli_odbornici_delat_aniz_by_byli_omezeni_specifikacemi\"><\/span>Co by m\u011bli odborn\u00edci d\u011blat, ani\u017e by byli omezeni specifikacemi?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>Pro hladk\u00fd pr\u016fb\u011bh projektu v\u00fdvoje syst\u00e9mu je d\u016fle\u017eit\u00e9 p\u0159edem definovat po\u017eadavky na v\u00fdvoj a pl\u00e1novat podle nich. Na druhou stranu, existuj\u00ed situace, kdy nem\u016f\u017eete pln\u011b vykon\u00e1vat svou roli jako odborn\u00edk na v\u00fdvoj syst\u00e9m\u016f, pokud jen d\u011bl\u00e1te to, co v\u00e1m bylo \u0159e\u010deno podle p\u0159edem definovan\u00fdch po\u017eadavk\u016f. V tomto dilematu se objevuje ot\u00e1zka &#8220;Co by m\u011blo b\u00fdt implementov\u00e1no, i kdy\u017e to nen\u00ed uvedeno ve specifikac\u00edch?&#8221;.<br><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Pravni_povinnosti_jsou_stanoveny_v_souladu_s_%E2%80%9Cucelem%E2%80%9D_specifikaci_a_smluv\"><\/span>Pr\u00e1vn\u00ed povinnosti jsou stanoveny v souladu s &#8220;\u00fa\u010delem&#8221; specifikac\u00ed a smluv<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Obsah toho, co je t\u0159eba implementovat, je ur\u010den podle &#8220;\u00fa\u010delu&#8221;, tedy &#8220;jak\u00fd v\u00fdznam nebo z\u00e1m\u011br byl p\u0159i uzav\u00edr\u00e1n\u00ed dohody&#8221;, i kdyby nebyl uveden v smlouv\u011b nebo specifikac\u00edch. Pod\u00edvejme se na n\u011bkolik p\u0159\u00edklad\u016f soudn\u00edch rozhodnut\u00ed.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Pripad_kde_povinnost_implementace_byla_poprena_kvuli_absenci_zaznamu\"><\/span>P\u0159\u00edpad, kde povinnost implementace byla pop\u0159ena kv\u016fli absenci z\u00e1znamu<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>N\u00e1sleduj\u00edc\u00ed citovan\u00fd p\u0159\u00edpad se t\u00fdk\u00e1 syst\u00e9mu, kter\u00fd vyvinul dodavatel a kter\u00fd se dostal a\u017e do f\u00e1ze testov\u00e1n\u00ed, kdy do\u0161lo k sporu o zru\u0161en\u00ed smlouvy kv\u016fli nedostate\u010dn\u00fdm funkc\u00edm. U\u017eivatel tvrdil, \u017ee chyb\u00ed &#8220;funkce automatick\u00e9 aktualizace dat&#8221;, co\u017e byl \u00fadajn\u011b hlavn\u00ed prodejn\u00ed bod tohoto syst\u00e9mu, ale soud tuto povinnost implementace neuznal.<br><\/p>\n\n\n\n<blockquote class=\"wp-block-quote\">\n<p>Jak bylo uzn\u00e1no v\u00fd\u0161e, v smlouv\u011b o tomto p\u0159\u00edpadu, z\u00e1kladn\u00edm n\u00e1vrhu a detailn\u00edm n\u00e1vrhu nejsou \u017e\u00e1dn\u00e9 z\u00e1znamy, kter\u00e9 by ukazovaly, \u017ee funkce \u2462 je c\u00edlem v\u00fdvoje tohoto syst\u00e9mu.<\/p>\n\n\n\n<p>\u017dalobce tvrd\u00ed, \u017ee funkce \u2462 byla hlavn\u00edm prodejn\u00edm bodem syst\u00e9mu pro \u017ealobce ze strany \u017ealovan\u00e9ho a zd\u016fraz\u0148uje pot\u0159ebu t\u00e9to funkce, <u>ale pokud by to bylo tak, jak tvrd\u00ed, m\u011blo by to b\u00fdt jasn\u011b uvedeno v smlouv\u011b atd.<\/u>, <u>a je t\u011b\u017ek\u00e9 si p\u0159edstavit, \u017ee by byl dohodnut v\u00fdvoj t\u00e9to funkce bez toho<\/u>.<\/p>\n<cite>Tokijsk\u00fd okresn\u00ed soud, 18. \u00fanora 2009 (Heisei 21)<\/cite><\/blockquote>\n\n\n\n<p>Toto rozhodnut\u00ed jist\u011b m\u016f\u017ee b\u00fdt jednodu\u0161e shrnuto jako &#8220;Pokud to nen\u00ed uvedeno v n\u00e1vrhu, nemus\u00edte to vytvo\u0159it&#8221;. Av\u0161ak p\u0159esn\u011bji \u0159e\u010deno, rozhodnut\u00ed bylo u\u010din\u011bno na z\u00e1klad\u011b &#8220;\u00fa\u010delu&#8221; z\u00e1znam\u016f v n\u00e1vrhu a smlouv\u011b, nikoli na z\u00e1klad\u011b form\u00e1ln\u00edch skute\u010dnost\u00ed, zda je z\u00e1znam v n\u00e1vrhu nebo ne. Jin\u00fdmi slovy, &#8220;Pokud zv\u00e1\u017e\u00edme d\u016fvody, pro\u010d nebylo v n\u00e1vrhu a smlouv\u011b nic uvedeno, je rozumn\u00e9 se domn\u00edvat, \u017ee nebyla dohodnuta \u017e\u00e1dn\u00e1 dohoda odpov\u00eddaj\u00edc\u00ed tomuto z\u00e1znamu&#8221;.<br><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Pripad_kde_byla_potvrzena_povinnost_implementace_i_bez_zapisu\"><\/span>P\u0159\u00edpad, kde byla potvrzena povinnost implementace i bez z\u00e1pisu<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>Na druhou stranu, existuj\u00ed p\u0159\u00edpady, kdy byla potvrzena povinnost implementace, i kdy\u017e nebyla uvedena v smlouv\u011b nebo specifikac\u00edch. N\u00e1sleduj\u00edc\u00ed citovan\u00fd p\u0159\u00edpad se t\u00fdk\u00e1 v\u00fdvoje syst\u00e9mu pro spr\u00e1vu historie u\u017e\u00edv\u00e1n\u00ed l\u00e9k\u016f, kde se nepoda\u0159ilo p\u0159en\u00e9st data z existuj\u00edc\u00edho syst\u00e9mu do nov\u00e9ho syst\u00e9mu, co\u017e znemo\u017enilo vyu\u017eit\u00ed nov\u00e9ho syst\u00e9mu a u\u017eivatel\u00e9 tak ukon\u010dili smlouvu. Nicm\u00e9n\u011b, dodavatel se br\u00e1nil t\u00edm, \u017ee p\u0159enos dat je mimo rozsah jeho pr\u00e1ce, co\u017e vedlo k sporu.<\/p>\n\n\n\n<p>V\u00fdvoj nov\u00e9ho syst\u00e9mu \u010dasto zahrnuje odstran\u011bn\u00ed existuj\u00edc\u00edho syst\u00e9mu a p\u0159enos dat. D\u016fle\u017eitost t\u011bchto \u00fakol\u016f a s nimi souvisej\u00edc\u00ed pr\u00e1vn\u00ed probl\u00e9my jsou podrobn\u011b vysv\u011btleny v n\u00e1sleduj\u00edc\u00edm \u010dl\u00e1nku.<\/p>\n\n\n\n<p>Souvisej\u00edc\u00ed \u010dl\u00e1nek: <a href=\"https:\/\/monolith.law\/corporate\/the-transition-from-the-oldsystem\" target=\"_blank\" rel=\"noreferrer noopener\">Pr\u00e1vn\u00ed probl\u00e9my spojen\u00e9 s p\u0159echodem ze star\u00e9ho syst\u00e9mu p\u0159i v\u00fdvoji syst\u00e9mu[ja]<\/a><\/p>\n\n\n\n<blockquote class=\"wp-block-quote\">\n<p>V existuj\u00edc\u00edm syst\u00e9mu byla ji\u017e ulo\u017eena data v\u00edce ne\u017e 50 000 pacient\u016f a <u>\u017ealobce se sna\u017eil zefektivnit administrativu vyu\u017eit\u00edm t\u011bchto dat<\/u>. Pokud by nebylo mo\u017en\u00e9 p\u0159en\u00e9st data pacient\u016f z existuj\u00edc\u00edho syst\u00e9mu do nov\u00e9ho syst\u00e9mu, <u>je z\u0159ejm\u00e9, \u017ee by to zp\u016fsobilo probl\u00e9my v l\u00e9k\u00e1rn\u011b<\/u>. Je tedy mo\u017en\u00e9 p\u0159edpokl\u00e1dat, \u017ee i z\u00e1stupce \u017ealobce <u>si toho byl jist\u011b v\u011bdom<\/u>. A p\u0159ed uzav\u0159en\u00edm smlouvy se z\u00e1stupce \u017ealobce zeptal z\u00e1stupce \u017ealovan\u00e9ho na mo\u017enost p\u0159enosu dat, co\u017e z\u00e1stupce \u017ealovan\u00e9ho tak\u00e9 uznal (vynech\u00e1no). U z\u00e1stupce \u017ealobce je <u>vysok\u00e1 pravd\u011bpodobnost, \u017ee si uv\u011bdomil, \u017ee bude muset ru\u010dn\u011b zadat data v\u00edce ne\u017e 50 000 pacient\u016f<\/u>, a <u>je t\u011b\u017ek\u00e9 si p\u0159edstavit, \u017ee by se rozhodl zav\u00e9st nov\u00fd syst\u00e9m<\/u>. Nav\u00edc, jak je uvedeno v\u00fd\u0161e v bod\u011b (1) I, \u017ealovan\u00fd nemohl p\u0159en\u00e9st data o l\u00e9k\u00e1rn\u011b z existuj\u00edc\u00edho syst\u00e9mu do nov\u00e9ho syst\u00e9mu, tak\u017ee tiskl tato data na pap\u00edr a zpracov\u00e1val je do PDF soubor\u016f, i kdy\u017e p\u0159enos dat nebyl p\u0159edpokl\u00e1d\u00e1n v smlouv\u011b, <u>je t\u011b\u017ek\u00e9 si p\u0159edstavit, \u017ee by \u017ealovan\u00fd prov\u00e1d\u011bl takovou n\u00e1ro\u010dnou pr\u00e1ci jako slu\u017ebu<\/u>.<\/p>\n<cite>Verdikt Tokijsk\u00e9ho soudu ze dne 18. listopadu 2010 (Heisei 22)<\/cite><\/blockquote>\n\n\n\n<p>Co je zde d\u016fle\u017eit\u00e9, je &#8220;\u00fa\u010del&#8221; smlouvy a &#8220;z\u00e1m\u011br&#8221; uveden\u00fd v smlouv\u011b. Pokud by ob\u011b strany uzav\u0159ely smlouvu s v\u011bdom\u00edm, \u017ee p\u0159enos dat je mimo rozsah pr\u00e1ce, soud pouk\u00e1zal na to, \u017ee by to znamenalo, \u017ee ob\u011b strany &#8211; u\u017eivatel i dodavatel &#8211; uzav\u0159ely smlouvu s neobvykl\u00fdm \u00famyslem. Jin\u00fdmi slovy, u\u017eivatel by p\u0159ijal obrovsk\u00e9 mno\u017estv\u00ed ru\u010dn\u00ed pr\u00e1ce a dodavatel by se p\u0159ipravil na projekt, v\u011bdom si, \u017ee to bude zp\u016fsobovat probl\u00e9my v pr\u00e1ci u\u017eivatele, co\u017e je velmi nesmysln\u00e9.<br><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Co_lze_vycist_z_obou_rozsudku\"><\/span>Co lze vy\u010d\u00edst z obou rozsudk\u016f<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>I kdy\u017e v smlouv\u011b nebo specifikaci nebylo nic uvedeno o p\u0159enosu dat, povinnost implementace byla potvrzena. Jedn\u00edm z d\u016fvod\u016f m\u016f\u017ee b\u00fdt skute\u010dnost, \u017ee se jednalo o &#8220;data&#8221;, co\u017e je ot\u00e1zka, kter\u00e1 se neprojevuje na vzhledu obrazovky. P\u0159edchoz\u00ed &#8220;chyb\u011bj\u00edc\u00ed nezbytn\u00e1 funkce&#8221; je n\u011bco, co se p\u0159\u00edmo projevuje na obrazovce nebo vzhledu syst\u00e9mu. Proto, i kdy\u017e jste laik v oblasti v\u00fdvoje syst\u00e9m\u016f, nen\u00ed tak t\u011b\u017ek\u00e9 objevit chyb\u011bj\u00edc\u00ed informace ve specifikaci. Na druh\u00e9 stran\u011b, probl\u00e9m p\u0159enosu dat m\u00e1 charakteristiku, \u017ee laici v oblasti v\u00fdvoje syst\u00e9m\u016f maj\u00ed obt\u00ed\u017ee s pochopen\u00edm d\u016fle\u017eitosti procesu, slo\u017eitosti pr\u00e1ce a pracovn\u00ed doby. Proto se tak\u00e9 p\u0159edpokl\u00e1d\u00e1, \u017ee byl situace, kdy bylo snadn\u00e9 o\u0161et\u0159ovat ot\u00e1zky, kter\u00e9 by m\u011bl dodavatel \u0159\u00eddit hladce s odbornost\u00ed.<\/p>\n\n\n\n<p>Pokud o tom takto p\u0159em\u00fd\u0161l\u00edme, vynech\u00e1n\u00ed informac\u00ed ve specifikaci nebo smlouv\u011b je tak\u00e9 probl\u00e9m \u00fazce spojen\u00fd s &#8220;povinnost\u00ed spolupr\u00e1ce&#8221; u\u017eivatele. Jin\u00fdmi slovy, je ot\u00e1zkou, zda u\u017eivatel skute\u010dn\u011b splnil svou &#8220;povinnost spolupr\u00e1ce&#8221; p\u0159i uzav\u00edr\u00e1n\u00ed smlouvy a vytv\u00e1\u0159en\u00ed specifikace. Celkov\u00fd v\u00fdklad pr\u00e1vn\u00edch povinnost\u00ed, kter\u00e9 by m\u011bl u\u017eivatel splnit v r\u00e1mci projektu v\u00fdvoje syst\u00e9mu, je podrobn\u011b pops\u00e1n v n\u00e1sleduj\u00edc\u00edm \u010dl\u00e1nku.<\/p>\n\n\n\n<p>Souvisej\u00edc\u00ed \u010dl\u00e1nek: <a href=\"https:\/\/monolith.law\/corporate\/user-obligatory-cooporation\" target=\"_blank\" rel=\"noreferrer noopener\">Jak\u00e9 jsou povinnosti spolupr\u00e1ce na stran\u011b u\u017eivatele, kter\u00fd objedn\u00e1v\u00e1 v\u00fdvoj syst\u00e9mu[ja]<\/a><\/p>\n\n\n\n<p>Pokud si p\u0159e\u010dtete tak\u00e9 v\u00fd\u0161e uveden\u00fd \u010dl\u00e1nek, m\u011bli byste b\u00fdt schopni pochopit, \u017ee v oblastech, kde je velk\u00e1 popt\u00e1vka po spolupr\u00e1ci u\u017eivatele, jako je identifikace obrazovky a nezbytn\u00fdch funkc\u00ed, a v p\u0159\u00edpad\u011b vynech\u00e1n\u00ed p\u0159em\u00fd\u0161len\u00ed o p\u0159enosu dat, je p\u0159\u00edb\u011bh zna\u010dn\u011b odli\u0161n\u00fd.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Jak_bychom_meli_uvazovat_o_odmene_za_vyvoj_ktery_neni_uveden_v_specifikacich\"><\/span>Jak bychom m\u011bli uva\u017eovat o odm\u011bn\u011b za v\u00fdvoj, kter\u00fd nen\u00ed uveden v specifikac\u00edch?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/monolith.law\/wp-content\/uploads\/2019\/10\/shutterstock_320070512-1024x683.jpg\" alt=\"\" class=\"wp-image-5433\" \/><figcaption class=\"wp-element-caption\">V p\u0159\u00edpad\u011b, \u017ee dodavatel reaguje na pr\u00e1ci p\u0159esahuj\u00edc\u00ed r\u00e1mec \u00fakolu, m\u016f\u017ee b\u00fdt mo\u017en\u00e9 po\u017eadovat dodate\u010dnou odm\u011bnu.<\/figcaption><\/figure>\n\n\n\n<p>Dal\u0161\u00ed ot\u00e1zkou, kter\u00e1 souvis\u00ed s t\u00e9matem tohoto \u010dl\u00e1nku a kter\u00e1 v\u00e1s mo\u017en\u00e1 zaj\u00edm\u00e1, je, zda je mo\u017en\u00e9 z hlediska pr\u00e1va po\u017eadovat vy\u0161\u0161\u00ed odm\u011bnu, pokud vytvo\u0159\u00edte n\u011bco, co nen\u00ed uvedeno ve specifikac\u00edch. O mo\u017enosti zv\u00fd\u0161en\u00ed odm\u011bny a o zp\u016fsobu v\u00fdpo\u010dtu odhadovan\u00e9 \u010d\u00e1stky v p\u0159\u00edpad\u011b, \u017ee je to mo\u017en\u00e9, se dozv\u00edte v\u00edce v n\u00e1sleduj\u00edc\u00edm \u010dl\u00e1nku.<\/p>\n\n\n\n<p>Souvisej\u00edc\u00ed \u010dl\u00e1nek: <a href=\"https:\/\/monolith.law\/corporate\/increase-of-estimate\" target=\"_blank\" rel=\"noreferrer noopener\">Je mo\u017en\u00e9 zv\u00fd\u0161it odhadovanou \u010d\u00e1stku pro v\u00fdvoj syst\u00e9mu?[ja]<\/a><\/p>\n\n\n\n<p>V \u010dl\u00e1nku v\u00fd\u0161e je vysv\u011btleno, \u017ee d\u016fle\u017eit\u00e9 je, zda existovala pr\u00e1ce p\u0159esahuj\u00edc\u00ed r\u00e1mec \u00fakolu, kter\u00fd byl v pom\u011bru k odm\u011bn\u011b. Jin\u00fdmi slovy, pokud se vztahuje na tento \u010dl\u00e1nek, pokud dodavatel reaguje na v\u00fdvoj n\u011b\u010deho, co nebylo zahrnuto v p\u016fvodn\u00edch specifikac\u00edch (v tomto \u010dl\u00e1nku, negativn\u00ed p\u0159\u00edklad), je mo\u017en\u00e9 uznat po\u017eadavek na dodate\u010dnou odm\u011bnu.<br><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Shrnuti\"><\/span>Shrnut\u00ed<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>V oblasti v\u00fdvoje syst\u00e9m\u016f je role, kterou by m\u011bl dodavatel hr\u00e1t, ur\u010dena podle obsahu smlouvy a specifikac\u00ed na jedn\u00e9 stran\u011b. Nicm\u00e9n\u011b, s ohledem na skute\u010dnost, \u017ee jsou jako odborn\u00edci sv\u011b\u0159eni s prac\u00ed na z\u00e1klad\u011b vysok\u00e9 d\u016fv\u011bry, je tak\u00e9 z\u0159ejm\u00e9, \u017ee jejich skute\u010dn\u00e1 podstata nen\u00ed ur\u010dena pouze form\u00e1ln\u011b. P\u0159esto bychom m\u011bli pochopit, \u017ee pr\u00e1vo hraje velkou roli p\u0159i pochopen\u00ed jejich skute\u010dn\u00e9 podstaty.<br><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Projekty na v\u00fdvoj IT syst\u00e9m\u016f pou\u017e\u00edvan\u00fdch v podnic\u00edch jsou v z\u00e1sad\u011b vytv\u00e1\u0159eny v souladu s p\u0159edem definovan\u00fdmi specifikacemi. Nicm\u00e9n\u011b, pokud zv\u00e1\u017e\u00edme v\u00fdznam toho, \u017ee dodavatel je jako odborn\u00edk na v\u00fdvoj s [&hellip;]<\/p>\n","protected":false},"author":32,"featured_media":63167,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[19,31],"acf":[],"_links":{"self":[{"href":"https:\/\/monolith.law\/cs\/wp-json\/wp\/v2\/posts\/61294"}],"collection":[{"href":"https:\/\/monolith.law\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/monolith.law\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/monolith.law\/cs\/wp-json\/wp\/v2\/users\/32"}],"replies":[{"embeddable":true,"href":"https:\/\/monolith.law\/cs\/wp-json\/wp\/v2\/comments?post=61294"}],"version-history":[{"count":2,"href":"https:\/\/monolith.law\/cs\/wp-json\/wp\/v2\/posts\/61294\/revisions"}],"predecessor-version":[{"id":63168,"href":"https:\/\/monolith.law\/cs\/wp-json\/wp\/v2\/posts\/61294\/revisions\/63168"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/monolith.law\/cs\/wp-json\/wp\/v2\/media\/63167"}],"wp:attachment":[{"href":"https:\/\/monolith.law\/cs\/wp-json\/wp\/v2\/media?parent=61294"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/monolith.law\/cs\/wp-json\/wp\/v2\/categories?post=61294"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/monolith.law\/cs\/wp-json\/wp\/v2\/tags?post=61294"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}