You are on page 1of 3

Overview

BIT 3143/BIT 31403 ANALISA KEPERLUAN DAN SPESIFIKASI PERISIAN / REQUIREMENTS ANALYSIS AND SOFTWARE SPECIFICATION
Norhanim binti Selamat norhanim@uthm.edu.my 07-4533768
Rosziati Ibrahim BIT 3143/ BIT 31403 1

RPP-04 Class: Wednesday; 4pm 6pm; BK17 Lab: Friday; 3pm 5pm; MKP@ SEL Thursday; 2pm 4pm; MTW@ WTL Text Book: Leszek Maciaszek (2007). Requirements Analysis and System Design. 3rd. Ed. Addison Wesley.

Rosziati Ibrahim

BIT 3143/ BIT 31403

Learning Outcomes
After this lecture, you should be able to
Understand the software process Understand the software development Understand the important of requirements analysis process

Overview of Software Process and Requirements Analysis

Topics Covered
Introduction Methodologies Requirements and Specification Phases Requirements Analysis Why are Requirements So Important? Potential Impact of Requirements Errors What is good requirements document?
3 Rosziati Ibrahim BIT 3143/ BIT 31403 4

Rosziati Ibrahim

BIT 3143/ BIT 31403

Introduction
Computer applications are used in all aspects of life. Various complexity Maintenance cost is the most important in computer systems Methodologies Rapid prototyping Exploratory programming Automated software synthesis System assembly from reusable software The life cycle development methodology.

The Life Cycle of Software Development Methodology


Requirements Analysis System Specification Software Design Implementation System Testing Maintenance

Rosziati Ibrahim

BIT 3143/ BIT 31403

Rosziati Ibrahim

BIT 3143/ BIT 31403

Requirements and Specification Phases


As one phase then subdivided into sub-phases Requirements Definition Requirements Specification Software Specification Requirements analysis Write in natural language Divide the requirements phase into 2 classes; functional and non-functional requirements

Requirements Analysis (1)


Functional requirements concern with the task that the new system going to perform Non-functional requirements concern all the constraints of the new systems Performance, resources, design, and hardware. Other approaches defined this stage as feasibility study (cost, technical and time)

Rosziati Ibrahim

BIT 3143/ BIT 31403

Rosziati Ibrahim

BIT 3143/ BIT 31403

Requirements Analysis (2)


All approaches perform the same tasks Objectives and foundations of the system to develop Why and under which constraints it will develop? The next step is what is expected from the system Produce a document in natural language Understood by both customer and analyst Customer and supplier have different views on and ideal specification Natural language can be understood by customer Natural language cause major errors and incompleteness to developer The specification for them is formal one
Rosziati Ibrahim BIT 3143/ BIT 31403 9

Why Are Requirements So Important?


The later the error detect, the more expensive it will be to repair Many unknown error until certain stage in development life cycle Many requirements errors being made. Errors made in requirements specifications are:
incorrect facts, omissions, inconsistencies, and ambiguities

Requirements errors can be detected


Rosziati Ibrahim BIT 3143/ BIT 31403 10

Potential Impact of Requirements Errors Not satisfy users need Disagreement between customers and developers, wasting time and resources Impossible to thoroughly test that the software meets its intended requirements Both time and money wasted building the wrong system
Rosziati Ibrahim BIT 3143/ BIT 31403 11

What is a Good Requirements Document?


Unambiguous Complete Include functionality, performance, design constraints, attributes/external interfaces Definition of the response of the software to all classes of input data in all situation Full labelling of tables, figures and diagrams Verifiable Consistent Modifiable Traceable Usable during operation and maintenance
Rosziati Ibrahim BIT 3143/ BIT 31403 12

Refresh your mind


http://www.iiis2011.org/iceme

Thank You

Rosziati Ibrahim

BIT 3143/ BIT 31403

13

Rosziati Ibrahim

BIT 3143/ BIT 31403

14