Software Engineering Books

Book Synopsis Ken Schwaber is president of Advanced Development Methods (ADM), a company dedicated to improving the software development practice. He is an experienced software developer, product manager, and industry consultant. Schwaber initiated the process management product revolution of the early 1990's and also worked with Jeff Sutherland to formulate the initial versions of the Scrum development process. Mike Beedle, an experienced software development practitioner, is the founder and CEO of e-Architects, Inc., a management and technical consulting company that helps its clients develop software in record time. Beedle has contributed to thousands of software projects for the last 20 years, and has used, recommended, and guided others to implement Scrum since 1995. Trade Review"Agile development methods are key to the future of flexible software systems. Scrum is one of the vanguards of the new way to buy and manage software development when business conditions are changing. This book distills both the theory and practice and is essential reading for anyone who needs to cope with software in a volatile world." — Martin Fowler, industry consultant and CTO, ThoughtWorks "Most executives today are not happy with their organization's ability to deliver systems at reasonable cost and timeframes. Yet, if pressed, they will admit that they don't think their software developers are not competent. If it's not the engineers, then what is it that prevents fast development at reasonable cost? Scrum gives the answer to the question and the solution to the problem. — Alan Buffington, industry consultant, former Present, Fidelity Systems Company Table of Contents 1. Introduction. 2. Great Ready for Scrum! 3. Scrum Practices. 4. Applying Scrum. 5. Why Scrum? 6. Why Does Scrum Work? 7. Advanced Scrum Applications. 8. Scrum and the Organization. 9. Scrum Values.

Read more less

Book Synopsis

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

Book SynopsisThe new edition of Software Engineering presents a step-by-step methodology that integrates Modeling and Design, UML, Patterns, Test-Driven Development, Quality Assurance, Configuration Management, and Agile Principles throughout the life cycle. The overall approach is casual and easy to follow, with many practical examples that show the theory at work. The author uses his experiences as well as real-world stories to help the reader understand software design principles, patterns, and other software engineering concepts. The book also provides stimulating exercises that go far beyond the type of question that can be answered by simply copying portions of the text.The new edition of Software Engineering is now available for the first time in McGraw Hill Connect! Connect for this course features the MHeBook, Writing Tool, Proctorio, and the Connect authoring tool that offers the ability to create your own questions.Table of ContentsPart 1: Introduction and System EngineeringChapter 1: IntroductionChapter 2: Software Process and MethodologyChapter 3: System EngineeringPart 2: Analysis and Architectural DesignChapter 4: Software Requirements ElicitationChapter 5: Domain ModelingChapter 6: Architectural DesignPart 3: Modeling and Design of InteractiveChapter 7: Deriving Use Cases from RequirementsChapter 8: Actor-System Interaction ModelingChapter 9: Object Interaction ModelingChapter 10: Applying Responsibility-Assignment PatternsChapter 11: Deriving a Design Class DiagramChapter 12: User Interface DesignPart 4: Modeling and Design of Other Types of SystemsChapter 13: Object State Modeling for Event-Driven SystemsChapter 14: Activity Modeling for TransformationalChapter 15: Modeling and Design of Rule-Based SystemsPart 5: Applying Situation-Specific PatternsChapter 16: Applying Patterns to Design a State Diagram EditorChapter 17: Applying Patterns to Design a Persistence FrameworkPart 6: Implementation and Quality AssuranceChapter 18: Implementation ConsiderationsChapter 19: Software Quality AssuranceChapter 20: Software TestingPart 7: Maintenance and Configuration ManagementChapter 21: Software MaintenanceChapter 22: Software Configuration ManagementPart 8: Project Management and Software SoftwareChapter 23: Software Project ManagementChapter 24: Software Security

Read more less

Book SynopsisIf you need this information then Pro ASP.NET MVC 4 is your perfect book.ASP.NET MVC 4 and the Web API: Building a REST Service from Start to Finish helps you build cutting-edge REST services using ASP.NET MVC 4 and the Web API in more depth and detail than any other resource.Table of Contents1. ASP.NET MVC as a Service Framework 2. What is RESTful? 3. Designing Our Sample REST API 4. Building the Environment and Creating the Source Tree 5. Controllers, Dependencies, and Managing the Database Unit of Work 6. Securing the Service 7. Putting It All Together

Read more less

Book SynopsisApply the industrial engineering science of invention and assembly to how software is described, planned, and built, allowing you to be free to flex your practices according to your needs, putting principle over habit and rules.Reading about Agile practices is like reading diet advice.Table of Contents· Introduction · Prologue · Section 1: Agile Codex Theory Chapter 1: The Codex Principles Application (samples of principles in action) Chapter 2: The Agile Principles Application (samples of principles in action) Chapter 3: Putting them Together Education to Agreement (a specific type of collaboration) Low Overhead Detailed Auditing Quick and Safe Deliveries Many Quality Gates The Importance of Dependencies Chapter 4: From Invention to Assembly Line Historical development of the assembly line Evolving from hardware and things to software and information · Section 2: Agile Codex Practices Chapter 5: Team Functions Chapter 6: Software Development LifeCycle SDLC in Industry Phases Constructing the Codex The Science of Risk Mitigation Flexibility How SDLC Length Affects Practices Chapter 7: Building Blocks Planned Release Epic User Story Bug Chapter 8: Workflow Planning Execution Release Chapter 9: Example · Conclusion

Read more less

