I-Portal REQUIREMENTS
From UG
(→Introduction) |
(→Functionality Overview) |
||
| Line 12: | Line 12: | ||
== Functionality Overview == | == Functionality Overview == | ||
| + | |||
| + | == QUESTIONS == | ||
| + | Admin Panel: | ||
| + | |||
| + | Q1. I-portal and ASN are separated? | ||
| + | :* Roles:Iportal: Shipper and planner | ||
| + | :** MOT: Air and Ocean | ||
| + | :** E0: Elizabeth Arden? | ||
| + | :* Roles:Truck-Dom: Shipper and Planner | ||
| + | :** MOT: Truck Dom | ||
| + | :** E0: EA DOM PORTAL | ||
| + | |||
| + | Q2, If it does, how? what is the process? Will we change the current business process for EA DOM? If it does not, THEN? | ||
| + | |||
| + | Q3, Shipper Role: | ||
| + | :* one:one? for Shipper: EO.client Company? | ||
| + | |||
| + | Q4. | ||
== Core International Shipper == | == Core International Shipper == | ||
Revision as of 14:25, 29 May 2012
Mantis
Introduction
The primary objective of International Portal (I-Portal) is to create a platform for CyberTrax2 to transform into Software-As-A-Service (SaaS) system that Jaguar Freight Services can offer as a fee-based service to external clients. Clients would be able to manage all aspects of their shipments from within CyberTrax2 for both domestic and international shipments. The portal should provide client users with the ability to create shipments, approve shipments, track shipments, etc.. This will streamline a business process of submitting and approving shipments and seamless communication at Elizabeth Arden. It is proposed to provide a web portal. Required software is a tool that allow a supplier to enter an Elizabeth Arden international traffic order.
The portal must be web accessible, secure, user-friendly, flexible, and scalable. The portal must also take into account data visibility rules (Clients will only be able to edit/view their own data) and system performance. This portal is mimic from ASN portal (Trucking domestic portal for Elizabeth Arden)
There are a number of features that should be postponed and released in phase two. This was done to launch international portal with core features as soon as possible.
Functionality Overview
QUESTIONS
Admin Panel:
Q1. I-portal and ASN are separated?
- Roles:Iportal: Shipper and planner
- MOT: Air and Ocean
- E0: Elizabeth Arden?
- Roles:Truck-Dom: Shipper and Planner
- MOT: Truck Dom
- E0: EA DOM PORTAL
- Roles:Iportal: Shipper and planner
Q2, If it does, how? what is the process? Will we change the current business process for EA DOM? If it does not, THEN?
Q3, Shipper Role:
- one:one? for Shipper: EO.client Company?
Q4.
Core International Shipper
High Level Deliverables
- Flexible Entitlements Management System
- User Interface Templates
- Client Specific Reporting
- Optimize current CT2 Client performance
Project Stakeholders & Roles
- Simon Kaye - CEO - Project Sponsor
- Marc Selter - VP - Product Manager
- Alex Dobrovolsky - Director of Technology - Solutions Architect
- Montira Renfrew - CT2 Systems Analyst/ CT2 Project manager
- Alex Pivniak - CT2 Software Developer (Elcosol)
- Denise Guastella - CT2 Support Manager
Project Scope
<Identify in-scope and out-of-scope items>
Out-Of-Scope
- SAS 70 & ISO27001 Compliance
- Web Application Penetration Tests
- High Availability (HA) Disaster Recovery environment(s)
- 100% integration of both Internal CT2 & Client CT2
- Functional & Non-Functional gaps in Internal CT2
Project Dependencies
<Identify internal and external dependencies to the project>
High-Level Timelines
<High-level milestone dates>
Risks
<Identify internal and external risks to the project: schedule, resources, technical, business, cost, market conditions, external vendors/partners, etc..>
Assumptions / Constraints
<Identify all assumptions and constraints for this project>
Business Requirements
<List each business requirement under a separate heading. Also include process flows (UML, Sequence Diagrams, Swimlane, Flow chart, etc..) as applicable>
Business Requirement 1...
Business Requirement 2...
Business Requirement 3...
Business Process Flow 1...
Business Process Flow 2...
Business Process Flow 3...
Functional/Non-Functional Requirements
<Identify all functional and non-functional requirements. Maintain standard headings. If a specific requirement is not required, note as Not Applicable. Each functional requirement must trace back to a specific business requirement.>
CyberTrax2 Internal Application
<Identify all functional requirements for CT2 Internal Application>
User Interface Requirements
Reporting Requirements
User Access / Security Requirements
Logging Requirements
Group / Master Requirements
Filtering Requirements
Archiving Requirements
CyberTrax2 Client Application
<Identify all functional requirements for CT2 Client Application>
User Interface Requirements
Reporting Requirements
User Access / Security Requirements
Logging Requirements
Group / Master Requirements
Filtering Requirements
Archiving Requirements
Non-Functional Requirements
<Identify all non-functional requirements for both CT2 Client Application and CT2 Internal Application>
Performance Requirements
Capacity Requirements
Support / Maintenance Requirements
User Guides
Training
Log(s) Accessibility
Testing Requirements
Security Requirements
Technical Design & Solution
Mock ups
<Include mock-ups of UI changes, report changes, etc..>
Technology Stack & Architecture
<Include changes to existing Technology Stack & Architecture - new libraries, updated library versions, new software/hardware, new interfaces, etc..>
Technical Diagrams (Flow Chart, Sequence, UML, Systems Architecture, Technical Architecture, Data Architecture, etc..)
<Include architecture diagrams and flow charts>
Web / Application (New/Modified classes, methods, etc..)
<List new or modified classes and methods>
Database (DDL changes - new/modified tables, indexes, stored procedures, etc..)
<Summarize database changes>
Configuration (Config File changes)
<Summarize config changes>
Logging (Log File changes)
<Summarize Log File changes and locations>
External Interfaces (EDI Message(s), external vendors)
<Identify any new external interfaces. Include sample request and reply along with field definitions. Include Source/Target server(s)/webservice(s) and functional accounts. If this is a modification of an existing EDI message, include samples of current message(s) and new message(s)>
