A
Software Requirements Specifications (SRS) document contains functional and nonfunctional requirements
only; it outlines what the development team understands the client’s
project system requirements to be. Foreground Image’s requirements
gathering team will include programmers, product marketers, systems
analysts/architects, a project manager, and a technical writer
as needed to put the compiled information together in easily
understandable terms with precise information. An SRS provides
an assurance that the development organization understands the
issues or problems to be solved and the software behavior necessary
to address those problems.
Composed in an easy-to-understand format, the SRS document organizes
information, establishes boundaries around the system and categorizes
each component in an organized way. Because the SRS document
serves as a parent document to further documents, it should include
sufficient functional system requirement details to develop a
design solution.
Questionnaires, Surveys, Interviews and Return-on-investment
(ROI) analysis may be some of the information gathered together
initially
The SRS document is composed after this information has been
gathered and analyzed. Some of the information included is:
• Overall Description
• External Interface Requirements
• System Features
• Other Nonfunctional Requirements
Proposal Analysis document
The Proposal Analysis provides an independent confirmation check
of the resources and time-scales of the project. The analysis
emphasizes the proposed resources and time-scale.
The objective of the analysis is to produce and report a systematic
and supportable feasibility judgment. The feasibility judgment
will determine if the proposed complexity of software and functionality
can be developed to the requirements for the quoted resources
and time-scales.
Purpose of the Software Development Project Plan
The Software Development Project Plan provides the action plan
for developing the software, and tells how the work will be carried
out. It includes schedules, project plans, commitments, and resource
allocations. The Software Development Project Plan describes
the process for designing, implementing, documenting, and testing
the final software product.
The foreground analytical plans and documents provide benchmarks
that are used to generate the Contract Execution document.
Contract Execution document
The development
process proceeds from need analysis, to user and task analysis,
to functional analysis, to function / task allocation, to requirements
analysis, to setting usability goals, to designing the interface,
with review by the client at each stage.
Good communication at the outset of any new project is essential.
Job expectations must be clearly set forth at the beginning
of the project. The Contract Execution document outlines estimated
delivery dates, payment schedules and revision compensation.
|
