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

Setting Up Projects and Processes

Our first iteration is all about getting things ready for all of the following iterations, and for any development efforts after the project is initially complete—bug fixes, maintenance, new feature requests, and so on. This sort of preparation will need to be undertaken for any new development effort over a certain expected degree of complexity, but it may not be broken out into its own iteration. Creating many of the foundational structures could be managed as part of other iterations;creating the project's structure when the first development that needs it starts, for example. The trade-off that's tied into taking that approach is that there is a higher probability that early definition work will have to be significantly altered as later development unfolds because that original structure couldn't accommodate multiple...