Beruflich Dokumente
Kultur Dokumente
1. Project planning – initiate, ensure feasibility, plan Activities of Implementation Phase of SDLC
schedule, obtain approval for project
2. Analysis – understand business needs and - Construct software components
processing requirements - Verify and test
3. Design – define solution system based on - Convert data
requirements and analysis decisions - Train users and document the system
4. Implementation – construct, test, train users, and - Install the system
install new system
5. Support – keep system running and improve
1. Traditional approach
- Also called structured system development Object-Oriented Approach
- Structured analysis and design technique
(SADT) Completely different approach to information systems
- Includes information engineering (IE) Views information system as collection of interacting
2. Object-oriented approach objects that work together to accomplish tasks
- Also called OOA, OOD, and OOP o Objects – things in computer system that
- Views information system as collection of can respond to messages
interacting objects that work together to o Conceptually, no processes, programs,
accomplish tasks data entities, or files are defined – just
objects
Traditional Approach OO languages: Java, C++, C# .NET, VB .NET
Object-oriented analysis (OOA)
Structured programming o Defines types of objects users deal with
o Shows use cases are required to complete
- Improves computer program quality tasks
- Allows other programmers to easily read and Object-oriented design (OOD)
modify code o Defines object types needed to
- Each program module has one beginning and communicate with people and devices in
one ending system
- Three programming constructs (sequence, o Shows how objects interact to complete
decision, repetition) tasks
o Refines each type of object for
Top-Down Programming
implementation with specific language of
- Divides complex programs into hierarchy of environment
modules Object-oriented programming (OOP)
- The module at top controls execution by “calling” o Writing statements in programming
lower level modules language to define what each type of object
- Modular programming does
o Similar to top-down programming
Current trends in Development (Adaptive Approaches)
- One program calls other programs to work
together as single system 1. The Unified Process (UP)
Object-oriented development approach
Offered by IBM / Rational
Structured Design o Booch, Rumbaugh, Jacobson
Unified Modeling Language (UML) used primarily for
- Technique developed to provide design modeling
guidelines UML can be used with any OO methodology
o What set of programs should be UP defines four life cycle phases
o What program should accomplish o Inception, elaboration, construction,
o How programs should be organized into a transition
hierarchy Reinforces six best practices
- Modules are shown with structure chart o Develop iteratively
- Main principle of program modules o Define and manage system requirements
o Loosely coupled – module is independent o Use component architectures
of other modules o Create visual models
o Highly cohesive – module has one clear o Verify quality
task o Control changes
2. Extreme Programming (XP)
Recent, lightweight, development approach to keep
process simple and efficient
Structured Analysis
Describes system support needed and required 5. Models, techniques, and tools make up a system
system functionality through informal user stories development methodology
Has users describe acceptance tests to demonstrate 6. System development methodology provides guidelines
defined outcomes to complete every activity in the SDLC
Relies on continuous testing and integration, heavy 7. System development methodologies are based on
user involvement, programming done by small teams traditional approach or object-oriented approach
8. Current trends include: Extreme Programming (XP),
Unified Process (UP), Agile Modeling, and Scrum
9. CASE tools are designed to help analysts complete
system development tasks
3. Agile Modeling
Hybrid of XP and UP (Scott Ambler); has more models
than XP, fewer documents than UP
Interactive and Incremental Modeling
o Apply right models
o Create several models in parallel
o Model in small increments
Teamwork
o Get active stakeholder participation
o Encourage collective ownership
o Model with others and display models
publicly
Simplicity
o Use simple content
o Depict models simply
o Use simplest modeling tools
Validation
o Consider testability
o Prove model is right with code
4. Scrum
For highly adaptive project needs
Respond to situation as rapidly as possible
Scrum refers to rugby game
o Both are quick, agile, and self-organizing
Team retains control over project
Values individuals over processes
Chapter Highlights