This Week on Clinical Swift

Early on in the development process, most of the information gathered from future users consists of documents (e.g., forms, policy/procedure) and interview data (e.g., feature descriptions, desired functions, specific dislikes, wish-list items, etc.). As a software designer using object-oriented design, the next major step in making this information actionable is capturing how users will interact with the planned software via use cases.   This week on Clinical Swift…

Textual Analysis: Moving from Use Cases to Classes


Leave a Reply

Your email address will not be published. Required fields are marked *