Systems Analysis Exam 1
use case diagram
a picture showing system behavior along with the key actors that interact with the system
Objective statement
a series of statements that express an organization's qualitative and quantitative goals for reaching a desired future position
Incremental commitment principle
a strategy in systems analysis and design in which the project is reviewed after each phase and continuation of the project is rejustified
project initiation
activities designed to assist in organizing a team to conduct project planning
true
an activity diagram shows the conditional logic for the sequence of system activities needed to accomplish a business process
extend relationship
an association between two use cases where one adds new behaviors or actions to the other
repository
an integrated and standard database used in CASE to provide product tool integration
corporate strategic planning
an ongoing process that defines the mission, objectives, and strategies of an organization
information systems planning
an orderly means of assessing the information needs of an organization and defining the systems, databases, and technologies that will best satisfy those needs
activity diagram
can be used to depict the flow of control from activity to activity, model work flow and business processes, help in use case analysis
steering committee
can only identify potential development projects
methodologies
comprehensive, multiple-step approaches to systems development that will guide your work and influence the quality of your final product
primary deliverables resulting from studying and documenting a systems processes
context data flow diagram (DFD), DFDs of the current logical system, thorough descriptions of each DFD component
data store
data at rest, which may take the form of many different physical representations
process models
data flow diagrams that concentrate on the movement of data between processes
data flow
data in motion, moving from one place in a system to another
report
enables you to work backwards from the information on a report to the data that must have been necessary to generate them
project planning vs. general IS planning
general information systems planning focuses on assessing the information systems needs of the entire organization
project identification and selection
identification and assessment of all possible systems development projects that an organization unit can undertake
forms
indicate what data flow in or out of a system and which are necessary for the system to function
project scope statement
is useful for ensuring that both you and your customer gain a common understanding of the project, is a short document prepared for the customer that describes what the project will deliver and outlines all work required to complete the project, is a very easy document to create because it typically consists of a high-level summary of the BPP information
competitive strategy types
low-cost producer, product differentiation, product focus or niche
corporate strategy involves
mission statement, objective statements, description of competitive strategy
Bottom-up source
project initiatives stemming from managers, business units, or the development group
Top-down source
projects identified by top management or by a diverse steering committee.
sequence diagrams
represent dynamic models of interactions between objects
SDLC phases
sequencing of phases has a compelling logic, relationships between phases are well specified, the different phases are clearly defined
activation
shows the time period during which an object performs an operation, either directly or through a call to some subordinate operation
baseline project plan
specifies detailed project activities for the next life cycle phase, analysis, and less detail doe subsequent project phases, contains all information collected and analyzed during project initiation and planning, and is used by the project selection committee to help decide if the project should be accepted, redirected, or canceled
information systems analysis and design
the complex organizational process through which computer-based information systems are developed and maintained
objective of the planning process
the development of a Baseline Project Plan and Project Scope Statement
context diagram
the diagram that shows the scope of the system, indicating what elements are inside and which are outside the system
strategic alignment
the extent to which the project is viewed as helping the organization achieve its strategic objectives and long-term goals
instance or generic
the forms sequence diagrams can be presented in
business case
the justification for an information system, presented in terms of the tangible and intangible economic benefits and costs and the technical and organizational feasibility of the proposed system
Competitive strategy
the method by which an organization attempts to achieve its mission and objectives
formal system
the official way a system works as described in organizational documentation
economic feasibility
the purpose is to identify the financial benefits and costs associated with the development project
return on investment (ROI)
the ratio of the net cash receipts of the project divided by the cash outlays of the project, enabling tradeoff analysis to be made between competing projects
business process reengineering
the search for, and implementation of, radical change in business processes to achieve breakthrough improvements in products and services
SDLC
the traditional methodology used to develop, maintain, and replace information systems
An activity diagram can be used for all of the following reasons:
to model work flow and business processes, help in use case analysis, and to depict the flow of control from activity to activity
