The total race experience with flying team needs analysis

From the selected project, and to understand the needs of teachers first met, then now ready to finalize the documentation requirements, it has been a month's time. This month, we have been doing is to demand analysis. It can be said requirements analysis through to our every meeting throughout our task every week.

Our project is to make a APP, dedicated to home care chronic obstructive pulmonary disease. The purpose of this system is to provide a personalized home or community care services and comprehensive guidance to patients with stable chronic obstructive pulmonary disease severity, proactive, effective management. Systems use environmental monitoring equipment to detect and regulate environmental indicators that the room of the patient, the patient's care to provide a comfortable environment; monitor the patient's wearable devices through a variety of signs data associated with COPD; by analyzing the patient's family in the process of rehabilitation care data generated using advanced data analysis techniques to provide early warning of acute exacerbation, the disease trend analysis and individualized behavioral interventions for patients. System builders COPD care path for patients with severe grade of a comprehensive assessment, and generate the corresponding care plan to guide patient care activities. By movement of the index patient assessment, recommend reasonable exercise prescription for patients; while providing health education to enhance self-management of patients.

The first time and met the teachers to communicate, the teacher gave us a book project approval, for us to understand what our product goals is to use what method, for whom provision of services, to what purpose. This is the beginning of our needs analysis, project by project books and teacher's description, the teacher let us first consider the needs of our extracted what. After the panel discussion we have come to this result:

 

 

Yes, it is such a record, not even a requirements document. . .

When the second and teachers to communicate, the teacher made it clear that, first of all explain this demand is not standardized, not even in the form of documents. The second major problem is too simple, so in the second week of our task is to write the first draft of requirements specification document to try to standardize the way to express our understanding of the needs. After the completion of the preparation of the document, the third meeting and teachers to communicate again, the teacher said, and the way we analyze the demand point of view is not right. For example login page, which has been refined to a prototype design, we should first analyze the major issues and what needs there, and then expand each big demand by small demand.

For our project, in fact, the core of the demand can be divided into three parts: generate care plans, the implementation of care plans, as well as health assessment. According to these three aspects, think again: what should be the plan of care? What are the basic action there? What features should be implemented ? Care plan is the equivalent of a reminder to the user, what time the patient should do something, but the source of care plans is the doctor's advice. No orders we will be unable to generate care plans, thus the need for order entry this demand. That generates a care plan, we must consider how to perform. Therefore, under this great demand there is a daily reminder services , including medication reminders, reminders to use equipment, sports reminders. After collecting data related to, for the user to generate a digital illustration, it can intuitively display the physical condition of the patient. It may take a digital picture of what form? Graphically, scores, etc. as well as intuitive body diagram line chart and so on.

After the third communication, we made it clear that a lot needs to start writing the first version of the document was last modified. In a subsequent communication, we have and continue to ask questions and think to solve. For example: If the patient does not enter orders how to do? For order entry what form we can use? Families can understand the physical condition of the patient? Digital illustration how that it would be better? By what means? The system is only responsible to remind, that the completion of the user how to get? What are the implications compliance will be? And so many problems, constantly modifying documents and communicate with the teacher, the slowly resolved.

Just last week, we draw up projects use case diagram, class diagram and timing diagrams, this way, let us demand of the project more clearly, this week's task is to confirm and finalize the teacher needs documentation.

In the process of identifying needs, we have a great harvest. We feel that the original requirements document should not be difficult to prepare, it can be made after the actual start, only to find simple and fundamental as you'd like. A start demand is even more obscure, in constant and teachers to communicate, the demand only gradually become clear, almost each modification requirements document will have a new problem. If it is not written in the document, and we may not notice the problems. We take turns to write and modify the process, but also so that we have mastered the method of writing requirements documents, we actively exchange process is to deepen mutual understanding and team collaboration.

Determine the demand, we will be able to further carry out the next plan, we believe in the future of cooperation, we will certainly gain a satisfactory result.

Guess you like

Origin www.cnblogs.com/RonnieDaddy/p/11789353.html