Week 12 Worklog
03/07/2026
Work Completed
- Started consolidating the final project documentation for LiveCap.
- Reviewed all work completed from the requirements analysis phase through system deployment.
- Updated the main documents: problem statement, project objective, functional requirements, non-functional requirements, and system overview.
- Verified consistency between the original requirements, system architecture, and implemented features.
Results Achieved
- The project documentation had a clearer and more organized structure.
- The requirements description and MVP scope sections were finalized.
- The report content accurately reflected the project development process from analysis to implementation.
04/07/2026
Work Completed
- Completed the system design section of the documentation.
- Updated use cases, activity diagrams/BPMN, data flow diagrams, and the overall LiveCap architecture.
- Reviewed the data model covering session, transcript segment, speaker, translation, and export file entities.
- Added explanations of each system component’s role.
Results Achieved
- The system design documentation was more complete and easier to understand.
- Clarified how users interact with the system and how data flows through each component.
- Established a stronger foundation for presenting the project from a BA/SA perspective, not just a development one.
05/07/2026
Work Completed
- Re-tested the core features of LiveCap.
- Executed key test cases: start session, grant microphone permission, receive captions, translate content, end session, export transcript, and error handling.
- Updated the UAT checklist and recorded test results.
- Noted remaining issues and how they are handled or constrained within the MVP scope.
Results Achieved
- Completed the test suite and UAT documentation for the system’s main flows.
- Confirmed which features meet the MVP requirements.
- Established a basis for evaluating the project’s completeness before the demo.
06/07/2026
Work Completed
- Reviewed the operational aspects of the system on AWS.
- Re-checked sections related to IAM, S3 storage, CloudWatch logging, HTTPS/WSS, and deployment configuration.
- Added content on security, monitoring, cost optimization, and system limitations to the documentation.
- Prepared an explanation for why the team uses AWS managed services instead of training custom AI models.
Results Achieved
- The cloud architecture documentation was more complete.
- Key technical decisions of the project were clearly articulated.
- The report covered not only system functionality but also operational aspects such as security, monitoring, and cost.
07/07/2026
Work Completed
- Consolidated each team member’s contributions.
- Updated the individual contribution section for the Information Systems role: requirements analysis, process design, data modeling, KPIs, UAT, and system documentation.
- Reviewed the deliverables to submit: worklog, report, system documentation, source code, demo flow, and workshop/project content.
- Revised the report content to unify terminology and timeline from Week 1 through Week 12.
Results Achieved
- Individual and team roles were presented more clearly.
- The worklog and report were consistent with the actual process: Weeks 1–6 for AWS self-study, Weeks 7–12 for LiveCap implementation.
- The main documentation sections were nearly complete for final submission.
08/07/2026
Work Completed
- Completed the final review of the entire LiveCap project.
- Re-tested the demo flow from start to finish to ensure it could be presented clearly.
- Reviewed minor errors in documentation, architecture diagrams, test case tables, and AWS service descriptions.
- Updated the limitations and future improvements section for the project.
Results Achieved
- The demo flow was clearer and easier to present.
- The final project documentation was refined in both content and presentation quality.
- The project included an honest assessment of limitations and a direction for future development, making the report more credible.
09/07/2026
Work Completed
- Finalized all remaining project documents.
- Reviewed the full report, worklog, system documentation, and personal summary section.
- Prepared the final version for submission and presentation.
- Summarized the knowledge, skills, and experience gained throughout the internship.
Results Achieved
- Completed the full set of end-of-term deliverables for the LiveCap project.
- Produced a clear summary of the AWS learning journey and the real-world project implementation process.
- Ready for the final demo, submission, and end-of-term evaluation.
Weekly Summary
In the final week, the team focused on completing documentation, testing, the demo flow, and all end-of-term deliverables for LiveCap. Key work included updating requirements documentation, system design, use cases, data models, KPIs, the UAT checklist, AWS architecture, security/monitoring/cost optimization sections, and each member’s individual contributions. I learned that completing a project means more than finishing the technical implementation — it also requires presenting it clearly, documenting it thoroughly, and evaluating it honestly. Through the Information Systems role, I gained a deeper appreciation for the importance of connecting business requirements, system design, data modeling, KPIs, UAT, and real-world implementation into a coherent whole. After 12 weeks — six weeks of AWS self-study and six weeks of implementing LiveCap — I came away with practical experience in building a cloud-based application using real-time processing, AWS managed services, storage, monitoring, security, and organized documentation practices.