information resources management january 23, 2001
TRANSCRIPT
Information Resources Information Resources ManagementManagement
January 23, 2001January 23, 2001
AgendaAgenda
AdministriviaAdministrivia Development MethodologiesDevelopment Methodologies People InvolvedPeople Involved Schema ArchitectureSchema Architecture CASE ToolsCASE Tools Homework #2Homework #2
AdministriviaAdministrivia
Homework #1Homework #1 Book?Book? Web PageWeb Page RegistrationRegistration
Development MethodologiesDevelopment Methodologies
Information EngineeringInformation Engineering Waterfall ModelWaterfall Model RAD ModelRAD Model
Phased (Incremental)Phased (Incremental) PrototypingPrototyping
SpiralSpiral CustomizationCustomization
Information EngineeringInformation Engineering
Data-orientedData-oriented Top-down approachTop-down approach
Broad understanding firstBroad understanding first Then, specific systems identifiedThen, specific systems identified
Information systems related to business Information systems related to business objectivesobjectives
Information Engineering StepsInformation Engineering Steps
PlanningPlanning AnalysisAnalysis DesignDesign ImplementationImplementation
Info. Eng. Planning PhaseInfo. Eng. Planning Phase
Identify strategic planning factorsIdentify strategic planning factors goals, CSFs, problemsgoals, CSFs, problems
Identify corporate planning objectivesIdentify corporate planning objectives units, locations, functions, typesunits, locations, functions, types
Develop enterprise modelDevelop enterprise model functions, data, relationshipsfunctions, data, relationships
Waterfall Model (SDLC)Waterfall Model (SDLC)
System Developmen LifecycleSystem Developmen Lifecycle Linear and sequentialLinear and sequential ““Classical”Classical” Specific, predefined phasesSpecific, predefined phases Definite end points for eachDefinite end points for each Historically, most widely usedHistorically, most widely used Template for other modelsTemplate for other models
Waterfall SDLCWaterfall SDLC
Single system developmentSingle system development Information Engineering or other Information Engineering or other
approach for overall strategic systems approach for overall strategic systems planningplanning
Waterfall ModelWaterfall Model
Time
Initiation Analysis
Logical Design
Physical Design Implement
Maintain
Identification
Database LifecycleDatabase Lifecycle
1. Enterprise Modeling1. Enterprise Modeling
2. Conceptual Data Modeling2. Conceptual Data Modeling
3. Logical Database Design3. Logical Database Design
4. Physical Database Design and Creation4. Physical Database Design and Creation
5. Database Implementation5. Database Implementation
6. Database Maintenance6. Database Maintenance
Waterfall ModelWaterfall Model
Time
Initiation Analysis
Logical Design
Physical Design Implement
Maintain
Identification
Enterprise Modeling
Conceptual Data Modeling
Logical Data Modeling
Physical Database Design and Creation
Database Implementation
Database Maintenance
Waterfall ProblemsWaterfall Problems
Projects aren’t so sequentialProjects aren’t so sequential Requirements finalized earlyRequirements finalized early Delay before system deliveredDelay before system delivered
All or nothingAll or nothing Sequential dependencies create delays Sequential dependencies create delays
forcing others to waitforcing others to wait
RAD ModelRAD Model
Rapid Application DevelopmentRapid Application Development Complete Development ApproachComplete Development Approach
““RAD/FAST” or “JAD” SessionRAD/FAST” or “JAD” Session ““Components”Components”
Fully functional and usefulFully functional and useful Completely specified, built and installed Completely specified, built and installed
in 60-90 daysin 60-90 days ConcurrentConcurrent
RAD ModelRAD Model
Business Modeling Data
Modeling
Process Modeling
Application Generation Testing &
Turnover
Business Modeling
Data Modeling
Process Modeling
Application Generation
Testing & Turnover
Business Modeling
Data Modeling
Process Modeling
Application Generation
Testing & Turnover
Team 1
Team 2
Team 3
Time
RAD DrawbacksRAD Drawbacks
System requires proper “components”System requires proper “components” Resources & skills for large number of Resources & skills for large number of
teamsteams High level of user involvement and High level of user involvement and
commitment requiredcommitment required System performance may sufferSystem performance may suffer Technical risks dramatically increase Technical risks dramatically increase
project risksproject risks
Phased (Incremental) ModelPhased (Incremental) Model
System is delivered in “increments”System is delivered in “increments” Initial increment is “core product”Initial increment is “core product” Increments larger than RAD system piecesIncrements larger than RAD system pieces Focus on specific increment - delay Focus on specific increment - delay
decisions on future incrementsdecisions on future increments System revised as development progressesSystem revised as development progresses SequentialSequential
Incremental ModelIncremental Model
Analysis Design Code Test
Analysis Design Code Test
Analysis Design Code Test Deliver #1
Deliver #2
Deliver #3
Incremental DrawbacksIncremental Drawbacks
System must have “increments”System must have “increments” Increments must be useful to usersIncrements must be useful to users Overall, longer (much longer) Overall, longer (much longer)
development timedevelopment time Business procedure changes with each Business procedure changes with each
increment deliveredincrement delivered
Prototyping ModelPrototyping Model Geared toward requirement collection, Geared toward requirement collection,
unfamiliar technology, complex interface designunfamiliar technology, complex interface design Prototype is a way of managing risk as much Prototype is a way of managing risk as much
as an exploration of new ideasas an exploration of new ideas
Listen to Customer
Build/ Revise
Customer Test Drive
PrototypingPrototyping
Prototype: software model of systemPrototype: software model of system
Closed-Ended - throwawayClosed-Ended - throwaway Open-Ended - evolutionaryOpen-Ended - evolutionary
Explorative - identify requirementsExplorative - identify requirements Experimental - try optionsExperimental - try options
““Entire” SystemEntire” System Key elements onlyKey elements only
Prototyping CyclePrototyping Cycle
Time between prototypesTime between prototypes Influences number of prototypesInfluences number of prototypes Shorter time between - more Shorter time between - more
prototypesprototypes More prototypes (generally) better More prototypes (generally) better
productproduct Company standard of fixed number of Company standard of fixed number of
prototypesprototypes
Candidates for PrototypingCandidates for Prototyping
Dynamic visual displaysDynamic visual displays Heavy user interactionHeavy user interaction Complex algorithms or calculationsComplex algorithms or calculations Ambiguous or conflicting requirementsAmbiguous or conflicting requirements
Prototyping ConsiderationsPrototyping Considerations User ResourcesUser Resources Decision MakersDecision Makers IS Resources - Tools, PeopleIS Resources - Tools, People User Understanding of PrototypeUser Understanding of Prototype
Time to completionTime to completion Full functionalityFull functionality Performance requirementsPerformance requirements Closed-endedClosed-ended
““Paper Prototype”Paper Prototype”
Spiral ModelSpiral Model Evolutionary software developmentEvolutionary software development Task RegionsTask Regions
Predefined tasks in eachPredefined tasks in each Multiple passesMultiple passes
Around the spiralAround the spiral Through each regionThrough each region Increasing complexity and level of detailIncreasing complexity and level of detail
Prototyping usually involvedPrototyping usually involved
Spiral ModelSpiral Model
Spiral DrawbacksSpiral Drawbacks
Unfamiliarity - newer modelUnfamiliarity - newer model Developer trainingDeveloper training User trainingUser training
High user involvementHigh user involvement When do spirals end?When do spirals end?
Management and control very importantManagement and control very important Risk assessment is criticalRisk assessment is critical
Expertise is neededExpertise is needed
Methodology CustomizationMethodology Customization
Fit the structure of the solution to the Fit the structure of the solution to the structure of the problemstructure of the problem Don’t use a hammer to drive in a screwDon’t use a hammer to drive in a screw
Customize based on system size or Customize based on system size or complexity, development risk, staff and tool complexity, development risk, staff and tool availability, user experience, controls required availability, user experience, controls required and system riskand system risk Customize a single approachCustomize a single approach Combine multiple approachesCombine multiple approaches
People InvolvedPeople Involved
Project managerProject manager Systems analysts & designersSystems analysts & designers Database analysts & designersDatabase analysts & designers UsersUsers ProgrammersProgrammers Database Administrators (DBAs)Database Administrators (DBAs) Networking expertsNetworking experts Other technical expertsOther technical experts
Project ManagerProject Manager
Assemble project teamAssemble project team Build detailed project plansBuild detailed project plans Monitor people and planMonitor people and plan Work with other managementWork with other management Ultimately held responsible for success Ultimately held responsible for success
of system development projectof system development project
System Analysts & DesignersSystem Analysts & Designers
Focus on business needsFocus on business needs ““Bridge” business and technologyBridge” business and technology System functions and dataSystem functions and data Analyst - “What should be done?”Analyst - “What should be done?” Designer - “How should it be done?”Designer - “How should it be done?”
Greater technology focusGreater technology focus
Database Analysts and Database Analysts and DesignersDesigners Focus on business needsFocus on business needs ““Bridge” business and technologyBridge” business and technology Primary focus on data requirementsPrimary focus on data requirements Analyst - “What data is needed?”Analyst - “What data is needed?” Designer - “How should it be stored?”Designer - “How should it be stored?”
UsersUsers
Ultimate users of new systemUltimate users of new system Provide requirements, business needsProvide requirements, business needs Review documentationReview documentation Test & accept new systemTest & accept new system Train other usersTrain other users May represent “actual” usersMay represent “actual” users
ProgrammersProgrammers
Design programs (detailed design)Design programs (detailed design) ““Write” programsWrite” programs Test programsTest programs Write SQL for database accessWrite SQL for database access
Database AdministratorsDatabase Administrators
Ultimately responsible for databasesUltimately responsible for databases current and futurecurrent and future
Provide data and modeling expertiseProvide data and modeling expertise Provide DBMS expertiseProvide DBMS expertise Monitor and tune databasesMonitor and tune databases
Other Technical ExpertsOther Technical Experts
Provide expertise in specified areasProvide expertise in specified areas networkingnetworking operating systemsoperating systems hardwarehardware development languagesdevelopment languages development methodologies and toolsdevelopment methodologies and tools
Database Schema ArchitectureDatabase Schema Architecture
Schema - view or model of a databaseSchema - view or model of a database Different views of same databaseDifferent views of same database Three kinds of schemasThree kinds of schemas
ConceptualConceptual ExternalExternal PhysicalPhysical
Conceptual SchemaConceptual Schema
Logical model of databaseLogical model of database Data modelData model Entity-Relationship DiagramEntity-Relationship Diagram
Independent of DBMSIndependent of DBMS Focus on data and relationshipsFocus on data and relationships
External SchemaExternal Schema
Also, User ViewAlso, User View Subset of conceptual schemaSubset of conceptual schema
data for specific taskdata for specific task specific usersspecific users specifc programsspecifc programs
Independent of DBMSIndependent of DBMS Entity-Relationship DiagramEntity-Relationship Diagram
Physical SchemaPhysical Schema
Description of how data will actually be Description of how data will actually be storedstored StructureStructure Data typesData types
Based on conceptual schemaBased on conceptual schema Specific process for conversionSpecific process for conversion
Tied to specific DBMSTied to specific DBMS
Schema RelationshipsSchema Relationships
Physical Schema
Conceptual Schema
External Schema 1
External Schema 2
External Schema n
Schema DevelopmentSchema Development
Physical Schema
Conceptual Schema
External Schemas
Enterprise Modeling
Conceptual Data Modeling
Logical Database Design
Physical Database Design
Database Implementation & Maintenance
CASE ToolsCASE Tools
Computer-Aided Software EngineeringComputer-Aided Software Engineering Computer-Automated?Computer-Automated?
FeaturesFeatures TypesTypes RepositoryRepository ToolsTools
CASE FeaturesCASE Features
DiagramsDiagrams DocumentationDocumentation Data DictionaryData Dictionary Team CoordinationTeam Coordination PrototypingPrototyping Code GenerationCode Generation Reverse EngineeringReverse Engineering
CASE TypesCASE Types
Full development - integratedFull development - integrated iCASEiCASE
Analysis & DesignAnalysis & Design upper CASEupper CASE
Implementation & MaintenanceImplementation & Maintenance lower CASElower CASE
CASE RepositoryCASE Repository
Data dictionary - data element definitions Data dictionary - data element definitions and descriptionsand descriptions Ensures consistencyEnsures consistency
Repository is much moreRepository is much more Database with linkages for all system Database with linkages for all system
development products and activitiesdevelopment products and activities IntegrationIntegration
Even across different CASE toolsEven across different CASE tools
CASE ToolsCASE Tools
Visio 2000 - MicrosoftVisio 2000 - Microsoft on laptopson laptops
Visible Analyst - Visible SystemsVisible Analyst - Visible Systems ER/Studio - EmbarcaderoER/Studio - Embarcadero ERWin - Computer AssociatesERWin - Computer Associates Oracle Designer - OracleOracle Designer - Oracle Power Designer - SybasePower Designer - Sybase
Homework #2Homework #2
Database JobsDatabase Jobs Search any source; find 5 jobsSearch any source; find 5 jobs Review requirementsReview requirements Find your job & reviewFind your job & review Table of resultsTable of results Analyze number and type of jobs and Analyze number and type of jobs and
the knowledge neededthe knowledge needed