Comments to document: Business Driver, Use Cases, and Feature Requirements

[juha.tiihonen@tkk.fi]

I tried to capture the comments on the document. Please feel free to correct, if necessary!

Comments to architecture:
Israel: Can identify a lot from the Figure. Sometimes team leader would like e.g. change scheduling from Field. Interaction (with customer) is typical, and actual customer requirements cause blurring of what has been identified. (Jiri: May have tactical needs. ) Summary & point: Use cases may require that FFMII must be richer than originally planned.  Click Software will provide corresponding use cases.

Comments to use cases:
Israel: certainly give good (ideas) for many real-life situations. Use case 4: maybe not sure about that one. This use case drives a much simplified interface. Might be more logical to include it in other use cases? 

Some hints on forthcoming use cases: Situation: asset management. Need to access information about assets. Maybe e.g. switchboard, another asset is also relevant, need information on that. It may become necessary to create a new task on-the-fly; assign maybe to yourself. Sketching functionality into mobile. Jiri: Assignee could be a creator. Israel. Happens quite a lot. Quite a few assets are usually close. 
Israel volunteers to write a use case for asset management. Provides it by next meeting.