This document provides guidelines for submitting a senior project proposal for CS500, including structure and content. It states that groups of four students must submit a project title by March 1st and the full proposal by March 6th. The proposal should include an introduction, problem statement, objectives, scope, methodology, significance, task breakdown, and timeline. The documentation guidelines are in the provided Telegram group. The proposal aims to concisely communicate the project goals, approach, importance, and feasibility within the given constraints.
This document provides guidelines for submitting a senior project proposal for CS500, including structure and content. It states that groups of four students must submit a project title by March 1st and the full proposal by March 6th. The proposal should include an introduction, problem statement, objectives, scope, methodology, significance, task breakdown, and timeline. The documentation guidelines are in the provided Telegram group. The proposal aims to concisely communicate the project goals, approach, importance, and feasibility within the given constraints.
This document provides guidelines for submitting a senior project proposal for CS500, including structure and content. It states that groups of four students must submit a project title by March 1st and the full proposal by March 6th. The proposal should include an introduction, problem statement, objectives, scope, methodology, significance, task breakdown, and timeline. The documentation guidelines are in the provided Telegram group. The proposal aims to concisely communicate the project goals, approach, importance, and feasibility within the given constraints.
Structure, Content, & More Form groups of four students and submit project title within three days, before Wednesday 01 March 2023.
Submit project proposal
in a week before or on 06 March 2023. Documentation guideline for all deliverables is uploaded on your telegram group. WIN2023_CS500 All communications shall be on this group You shall sign project commitment. Project Title (Example):
An Enterprise Information System for retail
companies’ internal inventory management
It should be accurate and informative, and free of
abbreviations or jargons. Should be aligned with the project objectives (specific enough to tell the reader what exactly the project is about). Introduction/Background (Overview/Executive Summary) • While this section is the first presented, it is better to write it after completing the rest of the proposal since the most of the text emanates from the rest of the section.
Statement of the Problem
• Customer & User level : Negative Statements • While Objectives are Positive Statements which improve the problem situation Aims (goals) and Objectives: [Example] The primary goal of this project is to build an EIS as a central data processing unit which can be utilized in various retail companies for their daily activities coordination including:
Daily Inventory Management: Sharing inventory levels of all
branches with employees to respond to customer orders more efficiently. Product Transfers: Providing a platform for staff from different branches to request products online. Sales Analysis: Performing inventory and sales data analysis to understand the customer preferences in different regions, and informing managers’ decision-making. Scope of the Project & Limitations • Setting the Boundary : What should and should not be included • Functionalities expected from the solution (system) • Possible problems that may hinder the project from achieving its objectives fully Methodology (Approaches) • The What, When, and How of the Project • Process model to be used • Methods, Tools, Techniques used in each of the process phases • Technologies • =========================================== • Documentation tools, Programming languages and tools, CASE tools, • Frameworks, Hardware & Software Platforms Significance & Audience (Utility & Beneficiaries) • What is the value of the system and to whom • What are the benefits of the developed system and who are the target groups • Functional rather than attractive behaviors of the system Task Breakdown & Feasibility Analysis • Who does what? What products (deliverables) are produced after completion of each task? • Achievability given the resources available
• And Finally project timeline / schedule
Project Schedule / Timeline Use Gantt or PERT charts