Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
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
Normal Size Small Size show me how
CIS454-Ch.4(Part 1)
Business Process & Functional Modeling
| Term | Definition |
|---|---|
| Functional Models | __________ ______ describe business processes and the interaction of an information system with its environment. |
| 2 Types of OO Models for IS | 1) Use cases 2) Activity diagrams |
| Use Cases | ___ _____ are used to describe the basic functions of the information system. |
| Activity Diagrams | ________ ________ support the logical modeling of business processes and workflows. |
| UML | ___ has been adopted as the standard notation by the Object Management Group (OMG). |
| Use Case | A formal way of representing the way a business system interacts with its environment; illustrates the activities performed by the users of the system; can document both "as-is," and "to-be." |
| Activity Diagram | Can be used for any type of process modeling activity. |
| Process Models | Depicts how a business system operates; illustrates the process or activities that are performed, and how objects (data) move among them; can document "as-is," and "to-be." |
| Logical Models | (includes activity diagrams and use-cases) - models that describe the business domain's activities without suggesting how they are conducted (Problem domain models). |
| Physical Models | Models that provide information that is needed to ultimately build the system. |
| True | By focusing on logical activities first, analysts can focus on how the business should run without being distracted with implementation details. |
| Use Cases | ___ _____ are the discrete activities that the users perform, such as selling CD's, ordering CD's, and accepting returned CD's from customers. |
| True | An analyst can employ use cases and the use-case diagram to better understand the functionality of the system at a very high level. |
| Use-case diagram | A ___-____ _______ is drawn when gathering and defining requirements for the system. |
| 4 Elements of a Use-Case Diagram | 1) Actors 2) Use Cases 3) Subject Boundaries 4) Set of relationships among actors, actors & use cases, and use cases. |
| 4 Use-Case Relationships | 1) Association 2) Include 3) Extend 4) Generalization relationships |
| Actor | Not a specific user, but instead is a role that a user can play while interacting with the system; can also represent another system in which the current system interacts with (represented by stick figures on the use-case diagram). |
| Actors | ______ represent the principal elements in the environment in which the system operates. |
| Actors | ______ can provide input into the system, receive output from the system, or both. |
| Specialized Actor | (i.e. - new patient) - A type of actor that is different from a general/regular actor in some way; inherits the behavior of the more general actor and extends it in some way. |
| Use Cases | ___ _____ are connected to actors through association relationships; these relationships show which use cases the actors interact with. |
| Asterisk | A many-to-many relationship between an actor and use-case is represented using this. |
| Use Case | Depicted by an oval in the UML, is a major process that the system performs and that benefits an actor or actors in some way; it is labeled using a descriptive verb - noun phrase. |
| Subject Boundary | A box that defines the scope of the system and clearly delineates what parts of the diagram are external or internal to it. |
| Subject Boundary | A _______ ________ can be used to separate a software system from its environment, a subsystem from other subsystems within the software system, or an individual process in a software system. |
| 5 Steps to Identify Major Use Cases | 1) Review requirements definition 2) Identify subject's boundaries 3) Identify primary actors & goals 4) Identify business processes and major use cases 5) Review current set of use cases |
| Goals | Represents the functionality that the system must provide for the actor, in order for the system to be a success. |
| Boundary | As actors are identified and their goals are uncovered, the ________ of the system will change. |
| True | The trick is to select the right size so that you end up with 3-9 use-cases in each system. |
| Packages | (i.e. - logical groups of use cases) - a container used to group use-cases together, in order to make the diagrams easier to read and keep the models at a reasonable level of complexity. |
| 8 | If more than _ use-cases, then the use-cases are too small, or the system boundary is too big. |
| Use-Case Diagram | A drawing that shows the system boundary, the actual use-cases, actors, and the various associations between these components; encourages the use of information hiding. |
| True | The major strength of the use-case diagram is that it provides the user with an overview of the business processes. |
| 4 Major Steps in Drawing a Use-Case Diagram | 1) Place & Draw Use cases 2) Place & draw actors 3) Draw subject boundary 4) Add associations |
| Association Relationships | Links an actor with the use-case with which it interacts. |
| Include | Represents the inclusion of the functionality of one use-case within another. |
| Extend | Represents the extension of the use-case to include optional behavior. |
| Generalization Relationship | Represents a specialized use-case to a more generalized one. |
Created by:
Jordan.WBL