KPI Business Requirements & Software Requirements Specification
From UG
(→Phase I - Core KPI Framework (gaps in Cost-Based KPIs)) |
(→Assumptions / Constraints) |
||
| Line 101: | Line 101: | ||
Assumptions | Assumptions | ||
* The KPI module will not require significant redeisgn within the next 3 years. | * The KPI module will not require significant redeisgn within the next 3 years. | ||
| - | * Critical resources (0.5 FTE Analyst and 1 FTE Developer) will be available for entire duration of | + | * Critical resources (0.5 FTE Analyst and 1 FTE Developer) will be available for entire duration of this project. |
* All major requirements would have been identified during the requirements/design phase of this project. | * All major requirements would have been identified during the requirements/design phase of this project. | ||
* Project Team will document & provide walkthrough of entire KPI design prior to construction. | * Project Team will document & provide walkthrough of entire KPI design prior to construction. | ||
| Line 113: | Line 113: | ||
* All in-scope KPIs must be delivered and fully functional by end of year 2012. | * All in-scope KPIs must be delivered and fully functional by end of year 2012. | ||
* Entire KPI project must be delivered with limited resources (0.5 FTE Analyst & 1 FTE Developer). | * Entire KPI project must be delivered with limited resources (0.5 FTE Analyst & 1 FTE Developer). | ||
| - | * | + | * |
== Business Requirements == | == Business Requirements == | ||
Revision as of 00:24, 10 April 2012
Mantis
<Mantis Number(s) & Link>
Project Overview
Business Objective(s)
Key Performance Indicators (KPIs) are valuable metrics that clients and Jaguar Freight Services (JFS) can utilize to improve their supply chain management operations. These metrics report on cost performance, cycle time performance, load utilization performance, etc.. Examples include cost per pound, cycle time between shipment creation to approval, etc.. There are an infinite number of possibilities for what one might consider a KPI. It is up to the client and/or JFS management team to utilize these KPIs to identify weak areas of their operations and to develop strategic corrective action plans to improve logistics performance.
The objective of the CyberTrax2 KPI project is to provide an easy to use, intuitive, interactive interface for both internal JFS management and external client users to view and report on KPIs. It is absolutely imperative that the accuracy and mechanics of KPIs are well understood by all.
High Level Project Deliverables
- KPI Dashboards
- Multi-Level Interactive KPI Charts & Graphs
- KPI Entitlements Management
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
- Mihail Tymoshenko - CT2 Software Developer (Elcosol)
- Denise Guastella - CT2 Support Manager
- Kostiantyn Ushakov - CEO/CTO Elcosol
- Perry Lee - CT2 Project Manager
Project Scope
The below items are in-scope for this KPI project:
- Design and implement a scalable KPI module that will satisfy all future KPI requirements for at least the next 3 years.
- Design must take into consideration future KPIs requirements (Mobile, International, External Interfaces [Google Maps], etc..)
- Fill in existing gaps (functional & non-functional) in existing cost-based KPI module.
- Design and Implement a KPI module for both Internal CT2 and Client CT2 applications.
- Implement below KPIs
- Cost-Based KPIs (gaps only)
- Date-based KPIs
- Utilization/Optimization-based KPIs
- International KPIs
- Ocean (FCL & LCL)
- Air
- Ability to overlap & report on multiple KPIs.
- Design and implement an entitlements management module to administer KPI-based entitlements. This specific KPI entitlements management module will need to fall in line with I-Portal entitlements management framework.
The below items are out-of-scope for this KPI project:
- Address performance issues with any CT2 module outside of KPI.
- Merge Internal CT2 and Client CT2 applications.
- Mobile KPI
Project Dependencies
- I-Portal Entitlements Management Framework must be designed prior to designing KPI Entitlement Management module.
High-Level Timelines
This project will be delivered in phases.
Phase I - Core KPI Framework / Address gaps in Cost-Based KPIs
Requirements
Design
Construction
Verification
Maintenance
Phase II - Date-Based KPIs
Requirements
Design
Construction
Verification
Maintenance
Phase III - Utilization/Optimization KPIs
Requirements
Design
Construction
Verification
Maintenance
Phase IV - International
Requirements
Design
Construction
Verification
Maintenance
Risks
<Identify internal and external risks to the project: schedule, resources, technical, business, cost, market conditions, external vendors/partners, etc..>
Assumptions / Constraints
Assumptions
- The KPI module will not require significant redeisgn within the next 3 years.
- Critical resources (0.5 FTE Analyst and 1 FTE Developer) will be available for entire duration of this project.
- All major requirements would have been identified during the requirements/design phase of this project.
- Project Team will document & provide walkthrough of entire KPI design prior to construction.
- QA resource will be fully allocated to this project during verfiication phase(s).
- Business unit will have adequate resources to perform UAT during verification phase(s).
- Current CT2 Chart & Graph library (JFreeChart) is adequate enough to satisfy existing & future KPI requirements.
Constraints
- KPI module must not negatively impact the current performance of CyberTrax2.
- KPI module must function under existing production server hardware.
- All in-scope KPIs must be delivered and fully functional by end of year 2012.
- Entire KPI project must be delivered with limited resources (0.5 FTE Analyst & 1 FTE Developer).
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)>
