-
Use Case Problem
If a stakeholder does not want to read your entire use case, what could you do convey the message across?
priyankam9
- Apr 27th, 2008
Simple thing is to have a Use Case Daigram adjacent to the Use Case, the daigram should tell the user what the use case will do, so that by looking into that satkeholder will get to knoe the functionality of the usecase instead of going through the whole shit.
triptigupta
- Apr 10th, 2008
BA should always have supplementary artifacts such as - flowcharts, wireframes of the screens and so on which explains the entire use case. So even if the stakeholder does not want to read the entire ...
-
My.Application.Log.WriteEntry , by default , writes to the file:
A) assemblyname.logB) Applog.LogC) Application.LogExplanation: This file is located in the application’s data directory.
