Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
117 Cards in this Set
- Front
- Back
|
System development |
process of modifying or replacing a portion or all of an information system normally undertaken by a project team composed of systems analysts, programmers, accountants, and other people in the organization. |
|
|
governance structure |
oversees projects makes sure they are selected and implemented in a way that ensures their congruence with goals, objectives, and strategies of the organization, as well as with legal and regulatory structures |
|
|
system development life cycle |
planning and analysis, design, and implementation |
|
|
top-down sequential approach: |
1. plan developed 2. design is developed to produce an architectural blueprint for implementation 3. working system is that conforms to the architectural plan is developed and implemented |
|
|
Systems planning and feasibility analysis |
1. top management discussion and planning 2. est. systems planning steering committee 3. est. overall objectives and constraints 4. developing a strategic information systems plan 5. identifying/prioritizing specific areas for focus 6. serves as a basis of the analysis and preliminary design 7. assemble team |
|
|
steering committee |
representing top management and all major functions within the organization. focus on overall current and future information needs of the company. not for details |
|
|
key success factors |
characteristics that distinguish a company from its competitors and are the keys to its success |
|
|
strategic systems plan |
written document tat incorporates both the short and long-run goals
|
|
|
Traditional systems development process
|
follows a somewhat rigid top-down sequential approach: A plan is developed. A design is developed. A working system that conforms to the plan is developed and implemented. Big-design-up-front |
|
|
Waterfall approach
|
Most appropriate in situations in which the plans and designs can be very clearly defined |
|
|
Systems development
|
means defining, shaping, and reshaping the four enterprise architecture domains: 1.The business architecture 2.The information architecture 3.The application architecture 4.The technical architecture |
|
|
Adapted Traditional Rigid Approach |
The traditional rigid approach has been adapted in two ways to become flexible. Iterative or agile approaches: All phases of the life cycle are carried on simultaneously. Breaking projects into smaller pieces: Greatly minimizes risk of project failure. |
|
|
Systems planning |
involves identifying subsystems within the information systems.
Identify problem areas that need to be dealt with either immediately or sometime in the future. |
|
|
Overview of Systems Planning and Analysis |
Objectives of Systems Analysis Gain an understanding of the existing system (if one exists). Identify and understand problems. Express identified problems of information needs and system requirements. Clearly identify subsystems to be given highest priority. Focus: Identify critical success factors. Give special attention to these factors. |
|
|
Systems Planning and Feasibility Analysis |
Careful attention must be given to developing an overall systems plan and strategy. Resources will be targeted to the subsystems where the needs are greatest. Duplication and wasted effort will be minimized. Systems development will be consistent with the strategic plan of the organization. |
|
|
Steps in Systems Analysis |
Step 1: Survey Current System Step 2 Identity Information Needs
Step 3: Identity system Requirements Step 4: Develop Systems analysis Report |
|
|
Four objectives of the systems survey: |
|
|
|
Phase 1: Survey the Current System |
The success or failure of a development project will depend to a large extent on the quality of the relationship between the development team and the individuals working on the system. |
|
|
Approaches to bridge communications gap: |
|
|
|
Sources for Gathering Facts |
Inside Sources:
Outside sources:
|
|
|
Analysis of Survey Findings |
Strengths and weaknesses of the subsystem under study are thoroughly analyzed. Standards used as benchmarks: Effectiveness Efficiency Bottlenecks |
|
|
Effectiveness |
– the system accomplishes the objectives set forth in the systems planning phase. |
|
|
Efficiency |
– whether objectives are achieved at the lowest possible cost. |
|
|
Bottlenecks |
represent weaknesses in the system where small changes can result in major improvements. |
|
|
Phase 2: Identify Information Needs |
Several basic approaches can be followed: Identify the manager’s primary job responsibilities. Identify the means by which the manager is evaluated. Identify some of the major problems the manager faces. Identify the means by which the manager evaluates personal output. Specified in terms of inputs and outputs. |
|
|
Inputs |
– specify the specific needs that must be met in order for that subsystem to achieve its objectives. |
|
|
Outputs |
– the input requirements for one subsystem will, in turn, specify output requirements for another subsystem. |
|
|
Phase 4: Develop a Systems Analysis Report |
Final output of systems analysis: Summary of the scope and purpose relationship of project to overall strategic information system plan Description of any overall problems Summary of the decisions Specification of system performance requirements Overall cost budget and timetable Recommendations |
|
|
Fact-Gathering Techniques |
depth/structure interview open/closed ended questionnaire
|
|
|
Techniques for Organizing Facts |
work measurement/distribution flow charting general/decision table/logical data flow/ systems/detail decision/hierarchical/matrix analysis narratives file/report summaries |
|
|
Fact-Gathering Techniques |
Depth/structured interview open/closed ended questionnaire document reviews: flowchart, organization charts, procedure/operations/reference manuals, historical records oservation |
|
|
Techniques for Organizing Facts |
Work measurement/distribution Hierarchical function |
|
|
Warnier-Orr Methodology |
– based on analyzing the outputs of an application and factoring the application into a hierarchical structure of modules to accomplish the necessary processing. |
|
|
Structured Systems Analysis and Design |
Comprises a classical waterfall approach to systems development that begins with a general description of a particular system. Logical flow and business process diagrams versus flowcharts
Systems design versus systems analysis |
|
|
Steps in Structured Systems Analysis |
Develop logical data flow diagrams Define data dictionaries Define access methods Define process logic |
|
|
Structured English |
is a special language for describing process logic that uses several key words. |
|
|
Iterative Systems Development |
Rapid Application Development (RAD): Rational Unified Process (RUP): |
|
|
Rapid Application Development (RAD): |
Involves a mixture of structured and iterative development.
A key feature is the use of prototype designs, which form tentative designs relative to the finished system. |
|
|
Rational Unified Process (RUP): |
breaks project life cycle into four phases: 1.Inception phase 2.Elaboration phase 3.Construction phase 4.Transition phase |
|
|
Object-Oriented Design and Analysis |
Object-Oriented (OO) approach
|
|
|
Object-Oriented (OO) approach |
differs radically from the classic approach that is based on DFDs, successive refinement, structured English, and related program coding. Using OO terminology, objects are said to possess methods (things they do) and attributes (data related to objects.) |
|
|
Diagrams in Process Orientation versus Object Orientation |
The classical top-down approach is process oriented and relies on DFDs and BPMN diagrams. OO design and analysis is object oriented and relies on OO UML diagrams. Accountants and auditors are interested in studying internal controls in terms of business process rather than business objects. |
|
|
Preparing and Submitting the Systems Design Specifications |
Detailed design proposal includes:
|
|
|
Business Process Blueprinting |
Prepackaged set of blueprints for all of a company’s business processes SAP-supplied blueprints The design team then focuses on adapting the initial set of blueprints to its own needs.
Focus on processes that are unique and important to strategies and goals. |
|
|
Resources-Events-Agents (REA) Model |
provides general model capturing/recording events and attributes. Capture events; How events relate to each other; How the events and their interrelationships are stored and processed. Journals, ledgers, and accounts are not needed and are instead generated as reports or “views.” |
|
|
General Design Considerations |
output (report or document) database data processing data input controls and security measures |
|
|
Design Techniques |
Forms design Database design Systems Design Packages |
|
|
Forms design |
- process of designing specific forms. Should focus on producing documents that provide effective interfaces between managers and the information system. |
|
|
Database design |
– available techniques: Data structure diagrams Record layouts File analysis sheets File-related matrices |
|
|
Systems Design Packages |
Prepackaged design methodologies to assist in systems development cycle: Computer-Aided Software Engineering (CASE) automated engineering discipline. DFDs, Narrative documentation, Screen and report prototypes Data dictionary descriptions |
|
|
Choosing Software and Hardware |
Advantages of purchased software packages:
Disadvantages of canned software packages (purchased software packages): Rarely exactly meets company needs Dedicated software package – intended for a narrow audience |
|
|
When evaluating purchased software |
use decision-table format consider following: How close is the fit to what is needed? How stable is the software vendor? Is there a trial period? How many other installations have used the software? How flexible is the software? Is the software user friendly? Are source programs supplied? |
|
|
upward compatible |
– easily upgrade-able to a larger or faster model in the future without losing existing data or programs. |
|
|
agile approach
|
an approach to systems development that us normally iterative and that focuses on keeping with certain best practices
|
|
|
attribute
|
data items related to objects
|
|
|
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 stages
|
|
|
BPEL
|
short form of WS-BPEL
|
|
|
cost-effectiveness
|
benefits of a design should exceed it's cost
|
|
|
Detailed design proposal
|
everything necessary to actually implement a design project, including timetables, a budget, personnel requirements, and design documents
|
|
|
Forms design
|
process of designing specific forms
|
|
|
information needs analysis
|
analysis of specific decisions made by managers in terms of the information imputs
|
|
|
integration
|
design criterion that means the avoidance of collecting and maintaining the same data items in more than one place
|
|
|
iterative approach
|
an approach to systems development in which the initial plans and designs are subject to revision as the project develops
|
|
|
object
|
basic unit of analysis in object-oriented analysis and design methodologies. Objects possess methods and attributes.
|
|
|
model driven architecture
|
trademarked approach to development based on the object and business processes; it automatically
|
|
|
pseudocode
|
structured english type of systems documentation that includes provisions for error conditions and data file access
|
|
|
software as a service (SAAS)
|
software application, suite of applications, or software services that are delivered over the internet entire accounting systems are delivered
|
|
|
standardization
|
design criterion that all data items are to be entered in a standard format and assigned a common name when used in more than one place
|
|
|
systems development life cycle
|
the concept that every systems development project goes through essentially the same process of lifecycle of systems analysis, systems design, and systems implementation
|
|
|
turnkey systems
|
computer packages that meet the specific needs of an individual situation with minimal design word.
|
|
|
WS-BPEL
|
Web services business process execution languages is an executable computer language that facilitates interactions between business processes and web services
|
|
|
systems implementation
|
Formal plans and controls should beestablished to address the problems that can occur during systemsimplementation.
|
|
|
Three major steps in systemsimplementation:
|
1.Establishplans and controls
2.Executeactivities as planned 3.Followup and evaluate the new system |
|
|
Step1: Establish Plans and Controls for Implementation
|
In order to manage the implementationproject adequately, specific plans need to be developed:1.abreakdown of the project into various phases,
2.specificbudgets applicable to each phase, and3.specifictimetables applicable to each project phase. |
|
|
Scheduling Techniques:
|
|
|
|
Software Process Improvement andCapability (SPICE) ISO 15504
|
is a process-based development approachthat focuses on the “maturity” of the process being developed.
|
|
|
Other project management methods:
|
|
|
|
Step2: Executing Implementation Activities
|
|
|
|
Step2: Executing Implementation Activities cont
|
In order to provide a smooth transition,management and the system team should make a formal announcement regarding the execution of the project.
Reassureemployees Minimizerumors Organization of a Special Project Team |
|
|
EmployeeTraining
|
|
|
|
Acquiringand Installing New Computer Equipment
|
|
|
|
DetailedSystems Design
|
|
|
|
Documentingthe New System
|
Documentation is one of the mostimportant parts of systems implementation.
|
|
|
Good documentation can serve a wide rangeof useful purposes:
|
1)trainingnew employees,
2)providingprogrammers and analysts with useful information for future program evaluationand modification activities,3)providingauditors with useful information for evaluating internal controls, and 4)assistingin ensuring that systems design specifications are met. |
|
|
FileConversion
|
A typical problem in systemsimplementation is that of data conversion:Insome cases, files maintained manually must be converted to computer format.Conversioncan be an expensive, time-consuming process.Datascreening may be necessary after entering the information into the computer dueto errors in the data input process.
|
|
|
There are three basic approaches to thefinal testing of the system:
|
|
|
|
Direct approach
|
- involves switching to the new system and abandoning the old system at a fixed point in time (cutover point).
|
|
|
Parallel approach
|
– involves running the new and old systems simultaneously.
|
|
|
Modular conversion
|
involves phasing in the new system in segments.
|
|
|
Step3: Evaluating the New System
|
|
|
|
Planningand Organizing a Systems Project
|
|
|
|
WorkMeasurement Techniques
|
|
|
|
Accuracyof Estimates
|
|
|
|
Lowballing
|
– purposely or inadvertently submitting unreasonably low time or cost estimates to obtain a contract.
|
|
|
ProjectAccounting
|
|
|
|
ProjectDevelopment Environment
|
|
|
|
Softwareapplication framework
|
|
|
|
All-in-Oneand Integrated Platforms
|
There is a trend toward integrating ITgovernance, enterprise architecture, business process modeling, and managementinto application suites.
Theseplatforms can work in conjunction with the components of the developmentenvironment. |
|
|
ControlOver Nonfinancial Information Systems Resources
|
|
|
|
Measuring hardwareperformance involves:
|
Systemsutilization
Systemsdowntime Systemsresponsiveness |
|
|
Systemsutilization
|
Ratios such as server CPU time used to time available
|
|
|
Systems downtime
|
Percentage of time that the application is unavailable for use.
|
|
|
Evaluating softwareperformance:
|
Surveysystem users
Constantlymonitor software performance |
|
|
Controls relating to personnelinvolve preparing performance reports for:
|
Softwaretechnicians
Hardwarerepair persons |
|
|
Auditingthe Information System
|
|
|
|
Maintainingand Modifying the System
|
|
|
|
Bugs
|
– computer programming errors that might not be detected until the system actually begins operation.
|
|
|
Control of system modifications:
|
|
|
|
Phase3: Identify the Systems Requirements
|
|
|
|
application solution stack
|
a group of software components needed to deliver a workable application
|
|
|
critical path
|
a list of activities that are critical in that if any one of them is delayed. the entire project will be delayed
|
|
|
Gantt chart
|
a scheduling technique that graphically depicts both the actual and the planned times for activities but does not show the relationships between various activities
|
|
|
integrated development environment (IDE)
|
a software platform for writing programming code
|
|
|
network diagram
|
a scheduling technique that depicts the order in which activities must be performed
|
|
|
project collaboration platform
|
a software platform that serves to optimize management of the communication chain in software development projects
|
|
|
project management
|
tools used to track progress and manage resources for a systems development project
|
|
|
software versioning system
|
a software platform that keeps current and historical versions of the software source code
|
