Professional Development (300578)
Lecture 8 – Project Proposal QA
Project Proposal Q&A
Professional Development (300578)
Lecture 8 – Project Proposal QA
Outline
• Company Outline
• Structure of Project Proposal • Writing Style
• Any Specific Questions
Professional Development (300578)
Lecture 8 – Project Proposal QA
• Company Outline
• Pinnacle Software Inc.
• Tailor made software company – It builds its own software • Has its own teams for development
• Geographically distributed
• International Company (Exists in India)
• Marketing Department has Given you a Project Brief • Marketing is not IT focused
• You are not developing it – So what are you doing?
Professional Development (300578)
Lecture 8 – Project Proposal QA
Company Outline
• Pinnacle Software Inc.
• Tailor made software company – It builds its own software • Has its own teams for development
• Geographically distributed
• International Company (Exists in India)
• Marketing Department has Given you a Project Brief • Marketing is not IT focused
• You are not developing it – So what are you doing?
You hand it over to the development team and your team manages it
Professional Development (300578)
Lecture 8 – Project Proposal QA
Professionalism in Document • Being assessed in both Part A and B
• It includes: • Title Page
• Executive Summary • Table of Contents
• Introduction
• Conclusion
• Writing Style
• Document Formatting – page numbers, headings, etc.
Professional Development (300578)
Lecture 8 – Project Proposal QA
Title Page
• This page should have your company’s name, the name of the document and who it is intended for.
• This should be a professional title page, not a simple heading. It will be representing Pinnacle Software Inc, therefore ensure this reflects that.
Professional Development (300578)
Lecture 8 – Project Proposal QA
Executive Summary
• The executive summary is a summary of the document’s purpose, what is in it, and outcomes or actions relating to the document. It is not a summary of the project brief.
• Identifying the documents outcomes is crucial in the executive summary
Professional Development (300578)
Lecture 8 – Project Proposal QA
Table of Contents
• There should be a table of contents of 1st level headings, and any 2nd level headings.
Professional Development (300578)
Lecture 8 – Project Proposal QA
Introduction
• The introduction is not an introduction to the project brief. It does provide context of the project, but it is more an introduction to what lies in the document. It should include: why the document was produced, the approach taken to build the document, who put the document together, and any goals or actions that the document will lead to.
Professional Development (300578)
Lecture 8 – Project Proposal QA
Conclusion
• A summary of what was presented within the document and any next actions.
Professional Development (300578)
Lecture 8 – Project Proposal QA
Writing Style
• This is a professional report not an academic assessment
• Academic writing focuses on demonstrating one’s comprehension to something
• Isassessedacademically
• Manyreferencesareused
• Discussions,demonstrates,arguesthroughknowledgeetc.
• Professional writing focuses on applying one’s comprehension to something
• Is not assessed academically, it is for a specific purpose
• Normally leads to some kind of action
• References are only for very specific things, for instance, prices of products
• Straight to the point, talks about actions and/or benefits in relation to the reason for the writing.
Professional Development (300578)
Lecture 8 – Project Proposal QA
Formatting
• There is no specific outline on how you format your document. However, it must be professional and must include the basic elements of a professional document, consistent formatting, headings, page numbers, etc.
Professional Development (300578)
Lecture 8 – Project Proposal QA
Structure of Specification Document
• Title Page
• Executive Summary
• Table of Contents
• Introduction
• Company and Client Project Objectives • Functional Requirements
• Non-Functional Requirements
• Conclusion
Professional Development (300578)
Lecture 8 – Project Proposal QA
Structure of Specification Document
• Title Page
• Executive Summary
• Table of Contents
• Introduction
• Company and Client Project Objectives
• Functional Requirements
• Non-Functional Requirements
• Conclusion
• Required email is a page before the title page. Do not send an email to the UC! If you do you will get zero marks for the email and questions.
Professional Development (300578)
Lecture 8 – Project Proposal QA
Company and Client Objectives
• This outlines the company’s (Pinnacle Software – the company you work for) position and its objectives towards the client. For instance, what are Pinnacle Software’s capability and objectives for applying for this project; what are you trying to achieve for the client.
• The title can be different for this section, for instance, Pinnacle Software’s Objectives
Professional Development (300578)
Lecture 8 – Project Proposal QA
Functional Requirements
• All the functional requirements identified from the project brief. Every functional requirement must have a unique ID, a function statement, a summary of function, and a justification of why the function is needed.
Professional Development (300578)
Lecture 8 – Project Proposal QA
Functional Requirements FR01 – User Management
Function Summary
Multiuser Management consisting of management (Creation, Reading, Updating and Deleting) of user accounts, authentication and authorisation of role-based user accounts, and facility for user self-management of account through profile management – password reset and change, email address assignment and contact detail management. Roles and details of users to be determined during analysis and design of proposed system.
Reasoning for Requirement
… (This is specific to your case study. Why do they need User Management. Not just because they will have users!)
Professional Development (300578)
Lecture 8 – Project Proposal QA
Non-Functional Requirements
All the non-functional requirements identified from the project brief. Every non-functional requirement discussed in relation to the project and how they will be achieved, along with its quantitative measure!
Many student groups go to Wikipedia and just pick the standard non- functional requirement areas without relating it to their given case study and not giving a quantitative measure. With such a submission you cannot achieve more than pass mark for this section.
Professional Development (300578)
Lecture 8 – Project Proposal QA
Client Email
• A professional email introducing the team and their role. Also addressing the purpose of the email before leading into the questions
• Questions
• Do not ask for requirements. You’ve attached a requirement document to the
email, so why would you be asking for requirements
• You are to ask questions to help you identify possible constraints and clear assumptions you may have that could affect your future proposed solutions.
Professional Development (300578)
Lecture 8 – Project Proposal QA
Structure of Proposal
• Title Page
• ExecutiveSummary
• TableofContents
• Introduction
• Project Overview and Objectives • Key Personnel and Stakeholders • Functional Requirements
• Non-Functional Requirements
• 3 Alternative Solutions
• Recommended Solution
• Project Approach
• Legal Considerations
• QualityAssurance
• Conclusion
• Appendix (If Any)
Professional Development (300578)
Lecture 8 – Project Proposal QA
Project Overview
• The project overview is an outline of the problem the project brief presents. It identifies the type of solution needed based on the problem, and the benefits of such a solution in relation to the core business functions of the business in the project brief.
Professional Development (300578)
Lecture 8 – Project Proposal QA
Key Personnel and Stakeholders
• The key personnel, staff, investors, etc. and stakeholders need to all be identified. Their roles within the project should also be discussed and justified. Any assumptions about these key personnel or stakeholders also need to be presented, such as availability in regard to consultation or similar.
Professional Development (300578)
Lecture 8 – Project Proposal QA
Alternative Solutions
• Present 3 alternative solutions to the problem. Each alternative solution must include a solution overview, technologies and resources to achieve the solution, constraints and assumptions, a cost benefit analysis, and benefits and justification of the solution towards the project brief.
• This section makes up ‘bulk’ of the the marks for Part B
Professional Development (300578)
Lecture 8 – Project Proposal QA
Recommended Solution
• From the 3 alternative solutions one solution is presented as the recommended solution. A detailed justification of why this solution is recommended must be present, and also why in comparison to the 2 alternative solutions is it the recommended.
Professional Development (300578)
Lecture 8 – Project Proposal QA
Project Approach
• How the project is to be approached must be presented. This will present a release schedule in relation to the functional requirements identified, any SDLC used and why.
• It is not a project plan!
Professional Development (300578)
Lecture 8 – Project Proposal QA
Legal Considerations
• Present legal considerations that need to be considered for such a project and the consequences of violating these legal considerations. Also, identify those who assume responsibility of each consideration.
Professional Development (300578)
Lecture 8 – Project Proposal QA
Quality Assurance
• An outline of the quality assurance procedures that will be implemented for the project must be present. This includes during the project life cycle and after.
Professional Development (300578)
Lecture 8 – Project Proposal QA
Conclusion
• A summary of what was presented within the document and any next actions.
Professional Development (300578)
Lecture 8 – Project Proposal QA
?