0% found this document useful (0 votes)
18 views7 pages

Bapm

The document outlines two use cases for a container mail order reservation application and a container tracking and monitoring system, detailing the steps involved, stakeholders, and conditions for each process. It also includes business rules governing booking, documentation, operational, security, access, and compliance requirements. The document emphasizes the importance of accurate data entry, timely updates, and adherence to regulations throughout the logistics process.

Uploaded by

shreya.jaiswal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
18 views7 pages

Bapm

The document outlines two use cases for a container mail order reservation application and a container tracking and monitoring system, detailing the steps involved, stakeholders, and conditions for each process. It also includes business rules governing booking, documentation, operational, security, access, and compliance requirements. The document emphasizes the importance of accurate data entry, timely updates, and adherence to regulations throughout the logistics process.

Uploaded by

shreya.jaiswal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

1.

Useful Reservation for the Application Case


UC-001, Application Ed.

Container Mail Order Reservation Application Name: Actor Priority:


High Stakeholders: Warehouse Manager, Logistics Operator, and
Sender; Desired Conditions:
1. The user's system registration details are accurate.
2. The user has a system registration.
3. Details about the container are accessible.
Trigger: The container must be transported by the sender from its
point of origin to its destination.
Fundamental flow:
1. Users will be taken to Dashboard's Programs section.
2. The "Buchen New Shipment" button is clicked by users.
3. Users will supply information about the containers' identification (ID,
size, kind, and weight).
4. The user chooses the contents of the container and notes if any
hazardous materials are present.
5. The user has chosen an input address or dropdown menu.

6. The user inputs the address or chooses from a dropdown menu to


enter the origin location.
7. The user inputs the address or chooses from a dropdown menu to
enter the destination location.
8. Using a calendar picker, the user chooses the preferred pickup time
and date.

9. If applicable, the user enters the delivery deadline.


10. The system verifies all data supplied. 11. The system looks for
available routes and modes of transportation.
12. The system shows the projected time of delivery and the
breakdown of costs.
13. The user hits "Confirm Booking" after reviewing the facts.
14. The system asks for more confirmation.
15. The user validates the final reservation;

16. The system creates a special shipping reference number;

17. The system emails or SMS the user the booking confirmation.
18. The system alerts warehouse managers and pertinent logistics
operators.
An alternate flow:

: Inaccurate container information


1. Invalid Red Field

2. For every invalid field, the system shows a distinct error message.
3 After updating the data, the user proceeds from step 10

A2: No routes available.


1. You are unable to locate the appropriate path for your particular data in
step 11.

2. System displays message: "No available routes for selected dates"

3. System suggests 3 alternative date options with available routes

4. Users select an other day or cancel their reservation 5. After choosing a


different date, proceed to Step 12

3: Dangerous Materials.
1. The user displays the hazardous content in step 5.

2. Additional hazardous materials are shown by the system on

3. Users end with a Declaration of Dangerous Materials.


4. Special handling requirements are added by the system.
5. Up until step 6, the river keeps flowing.
Outstanding level: System timeout (e1)
1. The system won't react for 30 seconds in a single step.
2. Users will be prompted to contact or worry again.
4. The reservation information will be saved as a draft if step 4 is finished.
fig 1 ( USED CASE 1)

Detailed Use Case 2: Container Tracking and Monitoring

Use Case ID: UC-002


Use Case Name: Container Tracking and Monitoring
Actor(s): Shipper, Customer, Logistics Operator, Warehouse Manager
Priority: High
pre condition :
1. The user's system registration details are accurate.
2. The reference number and shipping charges are reserved.

3. There are GPS and IoT tracking sensors in the container.


Trigger: Users must verify the container storage's location or condition.

The "Submit Program" area will be the next page users see.

2. From the list of running apps, users input a shipment reference number.

3. The system uses GPS and Internet of Things devices to retrieve real-
time tracking data.

4. The system displays an interactive map showing the current container


location.

5. The system shows the location of the container as of right now on an


interactive map. System shows comprehensive status panel with:

o Current location (city, facility, GPS coordinates)


