The concept sets the context for requirements specifications, and (typically) includes items as listed:

1) A vision statement of the basic idea for your term project What is the concept for the application and what will it do?

2) Rationale supporting the vision statement What is the need and market for the application/system?

3) A listing of the stakeholders who will be involved Who are the potential users (for example an application for Sheridan would have stakeholders of the school, the administration, IT department and students)

4) A list and explanation of any assumptions you are making: This can include the existence of similar applications Initial marketplace analysis.

5) Where and how the application will be used. The vision statement and rationale should state the problem you intend to solve (i.e., the need that a set of target users have), and the general characteristics of the proposed solution. The stakeholders should include but are not limited to the "target users". Assumptions could deal with issues such as characteristics of the users, projections for technology availability, and how and where the technology is to be used. Also, state if there is any existing application or technology artifact that can bias users or influence the design or concept