chapter-4-5-6-10-examreviews Flashcards
use case
an activity the system performs
user goal technique
an approach for identifying use cases in which an analyst talks to all users to get them to describe their goals in using the system
Event
an occurrence at a specific time and place that can be described and is worth remembering by the system
CRUD technique
Create - Read/Report - Update - Delete an approach in which an analyst looks at each type of data and includes use cases that create the data - read or report on the data - updates the data - delete the data
Event Decomposition
an analysis technique that focuses on identifying the events to which a system must respond and then determining how the system must respond.
External Event
An event that occurs outside the system - usually initiated by an external agent or actor
Temporal Event
an event that occurs as a result of reaching a point in time
state event
an event that occurs when something happens inside the system that triggers the need for processing. (internal events)i.e. sale of an item results in low stock - inventory reorder must take place
Event table
a catalog of use cases that lists events in roes and key pieces of information about each event in columns
Trigger
a signal that tells the system that an event has occurred - either the arrival of data needing processing or a point in time
Source
an external agent or actor that supplies data to the system
response
an output produced by the system that goes to a destination
destination
an external agent or actor that receives the data from the system
use case description
a description that lists the processing details for a use case
Brief Description
short paragraph of the use case
Intermediate Description
Title - main flow & exception conditions
Fully developed description
Contains use case name-scenario-triggering event-brief description-actors-related use cases - stakeholders -preconditions -postconditions -flow of activities - exception conditions.
things
tangible - roles - organizational - devices - sites/locations - incidents/events/or interactions
relationship
a naturally occurring association among specific things such as an order is placed by a customer and an employee works in a department
Attribute
one piece of specific information about a thing
cardinality
the number of associations that occur among specific things - 1:1 - 1:M - M:M
Entity Relationship Diagram ERD
The squares with the zero/one to many lines
Analysis Activities
Gather info - Define Sys Req - Prioritize Requirements - Prototype for Feasibility & discovery - Generate & evaluation alternatives - Review recommendations with Management
Gathering Info
interviewing users - watching users - review planning docs - review policy statements - study documentation from existing system
Define System Requirements
Uses modeling to help define system requirements
Prioritize Requirements
Identify the most essential requirements of the new system
Prototype for Feasibility and Discovery
used to better understand the user’s needs. Checks the feasibility of certain approaches to the business need.
Generate and Evaluate Alternatives
Many alternatives exist that will need to be evaluated for the best match
Review Recommendations with Management
When all other analysis activities are complete the review with management will happen to decide if best to proceed or not
Functional Requirements
a system requirement that describes and activity or process that the system must perform
Non-functional requirement
other than activities -such as technology-performance - usability - reliability and security
Models
representation of some aspect of the system being built
Mathematical Model
series of formulas that describe technical aspects of a system.
Descriptive Models
narrative memos - reports or lists that describe some aspect of a system.
Graphical Model
diagrams and schematic representations of some aspect of a system
Logical Model
Any model that shows what the system is required to do without committing to any one technology
Physical Model
Any model that shows how the system will actually be implemented
Stakeholders
all the people who have an interest in the success of a new systemthe usersthe clients (paying for it)the technical staff
Information Gathering Techniques
questionnaires - interview users - review existing documentation - observe business processes - research vendor solutions - conduct JAD sessions
Traditional approach
System of processes, processes interact with data entities, processes accept inputs and produce outputs.
OO approach
System is collection of interacting object, objects interact with people and each other, objects send and respond to messages.
Data flow diagram DFD
Represents sys requirements as processes, external agents, data flows, and data stores
Level of abstraction
Any modeling technique that breaks the system down into a hierarchical set of increasingly more detailed models.
DFD fragment
A DFD that represents the system response to one event withina single process symbol
Physical and logical DFDs
DFDs can be either physical system model, a logical system model or a combination of both.
Black hole
Process or data store with a data input that is never used to produce a data output.
Miracle
Process or data store with a data element that is created out of nothing.
Rule 7+-2
Modeling rule that limits the number of components or connections to no more than nine
Minimization of interfaces
Simplicity by limiting the number of of connections between model components.
Structured English
Writing process specifications that combines structured programming techniques with narrative English.
Decision table
A table representation of processing logic containing decision variables, decision variable values and actions or formulas
Decision tree
A graphical description of process logic that uses lines organized like branches of a tree.
Data flow definition
Text description of a data flows content and internal structure.
Data store definitions
Data store on the DFD represents a data entity on the ERD no separate definition iOS usually needed. If no ERD link analyst defines data store as a collection of elements.
Data element definitions
Describes a data type such as string, integer, floating point, or Boolean.
Activity-location matrix
A table that describes the relationship between processes and the locations in which they are performed.
Activity data matrix
A table that describes stored data entities the locations of which they are accessed, and the nature of the accesses.
Automation System Boundary
partitions the data flow diagram processes into manual processes and those that are to be included in the computer system
System Flow Chart
Representation of various computer programs, files, databases, and associated manual procedures that make up a complete system.
Structure Chart
hierarchical diagram showing the relationships between the modules of a computer program
Data Couples
the individual data items that are passed between modules in a program call.
Transaction Analysis
the development of a structure chart based on a DFD that describes the processing for several types of transactions
Transform Analysis
the development of a structure chart based on a DFD that describes the input-process-output data flow
Module coupling
the manner in which modules relate to each other; the preferred method is data coupling
Automation System Boundary
partitions the data flow diagram processes into manual processes and those that are to be included in the computer system
Module Cohesion
a measure of the internal strength of a module
Flowcharting
is a visual method that uses boxes and lines to describe the flow of logic in a program.
Structured English
describes the structure of the program in regular english
pseudocode
closer to programming language
three layer design
division of application software into the view, business logic and data access layers
viewer layer
executing on a client workstation, the user’s view
business logic layer
java server side components
data layer
oracle dbms - talks to the databases
