Book Image

Modern Programming: Object Oriented Programming and Best Practices

By : Graham Lee
Book Image

Modern Programming: Object Oriented Programming and Best Practices

By: Graham Lee

Overview of this book

Your experience and knowledge always influence the approach you take and the tools you use to write your programs. With a sound understanding of how to approach your goal and what software paradigms to use, you can create high-performing applications quickly and efficiently. In this two-part book, you’ll discover the untapped features of object-oriented programming and use it with other software tools to code fast and efficient applications. The first part of the book begins with a discussion on how OOP is used today and moves on to analyze the ideas and problems that OOP doesn’t address. It continues by deconstructing the complexity of OOP, showing you its fundamentally simple core. You’ll see that, by using the distinctive elements of OOP, you can learn to build your applications more easily. The next part of this book talks about acquiring the skills to become a better programmer. You’ll get an overview of how various tools, such as version control and build management, help make your life easier. This book also discusses the pros and cons of other programming paradigms, such as aspect-oriented programming and functional programming, and helps to select the correct approach for your projects. It ends by talking about the philosophy behind designing software and what it means to be a "good" developer. By the end of this two-part book, you will have learned that OOP is not always complex, and you will know how you can evolve into a better programmer by learning about ethics, teamwork, and documentation.
Table of Contents (18 chapters)
Free Chapter
1
Part One – OOP The Easy Way
5
Part Two – APPropriate Behavior

Non-Functional Requirements Are Essential

I'd almost go as far as to say that the primary indicator of success for an application architecture is whether it supports the non-functional requirements the customer has described. Anyone can, given enough patience and stubbornness, carry on gluing features together arbitrarily until all of the required functionality is present. However, making it do that coherently, in a way that combines desired attributes from the customer side (the NFRs) and the developer side (adaptability, readability, and the like) is where the art form of software architecture comes in.

So, what are these non-functional requirements? It's common to say that these are the "-ility" statements made about the software. It takes a bit of squinting to accept that, but it's roughly true:

  • Performance: How is this an -ility? Is it speedability? Velocitility? Well, something like that anyway. It's important to understand what's meant by performance...