Reference no: EM132467996
CI7230 - Modelling Enterprise Architectures - Kingston University London
CASE STUDY - Valentinos
Tasks
These all relate to the description of Valentinos given below. This description should not be regarded as complete but can be regarded as accurate (in other words you can expand upon it but your answer should not contradict it). You may want to investigate similar dating agency websites for ideas! Please note that there are no absolutely definitive (or correct) answers to these. You will be assessed on your ability to present the requirements in a clear and logical manner, the way you have addressed the description of the system provided, and the quality of your discussion of the issues arising.
Note that you are required to present requirements and models for the new system at Valentinos - much of the discussion below relates to the current system. It is important to draw the diagrams using a UML case tool. For each section some marks will be given for some explanation and design choices.
Part 1. Consider your use case diagrams in coursework 1 and produce 2 overall Activity Diagrams including swim-lanes and the transitions of use cases.
Part 2. Produce 4 Prototypes presented as a storyboard
Part 3. Using the MVC pattern, produce 4 Sequence Diagrams corresponding to the 4 Prototypes
Part 4. Redraw the class diagram from coursework 1 in more detail and consider 1 class and from that draw a state-chart diagram
Part 5. Consider the class diagram in point 4 above and via object relational mapping develop an entity relationship diagram ERD.
Part 6. Consider 1 sequence diagram from 3 above and your class diagram write the basic Java code including the name of the class, attributes (including the relationships with other classes). Also include the method name but not the method details.
Part 7. Redraw the Zachman Framework and complete it further considering where all the diagrams drawn in coursework 1 and coursework 2 would be presented and show where the component and deployment diagrams would be presented as well. (Please note: you don't need to actually draw a component or deployment diagram for this coursework).
Attachment:- Modelling Enterprise Architectures.rar