how the system

Property of STI IT1814

Image sources:https://i1.wp.com/michaellant.com/wp-content/uploads/2010/05/WhatTheCustomerWanted.jpg

https://www.redirontech.com/wp-content/uploads/2016/01/Failed.jpg

How the project team planned the

system

How the programmer(s)

wrote it

How the system was tested

How the system was installed.

What the customer really needed.

Requirements Analysis and Modeling

q Requirements Determination

q Requirements-Gathering Techniques

q Requirements Analysis

q Modeling with Unified Modeling Language (UML)


Phas

e

AnalysisPlanning Design Implementation

https://www.drain1.ca/wp-content/uploads/2018/01/flat-faces-icons-circle-3.pngSystems Analyst

Analyze requirements

Gather requirements

Model the user needs

Create system blueprints

Requirements Determination




Requirements

Functional Requirements

Non-Functional Requirements



Functional RequirementsExamples: A customer shall be able to search item

by typing a keyword in the search box.

The system shall be able to generate financial statements.

The administrator shall be able to add a new user.



Non-Functional Requirements

Operational requirements

Performance requirements

Security requirements

Cultural and political requirements



Systems Analysts or Project Team

Requirements Definition Report

Requirements Definition Report

Create requirements specification report

Create model of requirements

Analyze requirements

Gather requirements



• Revision History1. Introduction

1.1. Document Purpose1.2. Product Scope1.3. Product Overview1.4. Definitions

2. References3. Specific Requirements

3. 1. Functional Requirements3. 2. Non-functional Requirements

3.2.1. Operational Requirements3.2.2. Performance Requirements3.2.3. Security Requirements3.2.4. Cultural Requirements

4. Verification5. Appendixes

Example outline

Many companies employ standard templates from the following:

https://commons.wikimedia.org/wiki/File:ISO_Logo_(Red_square). svghttp://www.ieeespskolkata.org/assets/img/ieee.png

International Organization for Standardization

Institute of Electrical and Electronics Engineers


Group Activity

Material: 02 Seatwork 1

Instruction: Analyze each requirement in BOX A, whether it is a functional requirement or non-functional requirement, then place the requirement in the appropriate category in BOX B.


Requirements-Gathering Techniques

Systems Analysts or Project Team

Requirements

Commonly used techniques:Interviews JAD sessions

Questionnaires Document analysis

Observation



Interviews

Design interview questions

Select interviewees

Prepare for the

interview

Conduct the

interview

Post-interview follow-up



Joint Application Development (JAD) Session

Design JAD

session

Select participants

Prepare for the

session

Conduct the JAD session

Post-JAD follow-up



Questionnaires

Design questionnaire

Select participants

Administer the

questionnaire

Questionnaire follow-up



Document Analysis

Analyze Interpret and create report



Observation

Observe Take notes Analyze behaviors


Group Activity


Instruction: Suppose your team is in charge of developing a new system for ABC Hotel. Develop interview questions that will help you with gathering information from the employees regarding process of the hotel. Include the position of the employee you will interview.



Table 1. Table of characteristics of requirements-gathering techniquesSource: Systems Analysis & Design. An Object-oriented Approach with UML (5th ed.), 2015. p. 108

Interviews JAD Session QuestionnairesDocument Analysis

Observation

Type of informationAs-is, improvements,

to-beAs-is, improvements,

to-beAs-is,

improvementsAs-is As-is

Depth of information High High Medium Low Low

Breadth of information Low Medium High High Low

Integration of information Low High Low Low Low

User involvement Medium High Low Low Low

Cost Medium Low to Medium Low Low Low to Medium


Group Activity


Instruction: Suppose your team is in charge of developing a new enrollment system for a local school. The school is having difficulty finding enough slots in courses for students. What requirements-gathering techniques will you use? Describe in detail how you would apply your techniques.


Analyzing a

Requirements Analysis

Requirement

Characteristics of a good requirement

Necessary

Unambiguous

Consistent

Complete

Singular

FeasibleVerifiable

Traceable



Characteristics of a good requirement:

Necessary

REQ001 – The student shall log in to the system by providing his/her student number and password and by scanning his/her fingerprint.

