Scribd
Upload
57 views25 pages

CP) ) SAMPLE) ) Presentation

This document provides guidelines for a CSC-113 computer programming course. It lists the lecturer and their contact information. It then outlines several guidelines for starting a programming project, including understanding the system and actors, generating sample data, and considering good user interface designs. It concludes by listing some good programming practices such as indentation standards and common identifier casing.

Uploaded by

Zain Irfan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
57 views25 pages

CP) ) SAMPLE) ) Presentation

This document provides guidelines for a CSC-113 computer programming course. It lists the lecturer and their contact information. It then outlines several guidelines for starting a programming project, including understanding the system and actors, generating sample data, and considering good user interface designs. It concludes by listing some good programming practices such as indentation standards and common identifier casing.

Uploaded by

Zain Irfan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 25

CSC-113

COMPUTER PROGRAMMING

LECTURER :FASIHA IKRAM


EMAIL ADDRESS: [email protected]
Some Guideline To Start A
Project
OBJECTIVES

Understand the actor of your system


Make some data
Make User Interface
Lets start programming
UNDERSTAND THE SYSTEM

1. Understand your system


2. Figure out how system is working with any
software solution or understand the manual
system
3. Understand its needs
4. Understand the flow of program
5. Figure out the constants of your systems.
To do list
UNDERSTAND THE ACTOR OF YOUR SYSTEM

Lets do some paper work


type

H description

M priority
system
L
name

Due date
done
Y

N
Generate some data
SAMPLE DATA
Task Priority H M
Done Name Type Due Date
Description L

Enter a task
Y Task1 description office L 25-Jun-12
here
Deadline for
all Excel
N Task2 Home M 25-Oct-12
Project
Timesheets
Submit my
own Excel
y Task3 university H 05-Dec-16
Timesheet for
approval
Submit my
N Task4 Excel Expense office H 05-Dec-16
Sheet
Some good user interfaces
At the end of slides asci codes are available use them
Good Programming Practices

A coding standard can be useful for the


following reasons
• Programmers can quickly read someone
else’s code on a project
• New people can get up to speed quickly
• People new to a language are spared the
need to develop a personal style
INDENTATION AND BRACKET PLACEMENT EXAMPLES
ANSI C++ Style
if (hours < 24 && minutes < 60 && seconds < 60)
{
return true;
}
else
{
return false;
}
Kernighan and Ritchie Style
if (hours < 24 && minutes < 60 && seconds < 60) {
return true;
} else {
return false;
}
COMMONLY USED IDENTIFIER CASE

• Constants have Upper Case with Underscores:


THIS_IS_AN_EXAMPLE

• Variables and functions have Lower Camel Case:


thisIsAnExample

• Local variables have Lower Case with Underscores:


this_is_an_example
ASCII CHARACTER SET
Presentation Guidelines
1. Font size must be between 24-
28px for description
2. 28 – 32 For headings
3. Font colors should be
consistent.
4. Choose theme wisely
1. Title slide
 Main title: Full project name
 Sub-title: Project acronym
 Footer: Contract number, project duration (from – to), date
of
creation of your slides
2. Project Summary
This slide should communicate the main features of your project.
It should
be possible to use it as a standalone slide. It should include:
 One or several carefully selected pictures which illustrate the
system of the project
 A few bullet points on the outputs/results which the project will
generate
3. Background

This slide should illustrate:


 the underlying problems, issues, opportunities, which your
project addresses
 why your project is so interesting and relevant

4. Objectives and main steps(what functionalities you have


used in this system. E.g file handling , functions and array.)
 Add here a few lines describing:
 the key underlying objective(s)
 what you actually plan to do
 Also disscuss about some of the datatypes that you have
wisely selected while making the project.

5. some screen shoots


6. Conclusion
7. Future work
8. Question answer
Report Guidelines
Report guideline
1. Title Page
2. index (optional)
3. introduction (just one paragraph for each)
4. overview (just one paragraph for each)
5. DISADVANTAGES OF PRESENT WORKING SYSTEM (maximum
two paragraph for each)
6. ADVANTAGES OF YOUR SYSTEM (maximum two paragraph for
each)
7. Explain DATA STRUCTURES AND FILES (its good if you make tables
rather than writing descriptions )(e.g. variables, arrays, structures, )
8. explain about logic (IPO chart , flow chart(just show the flow chart for
some of the processing tasks not for complete program) , algo ) , (data
storage) and here you will also write the constrain that mention in
project proposal.
9. Screen shoots , explain some of screens (which is in best User
interface)
10. conclusion

You might also like