DOCUMENTS REQUIRED FOR
SOFTWARE PROJECT
The software requirements document is a written
statement of what the software will do.
What the software does is directly perceived by its
users – either human users or other software systems
You and the users must agree on actions they can
perform and response they should expect.
The main purpose of a requirements document is to serve
as an agreement between the developers and the customers on what the
application will do.
It does not state how the software will do it.
No technical expert is required for designing this
document.
This document is sometimes also deled by legal team of
the company and user.
ADVANTAGES
The customers can see early on if their needs will be
met ·
The developers
can estimate the effort involved in creating the application ·
The development
project leader has a basis for a project plan ·
The quality
assurance people have a basis for testing the application
SYSTEM DESIGN DOCUMENT
System design is a process by
which the software requirements
are translated into
a representation of
software components, interfaces,
and data necessary for
the implementation phase.
Features Software
Architecture and Design Documentationg
The Software Design
Document (SDD) captures the design of a system
At minimum, create
a document describing the software architecture of a system (or be able to
produce the document from a tool)
You may package it
into a separate document called Software Architecture Document
A reasonable size
for a Software Architecture Document for even a large system is 50-100 pages
International standard followed for writing
system/ architecture document is IIEEE Std. 1471
BASIC WEB ARCHITECTURE
The web is a two-tiered architecture.
A web browser display information content.
And a web server that transfer information to the
cilent..!
No comments
Post a Comment