LO1 Analyse the risk factors associated with phases of the software development lifecycle and generate possible strategies to mitigate the risks identified using a risk management process.
2024-11-18 14:15:34
Applied Software Engineering
|
Learning outcomes covered
|
1
|
Analyse the risk factors associated with phases of the software development lifecycle and generate possible strategies to mitigate the risks identified using a risk management process.
|
|
2
|
Design and implement component-based software applications based on software engineering techniques
|
|
3
|
Evaluate the role of design patterns and software architecture in software development and be able to characterise some important architectural styles.
|
|
4
|
Apply the major software testing techniques.
|
|
5
|
To be able to discern major causes of maintenance problems and be aware of reverse engineering, its limitations and tools to support it.
|
|
6
|
Critically analyse the concept of sustainable software engineering (Individual, Social, Economic, Environmental, Technical).
|
|
7
|
Identify the correct approach to sustainable design and manufacturing.
|
|
8
|
Evaluate Sustainable Software Engineering practices.
|
|
Element 1
|
|
Title
|
UML Design
|
|
Task details
|
This assignment is accompanied with a case study describing a high level system specification for an application.
Assignment Tasks:
Task 1
Use case model
Develop a Use case model for the information provided for ONE use case. As part of your answer produce the use case description and use case scenario steps. Include appropriate use case refactoring.
[10 marks]
|
|
|
Task 2
Class diagram
Produce a class diagram with appropriate principles of object orientation applied, related to the use case model in Task 1. As part of your model, produce a system class with clear set of public methods.
[20 marks]
Task 3
Sequence diagram
Produce a Sequence Diagram for the selected use case. Include possible guards, iteration, and message operations in your diagram.
[10 marks]
Task 4
Design patterns
Command pattern encapsulates a request as an object. Consider the following class diagram as the structure for the pattern:
Ref: Gamma et al.
Apply the command pattern (by modifying the classes in the above structure) to your chosen use case and class diagram which you have developed.
[10 marks]
Task 5
Component Models
Produce ONE Component with associated interface methods to represent the class diagram model. As part of your solution, illustrate various possible component composition and discuss the significance of your design.
[20 marks]
|
|
|
Task 6
Project Risk Management
Identify at least one risk which may occur during the completion of the system by using the Risk- Register template and how to control the identified risk.
[10 marks]
Task 7
UML demo and viva Ability to answer questions. [20 marks]
Notes:
Upload your answer sheet in a PDF file format
To produce diagrams, you may choose any suitable drawing tool, such as StarUML. Java source code listing and implementation is not required for this assessment.
Attempt ALL tasks
|
|
Marking Guide
|
Criteria
|
Issues
|
Mark
|
Marking breakdown where appropriate
|
|
|
Use case diagram
|
Have captured the application functionality in a use case diagram.
|
10
|
Use case diagram
Use case description and scenario steps
|
|
|
|
|
10 marks
|
|
Class diagram
|
Have you provided a class diagram which captures all elements of the system?
|
20
|
Class diagram with appropriate associations and multiplicities
|
|
|
Do you explore the issues involved in the engineering task required and software design required?
Have you understood the main functions that must be provided by the system?
|
|
10 marks
Appropriate principles of Object Orientation
10 marks
|
|
|
Have you documented your engineering analysis findings?
|
|
|
|
|
Have you applied the required level of abstraction in your models?
|
|
|
|
|
|
Have you produced a sequence model associated with your given use case scenario?
|
|
|
|
Sequence model
|
Have you produce a Sequence Diagram for the selected use case?
|
10
|
Sequence diagram guards, iteration
|
|
|
|
|
10 marks
|
|
|
Have you included possible guards, iteration, and message operations in your diagram.
|
|
|
|
Design Patterns
|
Have you produced a model to represent the specified Design Patterns?
|
10
|
Design pattern
10 marks
|
|
Component Model
|
Have you produced a suitable Component and associated interface and component composition?
|
20
|
Component and associated interface and component composition
10 marks
|
|
|
Have you related your component to the classes in your class diagram?
|
|
Component composition
10 marks
|
|
|
Have you applied appropriate component composition?
|
|
|
|
Project Risk Management
|
Identify at least one risk which may occur during the completion of the system by using the Risk-Register template and how to control the identified risk.
|
10
|
10 marks
|
|
Demo and viva
|
Ability to demonstrate the UML documents and answer questions.
|
20
|
20 marks
|
|
|
|
|
|
A magazine called “IT in the Valley” is published every month. An information system is needed to help deal with the editing of the magazine. It should also help with the payments to the contributors of stories and photographs and the receipt of payment from the advertisers.
The enterprise consists of four main departments: a Marketing Department, an Editing Department, a Processing Centre and an Accounts Department.
The information system will collect adverts, stories and photographs and publish magazine issues. It will also pay the journalists and photographers whose stories and photographs are published.
The Marketing Department receives advertising details from advertisers. Details of these adverts are recorded. The system should record who is to pay for the advertisement when it should appear and how large the advert should be. There may be other considerations such as where in the magazine it should appear. The Marketing Department passes the advertisement to the editor. An advertiser may place several different adverts in the same issue of the magazine.
The Editor checks and edits the adverts and sends them to the processing centre, where all the data concerning the content of the advertisement are stored this would normally consist of text and graphics.
In addition to the advertisements the magazine consists of a mixture of stories and adverts. A freelancing journalist submits stories to the editor. Sometimes a successful journalist has more than one story in the same issue. Details of the journalists are kept for reference situation exists for photographers. Photographers and journalists may be regular contributors or occasional contributors. Details of the stories and photographs must be stored. Complete issues of the magazine are also stored so old stories may be researched in the future. Any stories or photographs that have been submitted and remain unused after six months are archived.
The editor may match one or more photographs with a story to illustrate it. The editor chooses all the stories, adverts and photographs and puts them together to form the magazine issue.
Copies of completed issues of the magazine are sent to advertisers.
At the end of each month the Accounts Department send out payment to each of the journalists and photographers who have had a story published in the last issue of the magazine. The fee will have previously been agreed between the Editor and the journalist or photographer. The Accounts Department will also invoice the advertisers for adverts that have been published. If no payment is received within two months they will begin to bring legal proceedings against their debtors.
100% Plagiarism Free & Custom Written, Tailored to your instructions
