Version
|
Author
|
QA
|
Date
|
Status
|
Comment
|
|
2.1 |
Balzert |
|
3/91 |
accepted |
|
|
2.2 |
Balzert |
|
10/91 |
accepted |
a) |
|
2.3 |
Balzert |
|
10/95 |
accepted |
b) |
QA Quality Assurance
a) /F 115/ added
b) /F 15/, /F 125/, /F 185/, /D
65/, /F 130/, /D 10/, /D 20/ added, /D 30/, /D 70/ changed
The seminars presented by “Teachware”
company shall be computer managed.
1.1
Compulsory
Criteria
·
Managing seminars
·
Managing clients (participants/interested parties)
· Issuing and sending invoices
·
Queries like: When will the
next X seminar take place?
Which associates of Y company participated
the seminar X?
1.2
Optional Criteria
·
Advanced query possibility
·
Statistics
·
Support of data backup
·
Reuse of seminar and client management
1.3
Exclusion Criteria
·
No accounting (book keeping) integrated (the accounting gets
a copy of invoice and keeps track of payment and notifies of paying delay)
Product
is used for management of clients and presentations of “Teachware”
company. Besides, different queries should be answered.
2.1
Application Area
Commercial
application area: management of seminars and clients. Queries.
2.2
Target Groups
“Teachware” associates that can be categorized in two groups:
client management and seminar management.
2.3
Usage Conditions
Office environment.
Product
is used on an office computer.
3.1 Software
Operating
system: Windows 95
3.2 Hardware
PC
3.3 Orgware
Network connection to computer in accounting department.
3.4 Product Interfaces
One copy
of issued invoices is saved to a file, which can be accessed by accounting department
through a provided function. Accounting department enters paying delays through
a provided function.
4.1
Client Management
/F 10/ Client registration, editing and deletion (client = participant/interested
party) /PF 10/
/F 15/ Registration, editing and deletion of companies which
send their associates to seminars.
/F 20/ Registration of a client with verification:
/F 30/ - if she/he is already registered
/F 40/ - if the desired seminar is possible
/F 50/ - if the seminar is still free
/F 55/ - what is the kind of payment.
/F 60/ Forwarding of registration notification /PF 20/.
/F 70/ Client checking out (canceling) with verification /PF
20/:
/F 80/ - if she/he was registered at all.
/F 90/ - if canceling happened more than 4 weeks before seminar.
(-> 100 EUR cancellation
fee or substitute participant).
/F 100/ - if canceling happened less than 4 weeks before seminar.
(->
charge 100% of charge fee or substitute participant).
/F 110/ - if “Teachware”
canceled seminar (® no
invoice)
/PF 20/.
/F 115/ Informing the participant in case “Teachware”
canceled the seminar.
/F 120/ Registering, change and deletion of seminar booking /PF 50/.
/F 125/ A company can book another company’s
internal presentation.
/F 130/ Making address labels for sending advertisements to all clients
and companies.
/F 135/ A circular letter can be send to
all clients and companies.
/F 140/ Accounting department inputs all the delayed payments using
a provided function.
4.2
Seminar management
/F 150/ Registering, change and deletion of seminar presentations and seminar types /PF 30/.
/F 160/ Canceling seminar appointments /PF 20/.
/F 170/ Enter if a seminar really took place.
/F 180/ Registering, change and deletion of lecturers, as well as
assigning them to seminar presentations and types /PF 40/.
/F 185/ A circular letter can be send to
all lecturers.
/F 190/ Issuing a list of all participants for the seminar X (seminar title, date from, date to, place where the presentations is to take place, lecturer(s), first name, second name, company, place) /PF 70/.
/F 200/ Issuing a certificate for every participant (address, first
name, second name, date from, date to, seminar title, place where the seminar
took place, content overview, presentation custodian) /PF 70/.
4.3
Issuing invoice
/F 210/ Usually a certificate of seminar registration is issued together with invoice and send /PF 60/.
/F 220/ Copies of data sets considering
invoices will be saved to a
file, in order that accounting department can access it over network (through
a function).
4.4
Queries
/F 230/ When will the next seminar X take place? /PF 80/
/F 240/ Which associates of company Y has attended the seminar X? /PF 80/
/F 250/ Other kinds of queries should be
possible, for instance: With which 10 companies were made the biggest revenues
during a financial year? Which kinds of seminars had most participants during
a financial year?
5.1. Client Data
/D 10/ Save the following information about client (interested party/participant): /PD 10/ personal number, name (address, title, first and second name), address (street, house number, land code, postal code, place, phone, fax), date of birth, function, revenue, memo, notes, info-material, client since.
/D 20/ If a client is associate of a company, then save the following information about it: /PD 20/ Company short name, company name, address, phone, fax, name, address, department, date of birth, associate’s position in company, memo, notes, revenue, client since.
/D 30/ If a client or a company is late
with payment, then save the following data: date of invoice, which is not yet
paid for, and amount of invoice.
5.2 Seminar Data
/D 40/ For every presented seminar, following data should be saved /PD 30/: presentation number, duration (in days), from, to, daily period split – start, daily period split-end, start at first day, end at last day, where is it to take place (hotel/company, address, room), cooperation partner, public (yes/no), net price, cancellation fee, participants min, participants max, participants current, accomplished (yes/no).
/D 50/ Save the following data for every seminar type /PD 30/: short title of the seminar, seminar title, purpose, methodic, content overview, daily procedure, duration, documentation, target group, preconditions, fee without tax, min number of participants, max number of participants.
/D 60/ Save the following data about lecturer: personal number, name, address, phone, fax, date of birth, biography, fee per day, memo, notices, lecturer since /PD 30/.
/D 65/ If a lecturer gives a certain seminar presentation, save
this information.
5.3 Booking Data
/D 70/ The following data should be saved
about every seminar booking made by a client or a company /PD 40/: registered
on, acknowledgement on, checked out on, notification on.
/E 10/ Functions /F 180/ and /F 190/ should not take more than 15 sec to answer, all other function must answer in less than 2 sec.
/E 20/ It could be maximum 50 000 participants/interested parties and maximal 10 000 seminars governed.
/E 30/ According to experience, 5% of all
clients are late with payment.
/U 10/ Menu oriented usage is standard.
/U 20/ Interface is to be constructed for mouse. Its usage without mouse must also be provided.
/U 30/ DIN 66234, part 8, is to be followed.
/U 40/ There are two different views of seminar organization:
the view of a person in charge for clients (client manager), and a view of
a person in charge for seminars (seminar manager).
/U 50/ The client manager handles the
functions /F 10/ to /F 130/, as well as /F 230/ to /F 250/. She/he may
access only the data which belong to these functions. Access rights and prohibitions
are to be given with this in respect.
/U 60/ The seminar manager handles the
functions /F 150/ to /F 200/ as well as /F 250/. She/he may access only the
date which belong to these functions. Access rights and prohibitions are to
be given with this in respect.
Product Quality
|
very good |
good |
normal |
not important |
Functionality
|
|
|
|
|
|
Suitability |
|
x |
|
|
|
Correctness |
|
x |
|
|
|
Interoperability |
|
x |
|
|
|
Properness |
|
x |
|
|
|
Security |
|
x |
|
|
Reliability
|
|
|
|
|
|
Maturity |
|
|
x |
|
|
Fault
tolerance |
|
|
x |
|
|
Recoverableness |
|
|
x |
|
Usefulness
|
|
|
|
|
|
Intelligibility |
|
x |
|
|
|
Learnable |
|
x |
|
|
|
Usability |
x |
|
|
|
Efficiency
|
|
|
|
|
|
Time
response |
|
x |
|
|
|
Consuming
behavior |
|
x |
|
|
Changeability
|
|
|
|
|
|
Analyzability |
|
|
x |
|
|
Modifiability |
|
|
x |
|
|
Stability |
|
|
x |
|
|
Provability |
|
|
x |
|
Portability
|
|
|
|
|
|
Adaptability |
|
|
x |
|
|
Installability |
|
|
x |
|
|
Conformity |
|
|
x |
|
|
Exchangeability |
|
|
x |
|
Following
function sequences are to be checked:
/T 10/ Participants login, registration, checking out, new login,
invoice, payment delay.
/T 20/ Canceling, change.
/T 30/ Canceling, issuing
invoice.
/T 40/ Entering a seminar realization,
and issuing invoices.
Following data consistencies are to
be kept:
/T 50/ The booking is possible to be
made only if there is a client entry as well as a seminar presentation entry,
and if the seminar presentation is not yet overbooked.
/T 60/ A new seminar presentation can
be entered only if the corresponding seminar type is available.
Open (not defined)