Index. B Backup requirements, 89 Black-box testing, 188 Booch Method, 101 Boundary testing, 190 Bridge, 132

Transcription

1 Index A Abstract factory, Acceptance testing, 191 Accidental complexity, 125 Active and passive environments, 159 Activity diagrams, Adapter, 130 Afferent coupling, 124 Agile policies, principles, Agile vs. Scrum, 38 Android, 9 AOP. See Aspect-oriented programming (AOP) Apache Cordova, 8 Application architecture, 100 Application development clean test environment, 153 ClickOnce vs. Windows Installer, continuous delivery/integration, 154 Visual Studio Installer projects, 153 Architecture, 79 Arrange act assert, , 181 Aspect-oriented programming (AOP), 81 ASP.NET, 18 B Backup requirements, 89 Black-box testing, 188 Booch Method, 101 Boundary testing, 190 Bridge, 132 C Circuit breaker, Class diagrams, Code Clone, 4 Code coverage, Code reviewing adding comments, 71 architecture, 73 changes details, 69, 70 framework usage, 73 object-oriented design, 74 pattern usage, 74 propose solutions, 75 race conditions, 74 static code analysis, 73 style, 73 Team Explorer, 67 technical debt, 74 thread safety, 73 View Shelveset link, 69 CodeLens, 13 16, Cohesion, 124 Command patterns, 133 Command-Query Responsibility Segregation (CQRS) domain storage and read model, 87 logical design, 86 message-orientation, 88 workflow, 88 Command-Query Separation (CQS), 86 Community edition, 21 Component diagrams, Composable systems, 159 Composite reuse principle, Composite root, 128 Copy-modify-merge model, 52 Coupling, 124 CQ S. See Command-Query Separation (CQS) Cyclomatic complexity, 124 D Data-centric model, 139 Debugging, 7 8 Decorator, D efined processes, 29 Dependency inversion principle, Peter Ritchie 2016 P. Ritchie, Practical Microsoft Visual Studio 2015, DOI /

2 Deployment diagrams, Deployment pipeline, 167 Deployments, 166 Design, 80 Diagramming embedded within document, 113 embedded within web page, flowcharts, 101 high-level architecture diagrams, low-level design, testing, 102 types architectural, 103 behavioral, 103 directed graph, 103 working software, 102 Directed Graph bidirectional edges, 104 comment, 106 group, 105 node, 104 self reference, 104 Don t repeat yourself (DRY), 149 E Efferent coupling, 124 Enterprise architecture, Enterprise development build-per-environment, deployment strategies, 154 development environment, 156 experimental environment, 156 integration testing, 157 local environment, 156 Enterprise edition, 22 Environment flow, 165 Environments creation, Essential complexity, 125 Extensibility requirements, 89 F Façade, 135 Factory method, Flowcharts, 101 Future-proofing, Fuzz testing, 188 G Git, 9 11 clone, 55 code review process, 60 commit, 57 features, fork, 55 higher-level upstream configuration, 61 master, 58 origin, 58 process flow, pull, 58 push, 58 remote, 55 repo, 55 staging area, upstream, 55 working directory, 56 GitHub, H High Availability, cluster active-active clusters, 161 active-passive model, 162 N+1 model, 162 N+M model, 162 node failure, 163 N-to-1 model, 162 N-to-N model, 163 I, J, K Idioms, 123 Integrated development environment (IDE), 1 4, 7, 20, 24, 25 Integration testing, 157, IntelliSense, 1 IntelliTrace, 2 Interface-based programming, 146 Interface segregation principle, Inversion of control (IoC), 116, 132, 135, 145, 147 IoC container, 132 ios, 9 Iterative development, 30 Iterator, 136 L Layer diagrams, Layer pattern, Liskov substitution principle (LSP), 145 Locking binary files, 52 Lock-modify-unlock model, 51 Loosely-coupled design, 191 M Mediator, Memento, Menu items, 18

