22 terms

Chapter 10-Systems Devlopment

Waterfall Methodology
a sequential, activity-based process in which each phase in the systems development life cycle is performed sequentially from planning through implementation and maintenance
(RAD) Rapid Application Development
emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system to accelerate the systems development process
smaller-scale representation or working model of the users' requirements or a proposed design for an info 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
Agile Methodology
a form of XP, aims for customer satisfaction through early and continuous delivery of useful software components.
Agile Methodology Primary Principles
1. Slash the Budget 2. If it doesn't work, Kill it 3. Keep Requirements to a Minimum 4. Test and Deliver Frequently 5. Assign Non-IT Execs to Software Projects
Participatory Design (PD) Methodology
promotes the active involvement of users in the info systems development process.
Project MGMT
is the application of knowledge, skills, tools, and techniques to project activities in order to meet or exceed stakeholder needs and expectations from a project
Project Deliverables
any measurable, tangible, verifiable outcome, result or item that is produced to complete a project or part of a project
Project Milestones
represent key dates in a project
Project Manager
individual who is an expert in project planning and mgmt, defines and develops the project plan and tracks the plan to ensure all key project milestones are completed on time.
Project Scope
defines teh work that must be completed to deliver a product with specified features and functions
Components of Project Scope
1. Project product 2. Project objectives 3. Project deliverables 4. Project exclusions
(SDLC) Systems Development Life Cycle
is the overall process for developing info systmes from planning and analysis through implementation and maintenance
1. Planning 2. Analysis 3. Design 4. Development 5. Testing 6. Implementation 7. Maintenance
involves establishing a high-level plan of the intended project and determining project goals. 3 primary activities - 1. Identify and select the system for development 2. Assess project feasibility 3. Develop the project plan
involves analyzing end-user business requirements and refining project goals into defined functions and operations of the intended system 3 Primary activities - 1. Gather business requirements 2. Create process diagrams 3. Perform a buy versus build analysis
involves describing the desired features and operations of the system including screen layouts, business rules, process diagrams, pseudo code and other documentation. 2 primary - 1. Design IT infrastructure 2. Design system models
involves taking all of the detailed design documents from the design phase and transforming them into the actual system. 1. Develop IT infrastructure 2. Develop database and programs
involves bringing all the project pieces together into a special testing environment to test for errors, bugs and interoperability, in order to verify that the system meets all the business requirements defined in the analysis phase. 2 Primary activities - 1. write the test conditions 2. perform system testing
involves placing the system into production so users can begin to perform actual business operations with the system. 3 primary activities - 1. Write detailed user documentation 2. Determine implementation method 3. Provide training for the system users
involves performing changes, correntions, additiona dn upgrades to ensure the system continues to meet the business cgoals. 3 Primary activites - 1. Build a help desk to support the system users 2. Perform system maintenance 3. Provide an environment to support system changes