Book Synopsis1: Your First Spring Application.- 2: Working With Classes and Dependencies.- 3: Applying Different Configurations.- 4: Using Bean Scopes.- 5: Using Resource Files.- 6: Adding Simple Persistence to Your Spring Application.- 7: Letting Spring Build Your Data Access Objects.- 8: Showing Your Spring Application on the Web.- 9: Integrating Your Spring Application with External Systems.- 10: Exposing a REST API.- 11: Sending E-mails from Within Spring.- 12: Using Dynamic Languages.- 13: Where Do You Go From Here?.Table of Contents1. Your First Spring Application2. Working with Classes and Dependencies3. Applying Different Configurations4. Using Bean Scopes5. Working with Collections and Custom Types6. Using Resource Files7. Testing Your Spring Application8. Give Advice to Your Spring Application9. Adding Persistence to Your Spring Application with Spring Data JPA10. Showing Your Spring Application on the Web with Spring MVC and WebFlow11. Integrating Your Spring Application with External Systems: Spring Integration12. Exposing a REST API using Spring REST13. Adding E-mail and Scheduling Tasks14. Using Dynamic Languages15. Spring Data Within Your Spring Application16. Messaging with Your Spring Application: Spring AMQP and Kafka17. Be Social and Go Mobile18. Spring and Groovy19. Spring Boot, Simplifying Everything20. Using Spring Native and Reactive SpringA. Tools: IntelliJ IDEA and Eclipse Java IDE

Read more less

Book Synopsis Making fast and accurate technology decisions is critical to staying relevant to your customers. And technology needs to add value back to your organization quicker than ever. Google Cloud offers IT leaders the answer to today''s technology challenges. However, to realize its benefits you must navigate your journey without hitting common pitfalls that lead to stalled and unsuccessful cloud adoption. This book distills the lessons learned from guiding and working with hundreds of organizations on their journey to the cloud. Its goal is to give aspiring and current IT leaders the knowledge required to be an infrastructure leader. That is the term author Jeremy Lloyd uses for the person who can lead your organization''s Google Cloud adoption strategy. Of course, cloud adoption isn''t a solo endeavor. Jeremy covers the different generations of IT leaders, the team structure, and the skills required for a successful migration to Google Cloud. This book also covers why yoTable of ContentsChapter 1: Introduction Chapter Goal: Introduce a concept that there are essentially four types of infrastructure leaders as I know them. Let them build a relationship with one of the four which provides them with a lens upon which to view the current state and the path to progress forwards with GCP. Then inform them of the role that an infrastructure leader plays in a GCP adoption and migration strategy. Lay out the challenges they will face adopting GCP/Cloud. Provide guidance on a fundamental shift from a cost centre to a profit centre.No of pages - 12Sub-Topics1. What does an Infrastructure Leader do? Or Who is an Infrastructure Leader?2. Type of Infrastructure Leaders3. Challenges4. Becoming a profit centreChapter 2: About Google & Google CloudChapter Goal: Take the reader on a short journey of the history of Google and bring out the narrative around their values and principles and empower them to lead innovation across every sector they touch. Then bring out the core value proposition of Google Cloud itself, underpinned by evidence to backupNo of pages - 28Sub - Topics1. Google short history2. Introducing Google Cloud Platform3. Google Cloud Platform core components4. Why use Google Cloud PlatformChapter 3: Future of ITChapter Goal: Orient the reader into understanding that their current state has to change. Back up the messaging with trends and data points they can’t refute.No of pages - 3Sub - TopicsChapter 4: The Four Stages Of Google Cloud Platform AdoptionChapter Goal: Label and define the four states of GCP/Cloud adoption. Let the reader understand how and where any experience they currently have sits. Help them understand the considerations to going with one strategy over the others. No of pages - 7Sub - Topics1. Shadow IT2. Tactical Adoption3. Strategic Adoption4. Organisation TransformationChapter 5: Business CaseChapter Goal: Arm the reader with the information they need to write a rapid or detailed business case to justify adoption and migration to GCP. The aim is to make is simple for them to get the right story that will resonate with their organisation.No of pages - 6Sub - Topics1. Rapid Business Case2. Detailed Business Case3. Integrating with an existing business case templateChapter 6: The Cloud StrategyChapter Goal: Show them the importance of having a well-defined cloud strategy. Then give them almost a blueprint upon which to follow in how to create one.No of pages - 10Sub - Topics1. Version 2. Executive Summary3. Current State4. Financial Models5. Alignment to business strategy6. Guiding Principles7. Security8. Compliance9. Risk Management10. Governance11. Ways of Working12. Objectives and Key Results (OKRs)13. Implementation PlanChapter 7: Cloud Operating ModelChapter Goal: With a defined cloud strategy you need the next layer which is to define what your cloud operating model is. This chapter aims to inform what to consider and how their operating model could look and how to ensure it can evolve as the organisation matures with GCP.No of pages - 6Sub - TopicsChapter 8: Migration StrategiesChapter Goal: Inform the reader of the industry used migration approaches and Google Cloud’s take on them. No of pages - 3-5Sub - Topics1. Migration Objectives2. Migration Risk management3. Googlers & Office of the CTO4. Partner Ecosystem5. ActionsChapter 9: Modernisation StrategiesChapter Goal: Inform the reader about modernisation strategies, Google’s tools and some simple methods to help them quickly decide what to modernise.No of pages - 10Sub - Topics1. Modernisation guardrails2. Modernisation roadmap3. Mainframe Modernisation4. Migration Decision Tree5. ActionsChapter 10: Organisational ReadinessChapter Goal: Provide the reader with the considerations across key areas that will help them be prepared for cloud adoption/migration.No of pages - 34Sub - Topics1. Paving the roads for cultural change2. Google Cloud Adoption Framework3. Managing The Hype-cycle4. Skillset5. Cloud Adoption Teams (CMO, CCoE etc)6. Building a Cloud Center of Excellence 7. Security Readiness8. Governance Readiness9. Operations ReadinessChapter 11: Migration & Modernisation Team StructuresChapter Goal: Get the reader to understand the people, skills and ways of working that GCP migration and modernisation requiresNo of pages - 2Sub - TopicsChapter 12: MigrationsChapter Goal: Provide guidance across migration assessment, planning and execution. Inform them what good first mover workloads look like. No of pages - 20-22Sub - Topics1. Introducing The Migration Journey2. Assess3. Plan4. Migrate5. OptimiseChapter 13: Cloud-Native DevelopmentChapter Goal: The infrastructure leader won’t be responsible for cloud-native development but they can/should play a key role in it’s facilitation. It showcases the considerations across new areas that the infrastructure team should be focusing on.No of pages - 20Sub - Topics1. Cloud-Native Advantages2. Containers3. Integrated Development Environment4. Serverless5. BeyondProdChapter 14 : Day 2 OperationsChapter Goal: Introduce the concept of Day 2 Operations to the reader. Then give them guidance around what the infrastructure team should be thinking about across each of the sub-topics, all staying within a day 2 operations context.No of pages - 60Sub - Topics1. Day 2 Cloud Challenges2. Cloud Foundations3. Landing Zones 4. Compute5. Monitoring, Logging And Alerting6. Availability7. Reliability8. Recoverability9. Financial Operations10. Performance11. Security12. Automation13. Governance and Compliance14. Cloud Marketplace15. GCP Managed Services16. Containers17. Data Analytics18. Open Source19. Support20. Day 2 antipatterns21. DevOps/SRE/CREChapter 15: Productivity and CollaborationChapter Goal: Introduce a Google concept of BeyondCorp and how that ties in with a GCP migration strategy. Introduce Google Workspace and benefits of using it.No of pages - 8Sub - Topics1. BeyondCorp2. Google Workspace

