Project: AI-Powered Project Manager Support Web Application

Project Overview: The goal of this project is to develop a web application that leverages the OpenAI API
and ChatGPT to provide comprehensive support to project managers. The application will allow users to
upload business cases in Word or PDF format, after which ChatGPT will analyze the business case and
generate various project management artifacts, including a project charter, project plan with tasks and
durations, resource allocation, risk assessment, and a stakeholder matrix.
User Stories:

1. As a project manager, I want to upload a business case document (Word or PDF or paste text) to
the application for analysis.

2. As a project manager, I want to ask questions about the uploaded business case to receive
relevant answers from ChatGPT.
3. As a project manager, I want ChatGPT to create a project charter based on the content of the
uploaded business case.

4. As a project manager, I want ChatGPT to generate a detailed project plan that includes tasks,
suggested durations, task dependencies, resource allocation based on the content of the
uploaded business case.

5. As a project manager, I want ChatGPT to identify potential risks associated with the project and
provide risk mitigation strategies based on the content of the uploaded business case.

6. As a project manager, I want ChatGPT to develop a stakeholder matrix based on the information
from the business case.
7. As a user, I want the application to provide a user-friendly interface for document upload,
interaction with ChatGPT, and accessing generated artifacts.

8. As a user, I want the application to export the artifacts in word and excel formats.

Functional Requirements:

1. User Authentication and Authorization:

• Users must be able to create accounts and log in securely.
• Administrator must administer users (approve, disable etc)
2. Document Upload and Analysis:
• Users should be able to upload Word or PDF business case documents.
• The application should use the OpenAI API and ChatGPT to analyze the document
content.
• ChatGPT should be able to answer questions posed by the user about the document.
• ChatGPT should be able to answer general questions posed by the user (irrelevant to the
document.
3. Project Charter Generation:
 • ChatGPT should extract key information from the business case to generate a project
charter.
• The project charter should include project objectives, scope, stakeholders, and high-
level deliverables.
4. Project Plan Generation:
• ChatGPT should use document information to create a detailed project plan.
• The project plan should include a list of tasks, suggested durations, and task
dependencies.
• The project plan should be exported in excel format
5. Resource Allocation:
• ChatGPT should allocate appropriate resources (personnel, equipment) to each task in
the project plan.
• Resource availability and constraints should be considered.
6. Risk Assessment and Mitigation:
• ChatGPT should identify potential project risks and provide strategies to mitigate them.
• Risks should be categorized, and their potential impacts should be outlined.
7. Stakeholder Matrix:
• ChatGPT should analyze the document to identify project stakeholders and their roles.
• A stakeholder matrix should be generated, indicating stakeholders' interests and levels
of influence.
8. User Interface:
• The application should have an intuitive and user-friendly interface for document
upload, interaction with ChatGPT, and accessing generated artifacts.
9. Subscription Plans:
• Users should be able to choose from different subscription plans (e.g., monthly,
annually).
• Each subscription plan should have a set of features and usage limits associated with it.
10. Payment Gateway Integration:
• Integrate a reliable payment gateway (e.g., Stripe, PayPal) to handle payment
transactions securely.
• Users should be able to enter their payment information (credit card, PayPal account,
etc.) during the subscription process.
11. Payment Processing:
• Once users subscribe to a plan, the application should process the payment and confirm
the successful transaction.
• For recurring subscription plans, automatic billing should be set up according to the
chosen billing cycle (monthly, annually).
12. Billing and Invoices:
• Users should be able to view their subscription details, billing history, and download
invoices.
• Invoices should include information about the subscription plan, billing period, and
amount paid.
13. Payment Reminders and Notifications:
• Send automated reminders to users before their subscription renewal dates.
 • Notify users about successful payments, failed transactions, or subscription changes via
email or in-app notifications.
14. Subscription Management:
• Users should be able to upgrade, downgrade, or cancel their subscription plans.
• Changes to subscription plans should take effect immediately or at the start of the next
billing cycle.
15. Payment Non-Functional Requirements:
16. Security:
• Payment information must be handled securely and in compliance with industry
standards (PCI DSS).
• Ensure that user-sensitive data (such as credit card details) is properly encrypted during
transmission and storage.
17. Reliability:
• The payment gateway integration should be robust, ensuring consistent and reliable
payment processing.
• Failed transactions should be appropriately handled, and users should receive clear
error messages.
18. Performance:
• Payment processing should not significantly impact the overall application performance.
• Ensure quick response times during payment interactions.
19. User Experience:
• The payment process should be intuitive and user-friendly, guiding users through the
subscription selection and payment steps.
20. Technologies:
21. Payment Gateway: Integrate a reputable payment gateway provider such as Stripe or PayPal.
22. Subscription Management: Use a backend system to manage user subscriptions, invoices, and
billing cycles.
23. Notifications: Implement email notifications and in-app alerts for payment-related events.

General Non-Functional Requirements:

1. Performance:

• The application should provide timely responses and artifact generation.

• Response times should not exceed a certain threshold (e.g., 3 seconds for questions, 10
seconds for artifact generation).

2. Security:

• User data and uploaded documents must be stored securely.

• Communication with the OpenAI API should be done over secure channels.

• SSL support

3. Scalability:
 • The application should be designed to handle multiple concurrent users.
• System performance should not degrade as user load increases.

4. Compatibility:

• The application should be accessible from different web browsers and devices (desktop,
tablet, mobile).

5. Hosting:

• Suggest hosting provider

Technologies:
• Frontend: JavaScript (React, or another modern frontend framework)

• Backend: Python (Django, Flask, or another suitable backend framework)

• Database: PostgreSQL or MySQL

• OpenAI API: Integration for ChatGPT interactions

• Document Parsing: Libraries for parsing Word and PDF documents

• Security: Encryption, HTTPS, authentication, and authorization mechanisms