| A | B |
|---|
| systems analyst | A key person analyzing the business, identifying opportunities for improvement, and designing information systems to implement these ideas. Their primary goal is to create VALUE for the company. |
| four phases of the SDLC | Planning, Analysis, Design, Implementation |
| activities performed during the planning stage of the SDLC | Project Initiation (System request to identify business value, feasibility analysis) Project Management (Develop work plan, staff the project, and control & direct the project |
| deliverable of the planning phase | project plan (Describes how the team will go about developing the system) |
| activities performed during the analysis phase of the SDLC | Analysis strategy, information gathering, process & data modeling |
| deliverable of the analysis phase | System Proposal (Describes what business requirements the new system should meet.) |
| activities performed during the Design phase of the SDLC | Design strategy first; then Architecture, interface, database and file, and program designs |
| deliverable of the Design phase | System Specification (includes Architecture, interface, database and file, and program designs)s a |
| activities performed during the Implementation phase of the SDLC | Construction, installation, training, and establishing a support plan |
| What is the deliverable for the implementation phase? | New System & Maintenance Plan |
| methodology | A formalized approach to implementing the SDLC |
| The three major methodologies | Structured development, Rapid Application Development (RAD), Agile Development |
| methods associated with structured development | Waterfall & Parallel |
| methods associated with RAD | Phased, System Prototyping & Throwaway Prototyping |
| methods associated with Agile Methodologies | Scrum & Extreme Programming (XP) |
| Scrum product backlog | Contains all of the feature requirements |
| Scrum product owner | Ensure that the right features make it into the product backlog to support the users/customers of the product |
| Scrum master | makes sure that the project is progressing smoothly and ensures that every team member has the tools they need to get the job done. Sets up meetings and monitors the work being done, and facilitates release planning. |
| Scrum release backlog | prioritized set of features taken from the product backlog with time estimates calculated in |
| Scrum sprint | range from 3-30 days, 4-12 in a given release. At the end of each sprint you should have a product feature. The shorter the release cycles, the shorter the sprints |
| scrum sprint backlog | release backlog split up into several of these |
| scrum burn down chart | provides a day-to-day measure of given work remaining in a spirt or release. We can compare actual velocity and planned date to gauge whether or not we are on schedule. |
| Scrum defect backlog | Should be separated from a feature backlog and even some sprints should focus solely on this backlog |
| Daily Scrum | Standing meeting, no wasted time, short meetings, not an essential aspect of scrum for a expert team |
| Phases of the unified process | inception, elaboration, construction, transition |
| Two types of workflows in the Unified process? | engineering and supporting |
