Академический Документы
Профессиональный Документы
Культура Документы
CSEB 274
Name & ID :
Section
Lecturer
Assignment
Team Name
:
:
:
:
Requirement Engineering
Document Control :
Document Name
Reference Name
Version
Project Code
Status
Date Released
Name
Position
Prepared By :
Ms. Business Analyst
Business Analyst
XYZ Training
Reviewed By :
Mr.Reviewer
Lead Developer
XYZ Training
Approved By :
Mr.Client
Project Manager
XYZ Training
Signature
Version History:
Version
1.0
Release Date
27/1/2015
Section
All
Amendments
Original Document
Table of Contents
Document Control . i
Version History . ii
Table of Contents...iii
1.0 Introduction .
1.1 Purpose
1.2 Scope.
1.3 Definition &Acronyms...
1.4 References
1.5 Technologies to be used .
1.6 Overview
2.0 Overall Description
2.1 Product Perspective
2.1.1 User Interfaces
2.1.2 Hardware Interfaces.
2.1.3 Communication Interfaces
2.2 Product Feature.
2.3 Users Characteristics
3.0 Specific Requirements..
3.1 External Interfaces.
3.1.3 Session Verification Interface .
3.2 Functional Requirement ..
3.2.3 F003 Session Verification.
3.4 Design Constraints..
3.5 Software System Attributes .
3.5.1 Accuracy
3.5.2 Security ..
1.0 Introduction
1.1 Purpose
The purpose of this document is to specify the detail at the specific requirements
elicited by Training XYZ Requirements Engineering Team from Training XYZ
Sdn Bhd .It addresses the functionality,
Performance, interface, quality attributes and compliance requirements of Training
Logistics System (TLS).
This document is intended for system developer, project manager, configuration
manager and client.
1.2 Scope
ii.
1.4 References
This document is prepared in reference to the following documents:
i.
1.6 Overview
Section 1 contains the purpose, scope, definitions, acronyms and references made
to other documents.
Section 2 contains the overall description of the system, including constraints and
assumptions.
Section 3 contains specific requirements of TLS to be implemented.
2.0
Overall Description
Description
Priority Author
TLS GUI shall make use of only two colours , Medium Agile
skyblue (RGB Hex code : #87ceeb) for
background and greenyellow (RGB Hex code
: #adff2f) for text .
Table 1.0 TLS GUI Requirements
Internet Explorer -6
Processor
All Intel or AMD 1 GHZ
RAM
4 GB
Disk Space
100MB
Server side:
RAD
DB2 9.5
Processor
All Intel or AMD
2 GHZ
All Intel or AMD
2 GHZ
RAM
4 GB
Disk Space
3.5 GB
512 MB
500 MB
(Excluding data
size )
FEATURE
DESCRIPTION
P001
NOTIFICATION
P002
GATHER INFORMATION
P003
ARRANGEMENT
P004
CREATE CONTRACT
AGREEMENT
P005
MATERIALS
ACCESSIBLE
ROLE
BOOKING
DEPARTMENT
LOGISTIC
COORDINATOR
LOGISTIC
COORDINATOR
SALES
MANAGER
MATERIALS
HANDLING
DEPARTMENT
A coordinator primary role is to arrange all the training sites preparations that deal
with material handling department, booking department, training consultant and
sales manager of meeting sites.
<Agile Team >/ < University Tenaga Nasional >
DESCRIPTION
The Training XYZ Sdn Bhd
logistic coordinator
performs activities on TLS.
REQUIRED KNOWLEDGE
Knowledge on gathering the
information needed to run a
seminar including meeting
sites,seating arrangement and also
handling the travels.
Sales Manager Sales manager of the chosen Knowledge on giving a full
meeting site chosen.
preparation for the seminars as
agreement signed.
TABLE 3.0 INTENDED USERS AND REQUIRED KNOWLEDGE
REQUIREMENT ID
Item
DESCRIPTION
Purpose
Format
Related I/O
AUTHOR
REQUIREMENT ID
Item
DESCRIPTION
Purpose
Format
Related I/O
AUTHOR
REQ_IO301 VERSION
1.0
Email(input)
Email of User saved in the database system.
To allow user to login according to their own main menu.
String
Valid Range
6 Arabic Numerical Digits(000000-999999)
REQ_IO302, REQ_IO303 (Password must match with the email and the user
type to allow login)
Agile
REQ_IO302
VERSION
1.0
Password (input)
Password that is associated with the user name keyed in.
To prevent unauthorized access in wrong menu/TLS.
String
Valid Range
6 Arabic Numerical Digits(000000-999999)
REQ_IO301, REQ_IO303 (Password must match with the email and the user
type to allow login)
Agile
REQ_IO301
VERSION
1.0
User Type (input)
The type of user of the system
To allow user to pick the right type of user.
Radio Button Valid Range
6 Arabic Numerical Digits(000000-999999)
REQ_IO301, REQ_IO302 (Password must match with the email and the user
type to allow login)
Agile
AUTHOR
REQ_P001
VERSION
1.0
System shall allow receiving booking and keep a record of notification
received and sent.
Agile
REQUIREMENT ID
REQ_P002
DESCRIPTION
AUTHOR
VERSION
1.0
REQUIREMENT ID
DESCRIPTION
AUTHOR
REQ_P003
VERSION
1.0
System shall allow logistic coordinator to done all the arrangements.
Agile
REQUIREMENT ID
DESCRIPTION
AUTHOR
REQ_P004
VERSION
1.0
System shall create a contract agreement to be signed and kept in system.
Agile
REQUIREMENT ID
DESCRIPTION
AUTHOR
REQ_P005
VERSION
System shall handle all the materials.
Agile
1.0
REQUIREMENT ID
DESCRIPTION
AUTHOR
REQ_P006
VERSION
System shall allow user to terminate their login session.
Agile
1.0
REQ_P101
VERSION
1.0
System shall be able to verify user name, password, and user type
Agile
AUTHOR
REQ_P102
VERSION
1.0
System shall prompt user to re-input user name, password, and user type for
wrong input respectively.
Agile
REQUIREMENT ID
DESCRIPTION
AUTHOR
REQ_P103
VERSION
System shall allow user to cancel login
Agile
REQUIREMENT ID
DESCRIPTION
AUTHOR
REQ_P104
VERSION
1.0
System shall allow user to logout while in XYZ Training Menu
Agile
REQUIREMENT ID
DESCRIPTION
REQ_P101
VERSION
1.0
System shall display error message for wrong user name, password or wrong
user type input
Agile
AUTHOR
1.0
UC001
VERSION
1.0
Receive Booking
To allow logistic coordinator to receive training booking details
Booking department, Registrant
Registrant book a training place
Training placement is available to book.
STEP
ACTION
1
Registrant register in Training first-time registration
2
System verify first time registration.
3
System show Booking form and wait for registrant respond
submission.
4
User fill in the form and submit.
5
System verify form filled correctly.
6
System shows that the booking has been completed
7
Registrant logout.
8
Booking department receive notification that a registrant has
registered.
1.1
1.2
1.3
1.1
1.2
1.2.1
1.3
1.3.1
1.4
4.1
4.2
4.3
4.4
i.
ii.
AGILE
ALTERNATE FLOW
RULES
NOTE
AUTHOR
UC002
VERSION
1.0
Send Notification
Agile
Logistic Coordinator, Booking department
Minimum number of participant in a training achieved
Not yet notify the logistic coordinator about training scheduled to run
STEP
ACTION
1
Booking department submit notification to logistic coordinator
with the details of the training of meeting type, number of
participant, and required audio-visual equipment.
2
System send notification to the logistic coordinator.
3
Logistic coordinator receive notification.
AGILE
ALTERNATE FLOW
RULES
NOTE
AUTHOR
UC003
VERSION
1.0
Receive Notification
Agile
Logistic Coordinator, Booking department
Notification arrived into logistic coordinator inbox
The notification has not been received before but may receive again if the
Booking department send again
STEP
ACTION
1
Logistic coordinator receives notification.
2
Logistic Coordinator send reply to the booking department that
the notification of the details of the training has been received.
3
System send the reply back to Booking department
2.1
Logistic coordinator send fail reply
2.2
System display reply sent is failed
2.3
Back to Main flow step 2
REQ_IO301 until REQ_IO303 may be used
AGILE
UC004
VERSION
1.0
Gather Information
Agile
Logistic coordinator, trainer
Logistic Coordinator login to the TLS system
Training booking notification has been received
STEP
ACTION
1
Logistic Coordinator insert username, password, usertype
2
System verify login.
3
System display menu of TLS.
4
Logistic Coordinator choose an arrangement sub-menu.
5
System open a Training Booking System tool
6
Logistic coordinator logout.
7
System redirect the interface back to the main page.
1.1
Logistic Coordinator insert wrong username/ password/ usertype
1.2
System fail to verify
1.3
Back to Main flow step 1
4.1
Logistic coordinator press Logout button
4.1
Back to Main flow step 7
Menu is further split Find Meeting Sites, Plan Seating Arrangement, Receive
A/V equipments, receive travel information.
REQ_IO301 until REQ_IO303 included
AGILE
ALTERNATE FLOW
RULES
NOTE
AUTHOR
UC005
VERSION
1.0
Find meeting sites (extended from Gather Information)
Agile
Logistic Coordinator, Sales Manager
Logistic Coordinator browse through meeting sites catalogue
Logistic Coordinator has login into TLS
STEP
ACTION
1
Logistic Coordinator browse through the meeting sites cataloge.
2
Logistic coordinator input constraint according to date availability,
rental fee, spacing size.
3
System return results that specify with the constraint
4
Logisitic Coordinator further analyse the results by clicking on the
more button
5
System return the extra information available.
6
Logisitic Coordinator pick the desired location and save into the
system
AGILE
UC006
VERSION
1.0
Plan Seating Arrangement(extended from Gather Information)
Agile
Logistic Coordinator
Logistic coordinator open the seating arrangement editor option
The type of meeting and the size of the meeting site has been obtained
STEP
ACTION
1
Logistic coordinator draft the arrangement using seating layout
editor picking an element into the editor space . (WYSIWYG)
2
System will save the layout every two minutes
3
Logistic coordinator press save button when finished
1.1
1.2
AGILE
ALTERNATE FLOW
RULES
NOTE
AUTHOR
UC007
VERSION
1.0
Receive audio/Visual equipment
Agile
Logistic coordinator
Logistic coordinator receive meeting type and size of site has been obtained
Logistic Coordinator has login into TLS
STEP
ACTION
1
Logistic coordinator specify numbers of audiovisual equipment
needed and the type of the equipment to be used.
2
System save the entry
AGILE
ALTERNATE FLOW
RULES
NOTE
AUTHOR
UC008
VERSION
1.0
Receive travel information
Agile
Logistic Coordinator, trainer/ training consultant
Meeting date has been known
Logistic Coordinator has login into TLS
STEP
ACTION
1
Trainer send his basic details via email such as name, i/c, origin.
2
Logistic coordinator search for available flight.
3
System return result that suitable for the flight date
4
Logistic coordinator pick one of the flight.
5
System redirect to the specific page of origin of the result from
the respective airline website in its inner frame
6
Logistic coordinator filled in the info of booking details
7
System show the success booking through its inner frame browser
8
Snapshot captured and sent back to the trainer
AGILE
UC009
VERSION
1.0
Confirm contract agreement
Agile
Sales Manager, logistic coordinator
Logistic coordinator receive contract agreement from sales manager
UC010 has taken place
STEP
ACTION
1
2 carbon copy of contract agreement arrive to the logistic
coordinator via system from email of sales manager
2
Logistic coordinator check the agreement and pick accept and
press print.
3
System print two copy of the agreement
4
Logistic coordinator sign the agreement and post one of the copy
and the other one is being kept in a file
2.1
2.2
UC010 is included
AGILE
UC0010
VERSION
1.0
Create contract agreement
Agile
Sales manager, logistic coordinator
Logistic coordinator send number of pax of participants and the size of meeting
room required to the sales manager
Logistic coordinator request meeting site from sales manager
STEP
ACTION
1
Logistic coordinator fill in in an email form with the details of
number of pax and the size of hall/ meeting room needed
2
System send the email to the sales manager
3
Sales manager receive the email and send new invoice.
4
System notify the logistic coordinator the invoice
5
Logistic coordinator accept the invoice specified
6
System sends the response back to the sales manager to create
contract agreement
5.1
5.2
5.3
Includes UC009
AGILE
UC0011
VERSION
1.0
Ship material
Agile
Material Handling Department, Logistic Coordinator
Meeting type has been known
Material has not been collected in sufficient number
STEP
ACTION
1
Logistic Coordinator send request to the material handling
department.
2
System send request to the material handling department.
3
Material handling department collected enough material and
notify back to the logistic coordinator.
4
System send the notification to the logistic coordinator
5
Logistic coordinator approves and request boxed materials to be
sent to the meeting site.
6
System notify both sales manager of meeting site and material
handling department about the parcel postage details
5.1
5.2
ALTERNATE FLOW
RULES
NOTE
AUTHOR
UC0012
VERSION
1.0
Receive Material
Agile
Sales manager, logistic coordinator, material handling department
Sales manager receive parcel of boxed material
Material has been shipped
STEP
ACTION
1
Parcel arrives at the required address
2
Sales manager email to the logistic coordinator about the
received parcel.
3
System notify logistic coordinator and material handling
department about the email
UC011 has to take place first
AGILE
Description
Priority
TLS shall have
High
less than 0.00001
% computational
error in identifying
User sign in.
Author
Agile
3.5.2 Security
REQ_Q003
Description
Priority
TLS shall keep
use secured line
High
for connection
with XYZ Training
Sdn Bhd.
TLS shall keep the
High
browse history of
the user for user
view.
Author
Agile
Agile