Expectations: So for this course we are given an example company and a list of requirements for a new system that they are planning to build. From this list of requirements you're supposed to write a proposal for a potential solution that covers the details of the system that you would build if given the contract. To help with this, a template of what the proposal should look like is provided in the task overview/supporting documents. The template generally follows the flow of: Intro Requirements Methods Design Testing Sources With each of those sections requiring more detail/info to fulfill the proposal requirements. I'll cover each of these sections further down below. Intro: The first part is the introduction which is fairly straightforward in which the problem is described and outlined. Pretty much think of an opening paragraph to an essay. The thing that got me a kickback for revisions here was the scope, in which I stated the requirements that I would cover, but didn't list the requirements that I would NOT cover. The way to resolve this is to say something along the lines of, "this proposal looks at requirements A, B, C, but outside of the scope of this document are requirements X, Y, Z". Requirements: The requirements are fairly straightforward and provide background, context, and details on the main parts of the system that you'll be expected to write the proposal for. NOTE: There are more requirements listed in the requirements doc than what you need provide in your write-up/proposal. For example, let's say there are 10 requirements, and the rubric provided(in this example) only has you detail 3 of them, in that case you only need to go in depth on 3 of them. The other thing that can be confusing is that the requirements are generally broken up into main sections, and subsections/bullet points like so: Example: ***************************************** Main Section: Search Requirement The system must have a search function that is useful to users and can be used throughout the business. The search function will find information within a timeframe designated by the user and must allow for special characters and find the required data in a reasonable amount of time. (subsection)The following general requirements apply: The proposed system should have a response time of no less than 10 seconds The proposed system should allow for at most 100 search results to be displayed for the given search, anything more than that should display "too many records found" The system should allow for boolean searches (ex: AND, OR, NOT, etc...) The system should log all searches to a database ***************************************** I would write the above requirement as follows in my proposal: The system will have a search function that allows for users to search for records that are utilized throughout the business including sales records, contacts, meeting notes, etc... The search function will utilize special characters for internationalization as well as allowing for boolean modifiers for searches(OR, NOT, etc...). There will be a maximum response time of 10 seconds, and a maximum of 100 search results displayed so as to not overwhelm users or the system. Basically I integrated all the requirements/necessities into a general paragraph that encompasses everything and is fairly readable. To keep your proposal consistent, look back to what you stated/outlined in the scope section of the template/proposal. If you listed in the scope that your proposal will cover sections A, B, C, have your requirements match up with covering sections A, B, and C. Methods: For this section we compare and contrast different approaches to developing software. This is pretty straightforward as you choose a couple of methods and list their advantages and disadvantages and end up picking the method that works best. Design: Here you're required to draw some mock-ups/wireframes of what part of your proposal would look like or how it would function. For this part, I just used simple MS paint drawings, but others have suggested things like Visio, Figma, or Draw io. It really depends on what you want to use, but for this MAKE SURE you label the drawing, and what it corresponds to (i.e. is it a wireframe of a user interface, a mock-up of how data will flow from one part of the system to another, etc...) I didn't label my drawings and it contributed to me getting my proposal kicked back. So for example using the search requirement from above, I might draw an example of what a user might see when the utilize the search bar with the search box, buttons, options, etc... and label it: EXAMPLE DRAWING 1 HERE "Fig 1: Mock up of user search bar with various buttons and options that the user would have" and I might draw a chart showing how the search bar would connect with various parts of the system as a whole and label it " EXAMPLE DRAWING 2 HERE "Fig 2: Diagram of how the search bar will interact with the overall system to retrieve various business records and data" Testing: This section has you detail various tests that should be run before the system is fully implemented to verify its functionality. These tests should correspond with what you outlined in the scope and requirements. I.e. If you outlined in the scope and requirements A, B, C. Test one(or all) of those, and not X, Y, Z. For example using the search requirement above I might write a test like: This test will check the search requirement for logging. This will be done by inputting a user search and ensuring that it is written to the database Because they ask that you write multiple tests, it's technically possible that you could write all 3 tests for 1 requirement/system. I.e you could test search logging, verifying that the search function accepts boolean operators, and that the search function responds in less than 10 seconds. But I decided to play it safe and write tests that matched up with different requirements (i.e. I wrote a test that corresponded to requirement A, a test for requirement B, and a test for requirement C). Sources: Here you should list out the sources that you used for the research you did, I listed out my sources using MLA style.