CS 4970 – Capstone Design |
||
1.0 Problem DefinitionCover Page
1.1 Introduction
1.2 Background (technical)
1.4.Goals & Objectives
1.5 Overall Approach
References
IMPORTANT: Please note that your problem definition and literature review need to be handed in as a single document, at least 10 pages long. Your problem definition report style must follow the outline provided above with headings and sub-headings as indicated. Use inline numbered references within the text description of your problem definition report instead of footnotes. The literature survey is to cover 5 journal articles and should be a separate section of the problem definition report. You can find it above. At the outset, make sure that you define “system”, “components / parts”, internal constraints, external environment and interface requirements in your problem definition. This applies to the sections that follow. The problem definition consists of several parts. The first part is a narrative giving an accurate description of the work to be carried out. The second part identifies the objectives and tasks to be performed in carrying out the effort described by the problem statement. The problem statement is the English description of the effort to be provided by the project. The usual format is to have an overview paragraph describing the entire project, which is then followed by several paragraphs with the details required by the writer. The assumption is that sufficient information is required so that a different person other than the writer can carry out the succeeding step of requirement analysis. It is essential that you include a description of your motivation for this project, along with a description of (possible) market demand for the product or service, and other competitive solutions in the market place; preferably after your overview paragraph. . The second part is to define the project in terms of objectives and tasks. Objectives are the aims that one strives for, the tasks are the steps required for the work. Both objectives and tasks should be measurable. At this point it is also appropriate to describe experiments that may be required to determine the feasibility of some aspect of the project. It may be desirable to test some code segment (that may be time critical) or a circuit that needs to be tried out. A description should include work to be carried out and questions to be addressed. In the section describing the overall approach, you are expected to develop a system diagram figure illustrating the complete system and its major component parts including any interactions with external components. Each individual should write a problem statement for the project. This is individual work and should be treated as such. There will be one draft submission to the instructor, which will be checked for content. It is assumed that a writing intensive teaching assistant has provided all the help you need. The draft will be returned at the next class. You will then be expected to produce a final draft. Upon the return of the final draft, each group will combine the appropriate elements from each team members problem statement for single problem statement for each team. IMPORTANT: Please note that your problem definition and literature review need to be handed in as a single document, at least 10 pages long. The process model system diagrams discussed in class are attached below : |
