LEADER 01717oam 2200565I 450 001 9910450070703321 005 20200520144314.0 010 $a1-134-53904-5 010 $a0-415-24753-5 010 $a1-280-03209-X 010 $a9786610032099 010 $a0-203-64705-X 024 7 $a10.4324/9780203647059 035 $a(MiAaPQ)EBC200038 035 $a(Au-PeEL)EBL200038 035 $a(CaPaEBR)ebr10166240 035 $a(CaONFJC)MIL3209 035 $a(OCoLC)475908557 035 $a(OCoLC)56545441 035 $a(EXLCZ)991000000000249021 100 $a20180331d2004 uy 0 101 0 $aeng 135 $aurun#|||uuuuu 200 00$aCyberculture $ethe key concepts /$fDavid Bell. [et al.] 210 1$aLondon ;$aNew York :$cRoutledge,$d2004. 215 $a201p 225 1 $aRoutledge key guides 300 $aDescription based upon print version of record. 311 $a0-203-68664-0 311 $a0-415-24754-3 320 $aIncludes bibliographical references (p.196-205) and index. 327 $achapter KEY CONCEPTS -- THE KEY CONCEPTS. 410 0$aRoutledge key guides. 606 $aInformation technology$xSocial aspects$vEncyclopedias 606 $aComputers and civilization$vEncyclopedias 606 $aInternet$vEncyclopedias 608 $aElectronic books. 615 0$aInformation technology$xSocial aspects 615 0$aComputers and civilization 615 0$aInternet 676 $a303.48/34 686 $a05.20$2bcl 701 $aBell$b David$f1965 Feb. 12-$0969606 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910450070703321 996 $aCyberculture$92203495 997 $aUNINA LEADER 04900nam 2200697 450 001 9910585954203321 005 20230125185911.0 010 $a1-108-90692-3 010 $a1-108-91079-3 010 $a1-108-91485-3 035 $a(CKB)5470000001298901 035 $a(UkCbUP)CR9781108914857 035 $a(oapen)https://directory.doabooks.org/handle/20.500.12854/90901 035 $a(PPN)25826490X 035 $a(EXLCZ)995470000001298901 100 $a20200309d2022|||| uy| 0 101 0 $aeng 135 $aur||||||||||| 181 $ctxt$2rdacontent 182 $cc$2rdamedia 183 $acr$2rdacarrier 200 00$aConstitutional challenges in the algorithmic society /$fedited by Hans Wolfgang Micklitz, Oreste Pollicino, Amnon Reichman, Andrea Simoncini, Giovanni Sartor, Giovanni De Gregorio$b[electronic resource] 210 $cCambridge University Press$d2021 210 1$aCambridge :$cCambridge University Press,$d2022. 215 $a1 online resource (x, 330 pages) $cdigital, PDF file(s) 225 1 $aSocial Sciences 300 $aTitle from publisher's bibliographic system (viewed on 01 Nov 2021). 311 1 $a1-108-84312-3 327 $aOreste Pollicino and Giovanni De Gregorio, Constitutional law in the algorithmic society -- Andrea Simoncini and Erik Longo, Fundamental rights and the rule of law in the algorithmic society by law? -- Celine Castest-Renard, Human rights and algorithmic impact assessment for predictive policing -- Francesca Galli, Law enforcement and data-driven predictions at the national and EU level : a challenge to the presumption of innocence and reasonable suspicion? -- Amnon Reichman and Giovanni Sartor, Algorithms and regulation -- Angela Daly, Thilo Hagendorff, Li Hui, Monique Mann, Vidushi Marda, Ben Wagner, Wayne Wei Wang, Artificial Intelligence, governance and ethics : global perspectives -- Pieter Vancleynenbreugel, EU by-design regulation in the algorithmic society : promising way forward or constitutional nightmare in-the-making? -- Henrik Palmer Olsen, Jacob Livingston Slosser and Thomas Troels Hildebrandt, What's in the box? The legal requirement of explainability in computationally, eided decision-making in public ddministration -- Yaiza Cabedo, The international regulatory race for protecting investors from crypto-finance risks -- Hans W. Micklitz and Anne Aurelie Villanueva, Responsibilities of companies in the algorithmic society -- Serge Gijrath, Consumer law as a tool to regulate adverse consequences of AI output -- Federica Casarosa, When the algorithm is not fully reliable : the collaboration between technology and humans in the fight against hate speech -- Pietro Sirena and Francesco Paolo Patti, Smart contracts and automation of private relationships. 330 $aNew technologies have always challenged the social, economic, legal, and ideological status quo. Constitutional law is no less impacted by such technologically driven transformations, as the state must formulate a legal response to new technologies and their market applications, as well as the state's own use of new technology. In particular, the development of data collection, data mining, and algorithmic analysis by public and private actors present unique challenges to public law at the doctrinal as well as the theoretical level. This collection, aimed at legal scholars and practitioners, describes the constitutional challenges created by the algorithmic society. It offers an important synthesis of the state of play in law and technology studies, addressing the challenges for fundamental rights and democracy, the role of policy and regulation, and the responsibilities of private actors. This title is also available as Open Access on Cambridge Core. 606 $aConstitutional law$xDecision making 606 $aAlgorithms$xSocial aspects 606 $aJudicial process 606 $aLegislation 606 $aArtificial intelligence$xLaw and legislation 610 $abig data 610 $aconstitutions 610 $amass surveillance 610 $apredictive policing 610 $adue process 610 $aalgorithms 610 $aartificial intelligence 615 0$aConstitutional law$xDecision making. 615 0$aAlgorithms$xSocial aspects. 615 0$aJudicial process. 615 0$aLegislation. 615 0$aArtificial intelligence$xLaw and legislation. 676 $a342 700 $aMicklitz$b Hans-W$4edt$0277807 702 $aMicklitz$b Hans-W. 702 $aPollicino$b Oreste 702 $aReichman$b Amnon$f1967- 702 $aSimoncini$b Andrea$c(Law professor), 702 $aSartor$b Giovanni 702 $aDe Gregorio$b Giovanni 801 0$bUkCbUP 801 1$bUkCbUP 906 $aBOOK 912 $a9910585954203321 996 $aConstitutional challenges in the algorithmic society$93359658 997 $aUNINA LEADER 01482nam 2200457Ia 450 001 9910711119303321 005 20180711120953.0 024 8 $aGOVPUB-C13-5f6eb3c7714de5ac950991caf97b7807 035 $a(CKB)5470000002480821 035 $a(OCoLC)959982234 035 $a(OCoLC)995470000002480821 035 $a(EXLCZ)995470000002480821 100 $a20161006d1963 ua 0 101 0 $aeng 181 $ctxt$2rdacontent 182 $cc$2rdamedia 183 $acr$2rdacarrier 200 10$aExperimental fires in enclosures C.I.B. test results /$fDaniel Gross 210 1$aGaithersburg, MD :$cU.S. Dept. of Commerce, National Institute of Standards and Technology,$d1963. 215 $a1 online resource 225 1 $aNBS report ;$v8131 300 $a1963. 300 $aContributed record: Metadata reviewed, not verified. Some fields updated by batch processes. 300 $aTitle from PDF title page. 320 $aIncludes bibliographical references. 606 $aFire testing 606 $aFire testing$2fast 615 0$aFire testing. 615 7$aFire testing. 700 $aGross$b Daniel$0594468 701 $aGross$b Daniel$0594468 712 02$aUnited States.$bNational Bureau of Standards. 801 0$bNBS 801 1$bNBS 801 2$bOCLCO 801 2$bOCLCF 801 2$bOCLCQ 906 $aBOOK 912 $a9910711119303321 996 $aExperimental fires in enclosures C.I.B. test results$93538343 997 $aUNINA LEADER 02319nas 2200709-a 450 001 996206057203316 005 20231101153820.0 011 $a1936-0592 035 $a(OCoLC)85253006 035 $a(CKB)1000000000319581 035 $a(CONSER)--2007214237 035 $a(DE-599)ZDB2418105-5 035 $a(EXLCZ)991000000000319581 100 $a20070226a20089999 s-- a 101 0 $aeng 135 $aur||||||||||| 181 $ctxt$2rdacontent 182 $cc$2rdamedia 183 $acr$2rdacarrier 200 10$aEcohydrology $eecosystems, land and water process interactions, ecohydrogeomorphology 210 $aChichester, West Sussex, UK $cJohn Wiley & Sons$d©2007- 300 $aRefereed/Peer-reviewed 311 $a1936-0584 517 3 $aEcohydrol 606 $aEcohydrology$vPeriodicals 606 $aHydrology$vPeriodicals 606 $aWater$xEnvironmental aspects$vPeriodicals 606 $aAquatic ecology$vPeriodicals 606 $aBodies of water$xEnvironmental aspects$vPeriodicals 606 $aHydrologie$vPériodiques 606 $aÉcologie des eaux$vPériodiques 606 $aEaux$xAspect de l'environnement$vPériodiques 606 $aÉcohydrologie$vPériodiques 606 $aEau$xAspect de l'environnement$vPériodiques 606 $aAquatic ecology$2fast$3(OCoLC)fst00811988 606 $aEcohydrology$2fast$3(OCoLC)fst00901439 606 $aHydrology$2fast$3(OCoLC)fst00965147 606 $aWater$xEnvironmental aspects$2fast$3(OCoLC)fst01171209 608 $aPeriodical 608 $aperiodicals.$2aat 608 $aPeriodicals.$2fast 608 $aPeriodicals.$2lcgft 608 $aPériodiques.$2rvmgf 615 0$aEcohydrology 615 0$aHydrology 615 0$aWater$xEnvironmental aspects 615 0$aAquatic ecology 615 0$aBodies of water$xEnvironmental aspects 615 6$aHydrologie 615 6$aÉcologie des eaux 615 6$aEaux$xAspect de l'environnement 615 6$aÉcohydrologie 615 6$aEau$xAspect de l'environnement 615 7$aAquatic ecology. 615 7$aEcohydrology. 615 7$aHydrology. 615 7$aWater$xEnvironmental aspects. 676 $a551.48 906 $aJOURNAL 912 $a996206057203316 996 $aEcohydrology$9797905 997 $aUNISA LEADER 21556nam 2200793 450 001 9910829909703321 005 20240219134639.0 010 $a1-281-03229-8 010 $a9786611032296 010 $a0-470-16517-0 010 $a0-470-16516-2 024 7 $a10.1002/9780470165171 035 $a(CKB)1000000000376977 035 $a(EBL)316185 035 $a(SSID)ssj0000107929 035 $a(PQKBManifestationID)11114286 035 $a(PQKBTitleCode)TC0000107929 035 $a(PQKBWorkID)10015108 035 $a(PQKB)10494251 035 $a(MiAaPQ)EBC316185 035 $a(CaBNVSL)mat05201515 035 $a(IDAMS)0b0000648104a9bd 035 $a(IEEE)5201515 035 $a(OCoLC)181349072 035 $a(PPN)256182833 035 $a(EXLCZ)991000000000376977 100 $a20071115h20152007 uy 0 101 0 $aeng 135 $aur|n|---||||| 181 $ctxt 182 $cc 183 $acr 200 10$aAutomated defect prevention $ebest practices in software management /$fDorota Huizinga, Adam Kolawa 210 1$aHoboken, New Jersey :$cWiley-Interscience :$dc2007. 215 $a1 online resource (454 p.) 300 $aDescription based upon print version of record. 311 $a0-470-04212-5 320 $aIncludes bibliographical references and index. 327 $aPreface -- Features and Organization -- Practice Descriptions -- Intended audience -- Acknowledgements -- Permissions -- Disclaimer -- 1. The Case for Automated Defect Prevention -- 1.1 What is ADP? -- 1.2 What are the goals of ADP? -- 1.2.1 People: Stimulated and Satisfied -- 1.2.2 Product: High Quality -- 1.2.3 Organization: Increased Productivity and Operational Efficiency -- 1.2.4 Process: Controlled, Improved, and Sustainable -- 1.2.5 Project: Managed through Informed Decision Making -- 1.3 How is ASDP implemented? -- 1.3.1 Principles -- 1.3.2 Practices -- 1.3.3 Policies -- 1.3.4 Defect Prevention Mindset -- 1.3.5 Automation -- 1.4 From the waterfall to modern software development process models -- 1.5 Acronyms -- 1.6 Glossary -- 1.7 References -- 1.8 Exercises -- 2. Principles of Automated Defect Prevention -- 2.1 Introduction -- 2.2 Defect Prevention: Definition and Benefits -- 2.3 Historical Perspective: Defect Analysis and Prevention in Auto Industry - What Happened to Deming? -- 2.4 Principles of Automated Defect Prevention -- 2.4.1 Principle 1: Establishment of Infrastructure: "Build a strong foundation through integration of people and technology" -- 2.4.2 Principle 2: Application of General Best Practices: "Learn from others' mistakes" -- 2.4.3 Principle 3: Customization of Best Practices: "Learn from your own mistakes" -- 2.4.4 Principle 4: Measurement and Tracking of Project Status: "Understand the past and present to make decisions about the future" -- 2.4.5 Principle 5: Automation: "Let the computer do it" -- 2.4.6 Principle 6: Incremental Implementation of ADP's Practices and Policies -- 2.5 Automated Defect Prevention based Software Development Process Model -- 2.6 Examples -- 2.6.1 Focus on Root Cause Analysis of a Defect -- 2.6.2 Focus on Infrastructure -- 2.6.3 Focus on Customized Best Practice -- 2.6.4 Focus on Measurements of Project Status -- 2.7 Acronyms -- 2.8 Glossary -- 2.9 References -- 2.10 Exercises. 327 $a3. Initial Planning and Infrastructure -- 3.1 Introduction -- 3.2 Initial Software Development Plan -- 3.2.1 Product -- 3.2.2 People -- 3.2.3 Technology -- 3.2.4 Process -- 3.3 Best Practices for Creating People Infrastructure -- 3.3.1 Defining Groups -- 3.3.2 Determining a Location for Each Group's Infrastructure -- 3.3.3 Defining People Roles -- 3.3.4 Establishing Training Program -- 3.3.5 Cultivating a Positive Group Culture -- 3.4 Best Practices for Creating Technology Infrastructure -- 3.4.1 Automated Reporting System -- 3.4.2 Policy for Use of Automated Reporting System -- 3.4.3 Minimum Technology Infrastructure -- 3.4.4 Intermediate Technology Infrastructure -- 3.4.5 Expanded Technology Infrastructure -- 3.5 Integrating People and Technology -- 3.6 Human Factors and Concerns -- 3.7 Examples -- 3.7.1 Focus on Developer Ideas -- 3.7.2 Focus on Reports Generated by the Minimum Infrastructure -- 3.8 Acronyms -- 3.9 Glossary -- 3.10 References -- 3.11 Exercises -- 4. Requirements Specification and Management -- 4.1 Introduction -- 4.2 Best Practices for Gathering and Organizing Requirements -- 4.2.1 Creating the Product Vision and Scope Document -- 4.2.2 Gathering and Organizing Requirements -- 4.2.3 Prioritizing Requirements -- 4.2.4 Developing Use Cases -- 4.2.5 Creating a Prototype to Elicit Requirements -- 4.2.6 Creating Conceptual Test Cases -- 4.2.7 Requirements Documents Inspection -- 4.2.8 Managing Changing Requirements -- 4.3 Best Practices in Different Environments -- 4.3.1 Existing Versus New Software Project -- 4.3.2 In-House Versus Outsourced Development Teams -- 4.4 Policy for Use of the Requirements Management System -- 4.4.1 The project manager should approve the final version of the vision and scope document, which should be entered into, and tracked in, the requirements management system -- 4.4.2 The architect should approve the final version of the requirements specification (SRS) document. The requirements from SRS should be entered into, and their changes tracked in, the requirements management system. 327 $a4.4.3 The architect or lead developer should define the scope and test requirements for each feature to be implemented, and then enter those details in the requirements management system -- 4.4.4 The developer should create test cases for each feature she is assigned to implement, and add those test cases to the requirements management system -- 4.4.5 After the developer implements a feature, she should modify the test cases to verify the new feature, then, once the tests pass, she should mark the feature as "implemented" -- 4.4.6 Measurements Related to Requirement Management System -- 4.4.7 Tracking of Data Related to the Requirements Management System -- 4.5 Examples -- 4.5.1 Focus on Customized Best Practice -- 4.5.2 Focus on Monitoring and Managing Requirement Priorities -- 4.5.3 Focus on Change Requests -- 4.6 Acronyms -- 4.7 Glossary -- 4.8 References -- 4.9 Exercises -- 5. Extended Planning and Infrastructure -- 5.1 Introduction -- 5.2 Software Development Plan -- 5.3 Defining Project Objectives -- 5.4 Defining Project Artifacts and Deliverables -- 5.4.1 The Vision and Scope document -- 5.4.2 SRS, describing the product key features -- 5.4.3 Architectural and detailed design documents and models -- 5.4.4 List of COTS (Commercial-Off-the-Shelf-Components) used -- 5.4.5 Source and executable code -- 5.4.6 Test plan -- 5.4.7 Acceptance plan -- 5.4.8 Periodic reports generated by the reporting system -- 5.4.9 Deployment plan -- 5.4.10 User and operational manuals -- 5.4.11 Customer training plan -- 5.5 Selecting a Software Development Process Model -- 5.6 Defining Defect Prevention Process -- 5.7 Managing Risk -- 5.8 Managing Change -- 5.9 Defining Work Breakdown Structure (WBS) - An Iterative Approach -- 5.10 Best Practices for Estimating Project Effort -- 5.10.1 Estimation by Using Elements of Wideband Delphi -- 5.10.2 Estimation by Using Effort Analogy -- 5.10.3 Estimation by Using Parametric Models -- 5.10.4 Estimations of Using COTS and Code Reuse. 327 $a5.10.5 Estimation Quality Factor and the Iterative Adjustments of Estimates -- 5.11 Best Practices for Preparing the Schedule -- 5.12 Measurement and Tracking for Estimation -- 5.13 Identifying Additional Resource Requirements -- 5.13.1 Extending the Technology Infrastructure -- 5.13.2 Extending the People Infrastructure -- 5.14 Examples -- 5.14.1 Focus on the Root Cause of a Project Scheduling Problem -- 5.14.2 Focus on Organizing and Tracking Artifacts -- 5.14.3 Focus on Scheduling and Tracking Milestones -- 5.15 Acronyms -- 5.16 Glossary -- 5.17 References -- 5.18 Exercises -- 6. Architectural and Detailed Design -- 6.1 Introduction -- 6.2 Best Practices for Design of System Functionality and its Quality Attributes -- 6.2.1 Identifying Critical Attributes of Architectural Design -- 6.2.2 Defining the Policies for Design of Functional and Non-functional Requirements -- 6.2.3 Applying Design Patterns -- 6.2.4 Service Oriented Architecture -- 6.2.5 Mapping Requirements to Modules -- 6.2.6 Designing Module Interfaces -- 6.2.7 Modeling Modules and their Interfaces with UML -- 6.2.8 Defining Application Logic -- 6.2.9 Refining Test Cases -- 6.2.10 Design Document Storage and Inspection -- 6.2.11 Managing Changes in Design -- 6.3 Best Practices for Design of Graphical User Interface -- 6.3.1 Identifying Critical Attributes of User Interface Design -- 6.3.2 Defining the User Interface Design Policy -- 6.3.3 Identifying Architectural Patterns Applicable to the User Interface Design -- 6.3.4 Creating Categories of Actions -- 6.3.5 Dividing Actions into Screens -- 6.3.6 Prototyping the Interface -- 6.3.7 Testing the Interface -- 6.4 Examples -- 6.4.1 Focus on Module Assignments and Design Progress -- 6.4.2 Focus on the Number of Use Cases per Module -- 6.4.3 Focus on Module Implementation Overview -- 6.4.4 Focus on Customized Best Practice for GUI Design -- 6.5 Acronyms -- 6.6 Glossary -- 6.7 References -- 6.8 Exercises -- 7. Construction. 327 $a7.1 Introduction -- 7.2 Best Practices for Code Construction -- 7.2.1 Applying coding standards throughout development -- 7.2.2 Applying the test-first approach at the service and module implementation level -- 7.2.3 Implementing service contracts and/or module interfaces before their internal functionality -- 7.2.4 Applying Test Driven Development for algorithmically complex and critical code units -- 7.2.5 Conducting white box unit testing after implementing each unit and before checking the code to the source control system -- 7.2.6 Verifying code consistency with the requirements and design -- 7.3 Policy for Use of the Code Source Control System -- 7.3.1 Each developer should have a local copy (sandbox) of files related to her current work -- 7.3.2 Each team should have a sandbox with copies of all files needed to build each application -- 7.3.3 Parallel development practices should be well defined and understood by participating developers -- 7.3.4 Each developer should check out only code that she is actively modifying -- 7.3.5 Each developer should check in to source control only code that complies with the required coding standards and passes the designated quality checks -- 7.3.6 Each developer should clean the sandbox and re-shadow relevant files after major changes -- 7.3.7 The entire team should store code for different software versions in physically independent locations of the source control systems -- 7.3.8 The entire team should use versioning features only for small variations within one software version -- 7.3.9 Measurements Related to Source Control -- 7.3.10 Tracking of Source Control Data -- 7.4 Policy for Use of Automated Build -- 7.4.1 Creating a special build account -- 7.4.2 Cleaning the build area before each build -- 7.4.3 Shadowing or cloning the source code to the build directory -- 7.4.4 Building the application at regularly scheduled intervals after cleaning the build directory and shadowing or cloning the source code. 327 $a7.4.5 Completely automating the build process -- 7.4.6 Creating hierarchies for Makefiles and/or other build files -- 7.4.7 Parameterizing scripts and build files -- 7.4.8 For n-tier applications, establishing and creating a build on a staging area as well as a production area -- 7.4.9 Fully integrating automated builds with the source control system -- 7.4.10 Integrating testing into the automated build process -- 7.4.11 Measurements Related to Automated Builds -- 7.4.12 Tracking of Data Related to Automated Builds -- 7.5 Examples -- 7.5.1 Focus on a Customized Coding Standard Policy -- 7.5.2 Focus on Features/Tests Reports -- 7.6 Acronyms -- 7.7 Glossary -- 7.8 References -- 7.9 Exercises -- 8. Testing and Defect Prevention -- 8.1 Introduction -- 8.2 Best Practices for Testing and Code Review -- 8.2.1 Conducting White Box Unit Testing: Bottom-Up Approach -- 8.2.2 Conducting Black Box Testing and Verifying the Convergence of Top Down and Bottom Up Tests -- 8.2.3 Conducting Code Reviews as a Testing Activity -- 8.2.4 Conducting Integration Testing -- 8.2.5 Conducting System Testing -- 8.2.6 Conducting Regression Testing -- 8.2.7 Conducting Acceptance Testing -- 8.3 Defect Analysis and Prevention -- 8.4 Policy for Use of Problem Tracking System -- 8.4.1 During development, problem tracking systems should be used to store only severe defects, feature requests and developer ideas -- 8.4.2 After a code freeze, the problem tracking system should be used to record all defect reports and all feature requests -- 8.4.3 During release planning, recorded feature requests should be prioritized and their implementation scheduled -- 8.4.4 Measurements of Data Related to the Problem Tracking System -- 8.4.5 Tracking of Data Related to Problem Tracking System -- 8.5 Policy for Use of Regression Testing System -- 8.5.1 Configuring the regression system so that it provides detailed result information -- 8.5.2 Executing regression tests automatically after each build. 327 $a8.5.3 Reviewing regression test results at the beginning of each work day and updating the test suite as needed -- 8.5.4 Using regression results to assess the deployment readiness of the system -- 8.5.5 Measurements Related to the Regression Testing System -- 8.5.6 Tracking of Data Related to the Regression Testing System -- 8.6 Examples -- 8.6.1 Focus on Defect Tracking Reports -- 8.6.2 Focus on Test Type Reports -- 8.6.3 Example of a Root Cause Analysis of a Design and Testing Defect -- 8.7 Acronyms -- 8.8 Glossary -- 8.9 References -- 8.10 Exercises -- 9. Trend Analysis and Deployment -- 9.1 Introduction -- 9.2 Trends in Process Control -- 9.2.1 Process Variations -- 9.2.2 Process Stabilization -- 9.2.3 Process Capability -- 9.3 Trends in Project Progress -- 9.3.1 Analyzing Features/Requirements Implementation Status -- 9.3.2 Analyzing Source Code Growth -- 9.3.3 Analyzing Test Results -- 9.3.4 Analyzing Defects -- 9.3.5 Analyzing Cost and Schedule -- 9.4 Best Practices for Deployment and Transition -- 9.4.1 Deployment to a Staging System -- 9.4.2 Automation of the Deployment Process -- 9.4.3 Assessing Release Readiness -- 9.4.4 Release: Deployment to the Production System -- 9.4.5 Non-intrusive Monitoring -- 9.5 Acronyms -- 9.6 Glossary -- 9.7 References -- 9.8 Exercises -- 10. Managing External Factors -- 10.1 Introduction -- 10.2 Best Practices for Managing Outsourced Projects -- 10.2.1 Establishing A Software Development Outsource Process -- 10.2.2 Phase 0: Decision to Outsource -- 10.2.3 Phase 1: Planning -- 10.2.4 Phase 2: Implementation -- 10.2.5 Phase 3: Termination -- 10.3 Best Practices for Facilitating IT Regulatory Compliance -- 10.3.1 Section 508 of the US Rehabilitation Act -- 10.3.2 Sarbanes-Oxley Act of 2002 -- 10.4 Best Practices for Implementation of CMMI -- 10.4.1 Capability and Maturity Model Integration (CMMI) -- 10.4.2 Staged Representation -- 10.4.3 Putting Staged Representation Based Improvement into Practice Using ASDP. 327 $a10.4.4 Putting Continuous Representation Based Improvement into Practice Using ASDP -- 10.5 Acronyms -- 10.6 Glossary -- 10.7 References -- 10.8 Exercises -- 11. Case Studies: Automation as an Agent of Change -- 11.1 Case Study I: Implementing Java Coding Standards in a Financial Application -- 11.1.1 Company Profile -- 11.1.2 Problems -- 11.1.3 Solution -- 11.1.4 Data Collected -- 11.1.5 The Bottom Line Results - Facilitating Change -- 11.1.6 Acronyms -- 11.1.7 Glossary -- 11.1.8 References for Case Study I -- 11.2 Case Study II: Implementing C/C++ Coding Standards in an Embedded Application -- 11.2.1 Introduction -- 11.2.2 C/C++ Coding Standards -- 11.2.3 Considerations on Choosing a Coding Standards Checker -- 11.2.4 Experiences Using the Checker -- 11.2.5 Lessons Learned -- 11.2.6 Conclusion -- 11.2.7 References for Case Study II -- Appendix A: A Brief Survey of Modern Software Development Process Models -- A.1 Introduction -- A.2 Rapid Application Development (RAD) and Rapid Prototyping -- A.3 Incremental Development -- A.4 Spiral Model -- A.5 Object Oriented Unified Process -- A.6 Extreme and Agile Programming -- A.7 References -- Appendix B: Mars Polar Lander (MPL), Loss and Lessons -- B.1 No Definite Root Cause -- B.2 No Mission Data -- B.3 Root Cause Revisited -- Appendix C: Service-Oriented Architecture: Example of an Implementation with ADP Best Practices -- C.1 Introduction -- C.2 Web Service Creation: Initial Planning and Requirements -- C.2.1 Functional Requirements -- C.2.2 Non-Functional Requirements -- C.3 Web Service Creation: Extended Planning and Design -- C.3.1 Initial Architecture -- C.3.2 Extended Infrastructure -- C.3.3 Design -- C.4 Web Service Creation: Construction and Testing Stage 1 : Module Implementation -- C.4.1 Applying Coding Standards -- C.4.2 Implementing Interfaces and Applying a Test-first Approach for Modules and Sub-modules -- C.4.3 Generating White Box Junit Tests -- C.4.4 Gradually Implementing the Sub-module until all Junit Tests Pass and Converge with the Original Black Box Tests. 327 $aC.4.5 Checking Verified Tests into the Source Control System and Running Nightly Regression Tests -- C.5 Web Service Creation: Construction and Testing Stage 2: The WSDL Document Implementation -- C.5.1 Creating and Deploying the WSDL Document on the Staging Server as Part of the Nightly Build Process -- C.5.2 Avoiding Inline Schemas when XML Validation Is Required -- C.5.3 Avoiding Cyclical Referencing, when Using Inline Schemas -- C.5.4 Verifying WSDL document for XML Validity -- C.5.5 Avoiding "Encoded" Coding Style by Checking Interoperability -- C.5.6 Creating Regression Tests for the WSDL documents and Schemas to Detect Undesired Changes -- C.6 Web Service Creation: Server Deployment -- C.6.1 Deploying the Web Service to a Staging Server as Part of the Nightly Build Process -- C.6.2 Executing Web Service Tests that Verify the Functionality of the Web Service -- C.6.3 Creating "Scenario-Based" Tests and Incorporating them Into the Nightly Test Process -- C.6.4 Database Testing -- C.7 Web Service Creation: Client Deployment -- C.7.1 Implementing the Client According to the WSDL Document Specification -- C.7.2 Using Server Stubs to Test Client functionality - Deploying the Server Stub as Part of the Nightly Deployment Process -- C.7.3 Adding Client Tests into the Nightly Test Process -- C.8 Web Service Creation: Verifying Security -- C.8.1 Determining the Desired Level of Security -- C.8.2 Deploying Security Enabled Web Service on Additional Port of the Staging Server -- C.8.3 Leveraging Existing Tests: Modifying Them to Test for Security and Incorporating Them into the Nightly Test Process -- C.9 Web Service Creation: Verifying Performance through Continuous Performance/Load Testing -- C.9.1 Starting Load Testing As Early As Possible and Incorporating it into the Nightly Test Process -- C.9.2 Using Results of Load Tests to Determine Final Deployment. Configuration -- Appendix D: AJAX Best Practice: Continuous Testing -- D.1 Why AJAX? -- D.2 AJAX Development and Testing Challenges. 327 $aD.3 Continuous Testing -- Appendix E: Software Engineering Tools -- Glossary -- Index. 330 $aImprove Productivity by Integrating Automation and Defect Prevention into Your Software Development ProcessThis book presents an approach to software management based on a new methodology called Automated Defect Prevention (ADP). The authors describe how to establish an infrastructure that functions as a software "production line" that automates repetitive tasks, organizes project activities, tracks project status, seamlessly collects project data, and sustains and facilitates the improvement of human-defined processes. Well-grounded in software engineering research and in industry best practices, this book helps organizations gain dramatic improvement in both product quality and operational effectiveness.Ideal for industry professionals and project managers, as well as upper-level undergraduates and graduate-level students in software engineering, Automated Defect Prevention is complete with figures that illustrate how to structure projects and contains real-world examples, developers' testimonies, and tips on how to implement defect prevention strategies across a project group. 606 $aSoftware failures$xPrevention$xData processing 606 $aSoftware maintenance$xData processing 606 $aDebugging in computer science$xAutomatic control 606 $aComputer programs$xTesting$xData processing 606 $aComputer programs$xCorrectness 615 0$aSoftware failures$xPrevention$xData processing. 615 0$aSoftware maintenance$xData processing. 615 0$aDebugging in computer science$xAutomatic control. 615 0$aComputer programs$xTesting$xData processing. 615 0$aComputer programs$xCorrectness. 676 $a005 700 $aHuizinga$b Dorota$01688676 701 $aKolawa$b Adam$01688677 801 0$bCaBNVSL 801 1$bCaBNVSL 801 2$bCaBNVSL 906 $aBOOK 912 $a9910829909703321 996 $aAutomated defect prevention$94063132 997 $aUNINA LEADER 01476nas 2200481- 450 001 996523369503316 005 20240201213018.0 011 $a2476-3357 035 $a(OCoLC)993529357 035 $a(CKB)4340000000037347 035 $a(CONSER)--2023242543 035 $a(EXLCZ)994340000000037347 100 $a20170613a20119999 --- - 101 0 $aper 135 $aur|n||||||||| 181 $ctxt$2rdacontent 182 $cc$2rdamedia 183 $acr$2rdacarrier 200 00$aBarn?mah?r?z?-i faz??y? 210 1$aI?fah?n, ?r?n :$cD?nishg?h-i I?fah?n,$d[2011]- 215 $a1 online resource $cillustrations 311 $a2228-7485 517 1 $aSpatial planning 517 1 $aMajallah-i barn?mah?r?z?-i faz??y? 517 1 $aMajallah-i ?ilm?-i barn?mah?r?z?-i faz??y? 606 $aCity planning$zIran$vPeriodicals 606 $aUrbanization$zIran$vPeriodicals 606 $aUrbanisation$vPériodiques 606 $aCity planning$2fast$3(OCoLC)fst00862177 606 $aUrbanization$2fast$3(OCoLC)fst01162722 608 $aPeriodicals.$2lcgft 608 $aPeriodicals.$2fast 615 0$aCity planning 615 0$aUrbanization 615 6$aUrbanisation 615 7$aCity planning. 615 7$aUrbanization. 676 $a307.1/2 712 02$aD?nishg?h-i I?fah?n, 906 $aJOURNAL 912 $a996523369503316 996 $aBarn?mah?r?z?-i faz??y?$93562087 997 $aUNISA LEADER 03831oam 2200661zu 450 001 9910131939403321 005 20210807004752.0 010 $a2-8218-2651-6 010 $a2-8218-1536-0 024 7 $a10.4000/books.ifea.592 035 $a(CKB)3460000000122337 035 $a(SSID)ssj0001541348 035 $a(PQKBManifestationID)11852825 035 $a(PQKBTitleCode)TC0001541348 035 $a(PQKBWorkID)11534931 035 $a(PQKB)10287199 035 $a(WaSeSS)IndRDA00044277 035 $a(FrMaCLE)OB-ifea-592 035 $a(oapen)https://directory.doabooks.org/handle/20.500.12854/44664 035 $a(PPN)182836002 035 $a(oapen)doab44664 035 $a(EXLCZ)993460000000122337 100 $a20160829d2006 uy 101 0 $aspa 135 $aur||||||||||| 181 $ctxt 182 $cc 183 $acr 200 10$aDel trono a la guillotina : el impacto de la Revolución Francesa en el Perú (1789-1808 210 $cInstitut français d?études andines$d2006 210 31$a[Place of publication not identified]$cInstitut français d'études andines Embajada de Francia en el Perú Fondo Editorial de la Pontificia$d2006 215 $a1 online resource (291 pages) 225 1 $aTravaux de l'IFE?A 300 $aBibliographic Level Mode of Issuance: Monograph 311 08$a9972-623-42-4 320 $aIncludes bibliographical references. 330 $a«Es un descubrimiento apasionante al que nos invita Claudia Rosas Lauro a lo largo de las páginas de esta tesis, convertida en un libro sobre ?El impacto de la Revolución Francesa en el Perú?. Felicitamos esta merecida entrega editorial con la que se beneficiarán los investigadores internacionales que, actualmente, estudian las repercusiones de este acontecimiento de alcance mundial». Con estas palabras inicia Michel Vovelle ?el más grande historiador de la Revolución Francesa? el prólogo de este libro, que nos invita a reflexionar sobre la influencia de este importante evento histórico en la mentalidad de la sociedad colonial peruana. El estudio explora las múltiples vías de difusión y circulación de las noticias sobre el hecho revolucionario, que van desde la prensa escrita y los pasquines hasta las conversaciones en espacios públicos y los rumores; cómo se plasmó esta información en imágenes, representaciones y discursos. En ellos cobran vida los personajes del drama revolucionario y sus banderas políticas, con las secuelas del Terror y la guerra, al lado del ataque al trono y al altar; que llevaron finalmente al despliegue de actitudes que oscilaban entre la tolerancia y la represión, orquestadas por una política contrarrevolucionaria inspirada entre otros factores por el miedo a la revolución en una sociedad poblada de indios, negros y casta. La obra constituye no solo un aporte al estudio del impacto de la Revolucón Francesa en el Perú, sino también, contribuye a la comprensión de la sociedad de fines del periodo colonial. 410 0$aTravaux de l'Institut franc?ais d'e?tudes andines. 606 $aRegions & Countries - Americas$2HILCC 606 $aHistory & Archaeology$2HILCC 606 $aLatin America$2HILCC 607 $aPeru$xHistory$y1548-1820 607 $aFrance$xHistory$yRevolution, 1789-1799$xInfluence 610 $ahistoriographie 610 $acivilisation 610 $aFrance 610 $aPérou 610 $aRévolution 615 7$aRegions & Countries - Americas 615 7$aHistory & Archaeology 615 7$aLatin America 676 $a985/.03 700 $aRosas Lauro$b Claudia$0884375 801 0$bPQKB 906 $aBOOK 912 $a9910131939403321 996 $aDel trono a la guillotina : el impacto de la Revolución Francesa en el Perú (1789-1808$91974855 997 $aUNINA LEADER 02452nam 22004695 450 001 9910676686603321 005 20250628110034.0 010 $a9783476058867 024 7 $a10.1007/978-3-476-05886-7 035 $a(MiAaPQ)EBC7208146 035 $a(CKB)26272063700041 035 $a(DE-He213)978-3-476-05886-7 035 $a(ODN)ODN0010068276 035 $a(oapen)doab98520 035 $a(EXLCZ)9926272063700041 100 $a20230301d2022 u| 0 101 0 $ager 135 $aurnn|008mamaa 181 $ctxt$2rdacontent 182 $cc$2rdamedia 183 $acr$2rdacarrier 200 10$aDigitale Literaturwissenschaft $eDFG-Symposion 2017 /$fherausgegeben von Fotis Jannidis 205 $a1st ed. 2022. 210 $d2023 210 1$aStuttgart :$cJ.B. Metzler :$cImprint: J.B. Metzler,$d2022. 215 $a1 online resource (XIII, 848 S. 104 Abb., 84 Abb. in Farbe.) 225 1 $aGermanistische Symposien, Berichtsbände,$x2945-9494 311 08$a9783476058850 327 $aEinführung -- Sektion I. Literatur und Literaturwissenschaft unter digitalen Bedingungen -- Sektion II. Digitale Edition und Annotation -- Sektion III. Textanalyse -- Sektion IV. Schnittstellen der digitalen Literaturwissenschaft. 330 $aDieser Open Access-Band dokumentiert die Beiträge des DFG-Symposions 2017. Die Tagung 2017 zum Thema ?Digitale Literaturwissenschaft? behandelte in vier Sektionen sowohl die Veränderungen im Fach der germanistischen Literaturwissenschaft als auch der Literatur selbst. Insbesondere in der digitalen Edition und Annotation literarischer Texte sowie bei der Untersuchung größerer Textsammlungen sind in den letzten Jahren bedeutende Fortschritte erzielt worden. Durch diese Erweiterungen des literaturwissenschaftlichen Methodeninventars haben sich auch die Anforderungen an forschungsrelevante Institutionen, wie etwa Archive und Bibliotheken, und die Beziehungen zu ihnen einschneidend verändert. 410 0$aGermanistische Symposien, Berichtsbände,$x2945-9494 606 $aDigital humanities 606 $aDigital Humanities 615 0$aDigital humanities. 615 14$aDigital Humanities. 676 $a025.060013 686 $aLAN025000$2bisacsh 700 $aJannidis$b Fotis$0176514 702 $aJannidis$b Fotis$4edt$4http://id.loc.gov/vocabulary/relators/edt 912 $a9910676686603321 996 $aDigitale Literaturwissenschaft$94399937 997 $aUNINA