In Scope:

• Table Creation:
• • Asset_Financials table with fields: AssetID, PurchaseCost, DepreciationRate, CurrentValue, BudgetCode.
• • Expenditure_Tracking table with fields: ExpenseID, AssetID, ExpenseType, Amount, DateOfExpense.
• • The vendor_Payment table has fields: PaymentID, VendorID, AmountPaid, and PaymentDate.
• Relationships:
• • Establish foreign key relationships between Asset_Financials and Expenditure_Tracking tables.
• • Link the Vendor_Payment table with the Vendor_Management table using foreign keys.
• Basic SQL Queries:
• • Queries to calculate the total value of all assets.
• • Queries to list all expenses associated with a specific asset.
• • Queries to find the total amount paid to vendors in the last quarter.
• Data Entry and Population:
• • Populate tables with sample data for financial analysis and testing.
• Group Project Deliverables:
• • Financial data schema design documents.
• • SQL scripts for table creation and data population.
• • Basic SQL query examples.

Out of Scope:

• Advanced financial analysis and modeling.
• Integration with financial management or ERP systems.
• Detailed financial reporting and visualization.
• Advanced security measures and compliance checks.

General Guidelines for All Projects

In Scope:

• Basic understanding and application of SQL for creating tables, defining relationships, and writing queries.
• Ensure data integrity and consistency through the use of primary and foreign keys.
• Populating tables with realistic sample data for demonstration and testing purposes.
• Document the database schema, including entity-relationship diagrams (ERDs) and a data dictionary.
• Weekly progress reports and discussions.
• Final group presentations and papers.

Out of Scope:

• Any advanced database management features such as high availability clustering or distributed databases.
• Integration with other systems or external APIs.
• Detailed performance testing, tuning, or optimization for production environments.

Phase 1: Project Initiation and Planning (Weeks 1-2)

• Objective: Establish the project foundation and define the scope.
• Activities:
  • Team formation and role assignment.
  • Development of the project team charter.
  • Setup of team collaboration space using OneDrive.
  • Initial project team introduction presentation.
  • Website setup on WordPress.
  • Database setup with PostgreSQL and PgAdmin.
  • Initial research and development of the business case.

Phase 2: Requirements Gathering and Analysis (Weeks 3-4)

• Objective: Identify and analyze project requirements.
• Activities:
  • Conduct stakeholder interviews and gather requirements.
  • Develop and refine the business case.
  • Create basic database design and data dictionary.
  • SWOT analysis to evaluate project strengths, weaknesses, opportunities, and threats.
  • Initial conceptual database schema design.
  • Mid-course peer review to assess progress and gather feedback.
  • Submit all assignments for weeks 1-4 before the course closure date.

Phase 3: Design and Development (Weeks 5-6)

• Objective: Design and develop the system architecture and database.
• Activities:
  • Develop data flow diagrams (DFD), business process diagrams (BPD), and use case diagrams.
  • Implement the database schema in PostgreSQL.
  • UI design and database development, including creating and refining user interface designs.
  • Continuously update the WordPress site to reflect project progress and documentation.

Phase 4: Testing, Integration, and Presentation (Weeks 7-8)

• Objective: Integrate, test, and present all system components.
• Activities:
  • Establish relationships between database tables and perform data integrity checks.
  • Conducted system integration testing to ensure all components worked together as expected.
  • Develop and finalize the implementation security plan.
  • Prepare for final project presentations by reviewing and practicing the presentation material.
  • Final adjustments to the database schema based on testing feedback.
  • Finalize project documentation and prepare for submission.
  • Final group presentation to showcase the project to instructors and peers.
  • Conduct a peer review to gather feedback on team performance.
  • Reflect on project lessons learned and submit a final evaluation.

A Work Breakdown Structure (WBS) is an essential project management tool that breaks down the entire scope of a project into smaller, more manageable tasks or work packages. Here are the key elements that should be included in the WBS for the GreenLeaf IT Asset Management System project:

Project Phases:

• Initiation: Includes tasks related to project approval, stakeholder identification, and the creation of initial project documentation.
• Planning: Tasks include defining the project scope, developing the project plan, creating the schedule, and identifying resources.
• Design: Tasks involved creating the system architecture, designing the user interface, and establishing the database schema.
• Development: Coding, database setup, integration of system components, and creating user documentation.
• Testing: Unit testing, system testing, user acceptance testing, and fixing any issues identified.
• Implementation: Final system deployment, user training, and transition to the live environment.
• Closure: Final project review, documentation handover, and project closure activities.

