the attached files contain the explanation of the question.
Assignment 2 Due: Thursday 23 January 2020 Length: 3,500 words Weighting: 35% Assignment topic The purpose of this assignment is to evaluate your ability to develop a comprehensive implementation proposal for an information system that uses a systems approach. The proposal should be targeted at a potential ‘sponsor’ organisation that will need to be convinced of the appropriateness and effectiveness of the proposed new system. Choose an information system (e.g., ERP systems, CRM systems, SCM Systems, Management Information Systems, Decision Support Systems, Executive Information Systems, Enterprise Portals, Data Warehouse & Data Mining Applications, Enterprise Collaboration Systems, Knowledge Management Systems), and so on, that you have studied in this unit. Alternatively, you may wish to combine features of several systems. Please note for the purpose of this assignment, mobile apps or other e-business and digital enterprise applications should not be used as the chosen information system. Your assignment should describe the steps of the Systems Development Life Cycle (SDLC) discussed in Topic 4 of the subject. The proposed system must address an identifiable problem/opportunity that exists in the sponsor organization and relate to particular aspects of the organization’s overall strategic directions. It is important that you select the features of your system carefully and justify your selection. Do not just use (be critical of the use of) the standard features of a commercially available software package. For the purposes of this assignment, try to keep the system that you are proposing to a manageable size. Your proposed system could help the ‘sponsor’ by: · improving an existing manual information system · introducing a new information system · creating a new business opportunity · improving organizational productivity. The sponsor could be: · top management of your company · an investor · a financial institution which will lend you money · a client who has engaged you as a consultant. · But a sponsor is not the same as the financial sponsor. Format for Assignment 2 The format of the formal assignment will be: · Covering letter to sponsor · Title page · Table of contents · Executive summary (1 page) · Introduction · Body of your assignment with suitable headings and subheadings · Conclusions · Reference list (Harvard referencing style is required) · Appendices (including a background of the organization for your unit assessor!). References: Harvard Referencing Style is required in this subject. Please visit SCU Library website for information (URL: http://www.scu.edu.au/library/finding_info/citing_info.html). You can also contact SCU librarians for assistance. Marking criteria for Assignment 2 Category Specific criteria Maximum marks MC 1: Content – clear understanding of issues (30 Marks) Description of organizational context (good brief description of the chosen organization (e.g., industry, visions, missions, business processes)) 2 Discussion of its internal and external operating environments 3 Clearly identify the problem/opportunity for IS/IT 2 Clearly justify your choice of the proposed system (including cost/benefit analysis plus at least one other feasibility studies); Clearly explain how the information system that you are proposing will support the strategic goals of the organization 4 Present system analysis and system design for the intended system (a managerial viewpoint is sufficient) 4 Explain how the system will be developed, tested and implemented 6 Discuss post-implementation activities 3 Discuss project management, risk management and change management associated with the implementation 6 MC 3: Use of multiple sources of information and Referencing (3 Marks) Good research effort evidenced by using references from a variety of sources; Good integration of references into your discussion; Proper practice of in-text citation and provision of all the cited references in the reference list via applying Harvard Referencing Style 3 MC 4: Communication and Presentation (2 Marks) Use of study materials; Use of proper terminology; Good structure of the report; Professionally formatted and presented; Being able to clearly express ideas; Clarity of communication with good flow, reasoning and argument; Concise but not over simplifying; Spelling and grammar (use of spell-Checker!) 2 Total marks 35 Instructions from the side of our tutor · Please make sure you use an appendix with page numbers. In the appendix you include all the checkpoints you need to address Example: 3.0 External environment 3.1 Technology 3.2 Customers 3.3 competitors etc. This makes it easier to mark and hence easier to allocate marks. PowerPoint Presentation Client Request for Proposal (RFP) aka Request for Tender (RFT) etc. Contractor Proposal Executive summary Internal environment (organizational culture etc.) External environment (competitors, customers, technology, SWOT) Analysis (business requirements, functional requirements, build or buy? tangible, intangible benefits Etc.) Design Development Testing Risk Management Implementation Categories Production - many Project - One off Small scale - One person Large scale Many persons Many different skills Resources Objectives (SBS) Work i.e. people Money Materials Schedule Budget Specification 2 Work - making product or service 3 Objectives (SBS) ON schedule ON budget TO specification 4 Risk = ? Formula? Quadrant? Fail Production - many Project - One off Small scale - One person Large scale Many persons Many different skills Resources Objectives (SBS) Work Money Materials Schedule Budget Specification Success Categories Risk = pain or gain 5 Work - making product or service 6 System Development Life Cycle – SDLC Phase 1 - Conception Client Request for Proposal (RFP) Contractor Proposal Client Review, contract Phase 2 - Definition Phase 3 - Execution Phase 4 - Operation 7 2. Request For Proposal (RFP) Client: Need to be met Problem to be solved Market opportunity to be exploited Funding SWOT analysis RFP RFP Statement of Work (SOW) Description/background of problem, need, or general type solutions to be investigated Scope of work to be performed work/deliverables to be included work/deliverables to be excluded Requirements (SBS) Schedule - expected completion date Budget Specifications and standards 8 8 Section 2: Statement of Works The contractor shall be responsible for furnishing expertise, labour, materials, tools, supervision and all services for the completion of this project. The technical details are in section 6. Exclusions The contractor will not be responsible for site clearance Scheduled delivery date. The complete, fully functioning and tested system will be completed by… Cost and contract Price of contract with not exceed… Contract will be firm fixed price. Who has risk? 10 InitiationProject scope High level budget Time frames Project organization Charter PlanningDetailed plan Detailed schedules Detailed budget Resources Risk analysis Quality Communications Procurement ExecutingChange management Quality control Reporting Management of stakeholders, teams Closure (hand over)Final report Lessons learnt Release of resources SDLC 11 7-Step SDLC Model Suggested by Haag et al. (2008) 11 12 Example: Some Costs and benefits of a new supply chain management system (Laudon & Laudon 2005) 13 14 Project Planning Tracking Basics Advanced New Plan Tasks Resources Link Tasks - resource Format StartCalendars (base) Information Date Tasks Task duration Milestones Dependencies Scheduling Documentation Subtasks Work Cost Material Notes Standard Night 24 hour Used to create Proposal Used to mange project 15 16 17 Standard Night shift 24 hour 18 Project Planning Tracking Basics Advanced New Plan Tasks Resources Link Tasks - resource Format StartCalendars (base) Information Date Tasks Task duration Milestones Dependencies Scheduling Documentation Subtasks Work Cost Material Notes Standard Night 24 hour 19 20 21 Project Planning Tracking Basics Advanced New Plan Tasks Resources Link Tasks - resource Format StartCalendars (base) Information Date Tasks Task duration Milestones Dependencies Scheduling - constraints Documentation Subtasks Work Cost Material Notes Standard Night 24 hour 22 Milestone – 0 duration 24 Project Planning Tracking Basics Advanced New Plan Tasks Resources Link Tasks - resource Format StartCalendars (base) Information Date Tasks Task duration Milestones Dependencies Scheduling - constraints Documentation Subtasks Work Cost Material Notes Standard Night 24 hour 25 Task relationship DependenciesMeansLooksExample Finish-to-start (FS)Predecessor (A) must finish before successor (B) can start. Finish time for A defines start time for B. When A finishes, we can start B but not before.Activity A – lay foundations and concrete set. Activity B – build walls Lay foundations and concrete set (A) must finish before build walls (B) Start-to-start (SS)When predecessor (A) starts, successor (B) can start. We want A and B to start at same time. Successor (B) can start at same time, but does not have to i.e. does not require both tasks begin simultaneously. Activity A – pour concrete Activity B – level concrete Level concrete (B) cannot begin until pour concrete (A) begins Finish-to-finish (FF)When predecessor (A) finishes, successor (B) can finish. We want A and B to finish at same time Successor (B) can finish at same time, but does not have to i.e. it can finish after predecessor Start-to-finish (SF)When predecessor (A) starts, successor (B) finishes. Enter predecessor (numeric) OR Drag and drop 28 Task relationshipMeans Finish-to-start (FS)Predecessor (A) must finish before successor (B) can start. Finish time for A defines start time for B. When A finishes, we can start B but not before. Start-to-start (SS)When predecessor (A) starts, successor (B) can start. We want A and B to start at same time. Successor (B) can start at same time, but does not have to i.e. does not require both tasks begin simultaneously. Finish-to-finish (FF)When predecessor (A) finishes, successor (B) can finish. We want A and B to finish at same time Successor (B) can finish at same time, but does not have to i.e. it can finish after predecessor Start-to-finish (SF)When predecessor (A) starts, successor (B) finishes. 29 Project Planning Tracking Basics Advanced New Plan Tasks Resources Link Tasks - resource Format StartCalendars (base) Information Date Tasks Task duration Milestones Dependencies Scheduling - constraints Documentation Subtasks Work Cost Material Notes Standard Night 24 hour Scheduling task constraints - Degree to which task can be rescheduled (8 constraints) Flexible Can change start and finish: As Soon As Possible (ASAP) As Late As Possible (ALAP) Semi-flexible Can change start and finish: Start No Earlier Than (SNET) Start No Later Than (SNLT) Finish No Earlier Than (FNET) Finish No Later Than (FNLT) Inflexible Must start/finish specific: Must Start On (MSO) Must Finish On (MFO) 31 Scheduling task constraints Degree to which task can be rescheduled (8 constraints) Main representations Network Diagram - analysis Gantt Chart – enter data 32 33 34 Network 5 – 10 high level activities One start (no predecessor) One finish (no successor) All other activities – predecessor AND successor DO NOT PROCEED UNTIL LOOKS LIKE THIS 35 Project Planning Tracking Basics Advanced New Plan Tasks Resources Link Tasks - resource Format StartCalendars (base) Information Date Tasks Task duration Milestones Dependencies Scheduling - constraints Documentation Subtasks Work Cost Material Notes Standard Night 24 hour Task/ActivityDuration (days)Predecessors 1Foundations3None 1.1Survey1None 1.2Framework1Survey 1.3Concrete1Framework 2Walls2Foundations 3Roof3Walls 4Electrical1Roof 5Plumbing5Roof 6Plastering4Electrical 7Lights2Electrical 8Sinks1Plumbing 9Painting3Plaster 10Finishing1Sinks, Light fittings, Painting Build a house 36 37 Insert 3 blank rows below foundations 38 Enter sub tasks – surveying, formwork, foundations Select and indent all three 39 Enter subtask predecessors and durations 40 41 Expand/collapse 43 Project Planning Tracking Basics Advanced New Plan Tasks Resources Link Tasks - resource Format StartCalendars (base)