System Analysis and Design
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

System Analysis and Design

on

  • 25,320 views

discuss about System system analysis, system design, system analyst's role, Development of System through analysis, SDLC, Case Tools of SAD, Implementation, etc.

discuss about System system analysis, system design, system analyst's role, Development of System through analysis, SDLC, Case Tools of SAD, Implementation, etc.

Statistics

Views

Total Views
25,320
Views on SlideShare
25,313
Embed Views
7

Actions

Likes
16
Downloads
992
Comments
6

3 Embeds 7

http://ribams.bugs3.com 5
https://twitter.com 1
https://www.facebook.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

15 of 6 Post a comment

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Dictionary of Computer and Information Technology / S. K. Bansal.- New Delhi: A. P. H. Publishing, 2009.
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  •  Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011. Systems Analysis and Design / Alan Dennis, Berbara Haley Wixom and Roberta M. Roth.-4thth.- New Jersey: John Wiley & Sons, 2010.
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  •  Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011 http://wiki.answers.com/Q/What_is_boundary_spanning_roles_or_boundary_extension_in_management
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011 http://en.wikipedia.org/wiki/Agile_software_development http://en.wikipedia.org/wiki/Prototype http://en.wikipedia.org/wiki/project_champion http://en.wikipedia.org/wiki/Soft_Systems_Methodology http://en.wikipedia.org/w/index.php?search=multiview&title=Special%3ASearch
  • Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011Systems Analysis and Design / Alan Dennis, Berbara Haley Wixom and Roberta M. Roth.-4thth.- New Jersey: John Wiley & Sons, 2010.Dictionary of Computer and Information Technology / S. K. Bansal.- New Delhi: A. P. H. Publishing, 2009.

