2.2
Specification of the needs (functional and non functional)
A requirements specification should provide precise, measurable
and unambiguous details about what the product must give out in general,
without providing unnecessary constraints or suggesting possible solutions.
2.2.1 Functional needs
Functional requirements express an action that performs the
system response to a request (which outputs are produced for a given
set Input).
Our esprit knowledge base should provide all these
features:
§ Functionalities of Adding, updating and deleting
user, block accounts of some users for a defined duration
§ Uploading / downloading updating and delete
documents receives by privileged user
§ list of all documents in a sorted way: show library
§ Adding, updating, deleting and shows the list of
questions and its appropriate answers or
comments and users that makes it..
§ Display / update knowledge Scoreboard of teachers
§ Space to post announcements in the home page (seminars
-training...)
§ organize training
§ post testes in the provided space in the platform
§ download students copies
§ Send the corrected review for registered students.
§ register for training
§ Register to pass online test
§ Shows the personnel file of a user: all the registered
elements of the file must be displayed.
§ Search engine for documents by title / author / subject
/code.
§ Add / remove and count points: for each answer
/comment...
And other functionalities will be presented and explained in the
textual description part.
2.2.2. Non functional needs
All information systems with a certain point in their life cycle
must be considered non-functional requirements and testing. For some projects
these needs will require a very important work and other project areas a quick
check will suffice.
§ security
§ usability
§ reliability
§ interoperability
§ scalability
§ Performance requirement
§ Hardware
§ Deployment
Security needs: Our
application should
§ Contains interface for connection and verify if generated
information are correct.
§ Each user is classified with his
appropriate privileges: each registered user who
will be connected has its own interface.
§ Can define the possible levels of access to system for
system users and external systems.
Ex: Any confidential information provided
by clients will be encrypted with an encryption algorithm
§ Logout after idle time of inactivity or after three false
passwords.
Usability needs:
§ refer to general aspects of the interface Users Eg
standard used
§ Definition of the minimum browser (Web application)
Simplicity: A clear and simple user
interface to handle.
Performance needs: Describe the
execution performance of the system, generally in terms of response time.
§ (web) Download page time: Loading a webpage in the browser
should not take more than 15 seconds in normal condition.
§ Response time: the application loads, opening
times and screen refresh, etc.
§ Processing time- functions, data exports.
§ Initial load time and load data: Interrogation of the
database
Capacity requirements
Memory (Storage) - how much information should the system be able
to store?
Needs of availability /
reliability:
Related to the level of availability that must be
explicitly defined for critical applications
Ex availability requirement
24/24, 7 / 7 except during maintenance (specify
...)
Compatibility
§ Material needs
-define the minimum hardware necessary
to operate the system
§ Compatibility on different operating systems - on which
he should be able to function?
§ Compatibility on different platforms - What are the
hardware platforms to work?
Ergonomics
The ergonomics standards-User Interface, the density of elements
on the screens, the layout and flow, colors, keyboard shortcuts
Documentation
Elements of documentation required to explain how to use the
application.
Deployment needs
describe how the
application will be delivered to End User
ex: All the software on the client
side will be downloaded and installed from the browser, without the position of
the client is restarted or configure.
| 
