【正文】 path. – Gantt Charts –Show if project is behind, ahead, or on schedule. – Program Evaluation Review Technique (PERT) – Milestones with timebased estimates. – Timebox Management 18 Project Management Practices ?General Project Management – Documentation – Office Automation ?Project Controlling – Scope – Resource – Risk ?Closing A Project 19 Business Application Development 20 Business Application Development ? An Individual Application or Project is Initiated by – A new opportunity that relates to new or existing business process – A problem that relates to an existing business process – A new opportunity that will enable the organization to take advantage of technology – A problem with the current technology 21 ? Traditional SDLC Approach (Waterfall Method) – Phase 1—Feasibility – Phase 2—Requirements – Phase 3A—Design – Phase 3B—Selection – Phase 4A—Development – Phase 4B—Configuration – Phase 5—Implementation – Phase 6 – Post implementation Business Application Development 22 ?Advantages – This approach works best when a project’s requirements are likely to be stable and well defined. – This approach facilitates the determination of a system architecture relatively early in the development effort. – This approach provides a template into which methods for the requirements can be placed. ?Disadvantages – Unanticipated Events – Difficult to obtain explicit set of requirements – Managing requirements – Customer/user impatience – Changing environment can alter requirements prior to delivery Business Application Development 23 ?Integrated Resource Management Systems – Fully integrated corporate solution – SAP, Peoplesoft, Oracle Financials, etc. – Impact on way the corporation does business – Need to conduct an impact and risk assessment Business Application Development 24 ? Description of traditional SDLC phases – Feasibility Study ? Define a time frame for implementation ? Determine an optimum alternative/solution in meeting business needs and general information resource requirements or estimates ? Determine if an existing system can correct the situation with slight or no modification ? Determine if a vendor product offers a solution (develop or acquire) ? Determine the approximate cost ? Determine if the solution fits the business strategy Business Application Development 25 ? Description of traditional SDLC phases – Requirements Definition ? Determine stakeholders’ expectations ? Analyze requirements to detect/correct conflicts and determine priorities ? Identify system bounds/how system should interact with its environment ? Convert user requirements into system requirements . ? Record requirements in a structured format ? Verify that requirements are plete, consistent, unambiguous, verifiable, modifiable, testable and traceable ? Resolve conflicts between stakeholders ? Resolve conflicts between the requirements set and the resources that are available Business Application Development 26 ? Description of traditional SDLC phases – Entity Relationship Diagrams (ERD) ? An ERD depicts a system’s data and how these data interrelate. ? Use of ERD – An ERD can be used as a requirements analysis tool to obtain an understanding of the data a system needs to be capture and manage. [logical data model] – An ERD can also be used in the development cycle, as a design tool that helps document the actual database schema that will be implemented. [physical data model] – Not suitable for OO development aporach ? Relationship depicting – Primary key – Foreign key Business Application Development 27 ?Description of traditional SDLC phases – Software Acquisition ? Decision made to acquire rather than develop, the feasibility study should contain documentation that supports the decisoon. ? Request for Information (RFI) ? Request for proposal (RFP)/Invitation To Tender (ITT) ? Multiple vendors (shortlist) ? Agendabased presentation (scenario) ?select one (finalist) ?site visit ? conference room pilot Business Application Development 28 ?Description of traditional SDLC phases – Software Acquisition (cont.) ? Topics of discussion with users about vendors: – Reliability – Commitment to Service – Commitment to providing training and documentation ? Contract contents ? Contract management Business Application Development 29 ?Description of traditional SDLC phases – Design ? Limited user Involvement in the design ? Software baseline ? End of design phase ? IS auditor involvement – Controls – Continuous online auditing functions – Effectiveness Business Application Development 30 ?Description of traditional SDLC phases – Development ? Programming methods and techniques – Program coding standard – Traditional structured programming techniques (Topdown) – Cohesion – single, dedicated function – Coupling – dependence ? Online programming facilities (Integrated Development Environment IDE) – Allows faster program development and application of standards and structured programming techniques – Improve the programmer’s problemsolving abilities – Access control software should be used to prevent unauthorized access Business Application Development 31 ? Description of traditional SDLC phases – Development ? Programming languages – Highlevel (COBOL, C) – Objectoriented (C++, JAVA) – Scripting [such as SH(SHELL), PERL, TCL, Python, JAVAScript and VB Script] – Lowlevel assembler – Fourth generation (generally DB’s) – Decision support or expert systems ? Program debugging – Logic path monitors – Memory dumps – Output analyzers Business Application Development 32 ?Description of traditional SDLC phases – Development (cont.) ?Testing ?Elements of a software