Project Update: OpenCap UI and MusaCapital Backend Integration

[urbantech]

Current Status and Accomplishments

OpenCap UI (First Iteration)

• Components Created:
  • CapTable
  • Dashboard
  • LandingPage
• Testing:
  • Unit tests for each component (CapTable.test.js, Dashboard.test.js, LandingPage.test.js)
• Setup and Configuration:
  • Initial setup with React.js
  • Configurations using jest.config.js for testing
  • Basic styling and utility files included (App.css, index.css, reportWebVitals.js, setupTests.js, test-utils.js)
• Public Assets:
  • Static assets (favicon, HTML template, manifest file)
• Integration Plan:
  • The UI is designed to be integrated with the MusaCapital backend.

MusaCapital Backend

• Backend Structure:
  • Models: User, Stakeholder, ShareClass, Document
  • Controllers: documentController.js, stakeholderController.js, shareClassController.js, userController.js
  • Routes: documents.js, users.js, stakeholders.js, shareClasses.js
  • Tests: Comprehensive tests for models and routes (user.model.test.js, stakeholderRoutes.test.js, etc.)
• Setup and Configuration:
  • Configuration files (jest.config.js, package.json, package-lock.json)
  • Database connection setup (db.js)
• Version Control:
  • Git repository initialized with appropriate .gitignore
• Integration Plan:
  • The backend is prepared to handle requests from the OpenCap UI.

---

Completed Backlog

User Management

• Add a New Stakeholder
  • Story: As a user, I want to add a new stakeholder in a standardized format so that I can keep the cap table consistent with OCTA standards.
  • Acceptance Criteria: User can input stakeholder details following the OCTA data schema. The new stakeholder appears in the stakeholders' list with standardized attributes.
• Edit Stakeholder Information
  • Story: As a user, I want to edit stakeholder information using OCTA-compliant fields so that I can correct or update their details accurately.
  • Acceptance Criteria: User can edit existing stakeholder details using standardized fields and save changes. The updated information is reflected in the stakeholders' list.
• Remove a Stakeholder
  • Story: As a user, I want to remove a stakeholder and ensure the cap table reflects this change according to OCTA guidelines.
  • Acceptance Criteria: User can delete a stakeholder. The stakeholder is removed from the list, and ownership percentages are recalculated to maintain data integrity per OCTA standards.

Cap Table Management

• Add New Share Class
  • Story: As a user, I want to add a new share class using OCTA-defined attributes so that I can account for different types of shares in the cap table.
  • Acceptance Criteria: User can input details for a new share class using OCTA-compliant fields, which is then displayed in the cap table summary.
• Edit Share Class Details
  • Story: As a user, I want to edit share class details using OCTA-compliant fields so that I can update information about the shares.
  • Acceptance Criteria: User can modify existing share class details using standardized fields and save changes, which are reflected in the cap table summary.
• Remove Share Class
  • Story: As a user, I want to remove a share class and ensure the cap table updates according to OCTA guidelines.
  • Acceptance Criteria: User can delete a share class, and the cap table summary updates accordingly, maintaining compliance with OCTA standards.

Document Management

• Upload Documents with Metadata
  • Story: As a user, I want to upload documents with metadata compliant with OCTA standards so that I can keep all related files in one place and ensure interoperability.
  • Acceptance Criteria: User can upload documents with OCTA-compliant metadata, which are listed in the recent activities feed.
• View Uploaded Documents
  • Story: As a user, I want to view uploaded documents in a secure and OCTA-compliant manner so that I can access important files easily.
  • Acceptance Criteria: User can click on a document from the list and view its contents in an OCTA-compliant format.
• Delete Documents
  • Story: As a user, I want to delete documents and ensure that document management complies with OCTA standards.
  • Acceptance Criteria: User can delete a document, and it is removed from the list in a manner that maintains compliance with OCTA standards.

---

Updated Backlog

Cap Table Management

• View Cap Table Summary
  • Story: As a user, I want to view a summary of the company's cap table in an OCTA-compliant format so that I can see an overview of ownership and share distribution.
  • Acceptance Criteria: User can see a summary including total shares, diluted shares, and amount raised, along with a visual representation of ownership distribution, all formatted according to OCTA standards.

Activity Feed

• View Recent Activities
  • Story: As a user, I want to see recent activities in an OCTA-compliant format so that I can stay informed about the latest changes and updates.
  • Acceptance Criteria: Recent activities such as document uploads are listed with timestamps and follow OCTA standards for activity tracking.

Equity Plans

• Manage Equity Plans
  • Story: As a user, I want to manage equity plans using OCTA-compliant fields so that I can keep track of various equity distributions accurately.
  • Acceptance Criteria: User can create, edit, and delete equity plans using standardized fields. Equity plans are integrated into the cap table summary in compliance with OCTA standards.

Fundraising

• Track Fundraising Rounds
  • Story: As a user, I want to track fundraising rounds using OCTA-defined attributes so that I can monitor the financial health and growth of the company.
  • Acceptance Criteria: User can input details of fundraising rounds using OCTA-compliant fields, which are reflected in the amount raised and cap table summary.

Security and Compliance

• Ensure Data Security
  • Story: As a user, I want my data to be secure and compliant with OCTA standards so that I can ensure confidentiality and integrity of company information.
  • Acceptance Criteria: The system uses data encryption, secure access controls, and follows OCTA guidelines for data security and compliance.

Usability and Performance

• User-Friendly Interface
  • Story: As a user, I want the interface to be user-friendly and compliant with OCTA standards so that I can navigate and use the system efficiently.
  • Acceptance Criteria: The UI is intuitive with consistent design patterns and responsive performance, adhering to OCTA usability guidelines.
• Efficient System Performance
  • Story: As a user, I want the system to load quickly and handle data efficiently in a manner compliant with OCTA standards so that I can access information without delays.
  • Acceptance Criteria: The system should have fast load times and handle large datasets efficiently, following OCTA performance standards.

Documentation

• Complete API Documentation
  • Story: As a developer, I want comprehensive API documentation using Swagger so that I can easily understand and integrate with the API.
  • Acceptance Criteria: API endpoints are fully documented with descriptions, request/response examples, and authentication details.
• Finalize User and Developer Guides
  • Story: As a user, I want detailed user and developer guides so that I can effectively use and contribute to the system.
  • Acceptance Criteria: Guides cover all functionalities, setup, and troubleshooting steps.
• Ensure Setup and Deployment Documentation
  • Story: As a developer, I want complete setup and deployment documentation so that I can efficiently deploy the application.
  • Acceptance Criteria: Documentation includes setup instructions, environment configuration, and deployment steps.

---

Current Priorities

1. View Cap Table Summary
2. View Recent Activities
3. Manage Equity Plans
4. Track Fundraising Rounds
5. Ensure Data Security
6. User-Friendly Interface
7. Efficient System Performance
8. Complete API Documentation
9. Finalize User and Developer Guides
10. Ensure Setup and Deployment Documentation