CA214Systems Analysis

B.Sc. in Computer Applications

Renaat Verbruggen

School of Computing Room L2.43 (01)700.5257 renaat@computing.dcu.ie Moodle: CA214 Q&A etc.

Assessment

Structured Systems Analysis and Design Project Language Project, Systems Analysis Project developed using Computer Assisted Software Engineering package (Select SSADM) individual, 40%

A number of quizzes, MCQs 10% Final Exam, 2 hours, 50%

Presentation

Lectures Readings available through Moodle Get the full readings completed early, use

the summaries to revise.

Topics

Introduction to the Structured Systems Analysisand design method (SSADM).

Justification and Phases of SSADM: Feasibility Study Requirements Analysis Requirements Specification Logical System Specification Physical Design Model

Topics

Techniques of SSADM: · Logical Data Modelling; · Data Flow Modelling · Function Definition: · Relational Data Analysis · Entity/Event Analysis

Book:

If you are to buy one book for the course then I recommend:

Practical Business Systems DevelopmentUsing SSADM A Complete Tutorial Guide,3rd Ed.,Philip L Weaver, Nicholas Lambrou &Matthew Walkley. FT/Prentice Hall. 0-273-65575-2

Alternative Book:

Systems Analysis and Design, 8/EKenneth E. KendallJulie E. KendallISBN-10: 013608916XISBN-13:  9780136089162

Publisher:  Prentice HallCopyright:  2011International Student Edition

Book…

However I will link locally to the notes that we will be covering in lectures.

Electronic Books in DCU library

DCU Library currently subscribes to a number of e-books which can be accessed via the Safari Books Online database. You can search the entire set of 40 e-books by keyword, author, subject, title, etc..

STRUCTURED SYSTEMS ANALYSIS

Overall Goal: Specify a software system given a set of user requirements.

Structured Analysis is useful as it enables you to deal with possibly overwhelming detail in a modular, pictorial fashion.

By using the graphic, pictorial tools of Structured Systems Analysis we can overcome a number of serious problems in the investigation of systems.

SYSTEMS ANALYSIS PROBLEMS

The Systems Analyst finds it hard to learn enough about the business to see the requirements through the user’s eyes.

(Users tend to be “Doers” rather than “Explainers”).

Users don’t know what is feasible and what isn’t. (Either architecture, software or hardware).

There are no models to compare.

MORE SYSTEMS ANALYSIS PROBLEMS

The Systems Analyst can be Overwhelmed by detail (Both Business and Technical).

Narrative (story!) based specifications are frequently very difficult to understand (for both SA and User).

The detail of a specification document written in a way to be sensible to users may not be detailed enough for designers.

Core role of Systems Analyst

The analyst occupies a pivotal position between the user and the designer and needs methods to help.

User ↔ Systems Analyst ↔ Systems Designer

THE SPECIFICATION

If we can make a model of the system we can avoid the problem of the user wanting

to see what they get before they know what they want.

SSADM

UK Govt. standard. Method of organising the analysis and design

phases of a project We are not directly concerned with project

management side. It breaks into sets of activities and products (activities = when & how; products = what)