Read more less

Book SynopsisThis book takes developers on a journey into the cloud with Docker and Kubernetes. It walks you through the basics of Docker containers, how they are built, run, and published, and how the Kubernetes system allows you to use containers to better manage a cloud native application. Additionally, it walks you through various issues in cloud architecture, and how to design a cloud architecture that will work with your application and your team. The book takes a unique approach, getting you immersed in each subject with tutorials, then building up your technical knowledge, and finally backing up and thinking about more big-picture issues. Part one introduces Docker, building and working with Docker images, and covering best practices for Docker Containers. Part two covers the practicalities of "cloud native" and managing a Kubernetes application, including a full working example. The last part covers the design of cloud and microservice architectures, including the use of enterprise message queues, multi-site configurations and the common values that such architectures follow. This approach accelerates learning and keeps you moving forward without leaving you behind. The appendices also contain a wealth of worthwhile reference material for routine cloud application management. What You Will Learn Understand Docker and containerization Gain insight into what Kubernetes is Master essential cloud architecture design principles Design and implement notes for building cloud architectures Who This Book Is For Primarily developers who are moving to the cloud and want to get a sense of the environment they are getting into, and developers who want to move into a larger role of cloud architecture. Table of ContentsChapter ​1. Introduction - what they should expect from the book.PART 1: DockerChapter 2. Docker Under the Hood - introduction to the history and technology behind Docker. I find that really understanding Docker containers well requires a brief knowledge of their history and implementation.Chapter 3. A Docker Interactive Tutorial - the basics of building and working with Docker imagesChapter 4. Best Practices for Docker Containers - general tips, Debian vs Alpine, etc.PART 2: KubernetesChapter 5. The Cloud Native Philosophy - a general intro to the goals behind “Cloud Native” and KubernetesChapter 6. Getting Started with Kubernetes - showing how to deploy a simple system on Kubernetes with the Kubernetes dashboardChapter 7. Managing Kubernetes with kubectl - an introduction to the kubectl toolChapter 8. The Kubernetes environment - now that the user has some hands-on with Kubernetes, we introduce the components themselvesChapter 9. Basic Kubernetes Management - how to work with YAML filesChapter 10. A Full Kubernetes Cloud Example - full Kubernetes code for a cluster for a Message Board systemChapter 11. Going Further in Kubernetes - a brief introduction to other parts of KubernetesPART 3: Cloud ArchitectureChapter 12. Cloud Architecture Introduction - why architecting mattersChapter 13. Basic Cloud Architectures - basic architectural diagrams for the most common situationsChapter 14. Microservice Architectures - what microservices are, why they are important, and how to build such an architectureChapter 15. Enterprise Message Queues - what message queues are and how they make micro service architectures more flexible and resilientChapter 16. Architecting Data Stores - various database (and other data store) optionsChapter 17. Multi-Site Configurations - introducing terminology and through processes behind multi-site configurationsChapter 18. Architecture Values - a discussion of common themes for cloud architecturesChapter 19. ConclusionAppendices:1. Navigating the Linux Command Shell2. Installing Applications3. Common kubectl commands4. Kubernetes Storage Options5. Kubernetes Pod Scheduling6. Troubleshooting Kubernetes Clusters

Read more less

Book SynopsisDiscover a new way of thinking about business applications in light of the massive industry shift toward cloud computing and reactive programming technologies. This book synthesizes technologies and techniques such as event sourcing, command query responsibility segregation (CQRS), property-based testing, and GraphQL into a cohesive guide for modern business applications that benefit every developer.The book begins with a look at the fundamentals of modern business applications. These fundamentals include business rules and the managing of data over time. The benefits of reactive techniques are explained, including how they are fundamentally aligned with what application developers strive to achieve in their work.Author Peter Royal equips you with sound guidance to follow as you evolve your existing systems, as well as examples of how to build those systems using modern techniques in Spring, Java, and PostgreSQL.Table of ContentsPart I. On Business Applications1. What Is A Business Application?2. The Status Quo (and How It Can To Be)Part II. Design Prerequisites 3. What Is A Reactive System?4. Why Build Business Applications as Reactive Systems?5. What Is A Business Rule?6. Managing TimePart III. Design7. Constraints and Principles8. High-Level Data Flow9. Command Processor10. Command Generator11. Event Materializer12. Testing, Monitoring, and Observability13. Required TechnologiesPart IV. Implementation14. Building with Modern Spring, Java, and PostgreSQL15. Expansion Points and Beyond

