IS226 Assignment 1 PDF

Preview

Summary

practice to increase your skills ...

Description

IS226 Systems Analysis and Design Project Case Study 3 Stock Management System Assignment 1

Project Team: InfoTech Team Members Team # L3 Reenal Rajni Lata

S11171280

Ranjini Naashna Goundar

S11171487

Stefannie Stacey Louis

S11171274

Contents 1.0 Introduction ...................................................................................................................................... 3 2.0 Functional Requirements ................................................................................................................... 4 2.0.1 List of Functional Requirements.................................................................................................. 4 3.0 Non-functional Requirements ............................................................................................................ 5 3.0.1 Usability...................................................................................................................................... 5 3.0.2 Reliability .................................................................................................................................... 5 3.0.3 Performance ............................................................................................................................... 5 3.0.4 Implementation .......................................................................................................................... 5 4.0 Event Table........................................................................................................................................ 6 5.0 Data Modeling: Entity Relationship Diagram ...................................................................................... 7 5.1 Data Dictionary .............................................................................................................................. 7 5.2 Entity Relationship Diagram ........................................................................................................... 9 6.0 Structured Analysis .......................................................................................................................... 10 6.1 Context Diagram .......................................................................................................................... 10 6.2 Diagram 0 (Event-Partitioned System Model)............................................................................... 11 6.3 Diagram 1 .................................................................................................................................... 12 6.4 Process Descriptions .................................................................................................................... 13 6.5 Data Flow and Data Element Descriptions .................................................................................... 14 7.0 Conclusion ....................................................................................................................................... 15 8.0 References....................................................................................................................................... 16 9.0 Appendix ......................................................................................................................................... 17 4.0 Event Table ................................................................................................................................. 17 5.0 Entity Relationship Diagram ........................................................................................................ 17 6.1 Context Diagram.......................................................................................................................... 17 6.2 Diagram 0.................................................................................................................................... 17 6.3 Diagram 1.................................................................................................................................... 17

2

1.0 Introduction Necessity is the mother of invention. Stock management System is one aspect of the business that improves the business performance. It is necessary for business organizations to keep track of its daily records for smooth operation and to avoid inconsistencies in the day to day running.

Pacifica Computer Solutions (PCS) is a business selling computer parts but it uses a manual inventory record system which causes difficulties in keeping updated records for its clients. It is inefficient and time consuming as the number of users are increasing the need for computerized more efficient system is needed. Also, it is not economically and technically feasible to keep records on paper.

Hence, Pacifica Computer Solutions (PCS) approaches InfoTech for a new information system where my group is given the task of a systems analyst. The main purpose for a new system is to ease workflow and to produce reports for decision making on time.

3

2.0 Functional Requirements Functional requirements describe the basic system behaviour. It is what the system wants to do and not to do, it can be thought of in terms of where the system decides how to responds to inputs. Few examples include: data inputs, calculations and business processes (QRA, 2019). The diagram below illustrates a simple process of the system:

Input

System Behaviour

Output

These requirements are structures that helps the system to function as it was designed. In simple terms, if functional requirements are not encountered, the system will stop working. Therefore, functional requirements focuses on user requirements and are product features.

2.0.1 List of Functional Requirements  Enable the sales person to enter customer details and item details for warranty purpose.  Allow the system to update records of its clients.  Allow technician to create job sheet which records date & time of job commencement and completion.  Print invoice which provides customer details, item details, date of sale and total amount payable by customer.

4

3.0 Non-functional Requirements Nonfunctional requirement is a specification that describes the systems' operation and are often called technical or operating specification. The attributes of non-functional requirements serve as restrictions or constraints on the design of the selective system across the altered backlogs (Jada, 2019) .Non-Functional requirements attributes are as follows:

Non-functonal Requirement

Usability

Reliability

Performance

Implementation

3.0.1 Usability 

The system must be easy to use and accessible by the intended users.



The system must display all relevant data and reports.



