ISYS2452-Business Analysis and Design 2
Assignment 2

Content
1. Introduction 4
1.1 Purpose of the project 4
1.2 Document Conventions 4
1.3 Intended Audience and Reading Suggestions 4
1.4 Project Scope 4
2. Overall Description 5
2.1 Product Perspective 5
2.2 Product Features 5
2.3 User Classes and Characteristics 6
2.4 Operating Environment 6
2.5 Design and Implementation Constraints 7
2.6 User Documentation 7
2.7 Assumptions and Dependencies 7
3. System Features 8
3.1 Restricted Access 8
3.2 Simple User Interface with Accompanying Help Files 8
4. External Interface Requirements 8
4.1 User Interfaces 8
4.2 Hardware Interfaces 8
4.3 Software Interfaces 9
4.4 Communications Interfaces 9
5. Other Non-functional Requirements 9
5.1 Performance Requirements 9
5.2Safety Requirements 9
5.3 Security Requirements 9
Appendices 11
Appendix A – Actor and Overall Use Case Diagrams and Extended Use Cases 11
Actors Use Case Diagram 11
Overall Use Case Diagram 12
Extended Use Cases 13
Appendix B – Package Diagram 16
Appendix C – Class Diagram 14
Appendix D – Detailed Class Definitions 15
Appendix E – State Diagrams 17
State Diagram for Purchase Order 17
Appendix F – Sequence Diagram for Major Use Case 15
Sequence Diagram for Purchase Order 15

1. Introduction

1.1 Purpose of the project

RMIT has continued the process of designing the system for Basketcase. To achieve this, the system had to be analysed further. The purpose of the project is to create a Unified Modelling Language requirements specification document for the system, design an efficient purchasing and distribution effectively. This is the next stage after completion the Soft Systems Analysis. The appendices of this report include the requirements specifications. RMIT is confident that Basketcase will continue to take advantage of the services that they offer and have included the requirements specifications for approval.

1.2 Document Conventions
Acronym that we have used in our specifications is BC means Basketcase.
The appendices we have used:
Appendix A–Actor and Overall Use Case Diagrams and Extended Use Cases
Appendix B– Package Diagram
Appendix C – Class Diagram
Appendix D – Detailed Class Definitions
Appendix E – State Diagrams
Appendix F – Sequence Diagram for Each Major Use Case

1.3 Intended Audience and Reading Suggestions

This document is written for the CEO of Basketcase who is in charge of the company; also the Manufacturing Department who will interact with this system will read this document as well. This document includes appendix, which should be read together with the report.
1.4 Project Scope

The system for efficiently process of sales and it allows Basketcase employees (Manufacturing Department) to manage their activities and performance in order to increase efficiency and improve the quality of their work. The Manufacturing Department will be able to carry out their responsibilities to process purchase and distribution of raw materials. The manufacturing department will be able to get accurate information about expected raw materials needs base on current month and long term trend. To ensure these requirements can be implemented, the following must occur:
Detailing the use cases,
Identifying the packages required for these use cases,
Creating a class diagram,
Creating detailed definitions for the classes identified,
Creating state diagrams for classes with complex states, and
Creating sequence diagrams for the use cases.

2. Overall Description

2.1 Product Perspective

The new system that has been proposed by RMIT will be extremely beneficial to Basketcase. The functionality will be focused on purchasing and distribution efficiency of the manufacturing department.

The system will be responsible for:
Making report for material used
Making report for delivered materials
Record raw materials used
Checking delivered materials
Checking quote for materials
Placing order for raw materials