Software Engineering

127
7.2 
Step 2: Requirement analysis and specification
interactions, data storage and retrieval, data analysis, and report generation. Ease 
of use, errorless data processing, and intuitive interactions are the primary concerns 
of end users. Real-time systems, which control larger systems involving hardware 
components, are concerned with systems operations, failure modes, and graceful 
degradation of system performance, warning mechanisms, and corrective actions 
when system operations encounter adverse conditions.
Software implementation
 is the organization responsible for translating structural 
unit specifications of the physical architecture into software unit designs, coding 
and testing these code segments, and conducting software component integration 
and testing. It provides representatives to the SWE-IPT to offer insight into the soft-
ware implementation issues and concerns inherent with the evolving architecture.
Software test and evaluation
 represents the organization responsible for estab-
lishing the software product and post-development process test plans and proce-
dures. It provides representatives to the SWE-IPT to offer insight into the test issues 
and concerns inherent with the evolving architecture. It also ensures that software 
requirements are properly stated to provide a complete, consistent, and affordable 
testing strategy; conducts software dry-run and acceptance testing; and performs 
software quality assurance inspections to ensure adherence to software develop-
ment plans, procedures, and guidelines.
Post-development sustainment
 represents the organizations responsible for defining, 
designing, implementing, and qualifying post-development processes. Qualification of 
these processes is a test and evaluation exercise that ensures that the processes are suf-
ficient to facilitate anticipated post-development activities in an effective and efficient 
manner. These organizations provide representatives to the SWE-IPT to contribute 
insight into post-development issues and concerns inherent with the evolving software 
product architecture. This organization involves staff members proficient in software 
distribution, software training, and software support subject matter.
The various stakeholders have different, often competing interests, needs, and 
expectations that must be addressed by the software engineering effort. This diverse 
set of interests creates design challenges that might necessitate the conduct of 
trade-off analysis to be resolved. Stakeholder needs and expectations must be trans-
lated into a set of requirements for the software product and post-development pro-
cesses. These requirements are documented as one or more specifications against 
which the software architecture and testing program will be developed. The require-
ments specifications should not be baselined (placed under configuration control) 
until the requirements are nonvolatile and determined to be achievable within pro-
ject cost and schedule objectives.