Requirement Analysis

Didik Dwi P didik@um.ac.id

Bahasan Requirement engineering Requirement analysis Fact-finding techniques Business Requirement Specification (BRS)

System Analysis Phase Overview System analysis phase tasks: Requirements Process Modeling Data Modeling Transition to Systems Design

What are requirements? Functional expectations Performance expectations Constraints

System (existing, legacy) Environmental Cultural etc

Requirement Engineering

Requirement Engineering

Requirement Determination

Requirement Analysis

Basis for discussions with customer

Design basis for developers

Requirement Engineering Requirement Engineering covers all of the activities involved in discovering, documenting and maintaining a set of requirements for a computer-based system (Sommerville) Requirements engineering is an activity that involves capturing, structuring and accurately representing the clients requirements in a manner that can be effectively implemented in a system that will conform to the clients specifications (Sawyer)

Requirement Engineering Why requirement engineering is important? In software development projects, the Requirements Engineering Process (REP) can influence the development:
Cost Time Effort Quality

Major causes of project failures:

Incomplete requirements Changing requirements
7

Requirement analysis Other names:

Definition phase

Input:
System improvement objectives Project charter

Output:
Business Requirement Statement (BRS)

Most techniques used

Fact-finding

Requirement analysis A system requirement is a characteristic or feature that must be included in an information system to satisfy business requirements and be acceptable to users.
Inputs Outputs Processes Performance Controls

Requirement analysis Functional requirement: something the information system must do

Print invoice, read employee records, etc

Nonfunctional requirement: a property or quality the system must have

Cost Performance Security etc

10

Criteria for System Requirements Consistent not conflicting or ambiguous. Complete describe all possible system inputs and responses. Feasible can be satisfied based on the available resources and constraints. Required truly needed and fulfill the purpose of the system. Accurate stated correctly. Traceable directly map to functions and features of system. Verifiable defined so can be demonstrated during testing.
11

Requirement example The system must provide log-on security at the operating system level and at the application level Response time must not exceed four seconds An employee record must be added, changed, or deleted only by a member of the human resources department The system must support 50 users online simultaneously The transaction report should be generated every day at 10 pm The system must user-friendly to every type of users
12

Fact-Finding Techniques Fact-finding is the formal process of using research, interviews, sampling, questionnaires, and other techniques to collect information about systems, requirements, and preferences
also known as information gathering or data collection

13

Fact-Finding Techniques Sampling of existing documentation, forms, and databases. Research and site visits. Observation of the work environment. Questionnaires. Interviews. Prototyping. Joint requirements planning (JRP).

14

Sampling Existing Documentation Sampling process of collecting a representative sample of documents, forms, and records. Organization chart Memos and other documents that describe the problem Standard operating procedures for current system Completed forms Manual and computerized screens and reports Samples of databases Flowcharts and other system documentation And more
15

Research and site visits Research Computer trade journals Visit other companies with similar problems

16

Observation Observation a fact-finding technique wherein the systems analyst either participates in or watches a person perform activities to learn about the system. Advantages
Data gathered can be very reliable

Disadvantages
People may perform differently when being observed

17

Questionnaires Questionnaire a special-purpose document that allows the analyst to collect information and opinions from respondents. Advantages
Often can be answered quickly Relatively inexpensive way to gather data from a large number

Disadvantages
No guarantee that an individual will answer all questions Cannot observe body language

18

Questionnaires Multiple-choice questions Rating questions Ranking questions

Rank the following transactions according to the amount of time you spend processing them. ___ % new customer orders The implementation of quality discounts would ___ % order cancellations cause an increase in customer orders. ___ % order modifications ___ Strongly agree ___ % payments ___ Agree ___ No opinion Is the current accounts receivable ___ Disagree report that you receive useful? ___ Strongly disagree ___ Yes ___ No 19

Interview Interview - a fact-finding technique whereby the systems analysts collect information from individuals through face-to-face interaction. Advantages
Give analyst opportunity to motivate interviewee to respond freely and openly Can observe nonverbal communication

Disadvantages
Time-consuming Success highly dependent on analyst's human relations skills
20

Prototyping Discovery prototyping the act of building a smallscale, representative or working model of the users requirements in order to discover or verify those requirements. Advantages:
Can experiment to develop understanding of how system might work May minimize time spent on fact-finding

Disadvantages:
Developers may need to be trained in prototyping Could extend development schedule
21

Joint Requirements Planning Joint requirements planning (JRP) a process whereby highly structured group meetings are conducted for the purpose of analyzing problems and defining requirements. Participant:
Sponsor Facilitator Users and Managers Scribes IT Staff

22

Joint Requirements Planning Joint requirements planning (JRP) a process whereby highly structured group meetings are conducted for the purpose of analyzing problems and defining requirements. Participant:
Sponsor Facilitator Users and Managers Scribes IT Staff

23