Embed Code - If you would like this activity on your web page, copy the script below and paste it into
your web page.
Normal Size Small Size show me how
| Question | Answer |
|---|
| legacy system
| old system that is fast approaching or beyond the end of its useful life within an organization
|
| Conversions
| process of transferring information from a legacy system to a new system
|
| Software customerization
| modifies software to meet specific user or business requirements.
|
| off the shelf applications software
| supports general business processes and does not require any specific software customization to meet the organization's needs.
|
| Systems Development Life Cycle (SDLC)
| overall process for developing information systems, from planning and analysis through implementation and maintenance.
|
| SDLC
| begins with business need proceeds to an assessment of fuctions a system must have to satisfy the need and ends whne the benifits of the system out way the cost of its maintenance .
|
| Project scope
| describes the business need (the problem the project will solve) and the justification, requirements and current boundaries for the project.
|
| Phases in the systems development life cycle in order
| Planning Analysis Design development testing implementation/Maintenance
|
| Planning phase
| establishes a high level plan of the intended project and determines project goal.
|
| Change Agent
| person or event that is the catalyst for implementing major changes for a system to meet business changes.
|
| Brainstorming
| technique for generating ideas by encouraging participants to offer as many ideas as possible in a short period without any analysis until all ideas have been exh
|
| project management
| is the application of knowledge, skills, tools, and techniques to project activities to meet project requirements.
|
| project manager
| an individual who is an expert in project planning and management, defines and develops the project plan and tracks the plan to make sure its is on time and budget.
|
| project plan
| formal approved document that manages and controls the entire project.
|
| analysis phase
| firm analyzes its end-user business requirements and refines project goals into defined functions and operations of the intended system.
|
| Business requirements
| are specific business request the system must meet to be successful, so the analysis phase is critical because business requirements drive the entire systems development effort
|
| requirements management
| process of managing changes to the business requirements throughout the project.
|
| requirements definition document
| prioritizes all of the business requirements by order of importance to the
|
| Case tools
| tools used by software engineers use to automate support for the development of the system.
|
| sign-off
| consists of the users' actual signatures indicating they approve all the business requirements.
|
| Joint application development (JAD)
| session where employees meet, sometimes for several days to define or review the business requirements for the system.
|
| Computer-aided software engineering (CASE)
| tools are software suites that automate systems analysis, design, and development. Diagrams can provide the basics for the automatic generation of the system if the y are developed using a CASE Tool.
|
| Design phase
| establishes descriptions of the desired features and operations of the system, including screen layouts, business rules, process diagrams, pseudo code, and other documentation.
|
| Graphical User Interface (GUI)
| interface to an information system. Has the ability to model the information system screens for an entire system using icons, buttons, menus, and submenus. Data models represent a formal way to express data relationships.
|
| development phase
| takes all the detailed design documents from the design phrase and transforms them into the actual system. Goes from preliminary designs to actual physical implementation.
|
| software engineering
| disciplined approach for constructing information systems through the use of common methods, techniques, or tools. Uses computer-aided software engineering tools (CASE).
|
| Control objects for information and technology (COBIT)
| set of best practices that helps an organization to maximize benefits of an information system, while establishing appropriate controls to ensure minimum errors.
|
| scripting language
| programming method that provides for interactive modules to a website.
|
| object oriented languages
| group of data and corresponding processes into objects.
|
| Fourth -generation languages (4GL)
| programming languages that look similar to human languages. (example Find all records where name is smith)
|
| testing phase
| brings all the project pieces together into a special testing environment to eliminate errors and bugs and verify that the system meets all the business requirements defined in the analysis phase.
|
| Bugs
| are defects in code of an information system.
|
| Test conditions
| detail the steps the system must perform along with the expected result of each step.
|
| Alpha testing
| assess if the entire system meets the design requirements of the users
|
| development testing
| test the system to ensure it is bug-free
|
| integration testing
| verify that separate systems can work together, passing data back and forth correctly
|
| System testing
| verify that the units or pieces of code function correctly when integrated.
|
| User Acceptance testing (UAT)
| determine if the system satisfies the user and business requirements.
|
| development phase
| takes all the detailed design documents from the design phase and transforms them into the actual system.
|
| implementation phase
| phase that organizations place system into productions so users can begin to preform actual business operations with it.
|
| User documentation
| created that highlights how to use the system and how to troubleshoot issue or problems.
|
| online training
| training runs over the internet or on cd0r dvd, and employees complete the training their own time and pace.
|
| unit testing
| tests individual units or pieces of code for a sytem
|
| preventive maintenance
| makes system changes to reduce the chance of future system failures.
|
| Corrective maintenance
| makes system changes to repair design flaws, coding errors or implementation issues
|
| phases in the systems development life cycle
| Planning analysis design development testing
implementation/maintenance
|
| maintenance phase
| organization performs changes, corrections, additions, upgrades to ensure the system continues to meet business goals.
|
| Five primary reasons projects fail
| Unclear or missing business requirements Skipped SDLC phases Balance of the triple constraints Cost of finding errors Changing technology
|
