System Analysis And Design Management Information System

21,280
-1

Published on

3 Comments
17 Likes
Statistics
Notes
  • Thank You very much, I've also learn the way to design a great slide
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Do you have powerpoint presentation about policy in education
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • I have seen more than 3 presentations just like this one. Same number of slides, same text, same pictures and graphics, just photocopies of the orginal. The only difference is the name of the up loader and the theme (design) of the slides. Where I appreciate the original up loader (the one who did it first) at the same same time I also strongly condemn all those who have just downloaded the original, changed the theme and uploaded it under their name. SHAME ON YOU ALL .... CHEATERS
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
21,280
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
1,218
Comments
3
Likes
17
Embeds 0
No embeds

No notes for slide

System Analysis And Design Management Information System

  1. 1. 1 -
  2. 2. <ul><li>Many failed systems were abandoned because analysts tried to build wonderful systems without understanding the organization. </li></ul><ul><li>The primarily goal is to create value for the organization. </li></ul>1 -
  3. 3. <ul><li>The systems analyst is a key person analyzing the business, identifying opportunities for improvement, and designing information systems to implement these ideas. </li></ul><ul><li>It is important to understand and develop through practice the skills needed to successfully design and implement new information systems. </li></ul>1 -
  4. 4. 1 -
  5. 5. <ul><li>The project -- </li></ul><ul><ul><li>Moves systematically through phases where each phase has a standard set of outputs </li></ul></ul><ul><ul><li>Produces project deliverables </li></ul></ul><ul><ul><li>Uses deliverables in implementation </li></ul></ul><ul><ul><li>Results in actual information system </li></ul></ul><ul><ul><li>Uses gradual refinement </li></ul></ul>1 -
  6. 6. <ul><li>Planning (Why build the system? How should the team go about building it?) </li></ul><ul><li>Analysis (Who uses system, what will it do, where and when will the system be used?) </li></ul><ul><li>Design (How will the system work?) </li></ul><ul><li>Implementation (System delivery) </li></ul>1 -
  7. 7. 1 - A simple process for making lunch
  8. 8. 1 - Process Product Planning Analysis Design Implementation System Request Feasibility Analysis Workplan System Proposal System Specification New System and Maintenance Plan
  9. 9. 1 -
  10. 10. <ul><li>A formalized approach to implementing the SDLC </li></ul><ul><ul><li>A series of steps and deliverables </li></ul></ul><ul><li>Methodology Categories </li></ul>1 - <ul><li>Process-Centered </li></ul><ul><li>Data-Centered </li></ul><ul><li>Object-Oriented </li></ul><ul><li>Structured Design </li></ul><ul><li>Rapid Application Development </li></ul><ul><li>Agile Development </li></ul>
  11. 11. 1 -
  12. 12. 1 - Pros Cons Identifies systems requirements long before programming begins Minimizes changes to requirements as project progresses Design must be specified on paper before programming begins Long time between system proposal and delivery of new system
  13. 13. 1 -
  14. 14. 1 - Pros Cons Reduces Schedule Time Less Chance of Rework Still Uses Paper Documents Sub-projects May Be Difficult to Integrate
  15. 15. 1 - Spiral Model
  16. 16. 1 -
  17. 17. <ul><li>Incorporate special techniques and tools: </li></ul><ul><ul><li>CASE tools </li></ul></ul><ul><ul><li>JAD sessions </li></ul></ul><ul><ul><li>Fourth generation/visualization programming languages </li></ul></ul><ul><ul><li>Code generators </li></ul></ul>1 -
  18. 18. <ul><li>Phased development </li></ul><ul><ul><li>A series of versions developed sequentially </li></ul></ul><ul><li>Prototyping </li></ul><ul><ul><li>System prototyping </li></ul></ul><ul><li>Throw-away prototyping </li></ul><ul><ul><li>Design prototyping </li></ul></ul>1 -
  19. 19. 1 - Insert Figure 1-4 here
  20. 20. 1 - Pros Cons Users Get a System To Use Quickly Users Can Identify Additional Needs For Later Versions Users Work with a System that is Intentionally Incomplete
  21. 21. 1 -
  22. 22. 1 - Pros Cons Users Interact with Prototype Very Quickly Users Can Identify Needed Changes And Refine Real Requirements Tendency to do Superficial Analysis Initial Design Decisions May Be Poor
  23. 23. 1 -
  24. 24. 1 - Pros Cons Risks are Minimized Important Issues are Understood Before the Real System is Built May Take Longer Than Prototyping
  25. 25. 1 -
  26. 26. 1 - Pros Cons Fast Delivery of Results Works Well in Projects With Undefined or Changing Requirements Requires Discipline Works Best in Small Projects Requires Much User Input
  27. 27. <ul><li>Clear user requirements </li></ul><ul><li>Familiarity with technology </li></ul><ul><li>Complexity of system </li></ul><ul><li>Reliability of system </li></ul><ul><li>Time schedule </li></ul><ul><li>Schedule visibility </li></ul>1 -
  28. 28. 1 -
  29. 29. <ul><li>Business analyst </li></ul><ul><li>Systems analyst </li></ul><ul><li>Infrastructure analyst </li></ul><ul><li>Change management analyst </li></ul><ul><li>Project manager </li></ul>1 -
  30. 30. <ul><li>The Systems Development Lifecycle consists of four stages: Planning, Analysis, Design, and Implementation </li></ul><ul><li>There are six major development methodologies : the waterfall method, the parallel development method, the phased development method, system prototyping, design prototyping, and agile development. </li></ul><ul><li>There are five major team roles : business analyst, systems analyst, infrastructure analyst, change management analyst and project manager. </li></ul>1 -

×