requirements analysis 1. 1 introduction - 2005b501.ppt © copyright de montfort university 2000 all...

Requirements Analysis 1. 1 Introduction - 2005b501.ppt

© Copyright De Montfort University 2000All Rights Reserved

INFO2005Requirements Analysis

Introduction to Module

Department of Information Systems



Module Leader

Pam Watt – G5.32 [email protected]



Lecture 1 - Learning Objectives Introduce module schedule & reading

list Brief introduction the the module Overview of main topic areas



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)



Module Assessment

Coursework - 50%– Phase Test– Group Case Study

Examination - 50%– 2-hour closed-book



Module Learning Materials

Set Text– Bennett, S., McRobb, S. & Farmer, R.

“Object-Oriented Systems Analysis and Design using UML” McGraw-Hill 1999



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



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.



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.



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.



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.



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



Types of Requirements

Functional– What the system should do i.e.




Non-functional requirements




Requirements capture involves identifying:



Is this Systems Development?



Traditional Systems Lifecycle

Systems Investigation

Systems Analysis

Systems Design

Systems Implementation

Review & Maintenance

Feasibility Study

Project Selection

“Waterfall” Approach

May have iterations butthese are very costly



Prototyping - amended lifecycle

Identify basicInformationRequirements

Develop Systemto fulfil basicRequirements

Experiment withbasic system inApplication area

Refine Prototypeto reflect knownRequirements

Prototyping Tools:

Application PackagesProgram GeneratorsReusable Code4GLs



Software Development - Life Cycles

Prototyping

StartStart

StopStopRequirementsRequirementsgatheringgatheringand refinementand refinement

RefiningRefiningprototypeprototype

CustomerCustomerevaluation ofevaluation ofprototypeprototype

BuildingBuildingprototypeprototype

QuickQuickdesigndesign

EngineerEngineerproductproduct



Problems with Systems Development Poor requirements capture



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



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?)



Summary

Introduced module schedule & reading list

Brief introduction the the module Overview of main topic areas



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.

requirements analysis 1. 1 introduction - 2005b501.ppt © copyright de montfort university 2000 all...

Documents

analysis of requirements

montfort university

traditional requirements

v libraryjournals slide

requirements of users

elements of systems

brief introduction

theoretical introduction