CA 214 Systems Analysis B Sc in Computer

CA 214 Systems Analysis B. Sc. in Computer Applications

Renaat Verbruggen l l l School of Computing Room L 2. 43 (01)700. 5257 renaat@computing. dcu. ie Moodle: CA 228 Q&A etc.

Assessment l l Structured Systems Analysis and Design Project Language Project, Systems Analysis Project developed using Computer Assisted Software Engineering package (Select SSADM) individual, 50% Final Exam, 3 hours, 50%

Presentation l l l Lectures Readings available through Moodle Get the full readings completed early, use the summaries to revise.

Topics Introduction to the Structured Systems Analysis and design method (SSADM). l Justification and Phases of SSADM: l · Feasibility Study l · Requirements Analysis l · Requirements Specification l · Logical System Specification l · Physical Design Model

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

Book: If you are to buy one book for the course then I recommend: l l l Practical Business Systems Development Using SSADM A Complete Tutorial Guide, 3 rd Ed. , Philip L Weaver, Nicholas Lambrou & Matthew Walkley. FT/Prentice Hall. 0 -273 -65575 -2

Book… l 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 l l l 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 l l 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 l l l 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 l The analyst occupies a pivotal position between the user and the designer and needs methods to help. l 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. l

SSADM l l l 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)