Difference between revisions of "Software Development"

From The Thinkulum
Jump to navigation Jump to search
(Made minor changes to the topics intro, updated the SWEBOK download link, and added chapter numbers and placeholder topics.)
(Added "Introduction to the Guide" to the topic outline.)
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Introduction ==
== Introduction ==


=== Purpose ===
This is a collection of notes on software development. Its main purpose is to help me raise my development's level of professionalism. It also gives me a place to air an opinion or two.


This project is a growing set of notes on various aspects of software development. Its purpose is to define a set of standard operating procedures for my programming projects.
To give you an idea of my background, after some BASIC programming in my childhood and a break of many years for other interests, I returned to hobby programming just after undergrad and was able to make it my living several years later in 2006. That phase of my developer life started with Perl, and since then I've moved on to Python and XSLT. I've worked mainly in the area of text processing. JavaScript and PHP have played intermittent supporting roles for occasional web development or InDesign scripting. My projects have all been either solo or with a very small team. It's all been on Windows and mostly for the command line.
 
=== Background ===
 
For most of my coding life, I have been the only user of my programs. I wrote them to aid my work or personal life, and only rarely did anyone else even see my code or watch it run. This wasn't on purpose. It just turned out that way. In my current job I do belong to a small development team, but our programs are still only for in-house use, so the only needs we have to consider are our own.
 
This situation is starting to change. My programming projects are becoming more relevant to the outside world, and I want to share some of them as open source. This means I'm needing to reshape some of my programming practices and learn some areas of software development I've had the luxury of ignoring all these years.
 
I haven't completely ignored these areas, though. I pick up on them here and there as I read about how other people code or as I see them in the software I use. Knowing that I'll probably need to know about them someday, I've kept a list. And now the time has come for me to fill in the details.
 
I'm filling in the details here in this project for two reasons. First, as I learn, writing helps me clarify my thoughts and keep them flowing. And second, posting my writing might help other people. So if you're like me and you've programmed mainly for yourself--what I call private coding--and you're starting to share your work with others--public coding--then maybe what I've learned so far can grease some of your own planning.
 
=== Method ===
 
This project consists of my reading other developers' advice, examining their code, deciding what to adopt and how to adapt it to my needs and preferences, and creating templates, procedures, reference materials, and anything else that might help me code well for a public user base.
 
