Sad lecture 2
Download as PPTX, PDF1 like406 views
The document outlines the 9 steps in the systems analysis and design life cycle: 1) requirements determination, 2) requirements specification, 3) feasibility analysis, 4) final specifications, 5) hardware study, 6) system design, 7) system implementation, 8) system evaluation, and 9) system modification. It then provides details on the tasks involved in each step and discusses the roles, attributes, and tools used by systems analysts.
Sad lecture 2
- 1. Lecure2 SYSTEMS ANALYSIS AND DESIGN LIFE CYCLE
- 2. 1. Nine Steps in designing Information Systems. 2. Tasks performed in each step. 3. Nature of tasks performed by Systems Analysts. 4. The attributes of Systems Analysts. 5. The tools used by Systems Analysts. LEARNING GOALS
- 3. Steps involved in Analysis and Design 1. Requirements Determinations 2. Requirements Specifications 3. Feasibility Analysis 4. Final Specifications 5. Hardware Study 6. System Design 7. System Implementation 8. System Evaluation 9. System Modification LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN
- 4. Step 1 : Requirements Determination ▪ Arrived at by a consensus among managers ▪ Priorities among applications determined ▪ Pick high priority applications. LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN
- 5. Step 2 : Requirements Specification ▪ Known as System Requirements Specification (SRS) ▪ Understand the existing System ▪ Applications where a system is required are listed ▪ Arrive at the specifications of the users’ Requirements after discussions with the user ▪ A system may encompass several applications LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN
- 6. Step 3 : Feasibility Analysis ▪ Formulate Goals of the system and quantify goals ▪ Find alternative methods of meeting the goals ▪ For each alternative assess resources needed - Human Resources - Time and Money - Equipment needed ▪ Assess cost of each alternative ▪ Find the best alternative method subject to resource constraints LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN
- 7. Step 4 : Final Specifications ▪ Specifications would state what the system would achieve. ▪ Specification drawn up are improved for implementation. ▪ SRS written- given to user and agreement reached LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN
- 8. Step 5 : Hardware Study ▪ Determine Hardware and Software required to execute the application. ▪ Determine Response time,Volume of data to be processed, Frequency of reports etc & then pick the hardware. LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN
- 9. Step 6 : System Design ▪ Logical Design of the System ▪ Objects Identified ▪ Database Designed ▪ Program Specification drawn up ▪ Implementation Plan Drawn up ▪ Test Plan LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN
- 10. Step 7 : System Implementation ▪ Write Programs ▪ Create Database ▪ Document System ▪ Train Users ▪ Trial run of the system ▪ Test and Accept LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN
- 11. Step 8 : System evaluation ▪ Find out from Users whether the System meets specified requirements. ▪ List areas of dissatisfaction and find reasons ▪ Suggest if there has to be any improvements to the system LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN
- 12. Step 9 : System Modification ▪ Fix errors ▪ Add/Delete features as required by users ▪ Tune the System ▪ Continuously monitor system and assess performance LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN
- 13. Feasibility Analysis System Design Hardware Study System Evaluation System Maintenance Improved System Revised Requirements Budget & schedule Physical Requirements Configuration Data System Logical Design User Requirements Requirements Requirements Determination Specification Feasibility Study System Specification Analysis Functional Specifications Decision to Design Information System System Implementation Revised Prioritized Requirements Specifications Test Plan System Life Cycle Diagram
- 14. ▪ Defining Requirements - Involves Interviewing Users ▪ Prioritizing Requirements - Obtain Users Consensus ▪ Fact Gathering - Data, Facts, Opinions of Managers - Lower level Users should be consulted ROLES OF SYSTEMS ANALYST
- 15. ▪ Analysis and evaluation - Arrive at appropriate system ▪ Solving problems - Hazy requirements converted into specific requirements - Suggest many alternative solutions - Quantify cost and benefits ROLES OF SYSTEMS ANALYST
- 16. ▪ Drawing up specifications - FUNCTIONAL SPECIFICATIONS - Understood by users and programmers - Accepted by users - Precise and detailed - Account for possible changes ROLE OF SYSTEMS ANALYST
- 17. SYSTEM DESIGN ▪ Logical design of system - Objects identification - Normalizing database - Test plan ▪ Design must be modular to accommodate change ROLE OF SYSTEMS ANALYST
- 18. ▪ Evaluating Systems - Evaluation after use for sometime - Plan periodicity for evaluation - Modify as needed ROLE OF SYSTEMS ANALYST
- 19. ▪ KNOWLEDGE OF ORGANISATION - Knowing user’s jargon & practices - Know Management functions. ▪ KNOWLEDGE OF COMPUTERSAND SOFTWARE - Knowledge of system design tools - Keep abreast of modern developments ATTRIBUTES OF A SYSTEMS ANALYST
- 20. ▪ GOOD INTERPERSONNAL RELATIONS - Need to work as team member - Lead smaller teams - Interface with programmers & Users - Motivator. ▪ ABILITY TO COMMUNICATE - Oral Presentation - Report Writing - Answer queries ATTRIBUTES OF A SYSTEMS ANALYST
- 21. ATTRIBUTES OF A SYSTEMS ANALYST ▪ ANALYTICAL MIND - Problem solving attitude - Ability to assess trade offs - Sound commonsense - Curiosity to learn about new organizations ▪ BREADTH OF KNOWLEDGE - Broad Liberal Knowledge - Variety of jobs to be tackled in diverse organizations
- 22. ▪ Data Flow Diagram ▪ Decision Tables ▪ Modeling Language such as UML ▪ Normalization of Databases ▪ Testing tools ▪ ISO/CMM procedure manuals TOOLS USED BY SYSTEMS ANALYST