Docsity
Docsity
Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity

Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips
Guidelines and tips
Sell on Docsity
Sell on Docsity
Docsity AI
Docsity AI
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

Requirement Document Template for CS 389, Spring 2005, Papers of Software Engineering

Pace UniversitySoftware Engineering

A template for a requirement document designed for cs 389, spring 2005. It consists of 11 sections, including an introduction, description of the environment, targeted problem, vision of the software product, risks analysis, classes of stakeholders, assumptions and constraints, functional and non-functional requirements, dependencies, requirement engineering process, and references. Guidelines for creating requirement ids, prioritizing requirements, and testing requirements.

Typology: Papers

Pre 2010

Uploaded on 08/09/2009

koofers-user-fux
koofers-user-fux 🇺🇸

9 documents

1 / 3

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Requirement document Template
Version: 2/19/05
History:
Version 2/17/05 modified: Section 5 is “Risks Analysis” instead of “Risk”
This document is a template of requirement document designed for cs 389,
Spring 2005. It is composed of the 11 sections described below.1
1. Introduction
Purpose of this document
This is a requirement document…
It was realized…
(See section 1.1. p 469 of the Microsoft template)
2. Description of the environment
Who is the client2 (the person(s) paying and owner of the delivered software product.)?
Who is the customer (the person who will buy the software product)?
Who will develop the software? How?
Where the system will be used (country, organization, technical environment…)?
Will the system interact with existing systems?
…
3. Description of the targeted problem
Why is the software being developed?
4. Vision of the software product that is being developed
Vision of the solution (vision statement and major features of the software product)
5. Risks Analysis
What are the risks involved in the development of the software product?
Use the paper: Linda Wallace and Mark Keil. Software project risks and their effect on
outcomes. Communications of the ACM, April 2004, vol. 47, no. 4. On p. 72, threre is a
list of project risk factors.
1 You can use your own font, font style, font color… You will not use double-spaces.
2 We will use these definition for ‘customer’ and ‘client’ now on.
pf3

Partial preview of the text

Download Requirement Document Template for CS 389, Spring 2005 and more Papers Software Engineering in PDF only on Docsity!

Requirement document Template

Version: 2/19/ History: Version 2/17/05 modified: Section 5 is “Risks Analysis” instead of “Risk” This document is a template of requirement document designed for cs 389, Spring 2005. It is composed of the 11 sections described below.^1

1. Introduction Purpose of this document This is a requirement document… It was realized… (See section 1.1. p 469 of the Microsoft template) 2. Description of the environment Who is the client^2 (the person(s) paying and owner of the delivered software product.)? Who is the customer (the person who will buy the software product)? Who will develop the software? How? Where the system will be used (country, organization, technical environment…)? Will the system interact with existing systems? … 3. Description of the targeted problem Why is the software being developed? 4. Vision of the software product that is being developed Vision of the solution (vision statement and major features of the software product) 5. Risks Analysis What are the risks involved in the development of the software product? Use the paper: Linda Wallace and Mark Keil. Software project risks and their effect on outcomes. Communications of the ACM, April 2004, vol. 47, no. 4. On p. 72, threre is a list of project risk factors. (^1) You can use your own font, font style, font color… You will not use double-spaces. (^2) We will use these definition for ‘customer’ and ‘client’ now on.

6. Classes of stakeholders Client, customer, users, other stakeholders (technology experts, marketing experts, databases experts, domain experts, legal experts…) 7. Assumptions, dependencies, constraints Assumptions that the team is making about the project and the software product that is being developed (law, policy, technical assumptions, time assumptions…) Things you cannot change and have to work around Things you do not know but just assume 8. Requirements  You will design your own templates to describe the requirements. Suggested contents are offered below (you may add other contents.) The Microsoft and Volere^3 templates were presented in class, and are available in the Blackboard.  Requirement IDs will be unique (e.g. R1, R2…)  Requirements have to be prioritized. Assign ranks P1, P2, P3 and P4 where P1 is the highest priority. You can also use MoSCoW or Low/Medium/High. 8.1. Functional requirements The functional requirement description will contain the following content:  Requirement ID  Requirement name  Requirement description – A two or three sentence statement of the intention of the requirement  Users – who have access to the described feature  Source – who raised this requirement?  Priority  How to test the requirement – provide a test case 8.2. Non-functional requirements The non-functional requirement description will contain the following content:  Requirement ID  Requirement name  Requirement description  Source  Priority  How to test the requirement (^3) There is a part on cultural and political requirements in the Volere template (p. 56) that may be useful for you to read.