1 / 14

COMP2001/2011 HNC Individual Project

COMP2001/2011 HNC Individual Project. Module Leader - Pam Watt. 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.

charles-carney
Download Presentation

COMP2001/2011 HNC Individual Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. COMP2001/2011 HNC Individual Project Module Leader - Pam Watt

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

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

  4. Teaching Lecture in weeks 1 & 2 Additional skills gained from COMP2013 Professional Standards Students must work individually with guidance from the supervisor

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

  6. Choose your project • Choose a real life project if possible • Or choose from the suggested list • Agree topic with supervisor • Formulate a project plan

  7. System Investigation • Fact finding • Document findings • Re-visit & refine project plan

  8. System Development • System analysis • System documentation • Discussion document of s/ware & h/ware • Verification document • Critical evaluation of project • DEMONSTRATION

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

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

  11. Fact-Finding Techniques • Background Reading • Interviewing • Document Sampling • Observation • Questionnaires

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

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

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

More Related