Contents Project Background 2 Introduction: 2 II Literature review 3 III Formulate the project problem 4 Project Objectives: 8 Software development cycle: 8 Overview of System functionality: 10 Project management scheduling and plan: 10 Risk management 11

Project Background

Introduction:

The hospital’s ambition is to take care of patients and contribute to their state of health and thus respond to all the distresses of all citizens, whatever their age and income. It also has an important role in the training of doctors and paramedics and in research. Its role, and we all accept it, is to take charge of the heaviest and most costly pathologies that most often affect disadvantaged patients, whether financially or medically. Its objective is therefore to treat the most serious diseases, which come under several disciplines, which are expensive, and to advance medical research for these pathologies. It also takes care of patients who, by choice or by necessity, prefer the public service for less serious pathologies. Logically, the hospital should be complementary to the private liberal service, which is more flexible, more efficient and, by definition, less encumbered with social problems, but also with heavy investments.

The hospital, for its part, tries, to rebalance its accounts, to make so-called profitable pathology and encourages activities that compete with liberal activity and clinics in their areas of excellence.

In the digital age, all business sectors are impacted by new technologies. Health is no exception. Between revolution and caution, remote self-medication should be taken with a grain of salt.

If in certain developed areas of the world, the health sector is modernizing at a great speed and most inhabitants have access to quality care, this industry suffers from a strong constant increase in demand. According to many studies, current doctors and hospitals still not enough and it shows: overcrowded health centres, overwhelmed staff, degraded infrastructure, problems with the supply of certain drugs and increased waiting times. n waiting for patients in hospital corridors, the French solidarity system needs more professionals and more budget to meet the demands of a growing population. In this complicated context, the acceleration of digital opens up many opportunities.

The current idea aims to assist hospitals in improving their administrative, organizational and functional aspects. Which we will try to discuss in an organized manner.

II Literature review

Information technology impact on life:

Information Technology (IT) is playing an increasingly important and dominant role in the healthcare sector. A multitude of IT solutions is available to healthcare establishments, healthcare providers, patients and the population as a whole. These include clinical information systems used in hospital organizations that allow, among other things, the management of computerized patient records, laboratory results and medical imaging. There is also a greater use of different forms of telemedicine, including teleconsultation, tele radiology and tele homecare, which aim to provide better access to health care services for geographically isolated or declining patients. Finally, the applications available on mobile phones and digital tablets bear witness to their ability to transform, and even reinvent, the ways of providing care to patients who are more involved in the management of their medical condition.

The need to improve the efficiency of hospitals:

Non-invasive procedures are on the rise, whether on an outpatient basis or even outside the hospital. With the aging of the population, the number of elderly people who will need care will increase, while the development of lighter anaesthesia methods has considerably broadened the range of treatments available to them. For this population group, in particular, there is a need to develop a more homogeneous model in which primary health care, social care and hospital treatment are articulated in a more coherent way.

Evolution of website to handle the healthy advisory:

Website design for Health advisory system can be some difficult. These systems often have a huge quantity of information and data, to present on their website, and struggle to do so in such a way that does not confuse or overwhelm their visitors. Additionally, many today ready systems were created in past, and no longer conform to today’s design standards, making them incompatible or difficult to browse on mobile devices and smartphones.

Characterization of current situation:

· There is a shortage in the number of hospitals, and specialized medical staff There are precautionary measures preventing free movement due to the Corona pandemic

· There are many patients suffering from transportation to and from hospitals

· There are many cases that do not require you to go to medical care

User Requirements gathering:

To be sure that our suggested website correspond well with the expectations and actual uses of the end users (patients, doctors…etc.), it is necessary to have recourse to the collection of user requirements. This expression of needs finds its place in the framing phase of the project cycle.

By collecting the needs of the end user, we access an end-user view. The work of collecting needs is carried out during individual interviews or focus groups. It is important to get verbatim to illustrate the point and be very pragmatic. We will be able to confirm or refute certain initial assumptions and readjust our design strategy thanks to a better knowledge of our audience.

Mechanize and mythology of systems’ users requirements collecting:

There are two kinds of information gathering techniques: elicitation and collaboration.

Elicitation is the activity of making tacit information explicit. It can be carried out:

· Either by fetching existing data: from people with expertise, described in documents (procedures, regulatory texts, etc.), stored in software and databases, etc.

· Or by receiving the information.

Elicitation involves:

· Discuss directly with the project stakeholders,

· Research all subjects that may be directly or indirectly part of the scope,

· Experiment by our self the processes, tasks, professions to better perceive the stakes,

· Communicate their expectations and make themselves known to encourage stakeholders to push the information in their possession to us.

Collaboration, on the other hand, is the activity of making people work or work with other people in order to solve a common problem.

First, the Business Analyst must ensure that he correctly understands the scope of the subject on which he needs to collect data.

Functional requirements:

For patients:

· Register.

· Login/ logout

· Edit profile

· Send question(s)

· View Answer(s)

· Upload Docs (Rays, reports, recommendations … etc)

· Chat with expert (voice, video, text)

· Make order(s)

· Cancel order(s)

· Pay online

For Doctors:

· Register.

· Login/out

· View complaints

· Retrieve Patient’s health record

· Send advice / medications

· Update Patient’s health records

For Pharmacy:

· Register

· Login / out

· View request

· Issue invoice

· Send order to client (patient)

· Get cash/online

· Make report sales

Non-Functional requirements:

Security:

· Patient Identification

· Logon ID

· Modifications

· Front Desk Staff Rights

· Administrator rights

Performance:

· Response Time

· Capacity

· User-Interface

· Conformity

Maintainability:

· Back-Up

· Errors

Reliability:

· Availability

Project Objectives:

· Reducing waiting times inside the hospital

· Improve time management and medical staff work

· Reducing the burden of moving from home to hospital for patients

· Reducing time spent examining and purchasing medicines.

· Improving hospital performance efficiency

Software development cycle:

The “software lifecycle” refers to all the stages in the development of software, from its conception to its disappearance. The objective of such a breakdown is to make it possible to define intermediate milestones allowing the validation of the software development, that is to say the conformity of the software with the expressed needs, and the verification of the development process, that is to say the conformity of the software with the expressed needs, and the verification of the development process. ie the adequacy of the methods implemented.

The origin of this breakdown comes from the observation that errors have a cost that is all the higher the more they are detected late in the production process. The life cycle makes it possible to detect errors as early as possible and thus to control the quality of the software, the deadlines for its realization and the associated costs.

The software life cycle generally includes at least the following activities:

· Definition of objectives, consisting in defining the purpose of the project and its inclusion in a global strategy.

· Analysis of needs and feasibility, that is to say the expression, collection and formalization of the needs of the applicant (the customer) and of all the constraints.

· General design. This is the development of specifications for the general architecture of the software.

· Detailed design, consisting in precisely defining each subset of the software.

· Coding (Implementation or programming), ie the translation into a programming language of the functionalities defined during the design phases.

· Unit tests, making it possible to individually verify that each sub-assembly of the software is implemented according to the specifications.

· Integration, the objective of which is to ensure the interfacing of the various elements (modules) of the software. It is the subject of integration tests recorded in a document.

· Qualification (or acceptance), that is to say the verification of the conformity of the software with the initial specifications.

· Documentation, aimed at producing the information necessary for the use of the software and for further developments.

· Start of production,

· Maintenance, including all corrective (corrective maintenance) and scalable (scalable maintenance) actions on the software.

Finally, the sequence and presence of each of these activities in the lifecycle depends on the choice of a lifecycle model between the customer and the development team.

Overview of System functionality:

System context diagram: