Srs DHopebook

323
srs
srs (software requirments specifications)

SRS DHopebook

Nowadays, people are more interested to know authentic details online about their any particular disease like what could be all possible symptoms, lifestyle, complications regarding that disease, etc. Many websites are already developed for this purpose but there is a need to add 1 more unique feature online that is real success stories of those patients that survived that particular disease and are survivors now so this would be a ray of hope for others who are already battling or suffering from that disease. Survivors can explain what challenges or conditions they faced, and how did they get there? What was involved? What treatment did they have? What is their present condition as a result of this treatment? What things can they do now that they couldn’t do before? The main goal is to help and convince potential patients to take the next step, and have faith. This would be so helpful for their mind and health and with this hope and faith, there would be more chances for their recovery. So there is a need to design and develop a user-friendly web app like a
colorful notebook, each page display details of a particular disease with success stories of
survivors that how they recovered from this disease, and how long it took? so this can be a great option for patients to put their minds at ease when it is thinking the different scenarios so with this web app, users or patients would be able to get all details about any minor or major disease and also able to read success stories of people or survivors who fought with that disease and now living a healthy life.


 

Scope of Project DHopebook:

Project scope is the part of project planning that involves determining and documenting a list of specific project  goals, deliverables, tasks, costs and deadlines. Defining the project scope involves adopting a clear vision and an agreement on the outcomes of the project. This allows each milestone of the project to stay on target

Functional and Non Functional Requirements of DHopebook:

Functional Requirements :

A functional requirement shows that what the system must do what services the system present to users. It describes a software system or its component. A function is nothing but inputs to the software system, its behavior, and outputs

Functional Requirements of DHopebook:

Admin
1. Admin can login into the system
2. Admin can verify doctors or survivors details.
3. Admin can delete/ edit information of disease or success story.
4. Admin can block any doctor or survivor.
5. Admin keep track of all the activities.
Doctors:
1. Doctors can register into the system.
2. After verification, doctors can login to system.
3. Doctors can write content on disease related to their specialization.
4. Doctors can review survivor’s story and approve or reject that with comments.
Users:
1. Users can be patients/Survivors/Guest.
2. Users can search about any disease by using Disease Search Engine.
3. User can read all details about any disease and survivors success stories without logging in.
4. In order to post their story, they need to first get registered.
5. After verifying from admin end, they can login and post their story.

NON-FUNCTIONAL REQUIREMENTS DHopebook:

  • Application is user friendly.
  • Application Perform fast manipulation and calculations.
  • Application is adaptable.
  • Application will be able to work on all types of operating systems.
  • Application will be capable to handle multi user activities simultaneously.
  • There will be back up system to face any problem in system
  • All the options should be learning friendly I.e. member could easily understand what that option will do if he clicked on it.
  • Response Time is very awesome.
Some others are:
  • Accessibility
  • Maintainability
  •  Fault Tolerance.
  • Security
  • Robustnes



 

Use Case Diagram of Diagnosis of DHopebook

a use case diagram can summarize the details of your system’s users   and their interactions with the system. Scenarios in which your system or application interacts with organizations, people, or external systems. Goals that your system or application helps those entities achieve



 

 

Usage Scenarios Diagnosis of DHopebook:

A brief user story explaining who is using the system and what they are trying to accomplish. A Scenario is made up of a number of simple, discrete steps that are designated as being performed by either the System or a  User.

 

ADOPTED METHODOLOGY for DHopebook:

The adopted methodology for this project is vu process model. Vu process model is a combination of water-fall model and spiral model. This combination has many advantages. This model has high risk analysis so avoidance of risk would be achieved. This model is easy to understand and use. Now first we will discuss the Water-fall model.



 

Work Plan of Diagnosis of DHopebook:

Work plan



for complete srs contact us

watsapp: 03469806607