SYSTEM ANALYSIS AND DESIGN LAB NARZU TARANNUM(NAT)

INTRODUCTION  THERE ARE SEVERAL TOOLS AND TECHNIQUES TO BUILD INFORMATION SYSTEMS, TO CHOOSE THE APPROPRIATE ONE TO BUILD YOUR SYSTEM, YOU MUST STUDY THEM FIRST AND KNOWS THEIR USES. METHODOLOGY IS AN APPROACH, A METHOD OR A TECHNIQUE FOR DEVELOPING INFORMATION SYSTEMS. THE METHODOLOGY DEFINES A METHOD AND A WAY OF DEVELOPING AN INFORMATION SYSTEM, GUIDING PLANNERS IN THE DESIRED WORKING METHOD.

SYSTEMS DEVELOPMENT TOOLS AND TECHNIQUES SYSTEMS ANALYSTS MUST KNOW HOW TO USE A VARIETY OF TECHNIQUES SUCH AS MODELING, PROTOTYPING, AND COMPUTER-AIDED SYSTEMS ENGINEERING TOOLS TO PLAN, DESIGN, AND IMPLEMENT INFORMATION SYSTEMS. SYSTEMS ANALYSTS WORK WITH THESE TOOLS IN A TEAM ENVIRONMENT, WHERE INPUT FROM USERS, MANAGERS, AND IT STAFF CONTRIBUTES TO THE SYSTEM DESIGN.

SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)

QUESTIONS TO BE ANSWERED PLANNING PHASE WHY SHOULD WE BUILD THIS SYSTEM? WHAT VALUE DOES IT PROVIDE? HOW LONG WILL IT TAKE TO BUILD? ANALYSIS PHASE WHO WILL USE IT? WHAT SHOULD THE SYSTEM DO FOR US? WHERE & WHEN WILL IT BE USED? DESIGN PHASE HOW SHOULD WE BUILD IT? IDENTIFY LANGUAGE PLATFORMS AND SYSTEM ARCHITECTURE NEEDED TO IMPLEMENT YOUR DESIGN.

INVESTIGATION/PLANNING INCLUDES FACT FINDING ANALYSIS INCLUDES FEASIBILITY ANALYSIS DESIGN IMPLEMENTATION TESTING MAINTENANCE

FOUR MAIN WAYS OF FACT FINDING QUESTIONNAIRE FORM INTERVIEW OBSERVATION STUDYING AT THE END OF THIS PROCEDURE YOU SHOULD WRITE DOWN A REPORT WHICH DESCRIBE THE EXISTING SYSTEM WITH A DESCRIPTION OF THE OUTPUT NEEDED FROM THE NEW SYSTEMS.

FEASIBILITY STUDY IT LOOKS AT THE CHANCES OF BEING ABLE TO SOLVE A PARTICULAR PROBLEM AT A REASONABLE COST. TECHNICAL FEASIBILITY ECONOMICAL FEASIBILITY IT’S THE DOCUMENT PRODUCES AN IDEA OF THE TIME THE PROJECT IS LIKELY TO TAKE ALONG SOME ESTIMATE OF COST ~COST/BENEFIT ANALYSIS & REPORT.

SYSTEM ANALYSIS ALSO INCLUDES: SET OVERALL GOALS OF THE SYSTEM SCOPE OF THE SYSTEM IDENTIFY SYSTEM INPUTS AND OUTPUTS USER TYPES AND THERE USER ACCESS LEVEL FUNCTIONAL & NONFUNCTIONAL REQUIREMENTS. IDENTIFY SYSTEMS LIMITATIONS

SYSTEM DESIGN PROCESS MODEL  PREPARE USE CASE DIAGRAM OF THE WHOLE SYSTEM AND DESCRIPTION FOR EACH USE CASE. DATA MODEL  DESIGN CLASS DIAGRAM/E-R DIAGRAM OF WHOLE SYSTEM AND DESCRIPTION OF EACH IDENTIFIED CLASS. SEQUENCE DIAGRAM  PREPARE THE SEQUENCE DIAGRAM OF THE WHOLE SYSTEM FROM PERSPECTIVE OF EACH TYPE OF USER. DESIGN STATE DIAGRAM/ FLOWCHART IDENTIFY THE IMPROVEMENT YOU HAVE ACHIEVED SO FAR FUTURE SCOPE OF WORK IMPLEMENTATION……………

REPORT INTRODUCTION THE EXISTING SYSTEM/BACKGROUND STUDY THE PROPOSED SYSTEM SYSTEM PROTOTYPE AND CODING SYSTEM IMPLEMENTATION, TESTING AND MAINTENANCE CONCLUSION REFERENCES  INCLUDING: TITLE PAGE; TABLE OF CONTENTS; LIST OF TABLES; LIST OF FIGURES; LIST OF APPENDICES.

CLASS SCHEDULE 14/01/16  INTRODUCTION 21/01/16  FINAL DAY OF GROUP AND PROJECT NAME SUBMISSION 28/01/16  PREPARE REPORT ON FACT FINDING AND FEASIBILITY ANALYSIS(2.5%) 4/02/16  PREPARE REPORT ON COST-BENEFIT ANALYSIS AND ALL THE INFORMATION'S OF SLIDE_9(2.5%) 11/02/16  PHASE#1 PRESENTATION (10%) 18/02/16  PHASE#1 PRESENTATION 25/02/16  SHOW USE-CASE DIAGRAM 03/03/16  SHOW CLASS DIAGRAM/E-R DIAGRAM(5%) 10/03/16  SHOW SEQUENCE DIAGRAM & STATE DIAGRAM 24/03/16  FINAL PRESENTATION(10%) 31/03/16  FINAL PRESENTATION