Professional Documents
Culture Documents
Seminar Organization
Requirements Specification v3.0
version
author
2.1
Balzert
03/91
accepted
2.2
Balzert
10/91
10/95
07/00
2.3
Balzert
3.0
status
comment
1. Goals
The seminars presented by "Teachware" company should be supported by computers.
1.1 Compulsory criteria
managing seminars
managing presentations
managing clients (participants/interested parties)
managing client companies
managing lecturers
queries like: When will the next X seminar take place?
Which associates participated the seminar Y?
no accounting (book keeping) integrated (the accounting has a copy of invoice and
keeps track of payment and notifies the paying delay)
2. Product usage
The product is used by client-, company-, lecturer-, seminar- and presentation management
of "Teachware" company. Besides, the various queries should be answered.
2.1 Application area
Salesman, administrative application area
2.2 Target groups
Associates of "Teachware" company should be divided into: client manager, seminar
manager, presentation custodian.
"Teachware" clients: clients and companies can get the information about seminars and
presentations on the Internet. They can book using Internet, as well.
2.3 Company conditions
Office environment.
3. Product overview
Overview diagram:
4. Product functions
4.1 Use cases
F10 (PF10)
Use case: informing: from question to information
Goal: client gets required information or the information material is sent to her/him
Category: primary
Preconditions: Post condition success: client gets required information
file:///C|/reqspec3_0.htm (3 von 13)20.02.2007 14:27:34
Post condition failure: sending notification to clients that internal company presentation is
not possible
Actor: seminar manager
Triggering event: company notification is available
Description:
1. company data retrieved
2. presentation registration
3. booking undertaken
4. produce registration proof
Extension:
1. A company data actualization
1. B invoice verification
Alternatives:
1. A a new company inclusion
2. A to show an interest in company's wishes
2. B informing lecturers about company wishes
F30 (PF30)
Use case: presenting seminar: from participation to evaluation
Goal: lecturers are conducting the presentation
Category: primary
Preconditions: presentation has enough participants and is not canceled
Post condition success: presentation is conducted
Post condition failure: Actor: presentation custodian
Triggering event: presentation beginning date
Description:
1. participants list and evaluations to participants and lecturers
2. certificates to participants
3. evaluations collection
4. proof of
5. payment notification to account department
Extension: Alternatives:F40 (PF40)
Use case: designing seminar: from idea to a new seminar
Goal: new seminar conduction
Category: primary
Preconditions: ask for client's, company's, and lecturer's opinion, examine the market
Post condition success: new seminar realization
Post condition failure: Actor: seminar manager
Triggering event: start planning period
file:///C|/reqspec3_0.htm (6 von 13)20.02.2007 14:27:34
Description:
1. look at seminar and presentation statistics (participants figures and payments)
2. seminar realization
Extension:
2. A order lecturers
2. B presentation scheduled (Use case: presentation planning)
Alternatives:
1. A delete a seminar
1. B seminar modification
F50 (PF50)
Use case: acquiring lecturer: from choosing to engaging
Goal: new lecturers engaging
Category: secondary
Preconditions: market examination
Post condition success: new lecturer engaged, contract sent
Post condition failure: Actor: seminar manager
Triggering event: start the planning period or sporadic
Description:
1. to see a new seminar and presentation
2. lecturer registration
Extension:
2. to assign seminars and presentations to lecturer
Alternatives:
2. A delete lecturer
2. B actualize lecturer
F60 (PF60)
Use case: planning presentation: from scheduling to reservation
Goal: presentation scheduled, place fixed and reserved
Category: secondary
Preconditions: Post condition success: planned presentation
Post condition failure: planned presentation is not finished
Actor: seminar manager
Triggering event: start the planning period or sporadic
Description:
1. to see a new seminar
2. presentation registration
Extension:
1. to see unfinished planned presentations
Alternatives:
Short title of seminar, seminar title, purpose, methodic, overview, daily procedure, duration,
records, target group, requirements, fee without tax, min. participant rate, max. participant
rate
D50 (PD50) Lecturers data (max. 5 000):
Lecturer number, name, address, communication data, date of birth, biography, daily
allowance, short information, notices, lecturer since.
D60
If a lecturer conducts a seminar, this information should be saved.
5.3 Booking data
D70
For every seminar booking by company or client, following information should be saved:
Registered when, validated when, biledl when, canceled when, notification when.
6. Product efficiency
E10 (PE10)
Function F90 must take less than 15 sec to answer.
E20 (PE20)
All reaction times on user actions must take less than 2 sec (except function F90)
7. Quality requirements
Product quality
excellent good
normal
Functionality
Suitability
Accurateness
Interoperability
Compliance
Security
Reliability
Maturity
Fault tolerance
Recoverability
Usability
not
relevant
Understandability
Learn-ability
Operability
X
X
Efficiency
Time behavior
Resource
behavior
X
X
Maintainability
Analyzability
Changeability
Stability
Testability
Portability
Adaptability
Install-ability
Conformance
Replace-ability
8. User interface
U10
Standard Windows-oriented environment.
U20
The web-browser handling is simplified. The available functions are executed in side-wise
frames. In main frames are presented the lists and register masks.
UI30
Service interfaces are designed for mouse.
U40
ISO 9241-10: 1996 (Ergonomic requirements for office work with screen machines, part 10:
dialog design fundamentals) to be taken into account.
U50
Distinguish the following roles:
Role
Rights
Client manager
Seminar manager
Presentation custodian
Lecturer
Client, Company
9. Non-functional requirements
If a functionality would be used over the Internet, than a secure transmit has to be possible,
after a client's wish, especially for roles of client manager, seminar manager, presentation
custodian.
10. Technical product environment
Product is client/server and Internet-enabled.
10.1 Software
Server-operating system: Windows NT/98.
Client-operating system: Windows NT/98 or Browser.
10.2 Hardware
Server: PC.
Client: Browser enabled machine with graphic monitor.
10.3 Orgware
Network connection of servers to accounts department's computer.
10.4 Product interfaces
A copy of a produced invoice will be stored as a data. Account department has an access to
this data through an available function. Paying delays will be entered by account
department through an available function.
file:///C|/reqspec3_0.htm (11 von 13)20.02.2007 14:27:34
Functions
SemOrg v1.0
(Kernel)
SemOrg v2.0
(Kernel)
F10 informing
X (without
Internet)
X (with Internet)
F20 booking
X (without
Internet)
X (with Internet)
X (without
Internet)
X (with Internet)
F22 canceling
X (without
Internet)
X (with Internet)
F23 company
booking
SemOrg v3.0
(Kernel)
F30 presenting
seminar
X (without
Internet)
X (with Internet)
F40 designing
seminar
X (without
Internet)
X (with Internet)
F50 acquiring
lecturer
X (without
Internet)
X (with Internet)
F60 planning
presentation
X (without hotel
management)
X (without
Internet)
X (with Internet)
F80 participant
certificate
X (without
Internet)
X (with Internet)
F90 queries
X (without
Internet)
X (with Internet)
13. Supplements
X (with hotel
management)