Systems development life cycle (SDLC)
The overall process for developing information systems from planning and analysis through implementation and maintenance
old system that is fast approaching or beyond the end of tis useful life within an organization.
the process of transferring information from legacy system to a new system.
modifies software to meet specific user or business requirements.
Off the shelf application software
supports general business processes and does not require any specific software customization
1 of 7 SDLC phases Establishes a high-level plan of the intended project and determines project goals
person or event that is the catalyst for implementing major changes for a system to meet business changes.
technique for generating ideas by encouraging participants to offer as many ideas as possible in a short period without any analysis until all the ideas have been exhausted
temporary activity a company undertakes to create a unique product, service, or result
the application of knowledge skills, tools, and techniques to project activities to meet project requirements
individual who is an expert in project planning and management, defines and develops the project plan, and tracks the plan to ensure the project is completed on time and on budget.
describes the business need and the justification, requirements, and current boundaries for the project
formal, approved document that manages and controls the entire project.
2 of 7 phases of the SDLC that Involves analyzing end-user business requirements and refining project goals into defined functions and operations of the intended system
the specific business requests the system must meet to be successful.
the 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 company
the users’ actual signatures indicating they approve all of the business requirements
3 of 7 phases of the SDLC that Establishes descriptions of the desired features and operations of the system including screen layouts, business rules, process diagrams, pseudo code, and other documentation
4 of 7 phases of the SDLC that Involves taking all of the detailed design documents from the design phase and transforming them into the actual system
is a disciplined approach for constructing information systems through the use of common methods, techniques, or tools.
Computer aided software engineering (CASE)
provide automated support for the development of the system
control objects for information and related technology (COBIT)
set of best practices that helps an organization to maximize the benefits of an information system, while at the same time establishing appropriate controls to ensure minimum errors.
Object oriented languages
group data and corresponding processes into objects.
Fourth generation languages
programming languages that look similar to human languages.
5 of 7 phase of the SDLC that Involves bringing all the project pieces together into a special testing environment to eliminate errors and bugs, and verify that the system meets all of the business requirements defined in the analysis phase
defects in the code of an information system.
detail the steps the system must perform along with the expected result of each step.
6 of 7 Phases of the SDLC that Involves placing the system into production so users can begin to perform actual business operations with it
is created that highlights how to use the system and how to troubleshoot issues or problems.
runs over the internet or on a CD or DVD, and employees complete the training on their own time.
is held in a classroom environment and led by an instructor
group of people who respond to users’ questions
7 of 7 phases of the SDLC that Involves performing changes, corrections, additions, and upgrades to ensure the system continues to meet its business goals
makes system changes to repair design flaws, coding errors, or implementation issues.
makes system changes to reduce the chance of future system failure.
a set of policies, procedures, standards, processes, practices, tools, techniques, and tasks that people apply to technical and management challenges.
A sequence of phases in which the output of each phase becomes the input for the next
modern design approach where the designers and system users use an iterative approach to building the system.
Builds a small scale representation or working model of the system to ensure it meets the user and business requirements.
Consists of a series of tiny projects. foundation of multiple agile methodologies.
Aims for customer satisfaction through early and continuous delivery of useful software components developed by an iterative process using the bare minimum requirements
Rapid application development methodology
1 of 4 primary forms of agile methodology. Emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system to accelerate the systems development process
Extreme programming methodology
2 of 4 primary forms of Agile methodology. Breaks a project into tiny phases, and developers cannot continue on to the next phase until the first phase is complete
Rational unified process methodology
3 of 4 primary forms of Agile methodology. Provides a framework for breaking down the development of software into four gates:Inception Elaboration Construction Transition
Uses small teams to produce small pieces of deliverable software using sprints, or 30-day intervals, to achieve an appointed goal
Primary reasons for project failure
Unclear or missing business requirements
Skipping SDLC phases
Failure to manage project scope
Failure to manage project plan
easy to quantify and typically measured to determine the success of failure of a project.
difficult to quantify or measure
the measure of the tangible and intangible benefits of an information system.
a trigger that enables a project manager to close the project before completion.
Individuals and organizations actively involved in the project or whose interests might be affected as a result of project execution or project completion
The person or group who provides the financial resources for the project
A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities and includes
Project scope statement
criteria are useful reminders on how to ensure that the project has created understandable and measurable objectives
graphical network model that depicts a project’s tasks and the relationships between them.
is a logical relationship that exists between the project tasks, or between a project task and milestone
estimates the shortest path through the project ensuring all critical tasks are completed from start to finish.
simple bar chart that lists project tasks vertically against the project’s time frame listed horizontally.
Uses the professional expertise within an organization to develop and maintain its information technology systems
An arrangement by which one organization provides a service or services for another organization that chooses not to perform them in-house
engaging another company within the same country for services
contracting an outsourcing arrangement within a company in a nearby country.
using organizations from developing countries to write code and develop systems. Geographically far away.
Need essay sample on "Ch. 9 MIS"? We will write a custom essay sample specifically for you for only $ 13.90/page