- Project tools
- How do I...
|Over 500 more tools...
Software Requirements Specification
Process impact: The SRS
precisely defines the software product that will be built. Decisions
made in writing the SRS are based on information in the project proposal and user needs documents. The SRS sets
requirements that must be satisfied by the system design. The SRS is verified and
validated by activities outlined in the QA
M-and-S provides an interface to create, manage and developp any
types of projects that need human and technical resources and that is related to
a real need in the society.
The first release will provide a framework to initiate a new
project and provide participants with the minimal tools to follow the
development of it and collaborate with other members: editing documents
related to his particular skill, collaborate with other members of the
project in which he participates.
For more information, see the project proposal.
ONE PARAGRAPH OVERVIEW
ONE PARAGRAPH OVERVIEW
- The feature set lists all
features in an organized way.
TODO: Describe the non-functional requirements for this release.
Some examples are provided below.
- What are the usability requirements?
Our main criteria for making the system usable is the difficulty
of performing each high-frequency use case. Difficulty depends on
the number of steps, the knowledge that the user must have at each
step, the decisions that the user must make at each step, and the
mechanics of each step (e.g., typing a book title exactly is hard,
clicking on a title in a list is easy).
The user interface should be as familiar as possible to users
who have used other web applications and Windows desktop
applications. E.g., we will follow the UI guidelines for naming
menus, buttons, and dialog boxes whenever possible.
- What are the reliability and up-time requirements?
- What are the safety requirements?
- What are the security requirements?
Access will be controlled with usernames and passwords.
Only adminstrator users will have access to administrative
functions, average users will not.
- Passwords must be 4-14 characters long
- We will not use encrypted communications (SSL) for this website
- What are the performance and scalability requirements requirements?
- What are the maintainability and upgradability requirements?
Maintainability is our ability to make changes to the product
over time. We need strong maintainability in order to retain our
early customers. We will address this by anticipating several
types of change, and by carefully documenting our design and
Upgradability is our ability to cost-effectively deploy new
versions of the product to customers with minimal downtime or
distruption. A key feature supporting this goal is automatic
download of patches and upgrade of the end-user's machine. Also,
we shall use data file formats that include enough meta-data to
allow us to reliabily transform existing customer data during an
- What are the supportability and operability requirements?
Supportability is our ability to provide cost effective
technical support. Our goal is to limit our support costs to only
5% of annual licensing fees. The product's automatic upgrade
feature will help us easily deploy defect fixes to end-users. The
user guide and product website will include a troubleshooting guide
and checklist of information to have at hand before contacting
Operability is our ability to host and operate the software as
an ASP (Application Service Provider). The product features should
help us achieve our goal of 99.9% uptime (at most 43 minutes
downtime each month). Key features supporting that are the ability
to do hot data backups, and application monitoring.
- What are the business lifecycle requirements?
The business lifecycle of a product includes everything that
happens to that product over a period of several years, from
initial purchase decision, through important but infrequent use
cases, until product retirement. Key lifecycle requirements are
- Customers must be able to manage the number of licenses that
they have and make informed decisions to purchaes more licenses
- The product shall support daily operations and our year-end
- The customer data shall be stored in a format that is still
accessible even after the application has been retired
TODO: Describe the environmental requirements for this release.
Environmental requirements describe the larger system of hardware,
software, and data that this product must work within. Some
examples are provided below.
- What are the system hardware requirements?
- What are the system software requirements?
- What programmatic interfaces must be provided?
- What are the data import and export requirements?
- We will store all data in a standard SQL database, where it can be accessed by other programs.
- We will store all data in an XML file, using a standard DTD.