For the users we have installation,
usage, and troubleshooting guides as well as the ever-present Frequently
Asked Questions (FAQ).
Roadmaps: Software development is rarely a single project with a set goal.
More often the software itself goes through a series of versions or releases,
which can be translated to a series of connected projects (for each release)
or an open-ended one. Roadmaps allow us to share??”communicate??”these
plans with both our developers and users.
???
???
Understanding the Problem
[ 10 ]
Error Reports: No software is perfect??”no matter how much its developer
likes to claims it is! ??”and so we need a mechanism for our testers and users
to report faults and errors to us so that they can be managed. Capturing
error reports is not the end result though. We must also ensure that they are
managed so they can be resolved to both our and the reporter's satisfaction.
Requirements: These could come directly from a user in the form of a feature
request, or we could determine that a particular error report requires us to
change our software. Irrespective of how we receive or capture them, they
need to be managed in the same manner as error reports.
Revision Control: Revision control allows us to store all files related to a
particular software development project.
Pages:
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29