WBS for porfolio site

[soraraso42]

1. Project Initiation

1.1 Define project objectives

• 1.1.1 Identify primary goals (showcase skills, attract employers)
• 1.1.2 Define success metrics (visits, interview offer) 1.2 Identify stakeholders
• 1.2.1 List primary stakeholders (me, peers)
• 1.2.2 Determine feedback channels (virtual and in-person chats) 1.3 Gather requirements
• 1.3.1 Document functional requirements (CRUD operations, Q&A listing) - 1.3.2 Document non-functional requirements (performance, security)

2. Planning

2.1 Create project timeline

• 2.1.1 Break down tasks into phases
• 2.1.2 Assign estimated durations for each task 2.2 Define resource allocation
• 2.2.1 Identify required tools (IDE, Azure, GitHub)
• 2.2.2 Determine any needed mentorship or guidance 2.3 Establish risk management plan
• 2.3.1 Identify potential risks (technical, timeline)
• 2.3.2 Develop mitigation strategies

3. Design

3.1 UI/UX Design

• 3.1.1 Wireframe creation
  • 3.1.1.1 Sketch initial layouts for home, joke list, forms, etc.
  • 3.1.1.2 Review and iterate based on feedback
• 3.1.2 Visual design mockups
  • 3.1.2.1 Choose Bootstrap theme, color scheme, and typography
  • 3.1.2.2 Create high-fidelity mockups using Figma or similar tool 3.2 Database Schema Design
• 3.2.1 Define tables for jokes
  • 3.2.1.1 Create table for jokes (ID, setup, reveal, keywords)
  • 3.2.1.2 Define relationships (if necessary)
• 3.2.2 Define user data structure
  • 3.2.2.1 Design table for user profiles (ID, name, email)
  • 3.2.2.2 Plan user authentication requirements (if needed)

4. Development

4.1 Frontend Development (Razor Views + Bootstrap)

• 4.1.1 Set up ASP.NET Core MVC with Razor Views
  • 4.1.1.1 Create project structure
  • 4.1.1.2 Install necessary packages (e.g., Bootstrap, jQuery)
• 4.1.2 Implement joke listing page
  • 4.1.2.1 Create Razor view for displaying jokes
  • 4.1.2.2 Add pagination or filtering options using plain JS
• 4.1.3 Implement joke creation/modification forms
  • 4.1.3.1 Design Razor form for adding/editing jokes
  • 4.1.3.2 Use Bootstrap for form layout and JS for validation
• 4.1.4 Implement search functionality
  • 4.1.4.1 Add search input field using Razor views
  • 4.1.4.2 Use plain JS to filter search results dynamically 4.2 Backend Development
• 4.2.1 Set up SQL Server database
  • 4.2.1.1 Install and configure SQL Server or use Azure SQL
  • 4.2.1.2 Create database and necessary tables
• 4.2.2 Create API endpoints for CRUD operations
  • 4.2.2.1 Implement GET, POST, PUT, DELETE methods for jokes
  • 4.2.2.2 Test endpoints with Postman or similar
• 4.2.3 Implement authentication (optional)
  • 4.2.3.1 Decide on authentication method (JWT, OAuth, Identity)
  • 4.2.3.2 Develop login/logout functionality if needed 4.3 Integration
• 4.3.1 Connect frontend to backend
  • 4.3.1.1 Ensure Razor views consume API data correctly
  • 4.3.1.2 Handle form submissions and display responses
• 4.3.2 Test API integrations
  • 4.3.2.1 Perform integration tests to ensure frontend-backend communication
  • 4.3.2.2 Fix any issues that arise

5. Testing

5.1 Unit Testing

• 5.1.1 Write unit tests for individual components (backend, forms)
• 5.1.2 Use a testing framework (e.g., xUnit for backend) 5.2 Integration Testing
• 5.2.1 Test interactions between Razor views and API endpoints
• 5.2.2 Validate database interactions and ensure data persistence 5.3 User Acceptance Testing (UAT)
• 5.3.1 Create test scenarios for joke creation, listing, and search
• 5.3.2 Gather feedback from test users

6. Deployment

6.1 Set up Azure environment

• 6.1.1 Create Azure account and resource group
• 6.1.2 Set up Azure App Service for hosting
• 6.1.3 Set up Azure SQL or configure local SQL Server to Azure SQL migration 6.2 Deploy application to Azure
• 6.2.1 Push code to Azure using Git or Azure CLI
• 6.2.2 Configure application settings in Azure (e.g., environment variables) 6.3 Configure CI/CD with GitHub Actions
• 6.3.1 Create workflow file for CI/CD with GitHub Actions
• 6.3.2 Test CI/CD pipeline for successful deployments

7. Documentation

7.1 Create user documentation

• 7.1.1 Write instructions on how to use the site (e.g., joke creation, search)
• 7.1.2 Include troubleshooting tips for common user issues 7.2 Create technical documentation
• 7.2.1 Document project structure, Razor view layouts, and API endpoints
• 7.2.2 Include API documentation using Swagger or a similar tool 7.3 Update resume and portfolio content
• 7.3.1 Write a case study about the project
• 7.3.2 Prepare to showcase the site in interviews

8. Review and Feedback

8.1 Collect feedback from peers and mentors

• 8.1.1 Present the project to peers for input and suggestions
• 8.1.2 Schedule feedback sessions with mentors 8.2 Implement improvements based on feedback
• 8.2.1 Prioritize feedback for implementation
• 8.2.2 Update project based on suggestions

9. Maintenance

9.1 Monitor application performance

• 9.1.1 Set up monitoring tools (e.g., Azure Monitor, Application Insights)
• 9.1.2 Analyze performance metrics and address any bottlenecks 9.2 Regularly update content and features
• 9.2.1 Refresh jokes and personal content periodically
• 9.2.2 Consider adding new features based on user feedback

---

resources used:

https://learn.microsoft.com/en-us/azure/app-service/tutorial-dotnetcore-sqldb-app?tabs=copilot&pivots=azure-portal