Systems analysis and design (Record no. 1653)
[ view plain ]
| 000 -LEADER | |
|---|---|
| fixed length control field | 11642nam a2200157 4500 |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| International Standard Book Number | 9788175156180 9( pb) |
| 040 ## - CATALOGING SOURCE | |
| Transcribing agency | CUS |
| 082 ## - DEWEY DECIMAL CLASSIFICATION NUMBER | |
| Classification number | 004.21 |
| Item number | AWA/S |
| 100 ## - MAIN ENTRY--PERSONAL NAME | |
| Personal name | Awad, Elias M. |
| 245 ## - TITLE STATEMENT | |
| Title | Systems analysis and design |
| Statement of responsibility, etc. | Elias M. Awad |
| 250 ## - EDITION STATEMENT | |
| Edition statement | 2nd ed. |
| 260 ## - PUBLICATION, DISTRIBUTION, ETC. (IMPRINT) | |
| Place of publication, distribution, etc. | Delhi : |
| Name of publisher, distributor, etc. | Galotia Publications , |
| Date of publication, distribution, etc. | 1997. |
| 300 ## - PHYSICAL DESCRIPTION | |
| Extent | 524 p. |
| Other physical details | ill. ; |
| 505 ## - FORMATTED CONTENTS NOTE | |
| Formatted contents note | Part ne<br/>Overview<br/>1. Systems Concepts the Information Systems Environment<br/>Introduction. The Systems Concept: Definition. Characteristics 8f a<br/>System: Organization, Interaction. Interdependence, tntegfration. Cen<br/>tral Objective. Elements of a System: Outputs and inputs. Processoris).<br/>Control. Feedback. Environment. Boundaries and Intetface. lypes of<br/>Systems: Physical or Abstract Systems. Open or Closed Systems.^Man-<br/>Made information Systems. Illustration -A Dynamic Personnel Infor<br/>mation System Model.<br/>2. The System Development Life Cy®^®<br/>Introduction. The System Development Life Cycle: Recognition of Need<br/>—What is the Problem? Feasibility Stutfy. ^talysls. Design. Imple<br/>mentation. Post-implementation and Maintenance. Considerations for<br/>Candidate Systems: Political Considerations. Planning and Control for<br/>System Success. Prototvoing.<br/>3. The Role of the Systems Analyst<br/>Introduction. Definition. Historical Perapective: The Earfy Years. The<br/>War Effort. VVhat Does It Take to Do S^tems Analysis? Acsdemic and<br/>Persorud Cjpalifications. The MuUifaces«d Role of the Anatyst: Otange<br/>Agent. Investigator and Monitor. Architect. Pi^hologist. Salesperson.<br/>Motivator. Politician. Tlie Analyst/User Interface: Behavioral Issues.<br/>Conflict Resolution. The Place of the Analyst in the MIS Oi^anization:<br/>The MIS Organization. Rising Positions in System Development: The<br/>Paraprqfessional. The Technical Writer. Conclusions.<br/>Part Two<br/>Systems Anafysis<br/>4. Systems Planning and the Initial Investigation<br/>Introduction. Bases for Planning in Systems Analysis: Dimensions of<br/>Planning. Initial Investigation: Needs Identification. Determining the<br/>User's Information Requirements. Case Scenario. Problem Definition<br/>and Project Initiation. Background Analysis. Fdct-Pinding. Fact Analysis.<br/>Determination of Feasibility.<br/>8. Informatipn Gathering<br/>Introduction. VWiat Kinds of Information Do We Need? Information<br/>about the Firm. Information about User Staff. Information about Work<br/>Flow. Where Does Information Originate? Information-Gathering<br/>Tools: Review of Literature, Procedures, and Forms. On-Site Observa<br/>tion. Interviews and Qpestionnaires. Types cf Interviews and Qpestionnaires.<br/>6. Hie Tools of Structured Analysis<br/>^ Iritroduction. What Is Structured Anafysis? The Tools of Structured<br/>Analysis: The Data Flow Diagram (DFD). Data Dictionary. Decision Tree<br/>and Structured English. Decision TMes. Pros and Ctms of Each Tool.<br/>7. PeasibllityStudy<br/>Introduction. System Performance Definition: Statement cf Con<br/>straints. Identification cf Specffic System Objectives. Inscription of<br/>Outputs. Feasibility Study: Feasibility Considerations. Steps in Feasi<br/>bility Ans^is. Feasibility Report. Oral Presentation.<br/>8. Cost/Benefit Analysis<br/>Introduction. Data Analysis. Cost/Benefit Analysis: Cost and Benefit<br/>Categories. Procedure for Cost/Benefit Determination. The System<br/>IVopo^<br/>Put Three<br/>Systems Design<br/>8« the Process and Stages of Systems Design<br/>Introduction. The Process of Design: Logical and Physical Design. Design<br/>Methodologies: Structured Design- Porm-Driven Methodology—<br/>The IPO Charts. Structured WsJkthroug/t. Major Development Activi<br/>ties: Personnel Allocation. Audit Considerations: Processir^ Controls<br/>and Data Walidation. Audit TYail and Documentation Control.<br/>10. Input/Output and Forma Design<br/>Introduction, input Design: Input Data. Input Media and Devices. Out<br/>put Design. Forms Design: What's a Porm? Classification of Porms.<br/>Requirements cfPorms Design. Carbon Paper as a Porm Copier. Types<br/>if Porms. Layout Considerations. Porms Control.<br/>11. File Organization and Data Base Design<br/>introduction. File Structure. File Oiganization: Sequential Organiza<br/>tion. Indeyed-Secptential Organization. Inverted List Organization. Dir&:<br/>t-Access Org/anization. Data Base Design: Objectives of Data Base.<br/>Key Terms. Logical and Physical Views of Data. Data Structure. Nor<br/>malization. The Role of the Data Base Administrator.<br/>l>iarl Four<br/>S^tem Implementation<br/>U. System Testing and Qpiality Assurance<br/>introdueiion. Why ^tem Testing? What Do We Test for? The Nature<br/>of Test Data. The Test Plan: ActiWly Network for System Testing. Sys<br/>tem Testing. Quality Assurance: Quality Assurance Goals in the Systems<br/>Lfe Cycle. Levels of Qpality Assurance. Trends in Testing. Role of the<br/>Data Processing Auditor: The Audit Trail.<br/>13. implementation and Software Maintenam^<br/>introduction. Conversion: Activity Network for Conversion. Combating<br/>Resistance to Change. Post-implementation Review: Request for Re<br/>view. A Review Plan. Software Maintenance: Maintenance or Enhance<br/>ment? Primary Activities of a Maintenance Procedure. Reducing Main<br/>tenance Costs.<br/>14. Hardware/Software Selection and the Computer Contract<br/>Introduction. The- Computer Industiy: Hardware Suf^liers. Software<br/>Suppliers. Service Suppliers. The Software industiy: Types of Software.<br/>A Procedure for Hardware»«oflwarB Selection: Major Phases in Selec<br/>tion. Software Selection. The Evaluation Process. Financial Considera<br/>tions in Selection: The Rentbl Option. The Lease Option. The Purchase<br/>Option. The Used Computer. The Computer Contract: The Art of<br/>Negotiation. Contract Checklist.<br/>18. Project Scheduling and Software<br/>Introduction. Why Do Systems Fail? What is Project Management? A<br/>18o Se^irSttsTp Disaster/Recmsi^p araid BtisScs<br/>in System Development<br/>Introcfuction. System Security: Dejiniiiona. Threats to System Security.<br/>Control Measures. Disaster/Recoveiy Planning: The Plan. Ethics In<br/>System Development: Ethics Codes and Standards of Behavior.<br/>Glossary of Terma<br/>ImSeacPart ne<br/>Overview<br/>1. Systems Concepts the Information Systems Environment<br/>Introduction. The Systems Concept: Definition. Characteristics 8f a<br/>System: Organization, Interaction. Interdependence, tntegfration. Cen<br/>tral Objective. Elements of a System: Outputs and inputs. Processoris).<br/>Control. Feedback. Environment. Boundaries and Intetface. lypes of<br/>Systems: Physical or Abstract Systems. Open or Closed Systems.^Man-<br/>Made information Systems. Illustration -A Dynamic Personnel Infor<br/>mation System Model.<br/>2. The System Development Life Cy®^®<br/>Introduction. The System Development Life Cycle: Recognition of Need<br/>—What is the Problem? Feasibility Stutfy. ^talysls. Design. Imple<br/>mentation. Post-implementation and Maintenance. Considerations for<br/>Candidate Systems: Political Considerations. Planning and Control for<br/>System Success. Prototvoing.<br/>3. The Role of the Systems Analyst<br/>Introduction. Definition. Historical Perapective: The Earfy Years. The<br/>War Effort. VVhat Does It Take to Do S^tems Analysis? Acsdemic and<br/>Persorud Cjpalifications. The MuUifaces«d Role of the Anatyst: Otange<br/>Agent. Investigator and Monitor. Architect. Pi^hologist. Salesperson.<br/>Motivator. Politician. Tlie Analyst/User Interface: Behavioral Issues.<br/>Conflict Resolution. The Place of the Analyst in the MIS Oi^anization:<br/>The MIS Organization. Rising Positions in System Development: The<br/>Paraprqfessional. The Technical Writer. Conclusions.<br/>Part Two<br/>Systems Anafysis<br/>4. Systems Planning and the Initial Investigation<br/>Introduction. Bases for Planning in Systems Analysis: Dimensions of<br/>Planning. Initial Investigation: Needs Identification. Determining the<br/>User's Information Requirements. Case Scenario. Problem Definition<br/>and Project Initiation. Background Analysis. Fdct-Pinding. Fact Analysis.<br/>Determination of Feasibility.<br/>8. Informatipn Gathering<br/>Introduction. VWiat Kinds of Information Do We Need? Information<br/>about the Firm. Information about User Staff. Information about Work<br/>Flow. Where Does Information Originate? Information-Gathering<br/>Tools: Review of Literature, Procedures, and Forms. On-Site Observa<br/>tion. Interviews and Qpestionnaires. Types cf Interviews and Qpestionnaires.<br/>6. Hie Tools of Structured Analysis<br/>^ Iritroduction. What Is Structured Anafysis? The Tools of Structured<br/>Analysis: The Data Flow Diagram (DFD). Data Dictionary. Decision Tree<br/>and Structured English. Decision TMes. Pros and Ctms of Each Tool.<br/>7. PeasibllityStudy<br/>Introduction. System Performance Definition: Statement cf Con<br/>straints. Identification cf Specffic System Objectives. Inscription of<br/>Outputs. Feasibility Study: Feasibility Considerations. Steps in Feasi<br/>bility Ans^is. Feasibility Report. Oral Presentation.<br/>8. Cost/Benefit Analysis<br/>Introduction. Data Analysis. Cost/Benefit Analysis: Cost and Benefit<br/>Categories. Procedure for Cost/Benefit Determination. The System<br/>IVopo^<br/>Put Three<br/>Systems Design<br/>8« the Process and Stages of Systems Design<br/>Introduction. The Process of Design: Logical and Physical Design. Design<br/>Methodologies: Structured Design- Porm-Driven Methodology—<br/>The IPO Charts. Structured WsJkthroug/t. Major Development Activi<br/>ties: Personnel Allocation. Audit Considerations: Processir^ Controls<br/>and Data Walidation. Audit TYail and Documentation Control.<br/>10. Input/Output and Forma Design<br/>Introduction, input Design: Input Data. Input Media and Devices. Out<br/>put Design. Forms Design: What's a Porm? Classification of Porms.<br/>Requirements cfPorms Design. Carbon Paper as a Porm Copier. Types<br/>if Porms. Layout Considerations. Porms Control.<br/>11. File Organization and Data Base Design<br/>introduction. File Structure. File Oiganization: Sequential Organiza<br/>tion. Indeyed-Secptential Organization. Inverted List Organization. Dir&:<br/>t-Access Org/anization. Data Base Design: Objectives of Data Base.<br/>Key Terms. Logical and Physical Views of Data. Data Structure. Nor<br/>malization. The Role of the Data Base Administrator.<br/>l>iarl Four<br/>S^tem Implementation<br/>U. System Testing and Qpiality Assurance<br/>introdueiion. Why ^tem Testing? What Do We Test for? The Nature<br/>of Test Data. The Test Plan: ActiWly Network for System Testing. Sys<br/>tem Testing. Quality Assurance: Quality Assurance Goals in the Systems<br/>Lfe Cycle. Levels of Qpality Assurance. Trends in Testing. Role of the<br/>Data Processing Auditor: The Audit Trail.<br/>13. implementation and Software Maintenam^<br/>introduction. Conversion: Activity Network for Conversion. Combating<br/>Resistance to Change. Post-implementation Review: Request for Re<br/>view. A Review Plan. Software Maintenance: Maintenance or Enhance<br/>ment? Primary Activities of a Maintenance Procedure. Reducing Main<br/>tenance Costs.<br/>14. Hardware/Software Selection and the Computer Contract<br/>Introduction. The- Computer Industiy: Hardware Suf^liers. Software<br/>Suppliers. Service Suppliers. The Software industiy: Types of Software.<br/>A Procedure for Hardware»«oflwarB Selection: Major Phases in Selec<br/>tion. Software Selection. The Evaluation Process. Financial Considera<br/>tions in Selection: The Rentbl Option. The Lease Option. The Purchase<br/>Option. The Used Computer. The Computer Contract: The Art of<br/>Negotiation. Contract Checklist.<br/>18. Project Scheduling and Software<br/>Introduction. Why Do Systems Fail? What is Project Management? A<br/>18o Se^irSttsTp Disaster/Recmsi^p araid BtisScs<br/>in System Development<br/>Introcfuction. System Security: Dejiniiiona. Threats to System Security.<br/>Control Measures. Disaster/Recoveiy Planning: The Plan. Ethics In<br/>System Development: Ethics Codes and Standards of Behavior.<br/>Glossary of Terma<br/>ImSeac |
| 942 ## - ADDED ENTRY ELEMENTS (KOHA) | |
| Koha item type | General Books |
| Withdrawn status | Lost status | Damaged status | Not for loan | Home library | Current library | Shelving location | Date acquired | Full call number | Accession number | Date last seen | Date last checked out | Koha item type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Central Library, Sikkim University | Central Library, Sikkim University | General Book Section | 31/05/2016 | 004.21 AWA/S | P18650 | 14/07/2018 | 14/07/2018 | General Books |