ICT700 Systems Analysis and Design Task 2 ICT700 System Analysis and Design Task 2 Semester 2, 2018 Assessment and Submission Details Marks: 35 % of the Total Assessment for the Course Due Date:...

1 answer below »
ICT700 Task 2 Semester 2 2018.docx


ICT700 Systems Analysis and DesignTask 2 ICT700 System Analysis and Design Task 2 Semester 2, 2018 Assessment and Submission Details Marks: 35 % of the Total Assessment for the Course Due Date: 5:00pm Monday, Week 12 Assignments are to be submitted by SafeAssign. DO NOT SUBMIT THE ASSIGNMENT TO THE COURSE CO-ORDINATOR OR TUTOR. The assignment will be marked out of a total of 100 marks. Once marked, ALL assignments will be checked for plagiarism and/or collusion between individuals. Refer to your Course Outline or the Course Web Site for a copy of the “Student Misconduct, Plagiarism and Collusion” guidelines. Note: Each student MUST be able to produce a copy of their assignment and this copy MUST be produced within 24 hours of it being requested by the Course Co-ordinator. Failure to produce the second copy of the assignment when requested may result in loss of marks or a fail grade for the assignment. Requests for an extension to an assignment extension MUST be made prior to the date of submission and requests made on the day of submission or after the submission date will only be considered in exceptional circumstances. Please note because this assignment is due close to the examination period extensions without documentation and a reason that could not have been foreseen. Case Study: Odd Jobs Limited. Background: Odd Jobs Limited (OJL) is a Sydney based business which has begun to offer casual labour to other businesses. The business offers skilled staff and vehicles for hourly hire with a three (3) minimum. The business was started by the business owner, ColinGrey who undertook all the planning and management of staff to jobs however the business has now grown to include over 100 part-time and full-time employees. The organisation is also looking to expand further into other centres. Currently Colin and staff are trying to manage the staff, customer relationship systems and invoicing with off the shelf software which have worked well in the past and an off the shelf accounting system which is used to manage the accounts receivable and accounts payable of the business. The staff of OJL drive a varied selection of vehicles which are owned by OJL. These vehicles range from motorbikes, cars/ utilities and heavy goods vehicles.As a requirement of their insurance policy, OJL must ensure that the staff have the appropriate licence for the vehicle they are assigned to and keep records on this(Required licence). This means that as part of their staff record keeping they must maintain details of a staff member’s licence. They also need to maintain details of their name, address, contact details, tax file number and industry qualifications. There are contracting staff who work like private contractors (as required), these people are expected to maintain their own industry qualificationsand professional indemnity but OJL must maintain details of the licence. The office staff have set hoursand no record of their licences are maintained. Although an off the shelf accounting package is used and email for communication with suppliers and customers there is currently a low level of computer use in the organisation. The contracting staff use anOJL supplied phone and their own laptops, tablets etc. while the office staff use supplied computing machinery as they are not required to be mobile. The contracting staff phone or email hours spent on a job and ask for details of their next job to head office. This means that currently some staff at head office almost exclusively handle telephone calls from contracting staff. The head office staff have got to know the contracting staff well as they have worked together for a long time and they often enjoy a chat about what is happening in head office, when the staff phone in job details. These phone calls are often lengthy as some staff only phone their job details in once a week, this concerns Colin Grey as he does not know the value of the daily hours of each staff and vehicle. Although the manual systems for stock management and customer relationship management have worked in the past, Colin Grey and the new staff manager, Gary Tallent and customer manager Tom Smith feel a new system including a phone-based app could offer significant improvements to the work processes currently in place. Tom Smith would like the contracting staff to update the job details as they complete the job. One of his requirements would be to enable the contracting staff to complete the customer invoice at the completion of the job by inputting hours and vehicle details (based on registration number). This is so he can check on jobs as there are completed. While Gary Tallent, would like to run a report once a month that showed job figures and the income generated by each vehicle. Business Processes: A JAD session with key stakeholders revealed the following information. The business processes described below are the system requirements for this information system solution: · It has been decided to focus on the building and implementing the mobile based app for the contracting staff and run a separate project for the customer relationship management system later. Therefore, do not model any of the customer relationship managementsystem (this is where OJLmaintain details of their customers). · However, OJLstill needs to record the following details for all customers: Name, Business number, Address, Telephone, Email, and Date of last job. · OJLneeds to maintain vehicle details for the separate vehicle classes as per the licence requirements including maintenance details. OJL must be able to track the movements and drivers of all vehicles. · Tom Smith wants to run a job report on the first of every month that shows the value amount of each job, type of job and per contracting staff member. · Tom Smith also requires that the following information on each job be kept, the customer, the date of the job, contracting staff (maybe more than one), vehicles(‘s) used and amount of job. · Any payments for salaries or expenses to staff are outside the scope of this system End of Case Study Part A Question 1: Report20 marks Your manager Colin Grey is sure an adaptive systems development methodology would be useful in this project but there is little knowledge about these in the organisation. Therefore, they want you to write a report discussing adaptive development and two methodologies Scrum and XP. State under what circumstances each one would be used and then make a recommendation for this project. To do well in this report you must use the detail from the case study in your report as examples, rather than given general information. The following sections need to be included; · Adaptive methodologies – general introduction to the methodologies, including when you would use an adaptive methodology. · General discussion · Advantages · Disadvantages · Scrum · General discussion · Advantages · Disadvantages · XP · General discussion · Advantages · Disadvantages · Recommendation Your target audience is executive business people, who have extensive business experience but limited computing knowledge. Your report should be no less than one thousand (1000) words and it would be best to be no longer than one thousand five hundred (1500) words long. Appropriate referencing is required. The textbook Satzinger et. al is a valid resource, however it is expected that at least five (5) other resources will also be used. Marking Criteria Maximum Marks Marks Obtained Answers Use of Report Format 1 Professional communication (correct spelling, grammar, formal business language used) and referencing > 2 1. Introduction/ background to adaptive methodologies > 5 2.Scrum > 5 3.XP > 5 4. Recommendation > 2 Total (I) = 20 0 Question 2: Memo20 marks Review the OJL case study and answer the following question with reference to the information in the case study. OJL have requested that you write a brief memorandum commenting on and setting a plan for the requirements gathering. Briefly discuss requirements gathering in general, introduce your plan and then state why you would recommend this plan. You are expected to use information from the course in your answer, for instance lecture three such as how you will gather information, what questions will you ask. Please cover the make or buy decision, could you buy already existing software to solve OJL problem (you must justify your answer). It is expected that you use the detail from the case study in your essay and failure to do this will reduce your marks Your target audience is executive business people, who have extensive business experience but limited computing knowledge. Attach this memo to your report from question 1 as an appendix. There is limited information available to you now but you are required to make reasonable assumptions based on the information that you have. Assumptions should be noted and specifically mentioned within your memo. Your memo should be no less than seven hundred and fifty (750) words and it would be best to be no longer than one thousand (1000) words long. Marking Criteria Maximum Marks Marks Obtained Answers Use of Memo Format 1 Professional communication (correct spelling, grammar, formal business language used) > 2 1. Description of requirements gathering > 4 2. Plan for requirements gatheringOJL > 5 3.Make or buy discussion for OJL > 5 4. Recommendation –justified recommendations for OJL > 3 Total (I) = 20 0 Part B Modelling and Diagramming Review the OJLcase study and answer the following questions with reference to the information in the case study. Do NOT extend the scope for any of the following solutions beyond that specifically described in the case study above. You are permitted to make reasonable assumptions where necessary but these should be noted. It is recommended that you review all documentation for this case study before finalising any single solution. Ensure that the required consistency has been included within and between each question solution. Question 3: Event Table20 marks Review the OJL Limitedcase study and prepare an event table for the information system to support the business processes as described. Use at least the following headings for the Event Table: Event Event Type Trigger Source Activity/Use Case System Response/ Output Destination 20 18 15 13 10 5 0 Outstanding: High Distinction: Distinction: Credit: Pass: Fail: Not Submitted: An outstanding attempt – well formatted and professionally presented piece of work. An excellent piece of work that meets all the specified criteria with very minor omissions or mistakes More than competently meets the criteria specified with only minor mistakes or omissions. Competently meets the criteria as specified with few minor mistakes or omissions. Satisfactorily meets the criteria. Did not sufficiently meet the criteria to pass. No attempt made or different from what is acceptable
Answered Same DaySep 27, 2020ICT700University of the Sunshine Coast

