Business Analysis Templates & Aides


Recent Templates | Categories | Search | Subscribe (RSS)

Business Case Methodology Template

16418 Views // 3 Comments // Article Rating
Business Case Methodology Template

This was created by the State of South Carolina and outlines a framework used to asses cost, benefits, and risks of proposed information technolog projects.

The purpose of this document is to provide guidelines for use by agencies in developing a business case justification for Major, Enterprise and Multi-agency projects in this standard format.

View Details

Volere Atomic Requirements Template

16733 Views // 3 Comments // Article Rating
Volere Atomic Requirements Template

The Volere Snow Card is a great way to capture the various attributes of a specific (atomic) requirement. Print this out and use it in your own requirements gathering workshop.

View Details

Volere Stakeholder Analysis Template

18313 Views // 4 Comments // Article Rating
Volere Stakeholder Analysis Template

This template helps you to identify the stakeholder roles, the representative(s) of each role and the type(s) of knowledge that you need from them for your given project.

View Details

Karl Wiegers' Software Requirements Specification (SRS) Template

25159 Views // 9 Comments // Article Rating
Karl Wiegers' Software Requirements Specification (SRS) Template

This Software Requirements Specification (SRS) Template created by Karl Wiegers allows you to capture the software requirements for a given software product/system.

View Details

Volere Communication Analysis Template

9747 Views // 4 Comments // Article Rating
Volere Communication Analysis Template

The Communication Analysis template/spreadsheet is a starting point for identifying people who need to talk directly to each other. The spreadsheet contains some common roles. You can replace these roles with the roles relevant to your project.

View Details

Volere Prioritization Template

12107 Views // 0 Comments // Article Rating
Volere Prioritization Template

One common issue with requirements is that there are always too many of them. So there has to be some way of choosing which ones will be implemented in which versions of the product. You can use a prioritization spreadsheet to priorities the requirements.

View Details
Page 10 of 10First   Previous   5  6  7  8  9  [10]  Next   Last   


Upcoming Live Webinars



Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC