

Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
The functional and non-functional requirements for a university student record system. Topics include user interface design, data input and output, payment processing, research capabilities, and system responsibilities. The system should be user-friendly, text-based, and incorporate multiple features such as automated reporting and email facilities.
Typology: Exercises
1 / 2
This page cannot be seen from the preview
Don't miss anything!


The syste
St La Th In Pa R lin
Nonfunct
Su R Ex St
The syste
Ea A M In In M
m should do
tudent record aboratory adm he ordering o nput and outp ayments mad esearch cont nked to a wid
ional require
ub‐systems sh ange of users xpanded to h traightforwar
m should do
asy‐to‐use us text‐based, c Mixed text and ncorporate an ncorporate kn Multiple confe
this:
ds ministration of goods and s put payments de for teachin ract reporting der University
ments are
hould be auto s to be suppo andle future, rd user interfa
this:
ser interface command lan d graphics sho n electronic m nowledge of p erences shoul
services s ng assistants g y system resp
omatically lin rted is very w , unforeseen ace
nguage interfa ould be suppo mail facility particular role d be support
onsible for st
ked wide tasks
ace is not acc orted
es and individ ed
taff salaries
ceptable
duals in the syystem
Nonfunct
So U Po
ional require
ome individu ser communi ortable to wo
ments are
als only being ity is a closed orkstation
g concerned w d one
with particulaar conferencees