Read more less

Book SynopsisBuild products on top of Ethereum's new and expansive technological stack. Writing any good web application requires planning, care, and deft technical skills, but Ethereum's execution model presents its own challenges for engineers wishing to build applications on top of its smart contract layer.Table of Contents​Chapter 1. IntroductionWe introduce the core concepts discussed in the book, and situate them with respect to the foundational principles of cryptocurrencies and web3. We discuss decentralisation. We describe the key design decisions of the EVM (Ethereum Virtual Machine) and how they raise some problems for product engineers. We describe the book ahead and what will be covered, chapter by chapter.Chapter 2. The lifecycle of an Ethereum transactionWe discuss the lifecycle of a request on Ethereum, guiding the user through: how is a request initiated by a UI and confirmed by a user; sent to a node, validated, how can UIs display its status, when is a transaction confirmed. We ask: what is a smart contract? We frame smart contracts as APIs. We also set up the following three chapters with the tripartite structure of write, read, and side-effect.Chapter 3. WalletsWe discuss the role of wallets as both stores and signers. We discuss the popular MetaMask model for wallet injection, WalletConnect, EIP-1193, and other attempts to standardise the wallet interface. We explore wallets as identities, and describe approaches to 'logging in' with Ethereum. We explore different attack vectors that integrating wallets might raise.Chapter 4. Nodes and IndexesWe talk about nodes – the programmatic gateway to the blockchain – in more detail: how to connect to them and use them to retrieve information. We discuss the difference between live data and indexed data. We discuss how external RPC nodes allow external function calls with and friends. We discuss ABIs and contract interfaces.Chapter 5. EventsWe investigate Ethereum's event model, and how to reconstruct a contract's state from the event log. We talk about Bloom filters and how to process many events efficiently.Chapter 6. TransactionsThis chapter builds more on the first chapter, diving into detail about the implementation of transactions. We discuss interfaces for creating, signing, and viewing transactions. We frame transactions theoretically and practically. We discuss the RPC call and its interface. We break down the minutiae of cryptographic signing and nonces, and consider how it affects the UI of applications. We discuss transaction statuses and estimation.Chapter 7. Error HandlingIn this chapter, we discuss the various failure modes of smart contracts and how to build rich, useful user interfaces around them. We consider gas, nonces, and transaction synchronisation. We talk about ways of building error-resilience into your product with input validation. We talk about standardising error messages at the smart contract level.Chapter 8. ToolingIn this chapter, we investigate the sorts of tools available to the product engineer, drawing on problems faced in the previous chapters. We discuss running manual tests, declarative provisioning of infrastructure, and keeping private keys safe. We also discuss current lacunas and places where existing tooling could be improved.Chapter 9. Data-first ApplicationsWe wrap-up the preceding discussion with a more opinionated chapter on a data-first approach to application design. In particular, I'll make the case for single-page applications backed by a data scraper as a strong model for building application infrastructure around smart contracts, tying together the themes of the preceding few chapters.Chapter 10. Conclusion: Smart Contracts, Smarter productsWe discuss the ways that the surface area of smart contracts rubs against the surface area of web applications, with an emphasis on the more commercial and conceptual. We explore how detaching state from interface allows for more decentralised and censorship-resistant protocols – and how product engineers can profit from this split. We talk about the many ways that thoughtful product engineering can improve the user experience of crypto, and ruminate on the future direction of the ecosystem.Appendix 1: A Common-Sense Crypto-Native ChecklistWe provide a summary of the main questions and action points found in the book, with an easy reference checklist for engineers to work through when building their crypto-native applications.Appendix 2: Resources and BibliographyWe provide one or two pages of QR codes, with links to relevant resources. We provide a more comprehensive, traditional bibliography.

Read more less

