Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Issue: 1.0
ISS/ECMS/Tech/Spec/URS/ECMS_URS_V1.0
User Requirements
Specification
Enterprise Cargo Management System
ECMS
Author
: SE18 Team7S
Document Version
: 1.0
Document Date
: 21 Feb 2011
Document Reference
: ISS/ECMS/Tech/Spec/URS/ECMS_URS_V1.0
Reviewed By
Confidential
Page i of 16
ECMS
Issue: 1.0
ISS/ECMS/Tech/Spec/URS/ECMS_URS_V1.0
Revision History
Date
02/21/11
Issue
Description
Author
0.1
NG SIEW LENG
Distribution List
Name
Department / Company
NUS / ISS
NG SIEW LENG
NUS / ISS
PRAGATI
NUS / ISS
NUS / ISS
VARUN TAK
NUS / ISS
ZHANG SHUDONG
NUS / ISS
PILA SOYTIP
Confidential
Page ii of 16
ECMS
Issue: 1.0
ISS/ECMS/Tech/Spec/URS/ECMS_URS_V1.0
TableofContents
TableofContents..........................................................................................................................iv
RevisionHistory............................................................................................................................iv
1. Introduction..............................................................................................................................1
1.1
1.2
1.3
1.4
1.5
Purpose...........................................................................................................................................1
DocumentConventions..................................................................................................................1
IntendedAudienceandReadingSuggestions.................................................................................1
ProjectScope..................................................................................................................................1
References......................................................................................................................................1
2.1
2.2
2.3
2.4
2.5
2.6
2.7
ProductPerspective........................................................................................................................2
ProductFeatures.............................................................................................................................2
UserClassesandCharacteristics....................................................................................................2
OperatingEnvironment..................................................................................................................2
DesignandImplementationConstraints.........................................................................................2
UserDocumentation.......................................................................................................................2
AssumptionsandDependencies.....................................................................................................3
2. OverallDescription..................................................................................................................2
3. SystemFeatures.......................................................................................................................3
3.1 SystemFeature1............................................................................................................................3
3.2 SystemFeature2(andsoon)..........................................................................................................4
4. ExternalInterfaceRequirements...........................................................................................4
4.1
4.2
4.3
4.4
UserInterfaces................................................................................................................................4
HardwareInterfaces........................................................................................................................4
SoftwareInterfaces.........................................................................................................................4
CommunicationsInterfaces............................................................................................................4
5.1
5.2
5.3
5.4
PerformanceRequirements.............................................................................................................5
SafetyRequirements.......................................................................................................................5
SecurityRequirements....................................................................................................................5
SoftwareQualityAttributes............................................................................................................5
5. OtherNonfunctionalRequirements.......................................................................................5
6. OtherRequirements................................................................................................................5
AppendixA:Glossary....................................................................................................................5
AppendixB:AnalysisModels.......................................................................................................6
AppendixC:IssuesList.................................................................................................................6
Confidential
Page 1 of 16
ECMS
Issue: 1.0
ISS/ECMS/Tech/Spec/URS/ECMS_URS_V1.0
1.
Introduction
The Institute of System Science (ISS) MTech Team, SE18 Team S07 has taken up the task
of developing Enterprise Cargo Management System (ECMS) for WWW Cargo Pte Ltd
(Project Sponsor).
This will involve the development of four core software modules:
1.1
Purpose
The purpose of this document is to describe the user requirements for the ECMS system.
It provides a basis for the traceability from the requirements to design and to the actual
implementation. Both functional and non-functional aspects of the system shall be
included in this document.
1.2
DocumentConventions
1.3
IntendedAudienceandReadingSuggestions
1.4
ProjectScope
Confidential
Page 2 of 16
ECMS
Issue: 1.0
ISS/ECMS/Tech/Spec/URS/ECMS_URS_V1.0
Rational Unified Process (RUP) methodology will be used for the software development.
This software project will be divided into four major phases:
1.5
Project Initiation
Project Planning / Requirements gathering
Analysis and Design
Implementation
References
To fully understand the background of this ECMS project, the reader should be familiar
with the following documents:
Document
Version
Filing Reference
ECMS Project Plan
1.0
ECMS Quality Plan
1.0
2.
OverallDescription
2.1
ProductPerspective
<Describe the context and origin of the product being specified in this SRS. For example, state
whether this product is a follow-on member of a product family, a replacement for certain existing
systems, or a new, self-contained product. If the SRS defines a component of a larger system,
relate the requirements of the larger system to the functionality of this software and identify
interfaces between the two. A simple diagram that shows the major components of the overall
system, subsystem interconnections, and external interfaces can be helpful.>
2.2
ProductFeatures
<Summarize the major features the product contains or the significant functions that it performs or
lets the user perform. Details will be provided in Section 3, so only a high level summary is
needed here. Organize the functions to make them understandable to any reader of the SRS. A
picture of the major groups of related requirements and how they relate, such as a top level data
flow diagram or a class diagram, is often effective.>
2.3
UserClassesandCharacteristics
The main system users are Administrative Manager, Administrative staff and staff of
Resource Centre who are all computer literate.
A user training session shall be provided for all users
Confidential
Page 3 of 16
ECMS
Issue: 1.0
ISS/ECMS/Tech/Spec/URS/ECMS_URS_V1.0
2.4
OperatingEnvironment
The system should run on common PCs for system deployment without need of
purchasing any additional hardware and software.
2.5
DesignandImplementationConstraints
2.6
UserDocumentation
Relevant user documentation (e.g. user manuals) shall be created for both training and
system support/maintenance purposes.
2.7
AssumptionsandDependencies
The following assumptions and dependencies apply for the ECMS system:
There will be only one planned release of ECMS system.
The first release of ECMS system shall focus on providing the core functionalities
of task assignment and timesheet management.
The ECMS system shall be developed using open-source software and/or software
or hardware provided by ISS. ISS workstations and facilities may be used.
Representative(s) from WWW CARGO Pte Ltd shall act as the project sponsor for
the ECMS system. He/she shall provide the user requirements and other feedback;
and is responsible for performing user acceptance tests (UAT) and formally
accepting the ECMS system.
In return, SE18-Team7S agrees to grant non-exclusive and non-transferrable rights
to WWW CARGO Pte Ltd to use the ECMS system. However, this does not include
any future support, enhancements or releases of the software.
Every team member is able to complete the assigned tasks on time.
The ECMS system shall be a new web-based system with no interfaces to the
existing legacy systems.
ECMS system shall be built using object-oriented technologies and techniques.
Rational Unified Process (RUP) methodology shall be adopted as the development
approach.
The SE18-Team7S shall not bear any liabilities in case in the unlikely event the
project cannot be delivered.
The SE18-Team7S shall not bear any liabilities for whatever other causes.
3.
SystemFeatures
Page 4 of 16
ECMS
Issue: 1.0
ISS/ECMS/Tech/Spec/URS/ECMS_URS_V1.0
3.1
Loginandlogout
All logged in users must be able to terminate their session by selecting a login
option. Closing the browser will also log them out.
After logged in, the user must be able to choose the department to enter data or to
precede their job. There are 6 departments to be chosen; Marketing, Customer
Services, Import (Air / Sea separately), Export (Air / Sea separately), Project (Air /
Sea separately) and Warehousing & Transportation
3.2
CustomerProfileManagement
After user has logged into the system, the user is able to create new customer
profile using web form. The web form should perform validation of the data.
The company related information: Address, telephone number, fax number, email,
contact person, company registration number (UEN NO), credit term, delivery
address, special information, sales person, last update date, list of customer
supplier information (company name, address, Tel, fax, person in charge, others,
pickup location, pickup timing)
The logged in user should be able to browse all the existing customer profiles in a
systematic manner. The logged in user should also be able to retrieve the customer
profile by search company name.
The logged in user should be able to update the customer profile record. The
system should display confirmation page for user to confirm the change.
The logged in user should be able to delete the customer profile. The system
should display confirmation page for user to confirm delete.
The system should maintain the last updated date and by which user for each
customer profile.
3.3
Agent/SupplierProfileManagement
After user has logged into the system, the user is able to create new agent/supplier
profile using web form. The web form should perform validation of the data.
The company related information: Address, branch, telephone number, fax number,
email, contact person, credit term, special information, bank details, B/L (Bill of
lading) instruction, fumigation requirement, last update date and list of their
customer information (company name, address, Tel, fax, person in charge, others,
pickup location, pickup timing)
The logged in user should be able to browse all the existing agent/supplier profiles
in a systematic manner. The logged in user should also be able to retrieve the
customer profile by search company name or by country name.
Confidential
Page 5 of 16
ECMS
Issue: 1.0
ISS/ECMS/Tech/Spec/URS/ECMS_URS_V1.0
The logged in user should be able to update the agent/supplier profile record. The
system should display confirmation page for user to confirm the change.
The logger in user should be able to delete the agent/supplier profile. The system
should display confirmation page for user to confirm delete.
The system should maintain the last updated date and by which user for each
agent/supplier profile.
3.4
MaintainingCostRecordsfromAgent/Supplier
Basically this function helps user to record the cost breakdown when they arrange
shipment from overseas for tracking purpose. The user can also compare the cost
that quoted by agent with the debit note before arranging payments to
agent/supplier. Typically the cost record is extracted from the emails between
supplier/agents.
After user has logged into the system, the user is able to create or save the cost
records by using Outlook, MS Word, MS Excel and Adobe format. The subject of
the file name will be the same format starting by entry date, agent name, shipper
name, consignee name, incoterms, shipment type, port of loading and port of
destination
(For example: 20110228 Alisped/Roberto Tarchi Nilfisk/ EXW/ LCL/ Italy-Sin)
The logged in user should be able to browse all the existing cost records by
opening in Outlook, MS Word, MS Excel and Adobe format. The logged in user
should also be able to retrieve the cost records by search agent company name,
file name or partial of file name.
The logged in user should be able to update the cost record from agent/supplier
(applicable for MS word & MS Excel only).
The logger in user should be able to delete the cost records. The system should
display confirmation page for user to confirm delete.
3.5
QuotationtoCustomerManagement
This system will helps user to track the quotation records before issuing the freight
invoice to customer. The system will maintain a list of quotations in the system
After user has logged into the system, the user is able to create or save the
quotations by using Outlook, MS Word, MS Excel and Adobe format. The subject of
the file name will be the same format starting by entry date, shipper name,
consignee name, incoterms, shipment type, port of loading and port of destination.
(For example: 20110228 Roberto Tarchi Nilfisk/ EXW/ LCL/ Italy - Sin)
Confidential
Page 6 of 16
ECMS
Issue: 1.0
ISS/ECMS/Tech/Spec/URS/ECMS_URS_V1.0
The logged in user should be able to browse all the existing quotation by opening
in Outlook, MS Word, MS Excel and Adobe format. The logged in user should also
be able to retrieve the cost records by search customer company name, file name
or partial of file name.
The logged in user should be able to update the quotation (applicable for MS word
& MS Excel only). Immediately the system should display the rename file page for
user to re enter the file name, which may adjust only date of entry.
The logger in user should be able to delete the quotation. The system should
display confirmation page for user to confirm delete.
3.6
QuotationtoAgent/SupplierManagement
After user has logged into the system, the user is able to create or save the
quotation by using Outlook, MS Word, MS Excel and Adobe format. The subject of
the file name will be the same format starting by entry date, agent name, shipper
name, consignee name, incoterms, shipment type, port of loading and port of
destination.
(For example: 20110228 FDI/ Bourjois Europe Intl/ C&F/ LCL/ Sin - HCM)
The logged in user should be able to browse all the existing quotation by opening
in Outlook, MS Word, MS Excel and Adobe format. The logged in user should also
be able to retrieve the quotation by search agent company name, file name or
partial of file name.
The logged in user should be able to update the quotation (applicable for MS word
& MS Excel only). Immediately the system should display the rename file page for
user to re enter the file name, which may adjust only date of entry.
The logger in user should be able to delete the quotations. The system should
display confirmation page for user to confirm delete.
3.7
ShipmentTracking(Followuplist)
The function will be used by customer service staffs for updating shipment details.
And to update to the customer when there is any news update from oversea
agents. The customer service staffs will also monitor the shipments and make sure
all the required documents are received before passing to operation team. This
tracking list will be indicated the status of shipment every steps.
After user has logged into the system, the user is able to create new shipment
information in the systems. Whenever the user create, the systems will immediately
send the message to the related customer and user can also add the person email
if they want to.
The tracking list will be indicated information about the shipment: Shipper name,
Consignee name, Ref or PO number, Incoterms, Port of Loading, Port of
Confidential
Page 7 of 16
ECMS
Issue: 1.0
ISS/ECMS/Tech/Spec/URS/ECMS_URS_V1.0
3.8
ImportShipmentDocumentProcessing
The purpose of this function is to reduce the time consumption in the operation
procedures. As normally the operation will need to issue a lot of documents by
enter the same information. So basically this function will be mainly used by import
operation staff. As some information from shipment tracking will be appeared in the
job sheet and others documents so the operation staff will not need to do double
job.
After user has logged into the system, the user is able to fill up shipment
information in the job sheet. The date from the job sheet will also transfer to the
Import costing sheet, Notice of arrival, Import delivery note, Console Manifest,
Transhipment cover sheet, Shipping Noted, House Bill of Lading and Master Bill of
Lading. After receiving documents from oversea agent, the operation staff will
generate the import documents as follows:
JOB SHEET: the data sheet that summarized all information of each
shipment including total amount of invoice to customer, all cost and profit
and loss. There are 2 formats of Import job sheet separate Air and Sea.
Information for Sea Import job sheet: Month of the job sheet, ETA, Job
number, Port of Loading, Container number, Vessel name, House Bill of
Lading number, Number of package, Package type, Weight, Measurement,
Shipper name, Consignee name, Carrier name or NVOCC, Agent name,
Invoice number, Total billing amount, Cost from various suppliers, Total profit
and Remark.Information for Air Import job sheet: Month of the job sheet,
ETA, Job number, House Airway Bill number, Master Airway Bill number, Port
of loading, Flight number, Number of package, Kind of package, Weight,
Measurement, Incoterms, Shipper name, Consignee name, Invoice number,
Total billing amount, Cost from various suppliers, Total profit and Remark.
IMPORT COSTING SHEET: the cover of each shipment at the file when
arranging the shipment. The costing sheet will be used to differentiated the
file, list of procedure to followed and summarized cost and profit when finish
the job. Costing sheet for Air and Sea is same format. The Import Costing
sheet should included: Agent name, Invoice number, Vessel/ MAWB,
HBL/HAWB, Port of Loading, Port of destination, Terms, Exchange rate, Job
number, Voyage of vessel/ Flight number, ETD, Shipper name, Number of
Confidential
Page 8 of 16
ECMS
Issue: 1.0
ISS/ECMS/Tech/Spec/URS/ECMS_URS_V1.0
Confidential
Page 9 of 16
ECMS
Issue: 1.0
ISS/ECMS/Tech/Spec/URS/ECMS_URS_V1.0
3.9
ExportShipmentDocumentProcessing
The purpose of this function is same as Import Shipment Document Processing,
which is to reduce the time consumption in the operation procedures. So basically
this function will be mainly used by export operation staff. But the different is there
is no shipment tracking for export. So all information of export will start from job
sheet.
After user has logged into the system, the user is able to fill up shipment
information in the job sheet. The date from the job sheet will also transfer to the
Export costing sheet, Collection note, Shipping note, House Bill of Lading and
Master Bill of Lading. After receiving booking confirmation from carrier or NVOCC
the operation staff will generate the export documents as follows:
JOB SHEET: the data sheet that summarized all information of each
shipment including total amount of invoice to customer, all cost and profit
and loss. There are 2 formats of Import job sheet separate Air and Sea.
Information for Sea Export job sheet: Month of the job sheet, ETD, Job
number, Port of Destination, Vessel name and voyage, House Bill of Lading
number, Number of package, Package type, Weight, Measurement, Shipper
name, Consignee name, Carrier name or NVOCC, Agent name, Type of
shipment differentiate by Nomination and Free hand, Invoice number, Total
billing amount, Cost from various suppliers, Total profit and Remark.
Information for Air Export job sheet: Month of the job sheet, ETD, Job
number, Port of Destination, Master Airway Bill number, Flight number,
House Airway Bill number, Number of package, Kind of package, Weight,
Measurement, Incoterms, Shipper name, Consignee name, Local Airfreight
Confidential
Page 10 of 16
ECMS
Issue: 1.0
ISS/ECMS/Tech/Spec/URS/ECMS_URS_V1.0
Confidential
Page 11 of 16
ECMS
Issue: 1.0
ISS/ECMS/Tech/Spec/URS/ECMS_URS_V1.0
3.10 ProjectShipmentDocumentProcessing
The purpose of this function is same as Import & Export Shipment Document
Processing, which is to reduce the time consumption in the operation procedures.
So basically this function will be mainly used by project operation staff. All
information before starting to generate the document will start from job sheet.
After user has logged into the system, the user is able to fill up shipment
information in the job sheet. The date from the job sheet will also transfer to the
Project costing sheet, Collection note, Delivery note and Export subsidiary
Certificate. Fro project job after receiving goods from courier or 3rd party agent to
arrange, the operation staff will generate the documents as follows:
JOB SHEET: the data sheet that summarized all information of each
shipment including total amount of invoice to customer, all cost and profit
and loss. There are 2 formats of Import job sheet separate Air and Sea.
Information for Sea Project job sheet: Month of the job sheet, ETA, Job
name, Job number, Port of Loading, Port of Destination, Vessel name and
Voyage, House Bill of Lading number, Number of package, Package type,
Weight, Measurement, Shipper name, Consignee name, Operation name,
Agent name, Invoice number, Total billing amount, Cost from various
suppliers, Total profit and Remark. Information for Air Project job sheet:
Month of the job sheet, ETA, Job number, House Airway Bill number, Master
Airway Bill number, Port of loading, Flight number, Number of package, Kind
of package, Weight, Measurement, Incoterms, Shipper name, Consignee
name, Invoice number, Total billing amount, Cost from various suppliers,
Total profit and Remark.
PROJECT COSTING SHEET: the cover of each shipment at the file when
arranging the shipment. The costing sheet will be used to differentiated the
file, list of procedure to followed and summarized cost and profit when finish
the job. Costing sheet for Air and Sea is same format. The Import Costing
sheet should included: Agent name, Invoice number, Vessel/ MAWB,
HBL/HAWB, Port of Loading, Port of destination, Terms, Exchange rate, Job
number, Voyage of vessel/ Flight number, ETD, Shipper name, Number of
package, Weight, Measurement, Consignee name, Contact person of
consignee with Telephone and Fax number, Procedure of the import job,
Detail of charges, Total Billing, Total Cost and Profit/Loss.
COLLECTION NOTE: the document that used for collect the goods from
shipper of each job. By issuing this document, Air and Sea collection noted
will be different in format and detail.
DELIVERY NOTE: the document that used for delivery of each job. This
document is very important for each job very much as it will be the evidence
to prove that the goods had been delivered to the final importer safely and
completely of amount of goods. By issuing this document, Air and Sea
delivery noted will be different in format and detail.
The logged in user should be able to edit all the information that indicate on the
document.
The system will remain the documents on the list until the job sheet status close. If
the status of shipment is unclose and the use wants to back up document the user
can also back up the document without close the file, as long as the document not
necessary to remain on the systems anymore.
Confidential
Page 12 of 16
ECMS
Issue: 1.0
ISS/ECMS/Tech/Spec/URS/ECMS_URS_V1.0
3.11 Transportation&Warehousing
The user will able to input the delivery planning of each day. And the warehouse
staff will able to retrieve the cargo, which still store at the warehouse. Moreover the
warehouse staff will able to locate the cargo location and record down the starting
date of storage for charging purposes.
3.12 ShipmentInvoice
Invoice is the document that indicated all the charges related to the shipment that
had been arranged. It is used for summarized all the charges and submit to the
customers. As the user already have the systems that still useable, so we will
remain that systems and will not adjust anything in this stage.
4.
OtherNonfunctionalRequirements
4.1
PerformanceRequirements
System Response Time : 2 3 seconds
(The time the system takes to react to a given input / command)
System Turnaround Time : 5 10 seconds
(The delay between submission of a job for a data-processing system and its
completion)
4.2
SecurityRequirements
The system will enforce passwords policies according to current enterprise
application standards
Access to confidential data and material, will be restricted on user role.
Login attempts will be limited to a configurable number of attempts, after which
access will be denied until a reset is performed by administrator.
Access to the application over the Internet will be secured.
4.3
SoftwareQualityAttributes
System Availability
o 16 Hours from Monday to Sunday (0600 2200)
o 24 Hours from Saturday to Sunday
Confidential
Page 13 of 16
ECMS
Issue: 1.0
ISS/ECMS/Tech/Spec/URS/ECMS_URS_V1.0
5.
OtherRequirements
<Define any other requirements not covered elsewhere in the SRS. This might include database
requirements, internationalization requirements, legal requirements, reuse objectives for the
project, and so on. Add any new sections that are pertinent to the project.>
AppendixA:Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire
organization, and just include terms specific to a single project in each SRS.>
AppendixB:AnalysisModels
<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams,
state-transition diagrams, or entity-relationship diagrams.>
AppendixC:IssuesList
< This is a dynamic list of the open requirements issues that remain to be resolved, including
TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>
Confidential
Page 14 of 16