PowerPoint PresentationGuiding principlesSoftware development - The ProcessAlternatively…Alternatively (2)…Slide 6Slide 7Slide 8Slide 9Slide 10Systems AnalysisSystem designSystem ImplementationCross Life Cycle ActivitiesSlide 15Slide 16Slide 17Software Engg. Paradigms ( Process models)Waterfall ModelSoftware Engineering paradigmsPrototyping: ProblemsSlide 22Rapid Application DevelopmentRADSlide 25O-O developmentSlide 27Slide 28Systems Development Process set of activities, methods, best practices and deliverables that are used to develop and maintain information systems.Process maturityas the development process matures, project costs decrease, timelines improve, productivity and quality increase.Software development - The ProcessGuiding principles•Get the Owners and Users Involved•Establish Phases and Activities•Establish Standards for Development and Documentation•Justify systems as Capital Investments•Don’t be afraid to Cancel or Revise Scope•Divide and Conquer•Design for Growth and ChangeSoftware development - The Process3 Generic Phases•Definition (What)–Customer contact•role of system, scope–Project Planning•risk analysis, resources, cost estimation, schedules–Requirement Analysis•Development (How)–Design–Coding–Testing•Maintenance–Correction of errors–Adaptation–Enhancements•Preliminary Investigation Phase –establishes the project context, scope, budget, staffing, and schedule.•Problem Analysis Phase –identifies and analyzes both the business and technical problem domains for specific problems, causes, and effects•Requirements Analysis Phase –identifies and analyzes business requirements that should apply to any possible technical solution to the problems.•Decision Analysis Phase –identifies and analyzes candidate technical solutions that might solve the problem and fulfill the business requirements. The result is a feasible, target solution.Alternatively…Alternatively (2)…•Purchasing Phase (optional) –identifies and analyzes hardware and software products that will be purchased as part of the target solution.•Design Phase –specifies the technical requirements for the target solution. Today, the design phase typically has significant overlap with the construction phase.•Construction Phase –builds and tests the actual solution (or interim prototypes of the solution).•Implementation Phase –puts the solution into daily production.•Operation and Support Phase –continues until the system is obsolete.•Preliminary Investigation–“Is this project worth looking at?”–Define the scope of the project, the perceived problems, opportunities, and directives that triggered the project. –Establish the project team and participants, the project budget, and the project schedule.•Problem Analysis–Gain an appropriate understanding of the business problem domain–Determine if the system is worth developing–Learning the system terminology, history, culture, and nuances of the organization (or department). –Address the causes and effects of the problems, opportunities, and directives.•Requirements Analysis–Identify the data, process, interface, and geographic requirements for the users of a new system. –Specify these requirements without expressing computer alternatives and technology details; at this point, keep analysis at the business level.–Prioritize - requirements can be classified as ‘mandatory’, ‘desirable’, or ‘optional’. •Decision Analysis–Define the candidate solutions–Evaluate each candidate for feasibility (next slide).–Recommend a feasible candidate as the target system. –Feasibility analysis•Purchasing–research the technology and marketplace–organize the business, technology, and relationship requirements, and establishes the mechanisms that will be used to evaluate the technical alternatives.–write the RFP. –receive proposals from vendors.–evaluate proposals.–make a recommendation to the system owners (and usually the information system managers as well).–execute the final orders, contracts, licenses, and service agreements.•Design–transform the business requirements from the definition phase into a set of technical design blueprints for construction.–addresses how specific technologies will be used in the new system.–design specs can include written documentation or prototypes–existing systems must be integrated in the design.•Construction–build and test a functional system that fulfills business and design requirements–implement the interfaces between the new system and existing systems–system testing – unit and system testing•Implementation–Install, deploy, and place the new system into operation or production. –User training, manuals, loading files and databases•Operations and System Support–ongoing maintenance of a system after it has been placed into operation. This includes program maintenance and system improvements.Systems Analysis–Organizational context and requirements (Enterprise Modeling)–Functional area context and requirements (Workflow diagrams)–Analyze existing System•Physical analysis•Logical analysis–New System requirement•Logical model of new system (Requirement specification)( Functional requirements - DFDs)–Documentation •Requirement specification Document•SystemEnvironmentSystem design–General design•Logical design of alternatives (broad sketches)•Evaluate and choose a solution approach–Detailed design (Physical design)•Process design - program specification (Program structure charts)•Data design - logical structure of data and files (E/R Models)•User interface design - Dialog and document flows–Design DocumentSystem Implementation– Coding– Testing– Installation– Manuals, User trainingCross Life Cycle Activities•Project Management–Schedules and cost, milestones•Software Quality Assurance–creation of Standards–ensure conformation to those standards•formal technical views•documentation of errors•testing strategyCross Life Cycle Activities•Measurement–Time, Effort, Costs, Productivity, Quality (Software Metrics)–enhanced estimates of new projects–baseline for process improvement–test effectiveness of new methodsCross Life Cycle Activities•Software Configuration Management–Controlled change•customers change requirements•developers change technical approach•management modifies project