Book SynopsisAssess, plan, develop, implement, and manage AWS EC2 Instances, Cloud Formation using JSON Template with Bash programming language, and Cloud Watch monitoring. This book helps the public and private sectors comprehend how to assess and evaluate AWS cloud software as a service (SaaS), infrastructure as a service (IaaS), and platform as a service (PaaS). Government and business sector entities are looking for strategies to upgrade on-premises information systems to virtual cloud infrastructure orchestration and automation.You'll gain a step-by-step approach to planning, developing, implementing, and managing cloud infrastructure, services, and platforms that help reduce cost increases, scalability, and improves security. Outline your strategy to research how cloud infrastructure is planned and developed before being deployed and managed by on-premises IT team members. This book also supports cloud services for AWS and helps you understand why supporting and usingAWS for cloud services Table of ContentsChapter I Cloud Services and TechnologiesChapter goal: This chapter enables readers to understand the value of assessing and evaluating cloud services provided by Amazon Web Services (AWS) and Microsoft Azure, prior to making an executive decision to partner with either service provider. Readers will comprehend how to calculate the total cost of ownership for usage of cloud services rendered by both service providers, and acquire knowledge of the advantages and disadvantage of services rendered by both services providers. Readers will also acquire knowledge of applicable laws regarding usage of cloud services in alignment with federal laws and guidelines as well as gain knowledge regarding policy enforcement mechanisms, system monitoring and audit mechanisms, and finally complete discussion questions that help readers comprehend their study of this chapter and the valued components that should be remembered. Sub-topics:1. Total Cost of Ownership2. Functional requirements3. Nonfunctional requirements4. Risk analysis and management guidelines5. Six components of GDPR6. Understand physical security issues7. Critical IT requirements related to data storage8. Potential privacy issues and migration strategiesChapter 2: Network Engineering Chapter goal: This chapter helps readers gain knowledge about Internet protocol and its impact in cloud architecture. Readers will also learn about packet switching, IP addressing, DNS, IP subnetting, IP address classes, CIDR Notation, multiple subnets in a LAN, subnetting proposal, Transport Control Protocol (TCP), transport reliability, TCP sliding windows, software defined networking, networking in the cloud, cloud command line interfaces, and cloud APIs. Having this knowledge helps improve decision making regarding what strategies best serve the needs of an enterprise migrating from an on-premises legacy information system to a cloud infrastructure. By the time readers conclude this chapter, they will understand the meaning of internet protocol, packet switching, authoritative, recursive, and what makes open-flow so popular. Most importantly, readers acquire knowledge about subnetting proposals and their role in supporting enterprises. Subtopics:1. TCP Connections2. SDN Enables BalletOnline Cloud Deployment3. Declarative resource definitions4. AWS Migration Environment and Configure Web ServicesChapter 3: Infrastructure Planning and MigrationChapter goal: This chapter will educate readers about cloud infrastructure planning methods that increase organizational structure that aligns with business acumen and helps readers understand migration prerequisites. This enables a reduction of setbacks arises during the migration from on-premises to cloud infrastructure. Furthermore, readers will be able to effectively assess migration tools and comprehend AWS Application Discovery. Most important, readers will acquire methods that have proven beneficial and provides a return on the initial investment. Sub-topics: 1. Cloud premigration considerations2. Cloud migration tool assessment3. AWS Application Discovery Services4. Agentbase options5. Agentless options6. Evaluation of discovery application and infrastructure data 7. Migration recommendationsChapter 4: Computing Development and ManagementChapter goal: Readers will gain knowledge about cloud service offering for email and how AWS services help reduce concerns of vulnerability. Readers will also learn about AWS Cloud Watch and how this tool helps capture metrics and reports statistics regarding the consumption for backup and archiving. Additionally, readers will learn about AWS backup and archiving as well as AWS virtual private cloud and the value of relying on VPN (Virtual Private Networks). Furthermore, readers will attain information about AWS S3 buckets and cloud synchronization services. Subtopics:1. Data Backups and Archiving to Cloud Using Cloud Sync Services2. AWS Cloud Watch Monitoring3. AWS Service Catalog4. Cloud operations end-users’ guides5. Cloud operations administrative guides6. LimitationsChapter V Cloud Computing Orchestration and AutomationChapter goals: This chapters prepares readers for the orchestration and automation of AWS cloud services. Readers will also learn about cloud advanced features as well as advanced data solutions in the cloud. Most importantly, readers will acquire knowledge about Symantec Cloud Workload Protection for Storage Overview. Attaining this knowledge will increase readers trust with AWS services and the ability to effectively manage their cloud virtual private infrastructure with security strategies that are impenetrable. Subtopics:1. Monthly cost analysis2. Total costs of ownership analysis3. Use casesa. Web applicationsb. Messagingc. Disaster recovery and backupd. IT service planning4. Return on investment analysisGlossaryIndex

Read more less

Book SynopsisLearn to write better automated tests that will dramatically increase your productivity and have fun while doing so. This book is a build-your-own adventure designed for individual reading and for collaborative workshops. You will build an xUnit automated test framework using JavaScript: initially a clone of Jest, but adding a couple of neat features borrowed from RSpec, the genre-defining tool for behavior-driven development (BDD). Along the way, you will explore the philosophy behind automated testing best practices. The automated test runner is one of the most important innovations within software engineering. But for many programmers, automated testing remains a mystery, and knowing how to write good tests is akin to sorcery. As the chapters of this book unfold, you will see how the humble test runner is an elegant and simple piece of software. Each chapter picks a single feature to build, like the it function or the beforeEach Table of ContentsPart 1: Building the Core of a Test Framework In this part we build a barebones implementation of a test runner.Chapter 1: Creating an NPM Package of My Very Own, You will create a new NPM package for concise-test, including an entry-point for the test runner.Chapter 2: Building it to Define a Testwe’ll implement the it function for defining tests, and start printing out some useful test run information on screen.Chapter 3: Grouping Tests with Describe, we’ll add support for grouping tests with the describe function, and we’ll continue to build out test reporting on screen. Chapter 4: Promoting Conciseness with BeforeEach and AfterEachWe continue our quest for concise testing facilities with the addition of beforeEach and afterEach functions. Chapter 5: Improving Legibility with Expect, We finish off the core of our API by building an abstraction over throw new Error. Part 2: Constructing a Usable Framework In this part we add features that you’ll use on a daily basis. Chapter 6: Formatting Expectation ErrorsWe write a formatter for stack traces to help pinpoint failures quickly. Chapter 7. Automatically Discovering Test FilesWe’ll add test file discovery to our test runner, and add support for running a single file through a command line argument. Chapter 8: Focusing on Tests with It.Only and Describe.Only, We split out runner into two phases: a discovery phase and an execution phase. In between them, we insert a filter phase to support running only a subset of phases. Chapter 9: Supporting Asynchronous Tests, We add the ability to wait on tests that return Promise objects, and timing out tests with it.timesOutAfter. Chapter 10: Reportingwe use a pub-sub model to build a plug-in system for reporters. Part 3: Extending for Power Users In this part we continue to add advanced features. Chapter 11: Sharing Behavior with it.BehavesLike, We borrow an important feature from Ruby: inheritance for describe blocks, which gives us a flexible mechanism for removing duplication between test groups. Chapter 12: Tagging Tests We create a mechanism for running a group of tests based on their tag. Chapter 13 : Skipping Tests we introduce a number of ways to skip tests, including tests without bodies, and it.skip plus describe.skip functions. Chapter 14 : Randomizing TestsWe add a runtime flag for randomizing the order of tests, which is a useful technique for catching invisible dependencies between tests. Part 4: Test Doubles and MocksChapter 15. Understanding test doubleswe create a function that can be used as a test spy and stub.Chapter 16. Module MocksWe create a system for mocking out entire modules, which is a useful technique when creating component doubles when testing React.

