Assessment Details and Submission Guidelines
Trimester T2 2020
Unit Code HS2011
Unit Title Systems Analysis & Design
Assessment Type Group Assignment
Assessment Title Proposed System Analysis and Modelling
Purpose of the
Assessment (with
ULO Mapping) In this assignment, students are required to develop a workable and stand-alone system using all the knowledge and information that they have learnt in the unit HS2011 to provide possible solutions and make recommendation.
Students will be able to:
2) Evaluate system implementation and post implementation systems requirements.
3) Identify, critically analyse and investigate the process of exploring problem areas in a given context
4) Apply analysis and modelling techniques in the context of practical problems, discuss alternative models and solutions
5) Apply problem solving and object oriented design skills to build a simple systems prototype
6) Understand the ICT profession in systems analysis and design
7) Communicate using effective oral and written communication tools, act in a professional manner and be an effective team member or team leader
8) Review and describe the major legal and ethical issues with respect to systems analysis and design
Weight 25% of the total assessments
Total Marks 25
Word Limit 2000-2500 words
Due Date Week 11
Submission
Guidelines • All work must be submitted on Blackboard by the due date along with a completed Assignment Cover Page.
• The assignment must be in MS Word format, 1.5 spacing, 11-pt Calibri (Body) font and 2 cm margins on all four sides of your page with appropriate section headings.
• Reference sources must be cited in the text of the report, and listed appropriately at the end in a reference list using Harvard or IEEE referencing style.
Your Tasks
This assignment continues from your first assignment. In the first assignment, you have analysed and modelled the current system by using structured analysis tools. This is a group assignment. Students are required to form into groups of four in order to prepare and present a solution to the case that was covered in Individual Assignment. This must be suitable for a presentation to company management.
Group Work and Project Teams
1. This task should be completed by project teams of four (4) students working together in a collaborative way. Students must form their own team (self-enroll) early in the semester.
2. Group work provides rich learning and social experiences to students. To be equitable and effective, however, a group project must operate on the basis of sustained input from all members of the group. There can be no room for ‘free riders’. A group project is the collective responsibility of the entire group, and if one member is temporarily unable to contribute, the group should be able to reallocate responsibilities to keep to schedule. In the event of longer-term illness or other serious problems involving a member of a project group, it is the responsibility of the other members to make the project supervisor aware of the situation straight away.
3. Marks will be awarded individually, based on participation, communication and contribution to the project.
4. The team leader will make one submission only on behalf of all members of the team. Ensure that the full name and student number of every member of the project team is provided as part of the submission.
5. A contribution form must be completed, signed and added in the report appendix.
More details of the case and specific problems can be found in a separate file ‘Individual and Group
Assignments Case Study’ on Bb.
Assignment’s Requirements
If students need more detail of the business, they should conduct their own research.
Diagrams should preferably be generated using Visio Pro or other virtual tools; however, students may use the drawing capabilities of other packages subject to the approval of the lecturer.
As a team, you need to review the proposals (Individual Assignment) that each member puts forward for submission. You need to discuss each proposal on its merits and decide which one will be best suited to use as your foundation for this assessment (Group Assignment). However, when modifying current system models, you should consider all members’ proposals and also your lecturer’s feedback. If you have not already done so, please make sure to join a group of four on BB as soon as possible.
The Report Components
Create a word-processed business report with:
• Document title
• Author(s) information
Executive Summary
• What this assignment is about and what you want to achieve.
Table of Contents
Introduction
• Why conduct system analysis and design for a business? What are some of the key things you need to consider when collecting requirements for the new proposed system?
• The purpose of your work
• Where you collected data and information for completing the report?
Problem(s) you are aiming to solve
In Individual Assignment, each student selected three (3) problems which they considered essential to solve and provided explanations. In your group, you should now discuss those problems and decide all key problems to be considered and why. Your proposed system should address these problems. You can quote your own Individual Assignment as a reference. Everything has been discussed in Individual Assignment, you shouldn’t repeat details in Group Assignment.
Scope and System Requirements (Proposed System)
• Description of Proposed System: You are required to provide a brief description of the proposed system and clearly explain the system’s objectives and constraints.
• Describe how would you apply the data gathering techniques effectively to gather system requirements (there are many techniques which you can adopt, such as ‘Interviews’…).
• List all system requirements you identified: List all functional and non-functional requirements for the proposed system. Provide a brief explanation for each of the requirements, particularly those which are new in the proposed system. You should explain why you added the new requirements and how they help to solve the problems identified.
User Stories and Acceptance Criteria
• A brief explanation of each stakeholder’s potential interests in the new system
• Identify different types of users and write at least TWO sample user stories based on each of the key stakeholders’ requirements. You should also list the key acceptance criteria.
Use Case Descriptions
You are required to
• Provide a brief use case description for each of key functions.
• Select 2 key use cases to create intermediate level use case descriptions.
• Select at least 1 of the 2-intermediate level use case descriptions to develop a full (formal level) use case description.
Recommendations
• Suggest and compare at least three (3) different types of solutions (e.g. develop from scratch, COTS, cloud-based etc.) and the advantages and disadvantages of each type for the business case. Discuss whether internal or external development would be more suitable for the proposed solution.
• Make your recommendation as to the most appropriate solution for the case with your justification as to why it is the best solution.
• Discuss what steps the case business needs to take if they follow your recommended solution and wish it to be successfully implemented and adopted.
• Confirm project feasibility by briefly discussing the economic, organisational, technical, and other factors along with the required resources and time schedule. You are not required to provide actual numbers e.g. costings or specific dates.
• Briefly discuss the most suitable methodology (e.g., Agile or Waterfall) which you consider the business can adopt for their new system’s analysis, design and implementation process.
• Justification of the chosen modelling approach – compare and contrast the structured analysis and design techniques and models with other modelling techniques (e.g., the object-oriented models and techniques), and clearly identify the strengths and weaknesses of each set. Your justification should be supported by appropriate references and linked to the case.
• A brief explanation on how you manage changes (both technical and people).
Please note that this assignment requires research and analysis. You are not just answering ‘what’ questions, but most importantly ‘why’ & ‘how’ questions. You should include relevant references, which can support your ideas and points of view. Your proposal & analysis should be comprehensible to management and to users who are computer literate. Your discussion and points of view should be supported by academic references (Journal articles, books, book chapters, conference papers and leading researchers’ blogs, published industry examples, etc.).
Conclusion
Summarize the whole assignment, your key findings and limitations.
Reference list
List all references used in the report. You need at least 6 to 8 journal references for Group Assignment. You have to follow the newest Harvard referencing system.
NB: this is a business report and should be written accordingly i.e. directed to the customer who is Sunshine Motors’ CEO and management team. It should reflect your understanding of the tasks required. Please make sure you start earlier and DO NOT WAIT to the final week.
Appendices
All modelling components (All tables and models) should be put in appendices:
• You are required to use the CRUD technique to identify new use cases for the proposed system which link to 3 or 4 new added data entities (you have to use both CRUD tables).
• You are required to complete an event table which includes all key events (10 to 12) for the new proposed system. Depends on your suggestions for the new proposed system, some of the Events of the current system may continue to apply to the Proposed System.
• OO Modelling (for the proposed system)
o Use case diagram: Present the system proposal using the OO modelling approach. Describe the key system functions and indicate the automation boundary of the information system as well as its users using a use case diagram. o Activity diagram: You are required to select your fully developed use case descriptions and develop corresponding activity diagram.
Notes on formatting and structure
It is expected that all work submitted would have been edited for spelling, grammar and clarity.
The Report should include *Title page, *Executive Summary, *Table of Contents, Introduction, Main Body (you can provide appropriate headings and sub headings for this section, for example, proposed system description, functional and non-functional requirements……, etc.), Conclusion, Recommendation, *References and *Appendix. Please note that accurate referencing using the latest version of the Harvard system (e.g. reference list and content) is a very important aspect of your assignment.
NB: Items marked with an * do NOT form part of the word count.
Bonus Points (up to 5 marks)
All groups or individuals have a chance to gain bonus points if you or your group has covered one or more the following points (please note that if you submit assignment late, we do not consider your bonus attempts):
• Provide an excellent report or models
• Complete additional tasks to fulfil the assignment, such as detailed use case descriptions.
• Discuss the Agile approach and discuss possible Agile tools that can be used to analyse the current/ proposed system.
• Detailed comparison of the traditional and OO approach.
• Demonstrate a sound research effort via high quality of references.
Any evidence of plagiarism will result in a Fail. Collaborative discussion with
other members in the unit around concepts and additional examples is highly recommended, but do not copy.
We have adopted Self Check facility for assessment submission. This facility provides a matching service which will compare Draft and/or Final Submissions with a significant
database of web published resources, including online databases and journals. In the case of a final submission, this will also be compared with other Holmes items submitted previously. By making use of the draft option and receiving reports back from Self Check it is expected students will be able to self-assess and correct submissions. It is the student's responsibility however, to familiarise themselves with how to avoid plagiarism please ask if you are not sure.
Don’t forget to keep back up. If your assignment goes astray, whether your fault or ours, you will be required to re-produce it. Lack of back-up will not be taken as an excuse for lost materials.
Late assignments may result in a lower grade for the assignment in terms of Holmes assessments guidelines.
How you will be assessed?
Please refer to the marking guide on blackboard