The system interface must be simple for understandability.

3.0.2 Reliability 

Must efficiently update parts at hand whenever parts are sold to customers.



Must warn early if stock is running low.



Must successfully enter new item details (number) and update stock.



Produce a report alerting when stock is lower than the threshold level.

3.0.3 Performance 

System must enable managers to review the list of suppliers.



Must enable managers to enter new supplier selling computer part details at a lower rate such as supplier name, address and phone contact.

3.0.4 Implementation 

Microsoft Visual Studio 2010 was used to build the system user interface.



The Programing is done in Microsoft Visual Studio 2010.



The connection between the Database and the System is achieved using Open Database Connectivity (ODBC) connection available at hand in Visual Studio 2010. 5

4.0 Event Table Event Salesperson creates order

Trigger New customer

2

Technician creates job sheet

New job

3

Technician wants to enter new item

4

Manager wants to order parts from his suppliers Manager wants to review the list of suppliers The manager wants to print the productivity report

1

5

6

Source Use Case Salesperson Record customer details Technician Record job details

Response Print invoice

Destination Salesperson

Stock update

Technician

New item

Technician

Record item number

Confirmation on computer stocks

Technician

New item

Manager

Produce report alerting

Confirmation notification

Manager Supplier

List of suppliers

Manager

Update supplier details

Job sheet

Manager

Manager removes inactive suppliers Gather reports Complied productivity report

Manager Supplier

Manager

6

5.0 Data Modeling: Entity Relationship Diagram 5.1 Data Dictionary Table Name

Attribute Name

Customer

Cus_ID Cus_LName Cus_FName Cus_Ph Cus_PO

Order

Item Details

Inventory

Job sheet

Contents

Type

Format

Range

Required

PK or FK

FK Referred Table

1000099999

Y Y Y Y

Pk

Order

Fk Pk

Customer

Pk

Order

CHAR(5) VARCHAR(15) VARCHAR(15) CHAR(8)

99999 Xxxxxx Xxxxxx 999-9999

VAR(5)

9999

Ord_ID Ord_Date

Customer ID Customer last name Customer first name Customer phone number Customer postal address Order ID Order Date

CHAR(5) DATE

99999 dd-mm-yyyy

Y Y

Cus_ID SalesPer_ID Item_Num Item_Name Item_Num Item_Desc Qty_Sold Unit_Price Qty_Sold Stock_onhand Inventory_Num

Customer ID Sales person ID Item Number Item Name Item Number Item Description Quantity Sold Unit Price Quantity Sold Stock on Hand Inventory Number

CHAR(5) CHAR(5) DECIMAL(8) CHAR(8) DECIMAL(8) CHAR(10) DECIMAL (> 0) DECIMAL($) DECIMAL (> 0) CHAR(8) NUMBER(20)

9999 9999 99999 Xxxxx 99999 Xxxxxx 99999 99999 99999 Xxxxx 99999

Y Y Y Y Y Y Y

Y

Pk

J_Number J_Date J_Time J_Commen J_Compl

Job Number Job Date Job Time

NUMBER(7) DATE TIME CHAR(8) CHAR(8)

99999 dd-mm-yyyy 2400 Xxxxx Xxxxx

Y

Pk

Job Commencement

Job Completion

Y

Item Details

Inventory

Y Y

7

Purchases

Invoice

Supplier

S_Order S_Details S_invoice T_Card Item_Num Cus_details Item_details D_ofSales T_amount payable Inv_Num

Sales Order Supplier details Supplier invoice Time card Item Number Customer details Item description Date of sale Total amount payable Invoice Number

CHAR(5) CHAR(10) VARCHAR(20) DATE DECIMAL(8) CHAR(10) CHAR (10) DATE NUM (20)

Xxxxx Xxxxx Xxxxx dd-mm-yyyy

NUM(20)

99999

S_Name Phone_Num Address Regional D_Sales

