PharmaStock: Use Cases & User Focus

 Toward the end of the week, I focused on my assigned sections of the design document, specifically use cases and user characteristics. This was about thinking through how PharmaStock will actually be used day to day instead of just listing features.

I defined two main use cases:

  1. Managing medication inventory — adding medications, updating quantities, and keeping expiration data accurate.

  2. Responding to alerts and insights — reviewing low-stock and expiring medications and taking action before problems happen.

Both use cases are written from the perspective of a pharmacist or pharmacy technician, since those are the people using the system the most.

I also documented user characteristics to keep the project grounded. PharmaStock is designed for independent pharmacies, not large chains, so the users are usually working in small teams with limited time. That means the app needs to be straightforward, easy to read, and focused on surfacing important information quickly instead of overwhelming users with options.

This part of the work helped clarify what really matters for the app and will make it easier to decide what features belong in the MVP versus what can come later.

Comments

Post a Comment

Popular posts from this blog

PharmaStock: Backend Infrastructure & Database Connectivity

 This week marked the transition from planning and design into real backend development. After organizing the project structure and defining use cases in previous weeks, I focused on building the technical foundation that the rest of the application will depend on. The primary goal was completing SCRUM-16, which involved connecting the ASP.NET Core backend API to a MySQL database and verifying that the system could successfully generate and manage database tables. I began by configuring MySQL to run inside a Docker container. Using Docker ensures that every developer on the team works against the same database environment, which reduces setup inconsistencies and avoids the common “it works on my machine” problem. Once the container was running correctly, I verified that it could be started, stopped, and inspected reliably. Next, I integrated Entity Framework Core with the Pomelo MySQL provider and registered the DbContext within the application. This step allows the backend to m...
Read more

PharmaStock Backend Progress Complete all backend endpoints

Image
 I completed the full Medication API (GET, POST, PUT, PATCH, DELETE) and finished SCRUM-37, implementing the stock quantity adjustment endpoint. Inventory quantities can now be increased or decreased, negative values are prevented, and all changes persist correctly in the database. I also finalized the inventory creation flow with duplicate lot validation and verified everything through Swagger testing. On the frontend side, I started SCRUM-38 and began building the Angular inventory list component to connect the UI to the new backend functionality. Overall, this week solidified the backend foundation and began transitioning into full-stack development. Medication Post Workflow            Medication Post          Post Inventory for new medication               Inventory adjustments
Read more

PharmaStock: Sprint Planning Complete

This week was focused on finalizing project planning and getting everything ready for development. I completed the setup of the Jira board , finalized all sprints for the full length of the project, and added clear completion criteria for each sprint and task. This gives the team a clear roadmap from MVP through enhancement features. I also synced my local GitHub setup with the main project repository and verified that the branching structure is ready for feature development. With planning complete and source control aligned, the project is now fully prepared to move into active development next week.
Read more