Information systems analysis and design exercise 1SE005

In this exercise you will test some of the modelling tools available in Object-Oriented systems development. Use cases are used in the information analysis while class diagrams could be used in business analysis, information analysis and in systems design. The sequence diagram is used in systems design. The exercise will be modelling a case company presented here below.

Better Bread AB (BBAB)

Owner: Family Cinnamon Share-capital: 250 000 SEK Turnover: 25 M SEK Employees: 10 bakers, 2 bread deliverers, 6 shop assistants, 2 sellers and 2 office employees. Sales: Directly to larger customers like ICA and Konsum (food stores), 3 own shops and through resellers. Customers: Around 200 customers, of them 25 large. The customers buying directly in the self owned shops are not included. Recipes: They have a large amount of recipes, describing the raw material use for a standard recipe and the time needed to produce the goods. Amount of recipes is about 200. Finished goods: Most products are delivered directly after the production to the customer. Some products, for instance gingerbread could be stored in finished goods storage. There are about 400 products total. Fleet of cars: 2 sedans and 2 lorries. Machinery: Up to date with a capacity that well meets the needs of the production. Office: Some technology for bookkeeping and invoice exists, no computers though. In the future computerised support would be needed. The supplier's ledger needs computer support directly. Salaries can be managed manually. Management: The production is led by two experienced bakers that know when its time to purchase raw material and how to plan the production. Deficiencies in raw material and delivery delays are reported to the office for action. Better Bread AB needs some computerised support for their businesses. They currently face big problems in keeping the delivery times, to control raw material use, production planning and so on.

Assignment 1: Choose a special part (problem) of the business you will look closer at. It could for instance be * the problem of deliver in time, especially when planning the lorries routing * the raw material use, how to keep track of that * the production planning, how to plan the actual production (this have impacts or is affected by the other two paragraphs) or another part you seem to find being of special interest. Check with Mirka first if you choose to work with your own problem. Make a Use case of the problem you described. Include all users (actors) that could be future users of the IT system that deals with the problem you face. Make a list of all users first and then another with all the basic functionality you would like the system to have. Put the users and functions in a matrix like below and find out whom will be using what functionality. Mark this with a dot or an X. Draw a graphical use case model out of this matrix. You need to describe briefly each use case too in text. Results: A user/functions matrix, a graphical Use case model and a textual description of each use case. Assignment 2: Make a class diagram describing all objects that are included in the special part of the business as described in assignment 2. To make the work a bit easier you could first make a process graph describing this restricted part of the company. Other ways to find the objects is to read the company description and identify objects from there. You could also use the results of the use cases (assignment 2) when you look for objects. The attributes and operations could be found in a similar way. Results: A class diagram describing the problem area. This class diagram will contain classes, relations between classes, attributes and methods connected to the classes. If some of the classes are hard to understand, give a short textual description of them too. Assignment 3: Create a sequence diagram corresponding to one of the use cases above. Result: A sequence diagram describing a use case.

Matrix example, maintenance system:

Report failure Create work order X X X X X Order spare part X X X X Report maintenance performance X etc.

Maintenance manager Technician Production manager Financial system Automatic alarm

Use case example, maintenance system:

Maintenance management Report failure

Automatic alarm

Maintenance manager

Create work order

Production manager

Order spare part Report maintenance performance Technician

Textual description example:
Name Short description Actors Triggers Result Essential process Report failure

Financial system

A failure on an equipment is to be reported into the maintenance management system. Technician, automatic alarm and production manager. The user creates a new report. A failure report has been stored. 1. Create new report that automatically will be assigned a number. 2. The user enters ID and the system assigns it as the signature. 3. The user search for equipment ID and location in the system. 4. Failure type, description and symptom is entered.

Class diagram example, maintenance system:

M EQ UIPM ENT Number Name Designation Downtime cost Location M is divided into 1 1 FAILURE ID Date Type Description Symptom M
is reported by

Sequence diagram example, maintenance system

User
Create report

consists of 1

is connected to is made on

1 JOB Type Priority 1 Status Periodicity Start time Expected finish time Time consumption Downtime Other work cost M M

is connected to

is divided into M

1 CATEG ORY Characteristic Type 1 1 is divided into M

PERSONNEL ID Name Hourly rate M is connected to 1 1 conducts is connected to N ARTICLE Number N ame Unit Purchase price Inventory placement Inventory balance Reorder point M is connected to 1

DOCUMENT Document name

1 is connected to

is divided into

COMPANY Name Address Phone Fax E-mail 1 M provides N

is divided into

Personnel Failure report

Assign number Date Get ID Reported by Get equipment, location Equipment ID, location Failure type Failure description Symptom

Equipment