Major Deliverables:

• Project Charter: Document outlining the project's purpose, objectives, scope, and stakeholders.
• System Requirements Specification (SRS): A detailed document capturing all functional and non-functional requirements.
• System Design Document: Includes the finalized system architecture, database schema, and UI/UX design.
• Test Plan: Document outlining the testing strategy, test cases, and expected outcomes.
• Final System: The completed and tested IT Asset Management System, ready for deployment.
• User Training Materials: Guides, tutorials, and manuals for end-users and system administrators.
• Project Report: Comprehensive report summarizing the project, including all documentation, lessons learned, and recommendations for future projects.

Work Packages:

• Each phase and deliverable should be broken down into specific tasks, such as:
  • Planning: Task creation, timeline development, and resource allocation.
  • Design: Drafting initial designs, reviewing with stakeholders, and finalizing designs.
  • Development: Writing code, setting up databases, and integrating system components.
  • Testing: Creating test cases, executing tests, and resolving identified issues.
  • Implementation: Installing the system, conducting user training, and monitoring initial use.
• Assign responsibility for each work package to specific team members or sub-teams.

Dependencies:

• Identify and document dependencies between tasks, such as tasks that must be completed before others begin.
• Use these dependencies to determine the critical path and adjust the project schedule.

Milestones:

• Include major milestones in the WBS to mark key project points, such as the completion of the design phase, the beginning of user testing, or the final system deployment.

Finance Department:

Asset Depreciation Calculation Process

• Calculating annual depreciation for IT assets.
• Updating financial records with current asset values.
• Reporting depreciated values to management for financial planning.

Budget Tracking and Reporting Process

• Monitoring expenditures against allocated budgets.
• Updating budget records in real-time.
• Generating budget status reports for department heads and management.

Vendor Payment Processing

• Receiving and verifying invoices from IT vendors.
• Processing payments and updating the financial system.
• Archiving payment records and managing vendor relations.

Information for Key Project Aspects

Project Milestones: Greenleaf expects the following key milestones to help define the phases of the IT Asset Management System project:

Project Approval and Kickoff (Week 1):

• Approval of the project charter and scope, followed by a kickoff meeting with all stakeholders.
• Deliverable: Project Charter and Initial Project Plan.

Requirements Finalization (End of Week 3):

• Completion of the requirements gathering and analysis phase, with a final System Requirements Specification (SRS) document.
• Deliverable: System Requirements Specification (SRS) Document.

System Design Completion (End of Week 4):

• Finalization of the system design, including the architecture, UI/UX design, and database schema.
• Deliverable: System Design Document.

Development Phase Completion (End of Week 6):

• Completion of system development, including coding, database setup, and initial integration.
• Deliverable: Working Prototype of the IT Asset Management System.

Testing Completion (End of Week 7):

• Completion of all testing phases, including unit, system, and user acceptance testing, with all major issues resolved.
• Deliverable: Test Plan and Testing Report.

Final System Deployment (End of Week 8):

• Deployment of the final system in the live environment, along with user training and transition support.
• Deliverable: Deployed IT Asset Management System and User Training Materials.

Project Closure (Week 9):

• Final project review and closure, including submitting the final project report and documentation.
• Deliverable: Final Project Report and Project Documentation.

Resource Availability:

Team Members:

• Availability: The project team comprises members from various departments, including IT, Procurement, Finance, HR, and Facilities. Each team member must dedicate 10-15 hours per week to the project.
• Roles: Key roles include Project Manager, System Architect, Database Administrator, UI/UX Designer, and Test Lead. Each role is critical for the timely completion of specific project phases.
• Collaboration: Team members will primarily collaborate through online platforms (e.g., OneDrive, WordPress) and weekly progress meetings.

Budget Constraints:

• Initial Budget Allocation: GreenLeaf has allocated $130,000 to develop and deploy the IT Asset Management System. This includes software licenses, hardware, and training materials.
• Resource Allocation: The budget covers costs related to software development, database management, security implementation, and user training.
• Cost Monitoring: Regular budget reviews will ensure spending aligns with the project plan. The project sponsor must justify and approve any additional budget requests.

Other Resources:

• Software: The project will utilize PostgreSQL for database management, WordPress for documentation, and project management tools for scheduling and tracking progress.
• Hardware: GreenLeaf will provide the necessary hardware, including servers for the IT Asset Management System, ensuring that all system components are adequately supported.
• Training: GreenLeaf has committed resources to user training, including developing training materials and conducting training sessions for end-users and system administrators.