1 / 24

INFO2005 Requirements Analysis Introduction to Module

INFO2005 Requirements Analysis Introduction to Module. Department of Information Systems. Module Leader. Pam Watt G5.32 pw@dmu.ac.uk. Lecture 1 - Learning Objectives. Introduce module schedule & reading list Brief introduction the the module Overview of main topic areas. Module Delivery.

gavin-strong
Télécharger la présentation

INFO2005 Requirements Analysis Introduction to Module

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. INFO2005Requirements AnalysisIntroduction to Module Department of Information Systems

  2. Module Leader • Pam Watt • G5.32 pw@dmu.ac.uk

  3. Lecture 1 - Learning Objectives • Introduce module schedule & reading list • Brief introduction the the module • Overview of main topic areas

  4. Module Delivery • Lectures • 2 lectures per week • Tutorial • 1 each week (but not weeks 5 & 6) • Labs • staffed in weeks 4, 5 & 6; unstaffed weeks 7-12 (See Timetable for times/rooms)

  5. Module Assessment • Coursework - 50% • Phase Test • Group Case Study • Examination - 50% • 2-hour closed-book

  6. Module Learning Materials • Set Text • Bennett, S., McRobb, S. & Farmer, R. “Object-Oriented Systems Analysis and Design using UML” McGraw-Hill 1999

  7. Module Learning Materials • Bibliography • see handouts • additional directed reading may be given in lectures • Web-based Resources • tutorials covering example TPS, Real-Time System and MIS • use of Internet as a research tool (search engines) • http://www.cse.dmu.ac.uk/~pw • Library/Journals

  8. Module Characteristics • Successful information systems can only be developed with a sound understanding of the requirements of users and other stakeholders. These requirements are often complex and must be analysed with care. • This module provides the necessary skills and techniques to achieve this understanding, building on elements of systems analysis that have been taught in Part 1.

  9. Module Characteristics • It focuses on the capture, modelling and analysis of requirements for new software systems, and is complementary to INFO2003 Database Design and to INFO2004 Object-Oriented Systems Design. • The approach taken is primarily object-oriented and uses UML notation but some traditional requirements modelling techniques will be introduced.

  10. Indicative Contents • Practical and theoretical introduction to techniques for the capture and modelling of usage requirements, e.g. traditional fact-finding approaches, JAD workshops, Use Cases and Task Scripts. • Practical and theoretical introduction to techniques for modelling and analysis of logical requirements, e.g. Class and Activity Diagrams.

  11. Indicative Contents • Introduction to a Systems Development methodology as a framework for requirements analysis, e.g. the Rational Unified Process. • Lifecycle issues, e.g. project planning, costing and estimation, management and control. • Brief comparison of the organisation and requirements analysis techniques of one or two other methodological approaches, e.g. SSADM and OPEN.

  12. Characteristics of Modern Systems • Volatile business environment • Wide range of complex system types • Increased use of complex data types • Sophisticated user interfaces (GUIs) • Client-Server environments / distributed systems • Tendency for larger systems

  13. Types of Requirements • Functional • What the system should do i.e.

  14. Types of Requirements • Non-functional requirements

  15. Types of Requirements • Requirements capture involves identifying:

  16. Is this Systems Development?

  17. Project Selection Feasibility Study “Waterfall” Approach Systems Investigation Systems Analysis Systems Design Systems Implementation Review & Maintenance Traditional Systems Lifecycle May have iterations but these are very costly

  18. Identify basic Information Requirements Develop System to fulfil basic Requirements Prototyping Tools: Application Packages Program Generators Reusable Code 4GLs Experiment with basic system in Application area Refine Prototype to reflect known Requirements Prototyping - amended lifecycle

  19. Software Development - Life Cycles Start Requirements gathering and refinement • Prototyping Stop Engineer product Quick design Refining prototype Building prototype Customer evaluation of prototype

  20. Problems with Systems Development • Poor requirements capture

  21. Effective Deployment of best practice • Involve users • Manage requirements • Iterative systems development • Incremental systems development • Use component-based architectures • Model systems visually • Verify system quality • Control changes to system

  22. Requirements Modelling • Use the Unified Modeling Language (UML) • Guided by analysis and organisational patterns • Key to ensuring that requirements are complete and consistent • (can we achieve 100% confidence?)

  23. Summary • Introduced module schedule & reading list • Brief introduction the the module • Overview of main topic areas

  24. References • References will be provided for each lecture e.g. • Bennett, S., McRobb, S. & Farmer, R. “Object-Oriented Systems Analysis and Design using UML” McGraw-Hill 1999, Ch 1 & 2 • Lectures provide an overview of the module topics. It is essential that you read around the subject area in order to gain the required depth of knowledge. These references are there to help you do this.

More Related