1.1.
Nonfunctional Requirements
The system will have user friendly user interface where the user will feel comfortable
using it
It will not be very colorful or boring it will be indeterminate for the better of the
user.the system also security system which it will have its own authentication and
error handling methods that Is efficient to protect the users data.the hardware
consideration in minimum because it is web based so it will work on any computer
with internet access.
1.1.1. User Interface and Human Factors
The university logo and the current basic design of registration system should be
displayed. The system should be attractive according to the university-level students.
The design and the color should make users feel comfortable when using the system
instead of flashing useless colors on the screen. The design should also reflect the
universities environment.
The overall style should be built up easily in order for users to use it easily and
efficiently. After accessing the system, the users should feel comfortable while
looking at it and browsing through it. The design should not be too colorful to
maintain a certain seriousness of the web design of the college but at the same time it
should not be too boring for the eye, so that it can appear pleasant to use.
The system should have an easily understandable design in order for users to use it. It
should provide the necessary information when the user commits possible errors. It
should indicate the several possibilities that the user has to go on in using the system.
The user will be allowed to undo any of the operation computed or, for irreversible
operation, will always be asked to double-check their choice in case they
misunderstood the option or clicked on a button by accident. The system will have
easy access to help center whenever the user needs any kind of assistance.
Hardware Consideration
The product is Web based therefore it will be used in any environment that allows
Web access.
For the system to successfully operate the registration system should be integrated
with other IT services and the internet portal.
1.1.2. Security Issues
Everyone (stakeholders and guests) can have access to the system and the catalogue.
Every student must have secure and private access to his/her data. The CPE and the
registrar can have access to every part of the system.
Data integrity should be assured by limiting access to the database and by appropriate
synchronization, and back-up functionalities.
The system will provide a protection of the database such as the one that the
university already provides. However, the system will have to increment this level of
protection because of the personal data made available on the system, and the larger
share of people that will be having access to it through the online registration. The
users’ privacy will be granted by the limited access that the log-in process is going to
give to the database. Also, the system does not grant direct access to the database
itself. Stakeholders who need to access the database will have to access it from a
source independent from the registration system.
The system will develop a security system that will reduce to the minimum the
possibility of corruption from systems and/or humans
1.1.3. Performance Consideration
The system is required a fair amount of speed especially while browsing through the
catalogue and presenting different possibilities for the schedule. The outcomes of the
product are not directly influenced by its speed, because all the operations are linked
to each other and one operation can not be computed before the one causing it.
When the system is disconnected or frozen due to over access at the same time, it
should save all the process of the users have made up to the point of abnormal
happenings. When the users log in with the same id, all the work should be provided.
The system should be able to manage all the information incoming from the database
and the catalogue.
1.1.4. Error Handling and Validation
The product will have its own validation technique where the user will be asked to
insert necessary information which used to check for his eligibility if the person is
qualified he will be allowed to access the system but if he is not then the system will
not allow the man to enter the system. with related to error handling the user will be
aware to take caution when inserting data and if he makes a mistake he will be able to
correct it.
1.1.5. Quality Issues
The reliability of the system is directly linked to the level of update of the documents
to which it is correlated, such as the catalogue or the students’ database.there for it
should be seen time after time for a defect.
The availability of the system is 24/7 to students who want to register with in the dead
line.
1.1.6. Backup and Recovery
As stated above the system should be updated with specific time to find any
incompatibility and to correct it in time.the system will have feature where the data
will be restored to the initiation of the update if any error occurred.
And additionally we will have additional database where the users data will be stored
and which have no any relation with the currently updating database so if any error
occurred we can get the prior data set with ease.
1.1.7.
Physical Environment
The system will be deployed with in the university where it is the main place the
registration will take place so that the coordinators can see it.
1.1.8. Resource Issues
As far as now there is no constraint on the resource the system will work on the
same hierarchy as the manual system work.there the resources are enough to go with.
1.1.9. Documentation
The level of documentation gathered from the offices that work on registration the
offices include CEP,Registration Directorate, the departments and also the college.the
development process is also documented in case it is needed for technical
maintenance.