📚 Seth MB

Search

Search IconIcon to open search

Planning

Last updated May 26, 2023 Edit Source

share_title="Look at this page from SethMB.xyz" share_description="https://sethmb.xyz/sixth/CompSci/Programming/Planning/" author="@saluki@fosstodon.org"

Taking time to think through what we intend to do will nearly always raise questions and usually helps you to understand the full scale of the problem that you are trying to solve.

# Methodologies

# Waterfall

Waterfall is flexible because you can go up or down the chain as needed.

# Lifecycle/Agile

A large project may use multiple instances of the agile pan to work on subprojects. It’s also possible to cycle around if an issue is found.

More subject to issues than Waterfall, as waterfall allows for queries to go back up the chain.

# Scrum

Continuous reviews of the project result in faster problem detection and resolution. Scrum immitates a much more natural working style. Sprints are used to focus on getting things finished bit by bit and allow everybody to stay on schedule.

# Flowcharts

A diagram that explains the flow of a program.

Shapes represent actions that must be perfomed.

The shapes are connected together with arrows - defining the flow route.

Flowcharts are much easier for the layman to understand.

The shapes all represent a specific action. In a flowchart, the shape is important. The key is shown below:

# Pseudo Code

Laid out roughly like code, with some form of uniform syntax. HOWEVER - there is not set syntax rules and ideas can be expressed more freely.

It is more natural for programmers to work with pseudo code than any of the other methods.

No rules as such, but it is conventional to declare the end of an IF, WHILE or something else.

Programming