What relationship would you anticipate between locus of control orientation and gender, age, race, religious affiliation, conformity to peer pressure, academic achievement, and participation in lotteries? How would this dimension influence the extent to which people are superstitious and the extent to which they believe in horoscopes, quack remedies, and magical rituals? Who is most likely to demonstrate ego strength by choosing a delayed but valuable reward over an immediate momentary pleasure? Do you feel more or less external in some areas of life (e.g., politics) than others (e.g., academics)? What childhood experiences or characteristics of your family may have contributed to your own locus of control expectancies?

TaskQuestion 1 – User Interface Design – 30 marksGiven a full use case description, design a user interface to support that use case. Illustrate your design with a set of annotated storyboards, and explain your design choices with reference to user interface design principlesPart 1 - Storyboards - 20 marks Given a use case description and a System Sequence Diagram showing the information flow requirements for that use case, develop a set of dialogues/storyboards that support the information requirements for that use case.Part 2 - UI Design Principles - 10 marks Discuss/explain your UI design with reference to principles of UI design, and architectural requirements.Question 2 – Use Case Realization – 70 marksGiven the full use case description and a domain model perform a Use Case Realization to support at least the normal flow through the user interface you just designed. Illustrate your realization with a sequence diagram and a design class diagram.Note: the use case realization is to be performed within a single execution context. Represent all remote parts of the system (if required) as actors.Also Note: The use case realization is to be performed using the ‘perfect memory assumption’ – no data access operations are necessary.Final Note: the purpose of use case realization is to produce a set of design classes which can be directly implemented as software in code.Part 1 - Sequence Diagrams (50 marks)Using a boundary class for each node of your UI design, assigning a use case controller class, and using the domain model provided, describe the collaboration between classes necessary to support the information needs of the use case. Illustrate at least the normal flow. Those intending to achieve higher grades should also illustrate first major alternate flows and then minor exception flows. Part 2 - Design Class Diagram (20 marks)Apply the results of your use case realization to create a design class diagram showing class attributes and methods required to support the illustrated flows of the use case.RationaleThis assessment task will assess the following learning outcome/s:be able to describe and apply an iterative incremental software development process.be able to analyse and verify system requirements.be able to produce and verify analysis and design models for a system.be able to evaluate a problem and determine the appropriate architectural style for the solution.be able to evaluate and choose appropriate software design patterns to compose the design of a software system.be able to demonstrate use of a Computer Aided Software Engineering (CASE) tool to document the models in a system.Marking criteria and standardsQuestion 1 Part 1: Storyboards - 20 marksCriteriaHigh DistinctionDistinctionCreditPassMark17-2015-1613-1410-12How well do the storyboards reflect an understanding of how to apply UI design principles to support a use case?User interface completely supports normal flow and all alternate and exception flows.Design closely follows all UI design principles.Navigation between UI nodes is clear and explicit.Functionality of all elements within nodes is made clear with annotationsUser interface completely supports normal flow and all major alternate flows.Design follows most UI design principles.Navigation between UI nodes is clear.Functionality of most elements within nodes is made clear with annotationsUser interface supports normal flow and some alternate flows.Design follows most UI design principles.Navigation between UI nodes is generally made clear.Functionality of some elements within nodes is annotatedUser interface supports normal flow.Design follows some UI design principles.Navigation between UI nodes may not be clear.Functionality of elements within nodes is not annotated.Question 1 Part 2: UI Design Principles - 10 marksCriteriaHigh DistinctionDistinctionCreditPassMark8.5-107.5-8.46.5-7.45.0-6.4How well does the discussion of the application of UI design principles reflect an understanding of those principles?Discussion presents a clear and correct explanation and justification for the design of all elements in all nodes of the user interface design.Discussion presents a clear and correct explanation and justification for the design of most elements in most nodes of the user interface design.Discussion presents a generally clear and correct explanation and justification for the design of most elements in most nodes of the user interface design.Discussion presents a generally clear and partially correct explanation and justification for the design of some elements in some nodes of the user interface design.Question 2 Part 1: Sequence Diagrams - 50 marksCriteriaHigh DistinctionDistinctionCreditPassMark4.3-54-4.23.2-3.92.5-3.1How well do the sequence diagram/s reflect an understanding of the process of use case realization?Diagrams demonstrate a clear and correct understanding of the concepts of actors, boundary, control, and entity classes.Diagrams demonstrate a clear and correct understanding of object responsibility and collaboration between objects to achieve a task.Diagrams correctly show all information flows required to fully support the use case.Diagrams demonstrate a clear and correct understanding of sequence diagram syntax, including message labelling, the creation of objects, and use of advanced constructs such as alt, loop, and ref fragments.Diagrams are well laid out, easy to follow, and syntactically correct.Diagrams demonstrate a mostly correct understanding of the concepts of actors, boundary, control, and entity classes.Diagrams demonstrate a mostly correct understanding of object responsibility and collaboration between objects to achieve a task.Diagrams correctly show most information flows required to fully support the use case.Diagrams demonstrate a mostly correct understanding of sequence diagram syntax, including message labelling, creation of objects, and use of advanced constructs such as alt, loop, and ref fragments.Diagrams are generally well laid out easy to follow, and generally syntactically correct.Diagrams demonstrate a generally correct understanding of the concepts of actors, boundary, control, and entity classes.Diagrams demonstrate a generally correct understanding of object responsibility and collaboration between objects to achieve a task.Diagrams show most information flows required to support normal and major alternate flows for the use case.Diagrams demonstrate a generally correct understanding of sequence diagram syntax, including message labelling and creation of objects.Diagrams are generally syntactically correct.Diagrams demonstrate a partial understanding of the concepts of actors, boundary, control, and entity classes.Diagrams demonstrate a partial understanding of object responsibility and collaboration between objects to achieve a task.Diagrams show some information flows required to support normal flow for the use case.Diagrams demonstrate a partially correct understanding of sequence diagram syntax, including message labelling.Diagrams may be poorly laid out and difficult to follow. May contain several syntax errors. Question 2 Part 2: Design Class Diagram - 20 marksCriteriaHigh DistinctionDistinctionCreditPassMark4.3-54-4.23.2-3.92.5-3.1How well does the design class diagram (DCD) reflect an understanding of the aims of use case realization?The diagram correctly shows all classes used in the sequence diagrams and none of the actors involved.All messages used in the sequence diagrams are assigned to the correct class in the DCD.All attributes necessary to support the methods are correctly assigned to the correct class.Design classes correctly integrate all methods and attributes required by all flows illustrated in the sequence diagrams.Associations and dependencies between classes are shown correctly.Diagram is well laid out, and syntactically correct.The diagram correctly shows at least the controller and entity classes used in the sequence diagrams and none of the actors involved.Most messages used in the sequence diagrams are assigned to the correct class in the DCD.Most attributes necessary to support the methods are correctly assigned to the correct class.Design classes correctly integrate most methods and attributes required by most flows illustrated in the sequence diagrams.Associations and dependencies between classes are generally shown correctly.Diagram is well laid out, and generally syntactically correct.The diagram correctly shows at least the controller and entity classes used in the sequence diagrams.In general, messages used in the sequence diagrams are assigned to the correct class in the DCD.In general, attributes necessary to support the methods are assigned to the correct class.In general, design classes integrate methods and attributes required by different flows illustrated in the sequence diagrams.Diagram is generally syntactically correct.The diagram shows at least the controller and entity classes used in the sequence diagrams.Some messages used in the sequence diagrams are assigned to the correct class in the DCD.Some attributes necessary to support the methods are assigned to the correct class.Design classes may not integrate methods and attributes required by different flows.PresentationAll text and all diagrams should be concatenated and presented in a single MS Word compatible word processed document.Diagrams should be exported as a high resolution PNG image file before incorporation into the word processed document.It is the student's responsibility to ensure that all diagrams in their submission are readable.RequirementsIt is necessary to prepare diagrams using a CASE tool that produces UML compatible diagrams.