3 Message queue, 85 Metrics accidental complexity, 125 code coverage, cohesion, 124 coupling, 124 cyclomatic complexity, 124 essential complexity, 125 Microservices, 164 Microsoft Fakes, Migration paths, Mocking frameworks, 182 Model-view-controller (MVC), Model-view-presenter (MVP), Monitoring, 160 Monolithic application, N Negative testing, NET 4.6, 17.NET Core, 17 O Object-oriented design, 74 OmniSharp, 24 Open/closed principle (OCP), 145 Open source software (OSS), 62 Operability requirements, 89 P Patterns abstract factory, adapter, 130 bridge, 132 circuit breaker, command, 133 composite root, 128 constructor injection, decorator, dependency injection, 127 description, 126 empirical process, 126 façade, 135 factory method, IoC container, 132 iterator, 136 layers, mediator, memento, model classes, 140 data-centric, 139 embedded, 141 MVC, 139 MVP, 139 shared, 140 property injection, 128 retry, service locator, 143 singleton, 143 software languages, 126 static factory, view, 142 Patterns and Practices accessibility, 81 AOP, auditability, 81 availability, 84 CQS, 86 decorator pattern, message orientation, 85 scalable, 84 Performance requirements, 90 Postel s Law, 150 Principle of least astonishment, 150 Principle of least knowledge, Principle of least privilege, 95 Production, 158, 166 Professional edition, 22 Project management charter, 28 project sponsor, 29 triangle, vision, 28 Protected information, 95 Q Quality attributes availability, 160 performance, 161 reliability/robustness/resiliency, 161 scalability, 161 R Rational unified process (RUP), 101 Recoverability requirements, 90 Reliability requirements, Revisioncontrol. See Version control Robustness requirements, 92 S Scrum business owner, 35 daily scrum, 36 process, 34 product owner,

4 Scrum (cont.) sprint, 35 stakeholders, 35 Security, Sequence diagrams, Service locator, 143 Single responsibility principle (SRP), 144 Singleton, 143 Smoke testing, 167 Software delivery defined process, 29 domain experts, 31 empirical process, 29 epic, 37 estimates, 35 iterative development, 30 SDLC, 30 sprint retro, 38 sprint review, 37 Solution architecture, Sprint, 35 Sprint retro, 38 Sprint review, 37 Staging, 157 Static factory, Systems Development Lifecycle (SDLC), 30 T Team Foundation Version Control (TFVC), 51 features, 65 local workspace, 62, 64 renaming solution items, 64 solution-level files, 63 Test Driven Development (TDD), Testing, 4, 102 arrange act assert, given, when, then, , 182 integration, Microsoft Fakes, Moq, 189 acceptance testing, 191 black-box testing, 188 boundary testing, 190 fuzz testing, 188 loosely-coupled design, 191 negative testing, record, replay, TDD, white-box testing, products, 169 record, replay, unittesting (see (Unit testing) ) Test naming, , 181 Th ird-party tools Git, 9 11 GitHub, Xamarin, 9 Th read safety, 73 Traceability, 92 Transient diagrams, U UML diagrams activity diagrams, class diagrams, component diagrams, sequence diagrams, use case diagrams, Unified Modeling Language (UML), 101 Unit testing definition, 169 test doubles assert, Mock File System, 171 CSV parser class, 170 dummy, 174 fake, 174 IFileSystem interface, 170 mocking, 170 spy, 172 SpyStream implementation, Stream.Read, 172 stub, 172 Unity, 13 Universal Windows, 9 Use case diagrams, User acceptance testing, 158 User stories, 37 V Version control branching, 52, 53 branching strategy, 54 broken code, 75 commented-out Code, 75 copy-modify-merge model, 52 development isolation, 53 feature avoidance, 76 feature isolation, 53 hotfix isolation, 53 lock-modify-unlock model, 51 mainline, 52 trunk, 52 unit test, 76 version branches avoidance, 76 Visual Studio 2013, 2, 3, 17, 25,

5 Visual Studio 2015 editions community, 3, 21 comparison, debugging, 7 8 enterprise, 3 4, 22 installer, 5 6 live code analysis, 7 professional, 3, 22 resolution, 18 test professional, 4 Visual Studio 2013, 2 Visual Studio Code, 23 Visual Studio Express, 2 Visual Studio installer, 5 Visual Studio Team Foundation Server 2015 Express, 2 Visual Studio Team Services, 24 W Waterfall processes, 47, 49 White-box testing, Work items, Work items management CodeLens, epic creation, feature form creation, 43 linked work item form, 42 product backlog item, 44 Team Explorer, work item Settings, 44 X, Y, Z X amar in, 9 199