Part 1 What requirement definition is one of the most important parts of any pro
ID: 3553530 • Letter: P
Question
Part 1
What requirement definition is one of the most important parts of any project. As most of the activities that will follow are related to the requirements that were collected and formalized, we can say that any imprecision that takes place during this process can lead to problems down the road to developing the system. In relation to this, answer the following questions:
Part 2
The dynamics that are associated with the interaction among different participants participating in a JAD session who are from different hierarchical groups within the company can be difficult to manage. In relation to this, answer the following question:
Explanation / Answer
The project scope is one of the most impotant part of any project.
The project scope is the definition of what the project is supposed to accomplish and the budget (of time and money) that has been created to achieve these objectives. It is absolutely imperative that any change to the scope of the project have a matching change in budget, either time or resources. If the project scope is to build a building to house three widgets with a budget of $100,000 the project manager is expected to do that. However, if the scope is changed to a building for four widgets, the project manager must obtain an appropriate change in budgeted resources. If the budget is not adjusted, the smart project manager will avoid the change in scope.
In establishing requirements, it is important to specifically establish the functions, attributes, constraints, preferences, and expectations of the product. Usually in the process of gaining information, functions are the first ones to be defined. Functions describe what the product is going to accomplish. It is also important to determine the attributes of a product. Attributes are characteristics desired by the client, and while 2 products can have similar functions, they can have competely different attributes. After all the attributes have been clarified and attached to functions, we must determine the constraints on each of the atrributes. Preferences, which is a desirable but optional condition placed on an attribute, can also be defined in addition to its constraints. Finally, we must determine what the client's expectations are. This will largely determine the success of the product.
Testing is the final step on the road to establishing correct requirements. There are several testing methods used, as listed below.
Establishing good requirements requires people with both technical and communication skills. Technical skills are required as the embedded system will be highly complex and may require knowledge from different engineering disciplines such as electrical engineering and mechanical engineering. Communication skills are necessary as there is a lot of exchange of information between the customer and the designer. Without either of these two skills, the requirements will be unclear or inaccurate.
It is essential that requirements in safety critical embedded systems are clear, accurate, and complete. The problem with requirements is that they are often weak about what a system should not do. In a dependable system, it is just as important to specify what a system is not suppose to do as to specfiy what a system is suppose to do. These systems have an even greater urgency that the requirements are complete because they will only be dependable if we know exactly what a system will do in a certain state and the actions that it should not perform. Requirements with no ambiguities will also make the system more dependable. Extra requirements will usually be required in developing a dependable embedded system. For example, in developing a dependable system for non-computer-literate people, extra requirements should be specified to make the system safe even in exceptional or abusive situations.
Working with the notetaker, the moderator opens the forum and facilitates the discussion. The moderator remains objective and does not offer evaluative comments, nor contribute ideas. The moderator may refocus the group if it gets off-task, and may probe deeper to encourage participants to reflect more on a thought; as a way of encouraging deeper reflection, the moderator may suggest alternative methods and procedures. The moderator encourages all participants to engage in the deliberation and protects individuals and their ideas from attack. The moderator's ultimate goal is to help the group identify common ground find solutions all participants can live with