8 4. Implementation Construction System is built (or acquired)ZEIT2301 Design of ISWeek 01: Intro4. ImplementationConstructionSystem is built (or acquired)System testingInstallationImplement a training plan for the usersNew system becomes operationalOperation & MaintenanceEstablish a support planSession 2, 2010

11 1. PlanningManagement activities that permit the stages of the database system development lifecycle to be realised efficiently and effectivelyCreation of a mission statement and objectivesDevelopment of standards for data collection and format

12 2. AnalysisCollecting and analysing information about the organisation to be supported by the new database systemUsing this information to identify the requirements of the new databaseA preliminary part of database design

17 6. MaintenanceMonitoring and maintaining the database system following installation

18 Systems development: Some terminologyZEIT2301 Design of ISWeek 01: IntroSystems development: Some terminologyMethodology: A comprehensive approach to system development; typically includes activities, techniques, and toolsTechnique: a collection of guidelines that help an analyst complete an activity or taskTool: a specific device, usually software, which makes it easier to use a specific techniqueSession 2, 2010

19 System Development MethodologiesZEIT2301 Design of ISWeek 01: IntroSystem Development MethodologiesHistorically methodologies tended to be either process-centred or data-centred.More recently the object-oriented approach seeks to integrate both process and data in a single model.Large organizations may follow internal methodologies or formal standards.For a complex information system, a systematic approach is crucial.Well-known methodologies include:Waterfall developmentParallel developmentRapid application developmentAgile developmentSession 2, 2010

21 ZEIT2301 Design of ISWeek 01: Intro“Structured” DesignThe advent of “Structured” design introduced formal models:Typically used one set of models to describe process (eg Data Flow Diagrams) and a separate set of models to describe data (eg Entity-relationship Diagrams)Structured development methodology involved a formal step-by-step approachMost well known methodology is the Waterfall methodMoves from one phase to the next in sequenceMany variants; later variants allowed for iteration where necessarySession 2, 2010

25 Pros and Cons of Parallel developmentZEIT2301 Design of ISWeek 01: IntroPros and Cons of Parallel developmentProsConsDivides project into sub-projects that can be worked on in parallel thus allowingearlier delivery of the systemSubsystems might not be independent; could require significant integration effortSession 2, 2010

26 Rapid Application DevelopmentZEIT2301 Design of ISWeek 01: IntroRapid Application DevelopmentRapid Application Development (RAD)Concentrates on developing at least part of the system much earlierInvolving users for feedbackUse of tools to speed developmentSession 2, 2010

28 RAD based approaches Phased Development PrototypingZEIT2301 Design of ISWeek 01: IntroRAD based approachesPhased DevelopmentA series of versions; initial version meets key requirementsPrototypingSystem prototypingPrototype evolves to become the systemThrow-Away PrototypingDesign prototypingPrototype is used only to help determine requirementsSession 2, 2010

31 Rapid Application Development 3ZEIT2301 Design of ISWeek 01: IntroRapid Application Development 3Throwaway PrototypingThe prototype is only used to help elicit requirements and thus inform system design.Session 2, 2010

39 Project Team Roles Role Responsibilities Business AnalystZEIT2301 Design of ISWeek 01: IntroProject Team RolesRoleResponsibilitiesBusiness AnalystAnalyzing the key business aspects of the systemIdentifying how the system will provide business valueDesigning the new business processes and policiesSystems AnalystIdentifying how technology can improve business processesDesigning the new business processesDesigning the information systemEnsuring the system conforms to IS standardsInfrastructure AnalystEnsuring the system conforms to infrastructure standardsIdentifying infrastructure changes required by the systemChange Management AnalystDeveloping and executing a change management planDeveloping and executing a user training planProject ManagerManaging the teamDeveloping and monitoring the project planAssigning resourcesServing as the primary point of contact for the projectSession 2, 2010

40 ZEIT2301 Design of ISWeek 01: IntroSummaryThe SDLC consists of four stages: Planning, Analysis, Design, and ImplementationThe DBLC consists of six stages: Planning, Analysis, Design, DBMS Selection, Implementation, MaintenanceSystem development methodologies varyThe choice of an appropriate methodology depends on the characteristics of the system, the organisation and the available staff skill set.Session 2, 2010