Undertaken by the group and submitted for credit
Your group is asked to prepare a report on the feasibility of allowing new sign-ups and existing customers to manage their accounts via their set-top box and/or the mobile app. The report should be brief and to the point. Generally groups are encouraged to use CASE tools (such as the IBM rational architecture introduced in this course), but this is not an absolute requirement. The work must establish the key design aspects of the proposed system.
We require only ONE report for this coursework, which will be split into TWO sections. Section 1 will include Deliverable 1, while section 2 will include Deliverable 2.
Deliverable 1: GROUP work (70% of coursework)
A final group report (aprox 5000 words) which must include the following:
a) Examine the emails sent to your team regarding the corporate culture, and report back with suggestions to the questions asked. How could the new system improve the corporate culture?
b) A Rich Picture serving as an initial exploration of the primary issues and stakeholders; Please state any assumptions you might had to make throughout this process.
c) A Root Definition to be used as a starting point for the proposed design and CATWOE;
d) Two Detailed Use Case diagrams (use <<include>> and <<extend>> where appropriate) from the perspective of two of your main actors (e.g. Customers and Staff). You need to create the scenarios for 2 of your use cases (1 from every diagram).
e) A Conceptual Class Diagram demonstrating the main classes with their attributes, methods and associations (aggregation/composition and generalisation where appropriate).
f) Two Object Sequence diagrams for two of the main Use Cases.
g) Two State Chart diagram for two of your main classes.
h) One aspect of systems development is capitalising on the requirements in order to propose additional beneficial features. Suggest additional capabilities which could be added to the system to improve the FutureMedia’ business. Show these functionalities as extra use cases with a different colour on your use case diagrams.
Your report also needs to include:
1) A title page with the name of your group, the names and IDs of students involved.
2) Table of contents with appropriate sections.
3) Page numbering.
4) In the conclusion section of your report please discuss and indicate the participation and contribution of each member to the coursework.
5) Please complete the pro-forma below, indicating individual contributions and submit this together with your report. The pro-forma needs to be agreed and signed by all members of the group.
Please remember that large diagrams are best reproduced on a separate page. You must ensure that the diagrams are readable! Remember that this coursework is an opportunity to show what you have learned throughout this semester of this course. Please feel free to structure your report in such a way which reflects this. You could include information which is not in the required list above in order to support your argument.
Deliverable 2: Individual component (30% of your coursework1)
Reflection & Evaluation Report (approx. 1000-2000 words) providing:
1. Your assessment of the overall process as carried out by your Team (e.g. rationale, design issues etc.)
2. Your assessment of the dynamics and functionality of your Team (e.g. whether your cooperation was effective; what went wrong if anything; how do you feel you should have addressed sour points)
3. Any further considerations in terms of how you have managed your project, the modelling of your requirements or other areas that you feel your team should have placed more attention to.
4. The report should also include complete and detailed answers of the following questions:
(a) Software development has in general been characterised as a period of great risk.
Explain why understanding and modelling of the problem is important for finding a good design solution. (5 marks)
How could Soft Systems methodology (SSM) be used to help the analyst to undertake analysis and design? Your answer should also make reference to a definition of SSM. (15 marks)
Describe in detail one software engineering process/methodology (e.g. Extreme Programming, Rapid application Development etc.) and explain how they could support contemporary software development. Your answer should outline the key features of such a process together with its advantages and disadvantages. (20 marks)
(b) Object oriented analysis and design (OOAD) is argued to help software engineers produce better and more reusable software.
Discuss the fundamental features of object-orientation. (10 marks)
Explain how these could help to overcome some of the problems faced by software engineers. (5 marks)
Explain the means by which the Unified Modelling Language (UML) might be used to model the requirements (including examples and a discussion of the diagrams you might produce). (10 marks)
Discuss why traditional structured systems analysis and design (SSAD) is argued to be of less and less relevance as systems become more interactive, flexible and more component-based as opposed to OOAD. (15 marks)