Software Engineering

154
CHAPTER 8 
Software Requirements Analysis Practice
Distribution may be done via in-house shipping resources, external postal ser-
vices, or through the Internet. Internet distribution will require some effort to 
prepare, test, and monitor website activity that permits access to the electronic dis-
tribution packages, as well as providing electronic payment methods.
Installation may be done at the customer’s operational location to properly con-
figure the computing environment to achieve the best software performance, or it 
may be installed by the organization’s network administrator. Commercial software 
installation packages may be used, and some effort will be required to prepare and 
verify that the installation package works properly on a variety of computer envi-
ronments and with a range of operating systems.
Training delivery methods must be determined and specified to incorporate the 
cost associated with end-user training as part of the software deployment strategy. 
The common forms of training methods involve: (1) hands-on, instructor-led class-
room training, where an instructor shows users how the software works and how 
to perform common tasks; (2) group demonstration seminars, where an instructor 
shows users how the software works and how to perform common tasks in a live 
demonstration; (3) computer-based training (CBT), which allows end users to com-
plete interactive lessons that walk them through the process of performing common 
tasks, and the interactive software tests them on their performance and understand-
ing; and (4) book-based training, where end users complete workbook lessons in 
how to perform common tasks, often illustrated with screenshots. Whichever train-
ing method or combination is selected, the requirements for product training must 
be specified. This involves identifying the set of user documentation and training 
materials that must be developed and available at the software deployment readi-
ness review.
Support processes involve help-desk operations, problem reporting, tracking, 
resolution, software patch deployment, and software enhancement development. 
The establishment of the organizational capability to perform each of these pro-
cesses must be planned and developed to support the software deployment readi-
ness review. This may involve the transition of software development (engineering, 
implementation, and testing) equipment and CASE tools to the sustainment organi-
zation. An inventory of items to be transitioned must be addressed by the software 
requirements specifications to provide a basis for post-development planning.