1. Information System IS: a set of related components working together in some environment to perform functions that achieve some objective.

2. Process Standard operating procedures Organizational policies InputOutput Customers Competitors Government Regulations Shippers

3. IS Functions –Input, Processing, Output, Storage, Controls IS Components –People, Procedures, Data, Software, Hardware Alternative: Object-oriented view of a system

4. Systems Development: the process System lifecycle: –development phase * –production phase Systems approach –divide and conquer conversion

5. System Analysis –study business problem domain, existing system –identify requirements –specify characteristics of new system System decomposition –by functions performed –in terms of objects Systems Development: the process

6. System Design –evaluate alternative solutions, design a chosen solution –design document: basis for implementation Systems Development: the process

7. Two system development approaches Functional Decomposition –identify major activities, break up into composite steps (structured analysis and design) –focus on verbs (what a system does) Objects that comprise the system and how they act and relate –object structure and behavior analysis –focus on nouns (objects performing functions)

8. SDLC System development methodology –activities to solve a problem A methodology uses certain techniques (used to model a system) Model –representation of real world –used in analyzing and communicating what we understand DATA MODELS, PROCESS MODELS, OBJECT MODELS, etc.

9. System development catalysts User demand problems in current system, need for enhancements, improved efficiency Technology push new technology as catalysts Strategic pull system to support new business strategies/ products to stay competitive

10. Projects of varying complexity Upto 1000 lines –trivial, single person, few days/week 1000-10,000 lines –simple, 3/4 progr/analyst, 6-12 months –often formal analysis and design not used, but could be - leads to more maintainable system 10,000-100,000 lines –difficult, 6-12 people, 2-3 years –formal analysis and design essential –requirements/users change over time 100,000 - 1 million lines –complex. 50-100 people, 3-5 years –diverse community of users 1-10 million lines –nearly impossible > 10 million –absurd??

11. Why do IS projects fail? Did not support business strategy & objectives poor planning, project management failure to understand user requirements –user involvement in system development inadequate cost vs. benefit analysis –escalating costs, intangible benefits myriad of design defects/ errors installation of incompatible or inadequate technology no adequate controls implemented unstructured, un-maintainable software

12. Successful systems development Informal, sloppy art structured, engineered and managed approach (SDLC) stress user involvement in system development system planning and project management evaluate alternate designs before committing clean, complete and up-to-date documentation design for growth and change

13. Bugs! software errors cost U.S. users $59.5 billion each year. (National Institute of Standards and Technology (NIST) –just the cost of routine work-arounds and corrections by users, along with the added cost of buggy software that had to be fixed late in the development process. The real cost of bugs is much higher. –$22.2 billion of that $59.5 billion, or 37%, could be saved through "feasible improvements" in software testing. –“We indulge ourselves with the idea that all software has bugs, so trying harder to get rid of them is pointless perfectionism. Intellectually we should know better” !

14. Software: the product Software: a strategic business issue, not just a low-level support activity Can software be “manufactured” like physical products? (software “factories”) –Costs are concentrated on engineering (design) and support –“mythical man-month” Adding people to a project that is late will only worsen the situation. Why? Efficiency through re-use

15. Time Failure Rate Hardware Software Infant mortality Wear out Ideal Changes Failure Curves Actual

16. The Systems Analyst Roles –as a CONSULTANT (external) provide a fresh perspective disadvantage: organizational culture may not be known –as a SUPPORTING EXPERT –as a CATALYST FOR CHANGE interact with management excellent with people and machines analyze need for change, design change with consensus, implement change

17. The Systems Analyst Qualities –problem solver good analysis skills tools and techniques for analysis –communicator –computer skills –knowledge of business processes –self-disciplined and self-motivated

18. Systems Development Process set of activities, methods, best practices and deliverables that are used to develop and maintain information systems. Process maturity as the development process matures, project costs decrease, timelines improve, productivity and quality increase. Software development - The Process

19. Guiding 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 Change

20. Software development - The Process 3 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

21. 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…

22. 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.

23. 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.

24. 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

25. 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.

26. 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

27. Implementation –I nstall, 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.

28. 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 System Environment

29. System 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 Document

30. System Implementation – Coding – Testing – Installation – Manuals, User training

31. Cross 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 strategy

32. Cross Life Cycle Activities Measurement –Time, Effort, Costs, Productivity, Quality (Software Metrics) –enhanced estimates of new projects –baseline for process improvement –test effectiveness of new methods

33. Cross Life Cycle Activities Software Configuration Management –Controlled change customers change requirements developers change technical approach management modifies project approach –Software configuration Programs Documents Data structures Documentation Fact Finding

34. Effort Distribution Development : Maintenance 40:60, 30:70 Development Costs (Typical) Requirement : 10% Design: 20% Coding: 20% Testing: 50% (often under-estimated. Can be reduced through better design andcoding) [Note: easy to test easy to maintain]

35. Software Engg. Paradigms ( Process models) Waterfall model (Classical life Cycle) Planning Reqt.Analysis Design Code Test Install Maintenance Feasibility Report Requirements Specification Report Design Document Programs Test Report Installation Report

36. Waterfall Model old way of doing things All projects go through these phases But… Sequential progress unrealistic, iterations expensive Frozen requirements difficult to state all requirements at the beginning requirements drift gap between users and designers, little communication with users working system unavailable till late in the project –also disastrous for errors at this stage

37. Reqt.Generation and refinement Quick Design Customer Evaluation of prototype Refine PrototypeEngineer Product Build Prototype Software Engineering paradigms Prototyping -a modeling paradigm Discard prototype Engineer prototype to production system

38. Prototyping: Problems Customer impatient when prototype is rebuilt to production system –Inefficient system often becomes the production system system (NOTE: Ideally prototyping is the mechanism for identifying requirements) –high risk innovation applications –promote send user participation –good candidates for prototyping: –user unable to specify requirements. –Do not know what they want/what they want is not what they need –“I do not know what I want, but I will when I see it”

39. Software Engineering paradigms The RAD model (Rapid Application Development) –linear sequential development,emphasizes very short development cycle –component based construction –well-understood requirement, constrained scope –use of fourth generation techniques (4GLs)

40. Rapid Application Development Business Modeling Data Modeling Process Modeling Application Generation Testing and Turnover 60 -100 days Team 1Team 2Team 3

41. RAD 4GLs : –Enable developers to specify s/w characteristics at higher level of abstraction. Tool automatically generates source code. Tools: –non-procedural languages for DB query,report generation,data manipulation,screen interaction, graphics,etc –reduces development time for smaller applications –user and developer commitment to rapid-fire activities –inefficient code? Use where high performance is required? –Use of reusable program components

42. OOD Customer prototype OOA Browse library of reusable components Customer Evaluation Design/Implementation Component Library Component Specification Component Design Library entry Coding Testing Software Engineering paradigms O-O Systems Development: reuse paradigm

43. O-O development –Focus on reuse Object Class library –Focus on interoperability –Faster development,easier maintenance,platform independence

44. Risk analysis based on initial requirementsPlanning Risk analysis Customer evaluation Engineering Risk analysis based on customer reaction Go, no-go decision Toward a completed system Initial software prototype Next prototype level Engineered system Customer evaluation Planning based on customer comments Initial requirements gathering and project planning Spiral Model