Project: health-watcher

Stakeholders

Name: Citizen
Description: Any person who wishes to interact with the system.

Name: Employee
Description: Health System employee, placed on DIEVS.

Name: SystemOwner

Name: SystemDeveloper
Description: developers that design and implement the system, as well as for caring through the testing and homologation of the system.

Concerns

Name: ResponseTime
Description: The response time must not exceed 5 seconds.
Classification: Non-Functional
Sources:

• NFR Framework catalogue

• The response time must not exceed 5 seconds to log the system.
• The response time must not exceed 5 seconds to submit a complaint specification.
• The response timea must not exceed 5 seconds to submit a query information.

Name: Encryption
Description: The system should use a security protocol to send data over the internet.
Classification: Non-Functional
Sources:

• documents

• The system should use a security protocol to send complaint specification over the internet.
• The system should use a security protocol to send query information over the internet.

Name: Compatibility
Description: Allow exchange of information with the SSVS system (Sanitary Surveillance System). This exchange will firstly be only to query sanitary licenses and on another time – when SSVS have deployed the Complaint Control module – it will be given the automatic entry of the Sanitary Surveillance complaint nature.
Classification: Non-Functional
Sources:

• document (use cases)

• Allow exchange of information with the SSVS system during complaint specification.
• Allow exchange of information with the SSVS system during query specification

Name: AccessControl
Description: ensure only authorised operations are carried out by citizens and employees.
Classification: Non-Functional
Sources:

• NFR Framework

• guarding againts unauthorized change log data
• guarding againts unauthorized register employees data
• guarding againts unauthorized register table data
• guarding againts unauthorized update complaint
• guarding againts unauthorized update employee
• guarding againts unauthorized update health unit
• allow citizens to register complaints
• allow citizens to access complaint data
• allow citizens to access health unit data

Name: QueryInformation
Description: Makes possible for a citizen to perform queries. Query Health Guide: The citizen might query: -Which health units take care of a specific specialty. -Which are the specialties of a health unit. Query Diverse Information The citizen might query: Information about the complaint made by the citizen: -Complaint specification. -Situation (OPENED, SUSPENDED, or CLOSED). -Technical analysis. -Analysis date. -Employee that made the analysis. Information about diseases: -Description. -Symptoms. -Duration.
Classification: Functional
Sources:

• documents (use cases)

• 1.The system receives the type of query
• 2.1In the case of a query on specialties grouped by health units, the citizen selects the unit to be queried.
• 2.2In the case of a query on health units grouped by specialties, the citizen selects the specialty to be queried.
• 2.3In the case of a query on complaints, the citizen provides the complaint code.
• 2.4In the case of a query on diseases, the citizen selects the disease to be queried.
• 2.The system receives the data for the query
• 3.The system shows the query result.

Name: Register Complaint
Description: This use case makes possible for a citizen to register complaints. Complaints can be: Animal Complaint – DVA •Animals apprehension. •Control of vectors (rodents, scorpions, bats, etc.) •Diseases related to mosquitos (dengue, filariose). •Animals maltreatment. Food Complaint - DVISA •Cases where it is suspicious the ingestion of infected food. Diverse Complaint - DVISA •Cases related to several reasons, which are not mentioned above (restaurants with hygiene problems, leaking sewerage, suspicious water transporting trucks, etc.). The three kinds of complaints have the following information in common: •Complaint data: description (mandatory) and observations (optional); •Complainer data: name, street, complement, district, city, state/province, zip code, telephone number and e-mail. All these information are optional; •Complaint state (mandatory), which might be: OPENED, SUSPENDED or CLOSED. In the event of a registration, its state must be OPENED; •The system must register the complaint registration date. In addition to these data, each complaint has its specific ones. They are: Animal Complaint – DVA •Kind of animal (mandatory), amount of animals (mandatory), disturb date (mandatory); •Disturb location data: street, complement, district, city, state/province, zip code and telephone number. All these information are optional. Food Complaint - DVISA •Victim's name (mandatory); •Victim's data: street, complement, district, city (or closest one), state/province, zip code and telephone number. All optional; •Amount of people who ate the food, amount of sick people, amount of people who were sent to a hospital and amount of deceased people. All mandatory; •Location where the patients were treated, suspicious meal. All optional. Diverse Complaint - DVISA •Age (mandatory), scholar level (optional), occupation (optional); •Street, complement, district, city, state/province, zip code and telephone number of the closest location to the complaint location. All optional.
Classification: Functional
Sources:

