Pharmaceutical Inventory Management System: Project Working Documentation

This document outlines the weekly meetings and discussions held during the development of a pharmaceutical inventory management system. It details the project selection, work breakdown structure, stakeholder analysis, system design, documentation, and project closure. The document provides insights into the project's progress, challenges, and solutions, showcasing the team's collaborative approach and adherence to agile methodologies.

PROJECT WORKING DOCUMENTATION

Week 1
Group development and selection of project
3.8.2018 9:00 AM- 10:00 AM [Meeting Location]
Meeting
organizer Nishan Khadka
Meeting
medium Face-to-Face
Helper Srijan Nepali
Team member
for note Sadiquddin Syed
Time manager Nishan Khadka
Presence of
members All are present
Motive of the meeting: To discuss regarding the group making and
selection of an appropriate project
1 hour Nishan Khadka
Discussion
During this meeting, the discussion is regarding the group members of team and how the
project can be selected and different criteria of the selection is also discussed. We have
analyzed the different projects which will be suitable for the course; thereby we mutually
selected the project of pharmaceutical company which is the actual requirement of the project.
This project is real and relates to real world requirement on a large basis.
Conclusions
The conclusion of this meeting is that project has been selected on the basis of real factors and
its need in the real world. As the pharmaceutical company is facing the problem of managing
the services and is not able to provide the healthcare services at the remote places. This
traditional offl ine system is also facing issues in storing the data of the staff and patients and
this also take much of time when information is accessed.
Action Items Person Responsible Deadline
Group development Nishan Khadka 3.8.2018
Meetings session for discussion Srijan Nepali 3.8.2018
Analysis of project idea Sadiquddin Syed 3.8.2018
Selection of project Project Manager 3.9.2018
Final approval from the project manager Project Manager 3.11.201
8

Week 2
Development of work breakdown structure and project schedule
3.17.2018 9:00 AM- 10:00 AM [Meeting Location]
Meeting
organizer Srijan Nepali
Meeting
medium Face-to-Face
Helper Nishan Khadka
Team member
for note Sadiquddin Syed
Time manager Srijan Nepali
Presence of
members All are present
Motive of the meeting: To create final WBS and also define the
schedule of the project plan
1 hour Srijan Nepali and Sadiquddin Syed
Discussion
In this meeting, the discussion is regarding the creation of work breakdown structure in terms
of the project requirements and how the project is going to be developed. What types of stages
are going to be included in the plan? Each stage has its own demand such as development of
database should be a separate stage. Even each stage must be defined under the fixed
duration of time where the associated stage must be completed on time.
Conclusions
In the conclusion of this meeting, there is final designing and development of the work
breakdown structure. After the finalization of the stages required for the development lifecycle
of the project, the duration for each task and subtask is also finalized in context to time
required to complete it. This will helps in getting the knowledge regarding the next task and in
how much it can be completed. It will also help in managing the time delay appeared in
previous task.
Action Items Person
Responsible Deadline
Identification project objectives and constraints Nishan
Khadka
3.17.201
8
Designing layout of WBS Sadiquddin
Syed
3.21.201
8
Finalization of WBS Srijan Nepali 3.21.201
8
Assigning date and duration Sadiquddin
Syed
3.22.201
8
Approval on final schedule plan Project
manager
3.22.201
8

Week 3
Project Research
3.24.2018 2:00 PM- 4:00 PM [Meeting Location]
Meeting
organizer Sadiquddin Syed
Meeting
medium Face-to-Face
Helper Srijan Nepali
Team member
for note Nishan Khadka
Time manager Sadiquddin Syed
Presence of
members All are present
Motive of the meeting: Applying research on various aspects of the
project and to know more knowledge
2 hour Sadiquddin Syed
Discussion
Initially the research has been done on the current system of the organization and what type of
process it possesses. This helped in getting the details of the need of the new system for the
project and this new system will help in overcoming the limitations of the older system such as
poor delivery of system, poor management of data and so on. In addition to this, research on
market demand is also analyzed which demonstrate that the developed project will be a
success or not. The data collected is used for the selecting various alternate possible solutions
of the project such as web application, mobile application and so on. In last, final solution has
been proposed in context to interface online application and database management system.
Conclusions
The research has concluded that the data collected from the current system and market
overview is used for the collection of possible solution to the pharmaceutical company. The
final solution that has been selected from the mutual approval is the inventory system which is
combination of online interface and database management system.
Action Items Person
Responsible Deadline
Research on current process and system and data collection Nishan
Khadka
3.24.201
8
Research on market demand and data collection Sadiquddin
Syed
3.24.201
8
Discussion on collected data through research Srijan Nepali 3.25.201
8
Research on alternate solution of problem Sadiquddin
Syed
3.25.201
8
Discussion on solution proposed Srijan Nepali 3.26.201
8

