Most Critical Software Development Processes (Fournier)Business requirements definitionSystem technical architectureDatabase design and constructionGUI/programs design and construction processTesting processData conversionDocumentationCreation of user and system manualsTrainingSystem Implementation and OptimizationPost implementationSupport, enhancementsEvaluate effort level for completing remainder of projectOther factors to considerMost Critical Software Development Processes (Fournier)Business requirements definitionProblems and opportunitiesBusiness data and process model (data and functional needs)Operational, security, performance, etc. requirementsSystem technical architectureInitial technical architectureHardware, software, network equipment and facilities, distributed computing, capacity planTechnology for backup and recovery, security.Middleware for integration of heterogeneous computing platformsDevelopment tools, computing environment for new systemDatabase design and constructionTransformation of business data model to logical database structures,refined to meet data access and performance needs.Transform to physical database structures, considering any data distribution and capacity plan requirementsGUI/programs design and construction processDefining the application user interface, with prototypeDesigning and constructing all online and batch programs required.Testing processVerifying that system meets functional reqts and operations, security and control reqts.Unit testing, integration testing, acceptance testing, etc.Data conversionConverting legacy system data, populating new databasesConversion requirements, plan for conversion activities, timetableDesign, create and test conversion programsDocumentationCreation of user and system manualsTrainingUser training, systems personnel to operate and support new systemDetermine training requirements for new application, develop training strategy, prepare training materialSystem Implementation and OptimizationMigrating new system to production, fine tuningInstallation strategyPost implementationSupport, enhancementsTailoring the methodology to unique project development needsOne size does not fit all.Two critical factors to considerSize, Complexity of proposed systemSizeLines of code, function points, person-months of effort, etc.Common factors influencing SizeFunctional scopeNumber of interfaces with other systemsNumber and types of usersNumber of data entities and attributesFactors influencing ComplexityComplexity of business processesComplexity of business rulesComplexity of relationships between data entitiesTransaction volumeDistribution (geographical) of usersType of technology and level of maturity of technology.As Size and Complexity increases, the number of development phases should augment accordinglyPartitioning development effort into a set of discrete development phases allows development team toBetter track progress in each phaseAssess whether project is on track when milestones are reachedEvaluate effort level for completing remainder of projectOther factors to considerDevelopment time allocated (Fig 1-6)Importance of the proposed system for organization’s survivalGreater the criticality, more phased approach, with insertion of more control pointsType of technology base to develop and run the systemBringing together different technologies increases risks(A) Accelerated system development approach for large projects5 major phasesSurveyDefine business objectives, project scope, constraints and risks,user requirementsAnalysisDetailed requirements for the business application.Business process and data modelTechnical architectureHigh-level testing, training and data conversion strategyWorking prototype of GUI developed and reviewed with usersDesignTransform application reqts to detailed system specifications, in line with architecture that will be used to run the systemBusiness data model to logical data structureBusiness process model to detailed and complete set of transactions,with appropriate GUIRefine testing, training and data conversion strategies, and specify detailed plans outlining activities to be performed for theseConstructionCode and test application programsCreate the test and production databasesImplementationSystem and data conversionTrainingSpecialized techniques to speed up the development process(Accelerator techniques)Joint facilitated sessionsPrototypingTimeboxingIterative developmentPartitioning large projects into smaller, more manageable subprojects (6-18 months)Use of component based, reusable application development architecture(B) Fast-paced system development approach for medium sized projectsLess formalism – 3 major phasesRequirementsQuickly define scope and requirements to a level of detail sufficient for developing the application in a short timeframeBest strategy for testing, training and conversionDesign and ConstructionQuickly develop and test the system solution that will satisfy application reqts documented in previous phaseImplementation and OptimizationTransfer new system to productionConvert legacy data, trainingFine tuning(C) Rapid evolutionary prototyping approach for small projectsEvolutionary application prototypingDirect construct the system solution with evolutionary prototypingPrototype gradually evolves into a fully functioning system through a pre-determined number of development iterationsEach iteration is executed a rigid timebox to control possibility of creeping functionality and to ensure that system is delivered in time.ImplementationTransfer to productionQuickly train users and system personnel(A) and (C): Capture user reqts with a modeling approach – focus on what the system should do rather than on how to(B):Evolving system prototype is used to determine system requirements asthe system is gradually being