Terms | Definitions |
|---|---|
 In the MVC design pattern what role does the 'Model' play? | the model holds persistant data about the application, its state, on going activities etc |
| In the MVC design pattern what role does the 'View' play? | the view provides a window or interface on to the model and base for interaction |
| In the MVC design pattern what role does the 'Controller' play? | the controller captures events from the view, determines what to do, and updates the model |
| What are the basic components of the LAMP/ WAMP/ MAMP technology stack? | 1. Linux/ Windows/ Mac OS X (operating system) 2. Apache (http server) 3. MySQL (database) 4.PHP/ Perl/ Python (scripting languages) |
| What are the basic components for the WINS technology stack? | 1. Windows Server (operating system) 2. Internet Information Services (web server) 3. .NET (programming languages) 4. SQL Server (database) |
| How does a web application map to the MVC design pattern? |  |
| What is a MIME type? | A specification used on the internet to describe data. It stands for: Multipurpose Internet Mail Extensions. A MIME type is a textual label, represented as a primary object type and a specific subtype, separated by a slash. For example: • An HTML-formatted text document would be labeled with type text/html. • A plain ASCII text document would be labeled with type text/plain. • A JPEG version of an image would be image/jpeg. |
| What is a cookie? | It is a text file placed on your computer by a web site you have visited that tells the web server everything it needs to know about you (user id, session status etc) |
| what information is stored in a cookie? | A series of server specific name=value pairs for example: UserID=A9A3BECE0563982D session-id=277-7706416-3040918 |
| What is a scenario when discussed in a systems development context? | it's a semi structured textual description of a user interaction with a system |
| What are the principle elements of a use case diagram? | 1. actors 2. use cases 3. links between use cases 4. system boundary |
| In a use case diagram why would you use <<extend>> | For alternatives or options that sometimes happen. For example on an e-commerce site you may wish to extend the 'browse' use case with an 'add to basket' use case. |
| In a use case diagram why would you use <<include>> | For discrete sub-cases that usually happen. For example in an e-commerce application you may need to link the 'pay for item' use case with a 'provide payment details' sub-case. |
| In state chart notation the arrows signify transitions between states, what do the labels signify and how are they written? | The labels are of the format : Transition[Condition]/Action. Transition is mandatory, while condition and action are optional |
| In state chart notation what do the boxes signify? | The boxes signify states. The top part contains a noun describing the State of the system - this is mandatory. The bottom describes what the system is doing while in this state (do: Activity) this addition is optional. |
| How would you model boiling water on a gas cooker using state chart notation? |  |
| What is the difference between an activity and an action? | The difference between an Activity and Action is that an Activity is ongoing (boiling up water will take more than an instant). An action is something that just "happens", like someone flipping a switch, or inserting a card. |