Feasibility+Evidence+Description

10/3 Final version of FED

10/24/2011

11/3/2011 12/04/2011 1. Risk Assessment

<< Identify our project risk, its exposure and its mitigation plan. Please note risk is a threat or probability that something will happen and possibly create loss or injury. So, if your threat or your incident is already happened, then it is a problem, not a risk. More example of risks can be found at ICM EPG> Task: Assess and Plans to Mitigate Risks>> Table 11: Risk Assessment - Constructive meeting. - Focus on the most important requirements of the project. || - Re-negotiate system requirements. || - Use other forms of communication (email, phone, etc) || Get some information about possibility of interaction between exported data and Mysql database. || Should the fact that they aren't sure if they want to use TeleParent (or some other COTS) be counted in this table? I'm not sure...
 * ** Risks ** |||||| ** Risk Exposure ** || ** Risk Mitigations ** ||
 * ^  || ** Potential Magnitude ** || ** Probability Loss ** || ** Risk Exposure ** ||^   ||
 * Personnel time constraints. Students may have other commitments (other classes, groups, etc) that may limit their ability to allocate the full amount of time needed to complete the Vale project. || 3 || 6 || 18 || - Make a schedule that will satisfy all the time arrangement of each team members.
 * The clients may have left out technical limitations which didn't recognized by the developers. As a result, the system may not meet all of the client functionality requirements. || 5 || 8 || 40 || - Prototype/Demo system often for client
 * Possible changes in clients system requirements. || 6 || 4 || 24 || - Requirements must be discussed at each phase of the incremental commitment model to ensure that all stakeholder win conditions are met. ||
 * Client availability. Our Clients are school teachers who may not be able to meet with us in needed time. || 5 || 4 || 20 || - Schedule appointments in advance with client.
 * Interoperability - Analyzing exported data from EZ grade can't be used to input the data into Mysql data base. || 6 || 7 || 42 || - Weekly meetings between clients and team are required. Every team should develop the project with the same understanding. ||
 * Current system uncertainty - Clients are using two kinds of systems, but team cannot access the systems to analyze it. To analyze exported data from EZ grade which is the program (clients are using), we need the program and license. || 4 || 6 || 24 || Contact the clients to learn how they are working by using current systems and get the program and license.

=
T1's comments I think there are more risks based on last discussion. I already wrote about risk in new PR which is uploaded on our project web site,
 * New-requirement - Client want to interact our system with their scheduling system which will be developed by USC-team12. ||
 * Prototype - prototype should be considered by three users-student,teacher, and parent. However, until end of this week, client will be out of town. We need to have time to discuss about prototype. ||
 * Uncleared requirement : client wants to get usable data from system. However, there is no information what usable data is.

=
======== || Ian, 9/28/11 After the conversation yesterday, I think it's safe to remove TeleParent from this document. Please disregard that suggestion.

Zhen Huang, 9/28/11 I have updated the final FED documents. Please review it if have any questions.