COIT20254: Pharmaceutical System Progress Report 2

COIT20254: Information Systems Project
Term 1, 2018
Progress Report 2
Pharmaceutical System
Lecturer and Tutor: Indra Seher
Prepared by
Sadiquddin Syed S0277988
Srijan Nepali 12044047
Nishan khadka 12025666
1

Executive Summary
In this progress report, we have outlined the System design of our Pharmaceutical System. It
also states the current stage of Pharmaceutical System. In progress report, we have used
fact-finding techniques to gather the sufficient so that we can analyse before designing the
user interface. Unified Modelling language diagram also used to design the system as per
the collected information. There are no changes in the specification of the project. The
project schedule is reviewed and three parameters namely, Completed, In-Progress and
Scheduled have been used to highlight the current progress of the project. In the Last all the
concerned project risks are taken into consideration and group also provide
recommendations to provide a mitigation plan to these risks.
2

Table of Contents
Executive Summary....................................................................................................................2
Introduction................................................................................................................................4
Description of any changes and/or description of status of project..........................................4
Use Case Diagram...................................................................................................................5
Architecture Diagram.............................................................................................................6
Interface Design......................................................................................................................7
Database Design Diagram.......................................................................................................9
Project Status Matrix..............................................................................................................9
Group Meeting Status..........................................................................................................10
Schedule Review.......................................................................................................................11
Risk Review...............................................................................................................................15
Cost-Related Risk..................................................................................................................15
System Usability Risk............................................................................................................15
System Design Risk...............................................................................................................15
Team Communication Risk...................................................................................................15
System Failure Risk...............................................................................................................15
Summary...................................................................................................................................16
3

Introduction
Pharmaceutical system have been designed keeping all the current issues of the
pharmaceutical industry in mind. It helps to manage all the troublesome operations in a
better manner. It takes cares of sales and stock information of the medicine. It is designed
to store all the present as well as past transactions.
Currently, the project is in the design phase. All the stakeholders have been mapped and
their role and responsibilities have been outlined in the system design. In this stage, system
functional, non- functional requirements are also decided keeping the usability
fundamentals in mind. Risk management strategies are discussed and formulated so that
system can withstand every failure situation. To make the system platform independent,
cloud storage have been selected to provide the back-end support to the Pharmaceutical
system.
Description of any changes and/or description of
status of project
Till now the system and solution design of the Pharmaceutical system have been outlined.
All the Stakeholder where this system is proposed to be used have been evaluated to
formulate the functional and non-functional requirements of the system.
Fact-Finding techniques such as have been used to gather sufficient information form the
potential stakeholders. Following fact-finding techniques that have been used are:
Questionnaire, Interviews, Observation and Site Visit were used.
Unified Modelling Language diagram have been used to convert the collected information
into system design.
4

Use Case Diagram
Use case Diagram outlines the actors and their possible actions.
Figure 1 Use Case Diagram
5

Architecture Diagram
This architecture diagram help to provide the working of the system on a cloud platform.
Figure 2 Architecture Diagram
6

Interface Design
Following are the User Interface of the Pharmaceutical System.
Figure 3 Account
Figure 4 Inventory Management
7

Figure 5 Authentication
8

Database Design Diagram
Figure 6 Database Design
Project Status Matrix
Following task have been accomplished as per the decided schedule.
4 Explain solution and system design Completed
4.1 Defining stakeholders Completed
4.2 Define methodology Completed
4.3 System Analysis Completed
4.3.
1 Functional Requirement Completed
4.3.
2 Usability requirement Completed
4.3.
3 Reliability requirement Completed
4.3.
4 Performance requirement Completed
4.3.
5 Security requirement Completed
4.4 Explain risk management strategies Completed
4.5 New System Design Completed
4.5. Database design Completed
9

1
4.5.
2 Design system models Completed
5 Documentation Scheduled
6 Report Scheduled
7 Closing Scheduled
Group Meeting Status
Since it’s a group activity collaboration is the key to the success of this project. All the task
have been divided among the group member and in the last group meeting, it was decided
to use collaborated tools frequently to keep the track of the progress. Apart from the face-
face discussion this time we have used slack and Skype to keep track of the progress.
S.No Purpose Meeting Type
1. Brainstorming Session Face-Face Session
2. Group Meeting Slack and Skype
3. Feedback Session Face-Face Session
4. Training Session Face-Face Session
5. Documentation Session Skype
10