Read more less

Book SynopsisChapter 1: What is Advocacy?.- Chapter 2: Becoming a Developer Advocate.- Chapter 3: Starting a Developer Advocacy Team.- Chapter 4: Managing Work Output for your New Advocacy Team.- Chapter 5: Getting Started with Content for Developer Advocacy.- Chapter 6: Understanding and Optimizing Stakeholders in Developer Advocacy.- Chapter 7: Growing: Creating an Advocacy Roadmap.- Chapter 8: Amplifying Advocacy's Impact.- Chapter 9: Measuring Advocacy's Impact.- Chapter 10: Parting Thoughts on Successful Developer Advocacy.Table of Contents● Chapter 1: What is Advocacy? o Who can benefit from dev advocacy? o Why advocacy? o Business Goals? ● Chapter 2: Becoming o Advocacy starts with a team of 1 o Attributes of an advocate o Transitioning into advocacy as an Engineer o Preparing for advocacy as a tech company ● Chapter 3: Starting: The foundations of an advocacy team o Structure o Compensation o Roles o Interviewing for and Hiring Advocates ● Chapter 4: Starting: Advocacy work product o Tasks to be completed o Processes to be set up o Typical deliverables ● Chapter 5: Starting: Content o Content first conversations o The content factory o The anatomy of technical content ● Chapter 6: Starting: Stakeholders o Key to cross-functional collaboration o Developer Marketing o Engineering o DevRel ● Chapter 7: Scaling: Advocacy Roadmap o 0 to 100 Roadmap o Growing the team o Expanding capabilities ● Chapter 8: Scaling: Amplifying success o Going beyond the body shop o Increasing internal value o Leveraging PR and Marketing o Advocacy Operations 101 ● Chapter 9: Scaling: Measuring Impact o KPIs o Share of Conversation ● Chapter 10: The Advocacy North Star o Industry Examples o Conclusion

Read more less

Book SynopsisLearn how to make the right technical decisions to achieve your organization's business objectives. This book is a guide for software engineers who are responsible for making technical decisions that impact the business objectives of their organization.You'll start by reviewing business priorities, technical decision-making, and see how to overcome common challenges. Using real world case studies, this book offers a comprehensive overview of the skills and strategies required for senior engineers to effectively navigate complex technical and business challenges. You will also gain advice on building trust and credibility with business stakeholders and communicating technical challenges and opportunities to them. The Technical-Business Equilibriumreveals practical strategies for assessing technical feasibility and risk, selecting the best solutions to meet your company's goals, and communicating those decisions to business stakeholders. What You Will LearnUtilize techniques for evalTable of Contents1. Understanding Business Priorities.- 2. Technical Decision-Making.- 3. Balancing Technical and Business Priorities.- 4. The Role of Senior Engineers.- 5. Case Studies in Balancing Technical and Business Priorities.- 6. Best Practices for Balancing Technical and Business Priorities.- 7. Overcoming Challenges.- 8. Conclusion.

Read more less

Book Synopsis

Read more less

Book SynopsisBlazor in Action is a practical guide to building stunning UIs and client-side applications using C# and .NET. Written to the most recent stable build of Blazor, this example-driven book shows how to build a complete end-to-end hiking route web application that's full of easily reusable code. You'll create your own custom Blazor components, including handy UI elements like form controls, and learn how to implement access controls and other important security features. Finally, you'll learn how you can use Blazor components inside your existing ASP.NET applications, and get essential tips and tricks on tuning your app's performance. By the time you're done, you'll be ready to develop beautiful sites and apps that seamlessly execute your C# code natively in the browser.Trade Review"The ultimate guide to building Blazor web apps regardless of your experience level." Jeff Smith "An excellent resource for learning Blazor concepts." Mark Chalkley "A highly accessible and clear introduction to a very interesting and what will be a very relevant technology in the UI/UX space." John Rhodes "A very good book to learn Blazor, with a pratical examples and detailed explanations of concepts like components, routes, parameters, and event handlers." Alberto Acerbis "If you want to get started with Blazor, start with this book." Richard Michaels "I would highly recommend the book to anyone who has some background in web development and is staying current with C# language features." Al Pezewski

Read more less

Book SynopsisDesign systems optimized for deep learning models. Written for software engineers, this book teaches you how to implement a maintainable platform for developing deep learning models. In Engineering Deep Learning Systems you will learn how to: Transfer your software development skills to deep learning systems Recognize and solve common engineering challenges for deep learning systems Understand the deep learning development cycle Automate training for models in TensorFlow and PyTorch Optimize dataset management, training, model serving and hyperparameter tuning Pick the right open-source project for your platform Engineering Deep Learning Systems is a practical guide for software engineers and data scientists who are designing and building platforms for deep learning. It's full of hands-on examples that will help you transfer your software development skills to implementing deep learning platforms. You'll learn how to build automated and scalable services for core tasks like dataset management, model training/serving, and hyperparameter tuning. This book is the perfect way to step into an exciting—and lucrative—career as a deep learning engineer. about the technology Behind every deep learning researcher is a team of engineers bringing their models to production. To build these systems, you need to understand how a deep learning system's platform differs from other distributed systems. By mastering the core ideas in this book, you'll be able to support deep learning systems in a way that's fast, repeatable, and reliable.

Read more less

