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

Selecting a data storage option

Looking at the logical architecture for hms_sys, and allowing for a local data store for the Artisan Application that wasn't in the original diagram, there are three databases that development needs to be concerned with:

The Web-Store Database is attached to the Web-Store Application, and cannot be modified as a result. The current expectation is that modifications to data in that database will be handled by a call to the API that the Web-Store Application makes available. At this point, then, data access to and from this database can be set aside.

The artisan Database, on the other hand, doesn't exist yet at all, and will have to be created as part of the development of hms_sys. It feels safe to assume, given the artisan-level, installation-related stories from the first iteration, that keeping the number of software installations they...