System Analysis and Design Presentation Transcript

  • 1. System Analysis and Design Prepared By: Syed Aamir Abbas Muhammad Safdar MPhil Student (Semester-I) 2012-14 Minhaj University Lahore.
  • 2. Objectives Define the terms system, system analysis, and system design. Types of systems. Describe the principal functions of the systems analyst. List and describe the phases of the systems development life cycle. Describe the various data gathering and analysis tools. Describe a selection of systems design tools. Alternative approaches to Structured analysis & Design to the SLDC Explain the role of the maintenance task in the systems development life cycle.
  • 3. Contents• What is System Analysis and Design?• System Analyst.• System Development Life Cycle.• Feasibility Analysis.• Design.• Development• Implementation.
  • 4. Systems Analysis andDesign System Analysis and Design: what is it? Firstly we will define the system, than system analysis and system design as well. • System A set of detailed methods, procedures and routines established or formulation to carry out specify activity, perform a duty or solve a problem.
  • 5. Systems Analysis andDesign  System Analysis  The dissection of a system into its component pieces to study how those component pieces interact and work. (1) The survey and planning (2) The study and analysis (3) The definition  System Design The process of defining the architecture, components, modules, interfaces and data for a system to satisfy specified requirements.
  • 6. Systems Analysis andDesign Need for System Analysis and Design  Installing a system without proper planning leads to great user dissatisfaction and frequently causes the system to fall into disuse  Lends structure to the analysis and design of information systems  A series of processes systematically undertaken to improve a business through the use of computerized information systems
  • 7. Systems Analysis andDesign Roles of the System Analyst  The analyst plays a key role in information systems development projects.  Must understand how to apply technology to solve business problems.  Analyst may serve as change agents who identify the organizational improvement.
  • 8. Systems Analysis andDesign Qualities of the System Analyst  Problem solver  Communicator  Strong personal and professional ethics  Self-disciplined and self-motivated
  • 9. Systems Analysis andDesign System Analyst Recommend, Design, and Maintain Many Types of Systems for Users Strategic Level Higher Level A system analyst may be involved Knowledge with any or all of Level these systems at each organization Operational level Level
  • 10. Systems Analysis andDesign OPERATIONAL LEVEL Transaction Processing System (TPS) It is a process of large amounts of data for routine business transactions.  Boundary-Spanning Its concerned with the detection of information. It has two primary sources and two main sources. Primary sources of Information (1) Detect information (2) Send information into the environment presenting the company in a favorable light. Main sources of Information (1) Business intelligence. (2) Competitive information  Support the day-to-day operations of the company Example: Payroll Processing, Inventory Management.
  • 11. Systems Analysis andDesign KNOWLEDGE LEVEL  Office Automation System (OAS)  Supports data workers who share information, but do not usually create new knowledge Examples: Word processing, Spreadsheets etc.  Knowledge Work System (KWS)  Supports professional workers such as scientists, engineers, and doctors Examples: computer-aided design systems, virtual reality systems, investment workstations
  • 12. Systems Analysis andDesign Higher Level  Management Information System (MIS) To supports data worker who share information but do not usually create new knowledge. Example: Word processing, Spreadsheets, Desktop publishing, Email Electronic scheduling, Communication through voice mail, Email, Video  Decision Support System (DSS) Aids decision makers in the making of decisions Examples: financial planning with what-if analysis, budgeting with modeling  Expert System (ES) Captures and uses the knowledge of an expert for solving a particular problem which leads to a conclusion or recommendation. Examples: MYCIN (an early xpert system that used artificial intelligence ; XCON (eXpert CONfigurer)
  • 13. Systems Analysis andDesign Strategic Level  Executive Support System (ESS)  Helps executives to make unstructured strategic decisions in an informed way Examples: drill-down analysis, status access  Group Decision Support System (GDSS)  Permit group members to interact with electronic support Examples: email, Lotus Notes  Computer-Supported Collaborative Work System (CSCWS)  CSCWS is a more general term of GDSS. It may include software support called “groupware” for team collaboration via network computers. Example: video conferencing, Web survey system
  • 14. Systems Analysis andDesign Integrating New Technologies into Traditional Systems  Ecommerce and Web Systems.  Enterprise Resource Planning Systems.  Wireless Systems.  Open Source Software.  Need for Systems Analysis and Design.
  • 15. Systems Analysis andDesign Systems analysts need to be aware that integrating technologies affects all types of system
  • 16. Systems Analysis andDesign Ecommerce and Web Systems  Benefits  Increasing user awareness of the availability of a service, product, industry, person, or group.  The possibility of 24-hour access for users.  Improving the usefulness and usability of interface design.  Creating a system that can extend globally rather than remain local, thus reaching people in remote locations without worry of the time zone in which they are located.
  • 17. Systems Analysis andDesign Enterprise Resource Planning Systems (ERPS)  Performs integration of many information systems existing on different management levels and within different functions Example: SAP, Oracle
  • 18. Systems Analysis andDesign Wireless Systems  System analyst may be asked to design standard or wireless communication networks that integrate voice, video and email into organizational intranets or industry extranets  System analyst may also be asked to develop intelligent agents  Example: Microsofts new software based on Bayesian statistics  Wireless communication is referred as m-commerce (mobile commerce)
  • 19. Systems Analysis andDesign Open Source Software (OSS)  An alternative of traditional software development where proprietary code is hidden from the users  Open source software is free to distribute, share and modify  Characterized as a philosophy rather than simply the process of creating new software  Example: Linux Operating System, Apache Web Server, Mozilla Firefox Web browser, Koha, Newgenlib, Evergreen, OPALS, Greenstone, DSpace, Plone, Drupal, Eprint, and Joomla.
  • 20. Systems Analysis andDesign SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)  Typically the SDLC has 7 steps in the in the development and improvement of a computer system
  • 21. Systems Analysis andDesign IDENTIFYING PROBLEMS, OPPORTUNITIES, AND OBJECTIVES  Activity:  Interviewing user management  Summarizing the knowledge obtained  Estimating the scope of the project  Documenting the results  Output:  Feasibility report containing problem definition and objective summaries from which management can make a decision on whether to proceed with the proposed project
  • 22. Systems Analysis andDesign DETERMINING HUMAN INFORMATION REQUIREMENTS  Activity:  Interviewing  Sampling and investing hard data  Questionnaires  Observe the decision maker’s behavior and environment  Prototyping  Learn the who, what, where, when, how, and why of the current system  Output:  Analyst understands how users accomplish their work when interacting with a computer; and begin to know how to make the new system more useful and usable. The analyst should also know the business functions and have complete information on the people, goals, data and procedure involved
  • 23. Systems Analysis andDesign ANALYZING SYSTEM NEEDS  Activity:  Create data flow diagrams.  Complete the data dictionary.  Analyze the structured decisions made.  Prepare and present the system proposal.  Output:  Recommendation on what, if anything, should be done.
  • 24. Systems Analysis andDesign DESIGNING THE RECOMMENDED SYSTEM  Activity:  Design procedures for data entry  Design the human-computer interface  Design system controls  Design files and/or database  Design backup procedures  Output  Model of the actual system
  • 25. Systems Analysis andDesign DEVELOPING AND DOCUMENTING SOFTWARE  Activity:  System analyst works with programmers to develop any original software  Works with users to develop effective documentation  Programmers design, code, and remove syntactical errors from computer programs  Document software with help files, procedure manuals, and Web sites with Frequently Asked Questions  Output:  Computer programs  System documentation
  • 26. Systems Analysis andDesign TESTING AND MAINTAINING THE SYSTEM  Activity:  Test the information system  System maintenance  Maintenance documentation  Output:  Problems, if any  Updated programs  Documentation
  • 27. Systems Analysis andDesign IMPLEMENTING AND EVALUATING THE SYSTEM  Activity:  Train users  Analyst plans smooth conversion from old system to new system  Review and evaluate system  Output:  Trained personnel  Installed system
  • 28. Systems Analysis andDesign THE IMPACT OF MAINTENANCE  Maintenance is performed for two reasons  Removing software errors.  Enhancing existing software.
  • 29. Systems Analysis andDesign RESOURCE CONSUMPTION OVER THE SYSTEM LIFE
  • 30. Systems Analysis andDesign FEASIBILITY ANALYSES  Technical Feasibility: can we build it?  Economic Feasibility: should we build it?  Organizational Feasibility: if we build it, will they come?
  • 31. Systems Analysis andDesign TECHNICAL FEASIBILITY: CAN WE BUILD IT?  Familiarity with application: less familiarity more risk.  Familiarity with technology: less familiarity generates more risk.  Project size: large projects have more risk.  Compatibility: the hard it is so integrate the systems with the company’s existing technology, the higher the risk will be.
  • 32. Systems Analysis andDesign ECONOMIC FEASIBILITY: SHOULD WE BUILD IT?  Development Costs.  Annual operating costs.  Annual benefits (cost saving and revenues).  Intangible costs and benefits.
  • 33. Systems Analysis andDesign ORGANIZATIONAL FEASIBILITY: IF WE BUILD IT, WILL THEY COME?  Project champion(s).  Senior management.  Users.  Other stakeholders.  Is the project strategically aligned with the business.
  • 34. Systems Analysis andDesign OBJECT-ORIENTED SYSTEMS ANALYSIS AND DESIGN (OOSAD)  Analysis is performed on a small part of the system followed by design and implementation. The development cycle repeats with analysis, design and implementation of the next part and this repeats until the project is complete
  • 35. Systems Analysis andDesign ALTERNATE APPROACHES TO STRUCTURED ANALYSIS AND DESIGN AND TO THE SYSTEMS DEVELOPMENT LIFE CYCLE  Agile approach.  Prototyping  Ethics  Project champion Approach  Soft Systems Methodology (SSM)  Multiview
  • 36. Systems Analysis andDesign SUMMARY  Information is a key resource.  Systems analysts deal with many types of information systems.  Integration of traditional systems with new technologies.  Roles, qualities and skills of the systems analyst.  The systems Development Life Cycle.  Feasibility Analysis.  Alternate Approaches to structured analysis and design and to the SDLC.
  • 37. Systems Analysis andDesign REFERENCES  Systems Analysis and Design / by Kenneth E. Kendall and Julie E. Kendall- 8th ed.- New Delhi: PHI Learning, 2011  Systems Analysis and Design / Alan Dennis, Berbara Haley Wixom and Roberta M. Roth.-4th th.- New Jersey: John Wiley & Sons, 2010.  Dictionary of Computer and Information Technology / S. K. Bansal.- New Delhi: A. P. H. Publishing, 2009.
  • 38. Q/A ?