o Current status (in transit, at warehouse, customs check, etc.)
o Estimated time of arrival
o Temperature and condition readings (if applicable)
o Last five checkpoint entries with timestamps
6. Users have the option to choose between Timeline View and Card
View.
7. Users can view comprehensive status information by selecting
particular checkpoints.
8. Users have the option to get status alerts by push notifications,
SMS, or email.
ALTERNATIVE FLOW
1 Step 3 cannot call real-time data.
2. The system displays the most recent status and location
. 3. A warning message with the timestamp of the most recent
update will be shown by the system.
4. The automated data recovery procedure is initiated by the
system.
5. Users have the option to restore the original data or not.
All cargo Logistics Shipment Management
System - Business Rules
1. Booking and Scheduling Rules
Rule Exception
ID Rule Description Trigger Event Constraints s
Emergenc
y
shipment
s with
All the shipment System rejects manager
bookings must be made bookings with less approval
BR- at least 24 hours before than 24-hour on (code:
001 pickup time Shipment bookings notice EMG)
Custom
Container specifications Width, height, container
must be validated length must s require
BR- against international Container details confront iso specially
002 standards entries standards approved
Priorities customers Automatically
(Gold, Platinum tier) flags for
BR- receive expedited Customer expedited
003 processing classification checks processing No(none)
System requires Governm
Maximum booking value approval for ent
BR- without manager amounts > contracts
004 approval is $50,000 Cost calculation $50,000 exempt
Corporate
accounts
with bulks
Single shipments There are System shipping
BR- bookings cannot exceed Containers count the limits entry to 10 agreemen
005 10 containers validation containers ts
1.Documentation Rules
Rul Trigger
e ID Rule Description Event Constraints Exceptions
All customs Same-day
documents must be System processings
submitted 48 hours Docmentatio alerts users available
BR- before border n deadline approachin with 50%
006 crossing check g deadlines surcharge
Additional
forms auto-
generated
Hazardous materials Hazardous when
BR- require specialized materials hazardous
007 documentation flag flag is set None
Hardcopy
Document emergency
signatures must be Rejects backups in
BR- digital or verified Signature unverified system
008 with government ID validation signatures outage
System
archivs all Legal hold
documentat overrides
BR- Document retention Document ion for 7 standard
009 period is 7 years archiving years retention

English-only
when
Documents must be destination
available in English Translation accepts
BR- plus destination Document verification English
010 country language procesing required documents

2.Operational Rules
Rul
e ID Rule Description Trigger Event Constraints Exceptions
Manual entry
with supervisor
Containers must be Scan required override in case
BR- scaned at every Checkpoint before status of scanner
011 checkpoint arrival update failure
Perishable goods
Warehouse storage get temperature- Pre-booked
BR- allocation prioritizes Storage controlled areas premium storage
012 perishable goods assignment first overrides
Transport Time-critical
assignments must Algorithm balances shipments
BR- optimize for both Transport cost versus time prioritize speed
013 cost and time planning factors over cost
Status updates Remote areas
must be recorded System alerts if with poor
BR- within 15 minutes of updates are connectivity get
014 occurrence Status change delayed 2-hour alowance
Route changes
require customer Automatic Automatic
BR- notification within 1 Route notification notification
015 hour modification triggered triggered
3.Security and Access Rules
Rul
e ID Rule Description Trigger Event Constraints Exceptions
User access levels Emergency
BR- determine data Role-based access access protocol
016 visibility System login control enforced with audit trail
All financial
transactions require 2FA required
BR- two-factor Payment regardless of
017 authentications processing amounts None
Container security Customs
seals must be Seal verification inspection with
BR- verified at each Container before proper
018 transfers handoff acceptances documentation
System logs must Comprehensive
BR-
track all user Any systems audit trail
019
actions action maintained None
Password reset
BR- requires manager IT security team
020 approval for admin Password reset Manager approval has override
accounts request workflowss capability
4.Compliance Rules
Rul
e ID Rule Description Trigger Event Constraints Exceptions
All operations must
comply with local
BR- transport Regulatory
021 regulations Route planning database checks None(no)
GDPR compliance Origin/ GDPR protocols
BR- required for EU- destination activated for EU
022 related shipment checkss shipments None(no)
Denied party
screening must be Automatic
BR- performed on all Customer screening against
023 customers onboarding watch lists None(no)
Environmental
impact reports Hazardous Emergency
BR- required for materials Report generation response
024 hazardous shipment shipment and filings situations
Data retention and
deletion follows Automatic deletion
BR- regulatory Data lifecycle after retention
025 requirements managements periods Legal hold

You might also like