Complete Blue Catering Service Inc.âs (BCS) 2011 Form 1120, Schedule D,and Schedule G (if applicable) using the information provided below.⢠Form 4562 for depreciation is not required. Include the amount of tax depreciationgiven in the problem on the appropriate line on the first page of Form 1120.⢠Assume that BCS does not owe any alternative minimum tax.⢠If any information is missing, use reasonable assumptions to fill in the gaps.⢠The forms, schedules, and instructions can be found at the IRS Web site(www.irs.gov). The instructions can be helpful in completing the forms.Facts:Cara Siler, Janna Funk, and Valerie Cloward each own one-third of the common stockof Blue Catering Services Inc. (BCS). BCS was incorporated on February 4, 2008.It has only one class of stock outstanding and operates as a C corporation for taxpurposes. BCS caters all types of social events throughout southern California.⢠BCS is located at 540 Waverly Way, San Diego, CA 92101.⢠BCSâs Employer Identification Number is 38-4743474.Appendix C C-17⢠BCSâs business activity is catering food and services. Its business activity codeis 722300.⢠The shareholders also work as officers for the corporation as follows:⢠Cara is the chief executive officer and president (Social Security number231-54-8976).⢠Janna is the executive vice president and chief operating officer (SocialSecurity number 798-56-3241).⢠Valerie is the vice president of finance (Social Security number879-21-4536).⢠All officers devote 100 percent of their time to the business and all officersare U.S. citizens.⢠BCS uses the accrual method of accounting and has a calendar year-end.⢠BCS made four equal estimated tax payments of $20,000 each. Its tax liabilitylast year was $70,000. If it has overpaid its federal tax liability, BCS wouldlike to receive a refund.⢠BCS paid a dividend of $30,000 to its shareholders on November 1. BCS hadample earnings and profits (E&P) to absorb the distribution.The following is BCSâs audited income statement for 2011:BCSIncome StatementFor year ending December 31, 2011Revenue from sales $1,800,000Sales returns and allowances (5,000)Cost of goods sold (350,000)Gross profit from operations $1,445,000Other income:Capital loss (15,000)Dividend income 25,000Interest income 10,000Gross income $1,465,000Expenses:Compensation (950,000)Depreciation (10,000)Bad debt expense (15,000)Meals and entertainment (3,000)Maintenance (6,000)Property taxes (11,000)State income taxes (45,000)Other taxes (44,000)Rent (60,000)Interest (5,000)Advertising (52,000)Professional services (16,000)Employee benefits (32,000)Supplies (5,000)Other expenses (27,000)Total expenses (1,281,000)Income before taxes 184,000Federal income tax expense (62,000)Net income after taxes $ 122,000C-18 Appendix CNotes:1. BCSâs inventory-related purchases during 2011 were $360,000. It values its inventorybased on cost using the FIFO inventory cost flow method. Assume therules of §263A do not apply to BCS.2. Of the $10,000 interest income, $1,250 was from a City of Irvine bond that wasused to fund public activities (issued in 2005), $1,750 was from an Oceanside citybond used to fund private activities (issued in 2004), $1,000 was from a U.S.Treasury bond, and the remaining $6,000 was from a money market account.3. BCSâs dividend income came from Clever Cakes Inc. (CC). BCS owned 10,000shares of the stock in Clever Cakes at the beginning of the year. This represented10 percent of SSM outstanding stock.4. On October 1, 2011, BCS sold 1,000 shares of its CC stock for $25,000. It hadoriginally purchased these shares on April 18, 2008, for $40,000. After the sale,BCS owned 9 percent of CC.5. BCSâs compensation is as follows:⢠Cara $150,000⢠Janna $140,000⢠Valerie $130,000⢠Other $530,0006. BCS wrote off $25,000 in accounts receivable as uncollectible during the year.7. BCSâs regular tax depreciation was $28,000. None of the depreciation shouldbe claimed on Form 1125A.8. The $5,000 interest expense was from a business loan.9. Other expenses include $6,000 for premiums paid on term life insurance policiesfor which BCS is the beneficiary. The policies cover the lives of Cara, Janna,and Valerie.The following are BCSâs audited balance sheets as of January 1, 2011, and December 31,2011.2011January 1 December 31AssetsCash $ 180,000 $ 205,000Accounts receivable 560,000 580,000Allowance for doubtful accounts (60,000) (50,000)Inventory 140,000 150,000U.S. government bonds 20,000 20,000State and local bonds 120,000 120,000Investments in stock 400,000 360,000Fixed assets 140,000 160,000Accumulated depreciation (50,000) (60,000)Other assets 20,000 21,000Total assets $1,470,000 $1,506,000Liabilities and Shareholdersâ EquityAccounts payable 280,000 240,000Other current liabilities 20,000 18,000Other liabilities 40,000 26,000Capital stock 400,000 400,000Retained earnings 730,000 822,000Total liabilities and shareholdersâ equity $1,470,000 $1,506,000
Assignment ii
Due Date and Time
Weighting
Assessment Description
Detailed Submission Requirements
Unit Name/Code ISY3002/ISY302 IS Project 1
Assessment Number 3
Assessment Name Software Design Document Report and Presentation
Unit Learning Outcomes ULO 1: Work effectively in a team to liaise with clients to determine systems
requirements and elicit information necessary to create a software solution.
ULO 2: Demonstrate an understanding of the roles and responsibilities of software developers, clients and users of a system software developers, clients and users of a system. Graduate Attributes Assessed
Communications
Collaborations
Research
Critical thinking & problem solving
Communications
Critical Thinking & problem solving
Ethical Behavior
Flexibility
ULO 3: Conduct a feasibility study that outlines costs, timeframes, a development schedule, and the features and benefits of a prospective software solution.
ULO 4: Demonstrate skills in project planning and management, problem solving, analysis, and evaluation.
ULO 5: Demonstrate skills in software design, development, implementation, testing and documentation of an authentic industry type project, that is, a less well-structured or messy problem, requiring demonstration of high-level skills. Communication
Collaboration
Research
Critical Thinking & problem solving
Ethical Behavior
Communication
Collaboration
Research
Critical thinking & problem solving
Ethical behaviour
Communication
Research
Critical Thinking & problem solving
Ethical Behavior
Flexibility
Report submission deadline is 12.06.2020 by 5 PM AEST. 40% (30% Report and 10% Presentation)
A 4000 word Report on Software Design based on your Client’s project details.
15-minute Presentation in week 11 (08-02-2020) during class time by whole group.
Report: This report is to be submitted in MS Word format. Upload the report via Moodle/Turnitin. Follow the instructions as required by this assessment brief.
Presentation: All group members must give the presentation to get the marks. Zero marks will be given to the group member who does not give the presentation or who is absent on the presentation day.
INSTRUCTIONS
Report: The word limit of the report is 4000. It should be written in size 12 Arial Font. You must submit your own work and use appropriate references in Harvard style where needed. The similarity index of your report should not be more than 20%. Draft report must be discussed with the instructor in the class on 06-02-2020 and 13-02-2020. All groups must bring a hard copy of the Draft report for discussion.
Presentation: Maximum time allowed for presentation is 15 min. All group members must present the work to obtain marks. Zero marks for being absent on the presentation day.
NATURE OF THE TASK
This is a group assessment. Please make groups of three students for this assessment.
HOW TO PRESENT YOUR ASSIGNMENT / SUBMISSION INSTRUCTIONS
Your report must follow the structure given below;
1. Executive Summary
• It should summarize the key points of the Software Design Document.
• 250-300 words
2. Introduction
Introduction has the following sections;
• Background of Project: Explain the aims, objectives and importance of the project.
• Purpose: Explain the purpose of the Software Design Document.
• Structure: Explain the structure of the Software Design Document.
3. Conceptual Model
This section has the following three components;
• Technologies used: Explain the various technologies that will be used by you in this project.
• System overview: Provide an overview of main functionalities of the system.
• Architectural Pattern: Explain the architectural design pattern (s) that will be used by you in this project. Draw a block diagram of the software architecture.
4. Design Viewpoints
• Logical Viewpoint: Explain the logical viewpoint related to your project. Draw class diagrams to explain the logical viewpoint.
• Information Viewpoint: Explain the information viewpoint related to your project. Draw Entity Relationship (ER) diagrams to explain the Information viewpoint.
• Interface Viewpoint: Explain the various interfaces of the project. Provide screenshots of various aspects of Front End of the software.
• Interaction Viewpoint: Explain the interaction viewpoint related to your project. Draw Sequence Diagrams to explain the Interaction viewpoint.
5. Traceability Matrix
• Draw and explain the traceability matrix related to your project.
6. References
• In Harvard referencing style
7. Appendix (if needed)
• Programming code, screenshots, tables etc.
• Must be referred in the main body of the report.
RETENTION OF RECORDS
Students are required to keep a copy of all items submitted or completed for assessment or evaluation until the end of the grade appeal period.
GROUP CONTRIBUTION FORM
You must submit the Group Contribution Form with the report. Group Contribution Form is given at the last page of this assessment brief.
MARKING CRITERIA
See the rubric given at the next few pages.
Architecture Pattern (3 marks) Architectural Pattern is clearly explained
(3 marks) Few aspects of Architectural Pattern are not clearly explained
(2.25 – 2.75 marks) Many aspects of
Architectural Pattern are not clearly explained
(1.25 – 02 marks) Many aspects of Architectural Pattern are missing and are poorly explained
(0.25 – 1 marks) Architectural pattern used is missing and not part of the report.
(0 marks)
Block Diagram (2 marks) Block Diagram is clearly drawn
(2 marks) Some aspects of Block Diagram are not clearly drawn
(1.5-1.75 marks) Many aspects of Block Diagram are not clearly drawn
(1-1.25 marks) Block Diagram is poorly drawn
(0.25 – 0.75 marks) Block Diagram is missing
(0 marks)
Design View Points (12 marks)
Logical Viewpoint (3 marks) Class Diagrams are clearly drawn and explained
(3 marks) Few class diagrams are not clearly drawn and/or not clearly explained
(2 – 2.75 marks) Many class diagrams are missing and/or not clearly explained
(1-1.75 marks) Many class diagrams are missing and poorly explained
(0.25-0.75 marks) Logical Viewpoint section is missing and not part of the report
(0 marks)
Information Viewpoint (3 marks) Entity Relationship (ER) diagrams are clearly drawn and explained
(3 marks) Entity Relationship (ER) diagrams are not clearly drawn and/or not clearly explained
(2 -2.75 marks) Many Entity Relationship (ER) diagrams are missing and/or not clearly explained
(1-1.75 marks) Many Entity Relationship (ER) diagrams are missing and poorly explained
(0.25 – 0.75 marks) Information Viewpoint section is missing and not part of the report
(0 marks)
Interface Viewpoint (3 marks) All Interfaces are clearly explained and appropriate screenshots are provided
(3 marks) Few interfaces are not clearly explained and/or appropriate screenshots are not provided
(2-2.75 marks) Many interfaces are not clearly explained and/or appropriate screenshots are not provided
(1-1.75 marks) Many interfaces are not clearly explained and appropriate screenshots are not provided
(0.25 – 0.75 marks) Interface Viewpoint section is missing and not part of the report
(0 marks)
Interaction Viewpoint (3 marks) Sequence diagrams are clearly drawn and explained
(3 marks) Few Sequence diagrams are not clearly drawn and/or not clearly explained
(2-2.75 marks) Many Sequence diagrams are missing and/or not clearly explained
(1-1.75 marks) Many Sequence diagrams are missing and poorly explained
(0.25-0.75 marks) Interaction Viewpoint section is missing and not part of the report
(0 marks)
Traceability Matrix (3 marks)
Traceability Matrix (3 marks) Traceability Matrix is clearly drawn and explained
(3 marks) Few aspects of Traceability Matrix are not clearly drawn and/or not clearly explained
(2-2.75 marks) Many aspects of Traceability Matrix are missing and/or not clearly explained
(1-1.75 marks) Many aspects of
Traceability Matrix are missing and poorly explained
(0.25-0.75 marks) Traceability Matrix is missing and not part of the report
(0 marks)
Marking Criteria for the Oral Presentation
Assignment 3
Task Description Maximum Marks Marks Obtained
1 Comprehensive introduction:
– Introduced self
– Introduced the project and its importance 01
2 – Content
– Delivery
– Timing 03
3 – Well-designed Slides
– Readable/ Spellings/Grammar
– Slides are numbered
– References in Harvard Style 03
4 Answers to Questions 03
Total 10
Group Contribution Form
Unit Name/
Code
ISY3002/ISY302 IS Project 1
Assessment Number 3
Assessment Name Software Design Document
Due Date and Time Report submission deadline is 12.06.2020 by 5 PM AEST.
Instructions • Report will not be marked without the submission of this form with the report.
• This form should be completely filled.
• This form should be signed by all group members.
• Attach this form at the end of the report.
• Do not upload it separately on the moodle.
Names of Student Tasks Worked on Percentage Contribution to
Assessment
e.g. If you have
contributed equally then mention 33.33% contribution by each Signature
insert student name Insert tasks Insert % Insert signature here