Book Synopsis

Read more less

Book Synopsis

Read more less

Book SynopsisThis book guides students and professionals in developing cloud computing-based software projects like OCMS and RBCS using Oracle, PL/SQL, IDS, and .Net. It covers theory, technologies, tools, feasibility study, entity relationship model, data flow diagrams, normalization, table creation, and GUI application development.

Read more less

Book Synopsis

Read more less

Book SynopsisThis guide teaches the practical uses of Quicken for Macintosh software - the chapter topics are organized like the product for easy familiarity. It includes coverage of all the product features, menu items and tools for financial management.Table of ContentsPart I Quicken setup and basics: getting to know Quicken; setting up accounts and categories; going online with Quicken and Quicken.com. Part II Managing your bank and credit card accounts: recording bank and credit card transactions; online banking with Quicken. Part III Tracking your investments: tracking investments; using online investment tracking tools; maximizing investment returns. Part IV Managing your assets and debts: monitoring assets and loans; managing home, car and insurance expenses. Part V Saving money and achieving your goals: saving money at tax time; saving money and reducing debt; planning for the future. Part VI Working with Quicken data: automating Quicken transactions; reconciling accounts; insights, reports and graphs.

Read more less

Book SynopsisThis book is a critical introduction to code and software that develops an understanding of its social and philosophical implications in the digital age. Written specifically for people interested in the subject from a non-technical background, the book provides a lively and interesting analysis of these new media forms.Trade Review'This is a beautifully written book that pulls off the difficult task of introducing the subject of software and the workings of code to the non specialist whilst also providing an original take of the philosophical and the cultural importance of Code in contemporary culture.' - Michael Bull, University of Sussex, UK 'The book is warmly recommended:[Berry's] understanding of software is fantastic. It reaches out to so many discussions and has so many implications that it is an engine in itself: it produces ideas.' - Jussi Parikka, Leonardo on-line 'What is important about The Philosophy of Software is that it really is about what it claims to be about. Rather than trying to shoehorn software into an existing philosophical or political agenda it considers software as a thing in itself and finds those philosophers and philosophical ideas that best address the vitally important phenomenon of software. However much philosophy, computer science or cybercultural theory you may know this is a book that will set you thinking about software anew.' - Rob Myers, Furtherfield 'One of the most prolific contributors to the CCSWGs, David M. Berry has also contributed one of the most extensive manuscripts on reading code and code culture. The Philosophy of Software contains chapters on the epistemology and ontology of code, reading and writing code, running code, and the phenomenology of code. Written for a general audience, the book reads several code examples including the Microsoft Windows 2000 source code and obfuscated code competitions.' - Mark C. Marino, Computational Culture, 2014Table of ContentsAcknowledgements The Idea of Code What is Code? Reading and Writing Code Running Code Towards a Phenomenology of Computation Real-Time Streams Bibliography Index

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