Answer To: ICT700 Systems Analysis and Design Task 2 ICT700 System Analysis and Design Task 2 Semester 2, 2018...

Meenakshi answered on Sep 30 2020
155 Votes
9/28/2018
PART 3
Question 3: Event Table                                
In this case study we evaluate the system requirement as per requirement we design a table that is shown about the use case information
    
    Event
    General
    Special
    
    Action
    
    Object
    Includes
    Extends
    Specializes
    
    
    
    
    Source
    Source
    
    
    
    
    "Action"
    "Action"
    "Action"
    
    Destination
    
    Customer browses
    
    Customer
    Browse the
    
    
    View
    
    Look for a
    
    
    
    the Vehicle Rent
    Customer
    Non
    Vehicle Rent
    Vehicle Rent
    
    -
    
    
    Customer
    
    
    
    
    
    
    outputs
    
    Vehicle Rent
    
    
    
    index
    
    Customer
    

    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Customer find
    
    Customer
    
    find
    
    
    View
    
    Look for a
    
    
    
    
    Customer
    Non
    
    for a Vehicle
    Vehicle Rent
    
    -
    
    
    Customer
    
     a Vehicle for Rent
    
    Customer
    
    Rent
    
    
    outputs
    
    Vehicle Rent
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Customer views
    
    Customer
    
    view
    
    
    
    
    
    
    
    
    
    Customer
    Non
    
    
    Vehicle Rent
    -
    
    -
    
    Customer
    
    the outputs
    
    
    
    outputs
    
    
    
    
    
    
    
    
    
    Customer
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Customer log on to
    Customer
    -
    
    Log on to
    
    Mobile app page
    -
    
    -
    
    Customer
    
    the mobile app
    
    
    the mobile app
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Customer view his
    Customer
    
    
    View
    
    Customer
    
    Customer log on to
    
    
    
    
    
    
    -
    
    Customer
    
    
    -
    
    -
    
    Customer
    
    details
    
    
    
    
    
    
    
    the mobile app
    
    
    
    
    
    
    
    
    details
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Customer log off
    Customer
    -
    Log off from
    
    Mobile app page
    -
    Customer log on to
    -
    
    Customer
    
    from the mobile app
    
    
    the mobile app
    
    
    
    the mobile app
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Customer makes a
    Customer
    -
    
    Make
    Booking
    -
    Customer log on to
    -
    
    Customer
    
    booking
    
    
    booking
    
    
    the mobile app
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Customer views a
    Customer
    -
    
    show
    Booking
    -
    Customer log on to
    -
    
    Customer
    
    booking
    
    
    booking
    
    
    the mobile app
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
Question 4: Domain Model Class Diagram                     
amount
Date
Emp Id
Union No
Name
    
