Chater 17 Building Software to Support an Agile Organization
Order by
22 terms
Terms | Definitions |
|---|---|
 SYSTEMS DEVELOPMENT LIFE CYCLE | SDLC what does it stand for? |
| Systems development life cycle (SDLC) | - the overall process for developing information systems from planning and analysis through implementation and maintenance |
| Planning phase | SDLC - involves establishing a high-level plan of the intended project and determining project goals |
| Analysis phase | SDLC - involves analyzing end-user business requirements and refining project goals into defined functions and operations of the intended system |
| Business requirement | - detailed set of business requests that the system must meet in order to be successful |
| Design phase | SDLC - involves describing the desired features and operations of the system including screen layouts, business rules, process diagrams, pseudo code, and other documentation |
| Development phase | SDLC - involves taking all of the detailed design documents from the design phase and transforming them into the actual system |
| Testing phase | SDLC - involves bringing all the project pieces together into a special testing environment to test for errors, bugs, and interoperability and verify that the system meets all of the business requirements defined in the analysis phase |
| Implementation phase | SDLC - involves placing the system into production so users can begin to perform actual business operations with the system |
| Maintenance phase | SDLC - involves performing changes, corrections, additions, and upgrades to ensure the system continues to meet the business goals |
| methodology | Set of policies, procedures, standards, processes, practices, tools, techniques, and tasks that people apply to technical and management challenges |
| Waterfall methodology | - an activity-based process in which each phase in the SDLC is performed sequentially from planning through implementation and maintenance |
| Agile methodology | - aims for customer satisfaction through early and continuous delivery of components developed by an iterative process A(n) ........ project sets a minimum number of requirements and turns them into a deliverable product |
| Iterative development | - consists of a series of tiny projects |
| Rapid application development methodology (RAD) | - emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system to accelerate the systems development process The prototype is an essential part of the analysis phase when using a ............ methodology |
| Prototype | - a smaller-scale representation or working model of the users' requirements or a proposed design for an information system |
| Extreme programming (XP) methodology | - breaks a project into tiny phases, and developers cannot continue on to the next phase until the first phase is complete |
| SCRUM | - uses small teams to produce small pieces of deliverable software using sprints, or 30-day intervals, to achieve an appointed goal Under this methodology, each day ends or begins with a stand-up meeting to monitor and control the development effort |
| Agile Alliance | is a group of software developers whose mission is to improve software development processes |
| Scope creep | - occurs when the scope increases |
| Feature creep | - occurs when extra features are added |
| 65% 10% | ...% of agile projects are successful and ...% of waterfall projects are successful |
First Time Here?
Welcome to Quizlet, a fun, free place to study. Try these flashcards, find others to study, or make your own.