To show how I'm implementing these ideas in my own code, I'll refer to [https://github.com/thinkulum my GitHub repositories] throughout the project, mainly my templates for [https://github.com/audreyr/cookiecutter cookiecutter], a Python app that creates project skeletons for any language, and my snippets for [https://www.sublimetext.com/ Sublime Text 2], the text editor I use. Snippets are templates Sublime inserts wherever you type the corresponding trigger strings.
 
=== Limitations ===
 
To give you an idea of my background, I've worked for the past 15 or so years in the publishing industry doing mostly text processing and some web development. The languages I'm most familiar with are Perl, Python, XSLT, and some JavaScript, with a smattering of PHP and VBA. I've spent almost all my time in Windows. I hope to branch out into at least Linux in the future, if only to expand my mind.
 
This project will be oriented toward Python for now, but I imagine a lot of its suggestions apply to other languages too. At this point it also centers around desktop command-line programs, but I'm hoping to expand it into other interfaces and environments.
 
=== Feedback ===
 
Since this project is a place for me to learn, I welcome feedback, and I'm always open to arguments that my choices could be improved or suggestions for things I've missed.


== Topics ==
== Topics ==
Line 35: Line 9:
As a way to organize my notes and make sure I don't miss anything important, I'll use the structure of IEEE's ''Guide to the Software Engineering Body of Knowledge'' (SWEBOK). It's a standard that overviews the entire field and forms the basis for creating things like curricula and certifications. You can [https://www.computer.org/education/bodies-of-knowledge/software-engineering/v3 download the PDF] for free.
As a way to organize my notes and make sure I don't miss anything important, I'll use the structure of IEEE's ''Guide to the Software Engineering Body of Knowledge'' (SWEBOK). It's a standard that overviews the entire field and forms the basis for creating things like curricula and certifications. You can [https://www.computer.org/education/bodies-of-knowledge/software-engineering/v3 download the PDF] for free.


The items under the SWEBOK knowledge areas in the first level link to my notes on each topic.
The items under the SWEBOK knowledge areas in the first level link to my notes on each topic. I've sorted the knowledge areas to approximate my preferred order, though I'll address them more haphazardly.


* Ch. 1: Software requirements
* '''Introduction to the Guide'''
* '''Ch. 12: Software engineering economics'''
* '''Ch. 11: Software engineering professional practice'''
** [[/License/]]
* '''Ch. 14: Mathematical foundations'''
* '''Ch. 13: Computing foundations'''
* '''Ch. 15: Engineering foundations'''
* '''Ch. 9: Software engineering models and methods'''
* '''Ch. 7: Software engineering management'''
* '''Ch. 10: Software quality'''
* '''Ch. 6: Software configuration management'''
** [[/Version Control/]]
** [[/Version Numbers/]]
** [[/Distribution/]]
* '''Ch. 8: Software engineering process'''
** [[/Software Development Methodology/]]
*** [[/Iterative and Incremental Development/]]
* '''Ch. 1: Software requirements'''
** Requirements
** Requirements
* Ch. 2: Software design
* '''Ch. 4: Software testing'''
** [[/Testing/]]
* '''Ch. 2: Software design'''
** Design
** Design
** Architecture
** Architecture
** UX and UI
** UX and UI
* Ch. 3: Software construction
* '''Ch. 3: Software construction'''
** [[/Code Style/]]
** [[/Code Style/]]
** [[/Project Structure/]]
** [[/Project Structure/]]
Line 59: Line 52:
** [[/Logging/]]
** [[/Logging/]]
** [[/Test-First Programming/]]
** [[/Test-First Programming/]]
* Ch. 4: Software testing
* '''Ch. 5: Software maintenance'''
** [[/Testing/]]
* Ch. 5: Software maintenance
** [[/Refactoring/]]
** [[/Refactoring/]]
* Ch. 6: Software configuration management
** [[/Version Control/]]
** [[/Version Numbers/]]
** [[/Distribution/]]
* Ch. 7: Software engineering management
* Ch. 8: Software engineering process
** [[/Software Development Methodology/]]
*** [[/Iterative and Incremental Development/]]
* Ch. 9: Software engineering models and methods
* Ch. 10: Software quality
* Ch. 11: Software engineering professional practice
** [[/License/]]
* Ch. 12: Software engineering economics
* Ch. 13: Computing foundations
* Ch. 14: Mathematical foundations
* Ch. 15: Engineering foundations


== [[/Sources/]] ==
== [[/Sources/]] ==

Latest revision as of 15:32, 10 May 2023

Introduction

This is a collection of notes on software development. Its main purpose is to help me raise my development's level of professionalism. It also gives me a place to air an opinion or two.

To give you an idea of my background, after some BASIC programming in my childhood and a break of many years for other interests, I returned to hobby programming just after undergrad and was able to make it my living several years later in 2006. That phase of my developer life started with Perl, and since then I've moved on to Python and XSLT. I've worked mainly in the area of text processing. JavaScript and PHP have played intermittent supporting roles for occasional web development or InDesign scripting. My projects have all been either solo or with a very small team. It's all been on Windows and mostly for the command line.

Topics

As a way to organize my notes and make sure I don't miss anything important, I'll use the structure of IEEE's Guide to the Software Engineering Body of Knowledge (SWEBOK). It's a standard that overviews the entire field and forms the basis for creating things like curricula and certifications. You can download the PDF for free.

The items under the SWEBOK knowledge areas in the first level link to my notes on each topic. I've sorted the knowledge areas to approximate my preferred order, though I'll address them more haphazardly.

Sources

See the article linked in the heading for a list of code examples and other sources I'm drawing from.

<disqus/>

Retrieved from "https://www.thinkulum.net/w/index.php?title=Software_Development&oldid=459"