concept software in category java

This is an excerpt from Manning's book JUnit in Action.
System testing of software is testing conducted on a complete, integrated system to evaluate the system’s compliance with its specified requirements. The objective is to detect inconsistencies among units that are already integrated.
Dan North originated BDD in the mid-2000s. It is a software development technique that starts from the business requirements and goals and transforms them into working features. BDD encourages teams to interact, use concrete examples to communicate how the application must behave, and deliver software that matters, supporting cooperation between stakeholders. TDD helps us build safe software; BDD helps us build software that provides business value. Using BDD, we determine which features the organization really needs and focus on implementing them. We can also discover what users actually need, not just what they ask about.

This is an excerpt from Manning's book Modern Java in Action: Lambdas, streams, reactive and functional programming.
Google’s search engine is an example of a piece of code that’s too big to run on a single computer. It reads every page on the internet and creates an index, mapping every word appearing on any internet page back to every URL containing that word. Then, when you do a Google search involving several words, software can quickly use this index to give you a set of web pages containing those words. Try to imagine how you might code this algorithm in Java (even for a smaller index than Google’s, you’d need to exploit all the cores in your computer).
Before you delve into the details of the Java Module System, it’s useful to understand some motivation and background to appreciate the goals set out by the Java language designers. What does modularity mean? What problem is the module system looking to address? This book has spent quite a lot of time discussing new language features that help us write code that reads closer to the problem statement and, as a result, is easier to understand and maintain. This concern is a low-level one, however. Ultimately, at a high level (software-architectural level), you want to work with a software project that’s easy to reason about because this makes you more productive when you introduce changes in your code base. In the following sections, we highlight two design principles that help produce software that’s easier to reason about: separation of concerns and information hiding.

This is an excerpt from Manning's book JavaFX in Action.
In the pre-internet age, software was installed straight onto the hard drive. If suddenly overcome by an urge to share with friends your latest poetic masterpiece, you needed at your disposal both the document file and the software to open it. Chances are neither would be available. Your friends might be grateful, but clearly this was a problem needing a solution.
So, we don’t need to make any changes to the software; our game is already primed to go mobile. We just need to know how to get it there!