Schedule Review
Project Schedule helps the group to keep track of the all initially outline tasks. Project plan
helps the group member to strategies the project tasks in a better way.
Task Name Status
1 Planning Completed
1.1 Group Development Completed
1.2 Arranging meetings Completed
1.3 Selection of project topic Completed
1.4 System Analysis Completed
1.5 Defining project objectives and constraints Completed
1.6 Assigning project member tasks Completed
1.7 Work break down structure Completed
1.8 Project schedule Completed
1.9 Risks Analysis and Quality control Completed
2 Project Research Completed
2.1 Research on current business process and existing
system
Completed
2.2 Market research Completed
2.3 Research on possible solution Completed
3 Analysis Completed
3.1 Business process analysis Completed
3.2 Stakeholder analysis Completed
3.3 Risk assessment Completed
3.4 System analysis Completed
3.5 Present system analysis Completed
3.5.1 Client-based system analysis Completed
3.5.2 Distribution system analysis Completed
4 Explain solution and system design Completed
11

4.1 Defining stakeholders Completed
4.2 Define methodology Completed
4.3 System Requirements Completed
4.3.1 Functional Requirement Completed
4.3.2 Usability requirement Completed
4.3.3 Reliability requirement Completed
4.3.4 Performance requirement Completed
4.3.5 Security requirement Completed
4.4 Explain risk management strategies Completed
4.5 New System Design Completed
4.5.1 Database design Completed
4.5.2 Design system models Completed
5 Documentation In Progress
5.1 Executive Summary In Progress
5.2 Introduction In Progress
5.3 Project Management Overview In Progress
5.3.1 Statement of Work In Progress
5.3.2 Project Team Members and Responsibilities In Progress
5.3.3 Project Schedule In Progress
5.4 Proposed Strategic Alignment Scheduled
5.5 Proposed Strategic Alignment Scheduled
12

5.6 Description of Current System Scheduled
5.6.1 Issues Scheduled
5.6.2 Problems Scheduled
5.7 Proposed Stakeholder Analysis and Management Scheduled
5.8 Proposed Requirements Elicitation Methodology Scheduled
5.9 Proposed Requirements Statement Scheduled
5.10 Proposed Risk Analysis and Risk Management Strategie
s
Scheduled
5.10.
1 Proposed change management solution Scheduled
5.10.
2 Analysis of issues and proposed solutions Scheduled
5.11 Conclusions & Recommendations Scheduled
6 Report In Progress
6.1 Project proposal and plan Completed
6.2 Progress report 1 Completed
6.3 Draft final report Completed
6.4 Progress report 2 Completed
6.5 Presentation documentation In-Progress
6.5.1 Slide preparation Scheduled
6.5.2 Presentation in class Scheduled
6.6 Project working documentation Scheduled
6.7 Project report Scheduled
7 Closing Scheduled
7.1 Self and peer assessment submission Scheduled
13

7.2 Close the project Scheduled
System and solution Analysis task and documentation task are completed. All the schedule
are realistic in nature. Some tasks have been outlined that need more time and knowledge
and required resources have been employed for those tasks. All the group members
completed their respective tasks on time and that helped the project to meet its decided
schedule.
14

Risk Review
Risk review is done for Pharmaceutical System and it helps to look after the uncertainty in
the project. All the Constraints that can affect the system have been outlined to streamline
the project progress and Pharmaceutical system to respond to any uncertainty.
Cost-Related Risk
The main risk that was identified in the group meeting is the platform uncertainty i.e.
system will be running over multiple platforms and due to which cost of the development
will increase and performance of the system will also effect due to multiple platforms. So,
resolve this risk Pharmaceutical System is to be deployed on the cloud platform which will
reduce the platform dependency and single design will run on across the platform.
System Usability Risk
Group Members felt that required data was not there to design the system interface and
that will directly affect the usability of the system. To resolve this risk, group members
decided to employ Fact –Finding techniques to gather data across the potential
stakeholders.
System Design Risk
Group member also felt that system usability have to meet all the heuristic principles so that
it can be used by everyone otherwise the design will become complex and difficult to use.
To resolve these risks group members decide to conduct brainstorming session and design
thinking workshops to design an interface that meets all the requirement of the
stakeholders.
Team Communication Risk
Since all the group members are involved in the project progress and frequent face-face
sessions were not possible due to which project progress tracking becomes difficult, to bring
ease to this situation group decided to use Skype and Slack.
System Failure Risk
Group members were concerned related to the system failure which can put the system
reliability at risk, to resolve this risk group member decided to formulate a backup and
15

continuity policy which will guide the system at the time of failure. Application backup will
be stored at various cloud instance so that system can provide a 99.9 availability.
Summary
This progress report provides insights regarding the system design of the Pharmaceutical
system. Fact – Finding techniques were employed to gather the required information for the
system design. Based on these findings user interface of the system was designed. UML
diagrams were also used to bring the gathered information into a structural information.
Database design will help the Pharmaceutical system to provide the desired services to the
potential stakeholders. Using Project Plan schedule was reviewed, three parameters were
used – Completed, Scheduled and In-progress and these parameters provide insights of the
current progress status. At Last, project risks were reviewed and their mitigations were also
provided which were formulated in the group members.
16