Part 1 – The Proposal Document ()
University Financial Aide Fee Management Application
Tracks payments paid by students for school to include any technology or lab fees they pay on top of tuition (library, computer labs, admission fees, books, etc.).
The system should track all payments, any late fees, and categorize it so the students can see what portion of their money goes to tuition, books, fees, etc. The system will be controlled and maintained by a financial aid supervisor in order to provide security and allow access for students needing that information.
•Enter student information with different categories based on payment reasons/amounts
•Handling payment information bybank card/check as well as Cash
•Proper handling of new Departments/Classes
•Creation of new users and authority management.
•Database Backup/Database Recovery
•List of students
•Cash Handling Reports (Fines,Admission Fees,Other Fees)
•Proper Graphical User Interface
•Proper Links with MsWord/Ms Excel
•Using Visual Studio, create a project for your proposed application.
•Create a sample splash screen for your application (a splash screen is a screen that runs at program startup). This screen should have the application name, your name, the date, and a descriptive note about the purpose of the application. Include a graphic that fits the project; you may use any public domain graphic (i.e.: no licensed or copyrighted material!) or create your own graphic.
Update Part 1
It is known that many things can change between the design and implementation. Update your Application Proposal (shown as Part 1) and complete the following tasks.
•What items you will be able to create and how you will create them?
•Create a storyboard (graphic) and list of menu and screen items to delineate your proposed user screen(s) and menus. Include a starting list of the classes you believe will be useful to your application.
•List and describe any user data inputs and outputs your application will require and produce.
•If you will be using data validation as one of your techniques, list and describe the criteria needed for each proposed field.
•Using Visual Studio, create sample class implementations. These will be code stubs that provide the basis for the classes you will be using.
Create the Final Application proposed in Part 1.
•Compile and test the application before you submit it.
•If your final project does not match the proposed design exactly, document the differences.
List the differences between the design document specification and the final implementation.
•Write a detailed explanation of why the design was not implemented. For example, if your design was too ambitious and you did not have time to implement it completely, what did you do instead, and why was the original too time consuming?
•Your code project must be in Visual Studio.
•Your documentation must be in a Word-readable format (.docx, .doc, .rtf, .txt).
•Your final submission will consist of
othe application plus all project files (code files and other project files);
odocumentation of differences between proposed design and final product.