Busy. Please wait.
or

show password
Forgot Password?

Don't have an account?  Sign up 
or

Username is available taken
show password

why


Make sure to remember your password. If you forget it there is no way for StudyStack to send you a reset link. You would need to create a new account.
We do not share your email address with others. It is only used to allow you to reset your password. For details read our Privacy Policy and Terms of Service.


Already a StudyStack user? Log In

Reset Password
Enter the associated with your account, and we'll email you a link to reset your password.

Remove ads
Don't know
Know
remaining cards
Save
0:01
To flip the current card, click it or press the Spacebar key.  To move the current card to one of the three colored boxes, click on the box.  You may also press the UP ARROW key to move the card to the "Know" box, the DOWN ARROW key to move the card to the "Don't know" box, or the RIGHT ARROW key to move the card to the Remaining box.  You may also click on the card displayed in any of the three boxes to bring that card back to the center.

Pass complete!

"Know" box contains:
Time elapsed:
Retries:
restart all cards




share
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.

  Normal Size     Small Size show me how

MIS160 Exam 2

Crossword Bank

TermDefinition
Functional Requirements that encapsulate the activities that the system must perform
FURPS an acronym that stands for functional, usability, reliability, performance, and security requirements
Usability Requirements that encapsulate the operational characteristics related to users, such as the user interface, related work procedures, online help, and documentation
Stakeholder persons who have an interest in the successful implementation of the system
Client person or group that provides the funding for a system development project
Open-ended questions that encourage discussion or explanation
UML standard set of model constructs and notations defined by the Object Management Group
Activity A diagram that describes user (or system) activities, the person who does each activity, and the sequential flow of these activities
User Story one short sentence in everyday language of the end user that states what a user does as part of his or her work
Acceptance features/criteria that must be present in the final system for the user to be satisfied
Use Case an activity that the system performs, usually in response to a request by a user
Event something that occurs at a specific time and place, can be precisely identified, and must be remembered by the system
Actor an external agent; a person or group that interacts with the system by supplying or receiving data
Temporal an event that occurs as a result of reaching a point in time
State an event that occurs when something happens inside the system that triggers some process
Automation the boundary between the computerized portion of the application and the users who operate the application but are part of the total system
Includes a relationship between use cases in which one use case is stereotypically included within the other use case
Brainstorming a technique to identify problem domain objects in which developers work with users in an open group setting
Attributes descriptive pieces of information about things or objects
Compound an attribute that consists of multiple pieces of information but is best treated in the aggregate
Association a term, in UML, that describes a naturally occurring relationship between specific things, sometimes called a relationship
Relationship a term that describes a naturally occurring association between specific things, sometimes called an association
Cardinality a measure of the number of links between one object and another object in a relationship
Subclass the subordinate or more specialized class in a generalization/specialization relationship
Inheritance the concept that specialization classes inherit the attributes of the generalization class
System Sequence Diagram (SSD) a diagram showing the sequence of messages between an external actor and the system during a use case or scenario
Lifeline the vertical line under an object on a sequence diagram to show the passage of time for the object
Created by: marcjimenez