2. Requirements

The system has three stakeholders as follows:

Students

Second-year Computer Science students enrolled at the University of Bristol who take the Software Product Engineering unit as part of their course and work for a project requested by a real client. A use-case diagram for a student is provided at the OO Design & UML section.

Functional goals for students include being able to display a list of project briefs and to refine it via tags, access each page of a specific project, access a dashboard page where they can select and edit their choices, and send or receive messages from the client they work with once project allocation is done. After the allocation into teams takes place, they can no longer view other projects apart from their own.

Lecturers

The lecturers for the Software Product Engineering unit whose duties include student allocation to projects, in addition to the management and assessment of the unit. A use-case diagram for a lecturer is provided at the OO Design & UML section.

Functional goals for lecturers include being able to delete or approve submitted projects, view all projects at any time, view the preferences of each student, allocate students to teams, view messages within each team and edit teams even after student allocation in case a student gets removed from a group.

Clients

Organisations that submit projects for which the students work. A use-case diagram for a client is provided at the OO Design & UML section.

Functional goals for clients include being able to register an account via an online form, submit multiple projects up to a certain limit (to prevent scamming), modify submitted project at any time, and send or receive messages to the whole student team.

Overall, the requirements can be listed as following:

• Importance
• • Stakeholder
• • • Description
• Essential
• • All
• • • Ability to access each webpage within 3 clicks
• Optional
• • All
• • • Responsive website
• Essential
• • All
• • • A consistent theme throughout the website limited to 4 colours and 2 font faces
• Essential
• • All
• • • Ability to register on the website
• Optional
• • Student
• • • Ability to sign in via Single Sign-on
• Optional
• • Lecturer
• • • Ability to sign in via Single Sign-on
• Essential
• • Student
• • • Ability to view the list of all project briefs until allocation
• Essential
• • Student
• • • Denial of access to the other projects once allocation is made
• Essential
• • Student
• • • Ability to view each project brief separately until allocation
• Essential
• • Student
• • • Ability to select and edit project preferences
• Optional
• • Student
• • • Ability to filter and sort the project briefs by tags and number of applicants respectively
• Essential
• • Student
• • • Ability to view the allocated project
• Essential
• • Students
• • • Ability to message the client
• Optional
• • Student
• • • Dashboard page with a calendar and deadlines
• Essential
• • Lecturer
• • • Ability to approve or delete the submitted projects
• Essential
• • Lecturer
• • • Ability to view all project briefs at any time
• Essential
• • Lecturer
• • • Ability to view the preferences of each student
• Optional
• • Lecturer
• • • Automated student allocation into teams and projects
• Essential
• • Lecturer
• • • Ability to view the project and the messages of each team
• Optional
• • Lecturer
• • • Ability to edit teams at any time
• Essential
• • Client
• • • Ability to register by completing an online form, providing basic details such as company name and contact information
• Essential
• • Client
• • • Ability to submit multiple project briefs into the website through a form
• Optional
• • Client
• • • Submission form with dropdowns/checkboxes/fields
• Essential
• • Client
• • • Ability to modify the project briefs after submission
• Optional
• • Client
• • • Ability to upload multiple project briefs as a file such as pdf
• Essential
• • Client
• • • Ability to send and receive messages from the student team