The System Requirements Specification (SRS) document describes all data, functional and behavioral requirements of the software under production or development.
19 items found
Start your requirements gathering with this all-inclusive document outlining the entire process from start to finish.
How well are your project's IT service objectives meeting the needs of the end users? Find out by asking them to rank each service objective on its merits.
User stories can help you efficiently and effectively describe what knowledge management should look like for your unique organization. This template provides insight on how to use user stories to help you define your KM universe.
How does a deployment plan for Siebel look? Just like this example, showing when, where and how the new Siebel system will be rolled out to users and clients.
When developing a new system, you'll have to interview the future users and ascertain their requirements for the system. This form walks you through the process.
If you are developing an application for users, it helps to know what your basic business requirements are before you begin extensive analysis and design. This form will help you document them.
Are you developing a billing system for your client? You've defined your business requirements and information architecture and must now report back to Management on the project status. Here's a model executive summary report.
Are you about to select a commercial Relationship Management application? State exactly what you need. This thoroughly constructed sample RFI to solicit application package information from vendors will save you hours of work. Modify it to suit your requirements.
User involvement is key to designing an effective application and a good user interface. Give the business users a template of standards and procedures to follow so that they can describe how they do their work, including workflow, and thus how the application should work for them.