Vehicle
Vehicle Hire
System
Customer
BookingDate
D_ No
Id No
Employee
Name
Salary
Date
SSN No
hours
Time
Destination
Total hour
Question 5: Design Class Diagram                             5 Marks
Employee
ID :int
name: Varchar
location Varchar    
dateofjoin date                
void emphirevehicle(string name)
Void Listemp()
Findemployee()
VehicleBiookingePlace
VehicleBiookingePlace_ID :int
VehicleBiookingePlacename: Varchar
VehicleBiookingePlace_location Varchar
Date ;date
                    
void vehicle_hire(string name)
Void Listofvehicle()
Findvehiccle()
        
Vehicle
VehicleID :int
Vehiclemodel: Varchar
Veh_date : date                    
void vehicleadd()
Void List()
Void modifyvehiccle(int VehicleID)
Void delete(int vehicleid)
Table Name: State_master
Description: This table is used to store all the details of state.
    No
    Field Name
    Data type
    Size
    Constraints
    Description
    
    
    
    
    
    
    1
    state_id
    Int
    5
    Primary key
    State id unique
    
    
    
    
    
    
    2
    country_id
    Int
    5
    Foreign key
    Store the country id
    
    
    
    
    
    
    3
    state_name
    Varchar
    15
    Not null
    Store the state name
    
    
    
    
    
    
    4
    status
    enum
    -
    -
    Store the status of state
    
    
    
    
    
    active or inactive
    
    
    
    
    
    