Week 4
Business Process, stakeholder and system analysis
3.27.2018 9:00 AM- 10:00 AM [Meeting Location]
Meeting
organizer Nishan Khadka
Meeting
medium Face-to-Face
Helper Srijan Nepali
Team member
for note Sadiquddin Syed
Time manager Nishan Khadka
Presence of
members All are present
Motive of the meeting: Complete analysis of the business process,
stakeholder and system leads to gain of requirements
1 hour Nishan Khadka
Discussion
In this meeting, we have discussed on the identification and analysis of the business process
which includes the details of requirement of the process that is to be included in the
developing project such as healthcare services, delivery tracking and so on. After this, the
demand of the stakeholders should be met and these demands are identified and analyzed for
the implementation in the project. Data collected can be used in collecting the demand and
needs of the project. Later the discussion is moved towards the analysis on the selected
system whether the proposed solution will fulfill the demand and provide the business growth
to pharmaceutical company.
Conclusions
With this meeting, it has been concluded that the data collected from the identification and
analysis of business process and stakeholders. The proposed system is flexible and effi cient to
fulfill the requirements of the business process and stakeholders.
Action Items Person
Responsible Deadline
Identification of business process data Sadiquddin
Syed
3.27.201
8
Analysis on business process data Nishan
Khadka
3.28.201
8
Identification of Stakeholders and data related to them Sadiquddin
Syed
3.30.201
8
Analysis on Stakeholder data Sadiquddin
Syed
3.31.201
8
System Analysis Nishan
Khadka
4.07.201
8

Week 5
Analysis on the Present System
4.01.2018 9:00 AM- 10:00 AM [Meeting Location]
Meeting
organizer Srijan Nepali
Meeting
medium Face-to-Face
Helper Nishan Khadka
Team member
for note Sadiquddin Syed
Time manager Srijan Nepali
Presence of
members All are present
Motive of the meeting: To provide the knowledge of present system
and possibilities of fulfilling the demand and need of the
stakeholders and business process
1 hour Srijan Nepali
Discussion
This meeting is organized in context of present system and the team has discussed all the
possibilities of the system in managing the services of the pharmaceutical company. The
discussion is regarding how this system can be developed effi ciently and then used for the
company to manage the services and data stored. The system has ability to decrease the
efforts of the staff in working more that required at the company. The proposed system
analyzes the client-based aspects and distribution based system and in last how the
documentation can be created is also discussed.
Conclusions
The present system is analyzed on the basis of the client requirements and the developed
lifecycle of the proposed project is also analyzed on the basis of the distribution. The
documentation of the meeting will also provide the data of the proposed system. This present
system is in process and this inventory system will provide the effi ciency to handle the
operation of the company.
Action Items Person
Responsible Deadline
Identification of Client-based system Srijan Nepali 4.01.201
8
Analysis of Client-based system Sadiquddin
Syed
4.08.201
8
Identification of Distribution system Nishan
Khadka
4.09.201
8
Analysis of Distribution system Srijan Nepali 4.10.201
8
Documentation of analyzed system Nishan
Khadka
4.12.201
8

Week 6
Identification of stakeholder requirements and methodology
4.01.2018 9:00 AM- 11:00 AM [Meeting Location]
Meeting
organizer Sadiquddin Syed
Meeting
medium Face-to-Face
Helper Srijan Nepali
Team member
for note Nishan Khadka
Time manager Sadiquddin Syed
Presence of
members All are present
Motive of the meeting: To determine the demand of stakeholder and
the best methodology to develop the project
2 hour Nishan Khadka and Sadiquddin Syed
Discussion
In this meeting, there is discussion on the requirements of the stakeholders with which the
data is collected in the manner of project development. This data is collected from the
stakeholders with the help of questionnaires and feedback on the previous system. The
requirements so collected is then analyzed and evaluated in terms of the business process
requirements. Further the discussion is on the selection of proposed methodology used for the
development of the project. This selected methodology is then analyzed on the market
research where its successful implementation for project is measures in terms of probability.
Conclusions
With the help of this meeting, it can be concluded that requirements can only be gathered with
the full support and engagement of stakeholders. Instead of this, the proposed methodology of
the agile model for the database development and project management for the management of
whole project will be used. With the market research, it has been found that database provides
good support in storage of data and interface provides good support in online accessibility.
Action Items Person
Responsible Deadline
Collection of stakeholder requirements Nishan
Khadka
4.12.201
8
Analyzing the requirements Sadiquddin
Syed
4.21.201
8
Identification of methodology Srijan Nepali 4.15.201
8
Market research on selected methodology Sadiquddin
Syed
4.20.201
8
Documentation of meeting Srijan Nepali 4.21.201
8

