[مخالف - طلب حل : ]عندي مشروع في المدرسه عن الفيجول بيسك 6 ولزم أحد يساعدني أرجووكم

Here is your opportunity to search for a problem that you think can be solved using a structured programming in Visual Basic. You will go through all the steps of trying to find a problem to solve, and to step through all steps of solving a complete solution. Not only will you be solving a problem, you will be documenting all the specifications of the program as well as how these specifications change throughout the exercise.



Your project will include programming techniques that make use of the best form of file input/output required to meet your project specifications. You might ask: "What if my project does not need any form of file input/output?" It will.



Much of this major programming project will focus around your ability to embrace all the programming concepts that were introduced throughout the term. Journalize all of your experiences from trying to define the problem that you are trying to solve, to the crazy crashes that your code it doing. Don’t forget to document your proud moments also. It makes for entertaining reading.



Research and referencing your sources:

Most programming is learning from other’s examples. I would expect most of you to be looking online for examples of how to approach your solutions. I also believe that copy/paste is sometimes more effective than re-typing what you see on the web. Just like in a history essay, you provide your teacher with sources of your quotations and numeric support, I will ask for the same. When you embed any pieces of code from someone else, please comment the web site that helped you. You will also have a list of sources on one page at the end of your project.

15

Initial Specifications

Friday, May 15

15

Second round specifications

Friday, May 22

70

Program/ User Manual/ Final Package/ Journal

The last day of classes

100

TOTAL



You will be required to keep all your work in one folder. When it is handed in, I will be making sure your have followed through from your proposal all the way to your presentation.

STEP 1: Initial Specifications

We will negotiate the problem that you want to solve. If you have no ideas, then I do. I would prefer that the problem come from you and your interests, but if that is not possible, I will define the problem for you.

STEP 2: Second Round Specifications:

These specifications will be much more detailed. You will address explicitly how the user will input information, the possible choices presented to the user, and the forms of output for the user.

You will also create a “release schedule”, which will list all the steps that you will go through on your way to a complete project.

STEP 3: Project Journal

You will also be keeping a programming journal of the project. In this journal you will be entering your development of the program specifications, as well as frustrations with the process. You will be sharing any new programming techniques that you acquired while solving problems within your project.



STEP 4: User Manual/Final Package

I will be marking your entire package. Your entire package should be organised in such a way that I can easily check the development from your original specifications to your final product. This is to help you, as a student just in case your presentation does not go well. I will be able to see how much work you did in order to create the program and presentation. You will electronically hand in EVERYTHING, including the project and forms with all of your source code, your journal and manual. What part of EVERYTHING might you not understand? When I try to run your program from the source code, and the compiler complains about missing files, I get very sad – and you lose marks.

PROGRAMMING PROJECT INITIAL SPECIFICATIONS

NAME:_____________________



PROBLEM TO SOLVE:











IDEAS:

NAME:_____________________



PROBLEM:





DESCRIPTION OF USER FRONT END FOR DATA ENTRY:













DESCRIPTION OF PROGRAM OUTPUT:













DESCRIPTION PROGRAMMING TECHNIQUES TO LINK INPUT AND OUTPUT:

Here, you will show an itemized plan for completing your project. You will share how you foresee your program developing, from 1.0 to 6.7 (be creative with release names). Do not worry about specific times of completion; be more concerned about the specifications that would make a given release clearly unique. The release schedule will be like rungs on a ladder that will give you direction with clearly defined progressive goals.

Release Name

New incremental features of this release

















































































Major Programming Project Package: Table of Contents



1. Table of Contents: with a full listing of all file names(program, documents) and path.

2. Progression of specifications (specs sheet 1, 2, and the release schedule)

3. Program overview/introduction

4. Disclaimer/ list of known bugs

5. User Manual

6. Journal for the project

7. Notes to future programmers of your project: directions that would make it better.

8. Electronically submit everything, including your entire programming project:

Topic:

Programmers:







Criteria

Description

Marks

Out of

Package

Clarity

The package was complete and in order.

All sections were clear, and easily understood.

Bugs, Specs and journal

All three were clear and insightful.

Program:

Challenging

The problem that you chose to solve proved to be challenging.

Program:

Clear front end

Your program interface proved to be clear to the end user: both for data input and program output/display. The manual was an excellent support.

Program:

Clear code

Your code was clear, concise, well-documented, and structured.

Clear comments throughout: especially to give an overview of a function, class, or frequently used variables.

Program:

techniques

You used the best programming techniques to solve the problem.

Notes to future programmers

These notes give great direction to future programmers as to where there is room for improvement, and possibly how to fix the problems (if only you had more time!).

Criteria

Comments

Package

Clarity







Bugs, Specs and journal







Program:

Challenging





Program:

Clear front end





Program:

Clear code







Program:

Techniques





Notes to future programmers

Whatever type of problem you are trying to solve, it must embrace programming techniques that you have used throughout the semester: if, loop, multiple forms, file i/o. Simple games can do this, but in order to get full marks, it must also include some form of file i/o. Here are some ideas:





1. A simple game. This will require the user to input and save some variables for a game that allows the user to respond by using mouse and or keyboard input.

2. A simple quiz. Questions and answers will be read via text input. You should be able to switch from true and false, multiple choice, and fill in the blanks. Matching two columns is also an option. Since it is computerized, you can modify how it is graded. For example, in multiple choice could award 1 mark for getting it right the first time, .5 for getting it right the second time, and -.5 for getting it wrong after a second guess.

3. Reinforce your understanding of math by graphing simple equations. You can start with y=mx+b and then move on to quadratics. This may not sound like a lot of fun, but once you program for math, then you really understand math.

4. Create a program that supports your interests. You must clear this idea with me ahead of time, but I am very open-minded.



Have fun!!