Visits/GuidesRequirements1. Introduction1.1 PurposeThis software requirements specifications (SRS) document
gives a detailed description of the functionality of the system to be
implemented to support the administration of the visits and guides at
CERN.
The intended audience is:
1.2 ScopeThe software system to be produced will support the
following functions:
1.3 Definitions, Acronyms and AbbreviationsVisit A guided tour to one or more CERN sites, accompanied
by one or more guides 1.4 ReferencesVisits home page: http://www.cern.ch/visits/english/welcome1.html
1.5 OverviewThe rest of this SRS document contains the compiled list of requirements of the system to be implemented. Chapter 2 describes the general and implementational constraints
for the project, as well as a list of interfaces with other applications.
Chapter 3 contains a detailed description of the functionalities
of the system. 2. General description2.1 General constraintsIn its drive to make its applications easily accessible
(client platform independant, accessibility from outside CERN) and interconnected,
AS-CIS have decided to implement the user interface of its applications
on the Web. Therefore, if AS-CIS is to implement the proposed system,
it will be Web based. The server side will run on a Unix machine, using
Oracle as the database engine.
2.2 Interfaces with other applicationsThe main advantage of AS-CIS implementing the system
is its ability to integrate it with other administrative applications:
Two external (non-AIS) systems will be referenced as well:
Also, the AIS common login system will be used to authenticate users. 3. Specific requirements3.1 Functional Requirements3.1.1 GuidesThe principal function of the system is the administration
of the guides. Any person registered in the personnel system (HR) can
volunteer to give guided tours. The attributes of a guide referenced
from HR are:
Attributes of a guide maintained in the system are:
It should be possible to maintain the data concerning a guide, even if the person is no longer active as a guide. 3.1.2 Guides listingThe system must allow the user to query the guides on their attributes, one or more at the same time:
The user must have the possibility to use the list obtained as an email distribution list, f.i. to send an email to all conferenciers that speak German. 3.1.3 Visits AdministrationThe second function of the system is the scheduling of the visits and the definition of the guide(s) that will accompany the visit. First, a visit is requested by an individual or for a group for a certain date or period. The request is assigned a guide of type Hotesse (receptionist). Then, the different stages for that visit are scheduled with the accompanying guides. The selection of the guides depends on the courses they followed, their availability, and the languages they speak. At maximum 12 people are accompanied by a guide, so for bigger groups, more than one guide will be assigned. A stage is either for one group or for a number of individuals. Multiple groups can be put in the same conference, given that they all speak the same language. These conferences are scheduled before the first stage, and are assigned one conferencier. For the visits, an Entity-Relationship model is available. 3.1.4 Visits overviewA number of reports will be available for the overviews of the visits (to be determined). 3.1.5 Email list generationAn email distribution list of the guides must be dynamically refreshed on the IT listbox server. 3.2 The objects in the systemBelow is a description of the objects found in the system.
3.3 Performance requirementsNo strict performance requirements exist. The email list must be refreshed daily. 3.4 Other requirementsSince most users of the system are French speaking, the apllication must be generated in French. |
|
Author |