Week 7
Discussion on System Requirements
4.22.2018 9:00 AM- 11:00 AM [Meeting Location]
Meeting
organizer Nishan Khadka
Meeting
medium Group development and selection of project
Helper Srijan Nepali
Team member
for note Sadiquddin Syed
Time manager Nishan Khadka
Presence of
members All are present
Motive of the meeting: To determine the major system requirements
2 hour Nishan Khadka and Sadiquddin Syed
Discussion
This whole meeting is for the discussion on the system requirements. Firstly the discussion is
on the functional requirement where the discussion is on the function that the developed
project must possess. After this, the discussion led to the usability requirement which means
what the user wants in its interface to access the online system easily and use the services of
the pharmaceutical company. Later, the discussion is on the reliability of the system, how
much the system is reliable to the company and to the users and what can be done to improve
the quality of the system. Later the discussion is on the performance and security of the
proposed system, it contains the various techniques to improve the performance a security of
the inventory management system. Security can be achieved through various techniques such
as encryption and private login credentials and so on.
Conclusions
During this meeting, the data of the requirements are collected in the notes in context of
functionality, usability, reliability, performance and security.
Action Items Person
Responsible Deadline
Discussion on functional requirement Sadiquddin
Syed
5.06.201
8
Discussion on Usability requirement Sadiquddin
Syed
5.17.201
8
Discussion on Reliability requirement Nishan
Khadka
5.26.201
8
Discussion on Performance requirement Nishan
Khadka
5.26.201
8
Discussion on Security requirement Srijan Nepali 4.21.201
8

Week 8
Discussion on new system design
5.06.2018 9:00 AM- 10:00 AM [Meeting Location]
Meeting
organizer Srijan Nepali
Meeting
medium Face-to-Face
Helper Nishan Khadka
Team member
for note Sadiquddin Syed
Time manager Srijan Nepali
Presence of
members All are present
Motive of the meeting: To discuss about the design and layout of the
new system
1 hour Srijan Nepali
Discussion
This meeting is proposed in the need of discussion for the design of the database platform.
Here the discussion is also done on the modeling system of ERD to develop the internal
structure of the system where the discussion is preceded towards the selection of system
model to generate the lifecycle development of the system. With the help of this model, the
database for the project will be developed more effectively. Later we also discussed about the
type of coding used for the programming of the database and platform to develop this model.
Later the discussion proceeded for documentation of the database system to collect the review
from other system.
Conclusions
This meeting concluded that database management system will be developed using the agile
model of development and should use the structure query language or SQL for the
programming of the database and also to generate the query for the system.
Action Items Person
Responsible Deadline
Discussion on Database design Srijan Nepali 5.15.201
8
Discussion on ERD modeling Sadiquddin
Syed
5.16.201
8
Discussion on selection of system model Nishan
Khadka
5.17.201
8
Coding and platform discussion Srijan Nepali 5.25.201
8
Final conclusion for database system Nishan
Khadka
5.26.201
8

Week 9
Discussion on documentation
3.22.2018 9:00 AM- 11:00 AM [Meeting Location]
Meeting
organizer Sadiquddin Syed
Meeting
medium Face-to-Face
Helper Srijan Nepali
Team member
for note Nishan Khadka
Time manager Sadiquddin Syed
Presence of
members All are present
Motive of the meeting: To generate the idea regarding the technique
to do the documentation of the project
2 hour Nishan Khadka and Sadiquddin Syed
Discussion
Here the discussion is regarding the documentation of the developing project. The first
discussion is on the statement of work which is included in the overview of the project
management. Here, we also discussed that what are the roles and responsibilities played by
the team members so that the objectives of the project can be achieved. Here we also
discussed how the schedule will be maintained across the process of the project development
and we remain be focused on the project liabilities, Later the proposed strategic alignment is
also discussed in terms of the vision, values, prioritize, planning, goals and actions. Later the
possible issues and problems associated with the current system is also discussed. Later we
talked about the management of the stakeholders and how it can be achieved and managed.
Conclusions
Here, we learnt that how the documentation of the proposed project can be implemented and
analyzed in term of various aspects of the project so that agreement can be cleared in legal
and demand aspects.
Action Items Person
Responsible Deadline
Discussion on project management overview- statement of work Nishan
Khadka
5.31.201
8
Discussion on Roles and responsibilities Sadiquddin
Syed
5.31.201
8
Discussion on project schedule Srijan Nepali 5.31.201
8
Discussion on Strategic Alignment Nishan
Khadka
6.03.201
8
Discussion on Current System Sadiquddin
Syed
6.09.201
8
Discussion on Stakeholder Analysis and Management Nishan
Khadka
5.31.201
8

