information system - Answers collects, processes, stores, and outputs information
sub-system - Answers components of another system
components - Answers hardware, software, inputs, outputs, data, people, and procedures
super system - Answers collection of systems
automation boudary - Answers separates automated part of system from manual (human)
sdlc - Answers process of building, deploying, using, and updating an information system
predictive sdlc - Answers project planned entirely in advance
adaptive sdlc - Answers planning leaves room for contingencies
Planning, analysis, design, implementation, support - Answers 5 project phases
pure waterfall approach - Answers Assumes project phases can be sequentially executed Project
drops over the "waterfall" into the next phase
modified waterfall approach - Answers Tempers pure waterfall by recognizing phase overlap Informs
many current projects and company systems
inception - Answers in this phase you develop and refine system vision
elaboration - Answers in this phase you define requirements and core architecture
construction - Answers in this phase you continue design and implementation
transition - Answers in this phase you move the system into operational mode
techniques - Answers Collection of guidelines Enables an analyst to complete an activity or task
best practices - Answers proven techniques
unified process - Answers object-oriented system development methodology
use case - Answers Activity that the system carries out Basis for defining requirements and designs
discipline - Answers set of functionally related activities
Business modeling, requirements, design, implementation, testing, and deployment - Answers 6 main
UP development disciplines
Project management, configuration and change management, and environment - Answers 3
additional support UP disciplines
object - Answers thing with attributes and behaviors
User interface Problem domain objects - Answers types of objects
encapsulation - Answers combining attributes and methods into one unit
information hiding - Answers separating specification from implementation
inheritance - Answers extending the characteristics of a class
polymorphism - Answers ability for dissimilar objects to respond to the same message
CASE - Answers Database repository for information system
microsoft visio - Answers emphasizes technical drawing
rational rose - Answers CASE tool supporting object-oriented approach Strongly identified with UP
methodology
modeling - Answers Draws together various team members and users Simulates electronic execution
of tasks Spurs refinement and expansion of requirements Promotes informal training
mathmatecal, descriptive, graphical - Answers 3 types of models
predictive development - Answers Requirements assumed stable and feasible Requirements specified
and validated beforehand
adaptive development - Answers Requirements are assumed difficult to document Requirements
subject to change System prototypes used in validation process
structured walkthrough - Answers Reviews findings Reviews models based on findings Objective: find
errors and problems Purpose: ensure that model is correct
functional requirements - Answers requirements that are directly related to use cases Documented in
graphical and textual models
non-functional requirements - Answers requirements that have to do with performance, usability,
reliability, and security Documented in narrative descriptions to models
external event - Answers Occur outside the system Usually caused by external agent
temporal event - Answers Occurs when system reaches a point (deadline) in time
state event - Answers Asynchronous events responding to system trigger
general class symbol - Answers rectangle with three sections
generalization/specialization notation - Answers Inheritance hierarchy Rank things the more general
to the more special