Académique Documents
Professionnel Documents
Culture Documents
Lecture Outline
Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models Selecting the appropriate model Methodologies of the SDLC Traditional Approach to SDLC Information Engineering Approach to SDLC Object-Oriented Approach to SDLC Rapid Application Development Current trends in the SDLC CASE Tools
Phases in SDLC
Project planning initiate, ensure feasibility, plan schedule, obtain approval for project Analysis understand business needs and processing requirements Design define solution system based on requirements and analysis decisions Implementation construct, test, train users, and install new system Support keep system running and improve
5
SDLC Activities of each phase are similar Phases are not always sequential Phases can overlap Activities across phases can be done within an iteration
Define business problem and scope Produce detailed project schedule Confirm project feasibility
Economic, organizational, technical, resource, and schedule
Analysis Activities
Gather information to learn problem domain Define system requirements Build prototypes for discovery of requirements Prioritize requirements Generate and evaluate alternatives Review recommendations with management
10
Design Activities
Design and integrate the network Design the application architecture Design the user interfaces Design the system interfaces Design and integrate the database Prototype for design details Design and integrate system controls
11
Implementation Activities
Construct Verify
software components
Convert Train
Install
Enhance system
Small upgrades or enhancements to expand system capabilities Larger enhancements may require separate development project
Support users
Help desk and/or support team
13
15
Waterfall Approach
Each life cycle phase is completed in sequence and then the results of the phase flow on to the next phase There is no going back once the phase is completed (like a waterfall) or it is extremely difficult to do The key deliverables for each phase are typically produced on paper (hundreds of pages in length) The decisions made at each phase are frozen, i.e. they cannot be changed frozen
16
Identifying system requirements long before programming begins It minimizes changes to the requirements as the project proceeds
The design must be completely specified on paper before programming begins A long time elapses between the completion of the system proposal in the analysis phase
and the delivery of the system (usually many months or years). A paper document is often a poor communication mechanism, so important requirements can be overlooked in the hundreds of pages of documentation Users rarely are prepared for their introduction to the new system, which occurs long after the initial idea for the system was introduced. If the project team misses important requirements, expensive post-implementation programming may be needed. A system may require significant rework because of changes in business environment since the time the analysis phase occurred. It means going back to the initial phases and following the changes through each of the subsequent phases in turn.
17
The Parallel Model attempts to address the problem of long delays between the analysis phase and the delivery of the system. Instead of doing the design and implementation in sequence, it performs a general design for the whole system and then divides the project into series of distinct subprojects that can be designed and implemented in parallel Once all subprojects are complete, the final integration of the separate pieces is delivered
18
19
Overlap of activities
21
Spiral Model
Breaks each project into smaller pieces, each with a different type of risk (Sources of risk: undefined requirements, complex technology, uncertain competitive environment) The project begins in the center of the spiral where project is still small, easy to manage and low in risk Then the project slowly expands The project starts out small, initially handling a few of the risks Then the project expands in next iteration to address more of the risks Eventually the system is completed (all risks addressed)
23
24
26
Breaks the overall system into a series of versions that are developed sequentially The analysis phase identifies the overall system concept. The project team, users and system sponsors categorize the requirements into a series of versions The most important and fundamental requirements are bundled into the first version of the system. The analysis phase then leads into design and implementation, but only with the set of requirements identified for version 1 Once version 1 is implemented, work begins on version 2. Additional analysis is performed on the basis of the previously identified requirements and combined with new ideas and issues that arose from users experience with version 1. Version 2 then is designed and implemented, and work immediately begins on the next version. This process continues until the system is complete
27
Phased Model
28
Advantages: Quickly getting a useful system into the hands of users. Although it does not perform all the functions the users need, it helps them sooner to identify important additional requirements Disadvantages: The users begin to work with systems that are incomplete. It is critical to identify the most important and useful features and include them in the first version.
29
30
Prototyping model
Performs analysis, design and implementation phases concurrently, and all three phases are performed repeatedly in a cycle until the system is completed. The basics of analysis and design are performed, and work immediately begins on a system prototype (i.e., a quick-and-dirty program that provides a minimal amount of features The first prototype is shown to the users and the project sponsor, who provide comments, which are used to re-analyze, re-design, and re-implement a second prototype that provides a few more features This process continues in a cycle until the analysts, users and sponsor agree that the prototype provides enough functionality to be installed and used. Refinement occurs until it is accepted as the new system.
31
Prototyping SDLC
32
Throwaway Prototyping
Similar to the prototyping model in that it includes the development of prototypes, however, they are done at a different point in the SDLC Has a relatively thorough analysis phase that is used to gather information and to develop ideas for the system concept. Many of the features suggested by the users may not be well understood and many technical issues may not be solved. Each of these issues are examined by analyzing, designing and building a design prototype (it is not a working system; it only represents a part of the system that needs additional refinement and it contains only enough details to enable users to understand the issues under consideration) Typically, several prototypes are used during analysis and design phase. Each of them is used to minimize the risk of missing of important issues before the real system is built. Once the issues are resolved, the project moves into design and implementation. At this point, the design prototypes are thrown away, what is a principal difference between this model and prototyping, in which the prototypes evolve into the final system
34
35
37
39
Methodologies
Methodologies
Comprehensive guidelines to follow for completing every SDLC activity Collection of models, tools, and techniques
40
41
Models
Models
Representation of an important aspect of real world, but not same as real thing Abstraction used to separate out aspect physical (like a model of an airplane) abstract (e.g. in form of mathematical notation or in graphical form) Models in SDLC are graphical: diagrams and charts Project planning and budgeting aids
42
43
Tools
Tools
Software support that helps create models or other required project components Range from simple drawing programs to complex CASE tools to project management software
44
45
Techniques
Techniques
Collection of guidelines that help analysts complete a system development activity or task Can be step-by-step instructions or just general advice
46
47
Traditional approach
Also called structured system development Structured analysis and design technique ( (SADT) I Includes information engineering (IE)
Object-oriented approach
Also called OOA, OOD, and OOP Views information system as collection of interacting objects that work together to accomplish tasks
48
Structured Analysis
Define what system needs to do (processing r requirements) Define data system needs to store and use ( (data requirements) Define inputs and outputs Define how functions work together to accomplish tasks Data flow diagrams (DFD) and entity relationship diagrams (ERD) show results of structured analysis
49
50
51
52
Structured Design
What set of programs should be What program should accomplish How programs should be organized into a hierarchy
Modules are shown with structure chart Main principle of program modules
Loosely coupled module is independent of other modules 53 Highly cohesive module has one clear task
54
Structured programming
Improves computer program quality Allows other programmers to easily read and modify code Each program module has one beginning and one ending Three programming constructs (sequence, decision, repetition) d
55
56
Top-Down Programming
Divides complex programs into hierarchy of modules The module at top controls execution by calling lower level modules Modular programming
Similar to top-down programming
57
58
Focus on strategic planning to identify all the organization information needs (the application architecture plan), data modeling, and automated tools More focused on data itself than the structured approach. But just as the structural approach includes data requirements, IE includes processes, too The processing model of information engineering, the process dependency diagram, is similar to a data flow diagram, but it focuses more on which processes are dependent on other processes and less on data inputs and outputs Provides more complete life cycle support through the use of an integrated CASE tools (help to automate systems development; final program code can be generated automatically by the CASE tools) Became popular on large-mainframe systems in the 1980s, less used in the 1990s on smaller desktop systems (but concepts still used by planning and emphasis on data modeling) 60
Both approaches define information system requirements, design and construct information systems by looking at processes, data and the interaction of these two Industry merged key concepts from structured development and information engineering approaches into traditional approach An object-oriented technology provides a completely different perspective
61
Object-Oriented Approach
Completely different approach to information systems Views information system as collection of interacting objects that work together to accomplish tasks Objects things in computer system that can respond to messages Conceptually, no processes, programs, data entities, or files are defined just objects OO languages: Java, C++, C#, .NET, VB
62
63
65
SDLC Variations
Many variations of SDLC in practice
Based on variation of names for phases No matter which one, activities/tasks are similar
Rapid application development (RAD) is one of the variations of SDLC Aims to speed up the development process. Emerged in the 1990s as an attempt to address both weaknesses of the waterfall development: long development times and the difficulty in understanding a system from paperbased description.
Methods: Tries to speed up the activities in each phase (e.g. speeding the analysis phase by scheduling intensive meetings of key participants to get information gathered and decisions made rapidly) Using iterative development (e.g., spiral life cycle model) to speed up the process of getting to design and implementation Building prototypes of the system during analysis and design phases. It improves understanding of the system requirements Using CASE (computer-aided system engineering) tools to speed up the analysis, design and implementation phases 67
68
Unified Modeling Language (UML) used primarily for modeling UML can be used with any OO methodology UP defines four life cycle phases
Inception, elaboration, construction, transition
Defines workflows within each phase: business modeling, requirements modeling, analysis and design, implementation, testing, development, configuration and change management, and project management Involves roles of: designer, use case specifier, systems analyst, implementer, architect
69
70
72
Scrum
For highly adaptive project needs Respond to situation as rapidly as possible Scrum refers to rugby game
Both are quick, agile, and self-organizing
CASE tools are software tools designed to help systems analyst complete development tasks The CASE tool contains a database of information called a repository The repository stores information about the system, including models, descriptions, and references that link the various model together Information stored in repository can be used in a variety of ways by the development team Every time a team member adds information about the system, it is immediately available for everyone else CASE tools can check the models to make sure they are complete and follow the correct diagramming rules CASE tools can check one model against another to make sure they are consistent
74
75
77
a tool set for recording definitions and automating the rapid constructions of flexible, graphical clientserver applications integrated with Oracle Developer (a tool for creating GUI applications) includes a complete repository, diagramming and code-generating capabilities an integrated CASE tool that supports traditional approach to system development (process modeler, function-hierarchy diagrammer, data flow diagrammer, entity-relationship diagrammer) Design Transformer and Design Editor produce diagrams along with the database and application 78 logic
79
80
CASE Tools: Examples (contd) TogetherSoft The most recent concept of round-trip engineering allows synchronizing the graphical models (such as class diagram) with generated program code (automation in both directions round trip). If the program code is changed, the class diagram is updated and contra versa, if the class diagram is changed, the program code is updated. Together uses UML diagrams with several 81 different programming languages
82
CASE Tools: Examples (contd) Embarcadero Describe a new product that include modeling and round-trip engineering features provides flexible UML modeling capabilities for analysis and design provides round-trip engineering with several Java development tools (JBuilder and Sum Forte)
83
84
Readings
Todays lecture: Chapter 2 Approaches to System Development
!!! ou For next lecture: Chapter 3 The Analyst as a ky Project Manager an Th
85