SDS
- Introduction Document Goals
- Main Goals
- Main Product Features & Capabilities
- Related Documentation
- UML Modeling
- Persistence
- Non-functional Requirements
- Initial Test Plan (optional)
This document will describe in detail the software architecture and design of the project native application.The document we will describe the structure of the various classes.This document will provide several views of the system design to facilitate communication and understanding of the system. He intends to capture and pass on the significant architectural and design decisions made for this project
- Planning the system correctly and efficiently
- Preparation of neat code divided into organized structures
- Checking the correctness of the software design.
- Preparing an orderly structure so that we can write a neat code divided into organized structures
- To set an anchor for the readiness of our functional application
- Check the correctness of the structure
| Main Capability | Capability Description | Risks Level | |
|---|---|---|---|
| 1 | Register to the system | Anti-Drug-Jerusalem members need to be able to register to the system and get their permissions | High |
| 2 | Add and Deleting permissions to the system | The administrator can add and download permission to sync the app with Google calendar page for an organization. | Medium |
| 3 | Add event at Real Time Location | Every volunteer adds a real-time event from the field and shares the rest of the volunteers with The application.The application should report the event location every 30-60 second. | High |
| 4 | Generate Reports and send in Real Time Location | The volunteer will fill out a report on a real-time event from the field, information about a specific child for the child's documentation and sending the information to the staff with The application.The application should report the event location every 30-60 second. | High |
| 5 | See the Reports description and Show | The manager can open, edit and then report and give highlights on the location and event. | Medium |
| 6 | Add new requests | A manager can add new requests as needed to events that occurred in the field. | Medium |
| 7 | Request for volunteer and Add new volunteer | The system administrator accepts the volunteers' request to volunteer. You can add new volunteers with certain certificate | Medium |
| 8 | Manufacture Statistic Report | The system will provide statistics with different criteria, such as an event, a child and a place. | Medium |
| 9 | Using App | User( administrator and a volunteers) can view events synced with the app, switch from monthly / weekly / daily view mode, select an organization's event view, and view the list of recommendations. | Low |
| 10 | Future analysis | Administrator will be able to recover all the information of existing events for a future analysis of mistakes and making the team a volunteer more efficient in the future | Medium |
- Still the organization has not decided where to store database. Currently the application's data, the information about the activities, as well the system structure and objects - will be stored in a database placed at the organization’s server firebases.
- When the device regains connection, the real-time Database synchronizes the local data changes with the remote updates.
- Additional maintenance and management will be in the hands at Anti Drug & Alcohol Jerusalem.
The design suggested in this document is related to the following non-functional requirements:
- security - The system protects the details of patients in the organization by not being accessible to any user or available to the public, but only to the organization's managers who need this information.
- maintainability - The customer is given the ability to change the product according to his requirements, meaning that the customer will be able to continue to repair and modify the finished application easily without us. We provide this option because the application provides the customer with things that can be changed such as: route changes (different tour routes can change due to changes in levels of activities in certain places), change of team leaders (departure or change of staff), and so on..
- usability - The product will contribute to the efficiency of the organization's work: through a more convenient and accessible information gathering, access to the tour map in real time. When these are the main problems that are currently being created for the customer.
In order to make sure that our program will create genuine reports and will show the correct and realistic statistics, there is a need in tests that will verify this issue.
- Accessing from different Mobile Phones .
- Opening dummy accounts and check the behavior the application.
- After insert a new volunteers to the BD there is a need to verify that all data was fully and correctly uploaded.
- After Add and remove volunteers from the trainer lists.
- Creating a genuine report that reflects the correct information.
- Check the availability of push notifications by sending event and attendance form submit.
- Build prototype sketch and present it to the client
- Testing the application with the client framework
- Test the database by trying to save a lot of information and see how we maintain it effectively.