Ch 11 Systems Planning, Analysis, and Design
WS-BPEL
Web Services Business Protection Execution Languages (or as abbreviated BPEL). WS-BPEL is an executable computer language that facilitates interactions between business processes and Web services
dedicated software package
a commercially available software package that is intended for a narrow audience
rational unified process (RUP)
a four-phase iterative development process and software product from IBM that focuses on achieving milestones at the end of each phase
Warnier-Orr Methodology
a methodology and diagramming technique for analyzing the outputs of an application and factoring the application into a hierarchical structure of modules to accomplish the necessary processing
REA (Resources-Events-Agents) model
a model of the accounting system that focuses on recording events along with their impact on related resources and connection to related agents
software as a service (SaaS)
a software application, suite of applications, or software services that are delivered over the internet. Entire Accounting systems are delivered as SaaS
structured English
a special language for describing process logic that uses several key words, including IF, THEN, ELSE IF, and SO
waterfall approach
a synonym for the big-design-up-front approach to systems development
Model Driven Architecture
a trademarked approach to development based on modeling a given problem or project based on the object and business processes; it automatically transforms the model to computer software using a standard transformation language
strategic systems plan
a written document that incorporates both short and long run goals relating to the company's systems development effort
object-oriented approach
an approach to development that is used on DFDs, successive refinement, structured English, and related program coding
structured systems analysis and design
an approach to systems analysis that begins with a very general description of a particular system and then proceeds through a logically related set of steps, each increasing in detail
iterative approach
an approach to systems development in which the initial plans and designs are subject to revision as the project develops
big-design-up-front
an approach to systems development that focuses on producing initial plans and designs that are not subject to much change during the design and implementation phases
agile approach
an approach to systems development that is normally iterative and that focuses on keeping with certain best practices
rapid application development
an approach to systems software development that combines iterative and structured approaches
information needs analysis
analysis of specific decisions made by managers in terms of the information outputs
object
basic unit of analysis in object-oriented analysis and design methodologies. Objects posses methods (things that object do) and attributes (data related to objects)
key success factors
characteristics that distinguish a company from its competitors and that are keys to its success
steering committee
committee representing top management and all major functional areas within the organization that is charged with guiding the overall systems development effort
upwardly compatible
computer hardware that is easily upgradeable to a larger or faster model without losing existing data or programs
turnkey systems
computer packages that meet the specific needs of an individual situation with minimal design work
attributes
data items related to objects
standardization
design criterion that all data items are to be entered in the standard format and assigned a common name when used in more that one place
feasibility
design criterion that it must be possible to actually implement the design specifications
integration
design criterion that means the avoidance of collecting and maintaining the same data items in more than one place
detailed design proposal
everything necessary to actually implement a design project, including timetables, a budget, personnel requirements, and design documentation
systems planning
identifying subsystems with the information system that need special attention for development
BPEL
short form of WS-BPEL
canned software packages
software packages purchased from a vendor
pseudocode
structured-English type of systems documentation that includes provisions for error conditions and data file access
cost-effectiveness
the benefits of a design should exceed its costs
systems development life cycle
the concept that every systems development project goes through essentially the same process of life cycle of systems analysis, systems design, and systems implementation
forms design
the process of designing specific forms
systems analysis
the process of understanding existing systems and problems, describing information needs, and establishing priorities for further systems work
methods
things that objects do
bottlenecks
weaknesses in a system where small changes can result in major improvements in performance