Supplier Name Phone Number Address Regional Date of sale

CHAR(10) NUMBER(8) CHAR(8) CHAR(8) DATE

Xxxxx 99999 Xxxxxx Xxxxx dd-mm-yyyy

Xxxxx Xxxxx dd-mm-yyyy 99999

Y Y Y Y Y Y Y

Pk

Job sheet

Pk Purchases

Y Y Y Y

Pk

Invoice

Key: Fk: Foreign key Pk: Primary Key CHAR: Fixed character length data VARCHAR: Variable character length data NUMBER: Numeric data

8

5.2 Entity Relationship Diagram

9

6.0 Structured Analysis 6.1 Context Diagram

The above context diagram shows the interaction of users with the system, the various inputs and outputs.

10

6.2 Diagram 0 (Event-Partitioned System Model)

More detailed then the context diagram and is showing detail view of the stock management system inventory processes.

11

6.3 Diagram 1

Order

Supplier

]

Process 6 from Diagram 0 was opted and further discussed into sub processes making it easier for the analyst to analyze and improve the areas that needed more attention.

12

6.4 Process Descriptions Sales person creates order for new customer Record customer details Print invoice Repeat for each new order If new job Then technician creates job sheet Update stock and job details Or record item number Then enter new item Receive confirmation on computer stocks Produce report alerting If manager wants to order parts from his suppliers Then send confirmation notification Manager wants to review the list of suppliers Review list of suppliers Update suppliers’ details If there are new potential suppliers Add them If there are inactive suppliers Remove them The manager wants to print the productivity report Gather reports Produce a compiled productivity report End of all procedures

13

6.5 Data Flow and Data Element Descriptions New item Item Name: character code of fixed length of 8 Item Number: decimal values from 0 - 9 Item Description: character code with fixed length of 10 Quantity Sold: decimal values more than 0 Unit price: decimal values in FJD ($)

List of suppliers First Name: text field with max size of 15 Last Name: text field with max size of 15 Phone Number: numbers with fixed length of 7 Address: character code and number with max length of 8 Regional: character code with max length of 8 Date of sales: Date (DD.MM.YYYY)

Job sheet Job Number: numbers with fixed length of 7 Date: Date (DD.MM.YYYY) Time: Numbers (00.00) Job commencement: character code with max length of 8 Job completion: character code with max length of 8

14

7.0 Conclusion In summation, the best suitable information system to meet the desired needs of PCS was designed. This new system will update parts after every sales and purchases efficiently. It is recommended that the system is tested every month to inspect if it's operating as it should. Hence, with the new changes in PCS, it is expected that there will now be less problems and the company benefits from the computerized operations.

15

8.0 References Jada. (2019). Altexsoft. Retrieved from https://www.altexsoft.com/blog/non-functional-requirements/ QRA. (2019). Functional vs Non-Functional Requirements. Retrieved from https://qracorp.com/functional-vs-non-functional-requirements/

16

9.0 Appendix 4.0 Event Table- refers to a database table created by the user to store, retrieve and process events. 5.0 Entity Relationship Diagram – it shows the relationship of entity stored in databases. 6.1 Context Diagram – it shows the basic system processes from one entity to the other. Thus, it depicts the overall result of the new system that will be designed for the computer system. 6.2 Diagram 0 – it shows a data system as a whole and highlights the way it relates with external entities. 6.3 Diagram 1- is more detailed than Diagram 0 as it discontinuities the main processes into sub processes that can then be analyzed and improved.

17

Assignment 1: Mark Allocation Sheet After having discussed as group, we recommend the following mark allocation to each group member based on contribution or lack of it throughout the project.

Group number ________L3_________________ Project manager Reenal Rajni Lata

Member ID

Percentage of final points

S11171280 S11171487 S11171274

Signed Member name

ID

Reenal Rajni Lata

S11171280

Ranjini Naashna Goundar

S11171487

Stefannie Stacey Louis

S11171274

Signature

18...