Bad

REQ001 – The student shall log in to the system by providing his/her student number and password.

Good




Unambiguous

REQ001 - The system shall automatically refresh the databases quickly.

Bad

REQ001 - The system shall automatically refresh the databases within 0.5 seconds.

Good




Consistent

REQ001 – The system shall accept PayPal payment.REQ002 – The system shall accept only credit card payments.

Bad

REQ001 – The system shall accept PayPal payment.REQ002 – The system shall accept credit card payments.

Good




Complete

REQ001 – The employee shall log in to the system by providing his/her relevant information.

Bad

REQ001 – The employee shall log in to the system by providing his/her username, password, and department code.

Good




Singular

REQ001 – The registrar shall be able to enroll a student to an undergraduate course and drop that enrolled undergraduate course.

BadREQ001 – The registrar shall be able to enroll a student to an undergraduate course.REQ002 – The registrar shall be able to drop a student from his/her enrolled undergraduate course.

Good




Feasible

REQ001 – The employees shall log in to the system by examining his/her deoxyribonucleic acid (DNA).

Bad

REQ001 – The employees shall log in to the system by scanning his/her fingerprint.

Good




Verifiable

REQ001 – The user interface of the system shall be user friendly.

BadREQ001 – The system shall display the current total enrolled students on the dashboard page every two (2) seconds.REQ002 – The user interface of the system shall use the Arial font.

Good



Using Requirements Checklist


Group Activity


Instruction: Using the provided checklists, analyze the two (2) requirements on Table 1. Provide explanations if the requirement did not satisfy the specified characteristics. Restate the requirement if possible.


S u b j e c t

Modeling with Unified Modeling Language (UML)

https://upload.wikimedia.org/wikipedia/commons/thumb/d/d5/UML_logo.svg/1280px-UML_logo.svg.png

• Provides visual means for systems

• Use for modeling software and

systems

A c t o r

U s e C a s e

U s e C a s e

The Use-Case Diagram


Modeling with Unified Modeling Language (UML)Components of use-case diagrams:

A c t o r / R o l e

U s e C a s e

S u b j e c t< < i n c l u d e > >

< < e x t e n d > >

< < a c t o r > >A c t o r / R o l e

Actors Use-case Subject boundary box Relationships


Modeling with Unified Modeling Language (UML)

Identify major use-cases:

Step 1. Review requirements definition report

Step 2. Identify subject’s boundaries

Step 3. Identify primary actors and goals

Step 4. Identify business process and majoruse-cases

Step 5. Review current set of use-cases

Creating use-case diagram:

Step 1. Place and draw use-casesand their relationships

Step 2. Place and draw actors

Step 3. Draw subject boundary

Step 4. Add associations


Patient Manage Appointment

< < e x t e n d > >

< < a c t o r > >CAPTCHA

Recognition Service

Make New Appointment

Cancel Appointment

Change Appointment

Manager

Produce Schedule

Check Daily Schedule

Print Daily Schedule

Doctor

Update Schedule

Authenticate User

Authenticate Patient

Authenticate Employee

Verify User using

CAPTCHA

< < e x t e n d > >

< < e x t e n d > >

< < e x t e n d > >

< < e x t e n d > >

< < i n c l u d e > >

< < i n c l u d e > >

Appointment System

Step 1 Step 2. Step 3 Step 4 Figure. Example use-case

diagram for an appointment system


Group ActivityMaterial: 02 Seatwork 5

Instruction: Read and analyze the given scenario then perform the following:

1. Identify the functional requirements;2. Identify the subject boundary;3. Identify the primary and secondary actors and their goals;4. Create use-cases for every identified goals; and5. Create a use-case diagram based on identified functional requirements

and use-cases.


Generalization

• Key takeaways

• Points to consider when developing a project


Group Assignment

Material: 02 eLMS Activity 1

https://cdn2.vectorstock.com/i/1000x1000/04/21/teamwork-people-top-view-vector-3130421.jpg

eLMS


Evaluation of Case Study

• Case study for Prelim period will be evaluated using the given Grading Rubric for Case Study.

how the system

Documents