Systems Analysis & Design N106 Sri Lanka Institute of Information Technology BSc (IT) – First Year Systems Analysis & Design N106
Lecture 1 Introduction
Course Identification Lecturer in charge – Nideshika Ellepola E-mail – nideshika.e@sliit.lk Meeting lecturer on Wednesday 2.30 PM to 3.30 PM
Unit Objective To provide students an overall knowledge on the Software Development Life Cycle (SDLC) and to facilitate a detailed learning of the main phases which are, Planning Analysis Design Implementation
Unit Learning Outcomes On completion of the unit you should know, The phases and the sub activities of the SDLC Should also have a good knowledge of the different mechanisms used in the sub activities Able to compare and select an appropriate mechanism according to the given situation
Unit Assessment Criteria Mid term examination – 30% Group Project – 15% Lab Attendance & Performance – 05% Final Examination – 50% To pass this unit, students are required to get at least 45% of the marks for the midterm, the assignment and the final examination.
Unit Outline - Lectures Week Lecture Assignments Week 1 Introduction to SAD Week 2 Project Initiation Group Registration Week 3 Project Management Week 4 Systems Analysis Week 5 Gathering Information Assignment 1 Week 6 Process Modeling Week 7 Mid Term Examination Week 8 System Design Week 9 Architecture Design Week 10 User Interface Structure Design Week 11 User Interface Design Components Assignment 2 Week 12 Program Design Week 13 Construction & Installation Week 14 Revision
Unit Outline - Labs Week Lecture Week 2 Introduction to Microsoft Visio 2010 Week 3 Introduction to Microsoft Project 2010 Week 4 Exercises on Microsoft Project Week 5 Compiling a survey for information gathering Week 6 DFD Tutorial 1 & 2 Week 7 Mid Term Examination Week 8 DFD Tutorial 3 & 4 Week 9 DFD Tutorial 5 & 6 Week 10 DFD Tutorial 7 & 8 Week 11 DFD – Past Papers Week 12 Structure Chart Tutorial 1 Week 13 Structure Chart Tutorial 2 & 3 Week 14 Structure Chart - Past Papers
References Systems Analysis & Design By – Alan Dennis & Barbra Haley Wixom
Attention Attendance for the lecture + tutorial sessions is compulsory. (80% of attendance is compulsory) Lab Attendance is compulsory and marks will be given for performance. Plagiarism is prohibited. You will be penalized.
Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding the organization. The primarily goal is to create value for the organization.
Key Ideas The systems analyst is a key person analyzing the business, identifying opportunities for improvement, and designing information systems to implement these ideas. It is important to understand and develop through practice the skills needed to successfully design and implement new information systems.
THE SYSTEMS DEVELOPMENT LIFE CYCLE
Major Attributes of the Lifecycle The project – Moves systematically through phases where each phase has a standard set of outputs Produces project deliverables Uses deliverables in implementation Results in actual information system Uses gradual refinement
Project Phases Planning (Why build the system?) Analysis (Who, what when, where will the system be?) Design (How will the system work?) Implementation (System delivery)
A “Simple” Process for Making Lunch
Planning Identifying business value Analyze feasibility Develop work plan Staff the project Control and direct project
Analysis Analysis Information gathering Process modeling Data modeling
Design Physical design Architectural design Interface design Database and file design Program design
Implementation Construction Installation
Processes and Deliverables Product Project Plan System Proposal System Specification New System and Maintenance Plan Planning Analysis Design Implementation
SYSTEM DEVELOPMENT METHODOLOGIES
What Is a Methodology? A formalized approach or series of steps Examples Process-Centered Data-Centered Object-Oriented
Waterfall Development Method
Pros and Cons of the Waterfall Method Identifies systems requirements long before programming begins Design must be specified on paper Long time between system proposal and delivery of new system
Alternatives to the SDLC Parallel Development Rapid Application Development (RAD) Phased Development Prototyping Spiral Development Packaged Systems
Parallel Development Method
Pros and Cons of Parallel Development Reduces Scheduled Time Less Chance of Rework Still Uses Paper Documents Sub-projects May Be Difficult to Integrate
Rapid Application Development CASE tools JAD sessions Fourth generation/visualization programming languages Code generators
Three RAD Categories Phased development Prototyping A series of versions Prototyping System prototyping Throw-away prototyping Design prototyping
Phased Development
Phased Development Advantages Disadvantage Identification of important requirements. Quickly get a useful system to the users. Disadvantage Difficult to include all the important features in the version 1.
How Prototyping Works
Prototyping Advantages Disadvantage Have a system in place for the user at an early stage. Ability to quickly refine real requirements. Reassures the client. Disadvantage Requirements have to be analyzed quickly and carefully.
Throwaway Prototyping
Throwaway Prototyping Advantages Resolve technical issues. Enables the users to understand the system. Disadvantage Do not make use of the prototype.
Criteria for Selecting the Appropriate Methodology Clear user requirements Familiar technology Complexity Reliability Time schedule Schedule visibility
TEAM ROLES AND SKILLS
Information Systems Roles Business analyst System analyst Infrastructure analyst Change management analyst Project manager
Summary The Systems Development Lifecycle consists of four stages: Planning, Analysis, Design, and Implementation There are five major development methodologies: the waterfall method, the parallel development method, the phased development method, system prototyping and design prototyping. There are five major team roles: business analyst, systems analyst, infrastructure analyst, change management analyst and project manager.
Thank you! Q & A