Aims of the Module To help students integrate the skills and knowledge acquired during the course to produce detailed system requirements, and systems analysis to a realistic problem.
Module Content In completing this module, students should be able to demonstrate that they have the ability to: 1. Investigate & plan a project 2. Develop a project 3. Devise verification & test data 4. Evaluate their work
Teaching Lecture in weeks 1 & 2 Additional skills gained from COMP2013 Professional Standards Students must work individually with guidance from the supervisor
Deliverables 1. Submission of proposal (Thurs 14 Oct) 2. System Investigation (Thurs 18 Nov) 3. Development of project (Thurs 9 Dec) 4. Demonstration (week 12) Warning! Late work, without prior agreement with supervisor, will be capped at 40%.
Choose your project Choose a real life project if possible Or choose from the suggested list Agree topic with supervisor Formulate a project plan
System Investigation Fact finding Document findings Re-visit & refine project plan
System Development System analysis System documentation Discussion document of s/ware & h/ware Verification document Critical evaluation of project DEMONSTRATION
What do you do during Systems Analysis? ‘Systems analysis’ is often used as the name of a project phase that includes: –investigating a situation –recording what you have learned in the form of notes and models –analysing your notes and models in more detail –producing a specification of requirements for a new system—i.e. what it must do to meet its users’ needs
What do you do during Systems Analysis? (cont’d) Sometimes the analysis phase is split into: –Fact-finding and recording –Requirements analysis Abstract modelling notations are fundamental to all analysis activities In UML the main ones are: –Use Case Diagram –Class Diagram
Fact-Finding Techniques Remembering the techniques: –S... (for Sampling) –Q... (for Questionnaires) –I... (for Interviewing) –R... (for Reading or Research) –O... (for Observation) Not in order of importance, or sequence in the project
Fact Recording Requirements must be carefully documented Analyst’s notes must be: –summarised –organised –filed One way to do this is to use a CASE tool –E.g. a set of use case diagrams and descriptions
Resources Handbook website http://www.cse.dmu.ac.uk/~pw Books Object-Orientated Systems Analysis & Design Bennett, McRobb & Farmer (McGraw-Hill) The Essence of Computer projects - A student’s guide CW Dawson (Prentice-Hall)