system architecture

CS277 SOFTWARE ENGINEERING

Phase One Report

Table of Content

2. Project Organization

3. Project Management Plan

1. Introduction:

1.1 Problem Statement

It’s important to be fully aware of every aspect of any medication that you take. medications in general must have a prescription given to you by the doctor. It contains the recommended dosage, what’s the ingredients for the product, what’s the possible side effects, etc. There’s always a possibility that we lose this important document. when the prescription is lost, it takes lots of time to find a detailed prescription.

Something similar happened to Sara. Sara lost her medicine's prescription. She was unable to read the side effect of her medication and the ingredients that could cause allergy reaction. due to that, she suffered the following symptoms:

*Headache

*Upset stomach

*Vomiting

She ended up in the emergency room. The doctor asked her "Did you read your prescription?" and she said, " I lost it ".

because of this incident, Sara has gotten sick. she might not be the first to have such an experience.

1.2 Required Specification

The website we will be building will allow its users to have access to a huge database full of information related to medications they will be taking or been advised to take.

1.3 Proposed Solution

because of Sara's incident -and many like hers-, we wanted to help by creating a platform which helps her find information about any sort of medications. Our website will be a backup plan for anyone who accidently lost their medication instructions in their busy lives. It will also help the users to figure out if a certain medicine has an ingredient that they’re allergic to or if one of the medicines they’re taking will react badly with another one they’re planning to take, this usually happens with non-prescription medications that you don’t need to go to the doctor to get it. A study that took place in 2007, Orlando, Florida, involved 246 participants between the age of 19 and 50 years old, showed that Off the Counter Medication could cause a lot of complication to the patient if they’re not carful enough.

This is where our website could help. When patients know thoroughly the ingredient and the possible side effect and the possible allergy reaction, the risk of any health damages will be much reduced.

2. Project Organization

2.1 Software Process Model

We ended up using the Waterfall model. We’ve picked this model because our system was clear, and we could finish one phase before starting the next one. First, we will start by collecting data and information. Second, we will be designing the website and working on its development process. After we’re done with this step, we will evaluate how the system works and if there is any type of errors or mistakes that was done during the process, which is called testing.

2.2 Roles and Responsibilities

2.3. Tools and Techniques:

excel

Canva

Word

xmap

3. Project Management Plan

3.1 List of tasks

3.2 List of resources needed

Website for interface. (Conva)

Program for writing codes. (Eclipse)

Access to the internet and computers.

My sql for designing data base

3.3. List of Dependencies and Constrains:-

Impossible Deadlines – A successful project manager knows that repeatedly asking a team for the impossible can quickly result in declining morale and productivity. The odds of successfully completing a project under unreasonable deadlines are generally not feasible expectations

Ambiguous Contingency Plans – It's important for project managers to know what direction to take in pre-defined "what-if" scenarios. If contingencies are not identified, the entire project can become mired in an unexpected set of problems. Asking others to identify potential problem areas can lead to a smoother and successful project.

Inadequate Skills for the Project – A project sometimes requires skills that the project's contributors do not possess. Project management training can help a project leader determine the needed competencies, assess the available workers and recommend training, outsourcing or hiring additional staff.

Insufficient team skills - The team members for many projects are assigned based on their availability, and some people assigned may be too proud or simply not knowledgeable enough to tell the manager that they are not trained for all of their assigned work. Solution: Starting with the project manager role, document the core set of skills needed to accomplish the expected workload, and honestly bounce each person's skills against the list or matrix. Using this assessment of the team, guide the team towards competency with training, cross-training, additional resources, external advisors, and other methods to close the skills gap

Customers and end-users are not engaged during the project. Project teams can get wound up in their own world of internal deliverables, deadlines, and process, and the people on the outside do not get to give added input during the critical phases. Solution: Discuss and provide status updates to all project participants - keep them informed! Invite (and encourage) stakeholders, customers, end-users, and others to periodic status briefings, and provide an update to those that did not attend.

Vision and goals not well-defined - The goals of the project (and the reasons for doing it), along with the sub-projects or major tasks involved, are not always clearly defined. Clearly communicating these vague goals to the project participants becomes an impossible task. Some solutions and ideas to thrash vagueness: Determine which parts of a project are not understood by the team and other project participants - ask them or note feedback and questions that come up. Check the project documentation as prepared and tighten up the stated objectives and goals - an editor has appropriate skills to find vague terms and phrasing. Each project is, hopefully, tied into to the direction, strategic goals, and vision for the whole organization, as part of the portfolio of projects for the organization

3.5 Gantt-Chart