1. Systems Analysis & Design N106
Sri Lanka Institute of Information Technology BSc (IT) – First Year
Systems Analysis & Design N106

2. Lecture 1
Introduction

3. Course Identification
Lecturer in charge – Nideshika Ellepola –
Meeting lecturer on Wednesday 2.30 PM to 3.30 PM

4. 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

5. 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

6. 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.

7. 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

8. 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

9. References
Systems Analysis & Design By – Alan Dennis & Barbra Haley Wixom

10. 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.

11. 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.

12. 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.

13. THE SYSTEMS DEVELOPMENT LIFE CYCLE

14. 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

15. 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)

16. A “Simple” Process for Making Lunch

17. Planning Identifying business value Analyze feasibility
Develop work plan
Staff the project
Control and direct project

18. Analysis
Analysis
Information gathering
Process modeling
Data modeling

19. Design Physical design Architectural design Interface design
Database and file design
Program design

20. Implementation
Construction
Installation

21. Processes and Deliverables
Product
Project Plan
System Proposal
System
Specification
New System and
Maintenance Plan
Planning
Analysis
Design
Implementation

22. SYSTEM DEVELOPMENT METHODOLOGIES

23. What Is a Methodology? A formalized approach or series of steps
Examples
Process-Centered
Data-Centered
Object-Oriented

24. Waterfall Development Method

25. 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

26. Alternatives to the SDLC
Parallel Development
Rapid Application Development (RAD)
Phased Development
Prototyping
Spiral Development
Packaged Systems

27. Parallel Development Method

28. Pros and Cons of Parallel Development
Reduces Scheduled
Time
Less Chance of
Rework
Still Uses Paper
Documents
Sub-projects May Be
Difficult to Integrate

29. Rapid Application Development
CASE tools
JAD sessions
Fourth generation/visualization programming languages
Code generators

30. Three RAD Categories Phased development Prototyping
A series of versions
Prototyping
System prototyping
Throw-away prototyping
Design prototyping

31. Phased Development

32. 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.

33. How Prototyping Works

34. 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.

35. Throwaway Prototyping

36. Throwaway Prototyping
Advantages
Resolve technical issues.
Enables the users to understand the system.
Disadvantage
Do not make use of the prototype.

37. Criteria for Selecting the Appropriate Methodology
Clear user requirements
Familiar technology
Complexity
Reliability
Time schedule
Schedule visibility

38. TEAM ROLES AND SKILLS

39. Information Systems Roles
Business analyst
System analyst
Infrastructure analyst
Change management analyst
Project manager

40. 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.

41. Thank you!
Q & A