• documents (use cases)

• 1.The system obtain the kind of complaint;
• 2.The system registers the kind, date and time of the attendance;
• 3.The system shows the specific screen for each type of complaint;
• 4.The system obtain the data;
• 5.The system saves the complaint (with the OPENED state), return the code for the attendance, so that the citizen can take note and query for the situation of his/her complaint.

Name: Login
Description: allows an employee to have access to restricted operations on the Health-Watcher system.
Classification: Functional
Sources:

• documents (use cases)

• 1. The system receives the login and password from the employee
• 2. The system validates the password

Name: RegisterTables
Description: makes possible the registration of the system tables. For this use case are expected the insert, update, delete, search and printing. The tables are the following ones: •Health unit (unit code, unit description). •Specialty (code and description). •Health unit / Specialty (health unit and specialty). •Employee (login, name and password). •Type of disease (code, name, description, symptom and duration). •Symptom (code and description). •Type of disease / Symptom (type of disease and symptom).
Classification: Functional
Sources:

• documents (use cases)

• 1. The system receives the option to register (insert/update) in one of the tables.
• 2.The system receives the data.
• 3.The system saves the data.

Name: UpdateComplaint
Description: makes possible the update of the state of a complaint.
Classification: Functional
Sources:

• documents (use cases)

• 1. The system receives the option update complaint
• 2. The system requests the complaint number
• 3. The system shows the complaint code and its type
• 4. The system receives the conclusion
• 5. The system updates the complaint conclusion and the information about the employee who gave it

Name: RegisterNewEmployee
Description: makes possible the registration of new employees on the system.
Classification: Functional
Sources:

• documents (use cases)

• 1. The system receives the following information about the new employee: Login, Name, Password (with special fied for confirmation)
• 2. The system receives the confirmation of the operation

Name: UpdateEmployee
Description: makes possible the update of the employee's data on the system.
Classification: Functional
Sources:

• documents (use cases)

• 1. The system receives the option update employee
• 2. The system receives employee data to be updated:  Name  New pasword (with extra field for confirmation)  Current password
• 3. The system receive the confirmation to update
• 4. The system updates the employee's data

Name: UpdateHealthUnit
Description: makes possible the update of health unit's data.
Classification: Functional
Sources:

• documents (use cases)

• 1. The system receive the option update health unit.
• 2. The system receives the health unit data to be updated.
• 3. The system shows the health unit's data.
• 4. The system receives data to update.
• 5. The system updates the health unit's data.

Name: ChangeLoggedEmployee
Description: makes possible the logged employee to be changed.
Classification: Functional
Sources:

• documents (use cases)

• 1. The system obtain the option change logged employee.
• 2. The system shows the login screen, and from then on, this main flow will follow the one described on [Login.FR10].

Name: Usability
Description: The system should have an easy to use GUI, because it might be used by any person who has access to the internet. The system should have an on-line HELP to be consulted by any person that uses it. Several functionalities of the system should provide context sensitive help for the user (e.g., explain what are the types of complaints).
Classification: Non-Functional
Sources:

• documents (use cases)

• The system should have an easy to use to complaint specification
• The system should have an easy to use to login
• The system should have an easy to use to query information

Required By:

Name: Availability
Description: The system should be available 24 hours a day, 7 days a week. Because of the nature of not being a critical system, the system might stay off until any fault is fixed.
Classification: Non-Functional
Sources:

• documents (use cases)

• the system need to be available to complaint specification 24 h a day and 7 days a week.
• the system need to be available to login 24 h a day and 7 days a week.
• the system need to be available to query information 24 h a day and 7 days a week.

Name: Standards
Description: The system must be developed according to the standards established by X , responsible for the norms and standardization of systems for the City Hall.
Classification: Non-Functional
Sources:

• documents (use cases)

Name: HardwareandSoftware
Description: Here are listed the hardware and software to be used for the system to work. SOFTWARE • One license for the Microsoft Windows for the workstation HARDWARE • One computer with: Pentium III processor, 256 MB of RAM memory, net card 3Com 10/100. This equipment shall be used by the attendant as a workstation.
Classification: Non-Functional
Stakeholder-Priorities:

Stakeholder	Priority
SystemDeveloper	Important
SystemOwner	Very Important

Name: Distribution
Description: The system should be capable of running on separate machines. For example, the system core could be running on one machine and the servlets on another.
Classification: Non-Functional
Sources:

