Week 11

Skipped week 10...

so many assignment still so many more to go...

this week User Interface Design...

it's forms, buttons & all the relevant input and output user needs to interact with to be able to complete the desired task. The inputs & outputs can be identified by context diagram, or other DFD diagrams in other levels. If the OO approach is being used in analysis trigger in the event table might be the source to identify the required input/output.

One of the characteristics of a well-designed user interface is not necessarily providing too mush information but enough & well-organized. user should be able to navigate through pages & find necessary information easily.

nobody can tell whether the interface is well-designed but the user. there some factors out of control of human which should be considered when designing the interface. these factors are called human factors.

form can be designed in windows or browser; but having browser form has the advantage of sharing one form for internal staff as well as consumer and suppliers

Week 9

Traditional design,

Design phase can be in two ways; traditional & OO the design you choose is in close collaboration with the analysis but doesn't mean if you have done OO analysis you can't move to traditional design. yet some parts don't match...

Traditional approach focuses on top-down approach decomposition of function to be performed by given program. what the user see when interacts with system is user interface, behind that interface thousands of programing code exists.

Consider system analysis & design book, it has many chapter & each chapter talks about one topic, on the other hand to understand some chapters you have to read previous chapters... this is exactly what happens in traditional design, the application software (the book) is divided into many modules (like chapters) and each module should perform one specific function which is referred to as cohesion, the more the function is specific & identifiable the more module is cohesive (highly cohesive). modules are connected to each other but what we are looking for is not strong relationship between modules. modules which are not heavily connected to each other are called loosely coupled. modules with high cohesiveness & less coupling are desired since codes are easy to find & locate and changing one module doesn't lead to chaos.

The models we use to represent traditional approach can be divided into 3 type: flowchart, structure chart & pseudo code.