What is wrong if the body of a method which behavior is specified by a story diagram is empty whereas other method bodies are fine and the codegeneration seems to work properly?
Such a situation occurs if the story diagram of the method with the missing body is errorneous. Since the bodies of the methods are generated by a different code generator than the rest of the code, the code generation process can fail individually for separat methods. This is a result of missing analysis which inform immediately if a specification is valid or not. We are aware of that disadvantage and hope to present a solution soon. Until than, you can avoid such errors by completing the control flow of a method in each step of development. For instance, if you add a “For Each”-Activity first complete the control flow by adding all necessary transitions. Or if you add a “Success” transition add the “Failure” transition immediately before you start to implement the activity. This ensures that the code generator does not quit due to a broken control flow.
Related Questions
- What is wrong if the body of a method is empty when the behavior is specified by a story diagram whereas other method bodies are fine and the codegeneration seems to work properly?
- What is wrong if the body of a method which behavior is specified by a story diagram is empty whereas other method bodies are fine and the codegeneration seems to work properly?
- What is the significance for you in translating the story of their bodies into a body of language?
