Что такое findslide.org?

FindSlide.org - это сайт презентаций, докладов, шаблонов в формате PowerPoint.

Обратная связь

Презентация на тему 1. Introduction to Java Language. 3. Large Project Specific

Содержание

2. Large Project FeaturesSophisticated functionalityLarge code librariesLarge team
3. Sophisticated functionalitySeveral hundreds or even thousands application’s functionsLarge user manualSometimes sophisticated algorithms*Infopulse Training Center
4. Large code librariesAn application contains 20 –
5. Large team & employee turnoverSeveral sub teams
6. Different roles of team membersDevelopers + team leaderArchitects, algorithm designersTestersBusiness analystsTechnical writers *Infopulse Training Center
7. Long life cycle5-20 years of development5 –
8. Project DocsUser manualProgram source codeThat’s All!*Infopulse Training Center
9. Work with CodeCreationMaintenance (80% of lifecycle)ReviewBug Fixing*Infopulse Training Center
10. Code QualityLow code quality increases losses in interactions between team members*Infopulse Training Center
11. Code ConvensionsCode should be well documented and standardizedCode should be as simple as possible*Infopulse Training Center
12. DeclarationsOne declaration per line is recommended since
13. Class DeclarationsNo space between a method name
14. StatementsEach line should contain at most one
15. Compound StatementsThe enclosed statements should be indented
16. Naming ConventionsClass names should be nouns, in
17. Скачать презентацию
18. Похожие презентации

Large Project FeaturesSophisticated functionalityLarge code librariesLarge team & employee turnoverDifferent roles of team membersLong life cycle*Infopulse Training Center

Главная
Информатика
1. Introduction to Java Language. 3. Large Project Specific

1. Introduction to Java Language3. Large Project Specific

Large Project FeaturesSophisticated functionalityLarge code librariesLarge team & employee turnoverDifferent roles of

Sophisticated functionalitySeveral hundreds or even thousands application’s functionsLarge user manualSometimes sophisticated algorithms*Infopulse Training Center

Large code librariesAn application contains 20 – 100 class librariesA class library

Large team & employee turnoverSeveral sub teams in different cities and/or countries5-15

Different roles of team membersDevelopers + team leaderArchitects, algorithm designersTestersBusiness analystsTechnical writers *Infopulse Training Center

Long life cycle5-20 years of development5 – 15 application versions (usually containing

Project DocsUser manualProgram source codeThat’s All!*Infopulse Training Center

Work with CodeCreationMaintenance (80% of lifecycle)ReviewBug Fixing*Infopulse Training Center

Code QualityLow code quality increases losses in interactions between team members*Infopulse Training Center

Code ConvensionsCode should be well documented and standardizedCode should be as simple as possible*Infopulse Training Center

DeclarationsOne declaration per line is recommended since it encourages commentingPut declarations only

Class DeclarationsNo space between a method name and the parenthesisOpen brace “{”

StatementsEach line should contain at most one statement.A while statement should have

Compound StatementsThe enclosed statements should be indented one more level than the

Naming ConventionsClass names should be nouns, in mixed case with the first

How to Study Code ConventionsStep by step studyingWide use code reviewUse possibilities

Слайды презентации

Слайд 2 Large Project Features
Sophisticated functionality
Large code libraries
Large team &

Large Project FeaturesSophisticated functionalityLarge code librariesLarge team & employee turnoverDifferent roles

employee turnover
Different roles of team members
Long life cycle

*
Infopulse Training

Center

Слайд 3 Sophisticated functionality
Several hundreds or even thousands application’s functions
Large

user manual
Sometimes sophisticated algorithms

*
Infopulse Training Center

Слайд 4 Large code libraries
An application contains 20 – 100

Large code librariesAn application contains 20 – 100 class librariesA class

class libraries
A class library consists of 20 – 70

classes
A class contains 200 – 2000 code lines
So, application’s code =
100 000 – 20 000 000 code lines

Infopulse Training Center

Слайд 5 Large team & employee turnover
Several sub teams in

Large team & employee turnoverSeveral sub teams in different cities and/or

different cities and/or countries
5-15 (up to 50-70) developers in

each sub team
10-20% of natural turnover in a team
Step by step shifting of responsibilities to Ukraine

Infopulse Training Center

Слайд 6 Different roles of team members
Developers + team leader
Architects,

algorithm designers
Testers
Business analysts
Technical writers
*
Infopulse Training Center

Слайд 7 Long life cycle
5-20 years of development
5 – 15

Long life cycle5-20 years of development5 – 15 application versions (usually

application versions (usually containing sub versions and modifications)
Real examples:
Project

1 - 1996 – 2007
Project 2 - 2001 – 2010
Project 3 - 1989 – till now

Infopulse Training Center

Слайд 8 Project Docs
User manual
Program source code
That’s All!
*
Infopulse Training Center

Слайд 9 Work with Code
Creation
Maintenance (80% of lifecycle)
Review
Bug Fixing
*
Infopulse Training

Center

Слайд 10 Code Quality
Low code quality increases losses in interactions

between team members

*
Infopulse Training Center

Слайд 11 Code Convensions
Code should be well documented and standardized

Code

should be as simple as possible
*
Infopulse Training Center

Слайд 12 Declarations
One declaration per line is recommended since it

DeclarationsOne declaration per line is recommended since it encourages commentingPut declarations

encourages commenting
Put declarations only at the beginning of blocks
Try

to initialize local variables where they’re declared.

Infopulse Training Center

Слайд 13 Class Declarations
No space between a method name and

the parenthesis
Open brace “{” appears at the end of

the same line as the declaration statement
Closing brace “}” starts a line by itself indented to match its corresponding opening statement, except when it is a null statement the “}” should appear immediately after the “{“
Methods are separated by a blank line

Infopulse Training Center

Слайд 14 Statements
Each line should contain at most one statement.
A

StatementsEach line should contain at most one statement.A while statement should

while statement should have the following form:

while (condition) {
statements;
}

Infopulse Training Center

Слайд 15 Compound Statements
The enclosed statements should be indented one

Compound StatementsThe enclosed statements should be indented one more level than

more level than the compound statement
The opening brace should

be at the end of the line that begins the compound statement; the closing brace should begin a line and be indented to the beginning of the compound statement

Infopulse Training Center