Term
| Systems Development Life Cycle (SDLC) |
|
Definition
| The process for developing information systems for planning and analysis through implementation and maintenance–the foundation for all systems development methodologies, and literally hundreds of different activities are associated with each phase |
|
|
Term
|
Definition
Planning
Analysis
Design
Development
Testing
Implementation
Maintenance |
|
|
Term
|
Definition
| The planning phase involves establishing a high-level plan of the intended project in determining project goals |
|
|
Term
|
Definition
| The analysis phase involves analyzing the end-user business requirements and refining project goals into defined functions and operations of the intended system |
|
|
Term
|
Definition
| The detailed set of business requests that the system must meet in order to be successful |
|
|
Term
|
Definition
| The design phase involves describing the desired features and operations of the system including screen layouts, business rules, process diagrams, pseudocode, and other documentation |
|
|
Term
|
Definition
| The development phase involves taking all the detailed design documents from the design phase and transforming them into the actual system |
|
|
Term
|
Definition
| The testing phase involves bringing all the project pieces together into a special testing environment to test the system for errors, bugs, and interoperability in verify that the system meets all of the business requirements designed in the analysis phase |
|
|
Term
|
Definition
| The implementation phase involves placing the system introduction so users can begin to perform actual business operations with the system |
|
|
Term
|
Definition
| The maintenance phase involves performing changes, corrections, additions, and upgrades to ensure the system continues to meet the business goals |
|
|
Term
|
Definition
| And activity-based process in which each phase of the SDLC is performed sequentially from planning through implementation and maintenance–no longer serves most of today's development efforts. It does not accommodate midcourse changes; it requires you know exactly what you want to do on the project and a steady state until work is done |
|
|
Term
|
Definition
| And activity-based process in which each phase of the SDLC is performed sequentially from planning through implementation and maintenance–no longer serves most of today's development efforts. It does not accommodate midcourse changes; it requires you know exactly what you want to do on the project and a steady state until work is done |
|
|
Term
| Agile Software development methodologies |
|
Definition
| Aims for customer satisfaction through early and continuous delivery of useful software components developed by an innovative process with a design point that uses the bare minimum requirements–helps refine feasibility and supports the process for getting rapid feedback as functionality as introduced |
|
|
Term
|
Definition
| Emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system to accelerate the systems development process |
|
|
Term
|
Definition
| A smaller scale representation or working model of the users requirements were proposed design for an information system |
|
|
Term
|
Definition
| like other agile methods, breaks the project into tiny phases, and developers cannot continue onto the next phase until the 1st phase is complete- emphasizes the fact that the faster the communication were feedback the better the results |
|
|
Term
|
Definition
| owned by IBM, provides a framework for breaking down the development of software into 4 gates: inception, elaboration, construction, transition |
|
|
Term
|
Definition
| Uses small teams to reduce small pieces of deliverable software using sprints, or 30 day intervals, to achieve an appointed goal |
|
|
Term
|
Definition
| The application of knowledge, skills, tools, and techniques to project activities to meet project requirements |
|
|
Term
|
Definition
| The 3 variables of time, cost, and scope are interdependent–all projects are limited in some way by these 3 constraints–the relationship between these variables is such that if anyone of the 3 factors changes at least one other factor is likely to be affected |
|
|
Term
|
Definition
| occurs when the scope of the project increases |
|
|
Term
|
Definition
| occurs when developers add extra features that were not part of the initial requirements |
|
|
Term
|
Definition
| An Arrangement by which one organization provides a service or services for another organization that chooses not to perform them in-house |
|
|
