|
|
This article is sample content outsourced to DocuMaker Communication Solutions. You can get similar content for your own website by outsourcing it here. |
Improving The Development Process
See Also: Recommended Approach To Publishing
This guide is a “spin-off” of NeoBASIC’s Recommended Approach To publication Development and suggests a number of ways to improve the publication development process.
Quoted from NASA’s Software Process Improvement Guide:
“There is an evident need to implement some means by which every software activity provides new and improved insight into continually improving methods for developing and maintaining software; every experience must be used to gain new knowledge.”
Basically, improving publication development requires asking 14 questions:
How Can I Make My publication (or part of my publication)…
- run faster?
- easier to re-create?
- with less code?
- run from memory?
- smaller?
- automatic?
- generate code on its own?
- run from a different and faster programming language?
- easy to customize?
- easy to document?
- compile faster?
- un/install quicker?
- easy to organize and/or manage?
- easy to debug?
- easy to use?
Building upon what we know from NeoBASIC’s Recommended Approach To publication Development, the publication’s Development Plan is where all of the publication’s coding occurs. In this phase of development, the above issues could be addressed while defining the:
- Name of a publication feature and the task it performs…
- Batch DOS Commands a publication will use to read and produce output…
- Batch DOS Commands a publication will use to modify external data…
- Batch DOS Commands a publication will use to store data…
- Batch DOS Commands a publication will use to handle errors…
- Batch DOS Commands a publication will use to hide data…
- Batch DOS Commands a publication will use to perform other tasks…
- Where a feature will be in the publication…
- How the publication feature will be activated…
- What the publication’s interface will look like…
- Documentation’s page number and what it will say…
- Internal NeoBook DOS Pro Command(s) a publication will use (and for what)…
- How a publication will be tested for functionality…
- Other functions…
If you merge these two issues, you’ll come up with a nifty publication improvement process addressing the:
- Name of a publication feature and the task it performs – and considering how to make it:
- run faster?
- easier to re-create?
- with less code?
- run from memory?
- smaller?
- automatic?
- generate code on its own?
- run from a different and faster programming language?
- easy to customize?
- easy to document?
- compile faster?
- un/install quicker?
- easy to organize and/or manage?
- easy to debug?
- easy to use?
- Batch DOS Commands a publication will use to read and produce output – and considering how to make them:
- run faster?
- easier to re-create?
- with less code?
- run from memory?
- smaller?
- automatic?
- generate code on its own?
- run from a different and faster programming language?
- easy to customize?
- easy to document?
- compile faster?
- un/install quicker?
- easy to organize and/or manage?
- easy to debug?
- easy to use?
- Batch DOS Commands a publication will use to modify external data – and considering how to make them:
- run faster?
- easier to re-create?
- with less code?
- run from memory?
- smaller?
- automatic?
- generate code on its own?
- run from a different and faster programming language?
- easy to customize?
- easy to document?
- compile faster?
- un/install quicker?
- easy to organize and/or manage?
- easy to debug?
- easy to use?
- Batch DOS Commands a publication will use to store data – and considering how to make them:
- run faster?
- easier to re-create?
- with less code?
- run from memory?
- smaller?
- automatic?
- generate code on its own?
- run from a different and faster programming language?
- easy to customize?
- easy to document?
- compile faster?
- un/install quicker?
- easy to organize and/or manage?
- easy to debug?
- easy to use?
- Batch DOS Commands a publication will use to handle errors – and considering how to make them:
- run faster?
- easier to re-create?
- with less code?
- run from memory?
- smaller?
- automatic?
- generate code on its own?
- run from a different and faster programming language?
- easy to customize?
- easy to document?
- compile faster?
- un/install quicker?
- easy to organize and/or manage?
- easy to debug?
- easy to use?
- Batch DOS Commands a publication will use to hide data – and considering how to make them:
- run faster?
- easier to re-create?
- with less code?
- run from memory?
- smaller?
- automatic?
- generate code on its own?
- run from a different and faster programming language?
- easy to customize?
- easy to document?
- compile faster?
- un/install quicker?
- easy to organize and/or manage?
- easy to debug?
- easy to use?
- Batch DOS Commands a publication will use to perform other tasks – and considering how to make them:
- run faster?
- easier to re-create?
- with less code?
- run from memory?
- smaller?
- automatic?
- generate code on its own?
- run from a different and faster programming language?
- easy to customize?
- easy to document?
- compile faster?
- un/install quicker?
- easy to organize and/or manage?
- easy to debug?
- easy to use?
- Where a feature will be in the publication – and considering how to make it:
- run faster?
- easier to re-create?
- with less code?
- run from memory?
- smaller?
- automatic?
- generate code on its own?
- run from a different and faster programming language?
- easy to customize?
- easy to document?
- compile faster?
- un/install quicker?
- easy to organize and/or manage?
- easy to debug?
- easy to use?
- How the publication feature will be activated – and considering how to make it:
- run faster?
- easier to re-create?
- with less code?
- run from memory?
- smaller?
- automatic?
- generate code on its own?
- run from a different and faster programming language?
- easy to customize?
- easy to document?
- compile faster?
- un/install quicker?
- easy to organize and/or manage?
- easy to debug?
- easy to use?
- What the publication’s interface will look like – and considering how to make it:
- run faster?
- easier to re-create?
- with less code?
- run from memory?
- smaller?
- automatic?
- generate code on its own?
- run from a different and faster programming language?
- easy to customize?
- easy to document?
- compile faster?
- un/install quicker?
- easy to organize and/or manage?
- easy to debug?
- easy to use?
- Documentation’s page number and what it will say – and considering how to make it:
- run faster?
- easier to re-create?
- with less code?
- run from memory?
- smaller?
- automatic?
- generate code on its own?
- run from a different and faster programming language?
- easy to customize?
- easy to document?
- compile faster?
- un/install quicker?
- easy to organize and/or manage?
- easy to debug?
- easy to use?
- Internal NeoBook DOS Pro Command(s) a publication will use (and for what) – and considering how to make them:
- run faster?
- easier to re-create?
- with less code?
- run from memory?
- smaller?
- automatic?
- generate code on its own?
- run from a different and faster programming language?
- easy to customize?
- easy to document?
- compile faster?
- un/install quicker?
- easy to organize and/or manage?
- easy to debug?
- easy to use?
- How a publication will be tested for functionality – and considering how to make it:
- run faster?
- easier to re-create?
- with less code?
- run from memory?
- smaller?
- automatic?
- generate code on its own?
- run from a different and faster programming language?
- easy to customize?
- easy to document?
- compile faster?
- un/install quicker?
- easy to organize and/or manage?
- easy to debug?
- easy to use?
- Other functions – and considering how to make them:
- run faster?
- easier to re-create?
- with less code?
- run from memory?
- smaller?
- automatic?
- generate code on its own?
- run from a different and faster programming language?
- easy to customize?
- easy to document?
- compile faster?
- un/install quicker?
- easy to organize and/or manage?
- easy to debug?
- easy to use?
After analyzing and (hopefully) coming up with some solutions to these issues, you’ll have one more very important question to ask. This question should be addressed to each individual solution: How can my solution be used over and over again on new development projects?
In the beginning, when you start this “improvement” process, you’ll probably notice that the “process of creating a process” slows you down and doesn’t seem to be much of an improvement at all. However, as you create a solution for each issue and mold the solution in such a way that it can be re-used on future publications, later development will subsequently become faster and easier as long as your solutions are incorporated into the projects.
Current Keyword: IMPROVEMENT
improve, improvement, improving development, improving programming, improving software