• documents (use cases)

Name: UserInterface
Description: The user interface must be implemented using servlets.
Classification: Non-Functional
Sources:

• documents (use cases)

Name: Operational Environment
Description: Software, Hardware and User-Interface
Classification: Non-Functional
Sources:

• document (use cases)

Name: Persistence
Description: The persistence mechanism should store data about the complaints, employees, health units, deceases, specialities and citizens that complaint. The system must be capable of extension on the storage matter, making possible to use, arrays or different databases (MySQL, Oracle, etc.)
Classification: Non-Functional
Sources:

• documents (use cases)

Name: Concurrency
Description: The system must be capable to handle 20 simultaneous users.
Classification: Non-Functional
Sources:

• NFR Framework catalogue

• the system must be capable to handle 20 simultaneous users.

Name: Performance
Description: The system must be capable to handle 20 simultaneous users. The response time must not exceed 5 seconds.
Classification: Non-Functional
Sources:

• document (use cases)

Name: Security
Description: Security Protocol (encryption) and Access Control
Classification: Non-Functional
Sources:

• document (use cases)

Concerns-Contributions:

Name: Error and Exception Handling
Description: Several functionalities might raise errors while the user interacts with the system and require different handling techniques. General errors that apply to most cases are due to missing information (e.g. users do not fill in the required fields in an entry form) and the system signals the error and show which fields need to be provided. Other error might be related to entering invalid data and the error handling mechanism should try either to avoid that or to raise the error and suggest the correction.
Classification: Functional
Sources:

• documents (use cases)

• display an error mensage "employee is invalid".
• display an error message "name or the current password is missing";
• display an error message "the password or the employee is not valid"
• display message " employee information was not provided";
• display message "information was not provided";

Matchpoints

Name: MP_QueryInformation
Owner: QueryInformation
Rule: (Compatibility||AccessControl)>>(Availability||Concurrency||Usability||ResponseTime||QueryInformation)>>Security
Rule Visualization:

Associated Concerns:

Concern
Compatibility
AccessControl
Availability
ResponseTime
Security
Concurrency
Usability

Name: MP_UpdateComplaint
Owner: UpdateComplaint
Rule: Login>>Updatecomplaint>>AccessControl
Rule Visualization:

Associated Concerns:

Concern
AccessControl
Login

Name: MP_UpdateEmployee
Owner: UpdateEmployee
Rule: (Login>>UpdateEmployee>>AccessControl)[>Error and Exception Handling
Rule Visualization:

Associated Concerns:

Concern
Error and Exception Handling
AccessControl
Login

Name: MP_RegisterComplaint
Owner: Register Complaint
Rule: (Compatibility||AccessControl)>>(Availability||Concurrency||Usability||ResponseTime||Register Complaint)>>Security
Rule Visualization:

Associated Concerns:

Concern
Compatibility
AccessControl
Availability
ResponseTime
Security
Concurrency
Usability

Name: MP_RegisterTables
Owner: RegisterTables
Rule: Login>>RegisterTables>>AccessControl
Rule Visualization:

Associated Concerns:

Concern
AccessControl
Login

Name: MP_RegisterNewEmployee
Owner: RegisterNewEmployee
Rule: (Login>>RegisterNewEmployee>>AccessControl)[>Error and Exception Handling
Rule Visualization:

Associated Concerns:

Concern
Error and Exception Handling
AccessControl
Login

Name: MP_ChangeLoggedEmployee
Owner: ChangeLoggedEmployee
Rule: (Login>>ChangeLoggedEmployee>>AccessControl)[>Error and Exception Handling
Rule Visualization:

Associated Concerns:

Concern
Error and Exception Handling
AccessControl
Login

Name: MP_Login
Owner: Login
Rule: ((Availability||Usability||ResponseTime||Login)>>AccessControl)[>Error and Exception Handling
Rule Visualization:

Associated Concerns:

Concern
AccessControl
Error and Exception Handling
Availability
ResponseTime
Usability

Name: MP_UpdateHealthUnit
Owner: UpdateHealthUnit
Rule: (Login>>UpdateHealthUnit>>AccessControl)[>Error and Exception Handling
Rule Visualization:

Associated Concerns:

Concern
Error and Exception Handling
AccessControl
Login

History

Operators

Visualizations:

Dependencies:

Contributions:

Decompositions: