Information Systems

In this assessment, you will design and code a Java console application that validates the data entry of a course code (like IT4782) and report back if the course code is valid or not valid. The application uses the Java char and String data types to implement the validation. You can use either the Toolwire environment or your local Java development environment to complete this assessment.

Your program output should look like the sample output provided in the “Validate User Input Using Java Chars and Strings Instructions” course file resource. Full instructions for successfully completing this assessment are included in this resource. Use the submission template (WeekXSolutionSubmissionTemplate.docx).

Your assessment will be scored on the following criteria:

  1. Design a program that meets char and String processing requirements.
  2. Code an application that validates data entry.
  3. Test the application and document that testing.
  4. Explain the approach taken to complete data validation and the major decisions made.
  5. Identify relevant fundamental constructs in a submitted program.

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 1

    Sample Case Study Please note that this is just a sample case study. The models provided are just examples and

    do not cover all case aspects. For example, the event table, it only covers some key events,

    physical data dictionary is only for one data store….. these sample models should provide

    you with a general idea to help you complete your assignments.

    Acme Garage Lilydale—Case Description

    The Acme Garage specialises in repairing cars. The owner is Geoff who has worked in the field

    for many years and owns 3 garages around Victoria. There are 30 full time and part time employees

    currently working in his business. In the Lilydale location, there is Mary and Kim, who look after

    customer enquiries, maintain (Create, Retrieve, Update, Delete) customer profiles, generate

    customer invoices, process invoices and payments. Bill and Ben are car mechanics. Peter looks

    after the ordering processes.

    When customers come to have their cars repaired, their initial contact is with Kim or Mary. Before

    Kim or Mary accept their requests, they check the database system to ensure any previous work

    that the customer has requested has been paid for satisfactorily. This can be generated by their

    current computer system (when customer’s car registration number is entered into the computer,

    the system will provide relevant feedback). If there are outstanding payment issues with the car

    registration number, the customer will be required to pay all outstanding bills before their new

    requests are accepted. Customer details are kept in a Customer file and details of each job are kept

    in a Job file under car registration numbers. If all is ok, Kim or Mary will accept the vehicles and

    pass the jobs to the mechanics: Bill and Ben.

    They will check the car and identify problems, parts required and estimated completion time. They

    will need to complete forms which include all relevant information and forward to Kim or Mary

    who will check the lists and calculate the cost. They will then call the customer for confirmation.

    If customers agree, Mary or Kim will notify the mechanics to go ahead and repair the car. After

    the job is completed, labour hours and parts used are recorded in the Job file. The mechanics will

    notify Mary or Kim, who will prepare invoices and call customer to collect the cars. Customers

    can pay when they pick up the cars or within 30 days. Reminder emails will be sent to customers

    a week before the due date. If payment is not made within 30 days, the follow up emails will be

    sent to customer advising of a 10% penalty. At the end of every week, computer systems will

    generate reports, e.g., Jobs and used parts, Customer Payment report…

    Acme need to keep stock of frequently used parts (e.g., spark plugs, oil filters, air filters) which

    are purchased regularly from suppliers. Acme’s suppliers are mainly local, however for some

    special parts for expensive cars, they also purchase from overseas suppliers. The computer system

    will monitor the stock level automatically. For those parts from local suppliers where the inventory

    level drops down to quantities of 3, then notification will be sent to Peter, who supervisors the

    ordering processes. Peter has to contact suppliers and lodge a replacement order. However, for

    those parts from overseas suppliers, the notification will be sent when the inventory level drops to

    quantity of 5. Less frequently used parts are ordered as required. Once they have a reliable supplier,

    they tend to stick with them, so they only ever have one supplier for each part. Supplier details are

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 2

    recorded and filed in the database. In the case where stock is ordered, details of the order are

    recorded in the Order file. Peter works in the office and maintains the ordering processes. All parts

    are recorded in the database ‘Parts’ file. The parts database should be identified to the supplier

    allowing Peter to create, add, update, delete and modify both supplier and part tables. If ordered

    parts haven’t arrived within 10 days, the system automatically notifies Peter, who will contact

    suppliers immediately. The computer system will generate several reports by end of each month,

    e.g., ordering parts with the suppliers, delivered orders, an unpaid invoice report and an unfilled

    orders report. These reports will be sent to the Acme’s owner Geoff.

    A copy of all orders is stored in an Order file, where invoices and parts are checked against the

    goods received and are then attached to the order. If everything is correct, Peter will update the

    order and stock details on the system. He will then pass the invoices, (including the cost of the

    parts) to Mary or Kim who look after accounting and payments.

    Mary or Kim will pay the invoices within 10 days after the delivery. If invoices haven’t been paid

    in 10 days, the auto notification will be sent to their email to remind them that the orders are

    outstanding. At the end of the month, the system will generate reports on invoices paid during the

    month, the parts list which details the names of the parts, quantities, single costs and total costs.

    Most of the data entry involves simple business transactions (recording customer information, job

    information, parts information, supplier information, managing orders, receiving payments and

    making payments). As mentioned previously, a variety of information is extracted from the system

    through enquiries and the generation of periodic reports. This information is used by Geoff, the

    owner of the garage, to manage the business.

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 3

    Event Table and Use cases

    Event Trigger Source Use cases Response Destination

    External Customer makes enquires on fixing cars

    Customer sent car service enquires

    Customer Manage Car Servie Enquires

    Customer payment stutas checked; Customer informed

    Customer

    Cutomer request quote for fix cars

    Customer sent car service enquires

    Customer Organize Car Service Car issues identified; Quotes issued; Notified customer

    Customer

    Cutomer agrees to fix cars Customer put request to continue fix cars

    Customer Fix Car Car fixed; notification sent to customer; a copy of job done list sent to accountant.

    Customer

    Customer wants to pay bill

    Customer pick up cars; Customer want to pay outstanding bills

    Customer Organize Customer Car Service Payment

    Invoice issues; overdue notification sent; service charges paid and confirmed

    Customer

    Suppliers send invoice Suppliers Suppliers Process Purchase Payment

    Invoice checked and paid Suppliers

    Customer updates informaiton

    Customer enquires

    Customer Update customer information

    Customer information updated

    Customer

    Mamagement or other managers needs reports immidiately

    Management or managers requests

    Managers, Geoff or other relevant staff

    Generate Reports fulfilled reports Management; Geoff; Relavant staff

    Temporal Time to generate Jobs and used parts lists; customer payment reports (weekly reports)

    Time (at the end of week)

    System auto generated

    Generate Weekly Reports reports generated and sent Management; Geoff; Relavant staff

    Time to generate monthly reports, such as Parts ordering report, delivered orders, unpaid invoice, unfilled orders report..

    Time (at the end of each month)

    System auto generated

    Generate Monthly Reports

    reports generated and sent Management; Geoff; Relavant staff

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 4

    send overdue customer payment notification to customer

    30 days overdue System auto generated

    Process cusomter payment

    notification sent Customer

    notify overdue payment to supplier

    10 days after parts received

    System auto generated

    Process Purchase Payment

    notification sent; payment organized

    Mary or Kim; Suppliers

    State order stock System notify the stock level below the limits

    System auto generated

    Fulfil Orders stock ordered; Peter, supplier

    Above just some examples, you may add more into the table.

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 5

    Data Fragments

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 6

    Context Diagram

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 7

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 8

    Level 0 DFD

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 9

    Levels 1 & 2 DFD Layer

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 10

    Level 1 DFD Organize Payment

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 11

    Level 2 Diagram of Organize supplier payment.

    Supplier

    4.2.1

    Provide Notice 10 Days elapsed,No Payment

    4.2.2

    Check the supplier Invoice

    Supplier Invoice

    4.2.3

    Make a Payment

    Payment Confirmation

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 12

    ERD

    Customer Customer Invoice

    Services

    Parts Mechanic

    Supplier Invoices

    Supplier

    Customer IDPK

    Cus_fName

    Cus_LName Cus_ Address Cus_ Phone Mobile Number Car Registration

    Invoice_ IDPK

    Customer ID Service ID

    FK

    Cus_fName Cus_Lname Car Registration Number Services_ Des Total Cost

    Service_IDPK

    mechanic_ID

    Service descrition Quoat

    Part _IDPK

    Supplier_ID Service_ID

    FK

    Supplier Name Part_Des

    mechanic_IDPK

    Service_IDFK

    mechanic_Name Date availebility Speciality

    Invoice_IDPK

    Supplier_IDFK

    Total Price

    Supplier_IDPK

    Supplier_Name

    Address

    Has Knowledge

    Need

    Provide

    Has

    attribute namePK

    Has

    Includes

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 13

    Physical Data Dictionary Example – (Data store Customer)

    Attribute Name Format Type Size Deacription

    Customer ID 000-000-000-0 Number 10 Primary Key Must be unique “mandatory”

    Cus_fName Character 45 First name “mandatory”

    Cus_LName Character 45 Last name “mandatory”

    Cus_ Address Unit No, Street No, Street

    Name, Suburb, State, Zip

    code

    Character 50 The Customer residential / work Address “mandatory”

    Cus_ Phone number State code- phone number Number 10 Work/ home phone Number “Optional”

    Mobile Number 0000-000-000 Number 10 “mandatory”

    Car Registration Number Number 16 “mandatory”

    Logical Data Dictionary Example “Use case Number 1.0, Manage Car Service Enquires”

    Car Service enquiry= Customer No + Car registration Number + {Customer Phone}12 + Customer Address

    Customer Phone = Home | work| Mobile

    Customer Address = Unit Number + Street Number + Street Name + Suburb + State + Zip Code

    Remaining Payment= Customer No + Invoice No + Car Issues + Total Cost

    Payment Status confirmation = “Payment for Invoice ——– Has been Processed, Thank you “

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 14

    CRUD Analysis

    Entities Name

    Use Case

    Customer Customer Invoice Supplier Invoice Suppliers Car Parts Services Mechanics

    Manage Car service Enquiry R R R

    Organize Car service U U R R

    Fix car R/U U

    Organize Payment R/U R/U

    Generate report R R R R R R R

    Fulfill Order U R/U

    Create New Customer C

    Delete Customer Record D

    Create Customer Invoice C

    Delete Customer Invoice D

    Based on CRUD analysis, we must add use cases to completely maintain all record in each entity such as Create and delete Customer, Suppliers ,

    Services , Parts and Mechanics.

    For example : Create New Customer, Delete customer , Create New parts, Delete New Parts,etc

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 15

    Use case diagram shows automation boundary

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 16

    Mary & Kim

    Manage customer enquiries

    Maintain Customer profile

    Generate Customer Invoice

    Process Invoice and Payment

    Check and Calculate cost

    Peter

    Supervise order

    Maintain order

    Notify stock level

    <<include>>

    Provide Supplier order

    <<include>>

    Undate order detail l

    Generate Monthly report

    Generate Inoice report

    SystemSystem

    Update stock level

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 17

    Sample Activity Diagram – Customer Enquire

    Customer Enquire Activity Diagram

    Customer Kim & Mary System Mechanic

    N O

    Ph as

    e

    Make Car repairment request Accept The Request

    Entre Car registration number

    Outstanding Debt?

    Check Database

    Payment Request

    Accept custmer’s vehicle Customer Car Job

    Result

    Yes

    No

    Make Payment

    Notice of Payment

    Swinburne University of Technology Dr. Xuemei Tian and Ms. Maryam Nikpour 18

    Sample Sequence Diagram

    Customer Custom

    er Mary & Kim

    Database System

    Request Car Repairment Car Registration Number

    Outstanding Debt Cost

    update Database

    Confirmation

    Make a payment

    Result

    Sequence diagram

Order now and get 10% discount on all orders above $50 now!!The professional are ready and willing handle your assignment.

ORDER NOW »»