Reference no: EM132316288 , Length: word count:2000
Systems Analysis Assignment -
Read the attached case study answer the questions.
Case Study: Australian Electric Supply
Assignment Requirements and Deliverables -
You are required to write a report for the OZES management team, which must include the following information, and is organized in a professional and meaningful structure. Please note standard report structure including an executive summary must be adhered to.
1. Consultation -
The OZES management team has heard of agile and iterative systems development methodologies but is unsure of their effectiveness for their project as there is little knowledge about these in the organisation. Therefore, they want you to compare at least four (4) various methodologies of agile and iterative developments that could be adopted for OZES needs. State under what circumstances each one would be used and then make a recommendation for this project. To do well in this report you must use the details from the case study in your report as examples, rather than giving general information.
This part could be started with a general introduction to the agile and iterative methodologies relevant to the case study. For each chosen methodology you may use the following structure, which are then followed by a recommendations section:
Methodology X
- Discussions
- Advantages
- Disadvantages
Your target audience is executive business people, who have extensive business experience but limited computing knowledge.
This part should be no less than seven hundred and fifty (750) words and it would be best to be no longer than one thousand (1000) words long. Appropriate referencing is required.
The textbook Satzinger et al. is a valid resource, however it is expected that at least five (5) other resources will also be used and cited.
2. Analysis of the case
Review the OZES case study and analyse the case by professionally demonstrating the following modelling tables and diagrams for the information system solution to support the business processes as per the case study.
An Event Table -
- For the event table, use at least the following headings: Event / Event Type / Trigger / Source / Activity or Use Case / System Response or Output / Destination
A Use Case Diagram -
- Should be compatible with the event table solution.
- Solutions must follow the methodology as outlined within the Satzinger et al. textbook. Solutions are expected to align with the components as shown in Figure 3-12 and 3-15.
Use Case Description (intermediate) -
- For the ' Sell Second-hand Item ' use case only, as documented in the event table solution and the use case diagram solution.
- Solutions must follow the methodology as outlined within the Satzinger et al. textbook. Solutions are expected to align with the components as shown in Figure 5-2.
A Domain Model Class Diagram -
Solutions must follow the methodology as outlined within the Satzinger et al. textbook. Solutions are expected to show:
- The class name and attributes list for each class and sub class as required.
- All required associations.
- All attributes as specifically mentioned in the case study must be reflected.
- Other attributes as needed to support the described functionality.
It is not necessary to show methods, however you may include them if you wish. Solutions are expected to align with the components as shown in Figure 4-23 of the Satzinger et al. textbook.
Design Class Diagrams -
- For the 'Associate Broker' and 'Order' classes ONLY. These classes should be part of the Domain model class diagram solution.
- Each of these design class diagrams are expected to have a complete list of attributes and a comprehensive list of methods, which supports the specified functionality as described in the case study.
- Solutions must follow the methodology as outlined within the Satzinger et al. textbook. Solutions are expected to align with the components for the 'Design class diagram for Student' as shown on the right hand of Figure 12- 4.
Do NOT extend the scope for any of the solutions beyond that specifically described in the case study above. You are however permitted to make reasonable assumptions where necessary, but these should be noted.
It is recommended that you review all documentation for this case study before finalising any single solution. Ensure that the required consistency has been included within and between all solutions. You may use a tool such as Microsoft Visio Drawio to draw the models or neatly hand draw and scan into a pdf document. However, you should submit only one document.
3. Memo on pertinent issues
Currently there is not a strong reliance from OZES on computers to get their work done outside standard applications. Therefore, acceptance of the new system is a concern for the management team. They have requested that you write a brief memorandum commenting on adopting a User Centred Design (UCD) approach and setting a plan for the development of the Human Computer Interaction (HCI) when considering the CRM application. Briefly discuss UCD and HCI in general and investigate the implications of adopting a UCD approach on the project, introduce your plan supported by the principles of UCD and HCI, and then state why you would recommend this plan. You are expected to use theory in your response.
Review the OZES case study to complete the memo with reference to the information in the case study. Your target audience is executive business people, who have extensive business experience but limited computing knowledge. Attach this memo to your report as an appendix.
There is limited information available to you now but you are required to make reasonable assumptions based on the information that you have. Assumptions should be noted and specifically mentioned within your memo. Your memo should be no less than five hundred (500) words and it would be best to be no longer than seven hundred and fifty (750) words long.
Submission - The report is to be prepared as a single Microsoft Word document.
Attachment:- Assignment File - Case Study.rar