Unit 2 Flashcards
There are two general approaches to the SDLC
Predictive Approach to the SDLC
Adaptive Approach to the SDLC
Predictive Approach to the SDLC
Waterfall model
Assumes the project can be planned in advance and that the information system can be developed according to the plan
Requirements are well understood and/or low technical risk
Adaptive Approach to the SDLC
Iterative model
Assumes the project must be more flexible and adapt to changing needs as the project progresses
Requirements and needs are uncertain and/or high technical risk
Traditional Predictive SDLC
Earlier approach based on engineering
Typically have sequential Phases
Phases are related groups of development activities, such as planning, analysis, design, implementation, and deployment
Waterfall model
SDLC that assumes phases can be completed sequentially with no overlap or iterationOnce one phase is completed, you fall over the waterfall to the next phase, no going backDeliverable Driven
Phase I: Project Initiation
During project initiation, the system’s business value to the organization is identified (How will it lower costs or increase revenues?).
This phase is the fundamental process of understanding why an information system should be built
Feasibility Analysis is performed at this stage
Technical Feasibility
Economic Feasibility
Organizational Feasibility
Key Deliverable: Problem Statement or Systems Proposal
Phase II: Project Planning
The Planning phase will also determine how the project team will go about building the information system.
The Planning phase is composed of the following steps. Developing a Timeline Developing a Budget Developing Success Criteria Developing Process Standards
Key Deliverable: Project Plan
Phase III: Analysis
The analysis phase answers the questions of who will use the system, what the system will do, and where and when it will be used.
During this phase the project team investigates any current system(s), identifies improvement opportunities, and develops a concept for the new system
Key Deliverable: Functional Specification Document
Phase IV: Design
In this phases it is decided how the system will operate, in terms of the hardware, software, and network infrastructure; the user interface, forms, and reports that will be used; and the specific programs, databases, and files that will be needed.
Phase IV: Design Cont (Steps and Deliverable?)
Design steps
- Design Strategy: This clarifies whether the system will be developed by the company or outside the company.
- Architecture Design: This describes the hardware, software, and network infrastructure that will be used.
- Database and File Specifications: These documents define what and where the data will be stored.
- Program Design: Defines what programs need to be written and what they will do.
Key Deliverable: Technical Design or Specification Document
Phase V: Implementation
During this phase, the system is either developed or purchased (in the case of packaged software).
This phase is usually the longest and most expensive part of the process.
The phase has the following steps.
System Construction: The system is built and tested to make sure it performs as designed
Key Deliverable: The Concrete System
Phase V: Deployment
During this phase, the system is deployed .
The performance is evaluated and fine tuned
Key Deliverable: Stable System
Adaptive Approaches
Incremental development
Completes portions of the system in small increments and integrated as the project progresses
Sometimes considered “growing” a system
Walking Skeleton
The complete system structure is built first, but with bare-bones functionality
Examples include Prototyping, Rapid Application Development, Agile Development etc.
Agile Development
A guiding philosophy and set of guidelines for developing information systems in an unknown, rapidly changing environment
Chaordic
A term for adaptive projects –chaotic yet ordered
Agile Development (Continued)
Agile Values in “Manifesto for Agile Software Development”
Value responding to change over following a plan
Value individuals and interactions over processes and tools
Value working software over comprehensive documentation
Value customer collaboration over contract negotiation
SCRUM
Combination of principles of Rugby and Agile
Intense effort involving the entire team for a defined period of time
Product backlog
Prioritized list of user requirements
Product owner
The client stakeholder who controls backlogScrum master
Scrum project manager
Scrum Sprint
Scrum sprint
A time-controlled mini-project to implement part of the system
Scrum Practices
Scope of each sprint is frozen (but can be reduced if necessary)
Time period is kept constant
Daily Scrum meeting
What have you done since the last daily Scrum (during the last 24 hours)?
What will you do by the next daily Scrum?
What kept you or is keeping you from completing your work?
Methodologies
Methodologies
Provides guidelines for every facet of system development: What to do when, why and how
Specifies an SDLC with activities and tasks
Specifies project planning and project management models and reporting
Specifies analysis and design models to create
Specifies implementation and testing techniques
Specifies deployment and support techniques
Methodologies
A Methodology includes a collection of techniques that are used to complete activities and tasks, including modeling, for every aspect of the project
Models
Model
An abstraction of an important aspect of the real world.
Makes it possible to understand a complex concept by focusing only on a relevant part
Each model shows a different aspect of the concept
Crucial for communicating project information
In IS, some models are of system components that will be developed
Other models are used to manage the development process
Some models of system components
Use Case diagram Domain model class diagram Design class diagram Sequence diagram Package diagram Screen design template Dialog design storyboard Entity-relationship diagram Database schema
Some models used to manage the development process
Gantt Chart Organization hierarchy chart Financial analysis models- NPV, payback period System development life-cycle model Stakeholders list Iteration plan
Tools
Tools
Software applications that assists developers in creating models or other components required for a project
Integrated Development Environment (IDE)
set of tools that work together to provide a comprehensive development environment
Visual ModelingTools
Tools to create graphical models
Some typical tools
Project management application Drawing/graphics application Word processor/text editor Visual modeling tool IDE Database management application Reverse-engineering tool Code generator tool
Techniques
Technique
A collection of guidelines that help an analyst complete an activity or task
Learning techniques is the key to having expertise in a field
Strategic planning techniques Project management techniques User-interviewing techniques Dat-modeling techniques Relational database design techniques Structured programming techniques Software-testing techniques Process modeling techniques Domain modeling techniques User case modeling techniques Object-oriented programming techniques Architectural design techniques User-interface design techniques
