KPI Business Requirements & Software Requirements Specification

From UG

(Difference between revisions)
Jump to: navigation, search
(Created page with 'Category:DRs and KPIs')
Line 1: Line 1:
[[Category:DRs and KPIs]]
[[Category:DRs and KPIs]]
 +
 +
== Mantis ==
 +
''<Mantis Number(s) & Link>''
 +
 +
== Project Overview ==
 +
=== Business Objective(s) ===
 +
Key Performance Indicators (KPIs) are invaluable 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.. The list of possible KPIs are endless. 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 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 ===
 +
* Dashboard Reports
 +
* Multi-Level Interactive Charts & Graphs
 +
* Entitlements Management
 +
 +
=== Project Stakeholders ===
 +
* Simon Kaye - CEO - Project Sponsor
 +
* Marc Selter - VP - Product Management
 +
* Alex Dobrovolsky - Director of Technology
 +
* Montira Renfrew - Systems Analyst
 +
* Mihail Tymoshenko - Software Developer
 +
* Denise Guastella - Support Manager
 +
* Perry Lee - Project Manager
 +
 +
=== Project Scope ===
 +
''<Identify in-scope and out-of-scope items>''
 +
 +
=== 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)> ''

Revision as of 21:24, 9 April 2012


Contents

Mantis

<Mantis Number(s) & Link>

Project Overview

Business Objective(s)

Key Performance Indicators (KPIs) are invaluable 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.. The list of possible KPIs are endless. 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 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

  • Dashboard Reports
  • Multi-Level Interactive Charts & Graphs
  • Entitlements Management

Project Stakeholders

  • Simon Kaye - CEO - Project Sponsor
  • Marc Selter - VP - Product Management
  • Alex Dobrovolsky - Director of Technology
  • Montira Renfrew - Systems Analyst
  • Mihail Tymoshenko - Software Developer
  • Denise Guastella - Support Manager
  • Perry Lee - Project Manager

Project Scope

<Identify in-scope and out-of-scope items>

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)>

Retrieved from "https://wiki.jaguarfreight.com/KPI_Business_Requirements_%26_Software_Requirements_Specification"
Personal tools