Information System Requirements Specification Document
1. Introduction
This section describes the organization/Department under study, its business and function.
This section describes the purpose of this report, and explains the new Information System very briefly, and notes if it is the whole system or part of a larger system.
This section describes how the processes are currently operated in the organization under study. It also explains the manual system, and the business processes currently in place.
This section describes the proposed new IS, and its associated business processes.
2. Analysis of the Existing System
Draw DFDs for the existing system.
Describe how data is currently captured, stored, processed and disseminated in the existing (manual) system (eg., forms, folders, cabinets, reports etc).
Explain the aim of the new IS. What you would like to achieve through the new IS which wasn’t achievable in the existing manual system. Who are the actors of the new system.
Draw the overall use case diagram followed by diagrams for all use cases.
Draw the overall DFD (also called context diagram) followed by diagrams for all DFDs as required.
Draw the ERD for your system using the notation introduced in the class (include entity names, attributes, PK/FK, relationship names, relationship types (connectivities)).
Provide the data dictionary for your ERD.
Draw the relational schema for your ERD.
Provide the text description of each user interface your new system has (eg, main menu, data entry forms, adding/editing/deleting etc). If you would like to include figures, you can insert in appendices.
List and explain various managerial reports (and queries) that your new IS is able to produce. Managerial reports are very important as they provide input which inform managers’ decisions. The more useful, and innovative your reports are, the higher your mark for this assessment (also the more the reports, the better). You can use the following sub-headings, if you want, to explain your reports in a more structured way:
This section explains your plan for implementing the proposed IS (final report and presentation due in week 11). It should include project schedule (eg, using Gantt chart, PERT, CERT, or at least a table listing activities/timing/persons assigned to do).
Appendix:
If you would like to include any text, figure, table as side information, you can inset here (example, user interfaces if you have already created).
2 Introduction
M&J chickens is a growing business in Sydney. It is located in the Marrickville. The business offers customers raw and cooked chicken. The customers are mainly shops, pubs, restaurants etc. Currently, they are using a manual process to take and process orders. That is leading to errors in the order processing system and poos customer service. The result is loss of and trust in the market. The customer service manager of M&J Chicken has decided to design, develop, and implement an online order taking system to automate the order collection process and to allow customers in accessing their dedicated customer portal and to take online payments.
The purpose of the system is to help the business in automating their order collection process and to make their workflow error-free. It will also help to improve the customer services and to retain customers. Other than that, the system will also help to reduce the staffing cost and staffs will be able to be more productive.
In the existing system, a customer comes in person or calls M&J Chickens to place an order or to inquire. There are six staffs who attends the calls and take orders manually. That is leading to dissatisfaction among the customers, errors in orders, and bad customer services.
The proposed new system is an online web based system. It will automate the order collection, online payment and customer service processes. It will introduce an order form, an inquiry form, and a customer portal. The order form will help to take orders online along with online payment. The inquiry form is there to allow the customers to send queries and the staffs may reply to the queries.
The customers will be able to set their collection date and delivery option. The business will deliver the orders to the customers.
The context diagram of the existing manual process is,
The data flow diagram of the manual process is,
In the existing system all data are handled using pen and paper. The order details are taken over the phone. The details of the customers, orders, products, stocks etc. are managed using manual data entry and data handling processes.
The proposed new information system will be a web based system that the users can access from their computers and / or mobiles. A customer needs to make a profile first. Then the customer will be able to place an order for raw or cooked chicken. The customers can check in real-time whether the order is accepted or not. If the order is not accepted then one of the staff will call and take care of the order. If the order is accepted, the customer will be redirected to a payment page and must pay for the order. Once the customer makes payment, the order confirmation number will be sent to the customer. The customer can use that for further reference to the order. The customer will provide information about collection or delivery of the order. The staffs will process and prepare the order and then either will keep that for collection or deliver to the customer’s address.
Customers can place an enquiry and staffs will reply to that. Other than that, customers can check their past order details and current order details from their customer portals.
The overall use case diagram is,
A New customer can create a profile. The system will save the profile details and generate a unique username for the customer. The customer can set his/her own password.
A registered customer can login using valid credentials like username and password and check his/ her profile. The customer can make changes in the phone number, address etc. of the profile.
A registered customer will be able to select an option to order. The catalog contains the details of the items, descriptions and the prices. It will also show information about whether the product is available or not.
A register customer gives order details and proceed to payment. The order details include, the unique order number generated by the system, data of order, items ordered, quantity of each ordered item, total price etc.
A registered customer places an order and makes payment using credit card. System will save the order details and forward it to the order processing staff. And system will return a confirmed order no. and the same order number will be used to prepare and deliver the order.
Once an order is confirmed, a customer can track order, system will response with the tracking details. There is an external system called ‘Logistic Company’ connected to the use case. It further expands the use case into two other use cases within the boundary of the ‘Logistic Company’. Those two use cases are,
4.2.7.1 Order Status
The user can check the status of an order by entering the order number.
4.2.7.2 Update Order Status
The system will automatically update the status of the order based on data collected from other actors and the process running within the system.
A registered customer can place a query, system will forward the query to a staff. Once a staff replies on it, the system will return the answer to the customer.
Manager will be able to generate reports under different conditions and requirements. The system will generate all reports.
A staff gets notification about new order and opens it to view the details. The staff will be able to see the delivery details and item details of the orders. The staff will also see the customer details for the order. The staff can communicate with the customer for the order if required.
The context diagram is,
The DFD 1 is,
The ER diagram is,
| Table | Attribute | Date type | Key |
| Customer | CustID | INT | Primary key |
| FullName | Text | ||
| Address | Text | ||
| Phone | Text | ||
| Text | |||
| CreditCard | Text | ||
| Staff | StaffID | INT | Primary key |
| FullName | Text | ||
| JoiningDate | Date | ||
| Role | Text | ||
| Product | ProdID | INT | Primary key |
| ProdDesc | Text | ||
| Stock | Boolean | ||
| UnitPrice | Decimal(5,2) | ||
| Order | OrderID | INT | Primary key |
| OrderDate | Date | ||
| NeedDelivery | Boolean | ||
| DeliveryDate | Date | ||
| StaffID | INT | Foreign Key | |
| CustID | INT | Foreign Key | |
| OrderLine | OrderID | INT | Primary key, Foreign Key |
| ProdID | INT | Primary key, Foreign Key | |
| Quantity | Decimal(5,2) | ||
| Payment | PaymentID | INT | Primary key |
| Amount | Decimal(7,2) | ||
| PaymentDate | Date | ||
| OrderID | INT | Foreign Key | |
| Query | QueryID | INT | Primary key |
| CustID | INT | Foreign Key | |
| Date | Date | ||
| Status | Text | ||
| Details | Text | ||
| StaffID | INT | Foreign Key |
Customer (CustID, FullName, Address, Phone, Email, CreditCard)
Staff (StaffID, FullName, JoiningDate, Role)
Product (ProdID, ProdDesc, Stock, UnitPrice)
Order (OrderID, OrderDate, NeedDelivery, DeliveryDate, StaffID, CustID)
OrderLine (OrderID, ProdID, Quantity)
Payment (PaymentID, Amount, PaymentDate, OrderID)
Query (QueryID, CustID, Date, Status, Details, StaffID)
Login Interface
Once a customer is logged in, the home page will be,
A customer can do any of the five functionalities. When a customer clicks on the ‘Place New Order’ button, then the next screen will be,
The customer will select product, quantity, and the delivery date. Then it will proceed to the next screen that is the payment screen.
Here, the customer will enter credit card details and can save the card for future. Once payment is made, there will be a popped up dialog box saying the order is confirmed and with an order number,
Once order is confirmed and payment is completed, within 3 minutes, the portal will be back to the home screen automatically. Within the time, the customer can note down the order ID for further reference.
From the home screen, a customer can select ‘Track order’ button and can track a confirmed order on the following screen.
Once the tracking details is shown. The customer can go back to the home menu again. From there, the customer can choose to ‘View Past Orders’ and will go to the next screen. From there a customer can come back to the home screen.
From the home screen, a customer can select to ‘Update Profile’ and update either address or phone number from the next screen.
Once completed, customer can go back to the home menu and may select to place a query. The next screen will be,
A customer can check FAQ while placing a query.
Manager will be able to generate a customer report, it will show the details of the customers. The manager can sort the report using different columns and may filter data. For example, a manager can ask to generate the report on the customers who have not placed any order yet.
Manager can generated order summary report sorted and filtered by different conditions.
A manager can produce the pending order report and distribute to the staffs.
Manage can generate a report containing the delivery details of the orders scheduled for delivery on the same date.
Manage can generate detailed sales report to assess performance of the sales department.
Login
Pages: 4
Words: 890