Reference no: EM133123042
Milestone - Project Proposal and Requirements Analysis
Project Proposal
Objective: The goal of the project proposal is to identify the purpose of the project, characteristics and requirements, outline the work to be done, and design a timeline for completing the work. The project proposal will contain a management plan, technical approach, and resources needed to complete the project tasks within the allocated time and budget.
Deliverable: Capstone Project Proposal and Requirements Document
Note: The project proposal needs to be completed before the end of CST-560. It must be approved by faculty before project development can occur. Once approved, you must complete and submit this milestone before the end of the course and start working on Milestone 2.
Ideas for the project may come from a variety of sources (e.g., personal ideation or an opportunity offered by your current employer). Some projects are created out of pure academic curiosity, while others are intended to create an open-source tool as a contribution to the programming community. As you overview the project and its objectives, describe its origin, intended use, and other important characteristics.
General Information
The general information section of the Capstone Project Proposal should list the following:
- Project name
- Author
- Project organization
- Project manager
- Date project proposal document is submitted Project Overview and Project Objectives
This section of the Capstone Project Proposal states the business case or the problem that this project will be solving.
Background is one of the key characteristics of a project, to explain why the project should be initiated, what prerequisites are, and what results are supposed to be obtained at the successful completion.
This section should contain a few sentences about the high-level business need or justification for the project, as well as how it originated and other background information. While this information may be obvious to the author and the project sponsor, it is imperative to be aware that a scope of work is often distributed well beyond the immediate project audience. This background clarifies the usefulness of the project to someone who is not familiar with the project.
Project Scope
This section of the Capstone Project Proposal states the scope of the project and the requirements, as well as the characteristics of the final deliverable. Include details about the project, such as:
- Is it a real time system?
- Is it all screen-based?
- What reports can be produced?
- Where does the information come from?
- What manipulation is required for the data?
- Does it store data?
- How will the system manage security?
- What problem(s) (if any) does the project address/solve?
- Is this an innovative project or an improvement to an existing one?
- Is it an implementation of a published method or algorithm?
Project Completion
This section of the Capstone Project Proposal describes what measures will be used to calculate project success, taking into account completion criteria, assumptions, and constraints.
Completion criteria are explicit goals that must be attained to call an element of a project, or the entire project, "complete." The example below shows criteria specific to the listed project. You will work with your instructor to set criteria appropriate to your project.
1. Developed within the time allocated
2. Developed within cost
3. Meets the desired performance/technology level
4. Utilized the assigned resource effectively and efficiently
5. Customer approval and acceptance
6. No disruption to the main workflow of the organization
7. Coincides with the corporate culture
Objective: In the Requirements Analysis, the report definitions and layouts, screen definitions and layouts, data element definitions, workflow diagrams, performance metrics, unique features, and security matrices are gathered.
In your documentation of requirements, be mindful of the two categories: functional and nonfunctional requirements. Functional requirements refer to certain actions, UI elements, or similar action-driven components that must be implemented. Nonfunctional requirements refer to constraints imposed on performance metrics or resource utilization. As you gather and present these requirements, specify the nature of each. This will also impact your approach to architectural design (in Milestone 2), implementation (in Milestone 3), and prioritization of development resources.
Requirements Analysis (Data Science)
Special Instructions: These instructions are to be completed by MS Data Science Program students. Instructions for the MS Computer Science Program students are provided above.
Objective: In the Requirements Analysis, the report definitions and layouts, screen definitions and layouts, data element definitions, workflow diagrams, performance metrics, unique features, and security matrices are gathered.
In your documentation of requirements, be mindful of the two categories: Functional and non- functional requirements. Functional requirements refer to certain actions, UI elements, or similar action-driven components that must be implemented. Non-functional requirements refer to constraints imposed on performance metrics or resource utilization. As you gather and present these requirements, specify the nature of each. This will also impact your approach to architectural design (in Milestone 2), implementation (in Milestone 3), and prioritization of development resources.