Book SynopsisA hands-on guide to testing techniques that deliver reliable software and systems Testing even a simple system can quickly turn into a potentially infinite task. Faced with tight costs and schedules, testers need to have a toolkit of practical techniques combined with hands-on experience and the right strategies in order to complete a successful project. World-renowned testing expert Rex Black provides you with the proven methods and concepts that test professionals must know. He presents you with the fundamental techniques for testing and clearly shows you how to select and apply successful strategies to test a system with budget and time constraints. Black begins by discussing the goals and tactics of effective and efficient testing. Next, he lays the foundation of his technique for risk-based testing, explaining how to analyze, prioritize, and document risks to the quality of the system using both informal and formal techniques. He then clearly describes howTable of ContentsAcknowledgments. Introduction. Part I Goals, Strategies, and Tactics. Chapter 1 What Does It Mean to Be Pragmatic? What Do Effective and Efficient Mean? What Effects Do You Want? What Is the Right Level of Efficiency? Avoiding Redundancy. Reducing Cost. What Software Testing Isn’t…But Is Often Thought to Be. Five Phases of a Tester’s Mental Life. Other Founding Views on Testing. Testing as a Form of Quality Risk Management. So What Is the Test Team All About? What Does “Quality” Mean to You? Chapter 2 Triangle Test Exercise. Exercise: The Triangle Test. Your Solution for the Triangle Test. Your Solution for the Triangle Test (Continued). Author’s Triangle Test Solution. Chapter 3 Aligning Testing with the Project. Why Do Organizations Test? Perspectives on Testing. Testing in Context. Common Test Phases and Objectives. Testing Throughout the Organization. The V Model. Evolutionary and Incremental Models. The Spiral Model. Regrettably Common Model: Code and Fix. Testing Maintenance Releases. System Integration. Hardware/Software Development. The Test Process. Chapter 4 Understanding Test Strategies, Tactics, and Design. Aligning Mission, Strategies, and Tactics. Analytical Test Strategies. Model-Based Test Strategies. Methodical Test Strategies. Process-Oriented Test Strategies. Dynamic Test Strategies. Philosophical Test Strategies. Regression. Regression Strategy 1: Repeat All Tests. Regression Strategy 2: Repeat Some Tests. Three Other Regression Strategies. Tactics: Categories of Testing Techniques. Strategic and Tactical Considerations. The Test System. Classic Principles for Test Design. Phases of Test Development. Synopsis of Test Strategies, Tactics, and Design. Part II Risk-Based Testing. Chapter 5 Understanding Risks to System Quality. Categories of Quality Risks. Functionality. Performance and Reliability. Stress, Capacity, and Volume. States. Transactions. Installation and Deinstallation. Operations. Maintenance and Maintainability. Regression. Usability and User Interface. Data Quality. Error and Disaster Handling and Recovery. Date and Time Handling. Localization. Configuration and Compatibility. Networked, Internetworked, and Distributed. Standards and Regulatory Compliance. Security. Timing and Coordination. Documentation. Can You Think of Other Quality Risks? Chapter 6 Aligning Testing with Quality Risks. Prioritize Risks to System Quality. Testing, Customer Usage, and System Configurations. Approaches for Quality Risks Analysis. Informal Quality Risk Analysis. Tips for Risk Analysis. Challenges of Risk Analysis. Chapter 7 Quality Risk Analysis Exercise. My Solution. Comments on My Solution. A Funny Thing Happened to Me on the Way to the Quality Risks… . Bonus Exercise. Template. My Solution. Comments on My Solution. Bonus Example: Grays and Blues Quality Risk Analysis. Part III Static Testing. Chapter 8 Reviews and Other Static Tests. Testing Requirements and Designs. Reviews Costs and Benefits. Types of Reviews. Reviews for Verification and Validation. Reviews as a Way to Improve the Process, Improve the System, and Reduce Costs. Answers to the Three Questions about Static Testing. Reviews as a Way to Achieve Consensus and Understanding. The Review Process, Roles, and Responsibilities. Deliverables and Ground Rules from Reviews. Common Requirements and Design Bugs. Reviewing (and Testing) Documentation. Other Static Tests. Chapter 9 Review Exercise. Reviews. Your Solution. My Solution. Comments on My Solution. Bonus Exercise: Reviewing Triangle Requirements Title Page. Triangle Requirements Review Using Wiegers’s List. The Requirements Bugs You Found. My Solution: Requirements Bugs. Comments on My Solution. Part IV Behavioral Testing. Chapter 10 Equivalence Classes and Boundary Values. Equivalence Partitioning. Boundary Value Analysis. Integer. Real Numbers. Character and String. Date. Time. Currency. Beyond Functional Classes and Boundaries. Chapter 11 Equivalence Classes and Boundary Values Exercise. Functional Boundaries and Classes. My Solution and Comments. Nonfunctional Boundaries and Classes. Omninet Marketing Requirements Document (v0.3). Omninet System Requirements Document (v0.2). Chapter 12 Use Cases, Live Data, and Decision Tables. Use Cases and Scenario Tests. Nouns and Verbs, Adjectives and Adverbs. Live Data and Customer Tests. Decision Tables. Chapter 13 Decision Table Exercise. Decision Table Tests. My Solution and Comments. Decision Tables and Boundary Values. My Solution and Comments. Building a Decision Table for Testing. My Solution and Comments. Chapter 14 State Transition Diagrams. Describing Systems with States Using State Transition Diagrams. State Tables. Printer Server State Transition Diagram. Chapter 15 State Transition Diagram Exercise. Kiosk States. My Solution and Comments. ATM State Models. My Solution and Comments. Grays and Blues and State Transition Diagrams. My Solution and Comments. Chapter 16 Domain Testing. Combinatorial Explosions. A Domain Example Using Frequent-Flyer Programs. Possible Domain Test Values. An Aerospace Example. When Domain Rules Change. Domain Analysis Summary. Complex Domain Testing Example. A General Rule for Complex Domains. Chapter 17 Domain Testing Exercise. My Solution and Comments. Chapter 18 Orthogonal Arrays and All Pairs. Combinatorial Explosions. Orthogonal Arrays and All-Pairs Tables. Two Orthogonal Arrays. Selecting an Orthogonal Array. Applying Orthogonal Arrays to a Complicated Real-World Example. All-Pairs Tables. Other Thoughts on Configuration Testing. Chapter 19 Orthogonal Arrays Exercise. My Solution and Comments. Chapter 20 Reactive Testing. General Facts about Reactive Tests. Error Guessing, Attacks, and Bug Taxonomies. Bug Hunting. Exploratory Tests. Checklists. Other Sources of Inspiration for Reactive Testing. Advantages and Disadvantages. A Case Study of Exploratory Testing. Part V Structural Testing. Chapter 21 Control-Flow Testing. Code Coverage. McCabe Cyclomatic Complexity. Chapter 22 Control-Flow Testing Exercise. My Solution and Comments. Chapter 23 Data-Flow Testing. Chapter 24 Data-Flow Testing Exercise. My Solutions and Comments. Chapter 25 Integration Testing. Drivers and Stubs. Integration Techniques. Backbone Integration. McCabe Basis Paths for Integration. Enhanced Hex Converter Program. Call Flow. Chapter 26 Integration Basis Test Exercise. My Solution and Comments. Part VI Appendices. Appendix A Omninet: The Internet Everywhere Marketing Requirements Document. 1 Scope. 1.1 Terms, Acronyms, and Abbreviations. 1.2 Applicable Documents. 2 Required release date. 3 Description of requirements. 3.1 General technical requirements. 3.1.1 Welcome. 3.1.2 Payment. 3.1.3 Internet Browser. 3.1.4 Performance. 3.1.5 Localization. 3.1.6 Content Control. 3.1.7 Session Termination. 3.1.8 Confidentiality. 3.2 Administration. 3.2.1 Software Updates. 3.2.2 View Kiosks. 3.2.3 View Users. 3.2.4 Modify User. 3.2.5 Terminate User. Appendix B Omninet: The Internet Everywhere System Requirements Document. Functionality System Requirements. Reliability System Requirements. Usability System Requirements. Efficiency System Requirements. Maintainability System Requirements. Portability System Requirements. Design Models. Omninet System Architecture. Payment Processing Decision Table. Kiosk Module Flow. Kiosk State-Transition Diagram. Kiosk State-Transition Table. Kiosk OS/Browser/Connection Speed Configuration Orthogonal Array. Appendix C Bibliography and Other Recommended Readings. RBCS Company Profile. Index.

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less

a huge range and FREE tracked UK delivery on ALL orders.

Read more less