UseCases - Use Cases Classifier Generalizable Element...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck (Slides adapted from Dr. Stephen Clyde with permission)
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Introduction Use Case : “. .. a typical interaction between a user and a computer system”, Booch Here, “user” is anything that needs or invokes the functionality of the system “Computer system” is the system being modeled Use cases can capture and document the user-visible functionality of a system Use cases capture how the system will benefit the user Each use case achieves a discrete goal for the user
Background image of page 2
Goals Use cases help everyone come to a common understanding of what the system should do Developers End-users Domain Experts Use-cases are a communication tool for the design (not the implementation) Use cases represent a functional requirement of your system (as a whole)
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
User Goals User Goals are statements that represent what the users need to accomplish, independent of specific software features Examples of user goals for a Student Records Management System Ensure that a student’s records reflects courses taken and grades received in those courses Allow only authorized faculty and staff to update student records Ensure that students can obtain copies of their own (and only their) records in a timely manner
Background image of page 4
System Interactions Represent expected interacts between users and the computer-based system Suggest how the system fulfills a user goal Examples: A teacher alters a course grade for a student by selecting a semester selecting a course selecting a student reviewing the previous grade entering a new grade confirming the change A process for an administrator to create a new user A process for granting a user access rights
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
User Goals vs. System Interactions In some cases, system interactions and user goals can be very similar However, confusing system interactions with user goals or neglecting to identify user goals can fail to bring out and document the reasons why a system should must certain features result in lost opportunities for creativity
Background image of page 6
User Goals vs. System Interactions
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 03/26/2012 for the course CS 321 taught by Professor Kinga during the Spring '12 term at George Mason.

Page1 / 26

UseCases - Use Cases Classifier Generalizable Element...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online