Table Name: City_master
Description: This table is used to store all the details of city.
    No
    Field Name
    Data type
    Size
    Constraints
    Description
    
    
    
    
    
    
    1
    city_id
    Int
    5
    Primary key
    City id unique
    
    
    
    
    
    
    2
    state_id
    Int
    5
    Foreign key
    Store the State id
    
    
    
    
    
    
    3
    country_id
    Int
    5
    Foreign key
    Store the Country id
    
    
    
    
    
    
    4
    city_name
    Varchar
    15
    Not null
    Store the City name
    
    
    
    
    
    
    5
    status
    enum
    -
    -
    Store the status of city
    
    
    
    
    
    active or inactive
    
    
    
    
    
    
Table Name: Kilometer
Description: This table is used to store all the details of kilometer.
    No
    Field Name
    Data type
    Size
    Constraints
    Description
    
    
    
    
    
    
    1
    r_id
    Int
    5
    Primary key
    Id of kilometer
    
    
    
    
    
    
    2
    city_id
    Int
    5
    Foreign key
    Store the city id
    
    
    
    
    
    
    3
    loc_id
    Int
    5
    Foreign key
    Store the location id
    
    
    
    
    
    
    4
    km
    Int
    5
    Not null
    Store the kilometer
    
    
    
    
    
    
Table Name: Location_master
Description: This table is used to store all the details of location.
    No
    Field Name
    Data type
    Size
    Constraints
    Description
    
    
    
    
    
    
    1
    loc_id
    Int
    5
    Primary key
    Store the location id
    
    
    
    
    
    
    2
    city_id
    Int
    5
    Foreign key
    Store the city id
    
    
    
    
    
    
    3
    loc_name
    varchar
    20
    Not null
    Store the location name
    
    
    
    
    
    
Table Name: CMS
Description: This table is used to store all the details of Contact us and about us.
    No
    Field Name
    Data type
    Size
    Constraints
    Description
    
    
    
    
    
    
    1
    cms_id
    Int
    5
    Primary key
    City id unique
    
    
    
    
    
    
    2
    cms_title
    Varchar
    50
    Not null
    Store the cms title
    
    
    
    
    
    
    3
    description
    Text
    -
    Not null
    Store the Description
    
    
    
    
    
    
Table Name: User_Registration
Description: This table is used to store all the details of user registration.
    No
    Field Name
    Data type
    Size
    Constraints
    Description
    
    
    
    
    
    
    1
    uid
    Int
    5
    Primary key
    Store the uid
    
    
    
    
    
    
    2
    uname
    Varchar
    15
    Not null
    Store the User name
    
    
    
    
    
    
    3
    password
    Varchar
    15
    Not null
    Store the password
    
    
    
    
    
    
    4
    sname
    Varchar
    15
    Not null
    Store the...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here