Chapters in action

ch1 the problem

→ system analysis

(check the general idea from the client enough info to create a prototype

→ database (where to store and how to divide items)

→ algorithm (how to design the client demains)

ch2 is still the problem

→ thinking as if it's an art drawing and skeleton in parts the solution

→ try and error for expected questions and solutions for the client

→ creating a small, simple prototype

ch3 prototype and meeting with the client

the target of this meeting, so you and the client now

can chat with something available

→ system analysis + system design (recheck what the client wants after displaying the prototype to the client)

ch4 the back base of the solution

→ database (keep the Database normalization in mind, recheck the database tables )

→ data structure (how to store stuff (for basic array, class))

→ programming (from steps to functions)

check the core items that the client needed

so the solution becomes useful

ch5 things to look for

from this point

set a meeting and create a list of demands

-now during the meeting, all the basic operations are done (and checked with the client)

-some reports are done and shown to the client

-from now and so on

there will be two types of requirements from the client

Qol and solution easy use

ch6

→ missings items (layout, logic)

→ the outcome, display check

ch7 concepts to know if you to be more

+performance

with each iteration, a lot of testing needs to be done, for each system component

------------