Week 10
Discussion on documentation (Continued..)
6.01.2018 2:00 PM-4:00 PM [Meeting Location]
Meeting
organizer Nishan Khadka
Meeting
medium Group development and selection of project
Helper Srijan Nepali
Team member
for note Sadiquddin Syed
Time manager Nishan Khadka
Presence of
members All are present
Motive of the meeting: To generate the idea regarding the technique
to do the documentation of the project
2 hour Nishan Khadka
Discussion
Here the discussion is on the more terms of the documentation. The elicitation methodology for
the requirement gathering includes a high perspective of techniques with which various
stakeholders are engaged in the requirement gathering such as brain storing activity,
questionnaire activity and so on. Later the discussion is on the requirement statement which
includes the details of the requirement both in terms of the stakeholders and the legal aspects.
Risk management plan is also discussed with the knowledge of the change management
solution and involvement of risk register for risk identification, its solution and possible
recommendations.
Conclusions
With this, the knowledge of the full documentation of the project is discussed among the
project members and this will help in proper documentation.
Action Items Person
Responsible Deadline
Discussion on Requirements Elicitation Methodology Srijan Nepali 6.03.201
8
Discussion on Requirements statement Sadiquddin
Syed
6.09.201
8
Discussion on Risk Analysis and Risk Management Strategies-
change management solution
Nishan
Khadka
5.31.201
8
Discussion on risk and proposed solutions Sadiquddin
Syed
5.31.201
8
Finding possible recommendations Srijan Nepali 5.31.201
8

Week 11
Discussion on report development
6.01.2018 2:00 PM-4:00 PM [Meeting Location]
Meeting
organizer Srijan Nepali
Meeting
medium Face-to-Face
Helper Nishan Khadka
Team member
for note Sadiquddin Syed
Time manager Srijan Nepali
Presence of
members All are present
Motive of the meeting: To discuss about the different status of
project in terms of reports
2 hour Srijan Nepali
Discussion
This discussion includes the process of report development and which type of report should be
developed at the project progress. It involves the discussion on the proposed plan which
includes the layout of the project. Later two progress report has been developed in between
and there we discussed on both these report and what have to be included in this report. But in
between final draft is also proposed which is also analyzed by us to predict the possible project
requirement. Later, we also discussed on the evaluation of the team and how the team is
deployed and working at the project development.
Conclusions
Various reports have been developed and their discussion leads to the knowledge of the project
status which shows what has happened till the status has occurred and what the achievements
are.
Action Items Person
Responsible Deadline
Discussion on Proposed plan Srijan Nepali 6.03.201
8
Discussion on progress report 1 Sadiquddin
Syed
6.09.201
8
Discussion on final draft Nishan
Khadka
5.31.201
8
Discussion on progress report 2 Srijan Nepali 5.31.201
8
Discussion on Team evaluation Nishan
Khadka
6.09.201
8

Week 12
Report and closing of project
3.8.2018 2:00 PM-4:00 PM [Meeting Location]
Meeting
organizer Sadiquddin Syed
Meeting
medium Face-to-Face
Helper Srijan Nepali
Team member
for note Nishan Khadka
Time manager Sadiquddin Syed
Presence of
members All are present
Motive of the meeting:
2 hour Sadiquddin Syed
Discussion
This discussion is on the final presentation of the project and how it can be developed and
presented in the class. Various practices have been arranged in the meeting to improve the
confidence in presentation. It also includes the discussion on the project working
documentation and how to develop the final project plan report and what will be its key
features. Lastly, the discussion is on the proper closing includes the approval of each team
members and stakeholder on the developed plan. It also includes the signature on legal
agreements by the stakeholders and rechecking in context to the constraints and project
Conclusions
This meeting has provided the path for proper closing of the project including the improvement
in confidence while giving presentation at the class. Here proper working documentation is
demonstrated in terms of the weekly meeting generated to keeping focus of mind on the
project objectives and the need of the pharmaceutical company.
Action Items Person
Responsibl Deadline
Discussion on documentation of presentation Nishan
Khadka
5.31.201
8
Practice on developed slides Sadiquddin
Syed
6.07.201
8
Discussion on project working documentation Srijan
Nepali
5.31.201
8
Discussion on Project plan Sadiquddin
Syed
5.31.201
8
Discussion on closing of project Sadiquddin
Syed
5.31.201
8