Describe sources of information

Assignment 1

The assignment will be evaluated according to the following:

Bikes Rental System

A bike rental company in Jeddah rents bikes to their clients. Usually, clients would come to the store and look for a suitable bicycle and then check its availability and rent it from the shop manager for some time for some cost. If the bicycle was returned after the time of rental has ended, the shop manager will charge the client a late fee. If the bike was not returned the client will be charged a lost bike fee. The process of registering clients and managing their rental information manually has made the processes inaccurate and slow. The shop owner wants a simple system for his shop for the shop manager to manage the client’s data.

Q1: Describe as many sources of information as you can think of, that should be consulted to perform a domain analysis for a Bike Rental System.

Q2: Define a possible scope for the Bike Rental System. First list a wide range of things that the system should do. Then narrow down the scope. To do this, select a minimal set of the most important features that you would implement in the first release of the system.

Q3: Give precise problem statement for the Bike Rental System. Remember to think high-level goals.

A high-level goal is the business benefit in terms of (cost, speed, and quality)

Examples:

• Increasing efficiency of work
• Maximizing sales
• Reducing cost
• Improving profitability
• Increasing user satisfaction

Q4: Describe the set of functional requirements that would solve the problem statement you devised in Q3 and that meet the minimal set of features you defined in Q2 as well as non-functional requirements that would be important for the quality of the system.

Note: The total of functional requirements has to be 5 at least but you should mention at least one functional requirement for all types of users of the system.

FUNCTIONAL REQUIREMENTS

1- High-level: “The system shall charge users credit cards for purchases”

2- Low-level: “The system shall validate all passwords contain upper and lowercase characters and one number”

3- Something a system must do

4- In general, a functional requirement is a “shall statement”

5- Should define one thing not multiple things

6- Should not be a design choice

7- Each requirement should have a unique number

NON-FUNCTIONAL REQUIREMENTS

1- Constraints on a software system

2- Often known as software qualities, or just the “ilities” e.g. development costs, operational costs, performance, reliability, maintainability, portability, robustness etc.