The Advisor: Difference between revisions

From Ameise-en
Jump to navigationJump to search
No edit summary
 
(22 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{NavigatorBar|Project Support in AMEISE|The Friendly Peer}}
====Advisor====
====Advisor====
The advisor can be asked by the trainee if he is in trouble.


The advisor can be asked by the trainee if he/she is in trouble.


====Purpose of the advisor====
The task of the advisor is giving the trainee a couple of questions from a predefined catalog. If the trainee chooses one of these questions, the advisor will answer it.
The advisor has an own surface in the simulation environment.
The advisor gives just current advice. That means he does not have the possibility to give statements about long time aspects in the simulation run.


====Purpose of the Advisor====


====Questioning====
The task of the advisor is to provide the trainee with a couple of questions from a predefined catalog. When the trainee chooses one of these questions, the advisor will answer it.
The following list includes advice, which is delivered by the advisor if wished:
The advisor has an own interface in the simulation environment. The advice possibilities are snap - shots, they only refer to the actual state of the simulation run. Hence, the advisor is not able to judge on aspects which would need long-term observations of a simulation run.
# '''Previous phases should not be forgotten.'''<br/>Phases always needs a previous document as base, on which they are build on. If this document is missing the phase is doomed to failure.
 
# '''The previous phase should be finished before starting a new phase.'''<br/>It is important to the following phase, that the previous phase and thus emerged previous document has been finished more than 50% to enable an overlapping of the phases. If this is not the case, the initiated phase fails. The limit of 50% depends on the model. (QS-model).
 
# ''' The previous phase should be reviewed before starting a new phase.'''<br/>To build on results of phases, it’s important to review these phases. After the review, the trainee knows that the result of this phase still has errors. These errors need to be corrected, in order to not adopt them in the next phase.  
====Questions====
# '''The previous phase should be corrected based on the review, before starting a new phase.'''<br/>After the review it is important to correct the located errors to avoid their adoption in following phases.
 
# '''After testing a correction should be performed'''<br/>Besides the review, a trainee also can make a test to find errors in documents. Those errors also have to be corrected in order to obtain a correct document. <br/>
The following list includes advices, which can be delivered by the advisor on demand:
# '''incomplete documents should be subjected to a further working-over.'''<br/> During the simulation run it happens that single phases satisfy too less requirements or include too much errors. If the advisor recognizes a situation like this, he can react to it and deliver the trainee an advice to improve the phase.
# '''Predecessor phases should not be forgotten.'''<br/>Phases always need a previous document as a basis. If this document is missing the phase is doomed to failure.
# '''The predecessor phase should be finished before starting a new phase.'''<br/>It is important for subsequent phases, that the predecessor phase and the emerged previous document have been finished by more than 50% to enable an overlapping of these phases. If this is not the case, the initiated phase fails. The limit of 50% depends on the model. (QA Model).
# ''' The predecessor phase should be reviewed before starting a new phase.'''<br/>To build on results of phases, it is important to review these phases. After the review, trainees know that the result of this phase still contains errors. These errors need to be corrected, in order to not adopt them into the follow-up phase.  
# '''The predecessor phase should be corrected based on the review before starting a new phase.'''<br/>After the review, it is important to correct the remaining errors to avoid error propagation in following phases.
# '''Testing activities should be followed by corrective activities.'''<br/>A part from a review, trainees also can carry out tests to find errors in documents. These errors also have to be corrected in order to obtain a correct document. <br/>
# '''Incomplete documents should be subjected to a further review.'''<br/> During a simulation run, it may happen that single phases don’t meet enough requirements or exhibit too many errors. If the advisor recognizes a situation like this, he can react and give advice to improve the phase.






==== Please note that ====
==== Please note that ====
{{Box1|The '''feedback''' of the advisor can be both, positive as negative!}}
{{Box1|The '''Feedback''' of the Advisor can be positive or negative!}}
 
The feedback of the advisor depends on the '''current state''' of the phase or an activity. The answer to e.g. the question whether the specification has to be revised depends on the completeness of the specification document. If the specification already satisfies the requirements, this will be communicated to the trainee. If not, the trainee will get the advice to revise the document.
The advisor '''can not''' judge on phases, which have not yet been started! In this case, the trainee gets a message, stating that there is not enough data available for assessment. 


The report of the advisor depends on the '''current state''' of the phase. e.g. if asked if the specifications has to be over-worked, it depends on the completeness of the specification-document which report the trainee gets from the advisor. If the specifications already satisfy, it is communicated to the trainee. If not, the trainee gets the advice to over-work the document.
The advisor  '''can’t''' give statements to phases, which have not been started! In this case, the trainee gets a message, which says that there are not enough data available to evaluate. 


[[de:Der Ratgeber]]
[[de:Der Ratgeber]]
[[en:Main Page]]
[[en:The Advisor]]
<!--
<!--
[[sk:Hlavná stránka]]
[[sk:Hlavná stránka]]
Line 33: Line 40:
-->
-->


{{NavigatorBar|Project Support in AMEISE|The Friendly Peer}}
  
  
[[Category:Tutorial]]
[[Category:Tutorial]]
__NOTOC__
__NOTOC__
__NOEDITSECTION__
__NOEDITSECTION__

Latest revision as of 14:13, 11 August 2013


Advisor

The advisor can be asked by the trainee if he/she is in trouble.


Purpose of the Advisor

The task of the advisor is to provide the trainee with a couple of questions from a predefined catalog. When the trainee chooses one of these questions, the advisor will answer it. The advisor has an own interface in the simulation environment. The advice possibilities are snap - shots, they only refer to the actual state of the simulation run. Hence, the advisor is not able to judge on aspects which would need long-term observations of a simulation run.


Questions

The following list includes advices, which can be delivered by the advisor on demand:

  1. Predecessor phases should not be forgotten.
    Phases always need a previous document as a basis. If this document is missing the phase is doomed to failure.
  2. The predecessor phase should be finished before starting a new phase.
    It is important for subsequent phases, that the predecessor phase and the emerged previous document have been finished by more than 50% to enable an overlapping of these phases. If this is not the case, the initiated phase fails. The limit of 50% depends on the model. (QA Model).
  3. The predecessor phase should be reviewed before starting a new phase.
    To build on results of phases, it is important to review these phases. After the review, trainees know that the result of this phase still contains errors. These errors need to be corrected, in order to not adopt them into the follow-up phase.
  4. The predecessor phase should be corrected based on the review before starting a new phase.
    After the review, it is important to correct the remaining errors to avoid error propagation in following phases.
  5. Testing activities should be followed by corrective activities.
    A part from a review, trainees also can carry out tests to find errors in documents. These errors also have to be corrected in order to obtain a correct document.
  6. Incomplete documents should be subjected to a further review.
    During a simulation run, it may happen that single phases don’t meet enough requirements or exhibit too many errors. If the advisor recognizes a situation like this, he can react and give advice to improve the phase.


Please note that

The Feedback of the Advisor can be positive or negative!

The feedback of the advisor depends on the current state of the phase or an activity. The answer to e.g. the question whether the specification has to be revised depends on the completeness of the specification document. If the specification already satisfies the requirements, this will be communicated to the trainee. If not, the trainee will get the advice to revise the document. The advisor can not judge on phases, which have not yet been started! In this case, the trainee gets a message, stating that there is not enough data available for assessment.


Retrieved from "https://ameise.aau.at/ameise/en/index.php?title=The_Advisor&oldid=2047"