The Project Requirements Document (TEAM PROJECT)

Need your ASSIGNMENT done? Use our paper writing service to score better and meet your deadlines.

Get 15% off your first order! Use our special coupon "GET15"

Order a Similar Paper Order a Different Paper

The Project Requirements Document (TEAM PROJECT)

The Principles of Project Management

Place an order on this paper or different paper and we will take care of it. You won’t have to worry about the quality and deadlines

Get Started Now


Edward Kleinert

Executive Summary

In this project, we are going to make a graduation celebration complete with in person and virtual options of participation, musical acts, virtual souvenirs for those that can’t make it. The graduation ceremony is a significant signal showing that students will start their career life, also, a brief review about their school achievements. In addition to that, a successful graduation ceremony will be helpful for prompting university. Our project involves conducting market research, carrying out a feasibility study,receiving feedback from stakeholders at the end of this project. The Project Requirements Document (TEAM PROJECT)

The Requirements Document Purpose 

Project Conditions and Characteristics

  • The Solution

Our purpose is to help students celebrate the end of their studies and the beginning of their careers. Also, it is a great chance for showing the university’s power. Our primary stakeholders are the project team, school shareholders, graduates and suppliers, souvenir sellers, musicians and social media.

  • The Solution Functionality

The solution to the project will provide students with career advice after graduation and serve as a publicity tool for the school while it has an impact on recruitment. At the same time, selling souvenirs can save the cost of the university’s budget. It will not only satisfy the university’s needs but also enable the community’s cultural exchange and promote the acceptance of higher education by the whole population. The Project Requirements Document (TEAM PROJECT) 

  • Stakeholder Characteristics

participant stakeholders

  • Project team members.
  • Suppliers including places, equipment, food, souvenirs.
  • Designers and volunteers.
  • IT experts for an online graduation program.

the vested interest stakeholders

  • School shareholders
  • Snacks and souvenir sellers
  • Investors: Funding aims to get screen ads.

the customer stakeholders

  • Graduates and their parents

Community interest stakeholders

  • Environmentalists: Taking concerns to pollution.
  • Community leader: Safety and traffic issues.


  • Social media: Our activities appear on social platforms.


  • Product or Service Functions
  • We will provide career guidance to graduates.
  • We will summarize the learning achievements and experience for graduates.
  • We will provide schools with opportunities to show campus culture.
  • We can promote the development of social education. The Project Requirements Document (TEAM PROJECT) 
  • Assumptions
  • suppliers reduce the price of goods.
  • The situation of COVID-19 is resolved or improved
  • Dependencies
  • All of the list tasks follow finish-start dependency.


Basic requirements

Collect data of graduates: resource-based dependency

Selection of space: resource-based dependency

Find suppliers and volunteers: logical planning dependency

Find investors and IT experts: logical planning dependency



Decoration and testing


  • Constraints
  • COVID-19 and weather will affect attendance.
  • Regulations,Such as:Time and scale limit in order to reduce the risk of traffic jam and noise pollution.The Project Requirements Document (TEAM PROJECT) 

The High Level Scope of the Project 

Detailed Project Requirements

This section of the document lists specific requirements, detailed deliverables (specific products or services) that the project is expected to deliver.  This section lists specific requirements (functional and non-functional) for project.  It may include features, functions, look, feel, design, operations, rules, regulations, policies, procedures, or compliance concerns that must be met.

Requirements may be divided into the following sections:

  1. User requirements. These are requirements written from the point of view of end users, usually expressed in narrative form
  2. System requirements. These are detailed specifications describing the functions the system must be capable of doing
  3. Interface requirements. These are requirements about the user interface, which may be expressed as a list, as a narrative, or as images of screen mock-ups.



  • User Requirements (Functional)

Requirements should be written from the point of view of end-users, expressed in a narrative form.  They should describe the required look, feel, and behavior of the solution(s).  This may come from business rules, policies, procedures, regulations, or law. Discovery typically is through the elicitation sessions with users, stakeholders, and other stakeholders.


  • System Requirements (Non-Functional)

Detailed system requirements (Note: for a systems related (IS/IT) project, which impose constraints on the design or implementation of a system solution, such as performance requirements, security requirements, volume of use requirements, or reliability requirements. The Project Requirements Document (TEAM PROJECT)


Rules for Effective Requirements

Each requirement must form a complete sentence, containing a subject and a predicate.  These sentences must consistently use the verb ‘shall,’ ‘will’ or ‘must’ to show the requirement’s mandatory nature, and ‘should’ or ‘may’ to show that the requirement is optional.  The whole requirement specifies a desired end goal or result and contains a success criterion or other measurable indication of the quality.


  1. Identify and define objectives
  • Explain for what purpose the system is being deployed
  • Qualified objectives identify the desired deliverables
  • The value proposition explains return-on-investment



  1. Verify the requirements against the objectives
  • Validate accurate scope for high-level requirements
  • Assure consistent focus for application rules
  • Provide critical management tools for scope change decisions
  • Verify every iteration of the requirements and design documents


  1. Defining a good requirement
    • Correct (technically and legally)
    • Complete (express a whole idea or statement)
    • Clear (unambiguous and not confusing)
    • Consistent (not in conflict with other requirements)
    • Verifiable (it can be determined that the system or solution meets the requirement)
    • Traceable (uniquely identified and tracked)
    • Feasible (can be accomplished within cost and schedule)
    • Modular (can be changed without excessive impact)
    • Design-independent (do not pose specific solutions on design) The Project Requirements Document (TEAM PROJECT)




Prepared by   __________________________________

Project Manager


Approved by__________________________________

Project Executive Sponsor








Appendices (If applicable):


  • Legal and Regulatory Documents
  • Product Documents
  • Process Documents
  • Requirements Documents. The Project Requirements Document (TEAM PROJECT)

Need your ASSIGNMENT done? Use our paper writing service to score better and meet your deadlines.

Get 15% off your first order! Use our special coupon "GET15"

Order a Similar Paper Order a Different Paper