Book Image

Hands-On Software Engineering with Python

By : Brian Allbee, Nimesh Verma
Book Image

Hands-On Software Engineering with Python

By: Brian Allbee, Nimesh Verma

Overview of this book

Software Engineering is about more than just writing code—it includes a host of soft skills that apply to almost any development effort, no matter what the language, development methodology, or scope of the project. Being a senior developer all but requires awareness of how those skills, along with their expected technical counterparts, mesh together through a project's life cycle. This book walks you through that discovery by going over the entire life cycle of a multi-tier system and its related software projects. You'll see what happens before any development takes place, and what impact the decisions and designs made at each step have on the development process. The development of the entire project, over the course of several iterations based on real-world Agile iterations, will be executed, sometimes starting from nothing, in one of the fastest growing languages in the world—Python. Application of practices in Python will be laid out, along with a number of Python-specific capabilities that are often overlooked. Finally, the book will implement a high-performance computing solution, from first principles through complete foundation.
Table of Contents (21 chapters)
Free Chapter
1
Programming versus Software Engineering

Summary

Though it still needs to be thoroughly tested, which will be addressed in Chapter 14, Testing Data Persistence, preliminary testing of the JSON-based data file persistence feels pretty solid at this point. The CRUD operations that are required by BaseDataObject, passing through JSONFileDataObject to all of the concrete data objects, are all present and accounted for, and they appear to be fully functional. The change to the structure of the Order class might be cause for some concern with respect to the original design, but was not difficult to deal with. That change should be specifically called out during the approval process for the iteration, since it represents a change to the original design, but it doesn't feel like it will be a cause for any major concerns at this time.

With one data persistence mechanism done, and while the concepts are still fresh, it&apos...